-
Notifications
You must be signed in to change notification settings - Fork 914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rich output is too long #1750
Comments
Thanks for raising this @deepyaman. I have also found the rich tracebacks too verbose and was kind of waiting to see if anyone had the same opinion independently. @SajidAlamQB I think the right solution here would be:
We could make rich an optional dependency, but I would prefer that we keep it, change any settings so that the default behaviour is better for kedro users and make it more easily configurable for users who want to change those settings or disable it altogether. |
For reference, here's what the same traceback would look like now we've turned And with Personally I think a non-zero |
From @deepyaman:
I'm going to close the issue for now, but others should feel free to re-open it if and when they think we should tinker with these settings further. |
Description
I'm always frustrated when my traceback is 838 lines long for a trivial issue.
Context
How has this bug affected you? What were you trying to accomplish?
Possible Implementation
Make Rich an optional dependency (not just on certain platforms like Databricks).
Steps to Reproduce
pip install kedro==0.18.2
kedro new --starter spaceflights
and accept defaultscompanies["iata_approved"] = _is_true(companies["iata_approved"])
tocompanies["iata_approved"] = _is_true(companies["iata_approve"])
(removed a "d").kedro run
Expected Result
Tell us what should happen.
0.18.1 (not Rich) traceback is 57 lines long:
Actual Result
Tell us what happens instead.
0.18.2 (Rich) traceback is 838 lines long:
https://pastebin.com/raw/efg3bhD1 (I'd paste it here, but GitHub errors out saying body is too long/exceeds 65536 characters 🤦).
Your Environment
Include as many relevant details about the environment in which you experienced the bug:
pip show kedro
orkedro -V
): 0.18.2 (vs 0.18.1)python -V
): 3.10.5The text was updated successfully, but these errors were encountered: