Skip to content
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

[BugFix] Make the error message truncated not so aggressive #2876

Merged

Conversation

acezen
Copy link
Collaborator

@acezen acezen commented Jun 13, 2023

What do these changes do?

code shows that when error message is too large, truncated to 30 chars. BUT A snippet of 30 chars is usually not enough to tell something useful. This change enlarge the 30 to 1024 to show more log.

Related issue number

Fixes #2864

Signed-off-by: acezen <qiaozi.zwb@alibaba-inc.com>
@@ -111,7 +111,7 @@ def _generate_runstep_request(session_id, dag_def, dag_bodies):
# TODO: make the stacktrace separated from normal error messages
# Too verbose.
if len(e.details()) > 3072: # 3k bytes
msg = f"{e.details()[:30]} ... [truncated]"
msg = f"{e.details()[:1014]} ... [truncated]"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1014 is too long. 80 or 256 would be better.

@sighingnow sighingnow merged commit c489c63 into alibaba:main Jun 13, 2023
14 checks passed
@sighingnow sighingnow deleted the 2864-enlarge-error-message-output-size branch June 13, 2023 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] GAE error message is truncated tooooo aggressively
2 participants