I have checked the following:
This bug is:
Bruno version
3.0.3
Operating System
ubuntu-latest
Describe the bug
Response queries like res("foo") randomly start producing non-sensical results like "bearer" or "POST", obviously referencing header or HTTP verb instead of body. Once this starts happening, all subsequent response queries result in the same string. This affects both asserts and variables being set from response queries.
We have seen this behavior sporadically in the GUI client with 2.x versions and 3.x versions. Have to restart the client in those cases to make it work ok again. So for the GUI client, it is annoying.
But now it also started to happen in our pipeline using latest CLI version, making the pipeline useless. I suspect this is not specific to 3.x CLI, but we are just seeing it now due to our growing collection.
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The screenshot also shows how everything is fine and then response queries start failing for the same response. For all following requests, res("<whatever>") is evaluated to "bearer" in this run.
I have checked the following:
This bug is:
Bruno version
3.0.3
Operating System
ubuntu-latest
Describe the bug
Response queries like
res("foo")randomly start producing non-sensical results like "bearer" or "POST", obviously referencing header or HTTP verb instead of body. Once this starts happening, all subsequent response queries result in the same string. This affects both asserts and variables being set from response queries.We have seen this behavior sporadically in the GUI client with 2.x versions and 3.x versions. Have to restart the client in those cases to make it work ok again. So for the GUI client, it is annoying.
But now it also started to happen in our pipeline using latest CLI version, making the pipeline useless. I suspect this is not specific to 3.x CLI, but we are just seeing it now due to our growing collection.
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The screenshot also shows how everything is fine and then response queries start failing for the same response. For all following requests,
res("<whatever>")is evaluated to "bearer" in this run.