-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Assertion `token->code == RIGHT_PAREN' failed #345
Comments
backtrace:
|
Thanks for reporting @jaredmauch. Was about to ask if we could have the zonefile that triggered it, but you beat me to it 🙂. I'll probably get to this next week. |
@k0ekk0ek there's numerous that are triggering it
|
Curious if you have figured it out yet so I can grab a branch and test |
Not yet, I'm a bit pressed for time and another PR was first on my list. I'll have a look tomorrow. |
@jaredmauch, I believe indexer state is corrupted when the first |
Fixed it. Upon resize the partial token reference was not properly updated. @jaredmauch, can you give https://github.com/k0ekk0ek/simdzone/tree/fix-213 a try? If you add a remote in the nsd/simdzone Git submodule and checkout the fix-213 branch, things should work. |
I'm now seeing this:
|
Thanks for testing. I'll tackle the new one next. |
If you send me an email offline I can give you a tar of my entire config/directory that might help if there are others. I can't find your email but mine should be pretty easy to find :-) |
I also opened #349 as related to ease troubleshooting |
The last one was simply a bad test in the assert. i.e. the test is meant to verify the start of the field comes before the end of the field, but in this case it verifies the end comes before the start. As it's in |
Updated to head and seeing this issue.
I'll submit the triggering zonefile in a moment, i have more than one zone file that is triggering this with a secondary zone
The text was updated successfully, but these errors were encountered: