Brian Broll

It might be easier to just clear the pipeline data after a successful execution. Essentially, this should find all jobs that are not "Input" nodes then delete all associated data...

This is a bit more involved: - non-*debug* pipelines should probably have their data deleted on completion. There is probably no need for storing intermediate results as users are not...

On a related (but probably shouldn't be part of the same issue) note, it would be worth considering using temporary/scratch storage when supported by the storage adapter (such as "Temporary"...

Closing this since all the listed types are now supported and the documentation is up to date.

This is also related to control flow operations...

This actually raises a bigger question about the current framework for interactive editors/sessions. Currently, the browser connects to the compute instance using DeepForge as a proxy (via the InteractiveCompute router)....

It is also unclear if artifact explorers should behave the same way... It is more likely that they will not be quite as long running though it certainly is possible.

Basically. I was imagining just building it on the deployment machine (not pushing it to dockerhub) though I guess it could be useful to push to dockerhub under a different...

Even with updates, these should probably be treated as releases and should be snapshots in the published form

Yeah, this is probably a good idea. I get spoiled with bleeding edge distros ;) Regardless, the `python3` alias won't cause any issues on these distros either so it is...