Skip to content

Conversation

@IanButterworth
Copy link
Member

Fixes #1221

I believe this is part of #1238 which has stalled, so this just tackles not corrupting the config file.

@IanButterworth IanButterworth requested a review from Keno October 28, 2025 14:11
@IanButterworth
Copy link
Member Author

Getting reviews here is pretty hard, but I think this is important to do, so I'm going to go ahead. Reviewers, please post merge review.

@IanButterworth IanButterworth merged commit cd9c7fc into main Oct 29, 2025
29 checks passed
@IanButterworth IanButterworth deleted the ib/atomic_config_write branch October 29, 2025 15:22
@davidanthoff
Copy link
Collaborator

This is great to see!

I think this all looks good, I'm just wondering whether we actually need to keep the config files open at all, given that we have the separate lock file? I think we might be able to move to a world where on read of the config file we just 1) open file, 2) read data, 3) close file handle right away. That would make the whole write story easier on Windows, right?

I think (but don't have a good memory of it) that I kept the files open originally before I added the lock file story... Maybe... Probably worth thinking through a bit more, but it could potentially simplify things, right?

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.

juliaup destroyed config file when running out of disk quota

2 participants