Skip to content

Analyzer: Improve error handling when file paths can't be read despite escalated privileges - #1176

Merged
d4rken merged 1 commit into
mainfrom
io-read-fallback-behavior
May 24, 2024
Merged

Analyzer: Improve error handling when file paths can't be read despite escalated privileges#1176
d4rken merged 1 commit into
mainfrom
io-read-fallback-behavior

Conversation

@d4rken

@d4rken d4rken commented May 23, 2024

Copy link
Copy Markdown
Member

Shouldn't happen, but if it happens, we have some fallbacks to turn to.

See #1173

…e escalated privileges

Shouldn't happen, but if it happens, we have some fallbacks to turn to.

See #1173
@d4rken d4rken added enhancement New feature, request, improvement or optimization c: StorageAnalyzer labels May 23, 2024
@MarkyMarkDE

MarkyMarkDE commented May 23, 2024

Copy link
Copy Markdown
Collaborator

Is this (shouldn't happen but happens) similar with my bugs from ticket #1064?
This bug still exists since then and occur mostly when you restart your phone round 30 mins before your schedule should run

@d4rken

d4rken commented May 24, 2024

Copy link
Copy Markdown
Member Author

Is this (shouldn't happen but happens) similar with my bugs from ticket #1064? This bug still exists since then and occur mostly when you restart your phone round 30 mins before your schedule should run

Hm I don't think it's similar. The error from your ticket seems to be that the worker is prematurely canceled (CancellationException), it's not directly related to a failed I/O operations. Would need a debug log to get further insights into that.

@d4rken
d4rken merged commit 3d69d6c into main May 24, 2024
@d4rken
d4rken deleted the io-read-fallback-behavior branch May 24, 2024 03:54
@MarkyMarkDE

Copy link
Copy Markdown
Collaborator

Is this (shouldn't happen but happens) similar with my bugs from ticket #1064? This bug still exists since then and occur mostly when you restart your phone round 30 mins before your schedule should run

Hm I don't think it's similar. The error from your ticket seems to be that the worker is prematurely canceled (CancellationException), it's not directly related to a failed I/O operations. Would need a debug log to get further insights into that.

mmhh okay, but unfortunately I don't know first if this happens or not. Hope to get it reproduced ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: StorageAnalyzer enhancement New feature, request, improvement or optimization

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants