Lý Điệp

Hi @andrewbaldwin44, This bug doesn't occur in the Old UI with the `--legacy-ui` flag Here is the video of this bug: In this video, I used the example locust file...

Hi @andrewbaldwin44 , for the option 1, here is the error message:  For Option 2, after installing locust in dev mode version: locust-2.23.2.dev10 The command locust show error when...

Hi @andrewbaldwin44 Here is the HTML file generated from Modern UI mode, hope it helps a bit for the investigation (Change extension .JSON to HTML) [locust_modern_report.JSON](https://github.com/locustio/locust/files/14368101/locust_modern_report.JSON) I am using latest...

> It might, I'll take a look @G1-Diep-Duong can you provide the gauge logs from gauge start until after the BdbQuit? And could you provide the output of running gauge...

> Can you test if the vscode breakpoints work? I tried with "Debug Scenario" function, and noticed that this issue did not occur with vscode breakpoints

@bockstaller Yes, of course it solved this issue, but I still prefer to use pdb.set_trace() more than using built_in function "Debug Scenario" because I can use some customized args for...

Manual debugging (outside IDE) confirms the issue persists in v1.6.1. As this is a critical bug, I recommend prioritizing its fix.