-
Notifications
You must be signed in to change notification settings - Fork 13
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
Make StopIteration Errors more informative #38
Comments
The The real solution for this will be a better, more robust search algorithm. I had hoped that the fix for #36 would handle all remaining issues, but apparently that's not the case. A new algorithm should probably give up when text isn't found within a couple of lines. I believe the searches for code should all succeed at this point, since HTML is skipped to avoid modifications made by Pandoc. There should also be a fallback to using something like |
This entire category of errors from syncing code to source line numbers should be permanently eliminated by the last commit. Sorry for the long delay. |
No worries, this is great! |
Oftentimes when running
codebraid
, I get aStopIteration
error and it is difficult to tell where this error comes from. Is there a way to make theStopIteration
error more informative, like giving the snippet of text that causes the issue or the line number?The text was updated successfully, but these errors were encountered: