Proto commits in warp-build/warp

These 55 commits are when the Protocol Buffers files have changed:

2023-04-17

feat(tricorders/rust): generate binary and library signatures (#64) + move to nightly + use our own cargo manifest representation (cargo_toml is insuficient, cargo's own repr is not thread safe) + add tests for generating cargo toml signatures + better tree walking using ripgrep's ignore crate + fixed a bunch of tests + introduce `subpath` to dependency requirement + add better logger support using the `WARP_TRICORDER_LOG` env var + add e2e test for booting + update all deps + add anyhow test repository + add external crate support for rust libraries + add signature configuration to transitive dependencies

The documentation is generated from this commit.

2023-03-30

feat(schemas): send Goal when generating subtrees

2023-03-29

feat(core): support saving multiple signatures in code database Since a single Task now can be turned into several signatures, this changeset supports saving multiple signatures into the Code database, and rehydrating them when reading them out. Also, because tree-splitting should return several ASTs (one for each one of the subtrees that match the test matcher), we now support storing them individually as well.

2023-03-28

fix: remove unused rule tests

Add 'rules/' from commit 'b48f99f7e2e9aeeb67aad904380a681a919d5da6' git-subtree-dir: rules git-subtree-mainline: 3d8e2bac62af08db2a3467cecca55e3f63fb86de git-subtree-split: b48f99f7e2e9aeeb67aad904380a681a919d5da6

feat(core): restore AST splitting

feat(schemas): remove symbol, add test_matcher to get_ast

2023-03-27

feat(core): support multiple signatures This changeset allows us to handle multiple signatures coming from the resolution phase, including maintaining references as a task gets replaced by another due to the signature split. For this to work, the unit of work has to go from a single Target, to a compound key including the Target _and_ the Signature that is being built. Tasks were the clearest place where we could add the signature information to make all tasks in the queue and in the results unique. Since signatures are rather heavy objects, we introduce the SignatureRegistry to keep track of our signatures while issuing lightweight copyable handlers (SignatureIds). Because some Tasks get replaced by others when they are split into several new tasks due to the signature resolution, we needed also to be able to _replace_ what a Task was, without needing to replace all of the references to that task. For that we introduced the TaskId handler, that is issued by the TaskRegistry, which keeps track of all the tasks in place. And lastly, to avoid anyone being able to build a Task that will go unaccounted for or that will not be possible to _update_ through the TaskRegistry, we introduced the UnregisteredTask struct. This struct is used to capture the intent of creating a task, without actually creating one. Other than this, all the code has been updated to work with the `Task` struct instead of receiving individual Goal, TargetId, and SignatureId information. fix(core): rule expander double-root append The Rule Expander now makes sure that it does not add the root of a Signature to the paths contained in the Rule Config IF the paths already have that root as a prefix. Example: * root=./a/b path=./a/b/file => ./a/b/file * root=./a/b path=./file => ./a/b/file feat(core): send goal to tricorders In order to avoid filtering sigantures in the core, we will send the current Goal to tricorders to let them figure out what are the necessary signatures.

2023-03-24

feat(core): send TestMatcher to tricorders

2023-03-16

feat(schemas): new fields for better dep resolution We extend the UrlRequirement message to include a subpath. This can be used to specify what subpath of a specific url is relevant as a requirement. For example, if the URL is a Git repository, this can help us do subtree clones. If the URL is a tarball, this is used to narrow in the uncompressed output, etc. The Dependency message now includes a list of all the outputs that Dependency has generated. This makes it easier to write rules that rely on paths for includes. The PrepareDependency RPC now also includes the name of the package that is being prepared. We also regenerate all relevant code.

2023-03-15

feat(core): reintroduce dependency preparation rpc for tricorders

2023-03-14

chore: cleanup schemas

feat(schemas): add new field for tricorder urls

2023-03-13

chore: clean up old mark1 files from the tricorders

chore(MarkII): move all rules from label->target

2023-03-12

feat(tricorder/beam): prepare for bootstrapping To make the new tricorder flow work, we'll need a less involved tricorder bootstrapping process. Right now this is a regular Elixir release that has all code-generation pre-done (so no need to install protoc to bootstrap it).

2023-03-09

chore: move schemas to top of the repo

Add 'tricorders/' from commit '278bc98f0f8e2348c09abb5c6881c9a8c86d13c4' git-subtree-dir: tricorders git-subtree-mainline: b2cfc72f21cde0a32190635b8e181d42d4a968d0 git-subtree-split: 278bc98f0f8e2348c09abb5c6881c9a8c86d13c4

chore: restructure Mark I

2023-03-08

chore(docs): start preparing repo for publishing

2023-02-12

fix(tricorder): define missing messages

2023-02-05

chore: sync protos

feat(tricorder): begin new tricorder service schema

2023-01-09

chore: sync protos

feat(beam): improve analyzer

2022-11-29

fix: pass deps to tree splitting, and fix lift database entry labeling

feat: include dependencies during tree splitting

2022-11-28

feat(beam): receive and use dependency during signature generation

feat: feed in dependencies into the signature generation

2022-11-27

chore: sync protos

chore: bump schemas with new fields

2022-11-26

feat: get dependencies is now relocatable

chore: bump schemas

feat(beam): implement new rpcs and split up sources

chore: update schemas

2022-11-13

feat(schemas): introduce dependency requirement

fix: make build work again

feat: bring in new dependency requirement in proto schemas

2022-11-12

feat: introduce resolver services fix: codedb will override symbols now feat: emit new events for a label skipping and entering the queue feat: emit new service started event refactor: migrate all service communications to gRPC refactor: dependency resolver is now split into stages feat: implement experimental-regenerate-signatures flag feat: implement finding signatures by label chore: update protobuf schemas

feat(3rdpary): bootstrap tools by vendoring their dependencies

feat(github, gitlab): move git resolvers to gRPC protocol

feat(beam): rewrite resolver using gRPC protocol

2022-11-10

fix: clean up rfcs, update protos and namespaces

2022-11-09

feat: import new get interested paths request rpc

fix(erlang): implement get_interested_paths api

2022-11-08

chore: sync schemas

feat(schemas): clean up and update analyzer service rpcs

2022-11-07

chore: sync proto schemas

fix: update signature service schema

chore(beam): refactor proto libraries to not depend on symlinks Symlinks break when pulling repositories as tarballs.

fix: add symbol/ast to analyze file req/res

chore(schemas): bump!

2022-11-06

test(protobuf): add test workspace for protobuf + elixir rules/toolchains

chore(schemas): copy over proto schemas

feat: start defining grpc interfaces for the codedb