| commit | 1d8017549154d0bf2c36610d75eee8de9b25ce02 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Thu Apr 02 09:24:51 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Thu Apr 02 09:24:51 2020 +0200 |
| tree | 854997e22377a1a3b2b2ef00fa9efe8fc2651228 | |
| parent | 25b82a85dceb8f3ce847d712fa58809d87f316fb [diff] |
Introduce fsquota package This introduces a new fsquota package and a few low-level support packages to simplify the management of filesystem quotas. To expose an API that's nice to use while staying performant and safe the new fsinfo syscall is being used. Since that syscall is not yet in mainline it has been backported to our 5.6 kernel. Test Plan: Manually validated on our kernel, automated tests are pending some Bazel work to be able to run them inside our own kernel. X-Origin-Diff: phab/D462 GitOrigin-RevId: bb463056589d2b13b7cf32d48ab0b884e70b1bad
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)
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.