Fixed
Status Update
Comments
su...@google.com <su...@google.com> #2
Heres the other logs if the previous log isnt detailed
ku...@gmail.com <ku...@gmail.com> #3
Im trying to open the page again using my other project (cgdx-1132485) using Microsoft Edge Version 127.0.2651.98 (Official build) (64-bit) with Windows 11 23H2 Build 22631.3880.
But maybe this helps (Edit: even though if the error said 'Too Many Request', im just opening it normally without reopen the page many times)
VM1948 m=hfcr:34
POSThttps://accounts.google.com/RotateCookies 429 (Too Many Requests)
db @ VM1948 m=hfcr:34
fb @ VM1948 m=hfcr:35
(anonymous) @ VM1948 m=hfcr:33
setTimeout
(anonymous) @ VM1948 m=hfcr:33
$a @ VM1948 m=hfcr:33
e @ VM1948 m=hfcr:32
(anonymous) @ VM1948 m=hfcr:32
setTimeout
Xa.start @ VM1948 m=hfcr:32
gb @ VM1948 m=hfcr:36
(anonymous) @ VM1949 RotateCookiesPage:1
But maybe this helps (Edit: even though if the error said 'Too Many Request', im just opening it normally without reopen the page many times)
VM1948 m=hfcr:34
POST
db @ VM1948 m=hfcr:34
fb @ VM1948 m=hfcr:35
(anonymous) @ VM1948 m=hfcr:33
setTimeout
(anonymous) @ VM1948 m=hfcr:33
$a @ VM1948 m=hfcr:33
e @ VM1948 m=hfcr:32
(anonymous) @ VM1948 m=hfcr:32
setTimeout
Xa.start @ VM1948 m=hfcr:32
gb @ VM1948 m=hfcr:36
(anonymous) @ VM1949 RotateCookiesPage:1
su...@google.com <su...@google.com> #4
I Had same issue with my Laravel project that work in IDX Project. Im using IDX Laravel Template for this
yb...@google.com <yb...@google.com> #5
It seems that everyone is struggling with this issue? (Because I see the viewer count at 60+) I hope that this issue can be fixed ASAP
ia...@gmail.com <ia...@gmail.com> #6
i'm also experiencing this issue for about a week now in one of my workspace
yb...@google.com <yb...@google.com> #7
Automated by Blunderbuss job monospace-web-ide-autoassigner for config bug_blunderbuss_config for component 1379083.
da...@google.com <da...@google.com> #8
Same issue for since morning. Been trying to get access this whole time but to no avail.
Description
It is preferable to have a destructive migration to crashing the app.