Petteri Räty

An alternative to removing can be using scoping so that jQuery does not go into global scope. I haven't looked how easily the stack accommodates this. This would make jQuery...

Relevant here seems to be trying to run the project from the project directory. After copying the jar to server I get #147.

I used the following Gemfile to get latest warbler because the released gem had issues that I don't remember any more: ``` ruby source 'https://rubygems.org' gem 'google_drive' gem 'launchy' gem...

Also I think it’s a wrong call to disable it by default in the test environment. https://github.com/graphiti-api/graphiti/blob/a5bbb67b075aaba9e50604d7ef05fb609ad1b91a/lib/graphiti/railtie.rb#L94 This means it’s likely production where this problem surfaces.

> (fwiw that line is deprecated, it's [here](https://bbgithub.dev.bloomberg.com/BGOV/opportunity-search-vue/pull/90) now). > Copy paste error for the link?

> > We match Rails defaults for tests. If you enabled concurrency for graphiti in tests, everything would fail because Rails itself doesn't run with concurrency on in test mode...

> > That said, the issues I remember top of my head are A) rails does not eager load by default in test mode, which is requirement for things to...

> Again, thread safety is a different issue than the one that we are talking about. I would also love to see a source that threaded puma is used for...

> > Note any test will fail as the comment never gets assigned. Run an actual server in production mode and things will work correctly. > Work fine in development...

Is there a way to do this with CDP? If not, support would first need to exist in the protocol. https://chromedevtools.github.io/devtools-protocol/ The other option is that it's already supported to...