You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I just happened to implement a bad behaviour for my Server-Server communication (basically: Retrieve artist > Retrieve all Albums > add all unknown Artists to DB > goto next Artist in DB with lowest updated timestamp)
This made me hit rate limits (quite hard) for my in-Development flagged testing App.
The client now waited - silently - apparently indefinitely.
Could be either provide a way to:
Set a hard max-wait for Retry behaviour?
Enable some sort of logging capabilities that the client will wait?
The text was updated successfully, but these errors were encountered:
I'd be open to us implementing the ability to inject a *slog.Logger into the client for these sorts of messages now that slog is available within stdlib.
Hey, I just happened to implement a bad behaviour for my Server-Server communication (basically: Retrieve artist > Retrieve all Albums > add all unknown Artists to DB > goto next Artist in DB with lowest updated timestamp)
This made me hit rate limits (quite hard) for my in-Development flagged testing App.
The client now waited - silently - apparently indefinitely.
Could be either provide a way to:
The text was updated successfully, but these errors were encountered: