Repository navigation
Add the fetch timeout and node expansion limit to the Default Connection - #2611
Open
kmcginnes wants to merge 1 commit into
Conversation
Layer: 7-fetch-timeout-expansion-limit
This branch has not been 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
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
GRAPH_EXP_FETCH_REQUEST_TIMEOUTandGRAPH_EXP_NODE_EXPANSION_LIMITwere documented but never reached the Default Connection. They now do, from-eflags orconfig.json.A value that isn't a positive whole number is left out with a warning.
Upgrade notes
GRAPH_EXP_FETCH_REQUEST_TIMEOUTandGRAPH_EXP_NODE_EXPANSION_LIMIT, from-eflags orconfig.json, now reach the default connection.Evidence
Before:
/defaultConnectionleft both settings out.After: the scenario rows that set them expect both in the
/defaultConnectionbody, 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.