Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable failing extension tests in test-plugins-build.sh #13173

Open
3 tasks
rak-phillip opened this issue Jan 21, 2025 · 0 comments
Open
3 tasks

Enable failing extension tests in test-plugins-build.sh #13173

rak-phillip opened this issue Jan 21, 2025 · 0 comments
Labels
QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@rak-phillip
Copy link
Member

rak-phillip commented Jan 21, 2025

Capi, Statckstate, and Harvester extensions are failing to build with the following error after bumping Vue to 3.5 ( #13085):

error  in ./index.ts

Syntax Error: Thread Loader (Worker 0)
[BABEL] /home/phillip/Development/rancher-dashboard/harvester-ui-extension/pkg/harvester/index.ts: decode_js.EntityDecoder is not a constructor (While processing: "/home/phillip/Development/rancher-dashboard/harvester-ui-extension/node_modules/@vue/cli-plugin-babel/preset.js")
    at Generator.next (<anonymous>)
    at Generator.next (<anonymous>)
    at Generator.next (<anonymous>)

This error appears to be related to past issues experienced in Dashboard related to issues with how yarn classic is managing packages that contain an alias. Related tickets:

Acceptance Criteria

  • Capi, Stackstate, and Harvester extensions receive a resolution for "entities": "4.5.0"
  • Capi, Stackstate, and Harvester extensions are re-enabled in test-plugins-build.sh
  • Affected extensions are passing tests
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant