Skip to content

Set up dispatch sources after external write.#148

Merged
stephencelis merged 3 commits intomainfrom
external-write-fix
Apr 11, 2025
Merged

Set up dispatch sources after external write.#148
stephencelis merged 3 commits intomainfrom
external-write-fix

Conversation

@mbrandonw
Copy link
Member

Fixes #147.

In #129 we made a change to support atomic writes of the file in fileStorage. We made the assumption that if a file is deleted but the file exists (as is the case for atomic writes since they are a write+move), then we don't need to recreate the dispatch source. That worked well when the write was internally performed, but if someone atomically writes to the file it causes us to not re-setup the dispatch source. Now we always set up the dispatch source after a write.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

@stephencelis stephencelis merged commit 2c41085 into main Apr 11, 2025
6 checks passed
@stephencelis stephencelis deleted the external-write-fix branch April 11, 2025 18:23
mhayes853 pushed a commit to mhayes853/swift-sharing that referenced this pull request Aug 12, 2025
* Set up dispatch sources after external write.

* fix

* fix
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.

Unable to detect changes to FileStorageKey from external processes

4 participants