-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It looks like this is resetting the url to the beginning. I uploaded a log here: https://gist.github.com/Locke/e6fd4d1a1966980e27ce0e453b9436c2 #8
Comments
It might work again. |
Waiting for the next Soup Timeout to prove it works :-) |
LGTM, thank you very much! I also like the idea of printing the status code :) Full log: https://gist.github.com/Locke/cfe735fd21b069242378fb62a1d75c67 Small excerpt:
|
Now I got it down to just one repetition? scratches head |
And retry count works again ^^ |
It had just one repetition, as the second one worked. Now I saw some more repetitions (edit: still on the previous commit dadb614):
|
As long as the request.get returns != 200 there schould be no repetitions. |
the if dlurl == old_url test might fix this. |
Ok, I've let f1e0670 run for a bit and it looks fine: https://gist.github.com/Locke/abf4f1066b2aceed5ae6c6363585faca |
It looks like this is resetting the url to the beginning. I uploaded a log here: https://gist.github.com/Locke/e6fd4d1a1966980e27ce0e453b9436c2
Small excerpt:
Originally posted by @Locke in #7 (comment)
The text was updated successfully, but these errors were encountered: