Tinco Andringa

Having the same IV every chunk is the same as having no IV. You are not using the protocol in the way it was designed, so you are vulnerable to...

We ran into this issue as well, temporary workaround that fixed it for us was adding: ``` "resolutions": { "nwsapi": "2.2.0" }, ``` To the top of our `package.json`. A...

Any language that does not have an event loop built in will have the problem of multiple alternatives being available. Rust is moving towards a standardized interface for futures (Rust...

Same here on the DS1819+, I installed wireguard, it said it failed, then I tried uninstalling, that failed as well. I didn't want to be stuck so I checked the...

I think we're running into this. I thought it was because this line: https://github.com/rails/rails/blob/7-0-stable/activesupport/lib/active_support/notifications/instrumenter.rb#L28 loses the stacktrace, but that line hasn't changed in 14 years. Now that sentry also supports...

This is an example of a bad backtrace event: https://aeroscan.sentry.io/issues/3954652238/?project=1805098

I have the same problem, I can install [google-protobuf 3.21.12](https://rubygems.org/gems/google-protobuf/versions/3.21.12) just fine, but specifying it as an explicit dependency in my Gemfile doesn't solve the problem because it looks for...

Ah I just solved it. I accidentally ran `bundle install` before running `bundle update` and it installed an old version of Bundler (2.1.4) which has a bug that causes it...

Yeah, I got some more errors I didn't understand so I just removed the Gemfile.lock and ran bundle update. That fixed all issues, but it requires you run a diff...

Eh also make sure you actually uninstall the old bundler with `gem uninstall bundler` it kept using the old one even after installing the new one.