What's the best way to go about debugging why Pants is behaving as if both

colors

and

dynamic_ui

are off? It happened to me randomly the other day on 2.11.0rc2 but sorted itself out after a while for unknown reasons, and today it happened to a co-worker on 2.11.0 as well.

I think I'd recommend explicitly setting them and see if it still turns off. It might be that our default of seeing if you're a TTY isn't working for some reason sometimes

Explicitly setting

colors

and

dynamic_ui

did the trick, and after removing them they stay enabled weirdly enough. He did also kill pantsd though, not sure if pantsd handles stuff like that too. Now the only problem that remains is that pytest in similar sudden fashion refuses to output what was printed to stdout on failing tests..

Now the only problem that remains is that pytest in similar sudden fashion refuses to output what was printed to stdout on failing tests..

Hmmmmm you're using modern pants right? I can't remember which version but we did used to have an egregious issue that sometimes output would be missing. Pretty sure that is fixed now

2.11.0, yep 🙂

Oddly I thought I saw this too

Huh, that would be concerning and high priority bug. Is it flaky or consistent?

I didn't have enough runtime to say. My suspicion should be easy to validate

Turns out the pytest stuff was a human error. The TTY issue is still weird though..

there are definitely issues around logging levels not triggering

pantsd

restarts… but color and dynamic-ui-ness should definitely be per-client session, and not dependent on the server

I'm running into this on

main

in the Pants repo right now 😮