Fix post-merge Pixelbot 3.0 audit findings - #6
Merged
Merged
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.
The merged Pixelbot 3.0 app had several post-upgrade defects that only appeared in packaging and real Pixeltable 0.7.7 catalog use. This audit fixes the broken sdist, invalid video-frame column references, pipeline metadata failures, unsafe URL/media paths, and stale
agentsfrontend assumptions.The service now uses the public 0.7.7 frame and iterator metadata, handles B-tree indexes with null parameters, writes slideshows directly with PyAV, restricts URL downloads and generated-media paths, rejects unsupported legacy Office formats, and caps read/scratch responses. Directly imported media/document packages are declared, CI runs pytest on Python 3.11 through 3.14, verifies fresh dependency resolution, and rejects polluted source distributions.
Validation:
Provider-backed computed calls and hosted deployment remain outside this local audit; provider tests use mocks only.