Skip to content

Add pruning default dask configs before serialization#467

Merged
jacobtomlinson merged 2 commits intodask:mainfrom
dshkliarenko:prune-defaults-for-serialization
Jul 7, 2025
Merged

Add pruning default dask configs before serialization#467
jacobtomlinson merged 2 commits intodask:mainfrom
dshkliarenko:prune-defaults-for-serialization

Conversation

@dshkliarenko
Copy link
Contributor

Hi, this solves the issue (#249). Thanks.

Copy link
Member

@jacobtomlinson jacobtomlinson left a comment

Choose a reason for hiding this comment

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

Thanks for picking up a 4 year old issue, this is awesome.

Could I ask you to write some tests for it?

@dshkliarenko
Copy link
Contributor Author

@jacobtomlinson I had to make some refactoring so that it could be covered with tests properly.

Also, there is a caveat regarding the solution: it only works when security set to False, otherwise user data still is over limit because of serialized certificates.

@jacobtomlinson
Copy link
Member

Yeah this is a known issue. I don't think this PR actually loses #249 because most people want security=True. But it certainly help!

@jacobtomlinson jacobtomlinson merged commit eebe726 into dask:main Jul 7, 2025
6 of 7 checks passed
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