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

Bogus error messages "BUG in SwiftNIO, unleakable promise leaked" #2855

Closed
weissi opened this issue Aug 30, 2024 · 4 comments · Fixed by #3027
Closed

Bogus error messages "BUG in SwiftNIO, unleakable promise leaked" #2855

weissi opened this issue Aug 30, 2024 · 4 comments · Fixed by #3027

Comments

@weissi
Copy link
Member

weissi commented Aug 30, 2024

If a user accidentally shuts down the ELG before actually being done, they often get

BUG in SwiftNIO (please report), unleakable promise leaked.:486: Fatal error: leaking promise created at (file: "BUG in SwiftNIO (please report), unleakable promise leaked.", line: 486)

which is both

  1. wrong (in all cases that I've seen)
  2. Misleading

the message should be adjusted to say that it's likely that the EventLoop (which we can actually print!) was likely shut down already (and that it's a bug in NIO if it isn't shut down)

@weissi
Copy link
Member Author

weissi commented Dec 5, 2024

CC @Lukasa

This message is bogus and we need to reword it. Suggestions?

@Lukasa
Copy link
Contributor

Lukasa commented Dec 6, 2024

Do we think having this message is pulling its weight at all? We already print a message about shutting down the ELG in most of these cases.

@weissi
Copy link
Member Author

weissi commented Dec 6, 2024

Do we think having this message is pulling its weight at all? We already print a message about shutting down the ELG in most of these cases.

Are you suggesting to delete the message entirely and just making it preconditionFailure()? Fine by me, but I'd probably put something like promise of already-shutdown EventLoop leaked or smth.

@Lukasa
Copy link
Contributor

Lukasa commented Dec 9, 2024

I don't have a strong opinion either way, honestly.

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