Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pdb unusable due to invisible stdout

See original GitHub issue

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Ray installed from (source or binary): source
Ray version: 0.6.3@3a66d47a3a4b3fc31f82eb26fdff2ea282f85e1b
Python version: 3.6
Exact command to reproduce:
1. Set ipdb trace (import ipdb; ipdb.set_trace()) somewhere in the tune logging example, for example here: https://github.com/ray-project/ray/blob/aad48ee5a50e3afa13239fbed895e58f0b21811f/python/ray/tune/examples/logging_example.py#L39
2. Run the logging example, e.g. python ${RAY_PATH}/python/ray/tune/examples/logging_example.py

Describe the problem

In the latest master, stdout somehow gets handled incorrectly, thus making pdb unusable. This happens at least for trainables run with tune.run_experiments. Things work fine before https://github.com/ray-project/ray/commit/ef527f84abf0cee7ac6ad832828ff92311440ee4.

Issue Analytics

State:
Created 5 years ago
Comments:17 (10 by maintainers)

Top GitHub Comments

3reactions

richardliawcommented, Feb 28, 2019

Can we actually make this issue a high priority?

In a separate project I’m working on, it’s incredibly hard to debug things now… (this is not specific to Tune)

1reaction

robertnishiharacommented, Feb 12, 2019

That’s true, if Tune supported local_mode=True, then it would just work out of the box. The relevant issue is https://github.com/ray-project/ray/issues/2796.