Clarify that ActionDispatch::DebugLocks is accessible via HTTP #42160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I just spent more time than I am willing to admit to search for a file at `/rails/locks` (among other paths that I added as an argument) in my filesystem because I observed that the deadlocked server wouldn't handle any "normal" requests. The documentation somewhat hints at this by saying "insert it near the top of the middleware stack", but nevertheless I would have preferred to have this explicitly.
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I just spent more time than I am willing to admit to search for a file at
/rails/locks(among other paths that I added as an argument) in my filesystem because I observed that the deadlocked server wouldn't handle any "normal" requests and assumed the mentioned path therefore must be in my filesystem. Granted/railsis a very non-standard path and the documentation somewhat hints at this by saying "insert it near the top of the middleware stack", but nevertheless I would have preferred to have this explicitly.