| commit | b9431c95082a3de6c87f96b700e69b72e4d87fdc | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Aug 24 18:16:51 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Aug 24 18:16:51 2020 +0200 |
| tree | 2caae783a1f940e8d9c3ff4bf23ef150b537c225 | |
| parent | ca24cfaef52b388438f06e69352643a4ee0185ca [diff] |
supervisor: never give up This fixes T756, in which supervised processes would reach a negative backoff value. This seems to be caused by the backoff library's ExponentialBackoff having a default MaxElapsedTime of 15 minutes, after which it returns 'Stop', or, -1 seconds. Test Plan: There's no easy way to test this. Unfortunately, the behaviour to return Stop is not after a number of calls, but after time has elapsed. We don't want to wait 15 minutes for a test, and we don't have an easy way to mock time, either. But I did test this manually and I cannot observe the 'negative backoffs' after 15 minutes anymore. Bug: T756 X-Origin-Diff: phab/D619 GitOrigin-RevId: 49d8617bcf2c8b36127cb43acde8afb7cc35c99f
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.