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
{{ message }}
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
I have received a lot of bids I could not accomplish because of networking problems. I have so far fixed that, but deal list is full and lagging behind, so all finished downloads fail on import because of missed deadline.
AFAIK there is no remove / cancel / cleanup command and I haven't found anything in the docs.
At the current moment for me the only way is to reinstall bidbod or wait for all the files in queue to fail ( but not after download completes )
The text was updated successfully, but these errors were encountered:
We can add some extra command to do that, but as mentioned in our chat (sharing here for others to read) this situation is already late on fixing the root problem.
You should definitely set the --running-bytes-limit to only accept load up to a cap you know considering your networking and sealing resources.
On a truly excepcional case where you got some out of ordinary networking problem, then maybe yes this potentially new CMD to cancel might be useful. But just clarifying here that would/should be used on last-resources scenarios.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have received a lot of bids I could not accomplish because of networking problems. I have so far fixed that, but deal list is full and lagging behind, so all finished downloads fail on import because of missed deadline.
AFAIK there is no remove / cancel / cleanup command and I haven't found anything in the docs.
At the current moment for me the only way is to reinstall bidbod or wait for all the files in queue to fail ( but not after download completes )
The text was updated successfully, but these errors were encountered: