| commit | df952416e693f5b3180f1e69b6021a589cdc80d9 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon Dec 21 14:59:36 2020 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon Dec 21 14:59:36 2020 +0100 |
| tree | 9ad8fdce45516e723b3ebe1aa49aec8b2d8194e6 | |
| parent | 662b5b3119b0798980b887d1ef9fa1b5632aa7fb [diff] |
Fix nanoswitch logging after logtree refactor The LogTree refactor left nanoswitch without a way to sink its logs as it doesn't have a gRPC endpoint to read them from and logtree doesn't output to any stdout/stderr by default. This adds a simple sink similar to what's currently used the node code. Test Plan: Manually tested X-Origin-Diff: phab/D672 GitOrigin-RevId: 8698f9f920f36adf11fa1ef34a47723514eaa665
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)