-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pgoapi purge #3106
Pgoapi purge #3106
Conversation
I know my +1 doesn't count, but thorough testing reveals all works fine and dandy. +1 |
"medghaim commented 2 minutes from now" wizard! |
People are going to need to re-run requirements.txt as well as probably purge their db (unless we want to bother with writing migration scripts) |
Ew no. Delete pogom.db, re (is this from the future too?) |
"medghaim commented 2 minutes from now" time traveler |
Related #671 |
Yeah, invisiblek built off your earlier PR. Your commits are still up there somewhere! |
Modify
|
Nice. I'm not able to test this soon, but would be very happy when this is merged! Should @tejado do a release of this commit? |
Definitely runs. Going to compare pokemon amounts here in a few. |
LGTM so far so good. I'll let it churn overnight, see if anything weird pops |
Always a good sign when things run, @FrostTheFox :D |
Sometime during the overnight run I lost one of my |
I have 20 workers going, been running strong all night. |
Here we go:
That's causing the search_worker thread to dump out. Needs a bit of exception catching. |
Alright, ignore my issue, it's not really a pgoapi upgrade problem but a "I didn't handle thread exceptions well enough" problem. I'll task that in a separate PR |
LGTM -- I don't know if we hold off for the beehive misalignement or not though |
nobody else is seeing the misalignment at all? the locations i'm using literally have the exact lat or long and they're showing up misaligned =/ @medghaim any idea here? (see screenshot from above) |
I've fixed the reliability issues over in this a pr against this branch (that's the diff link excluding whitespace since I had to indent a lot for the fix). Should clear up and prevent any weird outliers for getting search threads lost. |
Can anyone give me good clear instructions on how to run more than 1 worker? simultaneously? That would be great! I obviously am doing something wrong and can't get it working on my end. |
- Handle exceptions better - Prevent search_workers from even fully exiting - High-load backoff is now backoff based instead of randomly assigned absolute - Logins will retry `login-retries` times before throwing an exception to cause the search_worker to create a new PgoAPI instance and start over
This fixes the hexes being off: tejado/pgoapi#171 |
pgoapi updated with the hex fix, latest commit pulls in that change +111111111111111111 |
@Crazy-Drew really not the place to be posting stuff like that |
* Use standard logging for this and for the check of the old pogom/pgoapi * Automatically remove pogom/pgoapi, regardless if its empty or not. Its not going to be useful anymore and will cause problems.
This looks ready. If anyone has any objections, speak now or forever handle issues from here on out. |
Yay! |
Also getting error when installing requirements.txt on line 18 for pgoapi, see gist https://gist.github.com/hack3rjack/4a95b33dd811721d8b91389eeb44590f |
@hack3rjack its just a warnings that depends on your python build, all fine with it |
ok then, thanks @aldarund |
log.info("Done!") | ||
|
||
# Ensure user has updated to the new api | ||
newpgoapiPath = os.path.join(os.path.dirname(__file__), "src/pgoapi") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not where pip installs pgoapi. In fact, there is no src/ directory.
Better to simply try importing pgoapi and catching whatever errors come up. We can also check pgoapi.__version__
if that is deemed necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go ahead and use your super brain to improve it then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will he is right, this check dont work and simply stop project from launching
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works perfectly fine here https://gist.github.com/invisiblek/f0e5f8b76eec1b23ebf1be3c5283072c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And? This is really braindead check. You basically rely that pip Will clone imto cuurent due and not clean it. This folder not even user, its just leftoff of installation . And recent pip Will delete this folder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*due - directory
*User - used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works awesome over here, definitely seeing way more pokemon now! I am loving this already!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in latest HEAD on develop.
In the future be a bit more respectful of people here. Calling anyone's code braindead is pretty fucking rude.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry. That was in the heat of the moment as the code was crashing right as i needed it.
I'll edit that comment and it wont happen again.
Kill our local copy of pgoapi and instead pull in a fresh copy from tejado's repo. Fixups along the way to handle the api changes.