Turbo 2.0: CircleCi exception

[samuelcole]

Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

---

What package manager are you using / does the bug impact?

Yarn v2/v3/v4 (node_modules linker only)

What operating system are you using?

Mac

Which canary version will you have in your reproduction?

turbo@npm:2.0.1

Describe the Bug

CircleCI will throw an exception in testing:

Oops! Turbo has crashed.

A report has been written to /tmp/report-031b50a3-6078-440d-b30e-ae1ab99c594c.toml

Please open an issue at https://github.com/vercel/turbo/issues/new/choose and include this file
Oops! Turbo has crashed.

A report has been written to /tmp/report-d7c3945b-76b5-4f9d-a3e3-bfe18a78ad37.toml

Please open an issue at https://github.com/vercel/turbo/issues/new/choose and include this file

Exited with code exit status 101

name = "turbo"
operating_system = "Ubuntu 22.04 (jammy) [64-bit]"
crate_version = "2.0.1"
explanation = """
file 'crates/turborepo-vt100/src/screen.rs' at line 878
"""
cause = "called `Option::unwrap()` on a `None` value"
method = "Panic"
backtrace = """

   0:   0x407e88 - <unresolved>
   1:  0x13273fe - <unresolved>
   2:  0x1306f99 - <unresolved>
   3:   0xefc176 - <unresolved>
   4:   0x9c7dc0 - <unresolved>
   5:   0x9c5cfd - <unresolved>
   6:   0x98e4db - <unresolved>"""

Expected Behavior

It succeeds

To Reproduce

Run CI

Additional context

No response

[samuelcole]

It seems to run from an interactive session fine: I SSH'd into the CircleCi box and ran yarn lint and everything seemed great.

[chris-olszewski]

This is odd, I need to do some testing to figure out what state the CircleCI box terminal is in for non-interactive sessions. It looks like there's a TTY setup even though it isn't a true terminal.

In the meantime you can add the env var TURBO_UI=false to disable the UI in CI and that should avoid the panic.

[chris-olszewski]

It seems this is a known bug/feature of CircleCI that they have a TTY session open e.g..

The turbo TUI output will not be helpful if not viewed in an actual terminal so I would suggest opting out of it so logs are useful. This is best done via the TURBO_UI=false environment flag, but can also be achieved by manually making turbo's stdout non-TTY: turbo lint | cat && test ${PIPESTATUS} -eq 0.

Keeping open as we shouldn't panic in this situation.

[samuelcole]

this workaround worked for me!

i just added it to my .circleci/config.yml step:

- run:
    name: Run TURBO lint
    command: yarn lint
    environment:
      TURBO_UI: "false"

[anthonyshew]

We've now documented this workaround for the time being: https://turbo.build/repo/docs/guides/ci-vendors/circleci

[aholland]

Here is my report-<uuid>.toml file as requested at https://discord.com/channels/818588653005176832/1247857006333923360

circleci@7e33ff8c3102:/tmp$ cat /tmp/report-d8f38136-02f3-4045-b8e0-61ca6cb0ade4.toml
name = "turbo"
operating_system = "Ubuntu 22.04 (jammy) [64-bit]"
crate_version = "2.0.1"
explanation = """
file 'crates/turborepo-vt100/src/screen.rs' at line 878
"""
cause = "called `Option::unwrap()` on a `None` value"
method = "Panic"
backtrace = """

   0:   0x407e88 - <unresolved>
   1:  0x13273fe - <unresolved>
   2:  0x1306f99 - <unresolved>
   3:   0xefc176 - <unresolved>
   4:   0x9c7dc0 - <unresolved>
   5:   0x9c5cfd - <unresolved>
   6:   0x98e4db - <unresolved>"""

[mpereira]

This also happens in terminals like Emacs eshell.

[chris-olszewski]

I believe this has been fixed with #8457 which was released as part of 2.0.4. If you encounter this with 2.0.4+ please reopen along with your terminal emulator and any other relevant information.