github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #9276] Unhandled Promise Rejection: Error: Token with "inlineKatex" type was not found. #30971

New Issue
Closed
opened 2026-04-25 05:05:02 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-25 05:05:02 -05:00
Owner
Copy Link

Originally created by @samuelhe52 on GitHub (Feb 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9276

Installation Method

Installed via pip, server running on Ubuntu 24.04.1

Environment

  • Open WebUI Version: v.0.5.7

  • Ollama (if applicable): Not using Ollama

  • Operating System: macOS 15.3

  • Browser (if applicable): Safari 18.3 & Chrome 132.0

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Actual Behavior:

After switching to a previous chat, then switching to New Chat, and then clicking on the model selection button, the web page becomes unresponsive.

Description

Bug Summary:
The page becomes unresponsive after switching to a previous chat, then switching to New Chat, and then clicking on the model selection button, and the console prints out an error message: "Unhandled Promise Rejection: Error: Token with "inlineKatex" type was not found."

Reproduction Details

Steps to Reproduce:
Switch to a previous chat, then switch to new chat, and then click on the model selection button would trigger the issue. Reproducible on Safari & Chrome on my mac and also Firefox on Ubuntu. Reloading the page resolves the problem.

Logs and Screenshots

Browser Console Logs:

[Log] {id: "", title: "🚦 Murphy’s Law Examples", models: ["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"], system: "You're a helpful assistant. You have access to som…y when the discussed topic is obviously relevant.", params: {}, …} (Help.B2mjg06d.js, line 137)
[Log] saveSessionSelectedModels (2) (Help.B2mjg06d.js, line 137)
["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"] (1)
"[\"deepseek_r1_realtime_thinking_preview.deepseek-reasoner\"]"
[Log] saveSessionSelectedModels (2) (Help.B2mjg06d.js, line 137)
["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"] (1)
"[\"deepseek_r1_realtime_thinking_preview.deepseek-reasoner\"]"
[Log] saveSessionSelectedModels (2) (Help.B2mjg06d.js, line 137)
["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"] (1)
"[\"deepseek_r1_realtime_thinking_preview.deepseek-reasoner\"]"
[Log]  (RichTextInput.Dr52WG8J.js, line 204)
[Log] size – 0 – 35 (Help.B2mjg06d.js, line 131)
[Warning] [tiptap warn]: Duplicate extension names found: ['codeBlock']. This can lead to issues. (RichTextInput.Dr52WG8J.js, line 113)
[Log] destroy (Help.B2mjg06d.js, line 6)
[Log] mounted (Help.B2mjg06d.js, line 137)
[Log]  (RichTextInput.Dr52WG8J.js, line 204)
[Log] size – 0 – 35 (Help.B2mjg06d.js, line 131)
[Warning] [tiptap warn]: Duplicate extension names found: ['codeBlock']. This can lead to issues. (RichTextInput.Dr52WG8J.js, line 113)
[Error] Unhandled Promise Rejection: Error: Token with "inlineKatex" type was not found.
Please report this to https://github.com/markedjs/marked.
	_t (scheduler.BXITcVIL.js:1:9816)

Server Side Logs:

Feb 03 18:25:16 nas-ThinkPad-T430s python[70792]: INFO:     100.108.7.103:63955 - "GET /api/v1/chats/2f04fa9a-6d8d-4aca-93a2-c0402d6a5fec HTTP/1.1" 200 OK
Feb 03 18:25:16 nas-ThinkPad-T430s python[70792]: INFO:     100.108.7.103:63957 - "GET /api/v1/chats/2f04fa9a-6d8d-4aca-93a2-c0402d6a5fec/tags HTTP/1.1" 200 OK
Feb 03 18:25:16 nas-ThinkPad-T430s python[70792]: INFO:     100.108.7.103:63959 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK
Feb 03 18:25:17 nas-ThinkPad-T430s python[70792]: INFO:     100.108.7.103:63961 - "GET /ollama/api/version HTTP/1.1" 200 OK
Feb 03 18:25:18 nas-ThinkPad-T430s python[70792]: INFO:     100.108.7.103:63963 - "GET /ollama/api/version HTTP/1.1" 200 OK
Feb 03 18:25:18 nas-ThinkPad-T430s python[70792]: INFO:     100.108.7.103:63965 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK
Originally created by @samuelhe52 on GitHub (Feb 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/9276 ## Installation Method Installed via pip, server running on Ubuntu 24.04.1 ## Environment - **Open WebUI Version:** v.0.5.7 - **Ollama (if applicable):** Not using Ollama - **Operating System:** macOS 15.3 - **Browser (if applicable):** Safari 18.3 & Chrome 132.0 **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Actual Behavior: After switching to a previous chat, then switching to New Chat, and then clicking on the model selection button, the web page becomes unresponsive. ## Description **Bug Summary:** The page becomes unresponsive after switching to a previous chat, then switching to New Chat, and then clicking on the model selection button, and the console prints out an error message: "Unhandled Promise Rejection: Error: Token with "inlineKatex" type was not found." ## Reproduction Details **Steps to Reproduce:** Switch to a previous chat, then switch to new chat, and then click on the model selection button would trigger the issue. Reproducible on Safari & Chrome on my mac and also Firefox on Ubuntu. Reloading the page resolves the problem. ## Logs and Screenshots **Browser Console Logs:** ``` [Log] {id: "", title: "🚦 Murphy’s Law Examples", models: ["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"], system: "You're a helpful assistant. You have access to som…y when the discussed topic is obviously relevant.", params: {}, …} (Help.B2mjg06d.js, line 137) [Log] saveSessionSelectedModels (2) (Help.B2mjg06d.js, line 137) ["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"] (1) "[\"deepseek_r1_realtime_thinking_preview.deepseek-reasoner\"]" [Log] saveSessionSelectedModels (2) (Help.B2mjg06d.js, line 137) ["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"] (1) "[\"deepseek_r1_realtime_thinking_preview.deepseek-reasoner\"]" [Log] saveSessionSelectedModels (2) (Help.B2mjg06d.js, line 137) ["deepseek_r1_realtime_thinking_preview.deepseek-reasoner"] (1) "[\"deepseek_r1_realtime_thinking_preview.deepseek-reasoner\"]" [Log] (RichTextInput.Dr52WG8J.js, line 204) [Log] size – 0 – 35 (Help.B2mjg06d.js, line 131) [Warning] [tiptap warn]: Duplicate extension names found: ['codeBlock']. This can lead to issues. (RichTextInput.Dr52WG8J.js, line 113) [Log] destroy (Help.B2mjg06d.js, line 6) [Log] mounted (Help.B2mjg06d.js, line 137) [Log] (RichTextInput.Dr52WG8J.js, line 204) [Log] size – 0 – 35 (Help.B2mjg06d.js, line 131) [Warning] [tiptap warn]: Duplicate extension names found: ['codeBlock']. This can lead to issues. (RichTextInput.Dr52WG8J.js, line 113) [Error] Unhandled Promise Rejection: Error: Token with "inlineKatex" type was not found. Please report this to https://github.com/markedjs/marked. _t (scheduler.BXITcVIL.js:1:9816) ``` **Server Side Logs:** ``` Feb 03 18:25:16 nas-ThinkPad-T430s python[70792]: INFO: 100.108.7.103:63955 - "GET /api/v1/chats/2f04fa9a-6d8d-4aca-93a2-c0402d6a5fec HTTP/1.1" 200 OK Feb 03 18:25:16 nas-ThinkPad-T430s python[70792]: INFO: 100.108.7.103:63957 - "GET /api/v1/chats/2f04fa9a-6d8d-4aca-93a2-c0402d6a5fec/tags HTTP/1.1" 200 OK Feb 03 18:25:16 nas-ThinkPad-T430s python[70792]: INFO: 100.108.7.103:63959 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK Feb 03 18:25:17 nas-ThinkPad-T430s python[70792]: INFO: 100.108.7.103:63961 - "GET /ollama/api/version HTTP/1.1" 200 OK Feb 03 18:25:18 nas-ThinkPad-T430s python[70792]: INFO: 100.108.7.103:63963 - "GET /ollama/api/version HTTP/1.1" 200 OK Feb 03 18:25:18 nas-ThinkPad-T430s python[70792]: INFO: 100.108.7.103:63965 - "GET /api/v1/users/user/settings HTTP/1.1" 200 OK ```
GiteaMirror commented 2026-04-25 05:05:03 -05:00
Author
Owner
Copy Link

@conner-replogle commented on GitHub (Feb 4, 2025):

I am also experiencing this issue

<!-- gh-comment-id:2632449501 --> @conner-replogle commented on GitHub (Feb 4, 2025): I am also experiencing this issue
GiteaMirror commented 2026-04-25 05:05:03 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 4, 2025):

We'll need a more reliable way to reproduce this issue consistently!

<!-- gh-comment-id:2632463327 --> @tjbck commented on GitHub (Feb 4, 2025): We'll need a more reliable way to reproduce this issue consistently!
GiteaMirror commented 2026-04-25 05:05:04 -05:00
Author
Owner
Copy Link

@samuelhe52 commented on GitHub (Feb 4, 2025):

A fresh installation using Docker doesn't have this issue, but after I replaced the webui.db file with the one from my pip installation and restarted the service, the issue shows up again. For me, this bug can be triggered 100% on every launch.

<!-- gh-comment-id:2632608678 --> @samuelhe52 commented on GitHub (Feb 4, 2025): A fresh installation using Docker doesn't have this issue, but after I replaced the webui.db file with the one from my pip installation and restarted the service, the issue shows up again. For me, this bug can be triggered 100% on every launch.
GiteaMirror commented 2026-04-25 05:05:04 -05:00
Author
Owner
Copy Link

@conner-replogle commented on GitHub (Feb 4, 2025):

The issue I encountered was caused by the markdown formatting of the model descriptions in the model dropdown. I had been using the symbols “”, “”, and “$$” to denote prices in my descriptions of each model. Removing these symbols from my descriptions resolved this problem.

<!-- gh-comment-id:2632713077 --> @conner-replogle commented on GitHub (Feb 4, 2025): The issue I encountered was caused by the markdown formatting of the model descriptions in the model dropdown. I had been using the symbols “$”, “$$”, and “$$$” to denote prices in my descriptions of each model. Removing these symbols from my descriptions resolved this problem.
GiteaMirror commented 2026-04-25 05:05:05 -05:00
Author
Owner
Copy Link

@samuelhe52 commented on GitHub (Feb 4, 2025):

The issue I encountered was caused by the markdown formatting of the model descriptions in the model dropdown. I had been using the symbols “”, “”, and “$$” to denote prices in my descriptions of each model. Removing these symbols from my descriptions resolved this problem.

I just found this out as well. Here is the exported model file, importing it in the model page should trigger the problem. In my case, I'm using "$$" to denote markdown-styled latex block.

models-export-1738638855312.json

<!-- gh-comment-id:2632733048 --> @samuelhe52 commented on GitHub (Feb 4, 2025): > The issue I encountered was caused by the markdown formatting of the model descriptions in the model dropdown. I had been using the symbols “$”, “$$”, and “$$$” to denote prices in my descriptions of each model. Removing these symbols from my descriptions resolved this problem. I just found this out as well. Here is the exported model file, importing it in the model page should trigger the problem. In my case, I'm using "$$" to denote markdown-styled latex block. [models-export-1738638855312.json](https://github.com/user-attachments/files/18651272/models-export-1738638855312.json)
GiteaMirror commented 2026-04-25 05:05:06 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Feb 13, 2025):

