Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
biancode opened this issue Mar 16, 2019 · 0 comments

Comments

@biancode
Copy link
Contributor

biancode commented Mar 16, 2019

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

  1. add listener
  2. add inject
  3. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant