|
Can you post a log of the looping import calls? Or Pm it to me?
|
|
|
|
|
@crashing with interpolate error
That should be fixed. An unnamed person who wasn't me moved something down three lines.
|
|
|
|
|
v0.1.8 is tagged. It should be quite stable and the auth bug is fixed. --p2pLP is still a mess.
|
|
|
|
|
@--nolp
Old option for when client side LP was broken for some people. I think I removed it.
|
|
|
|
|
@auth arguments
auth was meant to be purely optional. It is currently purely optional in bleeding edge and I think the previous version.
|
|
|
|
|
The 2nd one gets caught by our monitoring of API's.
|
|
|
|
|
Its right about 50% of the time. And people are working to try and increase that.
|
|
|
|
|
You can put a penalty on deepbit if you've done the analysis for your location and determined it is getting too many blocks. Or any other site. Especially if there LP is super slow or delayed.
|
|
|
|
|
@whoever wanted an lp_penalty option:
I added it. It is lp_penalty : seconds.
|
|
|
|
|
@r2edu
Are you seeing any errors on the front end?
Lp Penalty?
Sure.
Oh and there already is a mine_nmc...
|
|
|
|
|
Oh and if you want to integrate all the info on nmc etc... into the difficulty module including prices that would be awesome. There already is nmc difficulty and adding everything else should be pretty quick.
|
|
|
|
|
@Muyoso
Reducing the number of getworks?
We are working on it. Also issues with scheduling are confusing and I need to rewrite the whole scheduler system. Which scheduler are you using?
@enmaku
Its not very hard. Someone just has to code it.
|
|
|
|
|
@magnet
Did you get any errors on the bithopper side?
@simonk
I don't have enough access to my test machine to figure out the real issues. But it appears that it doesn't work for me.
|
|
|
|
|
Um, there is an issue with large amounts of hashing power getting pumped through bitHopper on arsbitcoin. If you update your twisted to the bleeding edge twisted it may fix it. How many GH/s are you pushing through it?
|
|
|
|
|
Either way we are currently timing out after 30 seconds instead of the more reasonable 5. So it works okay for smaller setups but not very well for people with lots of hashes.
|
|
|
|
|
Hm... I guess we need to have a timeout on getwork requests...
Um and I figured out how to add it. But it only works with new versions of twisted. As in bleeding edge.
|
|
|
|
|
Um, I think those errors come from burps patch. I'm toning it down to 2 retries and then sleep.
EDIT: Um... I just woke up. Not sure why I'm going back to sleep.
|
|
|
|
|
Whine on his forums. Especially if he steals you coins.
|
|
|
|
|
Show Posts
