Test works when run independently, but hangs when run in a collection.

[SiJiL82]

I have a very basic request for an API tutorial, it just passes a JSON body to the API and gets a JSON object back as a response:

I've added this to a collection, and if I run it independently by clicking it in the collection so it opens and click Send, it runs fine - returns instantly.
If I click "Run All" on the collection however, it hangs on the request- the StatusCode column just spins and never comes back.
The request has run - I can manually call the Sign In request in another tab and that then responds correctly, but the Thunder Client UI never comes back from the request:

It seems to be doing it for any POST request, the GET I've done worked fine.

Is there something I need to do to the collection config or the requests themselves that I need to do to get it working?

[rangav]

Hi @SiJiL82 thanks for reporting the issue.

Try restarting vscode and run collection.

[SiJiL82]

Hi @rangav - still getting the same thing.
I am running vscode in WSL (Ubuntu) in Windows if that makes any difference.

[rangav]

Oh ok, can you try locally first without WSL?

It could be WSL issue

[SiJiL82]

Just tried in a local VSCode (new copy of the code, so not running from the repo in the WSL file structure) and get the same results.

[jwmickey]

I have observed this as well. A workaround is to close the run-all tab and re-open it.

[rangav]

Hi guys, can anyone share sample collection that can reproduce the error, for my testing?

You can remove any sensitive data

[rangav]

Hi guys, do you still have this issue, I have released a new update v1.10.0, can you confirm please?

[SiJiL82]

I'll try and find the API and tests I was using, it was part of a course I was doing before xmas!

[rangav]

This bug is now fixed in v1.11.0
https://github.com/rangav/thunder-client-support/releases/tag/v1.11.0

please let me know if any feedback

[jwmickey]

Apologies for the delay in feedback - this does appear to be working from my observations so far.

One thing I did notice is that for one request I have a test that expects the response code to be 400, but is now failing because according to TC it is 404. The actual response is indeed 400.

[rangav]

@jwmickey thanks for confirming

can you try re-run 1 or 2 times, sometimes it could be network issues

[jwmickey]

To be clear, I am *expecting* the response to be 400. I tried it several times and got back a 404. The ones where I expect a 200 are still 200.

…

On Wed, Jan 26, 2022 at 11:19 PM Ranga Vadhineni ***@***.***> wrote: @jwmickey <https://github.com/jwmickey> thanks for confirming can you try re-run 1 or 2 times, sometimes it could be network issues — Reply to this email directly, view it on GitHub <#407 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADBZ2CJI36U3Z5RAP5LMH3UYDBWBANCNFSM5JCFMOVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[rangav]

@jwmickey thanks for clarification

when you run that request independently are you getting 400 or 404?

[jwmickey]

I apologize @rangav, it is not 404. The first run it shows "Error" for StatusCode. Then I ran it independently and it showed 400 and the test passed. Then run in collection worked as expected.

First run:

Second run:

[rangav]

No problem @jwmickey good that it’s working now.

whenever there is error in run collection, mouse hover on Error text, it will show error details.