nextcloud / nextcloud/server

[Bug]: Uploading a Python venv folder generates an error message

Open
#45,168 1 comment 0 reactions 0 assignees View on GitHub

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: ⚠️
Bug description

Uploading a venv Folder generates Error Messages, in both, client and Browser.
attached Screenshots:

  1. Browser
    Screenshot 2024-05-03 100519
  2. Client
    Client_venv
Steps to reproduce
  1. Generate a virtual environment in Python
  2. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.