Skip to content

Add fix for the sequence id ordering problem #233

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

Conversation

belagertem
Copy link
Collaborator

@belagertem belagertem commented Jan 23, 2025

Added the fix for the issue 218 from the commit from the main branch.
Fixed other queries in MessageStorage that require ordering.

Checklist

The following aspects have been respected by the author of this pull request, confirmed by both pull request assignee and reviewer:

  • Adherence to coding conventions
    • Pull Request Assignee
    • Reviewer
  • Adherence to javadoc conventions
    • Pull Request Assignee
    • Reviewer
  • Changelog update (necessity checked and entry added or not added respectively)
    • Pull Request Assignee
    • Reviewer
  • README update (necessity checked and entry added or not added respectively)
    • Pull Request Assignee
    • Reviewer
  • config update (necessity checked and entry added or not added respectively)
    • Pull Request Assignee
    • Reviewer
  • SDCcc executable ran against a test device (if necessary)
    • Pull Request Assignee
    • Reviewer

ben-Draeger and others added 5 commits January 22, 2025 15:04
SequenceIds are currently ordered lexicographically, which is wrong as
the SDC standards define no order on them. We hence order them by the
timestamp of the first message that they were used in.

# Checklist

The following aspects have been respected by the author of this pull
request, confirmed by both pull request assignee **and** reviewer:

* Adherence to coding conventions
  * [x] Pull Request Assignee
  * [x] Reviewer (midtuna)
* Adherence to javadoc conventions
  * [x] Pull Request Assignee
  * [x] Reviewer (midtuna)
* Changelog update (necessity checked and entry added or not added
respectively)
  * [x] Pull Request Assignee
  * [x] Reviewer (midtuna)
* README update (necessity checked and entry added or not added
respectively)
  * [x] Pull Request Assignee
  * [x] Reviewer (midtuna)
* config update (necessity checked and entry added or not added
respectively)
  * [x] Pull Request Assignee
  * [x] Reviewer (midtuna)
* SDCcc executable ran against a test device (if necessary)
  * [x] Pull Request Assignee
  * [x] Reviewer (midtuna)

---------

Co-authored-by: midttuna <[email protected]>

(cherry picked from commit 729356b)
Signed-off-by: Malte Grebe-Lüth <[email protected]>
Added kotlin and detekt.

(partly cherry picked from commit 4d84e9e)

Signed-off-by: Malte Grebe-Lüth <[email protected]>
…ssageStorage.getOrderedStreamForQuery

Signed-off-by: Malte Grebe-Lüth <[email protected]>
Signed-off-by: Malte Grebe-Lüth <[email protected]>
@belagertem belagertem self-assigned this Jan 23, 2025
Signed-off-by: Malte Grebe-Lüth <[email protected]>
Copy link
Collaborator

@maximilianpilz maximilianpilz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the default revision

Signed-off-by: Malte Grebe-Lüth <[email protected]>
@maximilianpilz maximilianpilz merged commit 57a62a1 into Draegerwerk:release/9.0.x Jan 27, 2025
2 checks passed
@belagertem belagertem deleted the add-fix-for-the-SequenceId-ordering-problem branch April 11, 2025 05:47
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.

3 participants