From 899705db034ca64375b3617412b9e2a51d139052 Mon Sep 17 00:00:00 2001 From: Yuriy Andamasov Date: Sun, 10 May 2026 23:19:46 +0300 Subject: ci: add connect-timeout and max-time to Context7 curl call MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Without explicit timeouts, a stalled TCP handshake or slow server response blocks the workflow indefinitely. --connect-timeout 10 bounds the TCP/connect phase; --max-time 60 caps total request duration. Both are within reasonable limits for a refresh POST that normally completes in well under a second. 🤖 Generated by [robots](https://vyos.io) --- .github/workflows/context7-refresh.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to '.github') diff --git a/.github/workflows/context7-refresh.yml b/.github/workflows/context7-refresh.yml index 9489b55e..e7910671 100644 --- a/.github/workflows/context7-refresh.yml +++ b/.github/workflows/context7-refresh.yml @@ -66,7 +66,11 @@ jobs: esac fi echo "Refreshing Context7 variant: $VARIANT" - curl -fsSL --retry 2 --retry-delay 10 -X POST \ + curl -fsSL \ + --connect-timeout 10 \ + --max-time 60 \ + --retry 2 --retry-delay 10 \ + -X POST \ "https://context7.com/api/v1/refresh" \ -H "Authorization: Bearer $CONTEXT7_API_KEY" \ -H "Content-Type: application/json" \ -- cgit v1.2.3