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
Commit f431e28
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/workflows/release.yaml
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -40,9 +40,13 @@ jobs:
40
40
- name: Set up Python
41
41
uses: actions/setup-python@v7
42
42
with:
43
-
python-version: '3.10'
43
+
# 3.13.17+ bundles pip 26.2.2+, which no longer trusts the compromised eMudhra/emSign root CA.
44
+
python-version: '3.13'
44
45
- name: Install uv
45
46
uses: astral-sh/setup-uv@v7
47
+
- name: Check pip includes the eMudhra/emSign CA removal
48
+
run: |
49
+
python -c "import sys, pip; v = tuple(int(p) for p in pip.__version__.split('.')[:3]); sys.exit(0 if v >= (26, 2, 2) else f'pip {pip.__version__} predates the eMudhra/emSign CA removal; need >= 26.2.2')"
pytest -n auto -m "fast and not cicdonly and not isolated" --junitxml=test-results/junit-fast-test.xml && pytest -m "isolated and not slow"&& pytest -m "registry_isolation"&& pytest -m "dialect_isolated"
136
+
pytest -n auto -m "fast and not cicdonly and not isolated" --junitxml=test-results/junit-fast-test.xml && pytest -m "isolated and not slow and not fork_isolated"&& pytest tests/test_forking.py::test_parallel_load -m "isolated and fork_isolated and not slow"&& pytest tests/test_forking.py::test_parallel_load_multi_repo -m "isolated and fork_isolated and not slow"&& pytest -m "registry_isolation"&& pytest -m "dialect_isolated"
136
137
137
138
slow-test:
138
-
pytest -n auto -m "(fast or slow) and not cicdonly and not isolated"&& pytest -m "isolated"&& pytest -m "registry_isolation"&& pytest -m "dialect_isolated"
139
+
pytest -n auto -m "(fast or slow) and not cicdonly and not isolated"&& pytest -m "isolated and not fork_isolated"&& pytest tests/test_forking.py::test_parallel_load -m "isolated and fork_isolated"&& pytest tests/test_forking.py::test_parallel_load_multi_repo -m "isolated and fork_isolated"&& pytest -m "registry_isolation"&& pytest -m "dialect_isolated"
139
140
140
141
cicd-test:
141
-
pytest -n auto -m "(fast or slow) and not pyspark and not isolated" --junitxml=test-results/junit-cicd.xml && pytest -m "pyspark"&& pytest -m "isolated and not pyspark"&& pytest -m "registry_isolation"&& pytest -m "dialect_isolated"
142
+
pytest -n auto -m "(fast or slow) and not pyspark and not isolated" --junitxml=test-results/junit-cicd.xml && pytest -m "pyspark"&& pytest -m "isolated and not pyspark and not fork_isolated"&& pytest tests/test_forking.py::test_parallel_load -m "isolated and not pyspark and fork_isolated"&& pytest tests/test_forking.py::test_parallel_load_multi_repo -m "isolated and not pyspark and fork_isolated"&& pytest -m "registry_isolation"&& pytest -m "dialect_isolated"
142
143
143
144
core-fast-test:
144
145
pytest -n auto -m "fast and not web and not github and not dbt and not jupyter"
Copy file name to clipboardExpand all lines: docs/guides/configuration.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1213,10 +1213,12 @@ Example configuration:
1213
1213
1214
1214
#### Default connections/scheduler
1215
1215
1216
-
The `default_connection`, `default_test_connection`, and `default_scheduler` keys are used to specify shared defaults across multiple gateways.
1216
+
The `default_connection`, `default_test_connection`, and `default_scheduler` keys specify a connection or scheduler for gateways that do not define their own.
1217
1217
1218
1218
For example, you might have a specific connection where your tests should run regardless of which gateway is being used. Instead of duplicating the test connection information in each gateway specification, specify it once in the `default_test_connection` key.
1219
1219
1220
+
A default is only used when a gateway omits the corresponding key entirely. If a gateway specifies its own `connection`, `test_connection`, or `scheduler`, SQLMesh uses that configuration as written and ignores the default. Fields are not merged, so a gateway connection cannot inherit individual fields such as `type` from `default_connection`. Each gateway connection must be a complete connection configuration.
1221
+
1220
1222
Example configuration specifying a Postgres default connection, in-memory DuckDB default test connection, and builtin default scheduler:
0 commit comments