Fixes stardust crash on new account. See #5883 #5884
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes an issue when you have a brand new account (no stardust yet) and run the bot. This makes sure the key is there before we do something with it.
|
👍 |
BreezeRo
pushed a commit
that referenced
this pull request
Jan 27, 2017
* Added Total Stardust to UpdateLiveStats task (#5874) * added Total Stardust to UpdateLiveStats task * fixes to tests, thanks to @nelsyeung * enabled option to log to file (#5881) * Fixes #5883 (#5884) This fixes an issue when you have a brand new account (no stardust yet) and run the bot. This makes sure the key is there before we do something with it. * removing proto and protobuf and changing pogoapi to dev * removing proto and protobuf, changing pogoapi to dev branch, fixing docs and install scripts
solderzzc
pushed a commit
that referenced
this pull request
Jan 30, 2017
* Proto requirements fix (#5888) * Added Total Stardust to UpdateLiveStats task (#5874) * added Total Stardust to UpdateLiveStats task * fixes to tests, thanks to @nelsyeung * enabled option to log to file (#5881) * Fixes #5883 (#5884) This fixes an issue when you have a brand new account (no stardust yet) and run the bot. This makes sure the key is there before we do something with it. * removing proto and protobuf and changing pogoapi to dev * removing proto and protobuf, changing pogoapi to dev branch, fixing docs and install scripts * Prevent bouncing between 2 forts Added simple logic to prevent bouncing between 2 forts when using Polyline walker * Original fixes by Anakin5 Original PR by Anakin5 which fixes the following: #5407 Fix step walker timing issue. This solve some problems where we were moving more than the configured speed from time to time. Improve a bit the computation speed of step_walker get_next_step pep8 fixes * Prevent bouncing between 2 forts Added simple logic to prevent bouncing between 2 forts when using Polyline walker
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes an issue when you have a brand new account (no stardust yet)
and run the bot. This makes sure the key is there before we do something
with it.
###Fixes
See #5883