-
Notifications
You must be signed in to change notification settings - Fork 42
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
Less verbose log printing on failed batch job #332
Comments
@jdries what do you think? |
Indeed, filtering on even only 'ERROR' logs would make more sense. |
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 1, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 1, 2023
…ror logs are printed after failed batch job
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 1, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 1, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 1, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 2, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 2, 2023
JohanKJSchreurs
added a commit
that referenced
this issue
Feb 6, 2023
merged #374 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
openeo-python-client/openeo/rest/job.py
Lines 226 to 235 in a184da6
This automatic log printing when a batch job failed is currently very verbose (up to debug level).
I have notebooks with failed jobs that have thousands of lines of this log dumping. That's not very practical to work with (e.g. copy-paste it to the support forum)
I guess we should only show warn and error level by default, and show instructions to get more detailed logs
The text was updated successfully, but these errors were encountered: