| commit | 5ade732e7778b774caf03c850fbfaa7b67132d9b | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Thu Aug 27 13:27:51 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Thu Aug 27 13:27:51 2020 +0200 |
| tree | ad467196bf11717d4193f45c346112ffe97c375b | |
| parent | a50e845df333a4d7531793e3fed61ca8411384f5 [diff] |
logtree: implement LeveledLogger interface
This implementes the equivalent of StructuredLogger from go/logtree as
a pure interface for further implementation by LogTree (or other logging
mechanism, eg. in tests).
StructuredLogger was a slightly poor name (because of the unfortunate
industry understanding of what structured logging is), so we go ahead
and rename that. Once this change goes through, the design document will
be reflected to rename 'Structured Logging' to 'Leveled Logging'.
We base the API off of github.com/golang/glog, but without a single
global instance. Other API differences include:
- No {Info,Warning,Error,Fatal}ln calls, as these are pretty much
equivalent to {Info,Warning,Error,Fatal} calls.
- V(n) now returns an interface with .Enabled(), instead of a boolean
value. This is necessary as the returned value will have to carry
its corresponding LeveledLogger instead of calling global functions.
Test Plan: plain interface, untested
X-Origin-Diff: phab/D620
GitOrigin-RevId: 06c7e3a88751ff7503e8106fac2360cf8de621c4
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 //core/cmd/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.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official 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.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.