Scrapes groups and graphs for member counts and recent activity respectively,
and uses that to print out a "tally" of activity for all local groups and their
channels. Since this output is intended to be shared with other parties,
anonymizes resource identifiers by default.
When %remove-nodes is sent as an update, it may refer to a parent node,
in which case the deletion of all the parent's children is implied. If
we hold onto references to nodes outside of graph-store, we are unable
to tell which of our references were affected, other than iterating over
every reference to check if one of the deleted indices is a prefix of
the reference. This is obviously undesirable, so we emit all of the
nodes we deleted, including the nodes deleted implicitly.
Creates a noun poke %fix-dangling, which iterates through the unreads
and dismiss those which refer to nodes which no longer exist.
Additionally, adds a migration which runs this poke.
* origin/mp/meta/deploy:
meta: update MAINTAINERS for auto-deploy
meta: add CD development stream information
Signed-off-by: Matilde Park <matilde.park@gmail.com>
Sets two environment variables, LANDSCAPE_STREAM and
LANDSCAPE_SHORTHASH, to be employed by landscape builds. Also reverts
the janeway version used to v0.13.1 as the --dev flag is unnecessary.
* origin/lf/update-log-order:
graph-store: use +bap for update-log listification
graph-store: add TODO comment for backwards tap
graph-store: run update log in correct order
Signed-off-by: Matilde Park <matilde.park@gmail.com>
Some other commits have been squashed in:
meta: remove user declarations for glob action
This is a tricky problem. SSH needs UID 0 to exist, and intuitively it
does (root), but we can't enforce that when GitHub is running our
container. Specifying "USER 0:0" in the actions Dockerfile doesn't cut
it.
Instead it seems best to try and construct a shadow-utils setup on the
underlying Docker image.
meta: target glob workflow at release/next-js
Adds a workflow that executes the 'glob' action on every push and pull
request to the 'release/next-js' branch.
(For now this is just staged to the 'jt/lacd' branch for testing.)
This action, when supplied with the appropriate arguments, will create a
Landscape glob from GITHUB_SHA [1] and deploy it OTA to the appropriate
ship.
It needs to be supplied the following:
* ship name
* base64-encoded GCP Service Account credentials
* a base64-encoded SSH secret key to be used for GCP actions
* the corresponding base64-encoded SSH public key
[1]: https://docs.github.com/en/free-pro-team@latest/actions/reference/environment-variables
We can't molt until clay has gotten its pork or else we'll build the old
app against the new kernel. This ignores vegas, since we should get a
notification from clay on /sys/lyv.
