Problemsby IbisTrouble with GitHub page
Dev tooling4 posts from 4 people4d active+00 posts in the last 7 days, 0 the 7 days before (fading)
Posts per day
The posts behind it
4, newest first[FEATURE] Docs: Ned Watch observability page (deadman and overrun monitoring for crews)### Feature Area Documentation ### Is your feature request related to a an existing bug? Please link it here. NA ### Describe the solution you'd like An observability page for Ned Watch under `docs/en/observability/` (with `ar`, `ko` and `pt-BR` copies for parity, and the...crewAIInc/crewAI · ned-mindOpen ↗Prefetched optional catch-all index page is rendered for sibling URLs### Link to the code that reproduces this issue https://github.com/nickolaj-jepsen/next-catchall-varyparams-repro ### To Reproduce Via repro script: 1. npm install && npx playwright install chromium 2. npm run repro (builds, runs next start, then check.mjs) Or by hand: 1. npm...vercel/next.js · nickolaj-jepsenOpen ↗Soft navigation into a nested layout scrolls past the new layout to the page...will scroll to the top of the first Page element"), and do not mention nested layouts. Workaround: render an absolutely positioned marker at the top of the document as the page's first element, so it becomes the scroll target.vercel/next.js · stefanprobstOpen ↗allowedDevOrigins causes a hydration mismatch (display:contents metadata boundary) on every full page load...affected? next dev (local) ### Additional context `allowedDevOrigins` is the documented workaround for a Windows-specific dev annoyance where `localhost` intermittently resolves to `::1` while the Turbopack dev server only listens on IPv4, making `http://localhost:3000` fail to...vercel/next.js · gpalavecino-gotoxy4 repliesOpen ↗
Companies and products named
About this problem
Evidence
4 posts from 4 people in 2 places, about 1 a week over 24 days. Mostly on vercel/next.js, crewAIInc/crewAI. Tools named alongside: Vercel, npm, PyPI, CrewAI.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about GitHub with no known issue, sharing the word "page". First post Sep 13, 2026, latest Oct 6, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other GitHub problems
Trouble with GitHub terminalTrouble with GitHub nextGitHub dependency conflicts break installsTrouble with GitHub checkGitHub outages and slowdowns disrupt workMigrating to or off GitHub is slow and riskyGitHub rate limits and usage caps block workRAG on GitHub returns irrelevant or missing contextTrouble with GitHub testGitHub lock-in makes switching costlyTrouble with GitHub proxyGitHub vulnerabilities are hard to triage and patch
History
steady to fading
unverified to corroborated
new to steady
Trouble with GitHub page (1 post)