Hey, encountered a bit of trouble in the "Should encode/decode w/arbitrary rail sizes and original message" section of the tests. Boiled down to missing definitions for 'get_rails' and 'get_indices' which I think I managed to reverse engineer but there still seems to be some reference data missing when running the tests, leading to list index out of range. Care to take a look? :)
Let me know if you need more detailed output or if I can otherwise be of assistance!
I had en error in my code that caused an infinite (or at least very long, I was unable to solve the halting problem while debugging) loop for that specific piece of input. It was caused by the usual culprit - faulty assumptions.
Full disclosure: I printed the incoming (n,x) to stderr so that I was able to debug my code locally and figure out the problem.
This comment is hidden because it contains spoiler information about the solution
Cheers!
Hey, encountered a bit of trouble in the "Should encode/decode w/arbitrary rail sizes and original message" section of the tests. Boiled down to missing definitions for 'get_rails' and 'get_indices' which I think I managed to reverse engineer but there still seems to be some reference data missing when running the tests, leading to list index out of range. Care to take a look? :)
Let me know if you need more detailed output or if I can otherwise be of assistance!
Thank you.
This comment is hidden because it contains spoiler information about the solution
I had en error in my code that caused an infinite (or at least very long, I was unable to solve the halting problem while debugging) loop for that specific piece of input. It was caused by the usual culprit - faulty assumptions.
Full disclosure: I printed the incoming (n,x) to stderr so that I was able to debug my code locally and figure out the problem.
This comment is hidden because it contains spoiler information about the solution
Huh. I may have ended up using a bit of a hack to get around that. Apologies if that was poor sport! :-)