Re-adding-people-page #538

Pato-desu · 2025-11-06T23:41:54Z

No description provided.

netlify · 2025-11-06T23:42:00Z

✅ Deploy Preview for pauseai ready!

Name	Link
🔨 Latest commit	`85c5c52`
🔍 Latest deploy log	https://app.netlify.com/projects/pauseai/deploys/69189d4bcc4c8500086d173c
😎 Deploy Preview	https://deploy-preview-538--pauseai.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 51 (🔴 down 2 from production) Accessibility: 89 (no change from production) Best Practices: 100 (no change from production) SEO: 98 (no change from production) PWA: - View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Pato-desu · 2025-11-06T23:45:31Z

Issue: #533

Pato-desu · 2025-11-06T23:46:17Z

Pato-desu · 2025-11-07T01:07:34Z

There's a 500 internal error in /people i don't know how to fix.
@joepio @anthonybailey @Wituareard can any of you take care of it, please?

Pato-desu · 2025-11-07T01:17:31Z

I don't understand much of the changes i did, the code is basically the same as before when the page was running

joepio · 2025-11-07T09:31:09Z

No 500 here in local dev on your branch, works fine @Pato-desu . I'm assuming you're missing the Airtable token.

However, I do see a different issue. We currently use the old volunteers table that has been migrated to a new one, but in the migration the photo's have been lost. So we have to move the photos.

Pato-desu · 2025-11-07T09:47:14Z

Yeah, i know. Same with titles. Its in the bullet TODO points

anthonybailey · 2025-11-07T12:20:06Z

From previous experience "no 500 here in local dev" does not predict no 500 in the wild, alas. (Which is what we have in the preview, to be clear.)

Was that using the Netlify CLI @joepio ? No need to invest, just a y/n

I can look at this issue. Also have opinions on some of the "where shall we manage the relevant data?" questions the todos imply.

Pato-desu · 2025-11-07T19:24:05Z

Also have opinions on some of the "where shall we manage the relevant data?" questions the todos imply.

what data?

Wituareard · 2025-11-08T01:06:04Z

@anthonybailey I tracked down the error to this line in paraglide bc "window" is defined in Deno but "window.location" seems to be undefined. But I have no idea why "setLocale" would be called in the first place https://github.com/opral/monorepo/blob/b951344b1f976a0f34729909d659c1fa2de6ae88/inlang/packages/paraglide/paraglide-js/src/compiler/runtime/set-locale.js#L112

Wituareard · 2025-11-08T01:08:56Z

And it might also mean that we can't serve any dynamic pages whatsoever at the moment? We don't have any non-API routes in production afaik

anthonybailey · 2025-11-08T02:41:04Z

what data?

We store names and emails and team assignments in a mess of old and new Airtables.

In general, we've had some success representing structured data that changes over time and is presented on website pages as JSON in the source-controlled repository rather than in a database. Allows pages to be static, etc.

Pato-desu · 2025-11-11T03:51:09Z

So, I don't know what you guys did but it was working today for me so thanks for that.
Now I changed the table and it's broken again.
Will see if i can fix it tomorrow.

Wituareard · 2025-11-12T03:59:04Z

Uhh, I don't think anything changed and I still get a 500 on /people

Pato-desu · 2025-11-12T06:47:19Z

@Wituareard I may should be doing something on my side. I stopped trying to do so because what usually happens to me is: I sometimes get 500 error, then I reload, I get the fallback data, then i reload, and get the actual people.

Could this be something that will get fixed once public?

anthonybailey · 2025-11-12T08:45:05Z

That is not likely, but given our lack of clarity anything is possible.

(I observe similar behaviour with the page on the preview site. First fetch from a sufficiently new client is always a 500. Future attempts succeed very consistently. No correlated problems on other pages.)

Pato-desu · 2025-11-12T13:39:06Z

All my comments were about the preview, sorry, I thought I clarified it but I only did to Joep in his DMs.
I was finally able to run stuff locally and it's working fine so... 🤷. Should we worry about the preview?

Testing first-request behavior on cold start

anthonybailey · 2025-11-12T16:56:30Z

Investigation Update: 500 Error on `/people` Route

Successfully Reproduced the Issue

We've definitively reproduced and identified the root cause of the 500 error on first access to /people.

Confirmed Pattern

First request to cold edge function: HTTP 500 (~6 seconds)
Subsequent requests: HTTP 200 (work correctly)
Edge function stays warm for multiple requests after initialization

Root Cause

The error occurs during paraglide locale initialization in Netlify Edge Functions (Deno runtime):

The initialization code checks typeof window !== "undefined"
In production Deno, window exists but window.location is undefined
Accessing window.location.href throws an error, causing the 500 response
Once the edge function is warm, subsequent requests bypass the failing initialization

Evidence

Reproduced with curl on fresh deployments (commit fb949da)
Confirmed with browser testing
When multiple users hit a cold edge simultaneously, multiple edge instances can spin up (multiple 500s observed)
Local testing with Deno 2.2.4 does NOT reproduce the issue (different window object behavior)

Why It Works Locally

pnpm preview: Runs in Node.js where window is undefined on server
netlify serve: Uses local Deno 2.2.4 where window is fully undefined
Production: Uses unknown Deno version with partial window object

Potential Solutions

Immediate fix: Change prerender = false to prerender = true in /people/+page.ts (make page static)
- Pros: Eliminates the issue entirely
- Cons: Loses dynamic functionality if needed
Runtime patch: Fix paraglide initialization to check window.location existence
- Add proper checks: typeof window !== "undefined" && typeof window.location !== "undefined"
- Location: src/lib/paraglide/runtime.js lines ~147 and ~300
Configuration workaround: Exclude /people from edge function handling
- Modify netlify configuration to serve this route differently

