Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1795] [BUG]: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 | Windows #1173

New Issue
Closed
opened 2026-02-22 18:23:30 -05:00 by yindo · 9 comments
yindo commented 2026-02-22 18:23:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @njss on GitHub (Jun 30, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1795

Originally assigned to: @timothycarambat on GitHub.

How are you running AnythingLLM?

Docker (local)

What happened?

When trying to ask a question, I get the following error message (using any models):
Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135

Are there known steps to reproduce?

Configure the sw
upload a pdf document
ask a question

Originally created by @njss on GitHub (Jun 30, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1795 Originally assigned to: @timothycarambat on GitHub. ### How are you running AnythingLLM? Docker (local) ### What happened? When trying to ask a question, I get the following error message (using any models): Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 ### Are there known steps to reproduce? Configure the sw upload a pdf document ask a question
yindo added the possible bugcore-team-onlyDesktopOS: Windows labels 2026-02-22 18:23:30 -05:00
yindo closed this issue 2026-02-22 18:23:31 -05:00
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@RockinRoddieAi commented on GitHub (Jun 30, 2024):

I am facing the exact same issue. I installed version 1.5.8. I have this issue on both of my Windows 11 Pro computers

I have tried to uninstall the model(s) and reinstall them and no go. This error renders Anything LLM useless and unusable. :(

I uninstalled 1.5.8 and went back to 1.5.7 and it works on both of my PCs

@RockinRoddieAi commented on GitHub (Jun 30, 2024): I am facing the exact same issue. I installed version 1.5.8. I have this issue on both of my Windows 11 Pro computers I have tried to uninstall the model(s) and reinstall them and no go. This error renders Anything LLM useless and unusable. :( I uninstalled 1.5.8 and went back to 1.5.7 and it works on both of my PCs
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@droza123 commented on GitHub (Jul 1, 2024):

Same problem here with 1.5.8. Totally fresh install.

@droza123 commented on GitHub (Jul 1, 2024): Same problem here with 1.5.8. Totally fresh install.
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 1, 2024):

This error is obviously tied back to ollama, I have a feeling it is device related. Please run the app in debug mode and on boot and when sending a chat there should be logs that describe the whole ollama runtime

https://docs.useanything.com/debug#anythingllm-debug-mode-on-windows

I will need those to help. I would prefer to not go back to the previous Ollama version as it is slower and the newer version has improved greatly.

Other details:

  • Do you have GPU?
  • CUDA installed? If so, which version
  • CPU specs (does it support AVX?)
@timothycarambat commented on GitHub (Jul 1, 2024): This error is obviously tied back to ollama, I have a feeling it is device related. Please run the app in debug mode and on boot and when sending a chat there should be logs that describe the whole ollama runtime https://docs.useanything.com/debug#anythingllm-debug-mode-on-windows I will need those to help. I would prefer to not go back to the previous Ollama version as it is slower and the newer version has improved greatly. Other details: - Do you have GPU? - CUDA installed? If so, which version - CPU specs (does it support AVX?)
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 1, 2024):

This error renders Anything LLM useless and unusable.

You can just use literally any other provider to get around this. Does downloading Ollama directly from them and just connecting with AnythingLLM still yield the same issue?

@timothycarambat commented on GitHub (Jul 1, 2024): > This error renders Anything LLM useless and unusable. You can just use literally any other provider to get around this. Does downloading Ollama directly from them and just connecting with AnythingLLM still yield the same issue?
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@RockinRoddieAi commented on GitHub (Jul 1, 2024):

Yah downloading directly did not seem to resolve the issue with 1.5.8. And yes I understand i can use other providers, i was trying to keep my deployment straight forward.

@RockinRoddieAi commented on GitHub (Jul 1, 2024): Yah downloading directly did not seem to resolve the issue with 1.5.8. And yes I understand i can use other providers, i was trying to keep my deployment straight forward.
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@RockinRoddieAi commented on GitHub (Jul 1, 2024):

Hi

I followed the debugging mode instructions. Log file details are below.

I have this issue on two issues:

Workstation specs:

GPU = Yes

NVIDIA GeForce RTX 3090

CPU = 12th Gen Intel Core i9-1290 3.19 GHz and yes it supports AVX

Laptop specs:

GPU = Yes

NVIDIA GeForce RTX 3050

CPU = 12th Gen Intel Core i-12700H 2.30 GHz and yes it supports AVX

C:\Users\r0ss\AppData\Local\Programs\anythingllm-desktop>

[Preferences] preference config stored at C:\Users\r0ss\AppData\Roaming\anythingllm-desktop\config.json

Prisma schema loaded from prisma\schema.prisma

Datasource "db": SQLite database "anythingllm.db" at "file:C:/Users/r0ss/AppData/Roaming/anythingllm-desktop/storage/anythingllm.db"

Already in sync, no schema change or pending migration was found.

Γ£ö Generated Prisma Client (v5.3.1) to .@.***\client in 342ms

Prisma schema loaded from prisma\schema.prisma

Γ£ö Generated Prisma Client (v5.3.1) to .@.***\client in 309ms

Start using Prisma Client in Node.js (See: https://pris.ly/d/client)


import { PrismaClient } from ***@***.***/client'

const prisma = new PrismaClient()

or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)


import { PrismaClient } from ***@***.***/client/edge'

const prisma = new PrismaClient()

See other ways of importing Prisma Client: http://pris.ly/d/importing-client

[OllamaProcessManager] Ollama will bind on port 11434 when booted.

[Preferences] Will load window with last know bounds.

Collector hot directory and tmp storage wiped!

[production] AnythingLLM Standalone Document processor listening on port 8888

[TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.

prisma:info Starting a sqlite pool with 33 connections.

[TELEMETRY SENT] {

event: 'server_boot',

distinctId: 'd0bfea5d-0865-477d-bd01-2fd3a4f18feb',

properties: { runtime: 'desktop' }

}

Hot loading of AnythingLLMOllama - LLM_PROVIDER is anythingllm_ollama.

[NativeEmbedder] Initialized

[CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.

[EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.

[production] AnythingLLM Standalone Backend listening on port 3001

[BackgroundWorkerService] Feature is not enabled and will not be started.

[OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager.

[OllamaProcessManager] [windows] Ollama subprocess running. Port 11434. PID 39160.

OllamaAPI offline - retrying. 1/3

[NativeEmbedder] Initialized

Error: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135

at createOllamaStream ***@***.***\community\dist\utils\ollama.cjs:26:21)

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

at async createOllamaChatStream ***@***.***\community\dist\utils\ollama.cjs:61:5)

at async ChatOllama._streamResponseChunks ***@***.***\community\dist\chat_models\ollama.cjs:399:30)

at async ChatOllama._streamIterator ***@***.******@***.***\core\dist\language_models\chat_models.cjs:82:34)

at async ChatOllama.transform ***@***.******@***.***\core\dist\runnables\base.cjs:384:9)

at async wrapInputForTracing ***@***.***\core\dist\runnables\base.cjs:258:30)

