Fork?

patmast3r · September 3, 2015, 1:16pm

Is it known what triggered this fork?

afaik it's already fixed as well. Devs had an eye on some weird behaviour the whole time.

Devs are on the ball as usual. ;)

Yes. Things like this will happen. So long is it's in BETA or for the future on the testnet this shouldn't concern people. That's what these things are for and major changes almost always come with bugs.

Well now we can shove this in the faces of those who complain launch is taking too long ;) nem would be crashing in value right now if we were live.

I think most people with working brains are realising that making sure everything works is the most important thing. Far more important than launchin until a certain deadline.

Crypti launched very early - pretty much broke down. Have they resolved their problems by now ?

NODE launched absurdly early - well...look at it.

Those projects could still turn out to be awesome but they will have a very very hard time recovering from these things.

rockethead · September 3, 2015, 1:16pm

Guys, spam the transactions, do whatever. I'd rather we launch later and clean up all the major bugs. I am not concerned even if the launch is pushed back a month.

Most important it is solid as a rock!

As usual here is my song for that;)

http://www.dailymotion.com/video/xsd7v_ashford-simpson-solid_music

nxkoil · September 3, 2015, 1:16pm

So, which is real chain? on chain.nem.ninja? Comparing with chain explorer I'm 54 blocks ahead. Do I need to delete my db and download from scratch?

Alice 4 is having the real (best) chain: http://alice4.nem.ninja:7890/chain/last-block
The block explorer is on a fork.

So, I'm good? Last block here is the same as Alice 4 :)

My NCC was about 5 blocks behind of Alice4.
Then 2 blocks, then after some minutes 1 block
Now they both are in 9711. ... still ...

Refreshed my browser: still 9711.
Now NCC: "NIS is synchronizing. At block 9711, est. less than 1 day behind."
And Alice 9712 ...

now both 9714.

Thingamajig · September 3, 2015, 1:16pm

Is it known what triggered this fork?

afaik it's already fixed as well. Devs had an eye on some weird behaviour the whole time.

Devs are on the ball as usual. ;)

Yes. Things like this will happen. So long is it's in BETA or for the future on the testnet this shouldn't concern people. That's what these things are for and major changes almost always come with bugs.

Well now we can shove this in the faces of those who complain launch is taking too long ;) nem would be crashing in value right now if we were live.

I think most people with working brains are realising that making sure everything works is the most important thing. Far more important than launchin until a certain deadline.

Crypti launched very early - pretty much broke down. Have they resolved their problems by now ?

NODE launched absurdly early - well...look at it.

Those projects could still turn out to be awesome but they will have a very very hard time recovering from these things.

Agreed, and such crypto's that are released prematurely are not giving any confidence in them as a currency or platform. It's the damage to the reputation that is going to be the most catastrophic and long lasting.

jabo38 · September 3, 2015, 1:16pm

I agree too. Node and Crypti both really messed themselves up. Qora too is struggling so badly it is in terrible shape too.

In the new improved PoS coin wars, these are the only three challengers besides NEM to come after NXT. It is very clear that NEM is going to be way better than they are. Having an extensive beta where we spam the network is a big part of this. I think people can really see the wisdom of waiting and thoroughly testing the software first before going live.

Jaguar0625 · September 3, 2015, 1:16pm

In the new improved PoS coin wars, these are the only three challengers besides NEM to come after NXT.

Which ones?

Jaguar0625 · September 3, 2015, 1:16pm

Also, this is why we do testing :D.

3x2 · September 3, 2015, 1:16pm

In the new improved PoS coin wars, these are the only three challengers besides NEM to come after NXT.

Which ones?

NODE,XCR and QORA, dint he said that? :P

kodtycoon · September 3, 2015, 1:16pm

In the new improved PoS coin wars, these are the only three challengers besides NEM to come after NXT.

Which ones?

NODE,XCR and QORA, dint he said that? :P

They are not and most likely will never be in the same league as nem...

jabo38 · September 3, 2015, 1:17pm

Yes. That's what I said. Right now it's looking only like NEM AND NEM only.

ButtCrack · September 3, 2015, 1:17pm

Just upgraded to the latest beta 0.4.12 straight from 0.4.9.
Looks like it downloaded the block chain from scratch although I copied the old one into the data directory.
Or I forgot to copy it…
Anyway, as everybody already said, testing is a must.
That is stress testing till breaking point is reached, rough and dirty.
But its funny or should I say retarded to release a program to fast.
There is a long list of these.
As of writing block height 10451, not sure if I am on the right fork ?

And hush hush about Qora, smaragda is lurking around.
A real genius in motivating ppl.
According to him the dev of Qora is a genius…
That's why at release v18 its still gets forked and other minor issues.

rockethead · September 3, 2015, 1:17pm

Just upgraded to the latest beta 0.4.12 straight from 0.4.9.
Looks like it downloaded the block chain from scratch although I copied the old one into the data directory.
Or I forgot to copy it...
Anyway, as everybody already said, testing is a must.
That is stress testing till breaking point is reached, rough and dirty.
But its funny or should I say retarded to release a program to fast.
There is a long list of these.
As of writing block height 10451, not sure if I am on the right fork ?

And hush hush about Qora, smaragda is lurking around.
A real genius in motivating ppl. ;)
According to him the dev of Qora is a genius...
That's why at release v18 its still gets forked and other minor issues.

According to others, our devs are the original Satoshi. :P

That's why they could solve the fork, synchronisation and some other stuff within a week. 8)

BloodyRookie · September 3, 2015, 1:17pm

The generation times for blocks are rising again, please everyone check if he/she is on a fork.

@rigel: you seem to have a script to generate transactions. Could you share it with us?

kodtycoon · September 3, 2015, 1:17pm

what does this mean? im stuck at block 10081 aswell im guessing because of this error.

Oct 28, 2014 1:11:52 AM org.nem.nis.a.c.ht afterCompletion INFO: exiting /node/active-peers/max-chain-height [127.0.0.1] Oct 28, 2014 1:12:02 AM org.nem.core.connect.HttpMethodClient a WARNING: forcibly aborting request to http://5.249.147.16:7890/chain/blocks-after Oct 28, 2014 1:12:02 AM org.nem.core.async.NemAsyncTimerVisitor b WARNING: Timer SYNC raised exception: java.util.concurrent.CancellationException java.util.concurrent.CompletionException: java.util.concurrent.CancellationException at java.util.concurrent.CompletableFuture.internalComplete(Unknown Source) at java.util.concurrent.CompletableFuture$ThenApply.run(Unknown Source) at java.util.concurrent.CompletableFuture.postComplete(Unknown Source) at java.util.concurrent.CompletableFuture.cancel(Unknown Source) at org.nem.core.connect.HttpMethodClient$a.cancelled(HttpMethodClient.java:207) at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:145) at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:151) at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.cancel(DefaultClientExchangeHandlerImpl.java:279) at org.apache.http.client.methods.AbstractExecutionAwareRequest.abort(AbstractExecutionAwareRequest.java:85) at org.nem.core.connect.HttpMethodClient.a(HttpMethodClient.java:128) at org.nem.core.connect.HttpMethodClient$$Lambda$120/3737718.accept(Unknown Source) at java.util.concurrent.CompletableFuture$ThenAccept.run(Unknown Source) at java.util.concurrent.CompletableFuture.postComplete(Unknown Source) at java.util.concurrent.CompletableFuture.complete(Unknown Source) at org.nem.core.async.e.a(SleepFuture.java:19) at org.nem.core.async.e$$Lambda$119/33236689.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.util.concurrent.CancellationException ... 19 more

Jaguar0625 · September 3, 2015, 1:17pm

what does this mean? im stuck at block 10081 aswell im guessing because of this error.

