Network Error: Connection reset by peer (os error 104)
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
I don't use often git-workspace but since one or two month I get this error:
$ git workspace update
Fetching repositories...
Error: Error fetching repositories from Gitlab user/group michel-thomas at https://gitlab.com in directory gitlab.com, using the token stored in GITLAB_TOKEN
Caused by:
0: https://gitlab.com/api/graphql: Network Error: Network Error: Error encountered in the status line: Connection reset by peer (os error 104)
1: Network Error: Error encountered in the status line: Connection reset by peer (os error 104)
2: Connection reset by peer (os error 104)
I checked the token: Ok, scope api, not expired.
When I go into one of my repos subdir, git pull / git fetch is working well.
And version is latest:
$ git workspace -V
git-workspace 1.6.0
Thanks for your help.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with git workspace update against the GitLab account and token described in the report, then compare it with the working git pull and git fetch commands. The issue is done when the update command can fetch the repositories without the connection-reset error while retaining the reported GitLab setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, graphql, rust
- Domain
- api, cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100