fix/dev: Fix Orb setup to avoid false cold-start failure - #1877
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
marcleblanc2
changed the title
marcleblanc2
changed the title
marcleblanc2
changed the title
marcleblanc2
enabled auto-merge (squash)
September 10, 2026 00:33
valerybugakov
approved these changes
Sep 11, 2026
…d-start failure next dev opens its port immediately, but contentlayer generation plus the first-page compile take ~30s, longer than Amp's fixed 10s readiness window. With health: / every fresh orb printed NOT RESPONDING even though the site came up fine. Port-open readiness reports success as soon as the dev server listens; the browser waits for the first compile instead. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a07e6b-4d78-7569-bb05-289a9c52ec9f
marcleblanc2
force-pushed
the
orb/drop-docs-health-check
branch
from
September 11, 2026 00:51
da63fc8 to
c063625
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
amp orb services ensureprinteddocs: NOT RESPONDING (readiness check timed out after 10000ms)on every fresh orb, even though the site came up fine ~30s later.next devopens its port immediately, but contentlayer generation (521 docs) plus the first-page compile exceed Amp's fixed 10s readiness window, and.amp/services.yamlhas no configurable timeout.Change
Remove
health: /from.amp/services.yaml. Amp now treats the service as ready when the port accepts a connection, whichnext devdoes within a couple of seconds. The browser waits for the first compile instead ofensurereporting a false failure.Tradeoff:
ensurenow proves the server is listening, not that a page rendered. A build error shows up in the browser oramp orb service logs docsinstead.Verified
In an orb:
ensurenow reportsdocs: started, port 31414, listeningin ~8s, and the portal URL returns 200 for/and/cody.Amp threads