Stage #QJ0 (Executing a quoted executable) is difficult to debug

I’m stuck on Stage #QJ0 (Executing a quoted executable).

Given that my code passes the previous stages, I thought the previously implemented argument parsing should make this stage pass. However, it doesn’t and I am finding this difficult to debug.

Nothing prints to stdout when running 'exe with space' <file> so I tried printing stderr:

exe  with  space: applet not found

Not sure what exactly that means - maybe the executable is not found? so I tried using Python’s os.listdir at the executable’s path and I can see the executables and text files are all present.

But trying to run file <executablePath> to understand the executable with Python’s subprocess.run fails and I only get the first line of the Traceback:

Traceback (most recent call last):

I am assuming the tester only waits for the first line of stdout and then fails the test when it not expected - but this means I am unable to debug the issue causing the traceback since the first line doesn’t help much.

Hi @warpftl, thanks for highlighting the issue!

We’ll review it internally and discuss potential improvements. I’ll get back to you as soon as possible.

@warpftl We’ve resolved the applet bug in these PRs: shell-tester #56 and shell-tester #58.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.