Bug
Running a deployment of debuff - based off of dev branch, I ran into an error trying to review a report by clicking the eye icon in this image:
I get this error at https://redacted.url/dashboard/queue/1:
The console log shows:
GET https://redacted.url/dashboard/queue/1 [HTTP/2 404 37ms]
XHR GET https://redacted.url/api/queue/NaN [HTTP/2 400 37ms]
Reproduction
- Deploy the production image (tested with
v1.0.0-dev.10).
- Create or receive a report.
- Open the report from the queue via the view/eye action.
- Observe the detail page error and the
/api/queue/NaN request.
Notes from LLM agent
- This is a static-export bug, not a Docker/Tailscale setup issue.
generateStaticParams() creates a fake _ route at build time. The deployed detail page reads that _ instead of the real URL’s 1, producing /api/queue/NaN.useParams() was not sufficient in this static fallback. The fix is to read the browser pathname, validate the ID, and serve the fallback page with HTTP 200 instead of 404. The label-definition detail route has the same pattern.- dev compose starts a live Next development server, which may hide this bug because it resolves route params dynamically
Bug
Running a deployment of debuff - based off of dev branch, I ran into an error trying to review a report by clicking the eye icon in this image:
I get this error at https://redacted.url/dashboard/queue/1:
The console log shows:
GET https://redacted.url/dashboard/queue/1 [HTTP/2 404 37ms]
XHR GET https://redacted.url/api/queue/NaN [HTTP/2 400 37ms]
Reproduction
v1.0.0-dev.10)./api/queue/NaNrequest.Notes from LLM agent
generateStaticParams()creates a fake_route at build time. The deployed detail page reads that_instead of the real URL’s1, producing/api/queue/NaN.useParams()was not sufficient in this static fallback. The fix is to read the browser pathname, validate the ID, and serve the fallback page with HTTP 200 instead of 404. The label-definition detail route has the same pattern.