elective-stereophonic
elective-stereophonic
NRS v1.5.12  
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.11.15 | Latest Experimental Nxt Client: Nxt 1.12.0e

Pages: [1] 2 3 ... 6  All

Author Topic: NRS v1.5.12  (Read 32393 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
NRS v1.5.12
« on: June 14, 2015, 01:29:51 pm »

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.5.12

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

sha256:

ac42f30dde2f84c624a78791befb44ed0f11dc8e456742388d410537914266f9  nxt-client-1.5.12.zip

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

sha256:

f29d6229f9a14ee37b217ffcf6484b7efcd16ac5ce714b64e968de7ceafd311e  nxt-client-1.5.12.jar

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



Change log:

Significantly reduced the number of threads used when WebSockets are enabled.
This should prevent the out of memory issues on some systems caused by
excessive number of native threads created.

Fixed important bugs in fork resolution during blockchain download.

Improved blockchain download speeds, reduce load on hallmarked nodes and avoid
slow peers during download.

Send event notifications when using the eventRegister and eventWait APIs only
after the database transaction has been committed, to make sure the changes
that triggered the event are visible at the time the event is emitted.

Added generateFileToken and decodeFileToken APIs, allowing creating and
verifying tokens for files.

Fixed file upload when using the test page.

The maximum file size accepted for upload can be restricted using the new
nxt.maxUploadFileSize property, default and minimum accepted value is 42 kB.


Client UI:

Fixed missing scrollbars in modals invoked from other modals.

Updated some translations. Added Romanian translation (experimental).

Updated bootstrap to version 3.3.4.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVfWnUAAoJEFOhyXc7+e2AwsAQANXmvSdHq3fgU/NJdJzM/vhL
NtPB/lQsXcMrB38QUADwvgKe2EAWf6re4aabjpNnXmVKntvYE/vJR4EQXpiXLFok
rSoPsbBYkxt1JKvb1lhWY90dTk+uWoziBzVd+cXDSABzWQyfqZGojAKe9SYpFSMS
qyoaALkL859xT3SREg3aFeiJ9Kk+dLflUFBb7oGH/ez0Q/WFCHtA88+HFL4fM8ro
UskRNj9IMjkqsw3l5GN3RgzRbfHCO6KxFDLXa4zg7toS6Vo9eODs4GO8eFSvsxnb
5VxqihpCgZ9Yo0wTuvAkoR5me3AWHQoia2ms93Uowa3GN8eF7KC8AYvFr7mhxjT/
+PLX5kun/yyhHk58ks/T9Wzn2eZ6ApgLT6tOLvmUVo82DVWcP4GkX4s0IXlHslwc
JpbKBDe75d/n+GfsibvcWeK0eTsePcLIFW4z0DtaUuADdStatjsmWbwXqPwWmLWd
+THOlBAIVIvSolIAHOL1tWT0jWDrgJj0eedOPlhNE3tzav+9j1N5fpC1+tOqRFr9
kuQwyK48S8KSX16y6VMKv2FjRVF3hHZnQMnUgOlUYEuTVBfw9ltdgxdFU5ZSmbwv
srAcS1M/fAJpirEi3+KBe2WPvN68MEeKr+OB3qOw0Z6Jwmu7mJBcWtwiO11h990b
jVEO+JbQWvTJAX1hXAP/
=6jAr
-----END PGP SIGNATURE-----
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: 514
    • View Profile
Re: NRS v1.5.12
« Reply #1 on: June 14, 2015, 01:31:39 pm »

Nice work,thanks!
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

dhj1965

  • Full Member
  • ***
  • Karma: +12/-31
  • Offline Offline
  • Posts: 198
    • View Profile
Re: NRS v1.5.12
« Reply #2 on: June 14, 2015, 01:34:00 pm »

thanks :)

my 6 nodes updated without any problem :)
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1795
    • View Profile
Re: NRS v1.5.12
« Reply #3 on: June 14, 2015, 01:36:06 pm »

To verify the installer executable:
From Windows Explorer, right click the installer executable file, in the "Digital Signatures" tab verify that the signer name is "Stichting NXT". You can view additional information by clicking the "Details" button.
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

yassin54

  • Hero Member
  • *****
  • Karma: +240/-14
  • Offline Offline
  • Posts: 2503
  • I am Homer, Sorry my english is Bad!!
    • View Profile
Re: NRS v1.5.12
« Reply #4 on: June 14, 2015, 02:37:36 pm »

installer Windows all work
Thanks
Great Job!  ;)

franckuestein

  • Jr. Member
  • **
  • Karma: +24/-4
  • Offline Offline
  • Posts: 74
    • View Profile
Re: NRS v1.5.12
« Reply #5 on: June 14, 2015, 02:45:06 pm »

