- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 8 2022
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
rebase
We should probably have done more "foundation" work on logging and other canonical practices before creating such a large stack of "needing to be addressed concerns"
address comment
Agreed, but why create work for others?
Sep 7 2022
remove comments
remove the comments
rebase
remove comments
remove comments
@jon what is the ETA of the review here? This is the very first diff in the stack so it should be prioritized, right? Thanks!
If the client gets to be in an unhealthy state, then there should be some logic to get try and get the client back into a healthy state and retry the get/put. Currently, an unhealthy client will both report an error and drop the message.