feat: new dashboard experience #211
Triggered via pull request
September 18, 2024 00:21
Status
Failure
Total duration
1m 12s
Artifacts
–
frontend-tests.yml
on: pull_request
build-test
37s
eslint
50s
Annotations
2 errors and 15 warnings
build-test
analytics#build: command (/home/runner/_work/trieve/trieve/frontends/analytics) /tmp/yarn--1726618957387-0.3628115467836721/yarn run build exited (2)
|
build-test
Process completed with exit code 2.
|
frontends/analytics/src/components/charts/HeadQueries.tsx#L24
[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/LowConfidenceQueries.tsx#L24
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/LowConfidenceQueries.tsx#L35
[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/NoResultQueries.tsx#L23
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/NoResultQueries.tsx#L36
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/NoResultQueries.tsx#L37
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/NoResultQueries.tsx#L45
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/NoResultQueries.tsx#L56
[solid/reactivity] The reactive variable 'props.params' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/components/charts/RagQueries.tsx#L145
[solid/reactivity] The reactive variable 'columns' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L31
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L41
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L42
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
frontends/analytics/src/pages/tablePages/SearchTablePage.tsx#L52
[solid/reactivity] The reactive variable 'props.getValue' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored.
|
eslint
The following actions uses node12 which is deprecated and will be forced to run on node16: ataylorme/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
eslint
The following actions use a deprecated Node.js version and will be forced to run on node20: ataylorme/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|