-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Catch IOException when Apalache server binds in-use address #2676
Comments
I spent a bit of time on this, but it seems to fail somewhere inside ZIO. Giving up for now, because I've hit my self-imposed timebox on this. |
I just ran into the same issue. This would be hard even for an experienced user to understand what's going on. Could we get rid at least of the zio stack trace? @shonfeder wdyt? |
I managed to strip these long stacktraces, preserving only the root cause stacktrace:
WDYT, is it enough? |
Awesome! Ideally, if we know the failure reason we can avoid any stack trace at all. |
Binding an in-use address (viz. port) from Shai / Apalache server results in a lengthy error trace.
We should catch and handle the exception.
Example stacktrace
The text was updated successfully, but these errors were encountered: