| commit | 832bc77f0f0530059dd66b59cfd8a000b59b6251 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Thu Apr 07 12:33:01 2022 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Tue Apr 19 08:06:03 2022 +0000 |
| tree | c063cc6398e410496844622ed9e2688f1e5c8116 | |
| parent | abe02eb86b64920be8aec862e380853be1fd3372 [diff] |
m/p/event/etcd: handle spurious watch updates With the recent etcd updates, we started seeing some failures in tests for the etcd-backed Event Value library. This seems to be due to etcd now sometimes returning 'spurious' watch updates, in which a keyvalue is returned twice, with two separate revision numbers, even though the underlying value has not been updated. We elect to deduplicate these within the event value library itself, if only to make it less work for downstream users to do the same. This is done be keeping a cross-watcher.Get map of key->values, and filtering out updates which effectively do not update the data underneath. We had one test relying on 1:1 correspondance between etcd puts and Event Value backlogged Gets. However, the rest of our codebase does not make this assumption, and it seems fair that this assumption doesn't make sense alongside the intended use of the Event Value system in which we deliberately and arbitrarily drop intermediate updates within a single Get call. Change-Id: I731a15b2d15ab6807bb95cb6c777c176dde22f0b Reviewed-on: https://review.monogon.dev/c/monogon/+/654 Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
Our build environment requires a working Podman binary (your distribution should have one).
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)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. 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. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
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.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...