Brendan Ribera

The behavior is actually there -- for example: * [`get_all_versions`](https://github.com/rails/rails/blob/master/activerecord/lib/active_record/migration.rb#L1030) queries the `schema_migrations` table for all of the versions that have actually been inserted * [`needs_migration?`](https://github.com/rails/rails/blob/master/activerecord/lib/active_record/migration.rb#L1042) finds the migration files...

Here's another [example from Elixir's ecto](https://github.com/elixir-ecto/ecto/blob/v2.1.4/lib/ecto/migration/schema_migration.ex) library.

The same way code conflicts are handled: the developer doing the merge has to correct the problem. In my experience, the "skipped compatible-but-out-of-sequence migrations" scenario happens fairly often, and the...

@ahmetb wrote: > I am inclined to say that you can probably do that loop yourself in a little wrapper script. If you're shipping your application in a shell-free image...

We're not on 1.23 yet, so we're stuck with maintenance mode :)

I think this project _needs_ to user the Dockerfile build methods and can't just switch to `nginx:alpine`. [ngx_stream_ssl_module](https://nginx.org/en/docs/stream/ngx_stream_ssl_module.html) / [ngx_stream_ssl_preread_module](https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html) aren't built by default, but are used by both images....

Cool! TIL [how alpine builds nginx](https://git.alpinelinux.org/aports/tree/main/nginx/APKBUILD) :)

We're seeing similar behavior with `'@grpc-js': v1.9.13` clients calling golang services, originating with roughly the same Istio version upgrade (unfortunately, we went from v1.17.5 to v1.20.0, so we're not really...

Hi folks: we've been able to resolve our issue in two different ways: 1. Upgrade to grpc-js `v1.10.4` (which includes grpc/grpc-node#2695) 2. Even with grpc-js before that release, we fixed...

@eigenhombre Yes, I'd absolutely welcome a PR! I like the notion of having the API expose `:dist` for when you need to actually know that value -- i.e. maybe even...