- 29 Dec, 2021 1 commit
-
-
Dridi Boukelmoune authored
-
- 21 Dec, 2021 1 commit
-
-
Dridi Boukelmoune authored
And expose bereq.time in vcl_pipe now that we have some. Refs #3562
-
- 20 Dec, 2021 2 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 19 Dec, 2021 5 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
fickle for that, and misleading information wastes oceans of time.
-
Poul-Henning Kamp authored
-
Guillaume Quintard authored
-
- 18 Dec, 2021 1 commit
-
-
Nils Goroll authored
-
- 16 Dec, 2021 1 commit
-
-
Dridi Boukelmoune authored
-
- 15 Dec, 2021 1 commit
-
-
Dridi Boukelmoune authored
They are grouped by categories and that hasn't changed, and the order of groups haven't changed. All occurrences of foo.* variables are sorted alphabetically instead of approximately by relationship between each other. Inside the first group, variables are now ordered based on the PROXY protocol diagram: - client - server - remote - local A note was added and is hopefully visible enough to maintain this order. You can verify that nothing changed: $ COMMIT=<this-commit-hash> $ git show $COMMIT~:doc/sphinx/reference/vcl_var.rst | sed '/^$/d' | sort | sha1sum 3400130e88c0456b3bc779b9dfeeff09e130efa3 $ git show ${COMMIT}:doc/sphinx/reference/vcl_var.rst | sed '/^$/d ; /.. NOTE:/d' | sort | sha1sum 3400130e88c0456b3bc779b9dfeeff09e130efa3 Use whatever alternative to sha1sum your system may provide.
-
- 14 Dec, 2021 11 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
This reverts commit 82be6f46.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
I checked the git history to understand this comment.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
And complain when two parameters are passed instead of one parameter and one option.
-
Nils Goroll authored
Confusing panic output was generated when a worker ran multiple requests before returning to the pool. Noticed when debugging #3755 : VCL::methods = {RECV, PASS, HASH, MISS, HIT, DELIVER}, Same panic with this fix: VCL::methods = {RECV, HASH},
-
Nils Goroll authored
Fixes #3755
-
Nils Goroll authored
-
Nils Goroll authored
I have checked that this catches #3752 too
-
Nils Goroll authored
This is useful to ensure that workspace does not, by chance or accident, contain data and, in particular, magic numbers from previous workspace use.
-
- 13 Dec, 2021 4 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
With this change, we can formalize the renaming of a parameter while maintaining the old name temporarily for compatibility. A deprecated alias can be set with either param.set or the -p option, but won't be listed by: - param.show [-j] - param.show [-j] changed - param.show -l Only an explicit param.show for the name of the alias will provide a minimal documentation with a deprecation notice and the current value. In the manual, there is only a deprecation notice. The rationale is that administration tools shouldn't pick them up when enumerating the parameters. Since we currently don't have deprecated parameters, this can only be tested manually, for example: PARAM_ALIAS(vcl_dir, vcl_path) To ensure that we don't break this, we could consider having a perpetual deprecated parameter.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
- 10 Dec, 2021 2 commits
-
-
Nils Goroll authored
Fixes #3752
-
Nils Goroll authored
-
- 07 Dec, 2021 1 commit
-
-
Dridi Boukelmoune authored
This reuses the stringform concept and introduces a similar bodyform flag for STRINGS and BLOB types. We can now assign either a STRING or a BLOB to [be]resp.body, without breaking the VRT ABI and API. In fact, the VRT API now uses a void* C type for the BODY VCL type and finds which type to use based on enum lbody_e. The enum completely changed but macros were added to maintain the API, and because of this change, enum lbody_e literals are formatted in two steps. As a result the BODY type grew another noindent flag. It prevents the insertion of white space between the LBODY_{ADD,SET}_ prefix and the type name suffix (BLOB or STRANDS).
-
- 06 Dec, 2021 1 commit
-
-
Lachlan Abbott authored
-
- 03 Dec, 2021 2 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
This way they can all nicely align in the VTC output. The recently added "end" legend that denotes the end of a transaction before a match happened for the given VXID conflicted with the end of the logexpect spec. The latter was renamed to "done".
-
- 02 Dec, 2021 2 commits
-
-
Dridi Boukelmoune authored
When a transaction ends, there will be nothing left to match for the transaction's VXID. Instead of timing the whole test case out, fail immediately.
-
Martin Blix Grydeland authored
The logics were off by one in the available buffer space checks, causing us to loose one word of per thread log buffer space, and making reasoning about available space tricky. Fix this. Refs 10749ffe Refs #3745
-
- 01 Dec, 2021 5 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
That is, when it's a request or backend transaction, otherwise it's still logged with VXID 0. The goal is to allow a correlation between VCL statements and their workspace footprint by sharing the same transaction instead of being split between raw and vxid scopes. That kind of debugging becomes possible when the workspace debug flag is used and VCL_trace records are not masked. Given the verbosity of both workspace and trace logs, we would need new tools to process transactions for this purpose and until we can link everything we have a chicken-egg problem. This change does not go all the way and relies on the thread-local worker reference to opportunistically log into its VSL buffer when it has one. When the workspace is initialized, the buffer may not be ready yet, so some logs may still end up raw. What's likely going to be missing is workspace early initialization and teardown: in other words before and after VCL execution, which should be good enough for the purpose of debugging workspace operations in VCL tasks.
-
Dridi Boukelmoune authored
Since its primary usage will be workspace logs, workers can be initialized earlier to offer even more opportunity for logging.
-
Nils Goroll authored
today: VRBT_REMOVE returns the element argument no matter if it was present in the tree or not, so it can not sensibly be used for assertions.
-