Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
4 of 8 tasks
ZID-TU-Graz opened this issue May 3, 2024 · 1 comment
Open
4 of 8 tasks
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 27-feedback bug

Comments

@ZID-TU-Graz
Copy link

⚠️ 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

@ZID-TU-Graz ZID-TU-Graz added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels May 3, 2024
@joshtrichards
Copy link
Member

venv isn't really meant to be synced across multiple computers AFAIK.. It's basically a throw away environment. I think it also uses symlinks so those could create some problems too with syncing. Might want to exclude it from sync and just sync requirements.txt or whatever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 27-feedback bug
Projects
None yet
Development

No branches or pull requests

3 participants