vault backup: 2024-11-06 08:51:01

This commit is contained in:
2024-11-06 08:51:02 -06:00
parent 3c34e87721
commit be5bf64332
2 changed files with 19 additions and 0 deletions

View File

@@ -0,0 +1,10 @@
Start time: 10:11
# To-dos
- [ ] Read and give feedback on Ricardo's replatform ideas: https://docs.google.com/document/d/1r3W1Ot1T89gxgmPGNKuFPg2lDZEJiUHlxdfbcwLMZYo/edit?tab=t.0#heading=h.lqshyo4dhsiq
- [x] Scale VMs back down from this morning's scale-up https://faithlife.slack.com/archives/C03R1MQSR51/p1730477236809519
- [ ] Finish Skeletor asynification
- [ ] Review all uses of Url and HttpContext to make sure they are not used after we do ConfigureAwait(false) (like in private controller methods)
- [ ] Review all HttpContext.Current usage to replace with passed-in HttpContextBase parameters
- [ ] Follow-up on on-call action-item to handle liquid errors differently
# Summary

View File

@@ -0,0 +1,9 @@
Start time: 09:12
# To-dos
- [ ] Finish Skeletor asynification
- [ ] Review all uses of Url and HttpContext to make sure they are not used after we do ConfigureAwait(false) (like in private controller methods)
Since _all_ controller methods (private and public, or otherwise) have access to the controller's base class HttpContext and Url properties, I'm going to keep ConfigureAwait(true) for any controller methods but make sure they pass HttpContext down to any methods outside the controller
- [ ] Review all HttpContext.Current usage to replace with passed-in HttpContextBase parameters
- [ ] Follow-up on on-call action-item to handle liquid errors differently
- [ ] Search for specific causes of bad site performance on 11/1 FBOTM day https://faithlife.slack.com/archives/C03R1MQSR51/p1730821466045049?thread_ts=1730477236.809519&cid=C03R1MQSR51
# Summary