at async pipeGeneratorWithSetup ***@***.***\core\dist\utils\stream.cjs:230:19)

at async StringOutputParser._transformStreamWithConfig ***@***.***\core\dist\runnables\base.cjs:279:26)

at async StringOutputParser.transform ***@***.***\core\dist\output_parsers\transform.cjs:36:9) {

response: Response {

[Symbol(realm)]: null,

[Symbol(state)]: {

  aborted: false,

  rangeRequested: false,

  timingAllowPassed: true,

  requestIncludesCredentials: true,

  type: 'default',

  status: 500,

  timingInfo: [Object],

  cacheState: '',

  statusText: 'Internal Server Error',

  headersList: [HeadersList],

  urlList: [Array],

  body: [Object]

},

[Symbol(headers)]: HeadersList {

  cookies: null,

  [Symbol(headers map)]: [Map],

  [Symbol(headers map sorted)]: null

}

}

}

From: Timothy Carambat @.>
Sent: Monday, July 1, 2024 10:36 AM
To: Mintplex-Labs/anything-llm @.>
Cc: RockinRoddieAi @.>; Comment @.>
Subject: Re: [Mintplex-Labs/anything-llm] [BUG]: Not working on windows 11. Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 (Issue #1795)

This error is obviously tied back to ollama, I have a feeling it is device related. Please run the app in debug mode and on boot and when sending a chat there should be logs that describe the whole ollama runtime

https://docs.useanything.com/debug#anythingllm-debug-mode-on-windows

I will need those to help. I would prefer to not go back to the previous Ollama version as it is slower and the newer version has improved greatly.

Other details:

  • Do you have GPU?
  • CUDA installed? If so, which version
  • CPU specs (does it support AVX?)

—
Reply to this email directly, view it on GitHub https://github.com/Mintplex-Labs/anything-llm/issues/1795#issuecomment-2200594885 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BJRVGWJVTJCQJDPPCUC3IY3ZKGAPVAVCNFSM6AAAAABKENEBJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGU4TIOBYGU .
You are receiving this because you commented. https://github.com/notifications/beacon/BJRVGWJBFAYPBUUZXBVFFW3ZKGAPVA5CNFSM6AAAAABKENEBJSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDFJU4K.gif Message ID: @.*** @.***> >

@RockinRoddieAi commented on GitHub (Jul 1, 2024): Hi I followed the debugging mode instructions. Log file details are below. I have this issue on two issues: Workstation specs: GPU = Yes NVIDIA GeForce RTX 3090 CPU = 12th Gen Intel Core i9-1290 3.19 GHz and yes it supports AVX Laptop specs: GPU = Yes NVIDIA GeForce RTX 3050 CPU = 12th Gen Intel Core i-12700H 2.30 GHz and yes it supports AVX --- C:\Users\r0ss\AppData\Local\Programs\anythingllm-desktop> [Preferences] preference config stored at C:\Users\r0ss\AppData\Roaming\anythingllm-desktop\config.json Prisma schema loaded from prisma\schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:C:/Users/r0ss/AppData/Roaming/anythingllm-desktop/storage/anythingllm.db" Already in sync, no schema change or pending migration was found. Γ£ö Generated Prisma Client (v5.3.1) to .***@***.***\client in 342ms Prisma schema loaded from prisma\schema.prisma Γ£ö Generated Prisma Client (v5.3.1) to .***@***.***\client in 309ms Start using Prisma Client in Node.js (See: https://pris.ly/d/client) ``` import { PrismaClient } from ***@***.***/client' const prisma = new PrismaClient() ``` or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate) ``` import { PrismaClient } from ***@***.***/client/edge' const prisma = new PrismaClient() ``` See other ways of importing Prisma Client: http://pris.ly/d/importing-client [OllamaProcessManager] Ollama will bind on port 11434 when booted. [Preferences] Will load window with last know bounds. Collector hot directory and tmp storage wiped! [production] AnythingLLM Standalone Document processor listening on port 8888 [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. prisma:info Starting a sqlite pool with 33 connections. [TELEMETRY SENT] { event: 'server_boot', distinctId: 'd0bfea5d-0865-477d-bd01-2fd3a4f18feb', properties: { runtime: 'desktop' } } Hot loading of AnythingLLMOllama - LLM_PROVIDER is anythingllm_ollama. [NativeEmbedder] Initialized [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [production] AnythingLLM Standalone Backend listening on port 3001 [BackgroundWorkerService] Feature is not enabled and will not be started. [OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager. [OllamaProcessManager] [windows] Ollama subprocess running. Port 11434. PID 39160. OllamaAPI offline - retrying. 1/3 [NativeEmbedder] Initialized Error: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 at createOllamaStream ***@***.***\community\dist\utils\ollama.cjs:26:21) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async createOllamaChatStream ***@***.***\community\dist\utils\ollama.cjs:61:5) at async ChatOllama._streamResponseChunks ***@***.***\community\dist\chat_models\ollama.cjs:399:30) at async ChatOllama._streamIterator ***@***.******@***.***\core\dist\language_models\chat_models.cjs:82:34) at async ChatOllama.transform ***@***.******@***.***\core\dist\runnables\base.cjs:384:9) at async wrapInputForTracing ***@***.***\core\dist\runnables\base.cjs:258:30) at async pipeGeneratorWithSetup ***@***.***\core\dist\utils\stream.cjs:230:19) at async StringOutputParser._transformStreamWithConfig ***@***.***\core\dist\runnables\base.cjs:279:26) at async StringOutputParser.transform ***@***.***\core\dist\output_parsers\transform.cjs:36:9) { response: Response { [Symbol(realm)]: null, [Symbol(state)]: { aborted: false, rangeRequested: false, timingAllowPassed: true, requestIncludesCredentials: true, type: 'default', status: 500, timingInfo: [Object], cacheState: '', statusText: 'Internal Server Error', headersList: [HeadersList], urlList: [Array], body: [Object] }, [Symbol(headers)]: HeadersList { cookies: null, [Symbol(headers map)]: [Map], [Symbol(headers map sorted)]: null } } } From: Timothy Carambat ***@***.***> Sent: Monday, July 1, 2024 10:36 AM To: Mintplex-Labs/anything-llm ***@***.***> Cc: RockinRoddieAi ***@***.***>; Comment ***@***.***> Subject: Re: [Mintplex-Labs/anything-llm] [BUG]: Not working on windows 11. Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 (Issue #1795) This error is obviously tied back to ollama, I have a feeling it is device related. Please run the app in debug mode and on boot and when sending a chat there should be logs that describe the whole ollama runtime https://docs.useanything.com/debug#anythingllm-debug-mode-on-windows I will need those to help. I would prefer to not go back to the previous Ollama version as it is slower and the newer version has improved greatly. Other details: * Do you have GPU? * CUDA installed? If so, which version * CPU specs (does it support AVX?) — Reply to this email directly, view it on GitHub <https://github.com/Mintplex-Labs/anything-llm/issues/1795#issuecomment-2200594885> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJRVGWJVTJCQJDPPCUC3IY3ZKGAPVAVCNFSM6AAAAABKENEBJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGU4TIOBYGU> . You are receiving this because you commented. <https://github.com/notifications/beacon/BJRVGWJBFAYPBUUZXBVFFW3ZKGAPVA5CNFSM6AAAAABKENEBJSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDFJU4K.gif> Message ID: ***@***.*** ***@***.***> >
yindo commented 2026-02-22 18:23:31 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 1, 2024):

We identified the root cause of this issue:

  • On windows systems which have a discoverable CUDA capable device GPU
  • Do not have Ollama already installed on the client system
  • Attempt to run the built in Ollama client
    -> Client fails as ollama does not failover on CUDA library missing to CPU and aborts the process.

The fix was to include missing binaries for CUDA support. Currently, these will be pre-bundled with AnythingLLM windows, future updates may move them to a post-install process.

As such, downloading the latest version of AnythingLLM 1.5.8 as of July 1, 2024 ~11:20AM PST will download this patched version.

Installation may take longer than expected since we are going to unpack the supporting libraries now, but it will result in a working and GPU-enabled built-in Ollama experience.

@timothycarambat commented on GitHub (Jul 1, 2024): We identified the root cause of this issue: - On windows systems which have a discoverable CUDA capable device GPU - Do _not_ have Ollama already installed on the client system - Attempt to run the built in Ollama client -> Client fails as ollama does not failover on CUDA library missing to CPU and aborts the process. The fix was to include missing binaries for CUDA support. Currently, these will be pre-bundled with AnythingLLM windows, future updates may move them to a post-install process. As such, downloading the latest version of[ AnythingLLM 1.5.8 ](https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/AnythingLLMDesktop.exe)as of July 1, 2024 ~11:20AM PST will download this patched version. Installation may take longer than expected since we are going to unpack the supporting libraries now, but it will result in a working and GPU-enabled built-in Ollama experience.
yindo commented 2026-02-22 18:23:32 -05:00
Author
Owner
Copy Link
Copy Source

