Hi Firxiao, it seems the issues you mentioned[0][1] doesn't have a definitive answer if it solves the problem. Would you be willing to help test out any changes?
Ideally we would cherry-pick the upstream changes, but at a very cursory glance it seems a decent chunk of code was changed, so merge conflicts could be likely. This is the route we would go first before upgrading the version, but perhaps it could be time to do a minor release update. This would require some review of the changes in 1.13.1 -> 1.13.2 to ensure no feature regressions occur. I'm not saying this is the case, but just stating it's not something that will instantly happen. [0] - https://github.com/NLnetLabs/unbound/issues/439 [1] - https://github.com/NLnetLabs/unbound/issues/411 ** Bug watch added: github.com/NLnetLabs/unbound/issues #439 https://github.com/NLnetLabs/unbound/issues/439 ** Bug watch added: github.com/NLnetLabs/unbound/issues #411 https://github.com/NLnetLabs/unbound/issues/411 ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080494 Title: Hang in Unbound 1.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2080494/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
