Replies: 1 comment 2 replies
-
It is very hard to understand from new code, especially when I have not seen/used the hisotry code for years.. But a PR is welcome and then we will better see your proposed changes |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I was trying to use methods related to reading history from server and found some usability issues.
Node.read_raw_history
to get history data in some range that ALWAYS includes bounds (ReturnBounds
is set to True and not configurable)ContinuationPoint
is returned insideNode.read_raw_history
request fromNode.history_read
- it is unused and not returned from method (you can't continue reading history if there is more than what was returned)To address those issues I patch
ContinuationPoint
intoNode.history_read
then copy and changeNode.read_raw_history
code so that it reads all history available and setsdetails.ReturnBounds
toFalse
(see Minimal Reproducible Example below)Can some of this configuration (
ReturnBounds
andContinuationPoint
) be actually added to asyncua code or maybe someNode.read_history_recursive
method added? I am ready to send a PR, need your advice and opinionBeta Was this translation helpful? Give feedback.
All reactions