I should write a style guide for bitHopper and then list the 60% of the code I want to rewrite to follow the style guide.
work.py is an especially big mess.
I don't have access to my test machine but has anyone been testing with trunk? If its working I can turn it on in the repo remotely.
Topic: bitHopper: Python Pool Hopper Proxy - page 125. (Read 355689 times)
Um... Oops? I expected the call to be in getwork_Store. Its fixed now although not turned on in bleeding edge.
It was a fair assumption by the rules of encapsulation.
so far that is the only reject I have gotten and It came when i switched to your fork without turning off my miner.. but so far everything is looking golden.
Um... Oops? I expected the call to be in getwork_Store. Its fixed now although not turned on in bleeding edge.
Infinity percentage of rejects... hmm might effect my expected award a tad bit.
That is a good offset to my 5500 shares / 0 stales
@gnaget depends on observers point of view...
if you go with the flow, I think not
if you go with the flow, I think not
Infinity percentage of rejects... hmm might effect my expected award a tad bit.
uuuhh a shiver passed on my spine, this will be a little hopping beast guys. When it will reach critical mass I'm gonna see a handful of proud coders
Isn't critical mass bad?
Um bad merge meant I left in one conflict...
The difference is I actually prune the store so there isn't a giant memory leak. And I cleaned up work a little bit.
Other than that the code is the same.
User shares are over the life of the database.
The difference is I actually prune the store so there isn't a giant memory leak. And I cleaned up work a little bit.
Other than that the code is the same.
User shares are over the life of the database.
okay
uuuhh a shiver passed on my spine, this will be a little hopping beast guys. When it will reach critical mass I'm gonna see a handful of proud coders
The difference is I actually prune the store so there isn't a giant memory leak. And I cleaned up work a little bit.
?? My pruning function was working when I committed it
Edit: I see what you did, I put the LoopingCall in bitHopper.main() to keep it consistent
Edit Edit: Yup, you have 2 LoopingCalls
Um bad merge meant I left in one conflict...
The difference is I actually prune the store so there isn't a giant memory leak. And I cleaned up work a little bit.
Other than that the code is the same.
User shares are over the life of the database.
The difference is I actually prune the store so there isn't a giant memory leak. And I cleaned up work a little bit.
Other than that the code is the same.
User shares are over the life of the database.
funny to see how some ppl take their measures against hoppers...
edit: forgot to tell, it's c00w's hopper but I like gray more than "that" blue hehe
edit: forgot to tell, it's c00w's hopper but I like gray more than "that" blue hehe
c00w: I just saw you have user data in the data site. What are the number representative of, and over what period?
4500 / 0
4500 / 0
Did you get it working? I made some changes to flow, but I know you made your own fixes, so I don't know how similar our code bases are
testing as I'm speaking ...
edit: ups I'll wait on this one, it's the "bad" merge
Who all is testing the getwork store? I'm getting stales, but only when I am not looking. I reset my db, and added some logging to try to debug it, and I'm at 1100 shares / 0 stales. If I stop watching, suddenly I'll get a run of stales and I'll miss it
Edit: 1800 shares / 0 stales
Edit: 1800 shares / 0 stales
link?
here's one https://github.com/gnaget/bitHopper/commit/742a5082862870b63ac3e95432c97d1223ece030
@gnaget don't miss the stales pls
2700 shares / 0 stales. I would say I'll actually MISS them...
Edit: 3300 shares / 0 stales. I'm digging this
Who all is testing the getwork store? I'm getting stales, but only when I am not looking. I reset my db, and added some logging to try to debug it, and I'm at 1100 shares / 0 stales. If I stop watching, suddenly I'll get a run of stales and I'll miss it
Edit: 1800 shares / 0 stales
Edit: 1800 shares / 0 stales
link?
here's one https://github.com/gnaget/bitHopper/commit/742a5082862870b63ac3e95432c97d1223ece030
@gnaget don't miss the stales pls
Who all is testing the getwork store? I'm getting stales, but only when I am not looking. I reset my db, and added some logging to try to debug it, and I'm at 1100 shares / 0 stales. If I stop watching, suddenly I'll get a run of stales and I'll miss it
Edit: 1800 shares / 0 stales
Edit: 1800 shares / 0 stales
link?
Who all is testing the getwork store? I'm getting stales, but only when I am not looking. I reset my db, and added some logging to try to debug it, and I'm at 1100 shares / 0 stales. If I stop watching, suddenly I'll get a run of stales and I'll miss it
Edit: 1800 shares / 0 stales
Edit: 1800 shares / 0 stales
Jump to: