Skip to content

[Dashboard] Fix: Use Secret Key to Fetch Routes on Server (#6333) #19323

[Dashboard] Fix: Use Secret Key to Fetch Routes on Server (#6333)

[Dashboard] Fix: Use Secret Key to Fetch Routes on Server (#6333) #19323

Triggered via push February 25, 2025 06:21
Status Failure
Total duration 6m 12s
Artifacts

CI.yml

on: push
optimize_ci
4s
optimize_ci
Matrix: E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 8 warnings
Unit Tests
***#test: command (/home/runner/work/js/js/packages/***) /home/runner/setup-pnpm/node_modules/.bin/pnpm run test exited (1)
Unit Tests
Process completed with exit code 1.
optimize_ci
Request body: {"token":"***","caller":{"name":"graphite-ci-action","version":"0.0.0"},"context":{"kind":"GITHUB_ACTIONS","repository":{"owner":"***-dev","name":"js"},"sha":"cf202c03ddc11631d02de0b053914dec2b05c176","ref":"refs/heads/main","head_ref":"","run":{"workflow":"CI","job":"optimize_ci","run":13514969500}}}
optimize_ci
Response status: 400
optimize_ci
***-dev/js/undefined
optimize_ci
Response returned a non-200 status. Skipping Graphite checks.
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-card.tsx#L77
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-card.tsx#L86
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-row.tsx#L79
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/dashboard/src/app/(dashboard)/(bridge)/routes/components/server/routelist-row.tsx#L113
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element