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

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
8 👍 28
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
15 👍 14
Improve support for a local event store 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.
#1342 opened Feb 11, 2020 by OLibutzki
6 👍 10
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
8 👍 6
Allow asynchronous code in Sagas Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: On Hold Use to signal that work on this issue is paused. The description should clarify why. Type: Feature Use to signal an issue is completely new to the project.
#1860 opened Jul 2, 2021 by cjdxhjj
3 👍 5
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
1 👍 4
Introduce Federated/Hierarchical CommandBus 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.
#1092 opened May 15, 2019 by smcvb
👍 3
Consistency gap in conjunction with state-stored aggregates Status: Under Discussion Use to signal that the issue in question is being discussed.
#1103 opened May 27, 2019 by OLibutzki
8 👍 3
High memory usage when large gaps appear in event store 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.
#1241 opened Oct 9, 2019 by sgrimm
7 👍 3
Allow registration of Upcasters on all components that do serialization of messages 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.
#746 opened Sep 3, 2018 by abuijze
4 👍 2
Alias/Business Name for an Event 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.
#722 opened Aug 20, 2018 by m1l4n54v1c
13 👍 2
Snapshot Warm-Up Service 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.
#1641 opened Dec 15, 2020 by smcvb
👍 2
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 Release 5.0.0
1 👍 2
Allow custom event validation implementations in the ResultValidator 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.
#2429 opened Oct 7, 2022 by fernanfs
👍 1
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
2 of 4 tasks
7 👍 1
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
4 👍 1
Testing command, event and aggregate (de)serialization 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.
#1904 opened Aug 5, 2021 by maartenjanvangool
5 👍 1
Custom Scopes 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.
#626 opened Jun 21, 2018 by m1l4n54v1c
👍 1
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
3 👍 1
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
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
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
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
3
Integration test facility to ensure and assert processed events 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.
#1426 opened Apr 30, 2020 by hatzlj
1
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
ProTip! no:milestone will show everything without a milestone.