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

fatalError() during high concurrency test #187

Closed
vlm opened this issue Mar 19, 2018 · 1 comment · Fixed by #191
Closed

fatalError() during high concurrency test #187

vlm opened this issue Mar 19, 2018 · 1 comment · Fixed by #191

Comments

@vlm
Copy link
Contributor

vlm commented Mar 19, 2018

Expected behavior

Users generally expect Swift NIO not to fail with internal assertions and fatalErrors they couldn't catch.

Actual behavior

Fatal error: Invalid FSM transition attempt: state complete, input connectTimeoutElapsed: file swift-nio/Sources/NIO/HappyEyeballs.swift, line 417
Illegal instruction: 4

Steps to reproduce

Compile and run the attached code against the master.

If possible, minimal yet complete reproducer code (or URL to code)

reproduce.swift.

SwiftNIO version/commit hash

b8d883da2c2090d02ec4890b5ab5c7c9bfa30935

Swift & OS version (output of swift --version && uname -a)

Apple Swift version 4.1 (swiftlang-902.0.38 clang-902.0.30)
Target: x86_64-apple-darwin17.4.0
Darwin Levs-MacBook-Pro.local 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64
@vlm vlm changed the title High concurrency assertion High concurrency fatalError Mar 19, 2018
@vlm vlm changed the title High concurrency fatalError fatalError() during high concurrency test Mar 19, 2018
@Lukasa
Copy link
Contributor

Lukasa commented Mar 19, 2018

Should be fixed by #191.

weissi pushed a commit to weissi/swift-nio that referenced this issue Jun 13, 2020
motivation: docs scripts is broken on selinux due to restriction on ssh-agent

changes:
* change the jazzy workspace to a directory accessible by the CI node so we can push from the agent instead of from the docker container
* dont remove older docs when pushing new ones
* add version information and source links
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 a pull request may close this issue.

2 participants