Tim Daubenschütz
Tim Daubenschütz
this is most likely an error that originates from the remote node crashing during a reconciliation
> To be honest, I am not sure how to test this case. Locally, I test this via pressing Ctrl+C to exit the server. Do you have an idea? Can...
ok sounds good thank you!
I'm currently traveling until after Oct 18 and this is something I have to take a little while to understand so I hope you don't mind if this will take...
I don't understand why we're trying to clear the interval with `unref`, I've not seen that anywhere. I'm only familiar with `clearInterval` and I've checked the nodejs docs and it...
> If not unref'ed the event loop would always keep a single item in the loop and not exit I'm not sure I understand the use case. In an application...
from: https://github.com/expressjs/session > Note The expires option should not be set directly; instead only use the maxAge option. Can you address your use case by using maxAge instead of expires?...
> because the `Expires` value must always be in GMT and it gets "calculated" I wasn't able to confirm this: - https://www.rfc-editor.org/rfc/rfc2616#section-3.3.1 - https://www.rfc-editor.org/rfc/rfc6265#section-4.1.1
I don't understand your problem. From my understanding, both express/session and fastify/session set both expires and maxAge in a similar way.
Interesting. Can you maybe refer me to a section of the Hetzner REST API where it's specified how user data can be created and added to a machine?