| commit | 56ae577a9f31df1a903dab7b72cf3f2ac518e5de | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Wed Jul 08 18:04:48 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Wed Jul 08 18:04:48 2020 +0200 |
| tree | 489af3cbef37b1292cbc6927a676feebabe6e6e7 | |
| parent | ac9947fd23ad4dab909a9282ac56fd51dcecb4e4 [diff] |
Increase E2E gRPC connection reliability The E2E test suite sometimes fails because of weird interaction between gRPC and SLIRP where gRPC has an open connection with SLIRP, but SLIRP hanged while connecting to the actual service. In that case gRPC hangs waiting for the server handshake which will never come as the upstream connection is never properly established. This forcibly terminates each gRPC call after 5s to make sure that multiple calls are attempted and it doesn't hang. Test Plan: Hard to test, I observe less of these errors X-Origin-Diff: phab/D583 GitOrigin-RevId: cc1336aab7f4d13412bdb2e93be027d7e3eb57fc
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.