Nice work, guys! Thanks for the release  ;)
Wallets updated.
Logged

coretechs

  • Sr. Member
  • ****
  • Karma: +161/-1
  • Offline Offline
  • Posts: 436
    • View Profile
Re: NRS v1.5.12
« Reply #6 on: June 14, 2015, 04:22:38 pm »

Thanks!  Blockchain explorers updated.

http://nxtportal.org
http://test.nxtportal.org
Logged
https://ardorportal.org - Ardor blockchain explorer | https://nxtportal.org - Nxt blockchain explorer | http://bitcoindoc.com - The Rise and Rise of Bitcoin
ARDOR-T43P-R2K9-8W79-9W2AL | NXT-WY9K-ZMTT-QQTT-3NBL7

cayenne

  • Sr. Member
  • ****
  • Karma: +10/-2
  • Offline Offline
  • Posts: 253
    • View Profile
Re: NRS v1.5.12
« Reply #7 on: June 14, 2015, 04:57:47 pm »

It's 12:55 PM according to my PC clock. But the blockchain (set to 12 hour, not 24 hour clock) says the latest block was:
450714 6/14/2015 00:51:12 AM

So the switch to 12-hour mode has a bug, I think. There are blocks from 11 AM, but it fails to switch to PM at noontime.

OK, now it has switched to PM at 1:00, rather than at 12 noon (12:00 PM)
https://en.wikipedia.org/wiki/12-hour_clock


« Last Edit: June 14, 2015, 05:07:23 pm by cayenne »
Logged

devlux

  • Sr. Member
  • ****
  • Karma: +67/-2
  • Offline Offline
  • Posts: 307
    • View Profile
    • Gemspace
Re: NRS v1.5.12
« Reply #8 on: June 14, 2015, 05:24:56 pm »

Not to complain, but would it be at all possible to have a release schedule in place?
I appreciate the hardwork, but trying to build anything on top of NRS when it gets random releases like this makes it hard.

Good work though and thanks!
Logged
Evolution NEXT D.A.C.
NXTAE:3385321989487982138 (EVOLVE)

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.5.12
« Reply #9 on: June 14, 2015, 05:27:01 pm »

Not to complain, but would it be at all possible to have a release schedule in place?
I appreciate the hardwork, but trying to build anything on top of NRS when it gets random releases like this makes it hard.

Good work though and thanks!

Not all release are mandatory. Unless state otherwise, every update are always not mandatory, as far as I know.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: NRS v1.5.12
« Reply #10 on: June 14, 2015, 06:03:01 pm »

Not to complain, but would it be at all possible to have a release schedule in place?
I appreciate the hardwork, but trying to build anything on top of NRS when it gets random releases like this makes it hard.

Good work though and thanks!

Thanks for your comment.

As already pointed out by Sebastien256, there is not immediate need to upgrade this time. Right now, we prefer this "random" release plan over a fixed one like the one being used for products like LibreOffice. This gives the developers more flexibility.

In case of critical security update, we cannot plan them beforehand anyway and upgrade might be crucial within a very narrow timeframe.
In case of iterative improvement like this one, just update to the latest release at your convenience. Feel free to skip upgrades when it does not match with your update plan for your organization/company.
Logged

kseistrup

  • Sr. Member
  • ****
  • Karma: +48/-0
  • Offline Offline
  • Posts: 465
  • Fortune favours the lucky
    • View Profile
    • @kseistrup
Re: NRS v1.5.12
« Reply #11 on: June 14, 2015, 07:38:18 pm »

I just noticed that my forging nodes are no longer forging after the upgrade to 1.5.12 (presumably this already happened with the first 1.5.* client).  I can start forging by providing my passphrase, but even if I log out with just “Logout” (as opposed to “Logout and stop forging”) I need to login with my password again.  How come?  Is there no way to have a node running in forging mode automatically?

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1795
    • View Profile
Re: NRS v1.5.12
« Reply #12 on: June 14, 2015, 08:00:04 pm »

It's 12:55 PM according to my PC clock. But the blockchain (set to 12 hour, not 24 hour clock) says the latest block was:
450714 6/14/2015 00:51:12 AM

So the switch to 12-hour mode has a bug, I think. There are blocks from 11 AM, but it fails to switch to PM at noontime.

OK, now it has switched to PM at 1:00, rather than at 12 noon (12:00 PM)
https://en.wikipedia.org/wiki/12-hour_clock

Good catch, this bug was introduced almost a year ago !
I fixed this for 1.5.13
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

kwilliams

  • Full Member
  • ***
  • Karma: +28/-3
  • Offline Offline
  • Posts: 226
  • NXT-FG7F-2W46-M7DE-EHPV5
    • View Profile
Re: NRS v1.5.12
« Reply #13 on: June 15, 2015, 05:57:53 am »

