-
Notifications
You must be signed in to change notification settings - Fork 170
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
Resolve the pesky "website may be down" errors during rosdep {init, update}
#808
base: master
Are you sure you want to change the base?
Conversation
EDIT: rewrote the change instead of relying on git merge. All tests passing now |
Codecov Report
@@ Coverage Diff @@
## master #808 +/- ##
==========================================
- Coverage 74.96% 74.06% -0.90%
==========================================
Files 42 42
Lines 3283 3285 +2
==========================================
- Hits 2461 2433 -28
- Misses 822 852 +30
Continue to review full report at Codecov.
|
testing if the fault is in CI or my code
Detected while using rosdep (ros-infrastructure/rosdep#808)
rosdep {init, update}
New desciption
While trying to recreate the env for bad networks, I found an pesky issue in rosdep init. This PR resolves that but not the handshake time-out issue.
Old description
On some networks, the following error is observed:
This PR resolves the issue by trying the connection multiple times. Increasing timeout was tried but did not always succeed.
Followup from #687@nuclearsandwich Would it be possible to have a test env for this?