My friend and I both started having this rate limit issue today, maybe starting a hour ago.
Same started happening for me as well - around an hour ago.
Same for me. I think this might be a widespread issue affecting many users currently.
same for me too… our team and i also face same issue
Same for me too ?? What happenend ![]()
same for me. happened across multiple machines
Ok happened to me too, seems like everyone is having this issue right now?
I am having the same problem. Please could you increase my rate limit? ![]()
Same thing happening to me, too from today. Could you increase my rate limit?
Same here. I am using multiprocessing to do CPU heavy tasks, but only 1 process is actually logging.
Same here, only 1 process is actually logging
Same for me. It looks like others are experiencing similar issues right now.
Same! It really looks a common problem today ![]()
I encouter the same 429 problem today.
Could you please help me. I am really anxious because the deadline for my current task is only in a few days
Same here; any update on this from the wandb site?
Hello Team, having the same problem. Is there a way to specify the parameter in CLI?
Literally the same error. In the end got my students to do it for me. They said apparently wandb put everything to their graphQL server so it’s not really designed to log a bunch of high-res data.
Honestly was kinda pissed off by this. My students were the same so they made mlop.ai. It was free labor so I said yes. Not a bad platform tbf just not as feature rich. Here’s the link for those that just wanna have the logger log some data fast that won’t crash your run GitHub - mlop-ai/mlop: Next Generation Experimental Tracking for Machine Learning Operations