Hi — first-time publisher here, hitting a strange pattern on chinmay-02/firmware_sentry. compote component upload --dry-run passes clean every time ("Uploaded archive is valid"), but the real upload fails during server-side processing with a generic "unknown error," at a different stage each time:
v1.0.1: failed at "Check examples" (50%) — job c72a5504-f696-420a-98b3-f18d4e35b92a
v1.0.2: failed at "Check manifest" (25%) — job 23942111-91dc-44be-a7af-ffb78721b603
Both versions now show "already on the registry" and block re-upload, so I can't retry without burning a new version number each time. compote manifest lint --warnings-as-errors passes locally, compote 3.1.0. Is this a known issue with first-time namespace publishes, or could someone check what actually happened server-side for those job IDs? Happy to share the manifest/archive if useful.
New component upload fails processing at different stages every attempt (chinmay-02/firmware_sentry)
Who is online
Users browsing this forum: Baidu [Spider] and 1 guest