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

[GH-ISSUE #374] collected URL article files cannot be moved into a workspace #214

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

Originally created by @santini-cyber on GitHub (Nov 14, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/374

Originally assigned to: @shatfield4 on GitHub.

Observed Behavior:
After running the collector and successfully capturing the content from a single URL website, the resulting article-*.json file cannot be moved into the workspace via the File Manager UI in order to be embedded.
Error/Log Data:
I am not seeing any errors in the docker logs. The json structure in the article file has been verified via json lint. I also reviewed the network trace in the developer tools for the Firefox and Chrome browsers and am not seeing any errors or warnings that might explain the observed behavior.
Repeatable:
Recreated the issue with Chrome, Firefox and Edge. Also recreated using several different URLs. And three successive daily builds.

Originally created by @santini-cyber on GitHub (Nov 14, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/374 Originally assigned to: @shatfield4 on GitHub. Observed Behavior: After running the collector and successfully capturing the content from a single URL website, the resulting article-*.json file cannot be moved into the workspace via the File Manager UI in order to be embedded. Error/Log Data: I am not seeing any errors in the docker logs. The json structure in the article file has been verified via json lint. I also reviewed the network trace in the developer tools for the Firefox and Chrome browsers and am not seeing any errors or warnings that might explain the observed behavior. Repeatable: Recreated the issue with Chrome, Firefox and Edge. Also recreated using several different URLs. And three successive daily builds.
yindo added the possible bug label 2026-02-22 18:18:23 -05:00
yindo closed this issue 2026-02-22 18:18:23 -05:00
yindo commented 2026-02-22 18:18:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 14, 2023):

Pull in latest and re-run the collector and the schema will work. This is only an issue if you are connected to a LanceDB vectordb, any other provider would not have this issue. Thanks!

c5dc68633b

@timothycarambat commented on GitHub (Nov 14, 2023): Pull in latest and re-run the collector and the schema will work. This is only an issue if you are connected to a LanceDB vectordb, any other provider would not have this issue. Thanks! c5dc68633b5b63ecdbe7a7ab5ba004e1eb9c0c29
yindo commented 2026-02-22 18:18:23 -05:00
Author
Owner
Copy Link
Copy Source

@santini-cyber commented on GitHub (Nov 15, 2023):

Tested collector this morning with new code. URLs captured as json files and can be moved in to the workspace + embedded. Getting the following error when executing the collector:
print(f"Your estimated cost to embed this data using OpenAI's text-embedding-ada-002 model at $0.0004 / 1K tokens will cost {ada_v2_cost(tokenCount)} using {tokenCount} tokens.")
NameError: name 'tokenCount' is not defined

@santini-cyber commented on GitHub (Nov 15, 2023): Tested collector this morning with new code. URLs captured as json files and can be moved in to the workspace + embedded. Getting the following error when executing the collector: print(f"Your estimated cost to embed this data using OpenAI's text-embedding-ada-002 model at $0.0004 / 1K tokens will cost {ada_v2_cost(tokenCount)} using {tokenCount} tokens.") NameError: name 'tokenCount' is not defined
yindo commented 2026-02-22 18:18:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 16, 2023):

Fixed 1e3d82e18485b60173362dd5c7c248abe0581f36

@timothycarambat commented on GitHub (Nov 16, 2023): Fixed `1e3d82e18485b60173362dd5c7c248abe0581f36`
yindo changed title from collected URL article files cannot be moved into a workspace to [GH-ISSUE #374] collected URL article files cannot be moved into a workspace 2026-06-05 14:34:06 -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 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#214
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?