# HG changeset patch
# User Yugo Horie
# Date 1696144340 -32400
# Sun Oct 01 16:12:20 2023 +0900
# Node ID f8f6290d60615a4dfe2d8b26246891228f19aa5d
# Parent 3db945fda515014d220151046d02f3960bcfca0a
Fixed stucking cache status into UPDATING.
Fixed issue-2162's stucking cache status to
introd
Hi, I had a same issue in those days.
Did you try the proxy_cache_lock_timeout?
https://forum.nginx.org/read.php?2,276344,276349#msg-276349
But the below article said if you reduce simply the once busy loop time, it
may not resolve this problem for which based on the nginx event
notification mech
Hello.
The upstream peer status is always up when the upstream peer is single.
FYI: https://github.com/vozlt/nginx-module-vts/issues/262
The conventional upstream round robin hasn't count peer->fails anywhere
when it is peers->single is 1.
Thus we’d like to only count it, but not to judge that the
Hi, sorry for bothering you.
It looks good to me. Thanks!
—
Yugo Horie
On Thu, Mar 2, 2023 at 8:51 Maxim Dounin wrote:
> Hello!
>
> On Thu, Feb 23, 2023 at 09:24:52AM +0900, u5h wrote:
>
> > Thanks reviewing!
> >
> > I agree with your early return strate
(u >= 0xf8) {
+
+(*p)++;
+return 0x;
+
+} else if (u >= 0xf0) {
u &= 0x07;
valid = 0x;
On Thu, Feb 23, 2023 at 6:41 Maxim Dounin wrote:
> Hello!
>
> On Thu, Feb 23, 2023 at 12:10:27AM +0900, u5h wrote:
>
> > # HG
# HG changeset patch
# User Yugo Horie
# Date 167705 -32400
# Wed Feb 22 23:56:15 2023 +0900
# Node ID 1a9487706c6af90baf2ed770db29f689c3850721
# Parent cffaf3f2eec8fd33605c2a37814f5ffc30371989
core: return error when the first byte is above 0xf5 in utf-8
* see https://datatracker.ietf.
