fix(ferndesk): timeouts + progress logs after CF 1010 fix - #12
Merged
Merged
Conversation
After CF 1010 bypass, GHA sync hung ~34m before a 502 with no logs (article/section listing). Use explicit (connect, read) timeouts and emit list_all page progress so runs fail/retry visibly instead of appearing stuck.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
3 tasks
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
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.
Summary
Follow-up to #11 / COR-444: curl_cffi Chrome impersonation cleared Error 1010, but run 34887933260 sat ~34m after
discovered 99with no logs, thenrate/limit 502. Bound curl_cffi timeouts to(15, 60)and addlist_allprogress logs.Note
FernDesk UI still needs Connect domain for
docs.cortex.foundationHTTPS (separate from api CF 1010).Test plan
gh workflow runFernDesk synclist_allprogress in logs; reach SUMMARY