This message was deleted.

the logs that are piling up are from a notebook that's part of your pipeline.yaml or from a notebook you're using to execute

poomber build?

notebook part of pipeline, just one

thanks!

ok, revised the notebook is pretty big (more than 1000 lines). but the steps to reproduce the issue are: 1. configure a

pipeline.yaml

just with one simple notebook output (one cell printing or plotting something will suffice). No log parameter. 2. call

ploomber build

with no log option, just execute the notebook and plot. 3. If you open the notebook you will see the plot rendered in the cell. 4. Now add log option to yaml. Add logger call with custom message inside the cell (

plot rendered

or some simple message) and execute ploomber with logging to file (INFO is ok) 5. as expected, log is printed to file and shown in cell 6. Remove all to get back to the very same state as step 2 (except the custom log as you need to check messages sometimes output file) 7. Open the notebook and you will see all logging output as in step 5. 8. if you want to restore the previous behaviour with no log you MUST remove the custom log call to file from the cell. Otherwise you will end with a cluttered cell.

followed up on github!