-
Notifications
You must be signed in to change notification settings - Fork 1.4k
WIP: jmccannon/ac/transaction-attempt-2 #6283
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #6283 +/- ##
==========================================
+ Coverage 49.20% 53.39% +4.19%
==========================================
Files 1768 1785 +17
Lines 78353 79537 +1184
Branches 6998 7070 +72
==========================================
+ Hits 38551 42468 +3917
+ Misses 38278 35463 -2815
- Partials 1524 1606 +82 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Fixed Issues (6)Great job! The following issues were fixed in this Pull Request
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Provided feedback in Slack, so removing my review. My main suggestion is to limit the footprint of the transaction to the private method of the invite command so that it's not passed around so much, and so that it's not held open for so long.
🎟️ Tracking
📔 Objective
This is the second attempt at creating a transaction that can be used throughout the call stack.
Currently, there's an error when a second thread comes in. (I know...the entire point of this is to allow this...I'm working on it 😄 )The error is
My current next steps are:
Retry functionality has allowed for tests to pass, but I believe this will be a speed bump in the event we get hit with >10 requests at once.
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes