Skip to content
CI

feat(web): add global metadata visibility toggle #42

Sign in to view logs

feat(web): add global metadata visibility toggle

feat(web): add global metadata visibility toggle #42

Triggered via push May 18, 2026 14:11
@offendingcommitoffendingcommit
pushed e490d91
main
Status Failure
Total duration 33s
Artifacts –

ci.yml

on: push
Lint, type-check, test & build
25s
Lint, type-check, test & build
Release
0s
Release
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Lint, type-check, test & build
Process completed with exit code 2.
Lint, type-check, test & build
@openconcho/web#test: command (/home/runner/work/openconcho/openconcho/packages/web) /home/runner/setup-pnpm/node_modules/.bin/bin/pnpm run test exited (1)
src/test/app.test.tsx > first load with no config > renders the settings form on first paint when no config exists: packages/web/src/test/app.test.tsx#L32
TestingLibraryElementError: Unable to find an element with the text: /Connect to Honcho Cloud or your self-hosted instance/i. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div> <div style="padding: 0.5rem; max-width: 100%;" > <div style="display: flex; align-items: center; gap: .5rem;" > <strong style="font-size: 1rem;" > Something went wrong! </strong> <button style="appearance: none; font-size: 0.6em; border: 1px solid currentcolor; padding: 0.1rem 0.2rem; font-weight: bold; border-radius: .25rem;" > Hide Error </button> </div> <div style="height: 0.25rem;" /> <div> <pre style="font-size: 0.7em; border: 1px solid red; border-radius: .25rem; padding: 0.3rem; color: red; overflow: auto;" > <code> useMetadataContext must be used within MetadataProvider </code> </pre> </div> </div> </div> </body> Ignored nodes: comments, script, style <body> <div> <div style="padding: 0.5rem; max-width: 100%;" > <div style="display: flex; align-items: center; gap: .5rem;" > <strong style="font-size: 1rem;" > Something went wrong! </strong> <button style="appearance: none; font-size: 0.6em; border: 1px solid currentcolor; padding: 0.1rem 0.2rem; font-weight: bold; border-radius: .25rem;" > Hide Error </button> </div> <div style="height: 0.25rem;" /> <div> <pre style="font-size: 0.7em; border: 1px solid red; border-radius: .25rem; padding: 0.3rem; color: red; overflow: auto;" > <code> useMetadataContext must be used within MetadataProvider </code> </pre> </div> </div> </div> </body> ❯ waitForWrapper ../../node_modules/.pnpm/@testing-library+dom@10.4.1/node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ ../../node_modules/.pnpm/@testing-library+dom@10.4.1/node_modules/@testing-library/dom/dist/query-helpers.js:86:33 ❯ src/test/app.test.tsx:32:17
Lint, type-check, test & build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/