elective-stereophonic
elective-stereophonic
NRS v1.7.2e
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Pages: [1] 2 3  All

Author Topic: NRS v1.7.2e  (Read 14275 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
NRS v1.7.2e
« on: December 07, 2015, 07:05:30 pm »

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.2e

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.2e.zip

sha256:

86e7cd23939765a3525d1f3e6c61a52e6427177f66e8abf94db7b7d4dceaf1f3  nxt-client-1.7.2e.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.2e.jar

sha256:

660bd0130d5c7d092431dc85b00eb98482c63203e48e3a86d84bf927eedce0f2  nxt-client-1.7.2e.jar

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.2e.exe

The exe and jar packages must have a digital signature by "Stichting NXT".


This is an experimental release for testing only. Source code is not provided.


Change log:

This is an experimental bugfix release. It is a mandatory update for testnet
nodes.

Accounts under phasing only control are not allowed to create or join
shufflings, or start shufflers.

Shuffling UI improvements. The My Shufflers page has been merged with
My Shufflings.

Added includeParticipantState parameter to getShufflers, to allow retrieving
shuffling participant state too with the same request.

The deleteAccountProperty API has been fixed to accept both recipient and
setter parameters, to be able to delete properties set to the account by
another account.

For consistency with setAccountProperty and deleteAccountProperty, the
getAccountProperties API account parameter has been renamed to recipient.
The account owner is also identified as recipient in the JSON fields of
the properties returned.

Added getAvailableToBuy and getAvailableToSell Monetary System APIs, to allow
calculating the rate required in order to completely fill an exchange request,
or the maximum available currency units or NXT amount considering the current
market offers.

Added Account Properties UI.

Account Control UI improvements and bugfixes.

This release will do a blockchain rescan on testnet only, deleting blocks
after height 484310.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWZc/AAAoJENqvaxkWiP4Z3+AQAOgp4W3LaztnVM72l3QhGYa6
NCdlVNPYQxJI1EKaYLSQhTwpzWBvY2SZ+P7Z67a0W0Er5svqg0AZ0oGM7Tbp4m7U
bz0gM0sWwxffn5ccLe1AdSniw2pGJLfLQhrtlJmDzCJsUSMuDhdzZ3J4cxb9ehIH
3bDXhVLtOLOoSJiIAJ0dHfzKxvBWjF7UJUNABu27Ljj/pgeyv4t3Q2P0JcHQedIX
O/E737tDdTx7aDMypqceTGJhRDRbSlIQ3z/TpacATVOdVF+WHhbUSiquiRF8rvXa
7hidBYxm/yMGm4U3DojDLQTlilixwEo+1/zknpj3fA2tfbObJMnCsRbE2icmGH2B
Dx74RZUxtKG4ohroysyS70kinYOWYMx3PAjIWrCmR1GLur3CrynxQACmgwbNxCOk
HnOtnaYDY8A0PnzBgQBeqq/uvn8nAFYe70N+4fggc7bJBz9QxpRlQ+WC0ahQCLob
eruJc2UqeIaZ0PgM9aJsP4LaVyyrl3MU+vLNNPuJQ0rOAuACYqpg0Kf1K4Edmkot
won/OYykl4KvSCjHBtxVlXsvL7THRo2Um1IXw3vcLUWu+XnOm5BntOhWOtHUN+AY
AtIVlLWC3zC4mZk928+KKBz19PCqG6chjmWhrCgOu0LLRqm/AgmJpnKphvPlKcgE
3D29f/yMEKuHki1Jp3H2
=73e9
-----END PGP SIGNATURE-----
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.2e
« Reply #1 on: December 07, 2015, 07:08:32 pm »

Note that this release will delete the blocks from the last few days on testnet and cause a fork there. There will be errors in the log and blacklisting of 1.7.1e and older peers, until they also move to 1.7.2e.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 513
    • View Profile
Re: NRS v1.7.2e
« Reply #2 on: December 08, 2015, 01:21:29 am »

Thanks,updated.Too bad I lost a payment after height 484310.
« Last Edit: December 08, 2015, 03:15:51 am by qq2536007339 »
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.7.2e
« Reply #3 on: December 08, 2015, 09:57:46 am »

Can not update my successfull 1.7.1e testNET VPS to 1.7.2e:

Code: [Select]
....
2015-12-08 00:43:14 FINE: Poll 5819406515142809241 has been finished
2015-12-08 00:43:17 FINE: Poll 2354938103242688579 has been finished
2015-12-08 00:43:20 INFO: processed block 450000
2015-12-08 00:43:23 INFO: Checksum passed at block 450000
2015-12-08 00:43:34 INFO: processed block 455000
2015-12-08 00:43:46 INFO: processed block 460000
2015-12-08 00:43:58 INFO: processed block 465000
2015-12-08 00:44:03 FINE: Transaction 10653334928549547241 has been rejected
2015-12-08 00:44:03 FINE: Transaction 1610338497170730905 has been released
2015-12-08 00:44:11 INFO: processed block 470000
2015-12-08 00:44:22 FINE: Transaction 152360589446582252 has been released
2015-12-08 00:44:22 FINE: Transaction 9470148039833812593 has been released
2015-12-08 00:44:22 INFO: processed block 475000
2015-12-08 00:44:33 INFO: processed block 480000
2015-12-08 00:44:41 FINE: Transaction 6740668935534210079 has been rejected
2015-12-08 00:44:41 FINE: Transaction 13044877526374043292 has been released
2015-12-08 00:44:41 FINE: Early finish of transaction 13044877526374043292 at height 483142
2015-12-08 00:44:41 FINE: Transaction 1078542203852326466 has been released
2015-12-08 00:44:41 FINE: Early finish of transaction 1078542203852326466 at height 483155
2015-12-08 00:44:41 FINE: Shuffling 6846283040177340533 entered stage PROCESSING, assignee 5873880488492319831, remaining
2015-12-08 00:44:41 FINE: Participant 5873880488492319831 did not submit processing
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483166
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483165
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483164
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483167
2015-12-08 00:44:41 FINE: Shuffling 6846283040177340533 entered stage CANCELLED, assignee 5873880488492319831, remaining
2015-12-08 00:44:41 FINE: Shuffling 6846283040177340533 was cancelled, blaming account 5873880488492319831
2015-12-08 00:44:41 FINE: Transaction 6130108325828118580 has been rejected
2015-12-08 00:44:42 FINE: Transaction 8431880759533023599 has been released
2015-12-08 00:44:42 FINE: Early finish of transaction 8431880759533023599 at height 483252
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 entered stage PROCESSING, assignee 5873880488492319831, remainin
2015-12-08 00:44:42 FINE: Shuffling participant 5873880488492319831 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 17158652599359757654 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 5183642564593472619 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 12745647715474645062 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 16992224448242675179 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 16992224448242675179 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 entered stage VERIFICATION, assignee 0, remaining blocks 15
2015-12-08 00:44:42 FINE: Shuffling participant 17158652599359757654 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling participant 5873880488492319831 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling participant 12745647715474645062 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling participant 5183642564593472619 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 entered stage DONE, assignee 0, remaining blocks 0
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 was distributed
2015-12-08 00:44:43 FINE: Registration never completed for shuffling 12715834022325590208
2015-12-08 00:44:43 FINE: Shuffling 12715834022325590208 entered stage CANCELLED, assignee 0, remaining blocks 0
2015-12-08 00:44:43 FINE: Shuffling 12715834022325590208 was cancelled, blaming account 0
2015-12-08 00:44:44 FINE: Shuffling 18010187208323581708 entered stage PROCESSING, assignee 6033326673854333936, remainin
2015-12-08 00:44:44 FINE: Participant 6033326673854333936 did not submit processing
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483648
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483647
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483646
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483649
2015-12-08 00:44:44 FINE: Shuffling 18010187208323581708 entered stage CANCELLED, assignee 6033326673854333936, remaining
2015-12-08 00:44:44 FINE: Shuffling 18010187208323581708 was cancelled, blaming account 6033326673854333936
2015-12-08 00:44:48 INFO: Checksum passed at block 484000
2015-12-08 00:44:48 FINE: Registration never completed for shuffling 2116146789204042375
2015-12-08 00:44:48 FINE: Shuffling 2116146789204042375 entered stage CANCELLED, assignee 0, remaining blocks 0
2015-12-08 00:44:48 FINE: Shuffling 2116146789204042375 was cancelled, blaming account 0
2015-12-08 00:44:49 FINE: Transaction 17632403758298131653 has been released
2015-12-08 00:44:49 FINE: Transaction 10282165754252393729 has been released
2015-12-08 00:44:49 FINE: Shuffling 17066004119398550389 entered stage PROCESSING, assignee 9107471420880698254, remainin
2015-12-08 00:44:49 FINE: Participant 9107471420880698254 did not submit processing
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484126
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484125
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484124
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484127
2015-12-08 00:44:49 FINE: Shuffling 17066004119398550389 entered stage CANCELLED, assignee 9107471420880698254, remaining
2015-12-08 00:44:49 FINE: Shuffling 17066004119398550389 was cancelled, blaming account 9107471420880698254
2015-12-08 00:44:49 FINE: Shuffling 11883961883981516616 entered stage PROCESSING, assignee 9107471420880698254, remainin
2015-12-08 00:44:49 FINE: Participant 9107471420880698254 did not submit processing
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484211
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484210
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484209
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484212
2015-12-08 00:44:49 FINE: Shuffling 11883961883981516616 entered stage CANCELLED, assignee 9107471420880698254, remaining
2015-12-08 00:44:49 FINE: Shuffling 11883961883981516616 was cancelled, blaming account 9107471420880698254
2015-12-08 00:44:50 FINE: Transaction 14071447012335411688 has been released
2015-12-08 00:44:50 FINE: Early finish of transaction 14071447012335411688 at height 484290
2015-12-08 00:44:50 FINE: nxt.de: Invalid max fees 10.000000 NXT, block 17473766081329873540 {"totalFeeNQT":100000000,"pr
nxt.de: Invalid max fees 10.000000 NXT, block 17473766081329873540 {"totalFeeNQT":100000000,"previousBlockHash":"b5cd960c
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.r(Unknown Source)
<------>at nxt.df$$Lambda$9/587153993.run(Unknown Source)
<------>at nxt.util.v$2.run(Unknown Source)
2015-12-08 00:44:50 FINE: Applying block 17473766081329873540 at height 484310 failed, deleting from database
2015-12-08 00:44:56 FINE: Rollback from block 11946872595449040309 at height 484309 to 11946872595449040309 at 484309
2015-12-08 00:44:56 FINE: Creating search index on account_info (name,description)
2015-12-08 00:44:56 INFO: Lucene search index created for table PUBLIC.ACCOUNT_INFO
2015-12-08 00:44:56 FINE: Creating search index on asset (name,description)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.ASSET
2015-12-08 00:44:57 FINE: Creating search index on goods (name,description,tags)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.GOODS
2015-12-08 00:44:57 FINE: Creating search index on poll (name,description)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.POLL
2015-12-08 00:44:57 FINE: Creating search index on currency (code,name,description)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.CURRENCY
2015-12-08 00:44:57 FINE: Creating search index on tagged_data (name,description,tags)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.TAGGED_DATA
2015-12-08 00:45:03 INFO: ...done at height 484309
2015-12-08 00:45:03 INFO: SUCCESSFULLY PERFORMED FULL RESCAN WITH VALIDATION
2015-12-08 00:45:03 FINE: Database transaction required 1465.187 seconds at height 484309
  nxt.df.a(Unknown Source)
  nxt.df.a(Unknown Source)
  nxt.df.r(Unknown Source)
  nxt.df$$Lambda$9/587153993.run(Unknown Source)
  nxt.util.v$2.run(Unknown Source)
2015-12-08 00:45:03 FINE: Running 2 final tasks...
2015-12-08 00:45:03 INFO: Looking for UPnP gateway device...
2015-12-08 00:45:03 INFO: nxt.upnpGatewayTimeout not defined or not numeric, using default value 7000
2015-12-08 00:45:03 INFO: nxt.upnpDiscoverTimeout not defined or not numeric, using default value 3000
2015-12-08 00:45:03 FINE: There are no UPnP gateway devices
2015-12-08 00:45:03 INFO: Started peer networking server at 0.0.0.0:6874
2015-12-08 00:45:03 INFO: Started API server at 0.0.0.0:6876, 0.0.0.0:6877
2015-12-08 00:45:03 FINE: Starting 9 background jobs
2015-12-08 00:45:03 FINE: Starting 2 delayed tasks
2015-12-08 00:45:04 FINE: Known peers: 7
2015-12-08 00:45:04 INFO: Initialization took 1470 seconds
2015-12-08 00:45:04 INFO: Nxt server 1.7.2e started successfully.
2015-12-08 00:45:04 INFO: Copyright ? 2013-2015 The Nxt Core Developers.
2015-12-08 00:45:04 INFO: THIS IS AN EXPERIMENTAL RELEASE!
2015-12-08 00:45:04 INFO: Client UI is at https://localhost:6877/index.html
2015-12-08 00:45:04 INFO: RUNNING ON TESTNET - DO NOT USE REAL ACCOUNTS!
2015-12-08 00:45:07 FINE: Average database transaction time is 0.070 seconds
2015-12-08 00:45:07 FINE: Poll 1947826240325430239 has been finished
2015-12-08 00:45:08 FINE: Transaction 13932930154345407092 has been released
2015-12-08 00:45:08 FINE: Transaction 18220658706250640101 has been released
2015-12-08 00:45:10 INFO: Blockchain download in progress
2015-12-08 00:45:10 FINE: Got 1 confirmations
2015-12-08 00:45:10 INFO: Downloaded 655 blocks in 5 s, 113 per s, 0 min left
2015-12-08 00:45:12 INFO: Finished blockchain download
2015-12-08 00:45:12 FINE: Connected to archive peer 178.150.207.53
2015-12-08 00:45:12 FINE: Need to restore 2 pruned data
2015-12-08 00:45:12 FINE: Done retrieving prunable transactions from 178.150.207.53
2015-12-08 00:45:12 FINE: Remaining 2 pruned transactions
2015-12-08 00:46:31 FINE: GetInfo: peer 119.81.29.172 changed announced address from null to 119.81.29.172
2015-12-08 00:46:31 FINE: Blacklisting 119.81.29.172 version 1.5.12
2015-12-08 00:46:46 FINE: GetInfo: peer 40.115.9.93 changed announced address from null to nxtclient1.cloudapp.net
2015-12-08 00:46:46 FINE: Blacklisting 40.115.9.93 version 1.5.15
2015-12-08 00:48:17 FINE: GetInfo: peer 5.146.64.45 changed announced address from null to raspnxt.hopto.org
2015-12-08 00:48:17 FINE: Blacklisting 5.146.64.45 version 1.6.2
2015-12-08 00:49:25 FINE: GetInfo: peer 37.139.6.166 changed announced address from null to 37.139.6.166
2015-12-08 00:49:25 FINE: Blacklisting 37.139.6.166 version 1.5.12
2015-12-08 00:53:09 FINE: Blacklisting 54.165.215.68 version 1.6.2
2015-12-08 00:55:01 FINE: GetInfo: peer 5.196.72.29 changed announced address from null to 5.196.72.29
2015-12-08 00:55:01 FINE: Blacklisting 5.196.72.29 version 1.5.12
2015-12-08 00:57:12 FINE: Database connection pool current size: 3
2015-12-08 00:57:12 FINE: Database connection pool current size: 4
2015-12-08 00:57:19 FINE: Database connection pool current size: 5
2015-12-08 00:57:19 FINE: Database connection pool current size: 6
2015-12-08 00:57:34 FINE: Database connection pool current size: 7
2015-12-08 00:57:34 FINE: Database connection pool current size: 8
2015-12-08 01:01:11 FINE: Average database transaction time is 0.005 seconds
2015-12-08 01:17:28 FINE: Average database transaction time is 0.006 seconds
2015-12-08 01:20:26 INFO: received block 485000
2015-12-08 01:32:34 FINE: Average database transaction time is 0.358 seconds
2015-12-08 01:34:19 INFO: Shutting down...
2015-12-08 01:34:19 INFO: Stopping background jobs...
2015-12-08 01:34:19 INFO: shutting down scheduledThreadPool
2015-12-08 01:34:19 INFO: ...Done
2015-12-08 01:34:19 INFO: shutting down sendingService
2015-12-08 01:34:19 INFO: shutting down peersService
2015-12-08 01:34:21 INFO: Database shutdown completed
2015-12-08 01:34:21 INFO: Nxt server 1.7.2e stopped.
Logged
Welcome to the Nxt generation of crypto!   Magis quam Moneta (More than a Coin)
"Do not worry, it is an attack" (c) Jean-Luc

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.2e
« Reply #4 on: December 08, 2015, 11:17:26 am »

Why, this looks normal to me. It has deleted blocks after 484310, then downloaded the new blocks forged since yesterday, and passed block 485000.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.7.2e
« Reply #5 on: December 08, 2015, 11:26:22 am »

Why
- I'm wondering too.

this looks normal to me. It has deleted blocks after 484310, then downloaded the new blocks forged since yesterday, and passed block 485000.
- yes, and then all of a sudden:
Quote
2015-12-08 01:20:26 INFO: received block 485000
2015-12-08 01:32:34 FINE: Average database transaction time is 0.358 seconds
2015-12-08 01:34:19 INFO: Shutting down...
2015-12-08 01:34:19 INFO: Stopping background jobs...
2015-12-08 01:34:19 INFO: shutting down scheduledThreadPool
2015-12-08 01:34:19 INFO: ...Done
2015-12-08 01:34:19 INFO: shutting down sendingService
2015-12-08 01:34:19 INFO: shutting down peersService
2015-12-08 01:34:21 INFO: Database shutdown completed
2015-12-08 01:34:21 INFO: Nxt server 1.7.2e stopped.
- why...
Logged
Welcome to the Nxt generation of crypto!   Magis quam Moneta (More than a Coin)
"Do not worry, it is an attack" (c) Jean-Luc

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.2e
« Reply #6 on: December 08, 2015, 11:30:51 am »

Unless it ran out of memory, because of the rescan, but shutting down without any error message is still unusual.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

phideas

  • Jr. Member
  • **
  • Karma: +16/-0
  • Offline Offline
  • Posts: 41
    • View Profile
    • Phideas.info | graphic designer and web developer
Re: NRS v1.7.2e
« Reply #7 on: December 08, 2015, 01:03:39 pm »

Small UI quirk: When approval request disappear from the list, the counter badge stay still there on left menu item.
Logged
graphic designer and web developer | NXT-KYNB-JC3D-PRS3-99GP5
www.phideas.info | Telegram: @phideas

phideas

  • Jr. Member
  • **
  • Karma: +16/-0
  • Offline Offline
  • Posts: 41
    • View Profile
    • Phideas.info | graphic designer and web developer
Re: NRS v1.7.2e
« Reply #8 on: December 08, 2015, 03:11:42 pm »

Still not happy with AC. It is not fool proof enough IMO. Imagine the most common usecase will be probably voting by accounts.
Now if user forget to type in the account id and will send an empty whitelist he is locked out with no way of recovery. (am i right here?)
Maybe checking for existing accounts and pubkeys in whitelist (as it is done already elswhere) could be a nice improvements towards more safety.
Is it possible to implement?

EDIT: Here is NXT-APNQ-LRZS-6JJK-2B85Q locked out becuse of empty whitelist. Is it possible to remove AC in this case?
« Last Edit: December 08, 2015, 03:20:52 pm by phideas »
Logged
graphic designer and web developer | NXT-KYNB-JC3D-PRS3-99GP5
www.phideas.info | Telegram: @phideas

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1790
    • View Profile
Re: NRS v1.7.2e
« Reply #9 on: December 08, 2015, 03:22:37 pm »

Why
- I'm wondering too.

this looks normal to me. It has deleted blocks after 484310, then downloaded the new blocks forged since yesterday, and passed block 485000.
- yes, and then all of a sudden:
Quote
2015-12-08 01:20:26 INFO: received block 485000
2015-12-08 01:32:34 FINE: Average database transaction time is 0.358 seconds
2015-12-08 01:34:19 INFO: Shutting down...
2015-12-08 01:34:19 INFO: Stopping background jobs...
2015-12-08 01:34:19 INFO: shutting down scheduledThreadPool
2015-12-08 01:34:19 INFO: ...Done
2015-12-08 01:34:19 INFO: shutting down sendingService
2015-12-08 01:34:19 INFO: shutting down peersService
2015-12-08 01:34:21 INFO: Database shutdown completed
2015-12-08 01:34:21 INFO: Nxt server 1.7.2e stopped.
- why...

Perhaps you were running on a Linux VPS without specifying the nohup command ?
This would (under certain conditions) trigger the Java shutdown hook whenever you logout or when your terminal session times out.
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: 1790
    • View Profile
Re: NRS v1.7.2e
« Reply #10 on: December 08, 2015, 03:29:01 pm »

Is anyone else getting heavy CPU loading? It maxes out a core in Firefox and I traced it to Lastpass add-on. Then I installed Chromium and it seemed better. Today I'm shuffling on testnet in Chromium and it's giving spurious CPU loads of roughly 50%, one core at a time. I'm not using any plugins in Chromium and have a pretty decent processor (4200M) and SSD so it should not be anywhere near 50%. Maybe there's something wrong with my Java installation? When I close Chromium and leave NRS running the CPU goes back to a trickle, so I think it's UI related.

Edit: It seems to have stopped doing it now. Aaaaargh! I don't know why this is happening!

P.S.: Possible rogue process that gets called by the UI when initiating a shuffle? It did stop as soon as I closed Chromium after starting a shuffle and now that I have opened Chromium again just to view my shuffle it is playing nice.

The first thing to test would be who is consuming the CPU the wallet running in the browser or the server.
What happens if you connect using the same browser to a remote node (PM me if you need a VPS node to connect to), do you still see the CPU spikes ?
If you do, then this is a client side issue. If you don't this is a server side issue.
The methods to diagnose server CPU spikes are different than the methods to diagnose client side CPU spikes so this should be the first thing to figure out.
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

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.2e
« Reply #11 on: December 08, 2015, 03:37:25 pm »

Still not happy with AC. It is not fool proof enough IMO. Imagine the most common usecase will be probably voting by accounts.
Now if user forget to type in the account id and will send an empty whitelist he is locked out with no way of recovery. (am i right here?)
Maybe checking for existing accounts and pubkeys in whitelist (as it is done already elswhere) could be a nice improvements towards more safety.
Is it possible to implement?

EDIT: Here is NXT-APNQ-LRZS-6JJK-2B85Q locked out becuse of empty whitelist. Is it possible to remove AC in this case?
Empty whitelist means any account can approve the transaction. While not very useful, this is allowed. You should be able to create an account control transaction removing the control, and then approve it using either this, or any other account.
Phasing using by-account with empty whitelist however is executed at finish height only, early release of such transactions is not supported. Meaning you will have to wait until finish height for the change to take effect, after the approval.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

CryptKeeper

  • Hero Member
  • *****
  • Karma: +78/-5
  • Offline Offline
  • Posts: 1235
    • View Profile
Re: NRS v1.7.2e
« Reply #12 on: December 08, 2015, 04:19:32 pm »

GUI refresh issue:

after approving still showing "Dashboard/Approval Requests (1)".
Logged
Follow me on twitter for the latest news on bitcoin and altcoins!
Vanity Accounts Sale :-)

phideas

  • Jr. Member
  • **
  • Karma: +16/-0
  • Offline Offline
  • Posts: 41
    • View Profile
    • Phideas.info | graphic designer and web developer
Re: NRS v1.7.2e
« Reply #13 on: December 08, 2015, 05:47:21 pm »

Still not happy with AC. It is not fool proof enough IMO. Imagine the most common usecase will be probably voting by accounts.
Now if user forget to type in the account id and will send an empty whitelist he is locked out with no way of recovery. (am i right here?)
Maybe checking for existing accounts and pubkeys in whitelist (as it is done already elswhere) could be a nice improvements towards more safety.
Is it possible to implement?

EDIT: Here is NXT-APNQ-LRZS-6JJK-2B85Q locked out becuse of empty whitelist. Is it possible to remove AC in this case?
Empty whitelist means any account can approve the transaction. While not very useful, this is allowed. You should be able to create an account control transaction removing the control, and then approve it using either this, or any other account.
Phasing using by-account with empty whitelist however is executed at finish height only, early release of such transactions is not supported. Meaning you will have to wait until finish height for the change to take effect, after the approval.

Thanks for clarification!
Didn't know it is possible to approve empty whitelisted AC. However there is no GUI support for this right?
I think because it is so easy for new user to get into trouble, there should be an easy way to fix it.
I'd like to propose this. What if such empty white list Approval Requests appeared in the GUI but only for the creator account.
It couldn't harm and the user would be able to fix his broken AC easy-peasy with one click.
Logged
graphic designer and web developer | NXT-KYNB-JC3D-PRS3-99GP5
www.phideas.info | Telegram: @phideas

abctc

  • Hero Member
  • *****
  • Karma: +148/-13
  • Offline Offline
  • Posts: 1396
    • View Profile
Re: NRS v1.7.2e
« Reply #14 on: December 08, 2015, 07:13:25 pm »

Perhaps you were running on a Linux VPS without specifying the nohup command ?
This would (under certain conditions) trigger the Java shutdown hook whenever you logout or when your terminal session times out.
- yes, probably it is the cause. Thank you.
Logged
Welcome to the Nxt generation of crypto!   Magis quam Moneta (More than a Coin)
"Do not worry, it is an attack" (c) Jean-Luc

petko

  • Jr. Member
  • **
  • Karma: +24/-0
  • Offline Offline
  • Posts: 98
    • View Profile
    • My blog
Re: NRS v1.7.2e
« Reply #15 on: December 08, 2015, 09:55:10 pm »


Thanks for clarification!
Didn't know it is possible to approve empty whitelisted AC. However there is no GUI support for this right?
I think because it is so easy for new user to get into trouble, there should be an easy way to fix it.
I'd like to propose this. What if such empty white list Approval Requests appeared in the GUI but only for the creator account.
It couldn't harm and the user would be able to fix his broken AC easy-peasy with one click.

There is UI support, there isn't a notification in Dashboard. You can approve the transaction from the transaction info dialog, Actions tab:



Logged

petko

  • Jr. Member
  • **
  • Karma: +24/-0
  • Offline Offline
  • Posts: 98
    • View Profile
    • My blog
Re: NRS v1.7.2e
« Reply #16 on: December 08, 2015, 09:59:51 pm »

GUI refresh issue:

after approving still showing "Dashboard/Approval Requests (1)".

I think it's on purpose. The approval request will disappear after the finish height (if not, that's a bug).
Logged

phideas

  • Jr. Member
  • **
  • Karma: +16/-0
  • Offline Offline
  • Posts: 41
    • View Profile
    • Phideas.info | graphic designer and web developer
Re: NRS v1.7.2e
« Reply #17 on: December 08, 2015, 10:50:31 pm »


Thanks for clarification!
Didn't know it is possible to approve empty whitelisted AC. However there is no GUI support for this right?
I think because it is so easy for new user to get into trouble, there should be an easy way to fix it.
I'd like to propose this. What if such empty white list Approval Requests appeared in the GUI but only for the creator account.
It couldn't harm and the user would be able to fix his broken AC easy-peasy with one click.

There is UI support, there isn't a notification in Dashboard. You can approve the transaction from the transaction info dialog, Actions tab:



Just wow and thanks! Didn't know about that option so I did a curl API request instead ;D
Oh boy NXT is so ...complex.
Logged
graphic designer and web developer | NXT-KYNB-JC3D-PRS3-99GP5
www.phideas.info | Telegram: @phideas

phideas

  • Jr. Member
  • **
  • Karma: +16/-0
  • Offline Offline
  • Posts: 41
    • View Profile
    • Phideas.info | graphic designer and web developer
Re: NRS v1.7.2e
« Reply #18 on: December 08, 2015, 10:54:41 pm »

Small UI quirk: Error message in shuffling is in NQT instead of NXT
"Incorrect amount. value 500000000 not in range [700000000-9223372036854775807]"
Logged
graphic designer and web developer | NXT-KYNB-JC3D-PRS3-99GP5
www.phideas.info | Telegram: @phideas

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 513
    • View Profile
Re: NRS v1.7.2e
« Reply #19 on: December 09, 2015, 06:24:00 am »

Should the receiver of properties have a change to refuse a setter? In case a setter set a aggressive properties name or value? The receiver have to pay 1 NXT to delete? Seems not fair.
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T
Pages: [1] 2 3  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly