Fossil SCM
Time skew when cloning a large repository via slow connection
Fixed
25d3f8d5641deed…
· opened 15 years, 4 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Minor
- Resolution
- Fixed
- Subsystem
- —
- Created
- Nov. 14, 2010 11:26 a.m.
Bytes Cards Artifacts Deltas
Sent: 53 1 0 0
processed: 99% fossil: *** time skew *** server time differs by 12.2 minutes
Received: 4720686 296 288 6
Total network traffic: 234 bytes sent, 922143 bytes received
Client is connected to the Internet using GPRS and connection is very slow. But I guarantee that the difference between server and client time is not more than 1-2 seconds. Does this message indicate a problem or I can safely ignore it?
drh added on 2011-03-02 22:50:35 UTC: It's just a warning. I have modified the time skew detection to take into account large transfers over slow networks. Hopefully that will help.