Skip to content

Conversation

nstiurca
Copy link

@nstiurca nstiurca commented Jul 7, 2023

On my system, I'm actually triggering the ENAMETOOLONG error code with strings of length ~150 characters. Not sure why, but I re-wrote the code based on the suggestion in the upstream bug.

@codecov
Copy link

codecov bot commented Jul 10, 2023

Codecov Report

Patch coverage: 87.50% and project coverage change: -0.02 ⚠️

Comparison is base (e33786c) 89.69% compared to head (ec5fd2c) 89.67%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #264      +/-   ##
==========================================
- Coverage   89.69%   89.67%   -0.02%     
==========================================
  Files          10       10              
  Lines        1775     1782       +7     
==========================================
+ Hits         1592     1598       +6     
- Misses        183      184       +1     
Impacted Files Coverage Δ
src/utils.jl 89.20% <85.71%> (-0.27%) ⬇️
src/read.jl 88.73% <100.00%> (+0.03%) ⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

true
catch e
if isa(e, Base.IOError)
e.code != -36 # -36 is ENAMETOOLONG; other IO errors indicate valid filename
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this code consistent across OS platforms? can we add a test to catch the new code paths here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect the original code might work as intended on Windows, and this branch wouldn't ever be triggered. Still, yeah I'll try to write a test.

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