53:1 error Definition for rule 'import/first' was not found import/first\n2026-01-16T04:48:47.3449237Z \n2026-01-16T04:48:47.3449561Z /home/runner/work/sistent/sistent/src/__testing__/routing.test.ts\n2026-01-16T04:48:47.3450573Z ##[error] 46:56 error Unexpected any. Specify a different type @typescript-eslint/no-explicit-any\n2026-01-16T04:48:47.3451454Z \n2026-01-16T04:48:47.3451715Z /home/runner/work/sistent/sistent/src/actors/worker/workerfy.ts\n2026-01-16T04:48:47.3452839Z ##[error] 74:7 error Expected an assignment or function call and instead saw an expression @typescript-eslint/no-unused-expressions\n2026-01-16T04:48:47.3454462Z ##[error] 75:7 error Expected an assignment or function call and instead saw an expression @typescript-eslint/no-unused-expressions\n2026-01-16T04:48:47.3455332Z \n2026-01-16T04:48:47.3455564Z /home/runner/work/sistent/sistent/src/base/Hidden/Hidden.tsx\n2026-01-16T04:48:47.3456037Z 5:55 error Error: Cannot access refs during render\n2026-01-16T04:48:47.3456254Z \n2026-01-16T04:48:47.3457918Z React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).\n2026-01-16T04:48:47.3458978Z \n2026-01-16T04:48:47.3459246Z /home/runner/work/sistent/sistent/src/base/Hidden/Hidden.tsx:5:55\n2026-01-16T04:48:47.3459605Z 3 |\n2026-01-16T04:48:47.3460030Z 4 | export const Hidden = React.forwardRef<HTMLDivElement, MuiHiddenProps>((props, ref) => {\n2026-01-16T04:48:47.3460639Z > 5 | return React.cloneElement(<MuiHidden {...props} />, { ref });\n2026-01-16T04:48:47.3461193Z | ^^^^^^^ Passing a ref to a function may read its value during render\n2026-01-16T04:48:47.3461585Z 6 | });\n2026-01-16T04:48:47.3461752Z 7 |\n2026-01-16T04:48:47.3461983Z 8 | export default Hidden; react-hooks/refs\n2026-01-16T04:48:47.3462181Z \n2026-01-16T04:48:47.3462666Z /home/runner/work/sistent/sistent/src/custom/CatalogDesignTable/CatalogDesignTable.tsx\n2026-01-16T04:48:47.3464046Z ##[error] 75:11 error Expected an assignment or function call and instead saw an expression @typescript-eslint/no-unused-expressions\n2026-01-16T04:48:47.3464979Z \n2026-01-16T04:48:47.3465295Z /home/runner/work/sistent/sistent/src/custom/CatalogDetail/ChallengesSection.tsx\n2026-01-16T04:48:47.3466041Z 22:7 error Error: Calling setState synchronously within an effect can trigger cascading renders\n2026-01-16T04:48:47.3466413Z \n2026-01-16T04:48:47.3467963Z Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:\n2026-01-16T04:48:47.3469020Z * Update external systems with the latest state from React.\n2026-01-16T04:48:47.3469712Z * Subscribe for updates from some external system, calling setState in a callback function when external state changes.\n2026-01-16T04:48:47.3470156Z \n2026-01-16T04:48:47.3470925Z Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).\n2026-01-16T04:48:47.3471589Z \n2026-01-16T04:48:47.3471931Z /home/runner/work/sistent/sistent/src/custom/CatalogDetail/ChallengesSection.tsx:22:7\n2026-01-16T04:48:47.3472357Z 20 | useEffect(() => {\n2026-01-16T04:48:47.3472586Z 21 | if (autoUpdate) {\n2026-01-16T04:48:47.3473039Z > 22 | setOpenChallenges((filteredAcademyData?.['challenges'] ?? []).length > 0);\n2026-01-16T04:48:47.3473541Z | ^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect\n2026-01-16T04:48:47.3473860Z 23 | }\n2026-01-16T04:48:47.3474094Z 24 | }, [filteredAcademyData, autoUpdate]);\n2026-01-16T04:48:47.3474410Z 25 | react-hooks