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
Enhance 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.
ShutdownLatch#registerActivity
with a way to cancel the activity.
Priority 3: Could
#2147
opened Mar 21, 2022 by
m1l4n54v1c
Align ResultMessage#getPayload implementations
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.
BufferingQueryUpdateEmitter
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Feature
Use to signal an issue is completely new to the project.
#1471
opened Jul 22, 2020 by
m1l4n54v1c
QueryUpdateEmitter should return a number of affected queries
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
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.
#1470
opened Jul 22, 2020 by
m1l4n54v1c
End Saga when Deadline expires
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.
Allow replay on a Saga
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
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.
Full Concurrency Policy sequence change
Ideal for Contribution
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: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Dynamic Configuration Changes
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
#1276
opened Nov 26, 2019 by
m1l4n54v1c
Aggregate polymorphism
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: Feature
Use to signal an issue is completely new to the project.
Graceful startup/shutdown
Status: Duplicate
Use to signal this issue is a duplicate of another. Please refer to the other issue.
CaughtUp should indicate that all events are handled
Status: Obsolete
Use to signal this issue is no longer necessary.
Type: Bug
Use to signal issues that describe a bug within the system.
#1070
by m1l4n54v1c
was closed Aug 7, 2019
Unable to stop Tracking EP right after startup
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: Bug
Use to signal issues that describe a bug within the system.
Spring default processor mode in application.properties
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Obsolete
Use to signal this issue is no longer necessary.
Type: Bug
Use to signal issues that describe a bug within the system.
InMemoryEventStoreEngine should not store events before the UOW is committed
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.
Ordering of event handler instance/type group selectors
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.
#1028
opened Mar 14, 2019 by
m1l4n54v1c
Dockerize of test scripts
Status: Duplicate
Use to signal this issue is a duplicate of another. Please refer to the other issue.
#1015
by m1l4n54v1c
was closed Jun 5, 2019
Builder pattern improvements
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.
#902
opened Nov 20, 2018 by
m1l4n54v1c
Streamline AxonServerConnector exception handling
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.
AxonServerConnector doesn't process events after re-connection to AxonServer
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.
Add possibility to register default TrackingEventProcessorConfiguration
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: Feature
Use to signal an issue is completely new to the project.
Rolling back to the safe point in previous segment
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Type: Bug
Use to signal issues that describe a bug within the system.
#876
by m1l4n54v1c
was closed Nov 2, 2018
Streamline QueryBus and QueryGateway error reporting
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.
CommandCallback should be removed
Status: Won't Fix
Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Asserting checked exception while creating an Aggregate
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.
Saga configuration in Spring
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.
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.