Andre Figueiredo
Andre Figueiredo
Same error here on Linux. I get stuck on "Running Jasmine with PhantomJS". I called my specRunner.html with `page.render` from `phantomjs` and got this screen: 
Nevermind, problem was on my side. Sorry I didn't read carefully docs. I was running a custom `specHtml` which **didn't console messages**[1]. So, `phantomjs` on `jasmine-runner.js` **never exited**. I didn't...
https://github.com/realriot/ff4d https://github.com/rianhunter/dbxfs
Well, your button take a little space because you set its dimensions to 1x1. Proper way to hide it would be: ``` display: 'none', borderWidth: 0 // if necessary ```...
i have the same issue, log says: using v0.2.2 from main nuxt monorepo and nuxt v2.15.8 ``` TypeError: Cannot read property 'sources' of undefined at Object. (node_modules/@nuxt/webpack/node_modules/terser-webpack-plugin/dist/index.js:44:18) at Object. (node_modules/@nuxt/webpack/node_modules/terser-webpack-plugin/dist/cjs.js:3:16)...
I'm too experiencing this weird output. Although I want to break lines with brackets instead, but it looks like it's the same behavior. I'm forced to add an extra white...
you can override by creating a decorator as defined here: https://github.com/spree-contrib/spree_social/blob/7963d4246b56e297e4ea7461e22bbe2a66ad20b7/lib/spree_social/engine.rb#L29:L33 ie: `app//engine_decorator.rb`: ``` OmniAuth::Strategies::Facebook.class_eval do def request_phase options[:scope] ||= 'email' options[:info_fields] = 'first_name,last_name,email' options[:display] = mobile_request? ? 'touch' :...
You skipped one step, from README: > Afterwards your overview should show your freshly created credentials in the form > > Application ID: 00000000A2B3C495 > Applications secrets: qOFCYaZKjm6e13aq3fdGiNz > >...
It actually gave me error when compiling patched ls.c, please see screenshot below. AFAIK coreutils 8.2 is from 2009, it has a lot of code since then. I patched 8.29...
Had the same issue, turns out, the guilty was Vue Syntax Highlight by rahul Kadyan (https://marketplace.visualstudio.com/items?itemName=znck.vue-language-features)