(1) Enable hash server usage (2) Introduce key scheduler #1677
Conversation
The KeyScheduler class in scheduler.py serves as the basic building block for more complex scheduling in the future (throttling by ms, query remaining hashes, etc). Usage is similar to any args that are usually parsed as a list: ex: -hk KEY_1 -hk KEY_2 -hk KEY_3
|
I'm assuming I can't submit a PR of a PR can I? :) |
|
This needs to be merged as soon as possible so the people that wants to use .51 can start using it. |
|
@sclo012 u could always merge it on ur own if you want it that badly! |
|
@ChowderChow are you going to merge my Hash Key status page for -ps into this? |
|
@hokiepokedad that will come after basic functionality is merged, though I'd prefer if you'd be the one to open a separate PR for that seeing as most of the code was yours. |
|
@ChowderChow sounds good |
|
Hope we are going to see this one merge soon :) |
|
i get this when i want to use -hk 2017-01-08 11:39:04,543 [ search-worker-2][ search][ ERROR] Exception in search_worker under account ****** Exception message: . |
|
I get the same exception as @fufufabulous |
|
Thanks it works now, how can we know the amount of requests/min ? |
| # Create the key scheduler. | ||
| if args.hash_key: | ||
| key_scheduler = schedulers.KeyScheduler(args.hash_key).scheduler() | ||
|
|
There was a problem hiding this comment.
If turning the other logs to debug, then maybe a single info message here to say that hash server is enabled?
* origin/develop: Thread safe webhooks & minor enhancements. (RocketMap#1710) Update step distance according to pgoapi changes & test results. (RocketMap#1707) Updated cachetools. (RocketMap#1705) [Readme] Remove old paypal stuff (1) Enable hash server usage (2) Introduce key scheduler (RocketMap#1677) # Conflicts: # pogom/models.py # pogom/schedulers.py
) * (1) Enable hash server usage (2) Introduce key scheduler The KeyScheduler class in scheduler.py serves as the basic building block for more complex scheduling in the future (throttling by ms, query remaining hashes, etc). Usage is similar to any args that are usually parsed as a list: ex: -hk KEY_1 -hk KEY_2 -hk KEY_3 * flake8 * Missing periods in comments * Update requirements.txt to use 0.51 API. * Get pgoapi from commit rather than develop branch. * Small debugging changes.
Description
The KeyScheduler class in scheduler.py serves as the basic building
block for more complex scheduling in the future (throttling by ms, query
remaining hashes, etc). Similar to how BaseScheduler is used for more complex scan methods.
Usage is similar to any args that are usually parsed as a list:
ex:
-hk KEY_1 -hk KEY_2 -hk KEY_3Motivation and Context
Enables 0.51 API usage.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: