Fix a typo in the shared-nothing blueprint - #2526
Merged
Merged
Conversation
"two machine" should be "two machines". Also serves to retrigger the build for this page, whose HTML is still serving the pre-merge figures from #2525 while its Markdown twin and the other two pages from that commit are correct.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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
1 participant
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.
I have two machine running a log servershould betwo machines.The real reason for the change is to retrigger a build for this page. Its HTML is still serving the pre-merge figures from #2525, which merged at 20:16 UTC: the volume line reads $1.35 and the total $61.39, where the merged file says $4.35 and $74.39.
It is not a build failure. The Markdown twin at
blueprints/shared-nothing.mdalready serves the new figures, the file onmainis correct, and the other two pages from that same commit,about/cost-managementandelixir/getting-started/migrate-from-heroku, are both live with their new numbers.It looks like a stale CDN object. The page and
about/cost-managementboth returncf-cache-status: HITwith an identicalage, so both were cached at the same moment, around the merge, when this page had not yet rebuilt and the other had. Query strings do not bust it, so the cache key ignores them, and aCache-Control: no-cacherequest header does not help either. The response also carriescache-control: no-store, no-cache, must-revalidate, max-age=0, which an object with a 14 minute age and an unchanged etag should not have survived.So this may not work. If the stale copy outlives a fresh build, the cache is holding it independently of the origin and it is one for Mintlify rather than something fixable from this repo. The typo is worth fixing either way.
two machinesalso gives a marker to check against: the live HTML currently readstwo machine, so once it readstwo machinesthe new render has landed and the figures can be rechecked at the same time.