orca dev install should check if the runtime build is up to date #122

New Issue

bvisness · 2023-09-17T16:42:04Z

bvisness commented

2023-09-17 16:42:04 +00:00

Mysterious problems arise if you run orca dev install without first running orca dev build-runtime. We should track a git hash or something when we build the runtime, and when running dev install, ensure that the hash matches. This should both ensure that the runtime was in fact built, and also catch the relatively common case where you git pull but forget to orca dev build-runtime.

One minor issue with the git hash is that it won't catch any local modifications you make. I think this is a reasonable caveat though in lieu of doing a full file/folder checksum of the source? On the other hand, it's not hard to do a full file/folder checksum of the source...

Mysterious problems arise if you run `orca dev install` without first running `orca dev build-runtime`. We should track a git hash or something when we build the runtime, and when running `dev install`, ensure that the hash matches. This should both ensure that the runtime was in fact built, and also catch the relatively common case where you `git pull` but forget to `orca dev build-runtime`. One minor issue with the git hash is that it won't catch any local modifications you make. I think this is a reasonable caveat though in lieu of doing a full file/folder checksum of the source? On the other hand, it's not hard to do a full file/folder checksum of the source...

bvisness self-assigned this 2023-09-17 16:48:13 +00:00

bvisness referenced a pull request that will close this issue

2023-09-17 17:10:19 +00:00

Check if the runtime is up to date on `dev install` #123

MartinFouilleul closed this issue

2023-09-18 10:05:10 +00:00

Sign in to join this conversation.