Skip to content

[codex] Add attachment update 4999 reproducer#257

Open
Flerpharos wants to merge 1 commit into
mainfrom
agent/attachment-update-4999-reproducer
Open

[codex] Add attachment update 4999 reproducer#257
Flerpharos wants to merge 1 commit into
mainfrom
agent/attachment-update-4999-reproducer

Conversation

@Flerpharos

Copy link
Copy Markdown
Collaborator

Summary

  • add an explicitly gated live integration reproducer for attachment update error 4999
  • report the update endpoint, object identifiers, request parameters, payload size, and payload hash
  • document Bash and PowerShell commands for maintainers to rerun the reproducer

Why

The existing integration suite performs attachment updates only as part of a broader metadata scenario. This focused path creates a minimal isolated attachment, captures the request shape, and reports a structured response when LabArchives returns 4999.

Validation

  • uv run --python 3.10 pytest --no-cov --integration tests/test_integration.py -k attachment_update_4999_reproducer (skipped as expected without the opt-in environment variable)
  • uv run --python 3.10 pre-commit run --all-files
  • uv run --python 3.10 pre-commit run --all-files --hook-stage pre-push
  • uv run --python 3.10 sphinx-build -b html docs/source docs/_build/html

The live LabArchives update was not run because the explicit reproducer gate was left disabled.

Fixes #155

@Flerpharos
Flerpharos marked this pull request as ready for review July 13, 2026 17:56
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.

Add an integration reproducer for attachment update 4999 failures

1 participant