elective-stereophonic
elective-stereophonic
[CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Pages: [1] 2  All

Author Topic: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)  (Read 6386 times)

HolgerD77

  • Core Dev
  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile

Introduction

Hi everyone,
as you might already know if you followed these two threads:
https://nxtforum.org/general-discussion/(core)-release-or-not-release/
https://nxtforum.org/general-discussion/(core)-edge-cases-for-1-5-6e/

we will have a final round of testing focusing on phasing and generally finding severe bugs before we release 1.5 on mainnet (see threads above for context, motivation: https://nxtforum.org/general-discussion/(core)-release-or-not-release/msg178939/#msg178939).

Thanks to @jl777 and other guys from the Destroyer fund we have a bounty of 25.000 NXT available for this testing.

Test Procedure

What we need you to do is:
  • Download latest 1.5 experimental release
  • Go to client/API on testnet
  • Pick up a feature/area you want to cover (Asset Exchange Phasing, File Upload, Monetary System Phasing, ...)
  • Announce here what you are working on
  • Run various test cases/scenarios you can think of ("Phased asset transfer", "phased asset sell", "phased divident payment", ...)
  • Write down your results
Report Format

Would be great if you could write down your results in a form similar to:

A1 ...
A2 ...
A3 Transfer Asset, Phasing BY-Account, Selling in Between
Test Description:
An asset is transfered from account A to account B, C has to approve the transaction at height x. Before transaction finishes it is tested to sell the same asset units on the asset exchange
Observed Behaviour:
UI: This is not possible and prevented in the UI, API: The API returns an error saying that...
Evaluation:
Behaviour seems normal/as expected


This would help us to replicate your results. Also write down things that worked!

Bounties 25.000 NXT

One part of the bounties is for testing various cases of phasing for different transaction types:

- Test phasing itself: min. 12 test cases, 2.500 NXT
- Asset Exchange: min. 12 test cases, 2.500 NXT
- Monetary System: min. 12 test cases, 2.500 NXT
- Voting System: min. 8 test cases, 1.500 NXT
- Aliases/Messaging: min. 8 test cases, 1.500 NXT
- Marketplace: min. 12 test cases, 2.500 NXT
- Balance Leasing/Payment/Other: min. 8 test cases, 1.500 NXT

Total: 14.500 NXT


The other part is for general finding of (severe) bugs.

Total: 10.500 NXT

So bounties are paid for test reports in the form I described above, covering a minimum of a certain number of different test cases. Test cases doesn't have to lead to errors or bugs, it is also ok if you just tested a certain uncommon scenario worth testing and discovered that everything behaved like expected.

Bounties are paid two weeks after 1.5 mainnet release, non-used bounties will be paid back to Destroyer fund.

Practical Instructions

@Daedalus posted some great instructions on how to use the testnet and where to start:
https://nxtforum.org/general-discussion/price-speculation/msg179076/#msg179076

Summing Up

So again, this is really important and it would be great if you join testing and help making 1.5 a success!

« Last Edit: May 20, 2015, 08:15:52 am by HolgerD77 »
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

xchrix

  • Guest
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #1 on: May 17, 2015, 02:29:56 pm »

tweeted about this: https://twitter.com/cryptocoinchart/status/599944259211505664
unfortunately i am stuck with too much work and dont have any time left.
is there an easy way to deposit something to testing funds?
Logged

HolgerD77

  • Core Dev
  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #2 on: May 17, 2015, 04:21:04 pm »

tweeted about this: https://twitter.com/cryptocoinchart/status/599944259211505664
unfortunately i am stuck with too much work and dont have any time left.
is there an easy way to deposit something to testing funds?

Maybe contact @jl777/Destroyer fund for that.
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #3 on: May 17, 2015, 08:36:27 pm »

Alias testing:

--- Phased alias creation ---
Created the same alias twice using phased transactions. The first alias was phased to a later block than the 2nd one.
The 2nd alias has been registered. The 1st alias is still phased, will expire in 7000 blocks.
So far so good.  Yeesssssss.

--- Sell alias phased then delete the alias before sell finish height
a. Submitted a phased alias sell #15879770201351680474
b. Deleted the alias #16258956003108435311
c. When the phased sell reached its finish height it wasn't executed, the following message appear in the log "At height 291999 phased transaction 15879770201351680474 no longer passes validation: Alias hasn't been registered yet: Yodayod, will not apply"

Looks good, the only thing, change is in the message, would I "Alias hasn't been registered yet or has been deleted"
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #4 on: May 17, 2015, 08:48:15 pm »

Now transaction #15879770201351680474 (The one which is approved but invalid.  Herh herh herh.) shows 0/1 approvals ...
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #5 on: May 17, 2015, 09:02:27 pm »

Also tried another sequence:
1. Phased asset delete
2. Asset transfer
3. When the phased delete reached its height, got the following message I:
At height 292024 phased transaction 10111445188594410393 no longer passes validation: Alias doesn't belong to sender: yodayod, will not apply

This is correct except that the finish height for transaction 10111445188594410393 is 292025 so it looks like it was executed one block ahead of time.
Hmmmmmm. Seek advice you must !
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #6 on: May 17, 2015, 09:08:37 pm »

To summarize, found two problems I so far:  Hmmmmmm.
1. Phasing transactions are executed one block before their finish height.
2. Approved but invalid phasing transactions are displayed as 0/1 approvals in the UI.
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #7 on: May 18, 2015, 07:35:03 am »

When transactions in block 292025 are being validated, the blockchain height is still 292024. The other problem should be fixed in the UI, as for transactions that became invalid counting of approvals is not performed at all, it should not attempt to display the approvals count.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

HolgerD77

  • Core Dev
  • Sr. Member
  • ****
  • Karma: +49/-0
  • Offline Offline
  • Posts: 299
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #8 on: May 18, 2015, 10:41:17 am »

2. Approved but invalid phasing transactions are displayed as 0/1 approvals in the UI.

Will have a look at that, thanks for reporting!
Logged
NXT-AQ9F-JC4F-NCM2-4JSXZ

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #9 on: May 18, 2015, 08:28:55 pm »

Submitted a phased asset transfer with voting model by asset, tx#15049183727575150927
From some reason I cannot approve the transaction, getting "Poll voting finishes at height 292976 before transaction validation height 292978"
Why did the server accept the transaction if it can never get approved ?
I don't recall setting a validation height how was it calculated ?

On another note, I see in the JavaScript console the following error "TypeError: current_balances is undefined nrs.js:1126" probably a simple null reference.
“Train yourself to let go of everything you fear to lose.”
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #10 on: May 18, 2015, 08:46:31 pm »

The asset sell/buy modals support not "Advanced" Dialog so, no way to test phasing of these important transactions, there is.  Hmmmmmm.
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #11 on: May 18, 2015, 08:57:41 pm »

Phased lease balance dialog is not scrollable so in some configurations you cannot get to the "Lease" button. Pressing Ctrl+- to make the content smaller works around this problem.
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #12 on: May 18, 2015, 08:59:43 pm »

In the transaction info dialog, phasing tab, the quorum and min_balance fields does not respect the asset decimal positions. Some strings are not translated on this tab.
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 14.500 NXT Bounty
« Reply #13 on: May 19, 2015, 09:17:27 pm »

Submitted a phased asset transfer with voting model by asset, tx#15049183727575150927
From some reason I cannot approve the transaction, getting "Poll voting finishes at height 292976 before transaction validation height 292978"
Why did the server accept the transaction if it can never get approved ?
I don't recall setting a validation height how was it calculated ?
This phased transaction was included in block 292974, and finishes at height 292976. It was only possible to approve it if the approval transaction got accepted at height 292975. The error message is not very clear, but the validation height refers to the height at which the approval transaction is being validated, in this case it means the current blockchain height was 292978 when the approval was submitted, and this is after the finish height. (If the approval transaction itself was phased, its finish height would have been required to be before the phased transaction finish height, which could be both in the future, this is why the error message is more generic rather than simply saying that the phased transaction has finished).
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
« Reply #14 on: May 20, 2015, 08:47:23 am »

The ApproveTransaction modal should not open in the following cases:
1. The transaction to approve is still unconfirmed (otherwise you get the following cryptic error when submitting "Invalid phased transactionFullHash")
2. In case the finish height of the transaction to approve has passed.
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
« Reply #15 on: May 20, 2015, 10:50:53 am »

Another annoyance is messages like "Incorrect phasing finish height". What incorrect is about this parameter ?
If the parameter is numeric and I submitted a non numeric value tell:
"Incorrect phasing finish height, value <value> has to be numeric"
If the value is numeric but has to be bigger than or smaller than something tell me:
"Incorrect phasing finish height, value <value> has to be bigger than <min>" or "... smaller than <max>"
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
« Reply #16 on: May 20, 2015, 11:10:28 am »

Tested setting currency activation height lower than phasing finish, received "Reservable currency activation height 294670 not higher than transaction apply height 294671". Good catch devs.
Logged

yoda

  • Jr. Member
  • **
  • Karma: +13/-0
  • Offline Offline
  • Posts: 26
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
« Reply #17 on: May 20, 2015, 11:11:47 am »

Something is wrong with issuing a currency with phasing I'm getting "Could not validate unsigned bytes returned by the server." which information do you need to debug this ?
Update: I did it again and it worked, not sure what happened.
Update #2: it has to do with setting the initial supply to 0, setting it any other value fixes the problem.
« Last Edit: May 20, 2015, 11:53:42 am by yoda »
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1795
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
« Reply #18 on: May 20, 2015, 08:10:06 pm »

Something is wrong with issuing a currency with phasing I'm getting "Could not validate unsigned bytes returned by the server." which information do you need to debug this ?
Update: I did it again and it worked, not sure what happened.
Update #2: it has to do with setting the initial supply to 0, setting it any other value fixes the problem.

Fixed, good catch
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1795
    • View Profile
Re: [CORE] 1.5 Release Phasing Testing / 25.000 NXT Bounty (UPDATED!)
« Reply #19 on: May 20, 2015, 08:12:22 pm »

Another annoyance is messages like "Incorrect phasing finish height". What incorrect is about this parameter ?
If the parameter is numeric and I submitted a non numeric value tell:
"Incorrect phasing finish height, value <value> has to be numeric"
If the value is numeric but has to be bigger than or smaller than something tell me:
"Incorrect phasing finish height, value <value> has to be bigger than <min>" or "... smaller than <max>"

I attempted to improve this. Its not strait forward since the client is trying to localize the server error messages. Hopefully, I got it right, give it a try once 1.5.9 is out and let me know.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651
Pages: [1] 2  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly