added --debug and --debug_brk options to meteor run
Fixed flaw in uuid generation where dynamic casting from hex string to integer
give the improper result for characters a-f.

See below for related snippet, spaced to make reading easy
X marks the spot!:
>  s
["0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "a", "b", "c", "d", "e", "f"]

>  _.map(s, function(input) { return ((input & 0x3)| 0x8)})
[ 8,   9,   10,  11,  8,   9,   10,  11,  8,   9,   8,   8,   8,   8,   8,   8]
                                                    X,   X,        X,   X,   X
_.map(s, function(input) { return ((parseInt(input,16) & 0x3)| 0x8)})
> [8,  9,   10,  11,  8,   9,   10,  11,  8,   9,   10,  11,  8,   9,   10, 11]
Merged jwulf change to start inner server with debug.
Clean up & style-ify debug and debug-brk options

* --debug-brk instead of --debug_brk to match node.js
* Use an enum passed through functions instead of global vars
Merging pull request #412 from jwulf

With some additional edits
Improve the way we log a specific error
Better management of user documents when created from external service.

Don't lose fields that were added in a previous login, but that aren't
received on a subsequent one. An example of this is the refresh token
sent from Google only on first login, in the case that the service
is configured on "offline" mode.

This is a prerequisite for merging in #464
When connecting to Mongo, default autoReconnect parameter to true.

Fixes #425.
Initial support for offline google oauth token
Improve offline google oauth token support:

- Use an argument to Meteor.loginWithGoogle and Accounts.ui.config
  rather than a UI-powered configuration option
- Add documentation
- Some cleanup
Don't lose Google refresh tokens
OAuth offline token docs improvement
Move the OAuth configuration wizard up.

Some of them are getting pretty high, and it was lower than
center on my 13" laptop.
Fix DomUtils.htmlToFragment with SELECTs. Add helpers.

When a <SELECT> was rendered on IE9 (or older) via DomUtils.htmlToFragment, the
hack we used somehow failed to properly set some attributes; they would show up
in innerHTML but not affect property values. eg, SELECTED would show up in an
OPTION's innerHTML but option.selected would not be set (nor would the parent
SELECT's value or selectedIndex). Fix this by replacing a mergeAttributes call
with an explicit attribute copying loop.

Also, add the helpers setElementValue and getElementValue to DomUtils, which are
used both in the test of this fix and will be used in a future change.

Fixes #496.
When preserving elements with values, preserve the value of elements unless the
server's rendering has changed.

This fixes two independent issues:

  - If the user has changed the value in a preserved field, and something causes
    the field to be rerendered, and the re-rendering renders the same value that
    was originally rendered, this now preserves the user's change rather than
    reverting to the original value.

  - INPUTs with type other than TEXT can now have reactive values (eg,
    type=SUBMIT).
Preserve CHECKED status similarly to VALUE.

Fixes #510.
Make minimongo tests pass in old browsers (FF3.6, IE8).

(Broken test added in 129154695455282a.)
Make minimongo test parse on IE7 unminified.
Merge remote-tracking branch 'meteor/devel' into devel

Conflicts:
	packages/accounts-google/google_server.js