Skip to content

Conversation

@alexey-troshkin-xpress
Copy link
Contributor

@alexey-troshkin-xpress alexey-troshkin-xpress commented Dec 18, 2025

User description

In version 1.2.0, a bug appeared that prevented the handling of the WrongExpectedVersionException.
Details at kurrent-io/KurrentDB-Client-Dotnet#374


Auto-created Ticket

#484

PR Type

Enhancement


Description

  • Update KurrentDB.Client dependency from 1.2.0 to 1.3.0

  • Resolves WrongExpectedVersionException handling bug

  • Incorporates upstream fixes and improvements


Diagram Walkthrough

flowchart LR
  A["KurrentDB.Client 1.2.0"] -- "upgrade" --> B["KurrentDB.Client 1.3.0"]
  B -- "fixes" --> C["WrongExpectedVersionException handling"]
Loading

File Walkthrough

Relevant files
Dependencies
Directory.Packages.props
Bump KurrentDB.Client to 1.3.0                                                     

Directory.Packages.props

  • Updated KurrentDB.Client package version from 1.2.0 to 1.3.0
  • Centralized package version management configuration
+1/-1     

@qodo-free-for-open-source-projects
Copy link
Contributor

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
🟢
No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@qodo-free-for-open-source-projects
Copy link
Contributor

PR Code Suggestions ✨

No code suggestions found for the PR.

@github-actions
Copy link

Test Results

 50 files  + 33   50 suites  +33   33m 42s ⏱️ + 22m 53s
282 tests + 10  281 ✅ +  9  0 💤 ±0  1 ❌ +1 
814 runs  +531  813 ✅ +530  0 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit a5bd94e. ± Comparison against base commit 2f9d974.

This pull request removes 5 and adds 15 tests. Note that renamed tests count towards both.
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/3/2025 7:25:25 AM +00:00)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/3/2025 7:25:25 AM)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(81afcab6-084f-4b49-92a9-7564158e5743)
Eventuous.Tests.Subscriptions.SequenceTests ‑ ShouldReturnFirstBefore(CommitPosition { Position: 0, Sequence: 1, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 2, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 4, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 6, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 2, Timestamp: 2025-12-03T07:25:25.5801568+00:00 })
Eventuous.Tests.Subscriptions.SequenceTests ‑ ShouldReturnFirstBefore(CommitPosition { Position: 0, Sequence: 1, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 2, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 6, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 8, Timestamp: 2025-12-03T07:25:25.5801568+00:00 }, CommitPosition { Position: 0, Sequence: 2, Timestamp: 2025-12-03T07:25:25.5801568+00:00 })
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/18/2025 9:58:09 AM +00:00)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/18/2025 9:58:09 AM)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/18/2025 9:58:13 AM +00:00)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/18/2025 9:58:13 AM)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/18/2025 9:58:16 AM +00:00)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(12/18/2025 9:58:16 AM)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(52af0a72-a1a6-4159-8ce8-eab22f585edf)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(c514ead8-ea72-421d-a47d-0a65a35beb46)
Eventuous.Tests.Azure.ServiceBus.IsSerialisableByServiceBus ‑ Passes(da6b7e52-b646-4cfb-8595-dd758633d42c)
Eventuous.Tests.Subscriptions.SequenceTests ‑ ShouldReturnFirstBefore(CommitPosition { Position: 0, Sequence: 1, Timestamp: 2025-12-18T09:58:08.8073693+00:00 }, CommitPosition { Position: 0, Sequence: 2, Timestamp: 2025-12-18T09:58:08.8073693+00:00 }, CommitPosition { Position: 0, Sequence: 4, Timestamp: 2025-12-18T09:58:08.8073693+00:00 }, CommitPosition { Position: 0, Sequence: 6, Timestamp: 2025-12-18T09:58:08.8073693+00:00 }, CommitPosition { Position: 0, Sequence: 2, Timestamp: 2025-12-18T09:58:08.8073693+00:00 })
…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants