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 #2971] [BUG]: Updating the workspace while a thread is loading breaks AnythingLLM #1894

New Issue
Closed
opened 2026-02-22 18:27:06 -05:00 by yindo · 5 comments
yindo commented 2026-02-22 18:27:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @DangerousBerries on GitHub (Jan 14, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2971

How are you running AnythingLLM?

Docker (local)

What happened?

I get these errors:

Error:
Invalid prisma.workspaces.update() invocation:
Error in connector: Error querying the database: cannot start a transaction within a transaction

AnythingLLM will get stuck in a loading icon and nothing will work.

Also Timothy I replied to you in closed issues a couple of times (like in Display Backfilled Context) and it seems like you didn't see them, do you not get notified for replies after issues are closed?

Are there known steps to reproduce?

While loading a thread in the background change the Max Context Snippets number and click "Update workplace".

Originally created by @DangerousBerries on GitHub (Jan 14, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2971 ### How are you running AnythingLLM? Docker (local) ### What happened? I get these errors: Error: Invalid `prisma.workspaces.update()` invocation: Error in connector: Error querying the database: cannot start a transaction within a transaction AnythingLLM will get stuck in a loading icon and nothing will work. Also Timothy I replied to you in closed issues a couple of times (like in Display Backfilled Context) and it seems like you didn't see them, do you not get notified for replies after issues are closed? ### Are there known steps to reproduce? While loading a thread in the background change the Max Context Snippets number and click "Update workplace".
yindo closed this issue 2026-02-22 18:27:06 -05:00
yindo commented 2026-02-22 18:27:07 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 14, 2025):

How you would arrive in this state is quite odd, is your docker instance overloaded or on a small machine with low resources? Being able to run a transaction is trivial to process so getting to this state will be very difficult to replicate as we already have the guards to prevent updating a null reference.

If there is a race condition from doing an update when a thread is loading (under what state - creation, deletion, etc?) then unless this becomes experiential for more users it will be wontfix for now. The background DB is SQLite and is can handle concurrent reads, but not writes since its a file-based system. However,it will do a write-ahead-log to prevent these exact kinds of errors. So how this happened is odd, but also something I cannot even try to replicate atm.

@timothycarambat commented on GitHub (Jan 14, 2025): How you would arrive in this state is quite odd, is your docker instance overloaded or on a small machine with low resources? Being able to run a transaction is trivial to process so getting to this state will be very difficult to replicate as we already have the guards to prevent updating a null reference. If there is a race condition from doing an update when a thread is loading (under what state - creation, deletion, etc?) then unless this becomes experiential for more users it will be wontfix for now. The background DB is SQLite and is can handle concurrent reads, but not writes since its a file-based system. However,it will do a write-ahead-log to prevent these exact kinds of errors. So how this happened is odd, but also something I cannot even try to replicate atm.
yindo commented 2026-02-22 18:27:07 -05:00
Author
Owner
Copy Link
Copy Source

@DangerousBerries commented on GitHub (Jan 14, 2025):

How you would arrive in this state is quite odd, is your docker instance overloaded or on a small machine with low resources? Being able to run a transaction is trivial to process so getting to this state will be very difficult to replicate as we already have the guards to prevent updating a null reference.

If there is a race condition from doing an update when a thread is loading (under what state - creation, deletion, etc?) then unless this becomes experiential for more users it will be wontfix for now. The background DB is SQLite and is can handle concurrent reads, but not writes since its a file-based system. However,it will do a write-ahead-log to prevent these exact kinds of errors. So how this happened is odd, but also something I cannot even try to replicate atm.

Oh I just have a thread that's like hundreds of thousands of characters so it takes time to load lol, but that's fine that you won't fix it I'll avoid doing that.

@DangerousBerries commented on GitHub (Jan 14, 2025): > How you would arrive in this state is quite odd, is your docker instance overloaded or on a small machine with low resources? Being able to run a transaction is trivial to process so getting to this state will be very difficult to replicate as we already have the guards to prevent updating a null reference. > > If there is a race condition from doing an update when a thread is loading (under what state - creation, deletion, etc?) then unless this becomes experiential for more users it will be wontfix for now. The background DB is SQLite and is can handle concurrent reads, but not writes since its a file-based system. However,it will do a write-ahead-log to prevent these exact kinds of errors. So how this happened is odd, but also something I cannot even try to replicate atm. Oh I just have a thread that's like hundreds of thousands of characters so it takes time to load lol, but that's fine that you won't fix it I'll avoid doing that.
yindo commented 2026-02-22 18:27:07 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 14, 2025):

Oh I just have a thread that's like hundreds of thousands of characters so it takes time to load lol, but that's fine that you won't fix it I'll avoid doing that.

The name or the chat??

@timothycarambat commented on GitHub (Jan 14, 2025): > Oh I just have a thread that's like hundreds of thousands of characters so it takes time to load lol, but that's fine that you won't fix it I'll avoid doing that. The name or the chat??
yindo commented 2026-02-22 18:27:07 -05:00
Author
Owner
Copy Link
Copy Source

@DangerousBerries commented on GitHub (Jan 14, 2025):

Oh I just have a thread that's like hundreds of thousands of characters so it takes time to load lol, but that's fine that you won't fix it I'll avoid doing that.

The name or the chat??

the chat lol

@DangerousBerries commented on GitHub (Jan 14, 2025): > > Oh I just have a thread that's like hundreds of thousands of characters so it takes time to load lol, but that's fine that you won't fix it I'll avoid doing that. > > The name or the chat?? the chat lol
yindo commented 2026-02-22 18:27:07 -05:00
Author
Owner
Copy Link
Copy Source

@DangerousBerries commented on GitHub (Mar 26, 2025):

I try to avoid this but eventually I stumble and get it again. I got a slightly different line though, maybe that could help:
Error in connector: Error creating a database connection. (Timed out during query execution.)

@DangerousBerries commented on GitHub (Mar 26, 2025): I try to avoid this but eventually I stumble and get it again. I got a slightly different line though, maybe that could help: Error in connector: Error creating a database connection. (Timed out during query execution.)
yindo changed title from [BUG]: Updating the workspace while a thread is loading breaks AnythingLLM to [GH-ISSUE #2971] [BUG]: Updating the workspace while a thread is loading breaks AnythingLLM 2026-06-05 14:43:19 -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
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#1894
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?