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

[GH-ISSUE #1284] [BUG]: Workspace setting fields not showing current configuration #806

New Issue
Closed
opened 2026-02-22 18:21:28 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:21:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @RahSwe on GitHub (May 5, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1284

Originally assigned to: @shatfield4 on GitHub.

How are you running AnythingLLM?

Docker (remote machine)

What happened?

When updating a parameter (such as system prompt), then switching to another tab in the workspace settings to change a parameter, then switching back to the previous tab, the old parameter information in that tab is shown.

Also, when switching between work spaces having changed a parameter in the previous workspace (such as preset chat messages), the current work space sometimes incorrectly show the settings of the previous workspace.

Are there known steps to reproduce?

See above

Originally created by @RahSwe on GitHub (May 5, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1284 Originally assigned to: @shatfield4 on GitHub. ### How are you running AnythingLLM? Docker (remote machine) ### What happened? When updating a parameter (such as system prompt), then switching to another tab in the workspace settings to change a parameter, then switching back to the previous tab, the old parameter information in that tab is shown. Also, when switching between work spaces having changed a parameter in the previous workspace (such as preset chat messages), the current work space sometimes incorrectly show the settings of the previous workspace. ### Are there known steps to reproduce? See above
yindo added the possible buginvestigating labels 2026-02-22 18:21:28 -05:00
yindo closed this issue 2026-02-22 18:21:28 -05:00
yindo commented 2026-02-22 18:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@Propheticus commented on GitHub (May 5, 2024):

It indeed does this when you don't save your changes using the update workspace button.
A bit clumsy UX-wise.

@Propheticus commented on GitHub (May 5, 2024): It indeed does this when you don't save your changes using the `update workspace` button. A bit clumsy UX-wise.
yindo commented 2026-02-22 18:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 5, 2024):

Then save the changes

@timothycarambat commented on GitHub (May 5, 2024): Then save the changes
yindo commented 2026-02-22 18:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@Propheticus commented on GitHub (May 10, 2024):

@timothycarambat I think I noticed what @RahSwe meant by their report. (tested on latest docker image)
When you change settings + save/update the workspace (!) and then navigate to other tabs of the settings and back to the tab you made changes in, the old settings are shown. When you close the settings and open them you see the newly saved settings, so they were successfully saved.
Feels like a cache (invalidation) thingy / local variables not being updated from their initialised value.

@Propheticus commented on GitHub (May 10, 2024): @timothycarambat I think I noticed what @RahSwe meant by their report. (tested on latest docker image) When you change settings + save/update the workspace (!) and then navigate to other tabs of the settings and back to the tab you made changes in, the old settings are shown. When you close the settings and open them you see the newly saved settings, so they were successfully saved. Feels like a cache (invalidation) thingy / local variables not being updated from their initialised value.
yindo commented 2026-02-22 18:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@RahSwe commented on GitHub (May 10, 2024):

Yes, that is what I tried to describe, sorry if I was being unclear.

@RahSwe commented on GitHub (May 10, 2024): Yes, that is what I tried to describe, sorry if I was being unclear.
yindo commented 2026-02-22 18:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@Propheticus commented on GitHub (May 10, 2024):

Yes, that is what I tried to describe, sorry if I was being unclear.

Reading it back now, you pretty much described it literally. Maybe just me/us not following 🦆

@Propheticus commented on GitHub (May 10, 2024): > Yes, that is what I tried to describe, sorry if I was being unclear. Reading it back now, you pretty much described it literally. Maybe just me/us not following 🦆
yindo commented 2026-02-22 18:21:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 10, 2024):

Ah, okay that went totally over my head. Sorry about that

@timothycarambat commented on GitHub (May 10, 2024): Ah, okay that went totally over my head. Sorry about that
yindo changed title from [BUG]: Workspace setting fields not showing current configuration to [GH-ISSUE #1284] [BUG]: Workspace setting fields not showing current configuration 2026-06-05 14:37:18 -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 investigating 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#806
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?