-
Notifications
You must be signed in to change notification settings - Fork 10
fix: resource cleanup #454
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: mineme0110 <[email protected]>
Signed-off-by: mineme0110 <[email protected]>
Signed-off-by: mineme0110 <[email protected]>
ZStream.fromQueue(inboundQueue) | ||
ZStream | ||
.fromQueue(inboundQueue) | ||
.timeout(10.seconds) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think having a timeout here is good.
Because in the case of web-sockets you may want to keep it open for a longer time.
the .ensuring(inboundQueue.shutdown)
LGTM
I'm not sure this will make any different for the out of memory problem. I really don't like this whole implementation of DIDCommRoutes. I did this very hachish. |
Signed-off-by: mineme0110 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems it's not working, suddenly the mediator dies. tested on cloud, will test locally
edit: locally worked, checking the cloud configuration
@mineme0110 this might be outdated due recent findings. should we close this PR? |
What was changed and what it is solving
How it was tested
Release Notes / Changelog