[Bug]: Uploading a Python venv folder generates an error message
Open
Nobody has claimed this yet.
0. Needs triage
27-feedback
bug
feature: database
feature: filesystem
hotspot: filename handling
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Uploading a venv Folder generates Error Messages, in both, client and Browser.
attached Screenshots:
- Browser
- Client
Steps to reproduce
- Generate a virtual environment in Python
- Upload the venv - folder to the cloud, either in Browser or in the Client
Expected behavior
No Error Message
Installation method
None
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies no source file, entry point, or test. First reproduce uploading a Python venv through both the browser and client, capture the exact error and relevant Nextcloud logs, and then trace the server-side upload handling. Done means venv uploads complete without error in both paths, with regression coverage added for the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100