@samuelhe52 Is the models-export.json file you provided a custom model from a base model that is to be imported in the Models section of the Workspace? I did get the same error that this issue suggests upon importing it there:

Uncaught (in promise) Error: Token with "inlineKatex" type was not found.
Please report this to https://github.com/markedjs/marked.
    parseInline marked.esm.js:2015
    parse marked.esm.js:1915
    parse marked.esm.js:1801
    tt marked.esm.js:2297
    w marked.esm.js:2330
    Qe Models.svelte:275
    p Models.svelte:249
    p Models.svelte:202
    dt scheduler.js:119
    _t scheduler.js:79
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    onload Models.svelte:443
    T Models.svelte:416
    c rocket-loader.min.js:1
    addEventListener rocket-loader.min.js:1
    D dom.js:361
    m Models.svelte:495
    m Models.svelte:400
    p Models.svelte:202
    dt scheduler.js:119
    _t scheduler.js:79
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    rl Models.svelte:168
    J utils.js:41
    _t Component.js:47
    _t scheduler.js:99
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    $$set root.svelte:69
    $set Component.js:507
    z client.js:1424
    oe client.js:384
    fn client.js:1756
    q +page.svelte:20
marked.esm.js:2015:30

Then after refreshing the page, I saw the model on that page, so I started a new chat, clicked the model selector, and also witnessed a different, but similar browser console error again. This triggered the page to become unresponsive.

