Skip to content

Comments

Simple lure attraction in move_to_fort worker#2068

Closed
z4ppy wants to merge 23 commits intoPokemonGoF:devfrom
z4ppy:dev
Closed

Simple lure attraction in move_to_fort worker#2068
z4ppy wants to merge 23 commits intoPokemonGoF:devfrom
z4ppy:dev

Conversation

@z4ppy
Copy link
Contributor

@z4ppy z4ppy commented Jul 31, 2016

Add optional lure attraction in move_to_fort

@douglascamata
Copy link
Member

@z4ppy please break down your lure attraction logic into many smaller methods.

@douglascamata
Copy link
Member

@z4ppy need to solve merge conflicts with dev too, so I can merge.

@z4ppy
Copy link
Contributor Author

z4ppy commented Jul 31, 2016

I did some smaller method and is better like that, ty :)

@z4ppy
Copy link
Contributor Author

z4ppy commented Jul 31, 2016

I don't know how launch unittest :(

DayBr3ak and others added 7 commits July 31, 2016 12:37
* add mock and nose to the dependencies

* added unit tests for the api_wrapper

* add testing to travis build

* fixing path ?

* pylint error fixed

* adding myself to contributors

* add test for the step_walker

* add runtime error for big distances

* change travis, nosetests should look for tests in all the folders

* Getting rid of nose, rename some files, add 'timeout_decorator' to the requirements

* update travis.yml

* changed run_tests script from bash file to python file

* revert file changes

* skipping failing test

* fix another test

* some style/import improvment

* revert SKIP_TIMEOUT

* remove run_tests.py

* move tests cases into main test folder

* refactor some code api_wrapper_test

* refactor and location parser

* test is failing add a FIXME tag

* location is now unicode friendly
* Warns if there aren't sufficient space left for loot.

SpinFort will terminate silently, and users will not notice
that SpinFort is skipping due to the lack of space.

As a result, it sends out requests to Niantic even faster than before
becuase tasks are looping faster and doing noops. More server busy (error 52)
errors appear in the log without an explanation of what's actually
going on.

* improve readability of should_run for SpinFort and MoveToFort
* adapted to new commits

* added config
changed gitignore

* added config

* locked versions

* typo

* account for task management change

* moved find_cluster to utils. follow_cluster now 1 task

* added test for follow_cluster

* added mock requirements

* trying to get travis to build

* trying to get travis to build

* added search for lured cluster functionality

* adapted tests

* removed double specification
@douglascamata
Copy link
Member

@z4ppy more merge conflicts, sorry :/

igaskin and others added 8 commits August 1, 2016 00:44
* added secondary criteria so it doesn't jump from cluster to cluster when they're equally large

* added secondary criteria so it doesn't jump from cluster to cluster when they're equally large

* updated cluster example
Adding an Anyball item to the release config
@douglascamata
Copy link
Member

@z4ppy your merge is a bit messy, showing modifications that doesn't belong to your PR... but I really want your feature. Do you mind opening another PR?

@z4ppy
Copy link
Contributor Author

z4ppy commented Aug 1, 2016

I will redo :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.