Jeroen de Bruijn

@nikersify DO you have time to check and merge this PR? I'm also getting this issue and would really like to use this workflow. I'd also be happy to help...

Nice analysis! I think I have a similar issue although I didn't measure the lines. For me the target also isn't reset after writing. I'm using STLINK/V3 MINI with an...

I'd argue this should stay open as the solution is a workaround instead of a solution!

Hi @jkralik , I recently ran into a problem with usage of resources and would like to limit the number of simultaneous connections to the CoAP server. I found this...

I've checked in my test setup and also works there. See the readme of the repo I've just referenced this in. Will be testing this in my application code, but...

FWIW I'm doing like example below in our DTLS server for IoT devices to create 1000 handshake workers/listeners, also using [go-coap](https://github.com/plgd-dev/go-coap). Has been working great for over a year now....

FWIW I'm using this successfully with GitHub Apps using https://github.com/vidavidorra/github-app-token with following permissions. Example workflow: https://github.com/vidavidorra/roadmap/blob/main/.github/workflows/triage.yml.  workflow code ```yml name: Add issue to project on: issues: types: opened jobs:...

I'm not quite sure, but I think you could already achieve that by setting `fetch-depth: 1` in the checkout action, don't configure it [as `1` is the default](https://github.com/actions/checkout/tree/v3.0.0#usage). The way...

Ah yeah, I guess you're right. In the PR we'll get a commit SHA range from GitHub, so we'll try to run on that range. In the case `fetch-depth: 1`...

Yeah I think we should name it `commit-depth` or something like that to avoid confusion with the checkout parameter.