Stream: git-wasmtime

Topic: wasmtime / Issue #1380 ANSI escape sequences to display c...

Wasmtime GitHub notifications bot (Mar 22 2020 at 07:42):

samrat opened Issue #1380:

Thanks for opening a bug report! Please answer the questions below
if they're relevant and delete this text before submitting.

• What are the steps to reproduce the issue?

  1. Clone https://github.com/samrat/wasmtime-colored-output
  2. Build the wasm file: cargo build --target wasm32-wasi
  3. Run the file with wasmtime: wasmtime target/wasm32-wasi/debug/wasmtime-colored-output.wasm

• What do you expect to happen? What does actually happen? Does it panic, and
  if so, with which assertion?
  I expected to see colored output, the ASCII escape codes are displayed instead.

• Which Wasmtime version / commit hash / branch are you using?
  c202a8eea

• If relevant, can you include some extra information about your environment?
  (Rust version, operating system, architecture...)
  ```
  rustc 1.43.0-nightly (564758c4c 2020-03-08)

  uname -r
  5.5.9-arch1-2
  ```

Wasmtime GitHub notifications bot (Mar 22 2020 at 07:42):

samrat labeled Issue #1380:

Thanks for opening a bug report! Please answer the questions below
if they're relevant and delete this text before submitting.

• What are the steps to reproduce the issue?

  1. Clone https://github.com/samrat/wasmtime-colored-output
  2. Build the wasm file: cargo build --target wasm32-wasi
  3. Run the file with wasmtime: wasmtime target/wasm32-wasi/debug/wasmtime-colored-output.wasm

• What do you expect to happen? What does actually happen? Does it panic, and
  if so, with which assertion?
  I expected to see colored output, the ASCII escape codes are displayed instead.

• Which Wasmtime version / commit hash / branch are you using?
  c202a8eea

• If relevant, can you include some extra information about your environment?
  (Rust version, operating system, architecture...)
  ```
  rustc 1.43.0-nightly (564758c4c 2020-03-08)

  uname -r
  5.5.9-arch1-2
  ```

Wasmtime GitHub notifications bot (Mar 22 2020 at 07:46):

samrat edited Issue #1380:

I experienced this bug when trying to run the [QuickJS wasm] file. I have created a repo to reproduce the issue.

• What are the steps to reproduce the issue?

  1. Clone https://github.com/samrat/wasmtime-colored-output
  2. Build the wasm file: cargo build --target wasm32-wasi
  3. Run the file with wasmtime: wasmtime target/wasm32-wasi/debug/wasmtime-colored-output.wasm

• What do you expect to happen? What does actually happen? Does it panic, and
  if so, with which assertion?
  I expected to see colored output, the ASCII escape codes are displayed instead.

• Which Wasmtime version / commit hash / branch are you using?
  c202a8eea

• If relevant, can you include some extra information about your environment?
  (Rust version, operating system, architecture...)
  ```
  rustc 1.43.0-nightly (564758c4c 2020-03-08)

  uname -r
  5.5.9-arch1-2
  ```

Wasmtime GitHub notifications bot (Mar 22 2020 at 08:07):

samrat commented on Issue #1380:

Looks like this is a deliberate decision and there is a WASI issue discussing this: https://github.com/WebAssembly/WASI/issues/162. I think this can be closed, given this is a known and deliberate limitation.

Wasmtime GitHub notifications bot (Mar 22 2020 at 14:45):

rene-fonseca commented on Issue #1380:

The common color codes should be supported for stdout. But you can try to use stderr instead of stdout to see if it works and isn't due to some other problem. stderr should not be filtering the codes at the moment.

Wasmtime GitHub notifications bot (Mar 23 2020 at 14:04):

samrat commented on Issue #1380:

Thanks @rene-fonseca.

This could be due to some other problem as this behaviour seems to be happening when I change to output to stderr as well.

Wasmtime GitHub notifications bot (Mar 23 2020 at 15:58):

sunfishcode commented on Issue #1380:

Allowing untrusted portable code write directly to a user's terminal is not something any serious system I'm aware of has ever knowingly done before, so we're researching how we can enable this functionality in a way that protects users and provides portability. As a temporary measure, streams which are attatched to ttys, which includes both stdout and stderr, are filtered to neutralize escape sequences and problematic control characters.

Last updated: Nov 22 2024 at 16:03 UTC