[code]Oct 28, 2014 1:11:52 AM org.nem.nis.a.c.ht afterCompletion
INFO: exiting /node/active-peers/max-chain-height [127.0.0.1]
Oct 28, 2014 1:12:02 AM org.nem.core.connect.HttpMethodClient a
WARNING: forcibly aborting request to http://5.249.147.16:7890/chain/blocks-after
Oct 28, 2014 1:12:02 AM org.nem.core.async.NemAsyncTimerVisitor b
WARNING: Timer SYNC raised exception: java.util.concurrent.CancellationException
java.util.concurrent.CompletionException: java.util.concurrent.CancellationException
at java.util.concurrent.CompletableFuture.internalComplete(Unknown Source)
at java.util.concurrent.CompletableFuture$ThenApply.run(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.cancel(Unknown Source)
at org.nem.core.connect.HttpMethodClient$a.cancelled(HttpMethodClient.java:207)
at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:145)
at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:151)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.cancel(DefaultClientExchangeHandlerImpl.java:279)
at org.apache.http.client.methods.AbstractExecutionAwareRequest.abort(AbstractExecutionAwareRequest.java:85)
at org.nem.core.connect.HttpMethodClient.a(HttpMethodClient.java:128)
at org.nem.core.connect.HttpMethodClient$$Lambda$120/3737718.accept(Unknown Source)
at java.util.concurrent.CompletableFuture$ThenAccept.run(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.complete(Unknown Source)
at org.nem.core.async.e.a(SleepFuture.java:19)
at org.nem.core.async.e$$Lambda$119/33236689.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.CancellationException
... 19 more
[/code]

Can you upload your NIS log somewhere and/or join #ournem on IRC?

kodtycoon · September 3, 2015, 1:17pm

what does this mean? im stuck at block 10081 aswell im guessing because of this error.

[code]Oct 28, 2014 1:11:52 AM org.nem.nis.a.c.ht afterCompletion
INFO: exiting /node/active-peers/max-chain-height [127.0.0.1]
Oct 28, 2014 1:12:02 AM org.nem.core.connect.HttpMethodClient a
WARNING: forcibly aborting request to http://5.249.147.16:7890/chain/blocks-after
Oct 28, 2014 1:12:02 AM org.nem.core.async.NemAsyncTimerVisitor b
WARNING: Timer SYNC raised exception: java.util.concurrent.CancellationException
java.util.concurrent.CompletionException: java.util.concurrent.CancellationException
at java.util.concurrent.CompletableFuture.internalComplete(Unknown Source)
at java.util.concurrent.CompletableFuture$ThenApply.run(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.cancel(Unknown Source)
at org.nem.core.connect.HttpMethodClient$a.cancelled(HttpMethodClient.java:207)
at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:145)
at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:151)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.cancel(DefaultClientExchangeHandlerImpl.java:279)
at org.apache.http.client.methods.AbstractExecutionAwareRequest.abort(AbstractExecutionAwareRequest.java:85)
at org.nem.core.connect.HttpMethodClient.a(HttpMethodClient.java:128)
at org.nem.core.connect.HttpMethodClient$$Lambda$120/3737718.accept(Unknown Source)
at java.util.concurrent.CompletableFuture$ThenAccept.run(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.complete(Unknown Source)
at org.nem.core.async.e.a(SleepFuture.java:19)
at org.nem.core.async.e$$Lambda$119/33236689.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.CancellationException
... 19 more
[/code]

Can you upload your NIS log somewhere and/or join #ournem on IRC?

http://s000.tinyupload.com/?file_id=56021954187736550515

deleted the data base and started fresh and same thing happened again..

http://s000.tinyupload.com/?file_id=49982572587063343436

rigel · September 3, 2015, 1:17pm

The generation times for blocks are rising again, please everyone check if he/she is on a fork.

I'm not on a fork (or at least in the same fork as Blockchain Explorer)

@rigel: you seem to have a script to generate transactions. Could you share it with us?

I have this in my /etc/cron.hourly, very raw but does the job:

[code]
#!/bin/bash

tr -d - </root/spam_nem/nem_addresses | while read ADDR
do
nc localhost 8989 <<EOF
POST /ncc/api/wallet/account/transaction/send HTTP/1.1
Host: localhost
Content-type: application/json
Content-length: 240

{"wallet":"betatest","password":"beta","account":"TCRIGEL6TUKDGDVBXIVY3HQNADAV6JZMGKNPL23Y","recipient":"$ADDR","amount":99999999,"fee":9000000,"message":"no more empty blocks","encrypt":0,"hours_due":12}

EOF
sleep 40
done
[/code]

jabo38 · September 3, 2015, 1:17pm

According to others, our devs are the original Satoshi. :P

That's why they could solve the fork, synchronisation and some other stuff within a week. 8)

We just need that tweet from Nick Szabo now. Hahahaha. I was actually lucky enough to send him a message and he responded. It was me just being a suck-up to him, but it was still pretty awesome.

BloodyRookie · September 3, 2015, 1:17pm

what does this mean? im stuck at block 10081 aswell im guessing because of this error.

[code]Oct 28, 2014 1:11:52 AM org.nem.nis.a.c.ht afterCompletion
INFO: exiting /node/active-peers/max-chain-height [127.0.0.1]
Oct 28, 2014 1:12:02 AM org.nem.core.connect.HttpMethodClient a
WARNING: forcibly aborting request to http://5.249.147.16:7890/chain/blocks-after
Oct 28, 2014 1:12:02 AM org.nem.core.async.NemAsyncTimerVisitor b
WARNING: Timer SYNC raised exception: java.util.concurrent.CancellationException
[/code]

Means you run into a timeout. That is the reason for not being able to sync.
We either have to set the timeout to a higher value or speed up things. I will look into that in more detail today.