Looks like someone testing some sort of repo migration script.
I don’t think it’s shady, just a bit irresponsible

I suppose they could, but I do expect to be able to ping someone from about any public place on GitHub. I often do and it's very useful.

Got it too. Insta blocked the account.

Definitely an annoying GitHub behavior, but at the same time I'm not sure what they could change.

Docker caching is so arcane and brittle that in the past I basically gave up and did my own cache keys by pushing/pulling intermediate layers at predictable locations.

e.g. REGISTRY/intermediates:bundler-%{SHA1(Gemfile, Gemfile.lock)}

Worked super well.

Of course, but I was working on bootsnap recently, and would really love to make things cleaner.

I think it may be time to try to integrate bootsnap in bundler itself.

> it doesn't address that code expects that $LOAD_PATH only contains Strings.

Rereading the ticket, I'm not sure this is really a big deal. Is that sort of code even common?

Also you'd only be exposed to that if upgrading to newer bundler so there would be plenty of time to adapt?

I think we really should work on getting rid of the require overrides.

I was rereading bugs.ruby-lang.org/issues/16848 just yesterday, I think we should revive that feature request.

Happy to brainstorm it with you if you are interested.

No, the spec state the headers must be normalized (which makes sense for an interface).

Servers would be free to expose the original headers in another way, but that would be outside the spec, and I don't know any server doing that.

Nah, it's just that extending an object means creating a singleton class. If it's just for a single object it's fine, but you you are doing this for lots of objects, it means the class will be different every time and that trashes the VM caches.

99.999% of the time it's best not to use it though.

Alright, you got a point :)

Not just conceptually!

I'm not sure what the context is in your case.

It did happen that I declined discussing things further until some prototype was published.

It's super easy to talk over each others head with prose. With code, there's no misunderstanding, it makes it clear what the goal is.

But to each their own.

So I took half an hour to open a prototype PR and then it was much more clear what I intended to do: github.com/puma/puma/pu...

Even for bigger changes, sometime a quick prototype PR help convey the intention much better than a long discussion.

Case in point, I opened github.com/puma/puma/is... to test the waters, but kept answering the same questions, clearly it wasn't clear to everyone what I had in mind.

That's not actionable data though.

All I can think of is: for the love of god, gimme the raw data!

I’m sure there are API that are just begging to be optimized.

Ruby and Rails are very similar in their versioning scheme. The major is used for marketing, the minor is equivalent to a major in SemVer term, and the patch is what SemVer people expect.

That’s more or less how we do it it Rails. There’s deprecation message mention the release that will remove the API.