gilbertw
@gilbertw
Member · Member since Oct 2026
0 followers · 0 following
- Topics created
- 4
- Posts created
- 5
- Likes given
- 8
- Likes received
- 12
- Days visited
- 0
- Solutions
- 0
Days visited count across the whole community, not just this forum.
Most active topics
- Blue-green deploy seems to keep adding more pods
6 replies · 0 votes
- Laravel queues stop processing after a deploy
1 replies · 0 votes
- How is burrow RAM billed? Does it include the page cache?
1 replies · 0 votes
- Pod restarts by itself 1–3 minutes after waking from idle
1 replies · 0 votes
Most liked posts
- Pod restarts by itself 1–3 minutes after waking from idle
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
5 likes
- Blue-green deploy seems to keep adding more pods
I switched one project to the bluegreen deploy strategy. I want one web pod that stops when idle and one worker that always runs. After a few deploys I had 8 we
3 likes
- Laravel queues stop processing after a deploy
After every deploy, the queue worker pod runs but processes nothing until I restart it by hand.
2 likes
- How is burrow RAM billed? Does it include the page cache?
The dashboard shows my burrow using 1.8 GB, but my process uses about 300 MB. Is the Linux page cache counted toward billed memory?
2 likes
Top categories
Top tags
- #deploys 2
- #pods 2
- #autoscaling 1
- #autostop 1
- #billing 1
- Laravel queues stop processing after a deploy
Liked by tomaszb
After every deploy, the queue worker pod runs but processes nothing until I restart it by hand.
Likes received · 10/12/2026
- Laravel queues stop processing after a deploy
Liked by rhea
After every deploy, the queue worker pod runs but processes nothing until I restart it by hand.
Likes received · 10/12/2026
- Postgres cluster has no writable primary, all nodes in recovery
After a region maintenance window, all three nodes of my Postgres cluster report in recovery. Nothing accepts writes. $ lark pg status -a db-prod NODE
Likes given · 10/12/2026
- How is burrow RAM billed? Does it include the page cache?
Liked by ozzie
The dashboard shows my burrow using 1.8 GB, but my process uses about 300 MB. Is the Linux page cache counted toward billed memory?
Likes received · 10/12/2026
- How is burrow RAM billed? Does it include the page cache?
Liked by rhea
The dashboard shows my burrow using 1.8 GB, but my process uses about 300 MB. Is the Linux page cache counted toward billed memory?
Likes received · 10/12/2026
- HTTP POST to a burrow URL does not wake a paused burrow (GET does)
2 KB. Not large.
Likes given · 10/12/2026
- How to retrieve boot diagnostics for a destroyed pod?
An ephemeral pod failed during boot and was destroyed. lark logs has nothing because it never started the app. Are boot-stage logs kept anywhere?
Likes given · 10/12/2026
- Blue-green deploy seems to keep adding more pods
It would help to post the full output of lark deploy, plus lark pod list before and after.
Likes given · 10/12/2026
- Blue-green deploy seems to keep adding more pods
Liked by tomaszb
I switched one project to the bluegreen deploy strategy. I want one web pod that stops when idle and one worker that always runs. After a few deploys I had 8 we
Likes received · 10/12/2026
- Blue-green deploy seems to keep adding more pods
Liked by rhea
I switched one project to the bluegreen deploy strategy. I want one web pod that stops when idle and one worker that always runs. After a few deploys I had 8 we
Likes received · 10/12/2026
- Blue-green deploy seems to keep adding more pods
Liked by bramblefox
I switched one project to the bluegreen deploy strategy. I want one web pod that stops when idle and one worker that always runs. After a few deploys I had 8 we
Likes received · 10/12/2026
- Burrow CLI: disable upgrade checks
Every lark burrow command checks for a CLI update first, which adds ~400 ms in CI. Is there a flag or environment variable to turn that off?
Likes given · 10/12/2026
- Pod restarts by itself 1–3 minutes after waking from idle
Liked by ozzie
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
Likes received · 10/12/2026
- Pod restarts by itself 1–3 minutes after waking from idle
Liked by deeplinker
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
Likes received · 10/12/2026
- Pod restarts by itself 1–3 minutes after waking from idle
Liked by tomaszb
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
Likes received · 10/12/2026
- Pod restarts by itself 1–3 minutes after waking from idle
Liked by rhea
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
Likes received · 10/12/2026
- Pod restarts by itself 1–3 minutes after waking from idle
Liked by bramblefox
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
Likes received · 10/12/2026
- New pods that mount a secret as a file are destroyed within one second
I added a file-mounted secret to lark.toml: [[files]] guest_path = "/etc/app/key.pem" secret_name = "TLS_KEY" New pods start and are destroyed within about
Likes given · 10/12/2026
- Burrows: persistent sandboxes that sleep when idle
How is the disk billed while it sleeps?
Likes given · 10/12/2026