ncs semaphore odd behavior

ncs semaphore odd behaviorhttps://devzone.nordicsemi.com/f/nordic-q-a/104269/ncs-semaphore-odd-behaviorI have some very wonky semaphore behavior. Basically, giving a semaphore in an ISR isn't waking up a blocked thread. Reproducing program: proj.conf: Produces the following output: Note how 'Main thread' is printed twice each second? And noticeen-USTelligent Community 13Thu, 28 Sep 2023 23:55:47 GMTRE: ncs semaphore odd behaviorhttps://devzone.nordicsemi.com/thread/448228?ContentTypeID=1Thu, 28 Sep 2023 23:55:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:25fbd2ad-00b3-493a-a102-2f93e64f3eecKWolfe81<p>Update provided on the Zephyr Discord group:</p> <h3 class="header-2jRmjb"><span id="message-username-1157102316286132285" class="headerText-2z4IhQ"><span class="username-h_Y3Us desaturateUserColors-1O-G89 clickable-31pE3P">tomb</span></span><span class="timestamp-p1Df1m timestampInline-_lS3aK"><time id="message-timestamp-1157102316286132285" datetime="2023-09-28T23:51:30.124Z"><i class="separator-AebOhG"> — </i>Today at 4:51 PM</time></span></h3> <div id="message-content-1157102316286132285" class="markup-eYLPri messageContent-2t3eCI"><span>IRQ</span><span>_DIRECT</span><span>_CONNECT will not allow the scheduler to run</span><span>, it effectively bypasses the kernels ability run its scheduling point that might otherwise happen after an ISR returns<br /><br />Use IRQ_CONNECT instead.</span></div><div style="clear:both;"></div>