-
Notifications
You must be signed in to change notification settings - Fork 343
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
eskip testable example is incorrectly passing #1860
Comments
AlexanderYastrebov
added a commit
that referenced
this issue
Sep 21, 2021
The #1860 pointed out to a bug golang/go#48362 that leads to false positive testable example due to trailing comment. Moreover #918 changed test input without changing the output and that went unnoticed due to this bug. This change removes trailing comment to fix the example. It also removes the test input instead of adding correct output because the input does not match the final implemenation and thus is misleading. Fixes #1860 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
AlexanderYastrebov
added a commit
that referenced
this issue
Sep 21, 2021
The #1860 pointed out a bug golang/go#48362 that leads to the false positive testable example caused by a trailing comment. Moreover #918 changed the test input without changing the output and that went unnoticed due to this bug. This change removes trailing comment to fix the example. It also removes the test input instead of adding a correct output because the input syntax is incorrect therefore misleading. Fixes #1860 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Merged
Thanks @ameowlia !! |
AlexanderYastrebov
added a commit
that referenced
this issue
Sep 23, 2021
The #1860 pointed out a bug golang/go#48362 that leads to the false positive testable example caused by a trailing comment. Moreover #918 changed the test input without changing the output and that went unnoticed due to this bug. This change removes trailing comment to fix the example. It also removes the test input instead of adding a correct output because the input syntax is incorrect therefore misleading. Fixes #1860 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃憢 Hello,
I am investigating the golang issue: golang/go#48362, where testable examples are causing false positives when the output comment block is not the last comment block example.
I ran a parser against the top golang repos, including this repo, and I found this bug with one of your testable examples.
The TODO comment block should be moved before the output comment block like so:
When I made this change, the example failed:
The text was updated successfully, but these errors were encountered: