-
Notifications
You must be signed in to change notification settings - Fork 123
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
update Node.js harness #178
Conversation
@StevenACoffman sorry for bother you. I'll try to update this harness. |
4369543
to
3f25280
Compare
I reimplemented and re-output the spec. |
@StevenACoffman Yes. I think it's a necessary part of the process. because according @vvakame mentioned
#180 does support |
So even after merging #169 and rebasing this as in #181 the tests continue to fail. I wasn't able to push the rebased version back up to @vvakame fork, so I created #181 PR to demonstrate the continued failure. Unfortunately, I'm not going to be able to spend more time looking into this at present, so if anyone else can sort it out, I would welcome a PR that passed the tests. |
superceded by #181 which is now merged! |
No description provided.