429 encountered (Filestream rate limit exceeded, retrying in 2.2 seconds.), retrying request

[avito]

Hello!
Finally managed to launch training successfully but got this weird message like the one the person received in the post below. Could you, please, increase my limit too?

After 429 encountered (Filestream rate limit exceeded, it takes three days since I click stopping

Hello! The same code runs successfully and in a normal speed before, but last week, I have met the problem like: wandb: 429 encountered (Filestream rate limit exceeded, retrying in 2.441980818670473 seconds), retrying request. After that, it runs extremely slower than before. Some runs does not report this issue in the logs runs much slower too(running the same code) . I tried to use ‘wandb init’ , start a new project, kill the processes and only keep <10 runs running… but it does not solve t…

[uma-wandb]

@avito I was able to bump your rate limit - please let me know if all is good on your end

[gonzabenito]

Hello, I have the same issue and I am unable to log my loss/epoch data. Please be kind to increase my limit?

[perezjc]

Hi there,

I’m getting this exact same issue but it seems more like a bug.

I’m not running (nor logging) anything: this warning (wandb: 429 encountered (Filestream rate limit exceeded, retrying in 2.0 seconds.), retrying request) appears even when I simply start a python terminal and run wandb.init().

Could you please help me? Thanks!