14:47:48.696 Uncaught (in promise) Error: Token with "inlineKatex" type was not found.
Please report this to https://github.com/markedjs/marked.
    parseInline marked.esm.js:2015
    parse marked.esm.js:1915
    parse marked.esm.js:1801
    tt marked.esm.js:2297
    w marked.esm.js:2330
    tt Selector.svelte:417
    nt Selector.svelte:415
    sl Selector.svelte:305
    ol Selector.svelte:493
    vt utils.js:165
    ss menu-content.svelte:74
    p menu-content.svelte:101
    dt scheduler.js:119
    _t scheduler.js:79
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    De Selector.svelte:237
    a Selector.svelte:267
    ctx Component.js:138
    onOpenChange menu.svelte:37
    r overridable.js:9
    f index.js:69
    r overridable.js:5
    Gt create.js:1044
    destroy create.js:201
    s event.js:23
    _ event.js:51
    c rocket-loader.min.js:1
    addEventListener rocket-loader.min.js:1
    z event.js:25
    z event.js:25
    action create.js:196
    m menu-trigger.svelte:36
    m menu-trigger.svelte:24
    _t Component.js:44
    m Selector.svelte:268
    m menu.svelte:72
    _t Component.js:44
    m Selector.svelte:237
    _t Component.js:44
    m ModelSelector.svelte:53
    m ModelSelector.svelte:111
    _t Component.js:44
    m Navbar.svelte:78
    m Navbar.svelte:80
    _t Component.js:44
    m Chat.svelte:1918
    m Chat.svelte:2102
    _t Component.js:44
    m Immutable
    _t Component.js:44
    p root.svelte:57
    p root.svelte:51
    Nt utils.js:203
    p +layout.svelte:246
    p +layout.svelte:243
    dt scheduler.js:119
marked.esm.js:2015:30

Once the model is deleted, the issue resolves itself. This has been tested on Mozilla Firefox v135.0 (64-bit).

<!-- gh-comment-id:2657568964 --> @silentoplayz commented on GitHub (Feb 13, 2025): @samuelhe52 Is the models-export.json file you provided a custom model from a base model that is to be imported in the `Models` section of the `Workspace`? I did get the same error that this issue suggests upon importing it there: ``` Uncaught (in promise) Error: Token with "inlineKatex" type was not found. Please report this to https://github.com/markedjs/marked. parseInline marked.esm.js:2015 parse marked.esm.js:1915 parse marked.esm.js:1801 tt marked.esm.js:2297 w marked.esm.js:2330 Qe Models.svelte:275 p Models.svelte:249 p Models.svelte:202 dt scheduler.js:119 _t scheduler.js:79 promise callback*ut scheduler.js:20 ht Component.js:81 ctx Component.js:139 onload Models.svelte:443 T Models.svelte:416 c rocket-loader.min.js:1 addEventListener rocket-loader.min.js:1 D dom.js:361 m Models.svelte:495 m Models.svelte:400 p Models.svelte:202 dt scheduler.js:119 _t scheduler.js:79 promise callback*ut scheduler.js:20 ht Component.js:81 ctx Component.js:139 rl Models.svelte:168 J utils.js:41 _t Component.js:47 _t scheduler.js:99 promise callback*ut scheduler.js:20 ht Component.js:81 ctx Component.js:139 $$set root.svelte:69 $set Component.js:507 z client.js:1424 oe client.js:384 fn client.js:1756 q +page.svelte:20 marked.esm.js:2015:30 ``` Then after refreshing the page, I saw the model on that page, so I started a new chat, clicked the model selector, and also witnessed a different, but similar browser console error again. This triggered the page to become unresponsive. ``` 14:47:48.696 Uncaught (in promise) Error: Token with "inlineKatex" type was not found. Please report this to https://github.com/markedjs/marked. parseInline marked.esm.js:2015 parse marked.esm.js:1915 parse marked.esm.js:1801 tt marked.esm.js:2297 w marked.esm.js:2330 tt Selector.svelte:417 nt Selector.svelte:415 sl Selector.svelte:305 ol Selector.svelte:493 vt utils.js:165 ss menu-content.svelte:74 p menu-content.svelte:101 dt scheduler.js:119 _t scheduler.js:79 promise callback*ut scheduler.js:20 ht Component.js:81 ctx Component.js:139 De Selector.svelte:237 a Selector.svelte:267 ctx Component.js:138 onOpenChange menu.svelte:37 r overridable.js:9 f index.js:69 r overridable.js:5 Gt create.js:1044 destroy create.js:201 s event.js:23 _ event.js:51 c rocket-loader.min.js:1 addEventListener rocket-loader.min.js:1 z event.js:25 z event.js:25 action create.js:196 m menu-trigger.svelte:36 m menu-trigger.svelte:24 _t Component.js:44 m Selector.svelte:268 m menu.svelte:72 _t Component.js:44 m Selector.svelte:237 _t Component.js:44 m ModelSelector.svelte:53 m ModelSelector.svelte:111 _t Component.js:44 m Navbar.svelte:78 m Navbar.svelte:80 _t Component.js:44 m Chat.svelte:1918 m Chat.svelte:2102 _t Component.js:44 m Immutable _t Component.js:44 p root.svelte:57 p root.svelte:51 Nt utils.js:203 p +layout.svelte:246 p +layout.svelte:243 dt scheduler.js:119 marked.esm.js:2015:30 ``` Once the model is deleted, the issue resolves itself. This has been tested on Mozilla Firefox v135.0 (64-bit).
GiteaMirror commented 2026-04-25 05:05:07 -05:00
Author
Owner
Copy Link

@samuelhe52 commented on GitHub (Feb 14, 2025):

Yes, that's exactly what I mean, importing the model file in the Models section would trigger the issue.

<!-- gh-comment-id:2659442334 --> @samuelhe52 commented on GitHub (Feb 14, 2025): Yes, that's exactly what I mean, importing the model file in the `Models` section would trigger the issue.
GiteaMirror commented 2026-04-25 05:05:07 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 20, 2025):

Potentially addressed with the latest dev, testing wanted after 0.5.15 release!

<!-- gh-comment-id:2671006143 --> @tjbck commented on GitHub (Feb 20, 2025): Potentially addressed with the latest dev, testing wanted after 0.5.15 release!
GiteaMirror commented 2026-04-25 05:05:08 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Feb 21, 2025):

Uncaught (in promise) Error: Token with "inlineKatex" type was not found.
Please report this to https://github.com/markedjs/marked.
    parseInline marked.esm.js:2015
    parse marked.esm.js:1915
    parse marked.esm.js:1801
    tt marked.esm.js:2297
    w marked.esm.js:2330
    Qe Models.svelte:275
    p Models.svelte:249
    p Models.svelte:202
    dt scheduler.js:119
    _t scheduler.js:79
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    onload Models.svelte:443
    T Models.svelte:416
    c rocket-loader.min.js:1
    addEventListener rocket-loader.min.js:1
    D dom.js:361
    m Models.svelte:495
    m Models.svelte:400
    p Models.svelte:202
    dt scheduler.js:119
    _t scheduler.js:79
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    rl Models.svelte:168
    J utils.js:41
    _t Component.js:47
    _t scheduler.js:99
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    $$set root.svelte:69
    $set Component.js:507
    z client.js:1424
    oe client.js:384
    fn client.js:1756
    q +page.svelte:20
marked.esm.js:2015:30

Then after refreshing the page, I saw the model on that page, so I started a new chat, clicked the model selector, and also witnessed a different, but similar browser console error again. This triggered the page to become unresponsive.

14:47:48.696 Uncaught (in promise) Error: Token with "inlineKatex" type was not found.
Please report this to https://github.com/markedjs/marked.
    parseInline marked.esm.js:2015
    parse marked.esm.js:1915
    parse marked.esm.js:1801
    tt marked.esm.js:2297
    w marked.esm.js:2330
    tt Selector.svelte:417
    nt Selector.svelte:415
    sl Selector.svelte:305
    ol Selector.svelte:493
    vt utils.js:165
    ss menu-content.svelte:74
    p menu-content.svelte:101
    dt scheduler.js:119
    _t scheduler.js:79
    promise callback*ut scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    De Selector.svelte:237
    a Selector.svelte:267
    ctx Component.js:138
    onOpenChange menu.svelte:37
    r overridable.js:9
    f index.js:69
    r overridable.js:5
    Gt create.js:1044
    destroy create.js:201
    s event.js:23
    _ event.js:51
    c rocket-loader.min.js:1
    addEventListener rocket-loader.min.js:1
    z event.js:25
    z event.js:25
    action create.js:196
    m menu-trigger.svelte:36
    m menu-trigger.svelte:24
    _t Component.js:44
    m Selector.svelte:268
    m menu.svelte:72
    _t Component.js:44
    m Selector.svelte:237
    _t Component.js:44
    m ModelSelector.svelte:53
    m ModelSelector.svelte:111
    _t Component.js:44
    m Navbar.svelte:78
    m Navbar.svelte:80
    _t Component.js:44
    m Chat.svelte:1918
    m Chat.svelte:2102
    _t Component.js:44
    m Immutable
    _t Component.js:44
    p root.svelte:57
    p root.svelte:51
    Nt utils.js:203
    p +layout.svelte:246
    p +layout.svelte:243
    dt scheduler.js:119
marked.esm.js:2015:30

Once the model is deleted, the issue resolves itself. This has been tested on Mozilla Firefox v135.0 (64-bit).

This appears addressed on my end!

<!-- gh-comment-id:2675530817 --> @silentoplayz commented on GitHub (Feb 21, 2025): > ``` > Uncaught (in promise) Error: Token with "inlineKatex" type was not found. > Please report this to https://github.com/markedjs/marked. > parseInline marked.esm.js:2015 > parse marked.esm.js:1915 > parse marked.esm.js:1801 > tt marked.esm.js:2297 > w marked.esm.js:2330 > Qe Models.svelte:275 > p Models.svelte:249 > p Models.svelte:202 > dt scheduler.js:119 > _t scheduler.js:79 > promise callback*ut scheduler.js:20 > ht Component.js:81 > ctx Component.js:139 > onload Models.svelte:443 > T Models.svelte:416 > c rocket-loader.min.js:1 > addEventListener rocket-loader.min.js:1 > D dom.js:361 > m Models.svelte:495 > m Models.svelte:400 > p Models.svelte:202 > dt scheduler.js:119 > _t scheduler.js:79 > promise callback*ut scheduler.js:20 > ht Component.js:81 > ctx Component.js:139 > rl Models.svelte:168 > J utils.js:41 > _t Component.js:47 > _t scheduler.js:99 > promise callback*ut scheduler.js:20 > ht Component.js:81 > ctx Component.js:139 > $$set root.svelte:69 > $set Component.js:507 > z client.js:1424 > oe client.js:384 > fn client.js:1756 > q +page.svelte:20 > marked.esm.js:2015:30 > ``` > > Then after refreshing the page, I saw the model on that page, so I started a new chat, clicked the model selector, and also witnessed a different, but similar browser console error again. This triggered the page to become unresponsive. > > ``` > 14:47:48.696 Uncaught (in promise) Error: Token with "inlineKatex" type was not found. > Please report this to https://github.com/markedjs/marked. > parseInline marked.esm.js:2015 > parse marked.esm.js:1915 > parse marked.esm.js:1801 > tt marked.esm.js:2297 > w marked.esm.js:2330 > tt Selector.svelte:417 > nt Selector.svelte:415 > sl Selector.svelte:305 > ol Selector.svelte:493 > vt utils.js:165 > ss menu-content.svelte:74 > p menu-content.svelte:101 > dt scheduler.js:119 > _t scheduler.js:79 > promise callback*ut scheduler.js:20 > ht Component.js:81 > ctx Component.js:139 > De Selector.svelte:237 > a Selector.svelte:267 > ctx Component.js:138 > onOpenChange menu.svelte:37 > r overridable.js:9 > f index.js:69 > r overridable.js:5 > Gt create.js:1044 > destroy create.js:201 > s event.js:23 > _ event.js:51 > c rocket-loader.min.js:1 > addEventListener rocket-loader.min.js:1 > z event.js:25 > z event.js:25 > action create.js:196 > m menu-trigger.svelte:36 > m menu-trigger.svelte:24 > _t Component.js:44 > m Selector.svelte:268 > m menu.svelte:72 > _t Component.js:44 > m Selector.svelte:237 > _t Component.js:44 > m ModelSelector.svelte:53 > m ModelSelector.svelte:111 > _t Component.js:44 > m Navbar.svelte:78 > m Navbar.svelte:80 > _t Component.js:44 > m Chat.svelte:1918 > m Chat.svelte:2102 > _t Component.js:44 > m Immutable > _t Component.js:44 > p root.svelte:57 > p root.svelte:51 > Nt utils.js:203 > p +layout.svelte:246 > p +layout.svelte:243 > dt scheduler.js:119 > marked.esm.js:2015:30 > ``` > > Once the model is deleted, the issue resolves itself. This has been tested on Mozilla Firefox v135.0 (64-bit). This appears addressed on my end!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#30971
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?