On 1/24/22 3:26 PM, Amos Jeffries wrote: > On 21/01/22 08:20, Alex Rousskov wrote: >> On 1/18/22 5:31 AM, Amos Jeffries wrote: >>> The following changes accepted into v6 are also eligible for v5 but have >>> issues preventing me scheduling them. >>> >>> >>> This has conflicts I need some assistance resolving. So will not being >>> doing the backport myself. If you are interested please open a PR >>> against v5 branch for the working backport before Feb 1st. >>> >>> * Bug #5090: Must(!request->pinnedConnection()) violation (#930) >>> squid-6-15bde30c33e47a72650ef17766719a5fc7abee4c >> >> The above fix relies on a Bug #5055 fix (i.e. master/v6 commit 2b6b1bc >> mentioned below as a special case). >> > > Okay. I will try again for a later release. >> >>> * Bug #5055: FATAL FwdState::noteDestinationsEnd exception: opening >>> (#877) >>> squid-6-2b6b1bcb8650095c99a1916f5964305484af7ef0 >> >> Waiting for a base commit SHA from you. >> >> >>> and; Fix FATAL ServiceRep::putConnection exception: theBusyConns > 0 >>> (#939) >>> squid-6-a8ac892bab446ac11f816edec53306256bad4de7 >> >> This fixes a bug in the Bug #5055 fix AFAICT, so waiting on the >> master/v6 commit 2b6b1bc backport (i.e. the previous bullet).
> FYI; As of right now the v5 HEAD should be fine to base the PR on. Please see https://github.com/squid-cache/squid/pull/967 I will leave it as a Draft PR until I have a chance to run more tests. Please test what you can as well. HTH, Alex. _______________________________________________ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
