-
Notifications
You must be signed in to change notification settings - Fork 100
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
Secretz is expecting a weird result #324
Labels
Comments
Hello @CamiloMM, your solution worked on my computer with the newest version. Can you update it with Best, |
I got some similar results. Node $ npm version
{ npm: '2.5.1',
http_parser: '2.3',
modules: '14',
node: '0.12.0',
openssl: '1.0.1l',
uv: '1.0.2',
v8: '3.28.73',
zlib: '1.2.8' } $ ./node_modules/.bin/stream-adventure verify ./stream-adventure/15-secretz.js
ACTUAL: "97911dcc607865d621029f6f927c7851 secretz/METADATA.TXT"
EXPECTED: "97911dcc607865d621029f6f927c78512cdcfa9f8bbefb82fb7a894964b5c199 secretz/METADATA.TXT"
ACTUAL: "2cdcfa9f8bbefb82fb7a894964b5c199 secretz/SPYING.TXT"
EXPECTED: " secretz/SPYING.TXT"
ACTUAL: ""
EXPECTED: ""
# FAIL Then I switched to node $ npm version
{ http_parser: '1.0',
node: '0.10.36',
v8: '3.14.5.9',
ares: '1.9.0-DEV',
uv: '0.10.30',
zlib: '1.2.8',
modules: '11',
openssl: '1.0.1l',
npm: '1.4.28' } $ ./node_modules/.bin/stream-adventure verify ./stream-adventure/15-secretz.js
ACTUAL: "97911dcc607865d621029f6f927c7851 secretz/METADATA.TXT"
EXPECTED: "97911dcc607865d621029f6f927c7851 secretz/METADATA.TXT"
ACTUAL: "2cdcfa9f8bbefb82fb7a894964b5c199 secretz/SPYING.TXT"
EXPECTED: "2cdcfa9f8bbefb82fb7a894964b5c199 secretz/SPYING.TXT"
ACTUAL: ""
EXPECTED: ""
# PASS |
migrated this to stream-adventure repo workshopper/stream-adventure#114 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think the expected result of secretz is wrong:
So while my format is
It seems to weirdly expect
I'm on Win7 x64 and
[email protected]
,[email protected]
,[email protected]
.In case my code triggered this bug, here's what it was:
The text was updated successfully, but these errors were encountered: