Added Env.callAsyncInParallel
used Env.callAsyncInParallel in several places
Merging and resolving conflicts
Restored logic swallowed by merge
Apparently, parallel calls didn't make them go away

On top of that, jenkins seems to be even more sensitive than usual to
these errors -- a time of day thing? Server load?
Why is it only suddenly failing on these *now*?

And why is jenkins only failing one of them at a time? And a different
one each time?
Reverting extra qunit changes added for jenkins

Because the jenkins test failures that these were added to deal with may
have been flukes.
Merging and resolving conflicts
Revert "Reverting extra qunit changes added for jenkins"

This reverts commit ef7078cd24a43966123bed9077009f5ca8dafbab.
Removed wildcards from views
Restored call to get user prefs before monitoring
Revert "Restored call to get user prefs before monitoring"

This reverts commit 2f7aae23caadfee080be521b3f5cec75e4d68d5b.
Restored call to get user prefs before monitoring
Added Fire to the python client
Added updated view files as updates
Merge pull request #1124 from blackshadowshade/1089_view_wildcards

Removed wildcards from views
Merge pull request #1111 from AdmiralJota/1065_parallel_async_calls

Allowed parallel asynchronous calls