Repository navigation
Refresh Pixelbot for Pixeltable 0.7.18 and clarify the showcase - #8
Draft
pierrebrunelle wants to merge 4 commits into
Draft
pierrebrunelle wants to merge 4 commits into
pierrebrunelle wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pixelbot's first chat response could disappear when the URL changed, several media defaults targeted retired APIs, and the README led with contributor details. This refresh makes the app a clearer, runnable Pixeltable showcase on a reproducible 0.7.18 stack.
Validation: 51 backend tests and 12 frontend checks pass; Ruff, mypy, ESLint, TypeScript/Vite, package build/import, and fresh Python 3.11 resolution pass. The managed local service, CSV edit/undo flow, eight local video operations, real CLIP indexing/search, and a DETR forward pass were exercised. The baseline schema reconciles through five additive updates with no destructive operations or computed-column backfills; all 19 models then agree.
npm auditreports zero known vulnerabilities.Paid model calls and real notifications were not run; those provider contracts are mocked. See the review evidence for precise coverage and remaining limits.