bzr should automatically retry idempotent network operations
Bug #390486 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
It would be nice if bzr transports (or a higher level) would automatically retry idempotent or readonly operations when there seems to be a transient networking error. There should be a limit on the number and speed of retries.
See also bug 390485.
| summary: |
- bzr should automatically try idempotent network operations + bzr should automatically retry idempotent network operations |
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
| Changed in bzr: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
I think this is basically fixed by John's flagging of safe-to-retry operations in 2.5. There might be other cases where we need to detect that we ought to retry.