Skip to content
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

Not clear how farm mechanizm works #693

Open
strogiyotec opened this issue Feb 4, 2019 · 4 comments
Open

Not clear how farm mechanizm works #693

strogiyotec opened this issue Feb 4, 2019 · 4 comments
Labels

Comments

@strogiyotec
Copy link
Contributor

It's not clear to my how farm class works.
Firstly , method start create endless loop which call methods cycle and cleanup(right?)
Secondly , method cleanup save new empty score to file save(threads, [Score.new(host: host, port: port, invoice: @invoice, strength: @strength)]) (why do we need to save empty score ?) then we reject scores by threads names scores.reject { |s| @threads.exists?(s.to_mnemo) }(why do we need it ?) and finally we add new score to pipeline
Thirdly , method cycle we pop score from pipeline, assign score's name to thread name , and then we get new score using farmer farmer.up(s) and save this score to file.
The main incomprehensible part is cleanup . I didn't find any explanation in White Paper so please add more comments in source code or put your answer here.
Thanks in advance

@0crat
Copy link
Collaborator

0crat commented Feb 4, 2019

@yegor256/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Feb 4, 2019

@strogiyotec/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@strogiyotec strogiyotec changed the title Not clear how method farm mechanizm works Not clear how farm mechanizm works Feb 4, 2019
@0crat 0crat removed their assignment May 5, 2019
@0crat 0crat added the scope label May 5, 2019
@0crat
Copy link
Collaborator

0crat commented May 5, 2019

Job #693 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented May 5, 2019

Bug was reported, see §29: +15 point(s) just awarded to @strogiyotec/z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants