Dridi Boukelmoune

Could this be a consequence of https://github.com/varnishcache/varnish-cache/pull/3557 ?

Bugwash suggestion: ```vcl # built-in sub vcl_backend_refresh { return (merge); } ``` In this subroutine we have access to `beresp` (read-write) and `obj_stale` (read-only) and the available transitions are: -...

> I am 👎🏽 because the suggested macro significantly decreases readability and I do not see any value in introducing a boilerplate which will just be applied wholesale. To be...

bugwash: ask issue reporters to try some jemalloc flags.

bugwash: we want pkg-varnish-cache to explicitly build with jemalloc support if we merge this change, removing automatic detection. edit: possibly only for x64_64 packages

Was this only approved by @nigoroll or during bugwash too? Did we hold the pull request because we just had a release?

I tried a light survey of the current situation: ```vcl varnishtest cmp varnish v1 -vcl { import debug; backend be none; sub vcl_recv { return (synth(200)); } sub vcl_synth {...

Closing for now because #3992 will pull the objhead rug pretty hard.

I have been working around this specific problem ever since I ran into failing auto-types, and subscribed to this issue when the last comment was https://github.com/keepassxreboot/keepassxc/issues/7881#issuecomment-1282800969. After reading this: >...