This removes all locally ran shell scripts, which should hopefully
enable the Tiltfile to run without changes on Windows.
We lose the invariant of clearing the output directories, which
seems like a reasonable sacrifice for banishing bash.
Change-Id: I756928a25cada1b613ed9fda145809a414a46466
The Go dependency is still required to build the pack binary.
Use "tilt docker" to use Minikube's Docker instance, if available,
removing the local Docker dependency for Minikube users.
The Makefile continues to not require Docker and runs buf locally.
Remove broken Powershell scripts (can't test on Windows). These scripts
should now be substantially easier to write.
Change-Id: Ie80bf68e0e468a747861bea36fa5b353d9de110d
Passing the strict lint checks requires a number of backwards-
incompatible changes:
- Rename the NodePrivileged service to NodePrivilegedService.
This is only used in CLI tooling, which are upgraded at the same
time as the server binary.
- The Publicrpc service was renamed to PublicRPCService.
- The EmitterChain type is renamed to ChainID.
- The default value for the ChainID type is renamed to
CHAIN_ID_UNSPECIFIED. This value wasn't referenced anywhere.
- The response and request types for GetLastHeartbeats were updated
to match the rpc method name.
Change-Id: I3954130d3b25ab1f859390407bba3d3c02ffe03c
- Explorer page fetch data from hosted Cloud Functions.
- Network page use GetLastHeartbeats rather than gRPC stream.
Change-Id: I57dce2ee0b84c4b31fcf7308855668a139ffe20e
- Add development BigTable instance
- Devnet Guardians save to local bigtable automatically
- Cloud Functions run in devnet containers
Change-Id: I9fa32a06b24218cf5c9c01cdff6f37c67e8d1e7c
- Use "npm ci" instead of "npm install" in a couple of places.
- Migrate generate-wasm.sh to a Dockerfile so it can be cached.
- Disable namespace creation and explorer build in CI.
Change-Id: I2e6ee806438863ca81ada701e14684f9f4cc0a76
This is checked when we do CPI calls and did not work since derive is using ctx.this as context address
Change-Id: Ie8fefedb40c3c5eb4966bb0b85f207a40e0fe3be
As discussed with Justin, we no longer need this endpoint.
Removing it means we no longer have to worry about
long-lived connections.
Change-Id: I75020652d383a6b5f79a3cad1b52ae87d323f012
Rather than waiting 15s for the timer to tick, request the
guardian set immediately at startup.
This has the added advantage of being able to crash the
runnable if the guardian set can't be fetched initially.
Change-Id: Ib4cb476c05e92ecd06496043d248eb3ca25b8065