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

Trace into Task.async & similar spawned processes #38

Open
cschneid opened this issue Aug 17, 2017 · 0 comments
Open

Trace into Task.async & similar spawned processes #38

cschneid opened this issue Aug 17, 2017 · 0 comments

Comments

@cschneid
Copy link
Contributor

This has come up a few times, most recently trying to trace Absinthe (graphql) using Tasks.

Things to think about:

  • UI to represent parallel vs. serial work?
  • What to do about tasks that outlive the caller? (fire & forget)
  • Tasks that are killed / stopped / crash?
  • Processes spawned manually (not via Task.async apis)
  • Background work done in GenServers (async & sync)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cschneid