Issues: AxonFramework/AxonFramework
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Inconsistency in AggregateTestFixture with constructor command handlers
Type: Bug
Use to signal issues that describe a bug within the system.
#3020
opened May 6, 2024 by
CodeDrivenMitch
Enhancing metric observability
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2791
opened Aug 1, 2023 by
CodeDrivenMitch
Improve Spanfactory configurability
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Allow easy configuration of CBOR
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
Expose total bus capacity as metric
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Under Discussion
Use to signal that the issue in question is being discussed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2677
opened Apr 6, 2023 by
CodeDrivenMitch
Error handling of Streaming queries is less than ideal
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
SimpleDeadlineManager does not use CorrelationDataProviders
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
OpenTelemetry support does not work properly
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Allow Development mode on test containers
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Feature
Use to signal an issue is completely new to the project.
AggregateTestFixture does not validate deadlines set in the past
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2460
opened Oct 27, 2022 by
CodeDrivenMitch
Autoconfigure automatic load balancing
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
QuartzDeadlineManager does not recover from failures
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
CachingSagaStore throw ConcurrentModificationException
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Duplicate
Use to signal this issue is a duplicate of another. Please refer to the other issue.
Type: Bug
Use to signal issues that describe a bug within the system.
#2406
by CodeDrivenMitch
was closed Sep 30, 2022
Allow OpenTelemetrySpanFactory to only create child spans
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Dead Letter Queue implementations can leak personal data to log
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Aggregates no longer allow private/protected no-arg constructors
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Propagate ResetContext in ReplayToken
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
Duplicate command handler resolver is triggered in polymorphic aggregates
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Cannot send two creational commands in same unit of work when using CreationPolicy.ALWAYS
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
PooledStreamingEventProcessors are not invoked immediately on availibity callback
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Bug
Use to signal issues that describe a bug within the system.
AggregateTestFixture creates EventSourcingRepository and does not invalidate it
Ideal for Contribution
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
ProTip!
Follow long discussions with comments:>50.