Skip to content

fix(ferndesk): timeouts + progress logs after CF 1010 fix - #12

Merged
echobt merged 1 commit into
mainfrom
fix/cor-444-ferndesk-timeouts-progress
Sep 14, 2026
Merged

echobt merged 1 commit into
mainfrom
fix/cor-444-ferndesk-timeouts-progress

Conversation

@echobt

@echobt echobt commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #11 / COR-444: curl_cffi Chrome impersonation cleared Error 1010, but run 34887933260 sat ~34m after discovered 99 with no logs, then rate/limit 502. Bound curl_cffi timeouts to (15, 60) and add list_all progress logs.

Note

FernDesk UI still needs Connect domain for docs.cortex.foundation HTTPS (separate from api CF 1010).

Test plan

  • Merge and gh workflow run FernDesk sync
  • Confirm no 1010; see list_all progress in logs; reach SUMMARY

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.
@mintlify

mintlify Bot commented Sep 14, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
cortex-foundation-add13747 🔴 Failed Sep 14, 2026, 8:29 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@echobt
echobt merged commit 63a7f7c into main Sep 14, 2026
3 of 4 checks passed
@echobt
echobt deleted the fix/cor-444-ferndesk-timeouts-progress branch September 14, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants