Eduardo Blancas

are you logging the actual values? things like y_pred and y_true should not be logged for a few reasons. They might contain sensitive data, but because they might be large...

yeah: ```sh ploomber examples -n templates/ml-basic -o ml cd ml ``` then modify the `pipeline.yaml` and add really long names. example: ```yaml - source: tasks.get product: '{{folder}}/get.parquet' name: this-is-a-really-long-name ```

yeah your modifications should appear whenever you run `ploomber plot`. if you don't, it's likely that you don't have ploomber installed in editable mode: ``` pip uninstall ploomber # move...

thanks for your feedback! I think we want the hook to work independently of its location so we'll work on it to fix it

Sure, so the changes need to go in `dagspec.py` and `taskspec.py`, the former deals with the `pipeline.yaml` spec, while the latter with each entry in the `tasks` section. Now that...

> @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? We represent each task...

sure!

any updates? @imskr

Yeah, this makes sense. the filenames should be predictable, I'm deciding between two solutions: 1. explicit config, something like: ```yaml tasks: - source: random-forest.py name: random-forest- product: 'n_estimators=[[n_estimators]]/criterion=[[criterion]].html' grid_number_suffix: false...

Ah, great catch! Yeah, for the second scenario I meant removing the grid_number_suffix, but I like your approach of having that option as well and showing it as part of...