-
-
Notifications
You must be signed in to change notification settings - Fork 357
CQ: we should check the return value of lseek #5783
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
base: main
Are you sure you want to change the base?
Conversation
An attempt to unify checks and error messages
Perhaps this already revealed some errors. It fails tests:
|
Yes, as it just checks if a return value does not indicate on an error, this really is a bug in r.random. If I read the code correctly, there is no need to call |
Rewinding a raster map can lead to lseek errors and generally should not be done, as raster reading functions perform seek on their own if required.
MacOS failure is caused by #5787 |
Concerning the message that you applied almost everywhere, isn't it similar to one of your examples last week where |
There shouldn’t be any reason to cast |
An attempt to unify checks and error messages.
There are more places where
lseek
return value should be checked, but I don't have time to work on them now.