tvoronov
@tvoronov
Member · Member since Feb 2026
SRE. I break CI so you do not have to.
0 followers · 0 following
Badges and trust level are earned across the whole community.
- Topics created
- 3
- Posts created
- 10
- Likes given
- 21
- Likes received
- 42
- Days visited
- 0
- Solutions
- 3
Days visited count across the whole community, not just this forum.
Most active topics
- Cache restore misses every run after switching to a matrix build
3 replies · 8 votes
- Pair suggests deprecated APIs for our internal SDK
2 replies · 6 votes
- Can I choose the machine size per branch?
2 replies · 0 votes
Most liked posts
- Self-hosted runner goes offline after host reboot
Install it as a service instead of running run.sh: sudo ./svc.sh install lattice-runner sudo ./svc.sh start systemctl status lattice.runner.* The service unit r
12 likes
- Secrets are empty in pull requests from forks
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
10 likes
- Cache restore misses every run after switching to a matrix build
After moving our test job to a matrix (node: [18, 20, 22]) the dependency cache never hits. Every run prints: Cache not found for input keys: deps-linux-6f1c2a…
8 likes
- Pair suggests deprecated APIs for our internal SDK
Pair keeps completing calls to client.fetchAll(), which we removed two versions ago. Is there a way to tell it which version of an internal library we use?
6 likes
- Branch protection: allow bots to push but require review for humans
Yes: in the rule set, add the bot's app to Bypass list with mode Always. Humans stay subject to the review requirement.
3 likes
Top categories
Top tags
- #bug 1
- #caching 1
- #pair 1
- #pipelines 1
- #product-feedback 1
Recent badges
- Pair suggests deprecated APIs for our internal SDK
Liked by quillon42
Pair keeps completing calls to client.fetchAll(), which we removed two versions ago. Is there a way to tell it which version of an internal library we use?
Likes received · 10/12/2026
- Cache restore misses every run after switching to a matrix build
Liked by quillon42
After moving our test job to a matrix (node: [18, 20, 22]) the dependency cache never hits. Every run prints: Cache not found for input keys: deps-linux-6f1c2a…
Likes received · 10/12/2026
- Read access to packages from a Lattice App installation token?
Quick update: package read permission for Lattice Apps is now in private beta. If you want in, reply here with your organization name and we will enable it. # a
Likes given · 10/12/2026
- Read access to packages from a Lattice App installation token?
Would love an actions-style packages: read on the app manifest. Even read-only would solve 90% of cases.
Likes given · 10/12/2026
- Read access to packages from a Lattice App installation token?
Liked by mbellweather
+1. We rotate the bot token monthly and it is our most common deploy failure.
Likes received · 10/12/2026
- Read access to packages from a Lattice App installation token?
Same problem here — our deploy app has to keep a bot user's token around just for this. Not great for audits.
Likes given · 10/12/2026
- Read access to packages from a Lattice App installation token?
Hi @mbellweather — thanks for the clear report. Package permissions are not available to Lattice Apps today; installation tokens can only reach packages that ar
Likes given · 10/12/2026
- Read access to packages from a Lattice App installation token?
I am building a Lattice App that needs to pull container images from the packages registry of the repositories it is installed on. Looking at the list of app pe
Likes given · 10/12/2026
- A "good first issue" feed on the explore page
As a student, finding a project to contribute to is hard. A feed of good-first-issues filtered by language would help a lot.
Likes given · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by mbellweather
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by ochieng-a
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by priyanka-dev
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by rafaelcosta
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by m-okoye
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by kaito-ishida
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by lena-sch
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by sanne-dev
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by quillon42
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- Secrets are empty in pull requests from forks
Liked by zhenya-k
No — on purpose. A workflow triggered by a fork's pull request runs the fork's code, so secrets are withheld; otherwise anyone could open a PR that prints them.
Likes received · 10/12/2026
- I built a terminal dashboard for pipeline runs
Liked by ochieng-a
This is brilliant. Does it handle self-hosted runner labels?
Likes received · 10/12/2026