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

linuxWaitFd: make NetworkSubsystemFailed error unreachable #6827

Merged
merged 1 commit into from
Nov 16, 2020
Merged

linuxWaitFd: make NetworkSubsystemFailed error unreachable #6827

merged 1 commit into from
Nov 16, 2020

Conversation

heidezomp
Copy link
Contributor

@heidezomp heidezomp commented Oct 26, 2020

This error from os.poll is Windows-specific, so unreachable on Linux.

Closes #6794

@heidezomp
Copy link
Contributor Author

Rebased PR on top of master to hopefully fix spurious CI failures.

@heidezomp
Copy link
Contributor Author

The macOS build keeps failing in a test which seems to be comparing some translate-c output, but I'm not sure how to even read/diagnose the build output. Seems to be completely unrelated to this PR though.

@andrewrk
Copy link
Member

It's the pinned issue: #6830

Been trying to figure it out all day, sorry about that.

@heidezomp
Copy link
Contributor Author

heidezomp commented Oct 27, 2020

It's the pinned issue: #6830

Been trying to figure it out all day, sorry about that.

Thanks for the heads up!

Note to self: Read the actual pinned issues when something fishy seems to be going on! 😄

@heidezomp
Copy link
Contributor Author

Rebased PR on top of master once more now that #6830 is fixed.

This error from os.poll is Windows-specific, so unreachable on Linux.
@heidezomp heidezomp changed the title linuxWaitFd: handle NetworkSubsystemFailed error from os.poll linuxWaitFd: make NetworkSubsystemFailed error unreachable Oct 29, 2020
@heidezomp
Copy link
Contributor Author

This was fixed concurrently by @ifreund in 1b34365; rebased/updated my PR to make the error unreachable.

@ifreund
Copy link
Member

ifreund commented Oct 29, 2020

This was fixed concurrently by @ifreund in 1b34365; rebased/updated my PR to make the error unreachable.

IMO leaking the abstraction of std.os and making it unreachable isn't the way to go. perhaps the errorset could exclude that error when not using windows?

@heidezomp
Copy link
Contributor Author

IMO leaking the abstraction of std.os and making it unreachable isn't the way to go. perhaps the errorset could exclude that error when not using windows?

Since the #6600 proposal to get rid of/rework std.os has been accepted, perhaps we should defer this decision and decide this (how error sets deal with OS-specific errors) for the new high-level OS abstraction as a whole?

@andrewrk
Copy link
Member

Since the #6600 proposal to get rid of/rework std.os has been accepted, perhaps we should defer this decision and decide this (how error sets deal with OS-specific errors) for the new high-level OS abstraction as a whole?

I think your change is a nice improvement in the meantime :)

@andrewrk andrewrk merged commit 9ea4dda into ziglang:master Nov 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
standard library This issue involves writing Zig code for the standard library.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compile error "NetworkSubsystemFailed not handled in switch" in reading file in io_mode = .evented
4 participants