Skip to content

Complete duplicate background fetch handlers#635

Open
caydyan wants to merge 1 commit into
stakwork:masterfrom
caydyan:codex/background-fetch-completion-162
Open

Complete duplicate background fetch handlers#635
caydyan wants to merge 1 commit into
stakwork:masterfrom
caydyan:codex/background-fetch-completion-162

Conversation

@caydyan

@caydyan caydyan commented Jun 14, 2026

Copy link
Copy Markdown

Summary

  • complete duplicate silent-push fetch handlers immediately with .noData when another background fetch is already running
  • keep the active background fetch completion handler intact so the in-flight task can finish normally

Validation

  • git diff --check
  • xcrun swiftc -parse sphinx/Crypter/SphinxOnionManager.swift

Closes #162.

BTC payout address: bc1qev5ant33v5y89qqjvcf4mh9hlax5svqf5xd7gc

@caydyan caydyan changed the base branch from master to develop June 14, 2026 13:31
@caydyan caydyan changed the base branch from develop to master June 14, 2026 18:31
@caydyan

caydyan commented Jun 14, 2026

Copy link
Copy Markdown
Author

Current-head validation rerun on 144c5432a69c233c0a6dfcacea3dcb8dc28b544a after correcting the PR base back to master:

  • PR diff is now scoped to sphinx/Crypter/SphinxOnionManager.swift only (1 file changed, 1 insertion, 2 deletions).
  • git diff --check origin/master...HEAD passed.
  • xcrun swiftc -parse sphinx/Crypter/SphinxOnionManager.swift passed.

I checked the previously requested develop base, but that branch is stale and does not contain the background-fetch code touched here; using it made GitHub show a 485-file PR diff from unrelated upstream master changes. The code change itself remains the same single-file duplicate-completion 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.

Improves messages background fetch

1 participant