Skip to content

Labelbox Python SDK Publish #136

Labelbox Python SDK Publish

Labelbox Python SDK Publish #136

Manually triggered January 16, 2025 03:27
Status Cancelled
Total duration 6m 27s
Artifacts 2

publish.yml

on: workflow_dispatch
build-lbox  /  path-filter
21s
build-lbox / path-filter
Matrix: build-lbox / test-build
Matrix: build-lbox / build
build-lbox  /  ...  /  detect-env
5s
build-lbox / provenance_python / detect-env
Matrix: build-lbox / container-publish
Matrix: build-lbox / pypi-publish
build-lbox  /  ...  /  generator
12s
build-lbox / provenance_python / generator
build-lbox  /  ...  /  upload-assets
5s
build-lbox / provenance_python / upload-assets
build-lbox  /  ...  /  final
0s
build-lbox / provenance_python / final
provenance_python  /  detect-env
provenance_python / detect-env
Matrix: test-build
publish-python-package-to-release
0s
publish-python-package-to-release
provenance_python  /  generator
provenance_python / generator
container-publish
0s
container-publish
pypi-publish
0s
pypi-publish
provenance_python  /  upload-assets
provenance_python / upload-assets
provenance_container  /  detect-env
provenance_container / detect-env
provenance_python  /  final
provenance_python / final
provenance_container  /  generator
provenance_container / generator
provenance_container  /  final
provenance_container / final
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 11 warnings
build-lbox / pypi-publish (lbox-clients)
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:Labelbox/labelbox-python:environment:publish-lbox-clients` * `repository`: `Labelbox/labelbox-python` * `repository_owner`: `Labelbox` * `repository_owner_id`: `33847372` * `workflow_ref`: `Labelbox/labelbox-python/.github/workflows/publish.yml@refs/heads/VB/debug-2` * `job_workflow_ref`: `Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/VB/debug-2` * `ref`: `refs/heads/VB/debug-2` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
build-lbox / container-publish (lbox-clients)
The run was canceled by @vbrodsky.
build-lbox / path-filter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / build (lbox-clients)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / provenance_python / detect-env
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / provenance_python / generator
Restore cache failed: Dependencies file is not found in /home/runner/work/labelbox-python/labelbox-python. Supported file pattern: go.sum
build-lbox / provenance_python / upload-assets
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / provenance_python / final
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size Digest
build-lbox-clients Expired
17 KB
sha256:ac63b1c2d8a4ff5a44d7467e3ba9771495bede8d407e83d072ef02cb09026c05
lbox-clients.intoto.jsonl Expired
5.32 KB
sha256:f52497b9b7f42482159c56bdd19426c8a79da927a82c1e8391c315328699a9a8