`cabal update` aborts everything when _one_ of the configured remotes is offline.
Open
cabal-install: other
type: bug
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
- have more than one remote configured
- `cabal update`
- one of the configured remotes answers with 503/504 whatever HTTP status codes
- expected behaviour: the other remotes are still updated properly.
- observed: the process aborts right after printing the error message.
(cabal version is some few-weeks old HEAD (some 1.25.0.0), if it matters)
Contributor guide
Assessment
This issue has not been assessed yet.