Vladimir Dementyev

MatchData#end returns invalid offset when called within evalAsync

5

Stackblitz reproduction: https://stackblitz.com/edit/ruby-wasm-demo-78s71k?file=index.html MatchData#end returns incorrect match offset when used in async context: ``` vm.eval(/(т)(е)(с)/.match('тест').end(0)) #=> 3 vm.eval(/(т)(е)(с)/.match('тест').end(1)) #=> 1 vm.evalAsync(/(т)(е)(с)/.match('тест').end(0)) #=> 3291 vm.evalAsync(/(т)(е)(с)/.match('тест').end(1)) #=> 3 ```

Calling `refresh()` fails when the `checkboxAllTarget` has been removed without disconnecting the host element. We should check for the `hasCheckboxAllTarget`. This problem occurs, for example, when using page morphing (and...

## Context Recently, we found an issue with the combination of Sniffer, Anyway Config, and Doppler: a max call stack error occurs when we have an HTTP-backed configuration source available...

VS Code: Add customBinaryPath option

11

### Motivation This option allows to provide any compatible binary to be used as `ruby-lsp` exec. This is especially useful for containerized development with VS Code running on the host...