dwolla jotform oauth url

Looks like the “typical” you should enter into the dwolla side for “oath redirect” is

8. In the OAuth URL field, enter https://www.jotform.com/dwolla_complete.php

from the better help here: https://www.jotform.com/help/360-Setting-Up-Dwolla-Integration-With-JotForm

ruby ffi cygwin woze and other crystal

Using simplecov 0.7.1
Using term-ansicolor 1.2.2
Installing debugger 1.6.1 with native extensions
Using rspec-expectations 2.14.2
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

/usr/bin/ruby.exe -r ./siteconf20161205-8584-k0h8zm.rb extconf.rb
checking for ffi.h… no
checking for ffi.h in /usr/local/include,/usr/include/ffi… no
checking for rb_thread_blocking_region()… no
checking for rb_thread_call_with_gvl()… yes
checking for rb_thread_call_without_gvl()… yes
checking for ffi_prep_cif_var()… no
creating extconf.h
creating Makefile

make “DESTDIR=” clean
rm -f
rm -f ffi_c.so *.o *.bak mkmf.log .*.time

make “DESTDIR=”
Configuring libffi
config.status: error: could not create man/Makefile
make: *** [libffi.mk:7: “/home/packrd/.gem/ruby/gems/ffi-1.9.0/ext/ffi_c/libffi-x86_64-cygwin”/.libs/libffi_convenience.a] Error 1

make failed, exit code 2

Gem files will remain installed in /home/packrd/.gem/ruby/gems/ffi-1.9.0 for inspection.
Results logged to /home/packrd/.gem/ruby/extensions/x86_64-cygwin/ffi-1.9.0/gem_make.out

An error occurred while installing ffi (1.9.0), and Bundler cannot continue.
Make sure that `gem install ffi -v ‘1.9.0’` succeeds before bundling.

 

meant “install cywin libffi-devel package first”

2000 toyota sienna back door stuck shut/closed side sliding door shut stuck/closed

OK we had this for both doors oddly.

Just must have shut them weird or something, and now, even though they’re unlocked, impossible to get open via the door handle{s}.

My wife figured out how to fix it, apparently you can still remove the inside door panels for either door, from the inside, even with the door closed.  So remove the panels and pull on some wires to get it to open again (youtube how to remove the panels).

allergic to pizza

I get “the runs” (diarrhea) after eating pizza.  After some painful cramps as the stuff goes through me LOL.

 

current work around/fix: take a probiotic pill before eating the slices.  Actually helps/works.

Anything else help out there? please comment!

Get a diagnosis from a doctor that is accurate? Share it here!

windows 10 ms dvd navigator filter

seems that is “almost” still has it

(though they’ll say it was removed in windows 8, though if you bought the windows 8 “pro pack” it brought it back).

My hunch is that the pro pack just supplied an mpeg2video decoder (NB: the patents on mpeg2video are expiring…)

but now if you provide your own it can still work [?]

chrome extension woe

Refused to execute inline script (or javascript URL) because it violates the following Content Security Policy directive: “script-src ‘self’ blob: filesystem: chrome-extension-resource:”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-93fgPWwrym5fXzZiAaRxBVwd4tc4seYr4/TXsZL+9P8=’), or a nonce (‘nonce-…’) is required to enable inline execution.

meant “add that to your manifest.json”

ex:

  “content_security_policy”: “script-src ‘self’ https://rawgit.com https://*.rawgit.com ‘sha256-qDggtJ0ZQS79xsMxbArH5hKSHI/hKg5qU1OGLMcyXgQ=’; object-src ‘self'”,

but oddly, when I was doing this *right* (trying to inject javascript code into a document) there was no error like this, turns out I was trying to inject it from within a “popup.js” and if I did it from a contentscript.js then voila, no complaint from chrome.

Very weird.

Anwyay content_script has access to the “real” document aparently, popup.js only has access to the document of the little popup thing when you click the extension icon 😐

Roger's meanderings, notes to himself, bug reports, and other things