21 replies

Amazing, @Frederik — thanks for

Amazing, @Frederik — thanks for confirming it's an issue on your end, and we're looking forward to a fix!

VincentOP•4/15/24, 12:30 PM

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).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

VincentOP•4/15/24, 2:26 PM

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!

VincentOP•4/16/24, 12:54 PM

@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

VincentOP•4/16/24, 1:02 PM

@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!

GitHub

🐛 Bug Report — `.getWebSocketAutoResponseTimestamp()` not returning...

The return value of the state.getWebSocketAutoResponseTimestamp() method doesn't return the correct timestamp in production. It does, however, work locally. Minimal replication Here is a minima...

VincentOP•4/17/24, 1:40 PM

Appreciate the help, @Frederik !

VincentOP•4/21/24, 11:10 AM

@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.

VincentOP•4/23/24, 6:49 AM

@Frederik Any updates here? We noticed the .getWebSocketsAutoResponseTimestamp().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?

VincentOP•4/24/24, 4:04 PM

Will do – thanks for the update!

VincentOP•4/24/24, 4:06 PM

Our issues are definitely trending down, this is great! Thank you so much for getting this addressed!

Amazing, @Frederik — thanks for

Similar Threads

Similar Threads

Similar Threads