Xilin

Hi @imjohnbo, I am sorry we forgot to comment /ok-to-test. If you take a look at this PR(https://github.com/ploomber/ploomber/pull/866) , you will see tests such as Integration tests / Windows-integration-forked (pull_request),...

Yes. I have recreate the scenario: here is the PR (https://github.com/ploomber/ploomber/pull/887) and you will see it fails on all forked integration tests like this: MacOS integration tests / Macos-integration-forked (pull_request)...

Thank you anyway. I have tried multiple ways. But looks like only part of information can be passed on to the original flow! Thanks for the template, it's very useful.

i think its ready

Oh yeah, i thought it was an github error. Fixed it, it should pass now.

``` ./src/ploomber/telemetry.py:6:80: E501 line too long (84 > 79 characters) ``` Wait this is weird, I run flake8 locally and it did not return this error? Also I think that...

@edublancas I think I hit some block on this. This one is issue 648. I was actually continuing another guy's work.

@edublancas I am working on the grid case, but I am not fully understand class meaning, in this test case, the NotebookRunner. What is it? Also some weird behavior happens...

@edublancas [here](https://github.com/ploomber/ploomber/runs/7957287940?check_suite_focus=true#step:10:2057) is the log I am a bit confused between these two definition: [this](https://github.com/ploomber/ploomber/blob/master/src/ploomber/spec/taskspec.py#L428) and [that](https://github.com/ploomber/ploomber/blob/928325795c5f98eb7e11a72d732b94141824a199/src/ploomber/tasks/taskgroup.py#L220) One is to generate a single task and one is to generate a...

Ok so what's left to do here? Are we settle on an option yet?