Vincent Comments - Answer Overflow

@Frederik Any updates here? We noticed the .getWebSocketsAutoResponseTimestamp() bug seemed to be fixed briefly yesterday afternoon, but today the bug is back again. Was a roll-out attempted but rolled back, perhaps?

22 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

I spoke a little too soon. Although in most cases retry works, we're still encountering some internal errors where retrying does not have an effect. So our issues aren't completely resolved yet.

20 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

@Frederik We just rolled out the change that grabs a new stub on every retry and that seem to have done the trick indeed—thanks! 🙏 This morning, we're still getting these "internal errors" but now whenever we get them, the retry will work (typically on the first retry), which makes this issue a lot less urgent for us. We'd still like to not get those "internal errors" of course, but at least it won't be causing issues for us anymore.

20 replies

CDCloudflare Developers

•Created by Vincent on 4/9/2024 in #durable-objects

Amazing, @Frederik — thanks for

@Frederik Thanks! Would you mind sending us a message when the fix is in production? Then we can do a final check and inform our customers.

22 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

Thanks, @Frederik — that's good information, will try that next.

20 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

20 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

@Frederik Small update here: we investigated a bit more today, and still have no good sense of where those internal error errors are coming from, but… we have noticed that they all don't carry the remote: true field, meaning it's unlikely that they're actually coming from transactional storage APIs—contrary to the initial hunch we had before. If so, they would have been thrown by the Durable Object, in which case we would see these errors having a remote: true property when caught in the worker. So it's more likely that they have a different origin, and maybe the focus on transactional storage was a red herring.

20 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

@Frederik Just sent you all the details. For us, it's mostly the internal error, not the Network connection lost thing.

20 replies

CDCloudflare Developers

•Created by chronark on 4/18/2024 in #durable-objects

since 2 days ago I'm getting a ton of

✅ Done!

20 replies

CDCloudflare Developers

•Created by Vincent on 4/9/2024 in #durable-objects

Amazing, @Frederik — thanks for

Appreciate the help, @Frederik !

22 replies

CDCloudflare Developers

•Created by Vincent on 4/9/2024 in #durable-objects

Amazing, @Frederik — thanks for

@Frederik I've also opened a GitHub issue for this one: https://github.com/cloudflare/workerd/issues/2025 — hope this helps to get this resolved! 🙏

22 replies

CDCloudflare Developers

•Created by Vincent on 4/9/2024 in #durable-objects

Amazing, @Frederik — thanks for

@Frederik In case it will help, here is a minimal replication of the bug: https://github.com/nvie/cloudflare-repros/tree/gwsart-bug?tab=readme-ov-file#the-replication Demo video using that minimal replication: https://share.cleanshot.com/nzVS2sMSHgz7YLcrTdXZ

22 replies

CDCloudflare Developers

•Created by Vincent on 4/9/2024 in #durable-objects

Amazing, @Frederik — thanks for

Ohhh, that's somewhat good news then. I was about to sit down and try to make a minimal replication of it, but maybe I can spare myself the effort in that case. Thank you very much! We're anxiously awaiting the fix! 🙏

22 replies

CDCloudflare Developers

•Created by Vincent on 4/9/2024 in #durable-objects

Amazing, @Frederik — thanks for

Hi Frederik, thanks for getting back to me! This morning I have been doing some testing, but unfortunately we're still running into this issue. We're still seeing issues where the returned date by .getWebSocketsAutoResponseTimestamp(mysocket) is too old. There have definitely been more recent ping/pongs that our clients have received from the auto-response, but it looks like the last auto-response timestamp still isn't reliably getting updated 😞

22 replies

Gaming

Programming