-
Notifications
You must be signed in to change notification settings - Fork 398
Back-ports for 6.0.2 #2802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Back-ports for 6.0.2 #2802
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submitted by: Frederic Lecaille <flecaille@haproxy.com>
... argument to specify a custom location Fixes #2742
Fixes: #2745 Conflicts: bin/varnishtest/tests/v00020.vtc
Conflicts: bin/varnishd/cache/cache_vrt.c
Conflicts: lib/libvmod_blob/hex.c
* either NULL or properly named * only named arguments can be possibly be speficied multiple times * only named arguments can be optional * positional arguments could be missing
In other news: VTEST works.
Conflicts: include/vrt.h This appears to break the VRT interface, but there are symbols we are willing to break even on a stable branch because they are needed by VCC-generated code and off limits to inline C and VMODs. Refs #2800
Submitted by: Frederic Lecaille <flecaille@haproxy.com>
We use double for all time representations, yet monotonic time, real time and durations are not to be confused. Also, we might want to change the representation of time in the future. To get an implicit documentation of the semantic type of a time value and to facilitate working on the latter, we start off by introducing simple typedefs which neither inply any change nor offer any type checking. But they pave the way...
When producing files with "foo > file", always use the pattern: foo > file.tmp mv file.tmp file Otherwise program failures end up generating partial content and make will not even rerun the failing program next time you type make. Actually clean CLEANFILES in the clean target. The reference dir is not built, but it should be in the distfile
The previous code was correct already, but we can make it clearer that HFP implies OC_F_PASS Also test explicitly that both HFM and HFP have their objects slimmed. Closes #2768
As long as we are not queuing any threads, there is no queue to move. We record the queue marker the first time we notice queuing and only then see if it doesn't move. Fixes #2794
Counts the number of times we failed a response due to running out of workspace during delivery. Conflicts: bin/varnishtest/tests/v00058.vtc
Conflicts: bin/varnishtest/tests/v00058.vtc
See details in r02275.vtc for why there isn't a test case for this.
Ref #2792 Conflicts: doc/changes.rst
and make sure the expects in the test are scrupulusly correct.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Akin to #2799, this is the proposed set of back-ports for 6.0.2 up to current master (f56cce5).
As usual the goal is to avoid breaking the VRT and libvarnishapi ABIs since it's a stable branch with one notable difference this time. Following consensus from #2800 we are breaking two VRT symbols without changing the VRT 7.0 version because those symbols should not be used by inline C or VMOD authors.
And with no surprises:
Some of the original commits were partially back-ported because sometimes patches cover a wee bit more than what the commit messages say.
I believe not to have broken the libvarnishapi ABI, and the following changes were left out:
SessErrorSLTThat last one may be introduced since we have both a patch introducing it and another moving it to the last entry to preserve binary compatibility. Feedback appreciated.
Other notable changes that were left out:
VRT_CollectStrandsdebug.sethdr(because strands again)Debatable changes that made it in:
libvgzifdefingI don't think they count as breaking changes. Feedback appreciated.
I found a couple nits in master, I will open separate tickets or fix them directly.
I didn't update the changelog, and according to
git logandgrepwe should mention those tickets:I will happily spam your inbox if this gets approved, and hope someone will take care of the changelog :)
Special thanks to @hermunn!