vhermecz

First, thx for the example link in the last comment @MrSakhs, that gave it finally away. While this is not entirely impossible indeed, the current implementation feels way too fragile....

@larskanis thx for the comment on taint removal, as we needed this quick, I copied latest [v0.999991](http://www.ch-werner.de/rubyodbc/ruby-odbc-0.999991.tar.gz) from Christian Werner's page, and did a quick patch. Could be further cleaned...

I was facing this same issue: - Env: yarn v1.22.21, node v20.10.0 - The `string-width ^5.0.0` dependency was coming from [next.js](https://www.npmjs.com/package/next) - `eslint-config-next > @next/eslint-plugin-next > glob > jackspeak >...

Is this really that hard?! 1.4 is broken, the LocalStoreClearMiddleware breaks Django's middleware contract, as process_exception is reraising the freaking exception, instead of simply returning None. That was fixed Sept...

Did not find anything for this. Connecting to the database, I've noticed that in our case job had RUNNING status (30) and flow had KILLING status (55). Not nice, but...