- 29 Aug, 2019 1 commit
-
-
Geoff Simmons authored
This necessitates adding the matchonly() method to the vre2set interface, which only checks for matches, and does not save the indices of matching elements. It also requires a length parameter (since headers in struct http are not null-terminated). It also requires the return of the configure-time check for whether the RE2::Set::Match() method can be called with a NULL vector for the indices.
-
- 23 Aug, 2019 1 commit
-
-
Geoff Simmons authored
Also update set.saved(), to enable checking if an integer was saved.
-
- 22 Aug, 2019 1 commit
-
-
Geoff Simmons authored
-
- 25 Jun, 2019 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
re2 no longer does that since commit 848dfb7e1d7ba641d598cb66f81590f3999a555a.
-
- 16 Apr, 2019 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 15 Apr, 2019 1 commit
-
-
Nils Goroll authored
-
- 07 Apr, 2019 1 commit
-
-
Nils Goroll authored
This should hopefully fix a panic which has to be caused by forgotten WS_Release() calls and which occurred close to VCL code which handles re2 sets. Redacted panic: Panic at: Fri, 05 Apr 2019 19:15:24 GMT Assert error in WS_Reserve(), cache/cache_ws.c line 236: Condition(ws->r == NULL) not true. version = varnish-trunk revision af2bad23deb2470533158f9d99ad3f4968b8d231, vrt api = 9.0 ident = Linux,3.13.0-137-generic,x86_64,-junix,-smalloc,-sdefault,-hcritbit,epoll now = 3999664.335146 (mono), 1554491669.714933 (real) Backtrace: 0x43c1bb: /usr/sbin/varnishd() [0x43c1bb] 0x49e182: /usr/sbin/varnishd(VAS_Fail+0x42) [0x49e182] 0x45d1ac: /usr/sbin/varnishd() [0x45d1ac] 0x44d792: /usr/sbin/varnishd(VRT_String+0x22) [0x44d792] 0x44de66: /usr/sbin/varnishd(VRT_SetHdr+0xf6) [0x44de66] ...(redacted for customer proprietary information) See also https://github.com/varnishcache/varnish-cache/issues/2967 for a general discussion regarding an inconsistency in the WS_Reserve() interface
-
- 18 Mar, 2019 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 07 Mar, 2019 1 commit
-
-
Geoff Simmons authored
-
- 05 Feb, 2019 2 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
- 02 Feb, 2019 2 commits
-
-
Nils Goroll authored
Ref d8ae26b5a0b4a1102360a61a145e4730e52d68bc
-
Nils Goroll authored
-
- 03 Dec, 2018 8 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
compile_fail.vtc evidently takes longer than 60s when run in a docker container.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 03 Oct, 2018 3 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 17 Jul, 2018 3 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 03 Jul, 2018 1 commit
-
-
Nils Goroll authored
The reason is the same as for https://github.com/varnishcache/varnish-cache/issues/2708 : VRT_priv_task may now return NULL for out-of-workspace errors, see https://github.com/varnishcache/varnish-cache/commit/de2b431086a13b243dc8b3e71cd8697db1df2c7f
-
- 07 Jun, 2018 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 06 Jun, 2018 2 commits
-
-
Geoff Simmons authored
If RE2 reports the "DFA out-of-memory" condition for a failed set match, the VMOD reports the error as well.
-
Geoff Simmons authored
-
- 05 Jun, 2018 3 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 04 Jun, 2018 1 commit
-
-
Geoff Simmons authored
Update REQUIREMENTS to reflect compatibility with Varnish 6.0. re2 compatibility has been tested through 2018-04-01. No longer using the auto-generated SYNOPSIS.
-
- 28 May, 2018 1 commit
-
-
Nils Goroll authored
Fixes parallel build failures when compilation of vmod_re2.c, set.c or re2.c is attempted before vmodtool is finished
-