On 4/17/23 14:52, Dr.X wrote:
Could you please explain why the developers are upgrading Squid from
version 4 to 5 and 6, while ignoring a critical built-in feature like
Delay Pools that has been reported as a bug since Squid 4.x?
Modern Squids are released on a fixed schedule[1], regardless of how
many old bugs are left in the code.
[1] https://wiki.squid-cache.org/ReleaseSchedule
FWIW, we have tried several other approaches, but they were all proven
to be even more problematic. For example, the natural "let's fix all
critical bugs before declaring a new version STABLE" approach (which we
also tried), leads to many problems in Squid environment, including these:
* The development version can "never" be honestly declared stable
because nobody volunteers to fix all critical bugs. Please note that we
cannot force developers to fix bugs -- there are no Squid Project
employees to order around.
* Some critical bug fixes are delayed forever because they require
changes deemed too disruptive to be done when the official development
branch code finally appears to be close of becoming stable -- working
well in known/important/supported environments.
* Since a stable declaration is always pushed back, the number of folks
interested in testing the development version goes down. With that
decrease, the number of critical bugs discovered/reported decreases as
well. As a result, if we do mark a release as stable, we are then
flooded with new critical bug reports (for a now "stable" version!).
* Persistent fights about bug classification consume a lot of developer
time and nerve cells. A broken feature deemed critical by one relatively
reasonable person may be treated as dead code that should be removed by
another reasonable person!
* The stable version is so old that it is effectively unusable in many
modern environments because it lacks essential features for those
environments. Those features cannot be added to that stable version
because doing so may disrupt its stability.
* The stable version effectively becomes unstable in many environments
because nobody volunteers to fix its bugs because most developers are
running or supporting some other code snapshot (that works for them or
their customers).
The Squid Project has decided that a fixed schedule of releases has a
potential to be an overall better approach. FWIW, I agree with that
decision. We all know that it will not fix all the problems.
Antony Stone has mentioned many good general reasons why some bugs take
longer to fix than others, especially in an open source project. My
response does not contradict that useful information. I was just trying
to provide an answer that is a bit closer to your specific question...
HTH,
Alex.
*From: *Dr.X <0xff1f@xxxxxxxxx>
*Date: *Tuesday, 11 April 2023 05:33
*To: *Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>,
squid-users@xxxxxxxxxxxxxxxxxxxxx <squid-users@xxxxxxxxxxxxxxxxxxxxx>
*Cc: *Dave Blanchard <dave@xxxxxxxxxxx>
*Subject: *Re: Is there any squid 4.x tested with Delay
pools to work and limit well ?
Ok nice , we will stick with squid 3.x then 😊
Thanks
*From: *Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>
*Date: *Tuesday, 11 April 2023 05:31
*To: *squid-users@xxxxxxxxxxxxxxxxxxxxx <squid-users@xxxxxxxxxxxxxxxxxxxxx>
*Cc: *Dave Blanchard <dave@xxxxxxxxxxx>, Dr.X <0xff1f@xxxxxxxxx>
*Subject: *Re: Is there any squid 4.x tested with Delay
pools to work and limit well ?
On 4/10/23 20:42, Dr.X wrote:
Is it solved in squid 6.x ?
I do not think so. AFAIK, Bug 4913 (Delay Pools don't work for Tunneled
traffic) affects all Squid versions starting with v4 (at least). IIRC,
there were some code improvements in that area, as side effects of other
projects, but nobody has worked on an actual fix yet.
Alex.
*From: *Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>
*Date: *Tuesday, 11 April 2023 03:24
*To: *squid-users@xxxxxxxxxxxxxxxxxxxxx <squid-users@xxxxxxxxxxxxxxxxxxxxx>
*Cc: *Dave Blanchard <dave@xxxxxxxxxxx>, Dr.X <0xff1f@xxxxxxxxx>
*Subject: *Re: Is there any squid 4.x tested with Delay
pools to work and limit well ?
On 4/10/23 18:41, Dr.X wrote:
So do you think we will have squid 4.x to be fixed soon or latter ?
Squid v4 receives very little attention these days. FWIW, I am not aware
of anybody working on Bug 4913 (Delay Pools don't work for Tunneled
traffic) right now (for any Squid version).
https://wiki.squid-cache.org/SquidFaq/AboutSquid#how-to-add-a-new-squid-feature-enhance-of-fix-something
Alex.
*From: *Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>
*Date: *Monday, 10 April 2023 04:31
*To: *squid-users@xxxxxxxxxxxxxxxxxxxxx <squid-users@xxxxxxxxxxxxxxxxxxxxx>
*Cc: *Dr.X <0xff1f@xxxxxxxxx>, Dave Blanchard <dave@xxxxxxxxxxx>
*Subject: *Re: Is there any squid 4.x tested with Delay
pools to work and limit well ?
On 4/8/23 15:35, Dave Blanchard wrote:
On Sat, 8 Apr 2023 16:40:02 +0000
Dr.X <0xff1f@xxxxxxxxx> wrote:
I was wondering if you have a Squid 4.x version that supports delay
pools and is not buggy. I asked Alex, the developer, and he
informed me that none of the 4.x versions support it. I also
reached out to Amos but haven't received a response yet.
I'm interested in this also, as I've just tried setting up delay
pools on 5.4 and so far haven't managed to make it work as expected.
I would like to clarify delay pools support status, again: For some
traffic, some delay pools configurations are probably working OK in
Squid v4+. The Squid bug Dr.X has been referring to above (and in other
recent squid-user emails) is Bug 4913 (Delay Pools don't work for
Tunneled traffic):
* https://bugs.squid-cache.org/show_bug.cgi?id=4913
* http://lists.squid-cache.org/pipermail/squid-users/2022-June/024922.html
* http://lists.squid-cache.org/pipermail/squid-users/2023-April/025725.html
HTH,
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
