@kriskowal and I were experimenting with tcp-netstring.js and such and the daemon hung occasionally.
Steps to reproduce
I'm not sure exactly.
One hypothesis from @kriskowal : Seems to occur after restart, like there’s an EADDRINUSE dying silently somewhere (or in the tcp worker log)
And that might be preventing reviveNetworks from progressing
Describe the bug
@kriskowal and I were experimenting with
tcp-netstring.js
and such and the daemon hung occasionally.Steps to reproduce
I'm not sure exactly.
One hypothesis from @kriskowal : Seems to occur after restart, like there’s an EADDRINUSE dying silently somewhere (or in the tcp worker log) And that might be preventing reviveNetworks from progressing
some steps leading up to it:
where
endo mv
was more likeendo eval "E(NETS).write('tcp', tcp')" tcp
Expected behavior
daemon doesn't hang, even when using TCP
Platform environment
endo version:
2024-04-25 14:29 2afacc58d feat(cli): Expand options for storing values (#2237)
linux. node 18.
Additional context
see also related discussion