-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub issue handler #56
Conversation
Create a new model for a github issue containing the repo address and issue number.
9bd267d
to
e896781
Compare
e896781
to
4dd35f9
Compare
Co-authored-by: Rob Applin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I found a couple of cases that the stack trace trimming would miss, which could result in new issues being created rather than comments added to existing issues.
|
||
|
||
class MatchingStackTraceSearchTest(TestCase): | ||
entries = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the following would not be matched by the regex:
File "/opt/mantidworkbench6.9/lib/python3.10/site-packages/mantid/simpleapi.py", line 1083, in __call__
and also the following kind of thing that I found in the error reports slack channel:
Exception: MDWorkspace::getExperimentInfo(): expInfoIndex is out of range.
at line 152 in '/usr/local/anaconda/envs/mantid-dev/plugins/python/algorithms/ConvertWANDSCDtoQ.py'
self.assertNotIn(username, _trim_stacktrace(test_trace)) | ||
|
||
def test_line_trimmer_file_lines(self): | ||
examples = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you might want to add the above examples to this test too
65c000f
to
dc9d5f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's get this in and get it working
This is the main pr for "automatic github issue creation" of the Mantid error reporter improvements Epic.
What's been added:
GithubIssue
comprised of a repo address and an issue numbergithub_issue_manager.py
which contains the main funcionget_or_create_github_issue
which does the followingTwo new environment variables have been added
GIT_AUTH_TOKEN
is the auth token of the account used to create the github issues / comments (on the live version of the error reports site this will be an auth token from https://github.com/Mantid-Error-Reporter)GIT_ISSUE_REPO
the repository to create the issues in (e.g'ISISNeutronMuon/mantid-isis-support'
)I've also changed the slack message poster so that, id an issue is created / found, it'll be linked in the slack message.