Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 209. (Read 450523 times)
November 24, 2016, 05:18:43 PM
Could Lannister just log in and say "hi"? It's been a while…
November 24, 2016, 05:03:41 PM
Something like this!
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
I'll take a look at this. On my system the threads go back to minimal usage, but with the recent changes, I may have broken something. Should be pretty easy to fix.
I noticed it when I launched the miner when there was work online and waited until the work was finished! I will try to reproduce this once again.
There is a difference when there is no work vs work, but none eligible to be mined (i.e. no bounties left). I would guess on your system with no work, it idles, but with non-eligible work, it's still doing something...that's what I may have broken when I redid all the i/o logic.
Here it's reproducible when I just start the miner up with no work:
November 24, 2016, 04:54:39 PM
Something like this!
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
I'll take a look at this. On my system the threads go back to minimal usage, but with the recent changes, I may have broken something. Should be pretty easy to fix.
I noticed it when I launched the miner when there was work online and waited until the work was finished! I will try to reproduce this once again.
There is a difference when there is no work vs work, but none eligible to be mined (i.e. no bounties left). I would guess on your system with no work, it idles, but with non-eligible work, it's still doing something...that's what I may have broken when I redid all the i/o logic.
November 24, 2016, 04:45:32 PM
Something like this!
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
I'll take a look at this. On my system the threads go back to minimal usage, but with the recent changes, I may have broken something. Should be pretty easy to fix.
I noticed it when I launched the miner when there was work online and waited until the work was finished! I will try to reproduce this once again.
November 24, 2016, 04:31:24 PM
Something like this!
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
I'll take a look at this. On my system the threads go back to minimal usage, but with the recent changes, I may have broken something. Should be pretty easy to fix.
November 24, 2016, 03:27:07 PM
@coralreefer: agreed! I have still extended the error messages a bit so we have it easier in the future.
These are possible:
And of course a plain
if it's really a duplicate.
These are possible:
Code:
Proof of Work:
Duplicate unconfirmed transaction: work is already closed
Duplicate unconfirmed transaction: maximum pows per block reached
Duplicate unconfirmed transaction: work ran out of funds
Bounty Announcement:
Duplicate unconfirmed transaction: no more bounty announcement slots available
Bounty:
Duplicate unconfirmed transaction: work is already closed, you missed the reveal period
And of course a plain
Code:
Duplicate unconfirmed transaction
if it's really a duplicate.
Excellent! great work as usual. Later tonight, I'll update the miner to check for both "Duplicate" and ":", if it see's both, then I'll display the "discarded" message. Otherwise, I'll display the error message. Is that as you intended it?
Something like this!
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
November 24, 2016, 02:52:55 PM
Guys I've been away for a while. So apologies for the stupid question but are we able to claim our tokens yet?
Nope. No ETA yet, either.
November 24, 2016, 01:58:05 PM
Should be fairly easy to enable the port with a script on a Linux box VPS hosted no?
Im not good with Unix at all.
Im not good with Unix at all.
November 24, 2016, 01:53:08 PM
Any chance someone could make a script do deploy a node? I'll host it on a VPS, maybe others would too if it was dead simple.
That would be great ;-)
Right now we have a docker image which works pretty simple (http://elastic-project.com/installing_and_running_elastic) but I have no idea if the port 6876 would be externally reachable.
November 24, 2016, 01:50:03 PM
Any chance someone could make a script do deploy a node? I'll host it on a VPS, maybe others would too if it was dead simple.
November 24, 2016, 01:39:43 PM
The chain is moving finally (without doing git pull) but will recompile right now.
Because I can't redeem xel maybe someone could send me some test-xel : XEL-XFMU-85XU-V4S3-EZZY2
Thanks
P.S. I could set up one or two other nodes if you need them.
Because I can't redeem xel maybe someone could send me some test-xel : XEL-XFMU-85XU-V4S3-EZZY2
Thanks
P.S. I could set up one or two other nodes if you need them.
November 24, 2016, 01:31:59 PM
Hi,
I just updated my public node to 0.7.1 @ https://elastic.cryptnodes.site/index.html
Blockdownload isn't happening at the moment - still stuck at block #2
I tried to redeem my XEL but I get the same error like if I try to add/edit my userinfo :
Was there a sollution to this or did I missed it ?
Regards
I just updated my public node to 0.7.1 @ https://elastic.cryptnodes.site/index.html
Blockdownload isn't happening at the moment - still stuck at block #2
I tried to redeem my XEL but I get the same error like if I try to add/edit my userinfo :
Code:
Could not validate unsigned bytes returned by the server.
Was there a sollution to this or did I missed it ?
Regards
With only 3 test nodes it is really "instable" to kick off the blockchain.
To make things easy you could use this in your (at the moment empty) conf/nxt.properties
Code:
nxt.numberOfForkConfirmations=0
nxt.testnetNumberOfForkConfirmations=0
Also, please do a git pull - i have added some fixes! It should sync from there on!
Regarding the other error ... I am clueless, but I will take a look into it tonight.
November 24, 2016, 01:23:40 PM
Guys I've been away for a while. So apologies for the stupid question but are we able to claim our tokens yet?
November 24, 2016, 01:20:59 PM
@coralreefer: agreed! I have still extended the error messages a bit so we have it easier in the future.
These are possible:
And of course a plain
if it's really a duplicate.
These are possible:
Code:
Proof of Work:
Duplicate unconfirmed transaction: work is already closed
Duplicate unconfirmed transaction: maximum pows per block reached
Duplicate unconfirmed transaction: work ran out of funds
Bounty Announcement:
Duplicate unconfirmed transaction: no more bounty announcement slots available
Bounty:
Duplicate unconfirmed transaction: work is already closed, you missed the reveal period
And of course a plain
Code:
Duplicate unconfirmed transaction
if it's really a duplicate.
Excellent! great work as usual. Later tonight, I'll update the miner to check for both "Duplicate" and ":", if it see's both, then I'll display the "discarded" message. Otherwise, I'll display the error message. Is that as you intended it?
November 24, 2016, 01:16:44 PM
Hi,
I just updated my public node to 0.7.1 @ https://elastic.cryptnodes.site/index.html
Blockdownload isn't happening at the moment - still stuck at block #2
I tried to redeem my XEL but I get the same error like if I try to add/edit my userinfo :
Was there a sollution to this or did I missed it ?
Regards
I just updated my public node to 0.7.1 @ https://elastic.cryptnodes.site/index.html
Blockdownload isn't happening at the moment - still stuck at block #2
I tried to redeem my XEL but I get the same error like if I try to add/edit my userinfo :
Code:
Could not validate unsigned bytes returned by the server.
Was there a sollution to this or did I missed it ?
Regards
November 24, 2016, 01:15:04 PM
@coralreefer: agreed! I have still extended the error messages a bit so we have it easier in the future.
These are possible:
And of course a plain
if it's really a duplicate.
These are possible:
Code:
Proof of Work:
Duplicate unconfirmed transaction: work is already closed
Duplicate unconfirmed transaction: maximum pows per block reached
Duplicate unconfirmed transaction: work ran out of funds
Bounty Announcement:
Duplicate unconfirmed transaction: no more bounty announcement slots available
Bounty:
Duplicate unconfirmed transaction: work is already closed, you missed the reveal period
And of course a plain
Code:
Duplicate unconfirmed transaction
if it's really a duplicate.
November 24, 2016, 01:05:25 PM
Hi EK, I fixed the longpoll error in the miner and updated the github.
Please let me know if you find anything else.
Please let me know if you find anything else.
Looks amazing! One little "artefact" I noticed is this:
When the work is completed, the miner still tries to submit PoW for this work. The reason is that the longpoll did not yet fire to "see a new block" (because there was no block). The job is more closed because its funds went to zero. I think I should give back a better error message if the funds are gone, so we dont confuse it with the "20 POW limit".
See here
I agree that eventually we can enhance the messaging to tighten up the integration between the miner / server. But I think we may want to hold off on it for a bit until we see a much larger scale test (probably will only occur once we go to mainnet) in case we observe other scenarios that could influence our direction. People will just need to understand that this is still Beta (or even Alpha) and that issues like this will exists for a while in this initial version.
November 24, 2016, 12:49:19 PM
Hi EK, I fixed the longpoll error in the miner and updated the github.
Please let me know if you find anything else.
Please let me know if you find anything else.
Looks amazing! One little "artefact" I noticed is this:
When the work is completed, the miner still tries to submit PoW for this work. The reason is that the longpoll did not yet fire to "see a new block" (because there was no block). The job is more closed because its funds went to zero. I think I should give back a better error message if the funds are gone, so we dont confuse it with the "20 POW limit".
See here
November 24, 2016, 10:00:01 AM
Hi EK, I fixed the longpoll error in the miner and updated the github.
Please let me know if you find anything else.
Please let me know if you find anything else.
November 24, 2016, 09:39:40 AM
Does anyone else except @EK was successful in launching 0.7.0 node? (compiling from source, not docker image). By successful I mean that after start there are preserved connections to other nodes.
Compile from source and running wallet 0.7.0 fine.
Jump to: