Open thomasjpfan opened 11 months ago
🤖
Hi @thomasjpfan,
I'm Dosu, an AI here to assist with Flyte. I can help you troubleshoot issues, answer questions, and guide you on your journey as a contributor while we wait for a human maintainer. I'm here to make your experience with Flyte as smooth as possible. Let's dive into your issue!
Thank you for bringing this to our attention. The width of the traceback display is typically controlled by the Python interpreter itself and not influenced by external libraries or settings within Flytekit. The code provided does not show any manipulation of traceback display settings.
However, it's worth noting that the terminal or console you're using might have settings that control the width of the output. You might want to check the settings of your terminal to see if there's a way to utilize the full width of the screen.
If you have any additional information about your environment (like the terminal or console you're using, your operating system, etc.), it could help us understand the issue better.
@thomasjpfan does dosubot
's answer makes any sense to you? Please add a thumbs up/down to the bot's response so it uses the feedback to keep learning
No, the bot's answer is not useful. We are using rich
to control the width, which is under flytekit's control. The reason why the trackback is narrow is because there are several columns, where the first column is used for datetime info.
Describe the issue
Tracebacks do not use the full width of the terminal screen. For example, with the following script:
And running:
pyflyte run raise_error.py an_error
results this UI:There is a lot of unused space for the trackback, which means we need to scroll up more to get to get to the location of the error.
What if we do not do this?
One needs to scroll up more to get to the informative traceback.
Related component(s)
flytekit
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?