Open magnus-bakke opened 5 months ago
your code is somewhere trying to write a struct to the ua server that cannot be parsed. Looks like something that is declared as an int or where an int is expected is not an int...
also the write has been done server side somewhere (we do not do type checking at that point, it is too slow), but the parsing only happens when a client subscribe to it and the server try to send the data
your code is somewhere trying to write a struct to the ua server that cannot be parsed. Looks like something that is declared as an int or where an int is expected is not an int...
You're right (thank you so much), a float was declared as an int. Would it not be a simple thing to print the node ID and variant type of the offender when it's parsed?
Usually it does. Looks like you hit a place where we do not.... MR welcome
Please read, before you post!
This is a BUG REPORT for issues in the existing code.
If you have general questions, code handling problems or ideas, please use the:
Discussionsboard: https://github.com/FreeOpcUa/opcua-asyncio/discussions
or
Gitter-Channel: https://gitter.im/FreeOpcUa/opcua-asyncio
To save some time, please provide us following informations, if possible:
Describe the bug
We are running asyncua in a Docker container using an image based on
python:3.10-slim-bullseye
.Because the person who developed and monitored this solution has left the company, I can't say when it was last working. All I know is that:
After launching the "master" application, which coordinates images (including the OPC UA repo that uses asyncua), I look at its logs and see this error and traceback for the OPC UA container:
This error tells me very little. (Some more error information about what was happening at the time of the error would be helpful.)
I can still connect to the server and list the nodes, but all values are absent with
Datatype = Null
,Statuscode = BadWaitingForInitialData
, andServer Timestamp = 8:00:00.000 PM
I know for a fact that it was working a few weeks ago. Since then, a few things have changed, but I have carefully looked at the changes and cannot find one that I would expect to cause any problems. Specifically, the ethernet adapter has been updated, and two new nodes have been added.
But that's all irrelevant because I just tried to deploy an older version without these recent changes, and it still fails. At that point, the server hadn't been changed in several months.
I understand this may not be sufficient information to reproduce, but I'm hoping someone with a better understanding of asyncua than me has some inkling. I'll happily provide more information, I just don't know what to provide.
To Reproduce
Steps to reproduce the behavior incl code:
This will be tricky since it worked before these changes.
Here's some code:
Expected behavior
A clear and concise description of what you expected to happen.
When viewed using UaExpert, these columns should be populated as there are no polling errors:
(and many more)
Screenshots
If applicable, add screenshots to help explain your problem.
You can post Screenshots directly to github, please don't use 3rd Party webpages
See also the expected behavior.
(Notice that it continues to fail to write a bunch of None values. These None errors are expected.)
Version
Python-Version:
3.10 opcua-asyncio Version (e.g. master branch, 0.9): 1.1.0