<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Signals on blog.szypowi.cz</title><link>https://blog.szypowi.cz/tags/signals/</link><description>Recent content in Signals on blog.szypowi.cz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://blog.szypowi.cz/tags/signals/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform under AzureCLI@2 never sees your cancel</title><link>https://blog.szypowi.cz/p/terraform-under-azurecli@2-never-sees-your-cancel/</link><pubDate>Mon, 20 Apr 2026 12:00:00 +0200</pubDate><guid>https://blog.szypowi.cz/p/terraform-under-azurecli@2-never-sees-your-cancel/</guid><description>&lt;p&gt;If you cancel an Azure DevOps pipeline mid-&lt;code&gt;terraform apply&lt;/code&gt;, or let it hit its &lt;code&gt;timeoutInMinutes&lt;/code&gt;, you probably expect terraform to catch SIGINT, release its state lock, and exit cleanly. Under &lt;code&gt;AzureCLI@2&lt;/code&gt; that does not happen. Terraform is SIGKILLed without ever seeing a signal, and the state lock stays behind.&lt;/p&gt;
&lt;h2 id="what-i-measured"&gt;What I measured&lt;/h2&gt;
&lt;p&gt;The Azure Pipelines agent applies a signal ladder on cancel: SIGINT, wait &lt;code&gt;PROCESS_SIGINT_TIMEOUT&lt;/code&gt; ms (default 7500), SIGTERM, wait &lt;code&gt;PROCESS_SIGTERM_TIMEOUT&lt;/code&gt; ms (default 2500), SIGKILL. Straightforward on paper.&lt;/p&gt;</description></item></channel></rss>