@RockinRoddieAi commented on GitHub (Jul 1, 2024):

Thanks, that did the trick.

Super impressed with this support thread.

Keep up all the great work. I am thoroughly enjoying this app.

From: Timothy Carambat @.>
Sent: Monday, July 1, 2024 12:30 PM
To: Mintplex-Labs/anything-llm @.>
Cc: RockinRoddieAi @.>; Comment @.>
Subject: Re: [Mintplex-Labs/anything-llm] [BUG]: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 | Windows (Issue #1795)

We identified the root cause of this issue:

  • On windows systems which have a discoverable CUDA capable device GPU
  • Do not have Ollama already installed on the client system
  • Attempt to run the built in Ollama client
    -> Client fails as ollama does not failover on CUDA library missing to CPU and aborts the process.

The fix was to include missing binaries for CUDA support. Currently, these will be pre-bundled with AnythingLLM windows, future updates may move them to a post-install process.

As such, downloading the latest version of AnythingLLM 1.5.8 https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/AnythingLLMDesktop.exe as of July 1, 2024 ~11:20AM PST will download this patched version.

Installation may take longer than expected since we are going to unpack the supporting libraries now, but it will result in a working and GPU-enabled built-in Ollama experience.

—
Reply to this email directly, view it on GitHub https://github.com/Mintplex-Labs/anything-llm/issues/1795#issuecomment-2200769963 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BJRVGWPJKO35AUHUCABKJBTZKGNZ5AVCNFSM6AAAAABKENEBJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQG43DSOJWGM .
You are receiving this because you commented. https://github.com/notifications/beacon/BJRVGWK2C7ZQ735HGMLT2DDZKGNZ5A5CNFSM6AAAAABKENEBJSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDFUK2W.gif Message ID: @.*** @.***> >

@RockinRoddieAi commented on GitHub (Jul 1, 2024): Thanks, that did the trick. Super impressed with this support thread. Keep up all the great work. I am thoroughly enjoying this app. From: Timothy Carambat ***@***.***> Sent: Monday, July 1, 2024 12:30 PM To: Mintplex-Labs/anything-llm ***@***.***> Cc: RockinRoddieAi ***@***.***>; Comment ***@***.***> Subject: Re: [Mintplex-Labs/anything-llm] [BUG]: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 | Windows (Issue #1795) We identified the root cause of this issue: * On windows systems which have a discoverable CUDA capable device GPU * Do not have Ollama already installed on the client system * Attempt to run the built in Ollama client -> Client fails as ollama does not failover on CUDA library missing to CPU and aborts the process. The fix was to include missing binaries for CUDA support. Currently, these will be pre-bundled with AnythingLLM windows, future updates may move them to a post-install process. As such, downloading the latest version of AnythingLLM 1.5.8 <https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/AnythingLLMDesktop.exe> as of July 1, 2024 ~11:20AM PST will download this patched version. Installation may take longer than expected since we are going to unpack the supporting libraries now, but it will result in a working and GPU-enabled built-in Ollama experience. — Reply to this email directly, view it on GitHub <https://github.com/Mintplex-Labs/anything-llm/issues/1795#issuecomment-2200769963> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJRVGWPJKO35AUHUCABKJBTZKGNZ5AVCNFSM6AAAAABKENEBJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQG43DSOJWGM> . You are receiving this because you commented. <https://github.com/notifications/beacon/BJRVGWK2C7ZQ735HGMLT2DDZKGNZ5A5CNFSM6AAAAABKENEBJSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDFUK2W.gif> Message ID: ***@***.*** ***@***.***> >
yindo commented 2026-02-22 18:23:32 -05:00
Author
Owner
Copy Link
Copy Source

@drgamedev commented on GitHub (Jul 22, 2025):

I am having the same issue. I've set up AnythingLLM. Then restarted. The same error is occurring again. Could someone please provide the precise steps to resolve it? Thanks.

@drgamedev commented on GitHub (Jul 22, 2025): I am having the same issue. I've set up AnythingLLM. Then restarted. The same error is occurring again. Could someone please provide the precise steps to resolve it? Thanks.
yindo changed title from [BUG]: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 | Windows to [GH-ISSUE #1795] [BUG]: Ollama call failed with status code 500: llama runner process has terminated: exit status 0xc0000135 | Windows 2026-06-05 14:39:21 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Desktop OS: Windows core-team-only possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1173
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?