id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17677	Large upload with multiple changesets fails silently. Failed to automatically close a full changeset.	anonymous	team	"Some background when this happened:
I have recently done an update/reimport of some trees. There were a total of about 25000 new trees and 29000 modified trees. 

This upload was split into 6 seperate changesets. With max size of 10000. The first 3 changesets went fine. The fourth changeset did no go as well. After it was completely filled up JOSM somehow refused to close it and did move on to the next one. 

To work around this I had to:
1. Cancel the upload,
2. Manually let JOSM close the still open changeset,
3. Redownload all data modified by changeset 4. It did not register those changes had happened.
4. Start the upload again.

Finally, repeat the above steps for each changeset left until everything is fully uploaded.

The error happened when creating changesets with only modified nodes.
Both the tags and location were modified. With the only exeption being a handful of nodes for which the location was not modified. 

This happened with version 14824"	defect	new	critical		Core			upload