Marten Veldthuis

Well sure, we need to look at our provisioning scripts to make sure the hostname for the new node gets added to the hosts file so it can resolve itself....

Maybe an optional `require 'bogus/rspec-mocks-compatibility'` that the user does if it want it? That file might even raise if the loaded RSpec is known to be incompatible (alternatively: not known...

We're hitting this issue as well. One snag with it is that we have set up `object_by_id` to run through a Pundit policy scope (`Pundit.policy_scope!(query_context[:api_session], type_name.safe_constantize).find_by(id: item_id)`). That scope is...

Couldn't you stop the visualization automatically after (attack+sustain+decay) seconds?

`inline-flex` actually isn't perfect either, the checkbox icon inside is then nudged too far right and/or enlarged. The whole component also still sitting with the bottom edge on the baseline...

I just tried the same and ran into the same error. Did you manage to resolve it?

Just wanted to report I'm having the same issue with our view specs. I'm trying to reproduce it on your spin-test app, but no luck so far. I did notice...

@Calamari I'd be interested to hear about your workaround. This message annoys me a lot as well.

Still here. The console logs print on test runs, so this is really annoying.

👍 What is this, the dark ages? We don't download and copy random Javascript files from the internet anymore. This should be on NPM.