Skip to content

query-planning can't be None#10928

Merged
crusaderky merged 1 commit intodask:mainfrom
crusaderky:query_planning_none
Feb 16, 2024
Merged

query-planning can't be None#10928
crusaderky merged 1 commit intodask:mainfrom
crusaderky:query_planning_none

Conversation

@crusaderky
Copy link
Copy Markdown
Collaborator

Align parsing of the variable to the config schema, which states it must be strictly True or False. This looks like leftover code from a moment where it could be None?

@github-actions
Copy link
Copy Markdown
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

     15 files  ±0       15 suites  ±0   3h 20m 34s ⏱️ + 3m 25s
 13 040 tests ±0   12 108 ✅ ±0     931 💤 ±0  1 ❌ ±0 
161 287 runs  ±0  144 754 ✅ +3  16 532 💤  - 3  1 ❌ ±0 

For more details on these failures, see this check.

Results for commit 22564aa. ± Comparison against base commit 0ad38fc.

Copy link
Copy Markdown
Contributor

@milesgranger milesgranger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @crusaderky.

CI failure seems unrelated
:

FAILED dask/dataframe/tests/test_dataframe.py::test_ffill - ValueError: All NaN partition encountered in fillna. Try using df.repartition to increase the partition size, or specify limit in fillna.

@crusaderky crusaderky merged commit eca8e33 into dask:main Feb 16, 2024
@crusaderky crusaderky deleted the query_planning_none branch February 16, 2024 16:30
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.

2 participants