| commit | 686444ed962d75053832ce59527cf15a552a7fc0 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Dec 21 14:21:14 2020 +0100 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Dec 21 14:21:14 2020 +0100 |
| tree | 6c522bf2b538dafe4e5c345c96a353418ecd0c41 | |
| parent | 553ab2b7a7f96e38ff7e381dcbefc095ed3520df [diff] |
launch-multi2: split up logs from nodes into prefixed lines Currently it's impossible to tell apart logs from each node. In general, we should move this over the the debug logging API instead of relying on qemu stdout, but this will do for now. Test Plan: Shouldn't affect any tests, as we don't actually test multi-node setups. Truth be told, we should. X-Origin-Diff: phab/D670 GitOrigin-RevId: 7b4e170e634096bc40432fbef0844d9924957182
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)