https://github.com/codesetuptest/django-django-10914
SWE-bench instance: django__django-10914
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (8.1%) to scientific vocabulary
Repository
SWE-bench instance: django__django-10914
Basic Info
- Host: GitHub
- Owner: CodeSetupTest
- License: bsd-3-clause
- Language: Python
- Default Branch: main
- Size: 0 Bytes
Statistics
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
SWE-bench Instance: django__django-10914
Repository: django/django Base Commit: e7fd69d051eaa67cb17f172a39b57253e9cb831a
Problem Statement
Set default FILEUPLOADPERMISSION to 0o644. Description
Hello, As far as I can see, the File Uploads documentation page does not mention any permission issues. What I would like to see is a warning that in absence of explicitly configured FILEUPLOADPERMISSIONS, the permissions for a file uploaded to FileSystemStorage might not be consistent depending on whether a MemoryUploadedFile or a TemporaryUploadedFile was used for temporary storage of the uploaded data (which, with the default FILEUPLOADHANDLERS, in turn depends on the uploaded data size). The tempfile.NamedTemporaryFile + os.rename sequence causes the resulting file permissions to be 0o0600 on some systems (I experience it here on CentOS 7.4.1708 and Python 3.6.5). In all probability, the implementation of Python's built-in tempfile module explicitly sets such permissions for temporary files due to security considerations. I found mentions of this issue on GitHub, but did not manage to find any existing bug report in Django's bug tracker.
Repository Contents
This repository contains the actual source code from the original repository at commit e7fd69d051eaa67cb17f172a39b57253e9cb831a. The code is ready for development and testing.
Docker Environment
A Dockerfile is provided to set up the proper environment for this instance:
bash
docker build -t swebench-instance .
docker run -it swebench-instance /bin/bash
Owner
- Name: CodeSetupTest
- Login: CodeSetupTest
- Kind: organization
- Repositories: 1
- Profile: https://github.com/CodeSetupTest
GitHub Events
Total
- Create event: 1
Last Year
- Create event: 1
Dependencies
- sweb.env.py.x86_64.2baaea72acc974f6c02079 latest build
- eslint ^0.22.1 development
- grunt ^1.0.1 development
- grunt-cli ^1.2.0 development
- grunt-contrib-qunit ^1.2.0 development
- pytz *
- sqlparse *
- mysqlclient >=1.3.13 test
- cx_oracle >=6.0 test
- psycopg2-binary >=2.5.4 test
- Pillow * test
- PyYAML * test
- argon2-cffi >=16.1.0 test
- bcrypt * test
- docutils * test
- geoip2 * test
- jinja2 >=2.9.2 test
- numpy * test
- pylibmc * test
- python-memcached >=1.59 test
- pytz * test
- pywatchman * test
- selenium * test
- sqlparse * test
- tblib * test