[GH-ISSUE #16162] issue: The program cannot stop at the breakpoint during debugging in VSCode. #17809

New Issue

2026-04-19T23:42:09-05:00

GiteaMirror commented

2026-04-19 23:42:09 -05:00

Originally created by @GuokaiLiu on GitHub (Jul 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16162

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

0.6.18

Ollama Version (if applicable)

0.9.1

Operating System

Windows10., macOS Sequoia

Browser (if applicable)

Microsoft Edge 138.0.3351.109

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

I want to debug the latest Open-WebUI in VSCode and expect the program to stop at the breakpoint during debugging in VSCode.

Actual Behavior

Open-WebUI: 0.6.0 can stop at the breakpoint during debugging in VSCode.

Open-WebUI: 0.6.18 cannot stop at the breakpoint during debugging in VSCode.

Steps to Reproduce

I have installed Open-WebUI by pip install open-webui

And set the .vscode/launch.json file as follows.


 {
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python Debugger: FastAPI",
            "type": "debugpy",
            "request": "launch",
            "program": "${workspaceFolder}/__init__.py",  
            "args": [
                "serve",  
                "--host", "0.0.0.0",
                "--port", "8080"
            ],
            "jinja": true,
            "justMyCode": false,  
            "purpose": ["debug-in-terminal"] 
        }
    ],
}

Open-WebUI 0.6.0 and Open-WebUI 0.6.18 are configured the same way.

Logs & Screenshots

See actual behaveior

Additional Information

No response

Originally created by @GuokaiLiu on GitHub (Jul 30, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16162 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version 0.6.18 ### Ollama Version (if applicable) 0.9.1 ### Operating System Windows10., macOS Sequoia ### Browser (if applicable) Microsoft Edge 138.0.3351.109 ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior I want to debug the latest Open-WebUI in VSCode and expect the program to stop at the breakpoint during debugging in VSCode. ### Actual Behavior - Open-WebUI: 0.6.0 can stop at the breakpoint during debugging in VSCode. <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/558589ec-5476-4d05-b080-72913b475f77" /> - Open-WebUI: 0.6.18 cannot stop at the breakpoint during debugging in VSCode. <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/d06a6047-d2e3-4976-b88e-302de89774a5" /> ### Steps to Reproduce I have installed Open-WebUI by `pip install open-webui` And set the `.vscode/launch.json` file as follows. ```json { "version": "0.2.0", "configurations": [ { "name": "Python Debugger: FastAPI", "type": "debugpy", "request": "launch", "program": "${workspaceFolder}/__init__.py", "args": [ "serve", "--host", "0.0.0.0", "--port", "8080" ], "jinja": true, "justMyCode": false, "purpose": ["debug-in-terminal"] } ], } ``` Open-WebUI 0.6.0 and Open-WebUI 0.6.18 are configured the same way. ### Logs & Screenshots See actual behaveior ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-19 23:42:09 -05:00

GiteaMirror closed this issue

2026-04-19 23:42:10 -05:00

GiteaMirror commented

2026-04-19 23:42:11 -05:00

@guenhter commented on GitHub (Jul 31, 2025):

Can you try to place the brekepoint somewhere else (e.g. in the startup procedure where you are sure it is visitted) just to be sure...

@guenhter commented on GitHub (Jul 31, 2025): Can you try to place the brekepoint somewhere else (e.g. in the startup procedure where you are sure it is visitted) just to be sure...

GiteaMirror referenced this issue

2026-04-20 00:37:09 -05:00

[GH-ISSUE #17809] issue: Always refer only to the first pasted long text file #18403

GiteaMirror referenced this issue

2026-04-25 07:48:48 -05:00

[GH-ISSUE #17809] issue: Always refer only to the first pasted long text file #33932

GiteaMirror referenced this issue

2026-05-05 20:33:38 -05:00

[GH-ISSUE #17809] issue: Always refer only to the first pasted long text file #57069

GiteaMirror referenced this issue

2026-05-13 05:16:22 -05:00

[GH-ISSUE #17809] issue: Always refer only to the first pasted long text file #73007