Avoid returning twice on error in `files.run`
Only set oplog-reply flag on the oplog collection

Otherwise can crash mongod!

Wed Feb 26 11:09:32.829 [conn499]  logs.tmp-test-logs-10833_meteor_com Assertion failure str::startsWith(ns, "local.oplog.") src/mongo/db/repl_block.cpp 261
0x10b9245ab 0x10b8fb64c 0x10b816015 0x10b5b2d06 0x10b714ce6 0x10b6bf354 0x10b6c398b 0x10b4dd9e2 0x10b917699 0x10b957055 0x7fff948637a2 0x7fff948501e1
I20140226-11:09:32.831(-8) (satellite.js:296) process 85850 for job tmp-test-logs-10833.meteor.com null exited with 1
 0   mongod                              0x000000010b9245ab _ZN5mongo15printStackTraceERSo + 43
 1   mongod                              0x000000010b8fb64c _ZN5mongo12verifyFailedEPKcS1_j + 284
 2   mongod                              0x000000010b816015 _ZN5mongo19updateSlaveLocationERNS_5CurOpEPKcNS_6OpTimeE + 2405
 3   mongod                              0x000000010b5b2d06 _ZN5mongo12ClientCursor19updateSlaveLocationERNS_5CurOpE + 52
 4   mongod                              0x000000010b714ce6 _ZN5mongo14processGetMoreEPKcixRNS_5CurOpEiRbPb + 534
 5   mongod                              0x000000010b6bf354 _ZN5mongo15receivedGetMoreERNS_10DbResponseERNS_7MessageERNS_5CurOpE + 1492
 6   mongod                              0x000000010b6c398b _ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE + 4939
 7   mongod                              0x000000010b4dd9e2 _ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE + 198
 8   mongod                              0x000000010b917699 _ZN5mongo17PortMessageServer17handleIncomingMsgEPv + 1657
 9   mongod                              0x000000010b957055 thread_proxy + 229
 10  libsystem_c.dylib                   0x00007fff948637a2 _pthread_start + 327
 11  libsystem_c.dylib                   0x00007fff948501e1 thread_start + 13
Add History entries for 0.7.1.2 bug fixes
Update banner and notices for 0.7.1.2
Update docs and examples
Merge branch 'release-0.7.1.2'

Conflicts:
	History.md
	docs/.meteor/release
	docs/lib/release-override.js
	examples/leaderboard/.meteor/release
	examples/parties/.meteor/release
	examples/todos/.meteor/release
	examples/wordplay/.meteor/release
	scripts/admin/banner.txt
Merge branch 'master' into devel
Add missing semicolon in deploy-galaxy
Replace `subscribeAndWait` with `subscribe` inside `onReconnect`
Return the sub from `ServiceConnection.subscribeAndWait`
Set up onReconnect after initial sub on the connection to log-reader.

If we set it up before `subscribeAndWait` returns, then we'll end up
with two subscriptions; we don't have the log-reader sub yet, so we
can't stop it when `onReconnect` runs the first time, so we end up with
a redundant subscription. This means that if a real reconnect happens
later, we'll stop the sub that we set up inside `onReconnect`, but not
the initial sub, so we've leaked a sub and end up with duplicate
messages after reconnect.
Clean up ServiceConnection timer when we receive a result.

Previously, we could make a connection, do some method calls, and then
10 seconds later the connection happens to be dropped and the connection
timer fires, which not only throws an unexpected error into the future,
but also resolves the future twice. I think ServiceConnection is just
supposed to time out if you don't hear anything from the server within
10 seconds, so it now no longer times out if you hear things from the
server but then happen to be not connected when 10 seconds has elapsed.
Use faye-websocket for server-to-server DDP

This matches what the SockJS server uses; now we only need to understand
and fix bugs in the implementation of one websocket npm module.

Some notes:

  - I actually trust that it's possible to close a connection before it
    successfully connects, which allows me to simplify the code a
    lot (since there shouldn't be multiple connections active per
    ClientStream). I put in some assertions to make sure this is the
    case, though.  (Note that this module also has a simpler model,
    where there's a single object representing the client connection,
    not a "client" object that spawns "connections".)

  - We now print connect errors as well as post-connect errors.  (This
    required adding a flag to keep tests quiet since it makes an
    expected-to-fail-to-connect connection.)  We need a better approach
    to stream error handling, though.

  - We used to have a test to make sure that a certain not-user-visible
    callback is called within a Fiber; structuring the code such that
    this test is still possible would lead to the code being less
    consistent and harder to read, so I dropped the test.

  - Fix a few bugs where we weren't using Meteor.setTimeout.
typo in history
Support {a: {$regex: '', $options: 'i'}}

Fixes #1874.
arguably support empty regexs in file watcher
minimongo: support semi-logical $elemMatch

ie, a document with some logical operator and some equality in an
elemMatch.

eg: {a: {$elemMatch: {x: 1, $or: [{a: 1}, {b: 1}]}}}

Fixes #1875.
history update
Merge branch 'devel' into oplog-limits-buffered