timestamp is now crashing node-opcua subscriptions via time interval bigger than In32 - Githubissues

BiancoRoyal / node-red-contrib-iiot-opcua

deprecated - very new developed by PLUS for Node-RED - https://plus4nodered.com

https://www.npmjs.com/package/node-red-contrib-iiot-opcua

BSD 3-Clause "New" or "Revised" License

34 stars 9 forks source link

timestamp is now crashing node-opcua subscriptions via time interval bigger than In32 #89

Closed biancode closed 5 years ago

biancode commented 5 years ago

I'm submitting a ... (check one with "x")

Problem

( x) bug report => please search GitHub for a similar issue or PR before submitting
( ) unexpected behaviour => please visit the Wiki before

Information

Current behaviour

crash on inject with timestamp for listener, because of a new Int32 stream in node-opcua

Expected behaviour

inject with timestamp should not crash node-red, it should set default time interval

Minimal reproduction of the problem with instructions

add listener
add inject
inject timestamp to listener

Your Environment

Please tell us about your environment:

(x) I am using just the Node-RED package and got node-opcua installed with it
( ) I have installed node-opcua global from source (using git clone)
( ) I have installed node-opcua as a global package (using npm i -g)
Device :
- ( ) macOS: v
- (x) Linux: v
- ( ) Windows: v
- ( ) Raspbian: v
- ( ) Other:
  - Name:
  - Version: Ubuntu

Node-RED version: 0.20.2
node-red-contrib-iiot-opcua version: 3.10.0 ``
Node: (min. 8.x) node --version = 10.15.3

node-opcua version = 0.6.0