Medium Reported by customer from FSH-1332.
This appears to be an issue that is unique to Perforce, see:
In Perforce if a user chooses the wrong LineEnd for the client, it can result in a mix of Unix and Windows line ends in the file.
The Crucible application, on seeing the double line endings is croaking with this error.
The workaround is to fix this issue on this file using a dos2unix command line script. However this can be tedious.
It would be preferred if fisheye could error out with the file name that has the bad line endings and perhaps with a line number rather than the line itself (Reasoning: Code security means that Software Code should not be appearing in a log file... the log file could be insecure if an end user does not secure it properly.)
- is duplicated by
-
FE-828 Error log contains 'Unexpected line' entries that corrupt console
-
- Closed
-