id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23738	Mass upload: JOSM tries to upload changes even though changeset is already closed	mmd	GerdP	"When trying to upload 100.000 changes with package size 10.000, JOSM tries to upload changes to an already closed changeset. A typical sequence of events would be as follows:

Step 1: Create changeset 1
Step 2: Upload 10k changes to changeset 1 -> HTTP 200
Step 3: Upload 10k changes to changeset 1 -> HTTP 409 (Changeset already closed)
Step 4: Close changeset 1
Step 5: Create changeset 2
Step 6: Upload 10k changes to changeset 2 -> HTTP 200
... etc.

Step 3 fails, because we've already uploaded 10k changes in step 2, and a changeset can only contain a maximum number of 10k changes, according to /api/capabilities.

It would be good if JOSM could somehow skip Step 3 above, since it's clear that the API will reject the request in any case."	enhancement	reopened	normal		Core