-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle and propagate errors when checking if paths are Dirs, Files or Exist #13186
Handle and propagate errors when checking if paths are Dirs, Files or Exist #13186
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missed returns post ctx.ServerError
|
IMHO in future other devs will make same errors, due to bad API design. |
@rozhuk-im that is not idiomatic for go. |
Line 30 in f2a3abc
Probably, but similar things are used. |
…-report-errors-on-checking-exists
Codecov Report
@@ Coverage Diff @@
## master #13186 +/- ##
==========================================
- Coverage 42.25% 42.19% -0.06%
==========================================
Files 697 697
Lines 76631 76825 +194
==========================================
+ Hits 32377 32416 +39
- Misses 38932 39061 +129
- Partials 5322 5348 +26
Continue to review full report at Codecov.
|
@zeripath can you resolve the conflicts? |
@6543 Conflicts resolved |
Tests fail |
…-report-errors-on-checking-exists
The previous merge managed to break repo_form.go Signed-off-by: Andrew Thornton <[email protected]>
Agh ! it looks like when I resolved conflicts I introduced a bug in repo_form.go. Should now be fixed. |
🚀 |
🚀 |
com.IsFile
and the like although simple do elide the difference with errors on filesystem reads and may cause incorrect intepretations.This PR switches all uses of from
com.Is*
toutil.Is*
and makes a best guess as to what to do - mostly log and propagate the error up.This may make some misbehaving systems and OSs appear less stable but ... at least the problems are not being elided anymore.
Fix #13175
(I'm calling this a fix for that issue because although I do not know what is behind the underlying issue here - a new bug report with logs following on from this change would be more useful.)