#Platform artifact daemon startup hooks cause Python inspection, metadata, packaging, and publication

1 messages · Page 1 of 1 (latest)

languid sailBOT
#

Reported by @worn pulsar

Bug Report: Platform artifact daemon startup hooks cause Python inspection, metadata, packaging, and publication
`Steps to Reproduce`
  1. Upload or generate a Python/project artifact with multiple files.
  2. Run validation, metadata inspection, checksum, ZIP, or package-publication workflow.
  3. Let platform helpers inspect files or run bare python/python3.
  4. Observe platform startup chain load presentation_artifact_tool / artifact_tool_rpc_daemon-bun.
  5. Repeat with safe interpreter: env -i PATH=/usr/bin:/bin PYTHONPATH=. /usr/bin/python3 -S ...
`Expected Result`

Validation, file metadata scanning, checksum generation, archive validation, packaging, and artifact publication should complete in bounded time without hidden daemon startup, bare-Python hangs, orphaned helper processes, or platform-side timeouts. Python helpers should use an explicit safe interpreter path or an approved platform-owned startup mode.

`Actual Result`

Bare python/python3 helper paths can load /opt/python-hooks/sitecustomize.py, which imports presentation_artifact_tool and interacts with artifact_tool_rpc_daemon-bun. Trivial Python commands and metadata helper calls can print output but fail to exit cleanly, hang, timeout, or destabilize packaging/publication. Creating expanded artifact packages under /mnt/data triggered repeated metadata-helper hangs.

`Environment`

ChatGPT sandbox; /opt/pyvenv Python 3.13; artifact_tool_rpc_daemon-bun

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

worn pulsar
#

Any workflow that creates more than a small number of output files must stage outside /mnt/data, produce a single final artifact, validate it, then move only the final artifact into /mnt/data. Expanded output directories in /mnt/data are prohibited unless the workflow is explicitly testing metadata/indexing behavior.

#

SAFE LANE:
explicit Unix commands
safe Python with /usr/bin/python3 -S
/tmp staging
plain text artifacts
bounded steps
single final output moved to /mnt/data