Fossil SCM
autosync fails after network outage
Closed
a1a08cb41896b1a…
· opened 15 years, 6 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Minor
- Resolution
- Overcome_By_Events
- Subsystem
- —
- Created
- Oct. 5, 2010 9:45 a.m.
I've noticed that when committing with autosync on, a failed network connection (say you forgot to turn it on),will stop syncing on all future commits until you do a another sync.
> fossil will automatically push your changes back to the server you > cloned from or whatever server you most recently synced with.
Can it be changed so it keeps trying to sync?
to reproduce
# clone repo # change file under vc # commit (autosync's correctly) # change file under vc # disconnect network # commit (fails to autosync - tries and fails) # reconnect network # commit (fails to autosync - does not retry)Issue # sync # change file under vc # commit (autosync's correctly) --
Comments (1)
system
2 years, 2 months ago
Closing as part of periodic cleanup.