| commit | 39f2f691726dc6e0a291aa8609085b835a313dad | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon Dec 21 14:51:42 2020 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon Dec 21 14:51:42 2020 +0100 |
| tree | 23d34844fa68be991d514bf8bd89bc5042779091 | |
| parent | 686444ed962d75053832ce59527cf15a552a7fc0 [diff] |
Make LaunchCluster not close DebugClient it's returning LaunchCluster currently closes the gRPC connection underpinning the DebugService it's returning. This causes all further calls to that service to immediately return with a CANCELED error. There's no reason why it should do this (probably a refactoring artifact), so just remove the Close call. Fixes T881. Test Plan: CTS is not run as part of automated test still because it takes too long. Bug: T881 X-Origin-Diff: phab/D671 GitOrigin-RevId: 6bfa382cba6a15b146b2f24311507456b58cdf98
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //metropolis/cli/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)