Rather than doing 12/24 hour time, etc. can we have the option to specify a format string directly? I would very much like my dates to show as "yyyy-MM-dd HH:mm:ss"...
Logged

slothbag

  • Sr. Member
  • ****
  • Karma: +74/-4
  • Offline Offline
  • Posts: 454
    • View Profile
Re: NRS v1.5.12
« Reply #14 on: June 15, 2015, 07:03:43 am »

Just wondering what benefits do we get from using websockets for p2p comms? I understand theres a little extra overhead in http, but at least its lightweight when dealing with thousands of peers.

Just curious, as I'm trying to evaluate websockets for my own projects.
Logged

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: NRS v1.5.12
« Reply #15 on: June 15, 2015, 07:05:19 am »

Just wondering what benefits do we get from using websockets for p2p comms? I understand theres a little extra overhead in http, but at least its lightweight when dealing with thousands of peers.

Just curious, as I'm trying to evaluate websockets for my own projects.
I have seen that a websockets connection is more likely to be able to be established from ISP connections that are otherwise problematic, ie firewalled and NAT by ISP who doesnt like anything but standard traffic
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1795
    • View Profile
Re: NRS v1.5.12
« Reply #16 on: June 15, 2015, 07:21:59 am »

Just wondering what benefits do we get from using websockets for p2p comms? I understand theres a little extra overhead in http, but at least its lightweight when dealing with thousands of peers.

Just curious, as I'm trying to evaluate websockets for my own projects.
I have seen that a websockets connection is more likely to be able to be established from ISP connections that are otherwise problematic, ie firewalled and NAT by ISP who doesnt like anything but standard traffic

Take a look here for in depth discussion http://stackoverflow.com/questions/14703627/websockets-protocol-vs-http
"... WebSocket connections are bi-directional, full-duplex and long-lived. After the initial handshake request/response, there is no transactional semantics and there is very little per message overhead. The client and server may send messages at any time and must handle message receipt asynchronously ..."
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

stdset

  • Jr. Member
  • **
  • Karma: +14/-1
  • Offline Offline
  • Posts: 86
    • View Profile
Re: NRS v1.5.12
« Reply #17 on: June 15, 2015, 08:38:01 am »

The memory issue remains for me. It appeared when I upgraded from 1.4.18 to 1.5.9 and also made corresponding Java upgrade. I run my node on a VPS with 4GB RAM and no swap. When I start NRS, memory usage is around several hundreds MB (like it was before), but when I login another day, the java process occupies about 3.5GB of virtual memory, while normal memory usage is still more or less OK (significantly less than 1GB). I tryed adding -Xmx1024M option, but it doesn't help much. May be there is an easy way to limit memory consumtion?
« Last Edit: June 15, 2015, 08:47:47 am by stdset »
Logged

jl777

  • Hero Member
  • *****
  • Karma: +718/-123
  • Offline Offline
  • Posts: 6170
    • View Profile
Re: NRS v1.5.12
« Reply #18 on: June 15, 2015, 08:41:46 am »

The memory issue remains for me. It apeeared when I upgraded from 1.4.18 to 1.5.9 and also made corresponding Java upgrade. I run my node on a VPS with 4GB RAM and no swap. When I start NRS, memory usage is around several hundreds MB (like it was before), but when I login another day, the java process occupies about 3.5GB of virtual memory, while normal memory usage is still more or less OK (significantly less than 1GB). I tryed adding -Xmx1024M option, but it doesn't help much. May be there is an easy way to limit memory consumtion?
on some VPS I am seeing the java use 300,000 files, which is causing problems
not sure how to fix it
Logged
There are over 1000 people in SuperNET slack! http://slackinvite.supernet.org/ automatically sends you an invite

I am just a simple C programmer

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.5.12
« Reply #19 on: June 15, 2015, 08:58:12 am »

The memory issue remains for me. It apeeared when I upgraded from 1.4.18 to 1.5.9 and also made corresponding Java upgrade. I run my node on a VPS with 4GB RAM and no swap. When I start NRS, memory usage is around several hundreds MB (like it was before), but when I login another day, the java process occupies about 3.5GB of virtual memory, while normal memory usage is still more or less OK (significantly less than 1GB). I tryed adding -Xmx1024M option, but it doesn't help much. May be there is an easy way to limit memory consumtion?
on some VPS I am seeing the java use 300,000 files, which is causing problems
not sure how to fix it

Have you tried to lower these numbers?
Code: [Select]
# Maximum number of inbound connections
nxt.maxNumberOfInboundConnections=250

# Maximum number of outbound connections
nxt.maxNumberOfOutboundConnections=50

It helps with the OutofMemory error and too many opened files issue with the latest websockets release. It did in my case anyway, YMMV.
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7
Pages: [1] 2 3 ... 6  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly