Manually Deleting Analyses too fast causes Logout.

[meyersbs]

When manually deleting analyses by clicking on the trash icon, if you rapidly double click the icon before the modal window pops up, clicking 'OK' on the first window causes a logout, but the second window popup overrides the logout screen, causing a failure. Terminal Output:

events.js:141
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read property 'user_id' of null
    at /home/benjamin/Linguine/linguine-node/routes/analysis.js:59:19
    at Query.<anonymous> (/home/benjamin/Linguine/linguine-node/node_modules/mongoose/lib/model.js:3336:16)
    at /home/benjamin/Linguine/linguine-node/node_modules/kareem/index.js:259:21
    at /home/benjamin/Linguine/linguine-node/node_modules/kareem/index.js:127:16
    at nextTickCallbackWith0Args (node.js:419:9)
    at process._tickCallback (node.js:348:13)

npm ERR! Linux 4.4.0-36-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script 'node ./bin/www'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the linguine-node package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./bin/www
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs linguine-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls linguine-node
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/benjamin/Linguine/linguine-node/npm-debug.log