Test Net for Advanced Users

[puppies]

Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one

the vps I'm using for testing graphene is just sitting around right now.  If you need peers to join you let me know. 

[clayop]

The test network has been delayed because we have a random crash in block production that we just now identified the cause of.   

It took me 1M blocks to reproduce the issue on my local test net!

Somewhat disappointed but it's understandable. Can you tell ETA?

[bytemaster]

The test network has been delayed because we have a random crash in block production that we just now identified the cause of.   

It took me 1M blocks to reproduce the issue on my local test net! 

[bulletproof]

Thanks puppies, will see how far I can get with that & leave 'flood_network' & other network commands until there is one

[puppies]

Just to follow up my ask in the Mumble - please consider getting this/a test net up again whilst one for the GUI is being worked on. I have been using it to test the cli_wallet API with the 2.0 version of my bitshares Ruby Gem & can't proceed until it is back up 

Thx & have a good weekend all

is there a reason you need an actual network up?  Couldn't you just run a local instance on and test that way?

[bulletproof]

Just to follow up my ask in the Mumble - please consider getting this/a test net up again whilst one for the GUI is being worked on. I have been using it to test the cli_wallet API with the 2.0 version of my bitshares Ruby Gem & can't proceed until it is back up 

Thx & have a good weekend all

[bytemaster]

I just killed the chain.        Will be back with a new test network later this week.

You certainly need to think about your wording .. unless you want people to believe you actually CAN kill the blockchain.

I assume you just switched of your initial witness nodes ..

LOL, yes.   

[abit]

several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to  restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem.    We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.

Can't wait. Where is the new code?

[bulletproof]

Get this error:

Code: [Select]

10 assert_exception: Assert Exception
operations.size() > 0: A transaction must have at least one operation
    {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}}
    th_a  transaction.cpp:51 validate

    {"name_or_id":"the-ae"}
    th_a  wallet.cpp:2762 import_balance

when I try to import balance...

pretty sure that means that key has no balance.

Getting this same error with test1 build while trying to import the 'nathan' account - am I doing something wrong? Witness node is running and currently at #260,000 (not producing blocks). Am I just not synced yet?

Code: [Select]

unlocked >>> import_balance nathan [5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3] true
import_balance nathan [5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3] true
1417187ms th_a       wallet.cpp:2721               import_balance       ] balances: []
10 assert_exception: Assert Exception
operations.size() > 0: A transaction must have at least one operation
    {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}}
    th_a  transaction.cpp:51 validate

    {"name_or_id":"nathan"}
    th_a  wallet.cpp:2762 import_balance
unlocked >>>
Thx

EDIT: Just seen head block is at 427293 - will wait a while 

[xeroc]

I just killed the chain.        Will be back with a new test network later this week.

You certainly need to think about your wording .. unless you want people to believe you actually CAN kill the blockchain.

I assume you just switched of your initial witness nodes ..

[bytemaster]

I just killed the chain.        Will be back with a new test network later this week.

[bytemaster]

several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to  restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

Eric checked in some fixes that may address this particular problem.    We do have logic to request from another node, but the timeouts were still tuned to BTS 1 timeframes so we reduced the timeout for BTS 2.

[lafona]

Just got my seed node up and running, the address is 73.182.245.244:32015
If you have any issues, let me know, it is on a raspberry pi, so I am not sure how long it will last, but I will be checking up on it regularly.

[alt]

several times, my witeness node blocked at some block
I watch the p2p log, it received block 419543, then 419544, then missed 419545, then received 419546, .......
and it will never receive block 419545, I have to  restart witness node, then it can request the block from other node.
I think we need a logic, when the witness node have missed a block more than 10 blocks, it should request from other node.

[lafona]

Yeah it is still the Aug-20 genesis file and afaik the chain-id is d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083 although I have been having some slight problems getting synced and staying on the chain. It was producing blocks earlier though.