Speculation

The production Deno version appears to be older than 2.2.4 with different window object implementation. Geographic distribution may affect which edge nodes/versions serve requests.

The caching layer (1-hour TTL based on User-Agent) masks the issue for most users after the first visitor takes the hit.

anthonybailey · 2025-11-12T17:18:57Z

This all matches with the other issue where we saw a 500 in production after introducing a dynamic route for our statement: #370 (and PR #379)

It overlaps with issues we had with preview-all-locales (many notes from PR #325) but is distinct in that for the latter case I can partially reproduce some problems locally.

I can see quick fixes, but give me a few more hours and there's a decent chance everything finally untangles much more.

- Creates /api/deno-version endpoint configured for edge runtime - Reports Deno version, window object status, and window.location availability - Will help identify differences between local (Deno 2.2.4) and production environments - Related to investigation of 500 errors on dynamic routes (#538, #540)

Changes isServer detection from build-time constant to runtime check. Problem: - import.meta.env.SSR evaluates to false in edge functions - Bundler optimizes away !isServer guard as dead code - Code tries to access window.location.href in Netlify's Deno runtime - Netlify provides window object but window.location is undefined - Crash: "Cannot read properties of undefined (reading 'href')" Solution: - Use runtime check: typeof window === "undefined" || typeof window.location === "undefined" - Correctly identifies edge functions as server-side (isServer = true) - Prevents bundler from removing the guard - Works in Node.js, Netlify Edge (Deno 2.3.1), and browsers Also removes importRuntimeWithoutVite() workaround - no longer needed with runtime isServer check that works in all contexts. Related: #538, #540

Wituareard · 2025-11-15T15:02:35Z

Closing this PR was probably accidental @anthonybailey ?

Wituareard · 2025-11-15T15:37:18Z

It seems to work, not getting any errors on my side

Wituareard · 2025-11-15T16:19:29Z

@anthonybailey Do you think we can merge?

anthonybailey · 2025-11-15T16:25:01Z

I am just bringing the fix from main now. If I closed this it was in error.

Wituareard · 2025-11-15T16:34:01Z

I've already merged it

Pato-desu · 2025-11-18T13:38:22Z

ok, i'll move the task list left to the issue itself

Pato-desu added 2 commits November 6, 2025 20:40

readding page

5ae2682

filtering by only titled people

990a5e8

Pato-desu added 2 commits November 6, 2025 20:47

forgot defaultTitle

2772830

idk man

94157dd

Wituareard mentioned this pull request Nov 8, 2025

localizeHref can't run on edge functions runtime (Deno) #540

Closed

Pato-desu added 2 commits November 11, 2025 00:43

Switching to Members table. Filtering out duplicates

888be99

link changed for members table

080797d

fixing fields

43e273b

Trigger rebuild to test fresh edge function deployment

fb949da

Testing first-request behavior on cold start

anthonybailey mentioned this pull request Nov 12, 2025

Diagnose edge function Deno version #544

Closed

anthonybailey mentioned this pull request Nov 15, 2025

Fix Netlify edge function crash and remove importRuntimeWithoutVite workaround #548

Merged

anthonybailey closed this in #548 Nov 15, 2025

Wituareard reopened this Nov 15, 2025

Wituareard added 4 commits November 15, 2025 16:25

Merge branch 'main' into re-adding-people-page

3144011

Revert dummy edit

d29c11d

Move constant to config

66ac02b

Remove magic value

85c5c52

anthonybailey marked this pull request as ready for review November 15, 2025 16:54

anthonybailey merged commit 62f5714 into main Nov 15, 2025
5 checks passed

Uh oh!

Re-adding-people-page #538

Re-adding-people-page #538

Uh oh!

Conversation

Pato-desu commented Nov 6, 2025

Uh oh!

netlify bot commented Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for pauseai ready!

Uh oh!

Pato-desu commented Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Pato-desu commented Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Pato-desu commented Nov 7, 2025

Uh oh!

Pato-desu commented Nov 7, 2025

Uh oh!

joepio commented Nov 7, 2025

Uh oh!

Pato-desu commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anthonybailey commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Pato-desu commented Nov 7, 2025

Uh oh!

Wituareard commented Nov 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Wituareard commented Nov 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anthonybailey commented Nov 8, 2025

Uh oh!

Pato-desu commented Nov 11, 2025

Uh oh!

Wituareard commented Nov 12, 2025

Uh oh!

Pato-desu commented Nov 12, 2025

Uh oh!

anthonybailey commented Nov 12, 2025

Uh oh!

Pato-desu commented Nov 12, 2025

Uh oh!

anthonybailey commented Nov 12, 2025

Investigation Update: 500 Error on /people Route

Successfully Reproduced the Issue

Confirmed Pattern

Root Cause

Evidence

Why It Works Locally

Potential Solutions

Speculation

Uh oh!

anthonybailey commented Nov 12, 2025

Uh oh!

Wituareard commented Nov 15, 2025

Uh oh!

Wituareard commented Nov 15, 2025

Uh oh!

Wituareard commented Nov 15, 2025

Uh oh!

anthonybailey commented Nov 15, 2025

Uh oh!

Wituareard commented Nov 15, 2025

Uh oh!

Uh oh!

Pato-desu commented Nov 18, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

netlify bot commented Nov 6, 2025 •

edited

Loading

Pato-desu commented Nov 6, 2025 •

edited

Loading

Pato-desu commented Nov 6, 2025 •

edited

Loading

Pato-desu commented Nov 7, 2025 •

edited

Loading

anthonybailey commented Nov 7, 2025 •

edited

Loading

Wituareard commented Nov 8, 2025 •

edited

Loading

Wituareard commented Nov 8, 2025 •

edited

Loading

Investigation Update: 500 Error on `/people` Route