Skip to content

Kiloclaw tracked image tag #2942

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
St0rmz1 merged 4 commits into from
Apr 30, 2026
Merged

Kiloclaw tracked image tag #2942

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
268e63d
feat(kiloclaw): denormalize tracked_image_tag to kiloclaw_instances
St0rmz1 Apr 29, 2026
af33e41
fix a few issues
St0rmz1 Apr 29, 2026
a4dc3f9
test(kiloclaw): account for tracked_image_tag sync waitUntil in alarm…
St0rmz1 Apr 29, 2026
dbce9ba
Merge remote-tracking branch 'origin/main' into kiloclaw-tracked-imag…
St0rmz1 Apr 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions packages/db/src/migrations/0107_classy_ultimo.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
ALTER TABLE "kiloclaw_instances" ADD COLUMN "tracked_image_tag" text;--> statement-breakpoint
CREATE INDEX "IDX_kiloclaw_instances_tracked_image_tag" ON "kiloclaw_instances" USING btree ("tracked_image_tag") WHERE "kiloclaw_instances"."destroyed_at" is null;
Copy link
Copy Markdown
Contributor

@kilo-code-bot kilo-code-bot Bot Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Build this index concurrently

kiloclaw_instances is already populated, and a plain CREATE INDEX takes a write-blocking lock until the index build finishes. Use a concurrent index build (or another safe migration path) so instance lifecycle writes are not blocked during deployment.

Copy link
Copy Markdown
Contributor Author

@St0rmz1 St0rmz1 Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on my tests, index creation took less than 1 second. Only 1 table is locked. Requests are queued. I feel like this is not a huge concern.

Copy link
Copy Markdown
Contributor

@pandemicsyn pandemicsyn Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also relatively speaking a pretty small table. we'll have less than 75k record in it.

Loading