Skip to content

fix(ci): downgrade Effect lint rules to warnings for CI compatibility #1

fix(ci): downgrade Effect lint rules to warnings for CI compatibility

fix(ci): downgrade Effect lint rules to warnings for CI compatibility #1

Triggered via push March 9, 2026 00:02
Status Failure
Total duration 1m 27s
Artifacts

ci.yml

on: push
Lint, Typecheck, Test, Browser Test, Build
1m 23s
Lint, Typecheck, Test, Browser Test, Build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
Lint, Typecheck, Test, Browser Test, Build
Process completed with exit code 2.
Lint, Typecheck, Test, Browser Test, Build
t3#typecheck: command (/home/runner/work/t3code/t3code/apps/server) /home/runner/.bun/bin/bun run typecheck exited (2)
Lint, Typecheck, Test, Browser Test, Build
The 'catch' callback in Effect.tryPromise returns global 'Error', which loses type safety as untagged errors merge together. Consider using a tagged error and optionally wrapping the original in a 'cause' property. effect(globalErrorInEffectCatch)
Lint, Typecheck, Test, Browser Test, Build
The 'catch' callback in Effect.tryPromise returns global 'Error', which loses type safety as untagged errors merge together. Consider using a tagged error and optionally wrapping the original in a 'cause' property. effect(globalErrorInEffectCatch)
Lint, Typecheck, Test, Browser Test, Build
Avoid using try/catch inside Effect generators. Use Effect's error handling mechanisms instead (e.g. Effect.try, Effect.tryPromise, Effect.catch, Effect.catchTag). effect(tryCatchInEffectGen)
Lint, Typecheck, Test, Browser Test, Build
Avoid using try/catch inside Effect generators. Use Effect's error handling mechanisms instead (e.g. Effect.try, Effect.tryPromise, Effect.catch, Effect.catchTag). effect(tryCatchInEffectGen)
Lint, Typecheck, Test, Browser Test, Build
Avoid using try/catch inside Effect generators. Use Effect's error handling mechanisms instead (e.g. Effect.try, Effect.tryPromise, Effect.catch, Effect.catchTag). effect(tryCatchInEffectGen)
Lint, Typecheck, Test, Browser Test, Build
Looks like the previous effect never fails, so probably this error handling will never be triggered. effect(catchUnfailableEffect)