starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #2897] [bug]: Time counter doesn't stop (ever) after a request was cancelled #938

New issue

Closed

opened 2026-03-16 17:45:16 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 17:45:16 +03:00

Owner

Originally created by @cpt-westphalen on GitHub (Jan 6, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2897

Originally assigned to: @aitchnyu on GitHub.

This might be a simple issue to solve:

I use the web Hoppscotch app.
If my API has a bug and doesn't respond to a request, Hopp allows me to click the big "cancel" button to stop the listening.

After that, every other request I make happens to -- as fast as the response time is -- never clear the time counter again:

The solution is probably just checking the counter function and the cancel button function to see what's missing.

Thank you all for this amazing app, by the way. :)

Originally created by @cpt-westphalen on GitHub (Jan 6, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2897 Originally assigned to: @aitchnyu on GitHub. This might be a simple issue to solve: I use the web Hoppscotch app. If my API has a bug and doesn't respond to a request, Hopp allows me to click the big "cancel" button to stop the listening. After that, every other request I make happens to -- as fast as the response time is -- never clear the time counter again: ![image](https://user-images.githubusercontent.com/97403327/211075892-c415d03e-a189-46aa-84df-cecf2210855c.png) The solution is probably just checking the counter function and the cancel button function to see what's missing. Thank you all for this amazing app, by the way. :)

kerem closed this issue

2026-03-16 17:45:21 +03:00

kerem commented

2026-03-16 17:45:27 +03:00

Author

Owner

@Imaginarybandit commented on GitHub (Jan 23, 2023):

Hello, I would like to tackle this issue

@Imaginarybandit commented on GitHub (Jan 23, 2023): Hello, I would like to tackle this issue

kerem commented

2026-03-16 17:45:32 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 23, 2023):

Hi @Imaginarybandit, feel free to look into this bug.

@liyasthomas commented on GitHub (Jan 23, 2023): Hi @Imaginarybandit, feel free to look into this bug.

kerem commented

2026-03-16 17:45:37 +03:00

Author

Owner

@aitchnyu commented on GitHub (Feb 2, 2023):

@cpt-westphalen I'm having a hard time reproducing this bug. Could you describe how to trigger it in steps I can do?

@aitchnyu commented on GitHub (Feb 2, 2023): @cpt-westphalen I'm having a hard time reproducing this bug. Could you describe how to trigger it in steps I can do?

kerem commented

2026-03-16 17:45:42 +03:00

Author

Owner

@cpt-westphalen commented on GitHub (Feb 2, 2023):

@aitchnyu This is it:

New folder, npm init -y, npm i express;
Create index.js file on root;
Paste this:

// index.js
const express = require("express");
const app = express();

app.get("/", (req, res) => console.log("this wont reply, ever."));
app.get("/reply", (req, res) => res.json({ hello: "world" }));

app.listen(3000, () => console.log("Serving at: http://localhost:3000/"));

Run node index.js on terminal;
Open Hop on latest Firefox (did not test on Chrome);
Configure it to use the Firefox extension to hit the localhost;
On Hop, select GET, paste/type http://localhost:3000/reply and send request. // => it will answer with < 100ms.
Keep GET, paste/type http://localhost:3000/ and send request. // => it will load for several seconds
Before the loading bar gets to the end, click the blue Cancel button to stop listening for response.
Keep GET, paste/type http://localhost:3000/reply and send request. // => it will answer with a huge response time

@cpt-westphalen commented on GitHub (Feb 2, 2023): @aitchnyu This is it: 1. New folder, `npm init -y`, `npm i express`; 2. Create `index.js` file on root; 3. Paste this: ``` // index.js const express = require("express"); const app = express(); app.get("/", (req, res) => console.log("this wont reply, ever.")); app.get("/reply", (req, res) => res.json({ hello: "world" })); app.listen(3000, () => console.log("Serving at: http://localhost:3000/")); ``` 4. Run `node index.js` on terminal; 5. Open [Hop](https://hoppscotch.io/) on latest Firefox (did not test on Chrome); 6. Configure it to use the Firefox extension to hit the localhost; 7. On Hop, select `GET`, paste/type `http://localhost:3000/reply` and send request. // **=> it will answer with < 100ms.** 8. Keep `GET`, paste/type `http://localhost:3000/` and send request. // **=> it will load for several seconds** 9. Before the loading bar gets to the end, click the blue `Cancel` button to stop listening for response. 10. Keep `GET`, paste/type `http://localhost:3000/reply` and send request. // **=> it will answer with a huge response time**

kerem commented

2026-03-16 17:45:47 +03:00

Author

Owner

@abrahamparayil commented on GitHub (Feb 5, 2023):

@cpt-westphalen I tried to reproduce the bug using the steps you have mentioned here but I am unable to reproduce the issue. The second GET request mentioned in step 10 responds back almost instantaneously.

Cc: @aitchnyu

@abrahamparayil commented on GitHub (Feb 5, 2023): @cpt-westphalen I tried to reproduce the bug using the steps you have mentioned here but I am unable to reproduce the issue. The second `GET` request mentioned in step 10 responds back almost instantaneously. Cc: @aitchnyu

kerem commented

2026-03-16 17:45:52 +03:00

Author

Owner

@aitchnyu commented on GitHub (Feb 6, 2023):

I can confirm for Firefox and hoppscotch.io. Will check with other users to see if its a fluke.

This is my experience. I called /, waited, called /reply, got 15743 ms, called /reply again and got a 37 ms. But I got many cases of: 3-5 subsequent requests to /reply will also have high response times till they converge into the milliseconds range.

Screencast from 2023-02-06 20-08-02.webm

@aitchnyu commented on GitHub (Feb 6, 2023): I can confirm for Firefox and hoppscotch.io. Will check with other users to see if its a fluke. This is my experience. I called `/`, waited, called `/reply`, got 15743 ms, called `/reply` again and got a 37 ms. But I got many cases of: 3-5 subsequent requests to `/reply` will also have high response times till they converge into the milliseconds range. [Screencast from 2023-02-06 20-08-02.webm](https://user-images.githubusercontent.com/5927706/217001056-fca2599e-b945-4fbb-bcea-78afc25dc198.webm)

kerem commented

2026-03-16 17:45:57 +03:00

Author

Owner

@Vansh-Baghel commented on GitHub (Feb 7, 2023):

@aitchnyu I guess that fixes the issue, right?

@Vansh-Baghel commented on GitHub (Feb 7, 2023): @aitchnyu I guess that fixes the issue, right?

kerem referenced this issue

2026-03-17 00:36:47 +03:00

[PR #938] [MERGED] ⬆️ Bump graphql from 14.6.0 to 15.1.0 #2951