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: ivansanchez[at]escomposlinux.org [Submitted to the original trac issue database at 11.05pm, Saturday, 7th February 2009]
I'm using the rails port rev 13578 (2009-02-08) and a custom script intended for bulk uploads.
It seems that the changeset controller is not able to correctly handle newlines and whitespace in the XML.
How to reproduce: make a script open a changeset and upload a chunk of XML using POST /api/0.6/changeset/#id/upload, but with no whitespace between XML elements (e.g. use "tidy"). Half of the elements being uploaded will get lost:
Some of my test cases follow. With whitespace between the nodes, the upload will go OK:
Author: Matt [Added to the original trac issue at 8.35am, Sunday, 8th February 2009]
Fixed, I think, in r13579. Looks like the diff reader was skipping elements when it shouldn't have been. I've added a test case similar to yours to the standard test suite.
Reporter: ivansanchez[at]escomposlinux.org
[Submitted to the original trac issue database at 11.05pm, Saturday, 7th February 2009]
I'm using the rails port rev 13578 (2009-02-08) and a custom script intended for bulk uploads.
It seems that the changeset controller is not able to correctly handle newlines and whitespace in the XML.
How to reproduce: make a script open a changeset and upload a chunk of XML using POST /api/0.6/changeset/#id/upload, but with no whitespace between XML elements (e.g. use "tidy"). Half of the elements being uploaded will get lost:
Some of my test cases follow. With whitespace between the nodes, the upload will go OK:
With no whitespace before the first , it will get lost:
With no whitespace at all, half of the nodes will get lost:
If there is whitespace between and , then the odd nodes will get uploaded and the even ones will get lost...
Also, sending a will raise an error:
Exactly the same error is triggered when the node has tags, with or without whitespace:
I'm not proficient in Ruby, so I cannot track down the bug.
The text was updated successfully, but these errors were encountered: