Attempt to reconnect long-running CLI commands in case of network timeout
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
This [Feature Request](https://github.com/hashicorp/nomad/issues/12062) makes "Error fetching deployment" seem like a minor nuisance.
After updating our cluster from 1.3.x to 1.5.6 I see this error every single time I run `nomad run job ...` - seems like a regression at this point.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Feature Request and reproduce the reported behavior using `nomad run job ...` against the affected cluster versions. Trace the long-running command's handling of network timeouts and determine what behavior is required so deployment fetching can reconnect instead of showing "Error fetching deployment." Done means the timeout case is handled consistently without interrupting the command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100