Skip to content

Add the fetch timeout and node expansion limit to the Default Connection - #2611

Open
kmcginnes wants to merge 1 commit into
t3/typescript-startup-stack-6-iam-settingfrom
t3/typescript-startup-stack-7-fetch-timeout-expansion-limit
Open

kmcginnes wants to merge 1 commit into
t3/typescript-startup-stack-6-iam-settingfrom
t3/typescript-startup-stack-7-fetch-timeout-expansion-limit

Conversation

@kmcginnes

@kmcginnes kmcginnes commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT were documented but never reached the Default Connection. They now do, from -e flags or config.json.

A value that isn't a positive whole number is left out with a warning.

Upgrade notes

  • GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT, from -e flags or config.json, now reach the default connection.

Evidence

Before: /defaultConnection left both settings out.
After: the scenario rows that set them expect both in the /defaultConnection body, and rows with invalid values expect the warning.

Merge Danger

Door: two-way

Impact: a deployment that already sets either value now gets it applied.

Related


🤖 Written by an AI agent on my behalf.

@kmcginnes
kmcginnes added this pull request to stack #2613 November 13, 2026 23:39

This branch has not been deployed

No deployments
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.

Default Connection ignores GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT

1 participant