Skip to content

fix: reject empty trajectory submissions - #199

Open
uuzzrm wants to merge 1 commit into
SkillNerds:mainfrom
uuzzrm:fix/reject-empty-trajectories
Open

fix: reject empty trajectory submissions#199
uuzzrm wants to merge 1 commit into
SkillNerds:mainfrom
uuzzrm:fix/reject-empty-trajectories

Conversation

@uuzzrm

@uuzzrm uuzzrm commented Aug 9, 2026

Copy link
Copy Markdown

Summary Reject empty trajectory submissions before resolving a watch directory or writing files. ## Changes - Reject empty and whitespace-only content at the shared submit_trajectory boundary. - Reject an empty JSON object, which otherwise becomes an empty # Trajectory document. - Add regression coverage for markdown, raw, JSON, and the HTTP submission path. ## Test plan - [x] Added/updated unit tests for the change - [x] python -m pytest -q tests/test_trajectory_submit_validation.py tests/test_sanitize.py --timeout=15 (17 passed) - [x] python -m py_compile src/xskill/ecosystems/_shared.py tests/test_trajectory_submit_validation.py - [ ] make test passes — the full 2,051-test run exceeded the local Windows timeout before completion - [ ] make e2e passes — not run locally ## Linked issues Closes #27

AI assistance

AI assistance was used for repository research, implementation, and test drafting. The diff and validation results are documented here for maintainer review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: /api/v1/trajectories/submit accepts empty/whitespace content, ingests a 0-byte trajectory

1 participant