You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Default Connection ignores GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT #2291
The configuration reference documents GRAPH_EXP_FETCH_REQUEST_TIMEOUT and GRAPH_EXP_NODE_EXPANSION_LIMIT as Default Connection settings you can pass with --env or in config.json, and uses both in its examples. Setting either one has no effect.
process-environment.sh builds defaultConnection.json from a fixed list of keys (GRAPH_EXP_CONNECTION_URL, GRAPH_EXP_GRAPH_TYPE, GRAPH_EXP_SERVICE_TYPE, GRAPH_EXP_IAM, GRAPH_EXP_AWS_REGION, and GRAPH_EXP_USING_PROXY_SERVER on the unified image) and never reads or writes these two. The client's DefaultConnectionDataSchema in packages/graph-explorer/src/core/defaultConnection.ts accepts both keys and maps them to fetchTimeoutMs and nodeExpansionLimit, but since the file never contains them, the Default Connection always falls back to the 240000 ms timeout and no expansion limit.
The docs date from #1572. The script has had the same gap since before the unified image work.
Environment
OS: any (Docker image)
Browser: any
Graph Explorer Version: current main
Graph Database & Version: any
Steps to Reproduce
Run the image with --env GRAPH_CONNECTION_URL=<db> --env GRAPH_EXP_FETCH_REQUEST_TIMEOUT=10000 --env GRAPH_EXP_NODE_EXPANSION_LIMIT=50, or put the same keys in config.json.
Inspect the generated defaultConnection.json in the container, or open the Default Connection in the UI.
Neither value is present. The connection uses the 240000 ms default and has no expansion limit.
Expected Behavior
Either the Default Connection picks up both values from --env and config.json, or the configuration reference stops listing them.
Two ways to resolve it:
Have process-environment.sh read both from config.json and the environment and write them into defaultConnection.json, with a startup scenario test for each.
Drop both from the variable list and the two examples in docs/references/configuration.md.
Related Issues
Related: #1670 (replace the shell scripts with TypeScript), #1674 (dynamic /defaultConnection route handler)
Important
Internal only — this issue is maintained by the core team and is not accepting external contributions.
Activity
Correct drifted configuration, logging, and Gremlin Server docs (#2393)