| commit | d868d69320140863a1938bfa042ad0824cfa9500 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Sun Nov 17 17:28:29 2019 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Sun Nov 17 17:28:29 2019 +0100 |
| tree | fd519288299185f48eec666a19b061b1444c9f78 | |
| parent | 45333b68dd60942adc61a29f50b2c72420b792e3 [diff] |
Add go-sqlite3 dependency to go.mod Fixes this "go mod tidy" error on master: ``` git.monogon.dev/source/nexantic.git imports github.com/rubenv/sql-migrate/sql-migrate imports github.com/mattn/go-sqlite3: module github.com/mattn/go-sqlite3@latest found (v2.0.0+incompatible), but does not contain package github.com/mattn/go-sqlite3 ``` The fix was to run `go mod tidy` using Go 1.12, since Go 1.13 got confused about the sqlite3 package (there is no v2.0.0 - I suspect an issue with the proxy). Notably, neither sql-migrate nor go-sqlite3 use Go modules, and there's no way to get rid of the dependency: https://github.com/rubenv/sql-migrate/blob/aff46b65bb7f71e015dc28dc2edd083737985dfb/sql-migrate/config.go#L17 Adds a `go mod tidy` invocation to gazelle.sh. Test Plan: Ran gazelle.sh. X-Origin-Diff: phab/D268 GitOrigin-RevId: 843710797dc2bccc2c7efdc249ac2b28a23c3fae
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora 30 or 31 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.