David Runger

Here's a permalink to the line in Vimium: https://github.com/philc/vimium/blob/97729f72533276d0d2aeb9f6b039e51cb96b785d/lib/utils.js#L23

@Epigene : I was having the same issue. I ran RSpec with `bin/rspec [...] --backtrace`. Then, when the test failed, I saw the full backtrace that had generated the unregistered...

@vinistock : Is there a tracking issue or PR that we can subscribe to, in order to stay updated on the progress toward indexing methods / providing "Go to definition"...

@rikkipitt I too was getting a 403 forbidden error from Cloudflare:  ```html 403 Forbidden 403 Forbidden cloudflare ``` I fixed it by setting the host header to `nil` when...

I'm chiming in here in case it helps others. I was getting this error and then fixed it by using the `release-tag` option. Here's how I am using this GitHub...

### Context The reason that this initially came to my attention (and my motivation for this change) is that a JavaScript library that I use (`element-plus`) actually [validates](https://github.com/element-plus/element-plus/blob/d4a5d150bd9ae8cb344d2791c8529fb891be858e/packages/components/input/src/input.ts#L177-L178) that focus...

Looking at the Ruby 3.3 test run, there are five failing specs ([link](https://github.com/rubycdp/cuprite/actions/runs/10550590601/job/29226917269?pr=272#step:5:456)). I believe that none of those failures are related to my change, and that those failures are...

> Looking at the Ruby 3.3 test run, there are five failing specs ([link](https://github.com/rubycdp/cuprite/actions/runs/10550590601/job/29226917269?pr=272#step:5:456)). > > I believe that none of those failures are related to my change, and that...