10000 stmhal: OSError's argument should be numeric errno · Issue #516 · micropython/micropython · GitHub
[go: up one dir, main page]

Skip to content

stmhal: OSError's argument should be numeric errno #516

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

Closed
pfalcon opened this issue Apr 21, 2014 · 2 comments
Closed

stmhal: OSError's argument should be numeric errno #516

pfalcon opened this issue Apr 21, 2014 · 2 comments

Comments

@pfalcon
Copy link
Contributor
pfalcon commented Apr 21, 2014

I just made corresponding changes to unix: acb1388 , and I suggest stmhal and other ports to follow - it's important to let people reliably test/recover from errors.

I also going to add "errno" module to micropython-lib, and then I suggest for stmhal to use the same numeric codes as Linux ;-).

@dpgeorge
Copy link
Member

Okay. Leave this open until I (or someone) gets round to it. I guess that's what issue trackers are for, after all!

dpgeorge added a commit that referenced this issue Jun 11, 2014
Also now returns correct POSIX errno when an IO operation fails.

Addresses issues #516 and #676.
@dpgeorge
Copy link
Member

stmhal/file.c now uses POSIX error codes, and returns a numeric errno as the first argument, following unix/file.c.

tannewt added a commit to tannewt/circuitpython that referenced this issue Jun 8, 2018
We now track the last time the background task ran and bail on the
PulseIn if it starves the background work. In practice, this
happens after the numbers from pulsein are no longer accurate.

This also adjusts interrupt priorities so most are the lowest level
except for the tick and USB interrupts.

Fixes micropython#516 and micropython#876
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

No branches or pull requests

2 participants
0