bytedance / bytedance/Protenix
permission error when setting up in read only virtual enviroment and no internet issue
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 310
- PR merge metrics
- No merged PRs in 30d
Description
I have installed protenix in a python virtual environment that is shared by a group and is read only so can be managed by the admin. But when users use the virt env it seems protenix needs to write inside it which is odd? ie
`PermissionError: [Errno 13] Permission denied: '/xxxx/software/protenix1.0.8_b_venv/lib/python3.11/site-packages/protenix/model/layer_norm/lock'`
How can this be fixed so the lock is written to say the users scratch area, can that be done using some environment variable before running protenix?
Contributor guide
Research direction
Reproduce the PermissionError in a read-only virtual environment without internet access, using the reported path under protenix/model/layer_norm/lock. Trace what creates or writes that lock and check whether the package exposes an environment setting for relocating it. Done means users can run Protenix without writing into site-packages, with the lock stored in a writable user or scratch location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100