Skip to content
Labelbox Python SDK Publish

Labelbox Python SDK Publish #127

Sign in to view logs

Labelbox Python SDK Publish

Labelbox Python SDK Publish #127

Manually triggered January 16, 2025 00:06
@vbrodskyvbrodsky
⁠ d40fb6e
develop
Status Cancelled
Total duration 10m 9s
Artifacts 3

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
2s
build-lbox / provenance_python / detect-env
Matrix: build-lbox / container-publish
Matrix: build-lbox / pypi-publish
build-lbox  /  ...  /  generator
19s
build-lbox / provenance_python / generator
build-lbox  /  ...  /  upload-assets
6s
build-lbox / provenance_python / upload-assets
build-lbox  /  ...  /  final
0s
build-lbox / provenance_python / final
build
0s
build
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

3 errors and 18 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/develop` * `job_workflow_ref`: `Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/develop` * `ref`: `refs/heads/develop` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
build-lbox / pypi-publish (lbox-example)
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-example` * `repository`: `Labelbox/labelbox-python` * `repository_owner`: `Labelbox` * `repository_owner_id`: `33847372` * `workflow_ref`: `Labelbox/labelbox-python/.github/workflows/publish.yml@refs/heads/develop` * `job_workflow_ref`: `Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/develop` * `ref`: `refs/heads/develop` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
build-lbox / container-publish (lbox-example)
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 / test-build (3.11, STAGING_LABELBOX_API_KEY, DA_GCP_LABELBOX_API_KEY, lbox-example)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / test-build (3.11, STAGING_LABELBOX_API_KEY, DA_GCP_LABELBOX_API_KEY, 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 / test-build (3.12, STAGING_LABELBOX_API_KEY_5, DA_GCP_LABELBOX_API_KEY, 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 / test-build (3.10, STAGING_LABELBOX_API_KEY_4, DA_GCP_LABELBOX_API_KEY, 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 / test-build (3.13, STAGING_LABELBOX_API_KEY_2, DA_GCP_LABELBOX_API_KEY, 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 / test-build (3.10, STAGING_LABELBOX_API_KEY_4, DA_GCP_LABELBOX_API_KEY, lbox-example)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / test-build (3.13, STAGING_LABELBOX_API_KEY_2, DA_GCP_LABELBOX_API_KEY, lbox-example)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / test-build (3.9, STAGING_LABELBOX_API_KEY_3, DA_GCP_LABELBOX_API_KEY, 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 / test-build (3.9, STAGING_LABELBOX_API_KEY_3, DA_GCP_LABELBOX_API_KEY, lbox-example)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-lbox / test-build (3.12, STAGING_LABELBOX_API_KEY_5, DA_GCP_LABELBOX_API_KEY, lbox-example)
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 / build (lbox-example)
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
build-lbox / container-publish (lbox-clients)
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
build-lbox-clients
17 KB
build-lbox-example
4.23 KB
lbox-clients.intoto.jsonl Expired
5.31 KB