Skip to content

Comments

[pull] dev-next from reF1nd:dev-next#1

Open
pull[bot] wants to merge 418 commits intoridesnails:dev-nextfrom
reF1nd:dev-next
Open

[pull] dev-next from reF1nd:dev-next#1
pull[bot] wants to merge 418 commits intoridesnails:dev-nextfrom
reF1nd:dev-next

Conversation

@pull
Copy link

@pull pull bot commented Jul 23, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot locked and limited conversation to collaborators Jul 23, 2025
@pull pull bot added ⤵️ pull merge-conflict Resolve conflicts manually labels Jul 23, 2025
@reF1nd reF1nd force-pushed the dev-next branch 2 times, most recently from 371268f to 2dcb869 Compare August 4, 2025 06:51
@reF1nd reF1nd force-pushed the dev-next branch 6 times, most recently from d4fb2d7 to 178d426 Compare August 18, 2025 10:57
When bbolt encounters corrupted page data at runtime, it panics
instead of returning an error. Wrap all DB transactions with
recover to catch these panics, delete the corrupted database
file, and reopen a fresh one.
The cache deduplication in Client.Exchange uses a channel-based lock
per DNS question. Waiting goroutines blocked on <-cond without context
awareness, causing them to accumulate indefinitely when the owning
goroutine's transport call stalls. Add select on ctx.Done() so waiters
respect context cancellation and timeouts.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.