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

Fitnesse slim fails with puzzling IndexOutOfBoundsException #1221

Closed
abailly opened this issue Apr 25, 2019 · 4 comments

Comments

@abailly
Copy link

commented Apr 25, 2019

We are using Fitnesse/Slim with (slightly customised) pySlim server. When running Suite for a set of pages I got the following error:
Screenshot 2019-04-25 at 17 36 36

I tried to debug the server but to no avail, probably because my debug-fu on Java is too rusty to be helpful. I also tried to upgrade to latest fitnesse (20190421), and to pass -v for more verbose debugging but to no avail. Is there way to know where/why this exception is thrown?

@tcnh

This comment has been minimized.

Copy link
Contributor

commented Apr 25, 2019

Can you share the wiki content to reproduce this? I'm pretty sure I've seen this before with a table that was not properly formatted

@abailly

This comment has been minimized.

Copy link
Author

commented Apr 25, 2019

Unfortunately not, but I came to a similar conclusion. However it's pretty much unclear which page is wrongly formatted...

@abailly

This comment has been minimized.

Copy link
Author

commented Apr 25, 2019

I found the culprit: It's a script table line containing a single item. ScriptTable fails to extract the action's name and throws this error. Would you consider a PR to fix that? What would be a more helpful error to throw?

@tcnh

This comment has been minimized.

Copy link
Contributor

commented Apr 26, 2019

A PR with an improved exception message is always welcome!
I'd say an exception like when a scenario is called with arguments that don't exist in the scenario would be nice and consistent. I believe the exception message starts with Bad Table!

abailly pushed a commit to abailly/fitnesse that referenced this issue Apr 26, 2019
script table throws SyntaxError on malformed assignment unclebob#1221
the SyntaxError exception is propagated up the call chain which requires more changes than expected. This should translate to `Bad Table` message when rendered in FitNesse.
abailly pushed a commit to abailly/fitnesse that referenced this issue Apr 28, 2019

@fhoeben fhoeben closed this Apr 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.