If the blocking command receives a response that isn’t well formed, i.e. a legitimate RESP array that doesn’t quite contain the right ‘schema’ as far as the command is concerned, it doesn’t log any errors. The test still fails as it times out but I thought that it was pretty annoying that no feedback was given.
Hi @jamestjw, thanks for highlighting this issue!
This is a known issue, and we’ve created an internal ticket to address it. However, it may take some time to implement the fix.
Let us know if you encounter other issues!
1 Like
does this only happen with ‘async’ tests so does this occur everywhere else too? This might be surprising but this is my first time submitting a wrongly formatted output so I had never encountered this before.
The stream extension may currently be prone to incomplete error messages. Once it’s migrated to the newer tester framework used in the base stages, these issues should be resolved.
ok no worries I’m nearly done with this extension anyway.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.