You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: dmgroom[at]gmail.com [Submitted to the original trac issue database at 5.30pm, Monday, 21st May 2007]
I'm not sure under what circumstances this occurs, and it may be when I myself do something wrong, but I have noticed duplicated nodes, and segments.
Occasionally I have noticed these duplicated segments form a way as well.
It is possible that these occur when either a way is split using Potlatch, or when a new way is joined onto an existing one with a new node. (maybe its not exactly the fault of Potlatch but due to the server being unresponsive [lots of 500 Internal server Errors being reported by JOSM today] and not all of Potlatch's edits get uploaded to the server?)
The text was updated successfully, but these errors were encountered:
Author: richard[at]systemeD.net [Added to the original trac issue at 1.53pm, Wednesday, 23rd May 2007]
It seems likely that this happens when the server is slow.
When Potlatch uploads a new way, the sequence goes something like this:
Potlatch SWF sends "putway" message to server
Server creates any nodes not in the previous version of the way
Server creates any segments not in the previous version of the way
Server deletes any nodes and segments not in the new version of the way
Server saves way_segments records to link the segments together as a way
Server returns "ok" and new way/node/segment IDs
Potlatch SWF updates its (internal) way object with the new details
This means that if the server is slow, and the user edits a way twice in succession, the nodes and segments will be created twice - because the second "putway" will be sent before the object has been updated in step 6.
Probably the best way to fix this is for Potlatch only to send "putway" for a given way when all previous putways on that way have been successfully returned.
Reporter: dmgroom[at]gmail.com
[Submitted to the original trac issue database at 5.30pm, Monday, 21st May 2007]
I'm not sure under what circumstances this occurs, and it may be when I myself do something wrong, but I have noticed duplicated nodes, and segments.
Occasionally I have noticed these duplicated segments form a way as well.
It is possible that these occur when either a way is split using Potlatch, or when a new way is joined onto an existing one with a new node. (maybe its not exactly the fault of Potlatch but due to the server being unresponsive [lots of 500 Internal server Errors being reported by JOSM today] and not all of Potlatch's edits get uploaded to the server?)
The text was updated successfully, but these errors were encountered: