Skip to content

Conversation

@istyf
Copy link

@istyf istyf commented Dec 3, 2025

The session service created allowed range and default in milliseconds, but compared
and divided with a time.Duration that is expressed in nanoseconds. The result was that 
the returned revised timeout was always zero.

Problem happened here: https://github.com/gopcua/opcua/blob/0d83d1cc736a5db59bfbb31a167d3e9c6b09c845/server/session_service.go#L76

This is a potential fix for #830 that talks about a connection failure due to a bad timeout value.

…imeout

    The session service created allowed range and default in millisecond, but compared
    with a time.Duration that is expressed in nanoseconds. The result was that the
    returned revised timeout was always zero.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant