aravindgee
aravindgee
Reviewed the status quo with Ludo, working on "Must" items first.
**Optimize build time** - @lgalabru Clarinet build time is already optimized through the use of a [matrix](https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs) ([example](https://github.com/hirosystems/clarinet/actions/runs/3394594400)). Current total build time is close to 1hr, is this acceptable? If...
@hugocaillard Yes it's feasible! If you're referring to PR #654, I've updated the logic to trigger the build only when the clarity-vscode subdirectory is updated.
**todo**: Optimize build time for clarinet packages - investigate additional paths for improving build time - eg. parallelize by platform (h/t @lgalabru ) and docker image generation.
Reviewed build time bottleneck with Ludo - since its not a major concern, we agreed to deprioritize this for the time being. Additional concerns brought up by Hugo - >...
Working on a new PR to trigger rebuild of VSCode whenever there's a new clarinet release.
Hi @lgalabru, @hugocaillard - seeing a lot of failures in the Github actions on Clarinet - with this concern, marked it as blocked to flag it to the team. However...
Superceded by #1078 .