You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/10/14 07:46:14 UTC

[GitHub] [camel-quarkus] ppalaga opened a new issue #270: TarfileTest can fail on exotic platforms

ppalaga opened a new issue #270: TarfileTest can fail on exotic platforms
URL: https://github.com/apache/camel-quarkus/issues/270
 
 
   This is related to this discussion: https://github.com/apache/camel-quarkus/pull/266#event-2709132842 where I did not have the time to find out all necessary details.
   
   So the problem is that `bos.toString()` in the test is using given platform's default encoding which might be incompatible with the encoding RestAssured uses to post the request. Note that RestAssured uses ISO-8859-1 by default for sending text messages.
   
   This is typically not an issue if both encodings are ascii-compatible, which is mostly the case in the western world. 
   
   But if the given system has its default encoding set to some encoding not compatible to ascii such as IBM1026 or UTF-16, the test will fail. It can be simulated passing the encoding to the test via `-Dfile.encoding`:
   
   ```
   mvn clean test -DargLine="-Dfile.encoding=IBM1026"
   ```
   
   Note that with `UTF-16`, the simulation does not work well, because maven expects the `env` command output to be encoded using that encoding, which is not the case when simulating, so there is some NPE thrown out of the Maven code.
   
   So once again, it is expected that `mvn clean test -DargLine="-Dfile.encoding=IBM1026"` passes.
   Actual behavior is that it fails.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services