Skip to content

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
67 Open 168 Closed
67 Open 168 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

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 updated May 9, 2024
1
How to solve the issue of business validation inaccuracies caused by projection delays? Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#3017 opened Apr 29, 2024 by yyc6698 updated May 6, 2024
7
Return position after Append Events Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Feature Use to signal an issue is completely new to the project.
#1740 opened Mar 22, 2021 by smcvb updated Mar 15, 2024
4
Allow prevention of @QueryHandlers when the Event Handling Component backing the query handler is Replaying 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.
#2949 opened Dec 21, 2023 by smcvb updated Mar 15, 2024
2
Contract Testing 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.
#2990 opened Feb 28, 2024 by meierw updated Feb 29, 2024
4
Table partitioning for event table Ideal for Contribution 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.
#2979 opened Feb 14, 2024 by williancolognesitrimble updated Feb 19, 2024
4
Support Synthetic Flows/Tests 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.
#2950 opened Dec 22, 2023 by vab2048 updated Dec 27, 2023
1
Automatic Aggregate Event Stream filtering Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1589 opened Nov 4, 2020 by smcvb updated Dec 21, 2023
1
Aggregate Stream Refactoring Support Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Feature Use to signal an issue is completely new to the project.
#1590 opened Nov 4, 2020 by smcvb updated Dec 21, 2023 Release 5.0.0
1
Implement Page and PageResponseType for QueryBus 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.
#486 opened Jan 29, 2018 by smcvb updated Dec 18, 2023
12
Allow parameterized ResponseType 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.
#1537 opened Oct 13, 2020 by jnfeinstein updated Dec 15, 2023
5
Health Indicator for Event Processors 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.
#2138 opened Mar 17, 2022 by smcvb updated Nov 28, 2023
3
Fix some static analysis findings Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2594 opened Feb 8, 2023 by timtebeek updated Nov 22, 2023
2 of 4 tasks
7
Support for Virtual Threads - JDK21 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.
#2710 opened May 14, 2023 by mjagus updated Oct 18, 2023
4
Aggregate Parameter Resolver 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.
#2399 opened Sep 27, 2022 by smcvb updated Sep 7, 2023
Provide a fluent API for assertions 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: Feature Use to signal an issue is completely new to the project.
#1476 opened Jul 27, 2020 by OLibutzki updated Sep 7, 2023
Add support for Quarkus Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#1318 opened Jan 15, 2020 by tunovic updated Sep 7, 2023
15
Support SpEL on an @ProcessingGroup annotation equivalent 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.
#1266 opened Nov 6, 2019 by jangalinski updated Sep 6, 2023
3
Provide SQL for all Entities Ideal for Contribution 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.
#1258 opened Nov 2, 2019 by jangalinski updated Sep 6, 2023
8
Projection Testing Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#729 opened Aug 23, 2018 by m1l4n54v1c updated Sep 6, 2023
8
Set initial token to head when all contained Event Handling Components of a Streaming Event Processor disallow replays 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.
#2760 opened Jun 20, 2023 by smcvb updated Jun 20, 2023
Distinct Repository beans based on configured Aggregate type 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.
#1688 opened Jan 22, 2021 by gsteen updated Jun 12, 2023
3
AggregateLifecycle.createNew does not return Entity ID in CommandResultMessage 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.
#2059 opened Dec 22, 2021 by jasperfect updated Jun 12, 2023
8
Enable tracing in DisruptorCommandBus with SpanFactory 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.
#2402 opened Sep 27, 2022 by smcvb updated Jun 12, 2023
3
Interceptor list Spring auto configuration 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.
#1422 opened Apr 24, 2020 by smcvb updated Jun 12, 2023
3
ProTip! What’s not been updated in a month: updated:<2024-04-09.