Skip to content
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

Fix regression in OSError handling logic #203

Merged
merged 1 commit into from
Nov 4, 2024
Merged

Conversation

pyrco
Copy link
Contributor

@pyrco pyrco commented Nov 4, 2024

dissect.target's NotADirectoryError and FileNotFoundError are now proper subclasses of the std.NotADirectoryError and std.FileNotFoundError and by this a subclass of OSError, so they should be treated as such.

dissect.target's NotADirectoryError and FileNotFoundError are now proper
subclasses of the std.NotADirectoryError and std.FileNotFoundError and
by this a subclass of OSError, so they should be treated as such.
Copy link

codecov bot commented Nov 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.15%. Comparing base (6266553) to head (396df6d).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #203      +/-   ##
==========================================
+ Coverage   47.09%   47.15%   +0.06%     
==========================================
  Files          26       26              
  Lines        3421     3425       +4     
==========================================
+ Hits         1611     1615       +4     
  Misses       1810     1810              
Flag Coverage Δ
unittests 47.15% <100.00%> (+0.06%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pyrco pyrco merged commit 910e364 into main Nov 4, 2024
16 of 20 checks passed
@pyrco pyrco deleted the fix-OSError-regression branch November 4, 2024 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants