Backport cherry-picked commits from master to 0.3 #2000
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- rename subscription variable sequence number to nextSequenceNumber - adjust logic Fixes #4202 - Wrong Supertype.
If there are a set of timer callbacks in the timer list that are executed in the same timer process cycle the order of them were inversed every time after they had been executed, except the first callback. Also, if a set of timer callbacks with same timer interval are added within 1 second of each other, they are synchronized to expire at the same time and added in front of each other, except the first one which will keep the first position. If four timer callbacks with the same time interval are added after each other they are put in the timer list in the following order: #1, #4, #3, #2. This change fixes so callback timers that will be executed with the same time interval and that are put together in a "block" in the timer list are not inversed within this block after each execution of them. It also fixes so all timers within a "block" are added in a deterministic order. As described above they where added in reversed order to the timer list except the first one. Now all timers that can be put together in a "block" are added in reversed order within this block. One advantage of putting the callback timers in reversed order is if a subscription with a set of monitored items are created with the same publish/sampling interval. In that case the monitored items that are created after the subscription has been created will be executed by the timer process before the subscription's publish function is called. This execution order will cause minimum delay of data notifications to be published.
add more required nodes for the minimal nodeset
The ModellingRules node of the Server object shall reference the modelling rules that the server supports. This server supports the modelling rules mandatory and optional.
7 tasks
Problems with the default LibreSSL vs OpenSSL
This was referenced Aug 23, 2018
Pro
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you find additional commits which should also be backported from master please leave a note here