CR/LF changes in DTL files causing load errors (#6301: SAX XML Parser Error)

Question

Question

Colin Brough · May 18, 2023

Is CR/LF changes to DTL files edited/committed to git via VS Code a known issue?

We had an issue with exporting files from one server and importing on another, using XML code exported from Studio: ERROR #6301: SAX XML Parser Error. Turns out that issue was down to CR/LF changes made when transferring the XML from one server to the other.

Now we are getting the same error only with DTL files when (1) creating DTL on Management Portal, then (2) exporting via VS Code ObjectScript extension, (3) committing to git (GitLab, self-hosted instance, if it matters), and then (4) subsequently cloning from git and importing and compiling, again via VS Code ObjectScript extension.

So, our suspicion is that:

somewhere in the tool chain the CR/LF's in these files are being changed, and
DTL's specifically are sensitive to these CR/LF changes in a way that other ObjectScript files are not (it looks like its around the XData segment)

Anyone able to confirm, point to documentation, or suggest a working set of configuration options for this kind of environment?

Product version: Ensemble 2018.1

$ZV: Cache for Windows (x86-64) 2018.1 (Build 184U) Wed Sep 19 2018 09:09:22 EDT

Discussion (2)3

Log in or sign up to continue

score 2 · Answer 1 · 2023-05-18T07:03:30-04:00

As you suggested, git is likely the culprit. It has an option for handling line-endings; see Configuring Git to handle line endings - GitHub Docs.

score 0 · Answer 2 · 2023-05-25T05:13:48-04:00

Turns out it wasn't git's fault - though really helpful for us to clarify what git is doing, and ensure we have a decent set of default .gitattributes set...

We don't fully know what is going on, but ALL DTLs on one Ensemble instance throw this error, on load in Management Portal or compile via Studio or VS Code - can't even create a new DTL. So we are currently suspecting some kind of corruption/error on that server, rather than something related to the code we are bringing from git. But no idea what has gone wrong. Its a dev server - we may just scrub it and reinstall...