dashboard#build: command (/home/runner/_work/trieve/trieve/frontends/dashboard) /tmp/yarn--1726590159071-0.05042395760619223/yarn run build exited (2)

Process completed with exit code 2.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/unbound-method] Avoid referencing unbound methods which may cause unintentional scoping of `this`. If your function does not access `this`, you can annotate it with `this: void`, or consider using an arrow function instead.

[@typescript-eslint/no-unsafe-call] Unsafe call of an `any` typed value.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

[@typescript-eslint/no-unsafe-return] Unsafe return of an `any` typed value.

[@typescript-eslint/no-unused-vars] 'A' is defined but never used. Allowed unused vars must match /^_/u.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

[@typescript-eslint/no-unsafe-call] Unsafe call of an `any` typed value.

[@typescript-eslint/no-unsafe-call] Unsafe call of an `any` typed value.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

[@typescript-eslint/no-unsafe-call] Unsafe call of an `any` typed value.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

[@typescript-eslint/no-unsafe-call] Unsafe call of an `any` typed value.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

[@typescript-eslint/no-unsafe-assignment] Unsafe assignment of an `any` value.

ESLint errors detected.

dashboard#lint:CI: command (/home/runner/_work/trieve/trieve/frontends/dashboard) /tmp/yarn--1726590273241-0.8807917509512386/yarn run lint:CI exited (1)

Process completed with exit code 1.

ESLint errors detected.

[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.

[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.

[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.

[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.

[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.

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/