You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CASR already supports stacktraces produced by different programming languages.
I propose to integrate CASR with Git to easily figure out which git commit caused a given stacktrace.
Similar to git-stacktrace 1, but it supports only three languages (Python, Java, JavaScript).
$ git stacktrace --since=1.day < trace
Traceback (most recent call last):
File "webapp/framework/resource.py", line 72, in _call
result = getattr(self, method_name)()
File "webapp/resources/interests_resource.py", line 232, in get
if self.options['from_navigate'] == "true":
KeyError
commit da39a3ee5e6b4b0d3255bfef95601890afd80709
Commit Date: Tue, 19 Jul 2016 14:18:08 -0700
Author: John Doe <[email protected]>
Subject: break interest resource
Link: https://example.com/D1000
Files Modified:
- webapp/resources/interests_resource.py:232
Lines Added:
- "if self.options['from_navigate'] == "true":"
I suppose it could be even implemented in a more simple way. We can just call git blame (or even use some Rust-native git library) on crash line. And store the corresponding commit and author into Casr report.
CASR already supports stacktraces produced by different programming languages.
I propose to integrate CASR with Git to easily figure out which git commit caused a given stacktrace.
Similar to git-stacktrace 1, but it supports only three languages (Python, Java, JavaScript).
Footnotes
https://github.com/pinterest/git-stacktrace ↩
The text was updated successfully, but these errors were encountered: