hensei-web/app/p/[party]/PartyPageClient.tsx
Justin Edmund 426645813e
Fix intermittent crash: bounded caching + HTTP timeouts/keepAlive + preview route dedupe (#428)
## Summary
- Fixes periodic production crashes (undici ECONNREFUSED ::1) by
bounding server cache size/lifetime and hardening server HTTP client.

### Root cause
- React server cache (cache(...)) held axios responses indefinitely
across many parameter combinations, causing slow memory growth until the
Next.js app router worker was OOM-killed. The main server then failed
IPC to the worker (ECONNREFUSED ::1:<port>).

### Changes
- `app/lib/data.ts`: Replace unbounded cache(...) with unstable_cache
and explicit keys; TTLs: 60s for teams/detail/favorites/user, 300s for
meta (jobs/skills/accessories/raids/version).
- `app/lib/api-utils.ts`: Add shared Axios instance with 15s timeout and
keepAlive http/https agents; apply to GET/POST/PUT/DELETE helpers.
- `pages/api/preview/[shortcode].ts`: Remove duplicate handler to dedupe
route; retain the .tsx variant using `NEXT_PUBLIC_SIERO_API_URL`.

### Notes
- Build currently has pre-existing app/pages route duplication errors;
out of scope here but unrelated to this fix.
- Ensure `NEXT_PUBLIC_SIERO_API_URL` and `NEXT_PUBLIC_SIERO_OAUTH_URL`
are set on Railway.

### Risk/impact
- Low risk; behavior is unchanged aside from bounded caching and
resilient HTTP.
- Cache TTLs can be tuned later if needed.

### Test plan
- Verify saved/teams/user pages load and revalidate after TTL.
- Validate API routes still proxy correctly; timeouts occur after ~15s
for hung upstreams.
- Monitor memory over several days; expect stable usage without steady
growth.
2025-08-31 12:16:42 -07:00

95 lines
No EOL
2.1 KiB
TypeScript

'use client'
import React, { useEffect } from 'react'
import { useTranslation } from 'next-i18next'
import { useRouter } from 'next/navigation'
// Utils
import { appState } from '~/utils/appState'
// Components
import Party from '~/components/party/Party'
import PartyFooter from '~/components/party/PartyFooter'
import ErrorSection from '~/components/ErrorSection'
interface Props {
party: any; // Replace with proper Party type
raidGroups: any[]; // Replace with proper RaidGroup type
}
const PartyPageClient: React.FC<Props> = ({ party, raidGroups }) => {
const router = useRouter()
const { t } = useTranslation('common')
// Initialize app state
useEffect(() => {
if (party) {
appState.parties[0] = party
appState.raidGroups = raidGroups
}
}, [party, raidGroups])
// Handle remix action
async function handleRemix() {
if (!party || !party.shortcode) return
try {
const response = await fetch(`/api/parties/${party.shortcode}/remix`, {
method: 'POST',
headers: {
'Content-Type': 'application/json'
}
})
const data = await response.json()
if (data && data.shortcode) {
// Navigate to the new remixed party
router.push(`/p/${data.shortcode}`)
}
} catch (error) {
console.error('Error remixing party', error)
}
}
// Handle deletion action
async function handleDelete() {
if (!party || !party.shortcode) return
try {
await fetch(`/api/parties/${party.shortcode}`, {
method: 'DELETE'
})
// Navigate to teams page after deletion
router.push('/teams')
} catch (error) {
console.error('Error deleting party', error)
}
}
// Error case
if (!party) {
return (
<ErrorSection
status={{
code: 404,
text: 'not_found'
}}
/>
)
}
return (
<>
<Party
party={party}
onRemix={handleRemix}
onDelete={handleDelete}
/>
<PartyFooter party={party} />
</>
)
}
export default PartyPageClient