github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 06:03:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #16085] feat: Handling folder nesting error #17778

New Issue
Closed
opened 2026-04-19 23:39:44 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-19 23:39:44 -05:00
Owner
Copy Link

Originally created by @Sirithi on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16085

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

When uploading/syncing a folder from my device the upload suddenly halts and gives a bunch of errors. extracted content is not available for this file. Please ensure that the file is processed before proceeding. When then manually uploading the file it crashed at, the file is uploaded just fine. We believe this may be caused by the levels of nesting in the folder (5 levels deep).

Desired Solution you'd like

A better error handling when this happens as the issue is clearly not with the file but somewhere else (presumably nested folders).

Alternatives Considered

Let nested files be uploaded for deeper nesting or clearly state there can only be x many levels in the folder you're uploading

Additional Context

No response

Originally created by @Sirithi on GitHub (Jul 28, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16085 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description When uploading/syncing a folder from my device the upload suddenly halts and gives a bunch of errors. extracted content is not available for this file. Please ensure that the file is processed before proceeding. When then manually uploading the file it crashed at, the file is uploaded just fine. We believe this may be caused by the levels of nesting in the folder (5 levels deep). ### Desired Solution you'd like A better error handling when this happens as the issue is clearly not with the file but somewhere else (presumably nested folders). ### Alternatives Considered Let nested files be uploaded for deeper nesting or clearly state there can only be x many levels in the folder you're uploading ### Additional Context _No response_
GiteaMirror commented 2026-04-19 23:39:47 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Jul 28, 2025):

A well presented bug report goes a long way.

<!-- gh-comment-id:3126047827 --> @silentoplayz commented on GitHub (Jul 28, 2025): A well presented bug report goes a long way.
GiteaMirror commented 2026-04-19 23:39:50 -05:00
Author
Owner
Copy Link

@Sirithi commented on GitHub (Jul 28, 2025):

Don't think it's a bug though. I believe the behavior is not documented very clearly

<!-- gh-comment-id:3126140364 --> @Sirithi commented on GitHub (Jul 28, 2025): Don't think it's a bug though. I believe the behavior is not documented very clearly
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#17778
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?