The error stack is inaccurate when using a query with a filter that doesn't return any result

[lepapareil]

Steps to reproduce

Create /tmp/test.hurl file :

GET https://hurl.dev/broken
HTTP 404
[Captures]
id: xpath "string(//span[@class='comment'])"

Executing hurl --test /tmp/test.hurl must succeed :

/tmp/test.hurl: Success (1 request(s) in 321 ms)

Then update /tmp/test.hurl file, adding a non-working regex filter :

GET https://hurl.dev/broken
HTTP 404
[Captures]
id: xpath "string(//span[@class='comment'])" regex "this regex does not work"

Executing hurl --test /tmp/test.hurl must fail, but the error stack is on the query instead of the filter :

error: No query result
  --> /tmp/test.hurl:4:5
   |
   | GET https://hurl.dev/broken
   | ...
 4 | id: xpath "string(//span[@class='comment'])" regex "this regex does not work"
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The query didn't return any result
   |

/tmp/test.hurl: Failure (1 request(s) in 323 ms)

What is the expected correct behavior?

error: No query result
  --> /tmp/test.hurl:4:5
   |
   | GET https://hurl.dev/broken
   | ...
 4 | id: xpath "string(//span[@class='comment'])" regex "this regex does not work"
   |                                              ^^^^^ The filter didn't return any result
   |

/tmp/test.hurl: Failure (1 request(s) in 323 ms)

Execution context

• Hurl Version (hurl --version): 5.0.1