{"push_id":3061888831,"size":5,"distinct_size":3,"ref":"refs/heads/mgmt_vcl_state","head":"a5b8a1970bd2a88e7bc9af1e44754d3bb113756c","before":"0c7ae0f1208d0b4ac4ffa4ae31c36e0b7673b180","commits":[{"sha":"6045eaaa6a2f0a51f667d4c2cf23cd7fb43abe9f","author":{"name":"Dag Haavi Finstad","email":"faaf46645cf753365630036b3c818998a7ffc3dc@varnish-software.com"},"message":"Add error handling for STV_NewObject() in vrb_pull\n\nFixes: #2831","distinct":false,"url":"https://api.github.com/repos/nigoroll/varnish-cache/commits/6045eaaa6a2f0a51f667d4c2cf23cd7fb43abe9f"},{"sha":"9e155bbab0949fb6d4c3cc023c75de5bf5ddb1fb","author":{"name":"Dag Haavi Finstad","email":"faaf46645cf753365630036b3c818998a7ffc3dc@varnish-software.com"},"message":"Fix test case: 'SMA'->'SM?'","distinct":false,"url":"https://api.github.com/repos/nigoroll/varnish-cache/commits/9e155bbab0949fb6d4c3cc023c75de5bf5ddb1fb"},{"sha":"518f46bbfd01b68907aa730b1112ab2e188a10cd","author":{"name":"Nils Goroll","email":"a05e1af71cc00bfb4dfcde6b94560e408ccabf9a@uplex.de"},"message":"minor vtim-ification","distinct":true,"url":"https://api.github.com/repos/nigoroll/varnish-cache/commits/518f46bbfd01b68907aa730b1112ab2e188a10cd"},{"sha":"3707eef4cb207502f761767e4d94f0dde518ca04","author":{"name":"Nils Goroll","email":"a05e1af71cc00bfb4dfcde6b94560e408ccabf9a@uplex.de"},"message":"change semantics of the vcl 'auto' state and centralize vcl mgt\n\nConceptually, the auto state was a variant of the warm state which\nwould automatically cool the vcl. Yet, cooling did not only transition\nthe temperature, but also the state, so 'auto' only worked one way -\nexcept that vcl.use or moving a label (by labeling another vcl) would\nalso set 'auto', so a manual warm/cold setting would get lost.\n\nNow the auto-state will remain no matter the actual temperature or\nlabeling, so when a vcl needs to implicitly change temperature (due to\nbeing used or being labeled), an auto vcl will remain auto, and a\ncold/warm vcl will change state, but never become 'auto' implicitly.\n\nThe vcl state/temperature test v00003.vtc, besides testing the new\nauto semantics, now also checks for the right vcl.list output and has\nbeen reduced by a duplicate check (warm event check has been\nintegrated into an existing warm event).\n\nOn other code changes:\n\n* mgt_vcl_setstate\n\n  is now only concerned with the state, the temperature will be\n  changed implicitly if so required. The state will either end up\n  changed or restored, depending on success.\n\n  owner of changes to the (struct vclprog).state member\n\n* mgt_vcl_settemp\n\n  responsible for the right action to change the temperature. For auto,\n  it will only change the temperature, for non-auto, also the state.\n\n  owner of changes to the (struct vclprog).warm member\n\n* mgt_vcl_tellchild\n\n  Inform the child about a change and/or temperature change\n\n* mgt_vcl_set_cooldown\n\n  Update the cooldown (go_cold) appropriately, should be called after\n  a change/temperature change.\n\nFixes #2834\nCloses #2801","distinct":true,"url":"https://api.github.com/repos/nigoroll/varnish-cache/commits/3707eef4cb207502f761767e4d94f0dde518ca04"},{"sha":"a5b8a1970bd2a88e7bc9af1e44754d3bb113756c","author":{"name":"Nils Goroll","email":"a05e1af71cc00bfb4dfcde6b94560e408ccabf9a@uplex.de"},"message":"no implicit warmup for manual temperature control\n\nAs discussed during bugwash, we should be consistent about the manual\ntemperature controls and not transition cold->warm, but rather fail.","distinct":true,"url":"https://api.github.com/repos/nigoroll/varnish-cache/commits/a5b8a1970bd2a88e7bc9af1e44754d3bb113756c"}]}
{"actor":{"display_login":"nigoroll"}}