Sebastian Cohnen
Sebastian Cohnen
I'm curious. Are you also using spring, @pedropombeiro?
I personally would already be happy with an option to easily disable spring with ruby-lsp. Setting `DISABLE_SPRING` should already do the trick. Implementing this correct while still using spring sounds...
> Yeah. The only downside is that for very large apps, Spring makes a considerable difference in the time it takes for us to boot our little custom server. Agreed....
Fixed in https://github.com/facebook/prophet/pull/2592
I'm not sure I follow why the referenced Rubygems PR should fix #218. I get the same errors when running this changeset locally I got with #218.
When I checkout this PR, using bundler `2.5.19`, rubygems `3.5.19` on ruby `3.3.5` (`arm64-darwin23`), I get two broken tests when running `rspec`: ``` $ rspec ..Bundler can't satisfy your Gemfile's...
> How are you stopping it specifically? Sorry should have more specific. Starting the project up with `docker compose up` (in the foreground) and stopping it with `CTRL-c`.
For me the issue of the incorrect "mapping" is typically resolved by starting/stopping the container a few times (I think even once typically helps, but I'm not 100% sure).
Maybe related to https://github.com/numpy/numpy/issues/28687?
Having a known security vulnerability is such a PITA, even if they are not used but just reported by tools 🙄 If you require certain compliance processes, this creates so...