-
Notifications
You must be signed in to change notification settings - Fork 1
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
Review the message-sending code path #805
Labels
Comments
stvnrlly
added
documentation
Improvements or additions to documentation
engineering
labels
Feb 15, 2024
Notes from our discussion:
Things we'd like to capture with this:
|
In addition, @xlorepdarkhelm and anyone else, if there are other things we can or should do to improve our Python code here, or other tooling we should get into place (or configure more), please list them here! I've captured some notes above already. |
This was referenced Feb 28, 2024
stvnrlly
assigned ccostino and unassigned xlorepdarkhelm, terrazoon, A-Shumway42 and anagradova
Feb 28, 2024
2 tasks
All things have been accounted for in the new issues linked above! Closing this one out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Goal: to check for (1) addressable complexity and (2) trap doors in the steps a sent message takes.
Multiple developers should share this task, both to get a range of opinions and to build familiarity with this core bit of the system.
Questions:
To complete:
docs/all.md
of the findingsReviewers:
The text was updated successfully, but these errors were encountered: