Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output with long lines and multi-byte characters displayed incorrectly #1008

Closed
eriwen opened this issue Dec 13, 2016 · 2 comments
Closed

Output with long lines and multi-byte characters displayed incorrectly #1008

eriwen opened this issue Dec 13, 2016 · 2 comments

Comments

@eriwen
Copy link
Contributor

eriwen commented Dec 13, 2016

This is migrated from GRADLE-3329, which had an attempted fix in Gradle 3.2.1.

Expected Behavior

Output should not be garbled by Gradle regardless of line length or character encoding.

Current Behavior

This build demonstrates unexpected characters in the output where multi-byte characters are.

Context

Those relying on multi-byte characters for output will be affected. I expect this affects international users more significantly.

Original forum post
Another forum post

Steps to Reproduce (for bugs)

Define and run the following task on a dumb terminal:

task demonstrateBug() {
  def text = "" + ("" * 10) + (" a b c d e f " * 2) + ("" * 10) + ""
  1000.times {println text + text}
}

Your Environment

This might behave differently depending on the OS and console.

sormuras added a commit to sormuras/beethoven that referenced this issue Dec 13, 2016
sormuras added a commit to sormuras/beethoven that referenced this issue Dec 13, 2016
@sormuras
Copy link

sormuras commented Dec 13, 2016

@eriwen It seems to be a Travis console/logging only problem. When I moved the test task into a plain shell script, like:

#!/bin/bash

for run in {1..1000}
do
  echo " ▓ ✔✔✔✔✔✔✔✔✔✔ a b c d e f  a b c d e f ✔✔✔✔✔✔✔✔✔✔ ▒ "
done

it too showed a lot of � characters in the output: https://api.travis-ci.org/jobs/183558479/log.txt?deansi=true
Will file an issue against Travis.

@eriwen
Copy link
Contributor Author

eriwen commented Dec 13, 2016

Nice @sormuras! That was step one on my list for triaging this, but you kindly did that for us. Thank you again. I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants