-
Notifications
You must be signed in to change notification settings - Fork 39
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
Crashes on Tap 13 data #28
Comments
Investigating. I'll have a fix out in the next day or 2, among other improvements. |
Apologize. Been swamped. Working on next release. |
I very much know that feeling. No need for apologies. Thank you for the good work |
Is this still an issu ein |
|
FYI this issue is because tap-out (the parser used by tap-spec) does not support YAML1.2 blocks. See this issue: scottcorgan/tap-out#17 @Munter in your TAP file you have the following: not ok 75 URI should have not redirects - http://copenhagenjs.dk/
---
operator: noRedirects
expected: "200 http://copenhagenjs.dk/"
actual: "302 http://copenhagenjs.dk/ --> 200 http://copenhagenjs.dk/"
at: https://mntr.dk/
https://mntr.dk/2014/getting-started-with-assetgraph/
https://mntr.dk/2014/i-love-the-unix-philisophy-but/
https://mntr.dk/2014/push-the-post-get-paradigm/
... Specifically it's failing at the line after SolutionFix scottcorgan/tap-out#17 - the upstream issue. |
Thanks for looking into this. Investigation is usually the hardest part :) |
@keithamus appreciate all the research and detailed issues. I'll jump on fixing tap-out. I have a planned rewrite the simplify collaboration on the repo. @Munter appreciate the patience. |
I've started a complete rewrite of tap-out (the parser) that's way less hacky. tap-out |
I have been working on a collection of packages under the org tap-format as sequels to my few tap-[formatter] modules. https://github.com/tap-format/spec will be the replacement for this. It's basically done, just needs documentation and screenshots/video-gifs. |
Any news on this? |
Anyone open to a PR for this? My time is limited right now. |
I wrote this: https://github.com/robwold/tap-spec-report-bug I wouldn't mind contributing a PR, but would it be to this repo, or to scottcorgan/tap-out#17 or somewhere else? In that issue you talk about deprecating tap-out in favour of another project, and it's not clear (to me at least) what the current state of affairs is. |
@robwold most likely the PR is going to be on tap-out, and then a PR on this repo to update the tap-out version. |
This reporter crashes when piping in Tap 13 data:
The text was updated successfully, but these errors were encountered: