I have my Ruby-based server-side commit hooks working but now I'm seeing a failure result I can't figure out yet.
I have a large sample data set that I'm using for testing (https://hub.docker.com/r/ditacommunity/demo-content/). This content is non-trivial DITA and all the files are valid (e.g., Oxygen validates the maps and topics).
However, when I load the files via my Ruby script that uses the BaseXClient.rb file, a few of the files fail to load with the error indicating that something in the BaseX client/server chain is trying to interpret the XML data as a file path. As far as I can tell it's the same documents every time, so I suspect there is something about the documents' details that is causing this.
I guess my question is: what could cause this behavior and how might I go about debugging and correcting it?
The Ruby script is here: https://github.com/dita-for-small-teams/dfst-git-commit-hooks/blob/develop/ server-side/post-receive
I probably have to rewrite the script to use the REST API so that I have more control over the encoding details (per earlier discussion of how to handle UTF-16 documents) but I'd still like to what's causing this as it points up to either a really subtle user error or a flaw in the basic API mechanism.
Cheers,
Eliot
---- Eliot Kimber, Owner Contrext, LLC http://contrext.com