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.

Sign up for GitHub

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

Jump to bottom

dill prints huge stack traces sometimes #6444

Closed
belisarius222 opened this issue Apr 4, 2023 · 0 comments · Fixed by #6452
Closed

dill prints huge stack traces sometimes #6444

belisarius222 opened this issue Apr 4, 2023 · 0 comments · Fixed by #6452
Assignees
@Fang-

Comments

@belisarius222
Copy link
Contributor

It should not ~| wrapped-task at the top of +call, since that can print a tang of a tang and end up with hundreds of thousands of lines of output.
Fang- added a commit that referenced this issue Apr 6, 2023
@Fang-
dill: exclude wrapped-task from most +call traces
e300fa2 
Instead of including wrapped-task as-is in most call traces, we now only
include it in traces for crashing (harden task) calls. For everything
else, we include only the tag of the resulting $task.

Closes #6444.
@Fang- Fang- mentioned this issue Apr 6, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Fang- Fang-

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

dill: exclude wrapped-task from most +call traces urbit/urbit
2 participants
@belisarius222 @Fang-