-
Notifications
You must be signed in to change notification settings - Fork 1
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
Expand discussion on nesting tasks and limitations #77
Conversation
start discussion on nesting of tasks
- when set to false, does not execute code - useful updating mostly the text of the docs
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #77 +/- ##
==========================================
- Coverage 86.00% 80.86% -5.14%
==========================================
Files 9 9
Lines 686 690 +4
==========================================
- Hits 590 558 -32
- Misses 96 132 +36 ☔ View full report in Codecov by Sentry. |
d5e9a46
to
b1f2537
Compare
@ffevotte I think this is ready for a first review. I found it quite tricky to explain the problem with nested tasks, but I tried 😅 https://maltezfaria.github.io/DataFlowTasks.jl/previews/PR77/troubleshooting/#nested-tasks |
While I was at it, I also added a small suggested workflow section with the experience described in #40 |
Still WIP, but the idea is to explain a bit better the current limitations. In particular, why nesting is somewhat tricky, and what are the current workarounds. Maybe this will also help us decide on a proper way forward, such as the nesting of
TaskGraph
s and merging ofLogInfo
objects.