Skip to content
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

potential parsing error #16

Open
kkew3 opened this issue Jun 29, 2018 · 0 comments · May be fixed by #20
Open

potential parsing error #16

kkew3 opened this issue Jun 29, 2018 · 0 comments · May be fixed by #20

Comments

@kkew3
Copy link

kkew3 commented Jun 29, 2018

Thank you so much for this utility it helps me a lot! It appears that there's some problem with parsing. See the original traceback (Figure 1) and the parsed traceback (Figure 2). The black squares cover the same file path. The reason why I feel there might be problems is that the yellow bold text after the arrow appears not very consistent with each other. It should be respectively "in main", "in run_divg_...", etc., instead of "in main", "control=2)", etc., from my point of view. Thanks!

Figure 1:
orig_tb

Figure 2:
parsed_tb

@erzoe erzoe linked a pull request Feb 18, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant