Problem
Ideally it would be populated with available scarb/foundry versions, allow re-runs and list experiments in progress and theirs status. This would have to be behind some UI with authentication i.e. via github.
It'd be a wrapper for experiment workflow essentially which can be messy at times, and inconvenient.
We could later expose it to compiler team for optimized UX of experiment running (if they wanted to run some weird stuff with a specific compiler rev or something).
inb4 It's a long shot because it's probably not worth it (a lot of work) but it seems like a fun side project to tackle if we had the time.
Proposed Solution
No response
Notes
No response
Problem
Ideally it would be populated with available scarb/foundry versions, allow re-runs and list experiments in progress and theirs status. This would have to be behind some UI with authentication i.e. via github.
It'd be a wrapper for experiment workflow essentially which can be messy at times, and inconvenient.
We could later expose it to compiler team for optimized UX of experiment running (if they wanted to run some weird stuff with a specific compiler rev or something).
inb4 It's a long shot because it's probably not worth it (a lot of work) but it seems like a fun side project to tackle if we had the time.
Proposed Solution
No response
Notes
No response