Enable the py-tracebacker for mules #2251
Open
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.
The current traceback system is great for giving visibility into the callstacks for serving requests, but when you use mules you don't get to see the same data.
This adds a new configuration option, --py-tracebacker-mule, which works the same way as --py-tracebacker. I added a new option because I didn't want to break anyone who was using the old behavior (although an earlier version of this change simply uses the same base path and adds -mule as a suffix between the path and the number). This results in in the same sockets being created as before and you can then read the stacks from them.
This is really useful in my usage, and I hoped others might find it useful enough that it should be a core feature.