Skip to content
Discussion options

You must be logged in to vote

It seems that this error is not strictly related to k8s, but to my tokyo runtime (main wasn't async) which was getting destroyed too fast.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@clux
Comment options

clux Sep 15, 2025
Maintainer

Answer selected by clux
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants