Data

Tools

Indexes

Applications

Experiments

Open Source Science

https://github.com/codesetuptest/django-django-11283

SWE-bench instance: django__django-11283

https://github.com/codesetuptest/django-django-11283

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.3%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

SWE-bench instance: django__django-11283

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
Created about 1 year ago · Last pushed about 1 year ago
Metadata Files
Readme Contributing License Authors

README.md

SWE-bench Instance: django__django-11283

Repository: django/django Base Commit: 08a4ee06510ae45562c228eefbdcaac84bd38c7a

Problem Statement

Migration auth.0011updateproxy_permissions fails for models recreated as a proxy. Description

    (last modified by Mariusz Felisiak)

I am trying to update my project to Django 2.2. When I launch python manage.py migrate, I get this error message when migration auth.0011updateproxypermissions is applying (full stacktrace is available ​here): django.db.utils.IntegrityError: duplicate key value violates unique constraint "idx18141authpermissioncontenttypeid01ab375auniq" DETAIL: Key (co.ntenttypeid, codename)=(12, addagency) already exists. It looks like the migration is trying to re-create already existing entries in the authpermission table. At first I though it cloud because we recently renamed a model. But after digging and deleting the entries associated with the renamed model from our database in the authpermission table, the problem still occurs with other proxy models. I tried to update directly from 2.0.13 and 2.1.8. The issues appeared each time. I also deleted my venv and recreated it without an effect. I searched for a ticket about this on the bug tracker but found nothing. I also posted this on ​django-users and was asked to report this here.

Repository Contents

This repository contains the actual source code from the original repository at commit 08a4ee06510ae45562c228eefbdcaac84bd38c7a. 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

GitHub Events

Total
  • Create event: 2
Last Year
  • Create event: 2

Dependencies

Dockerfile docker
  • sweb.env.py.x86_64.2baaea72acc974f6c02079 latest build
package.json npm
  • eslint ^0.22.1 development
  • grunt ^1.0.1 development
  • grunt-cli ^1.2.0 development
  • grunt-contrib-qunit ^1.2.0 development
setup.py pypi
  • pytz *
  • sqlparse *
tests/admin_scripts/custom_templates/project_template/additional_dir/requirements.txt pypi
tests/requirements/mysql.txt pypi
  • mysqlclient >=1.3.13 test
tests/requirements/oracle.txt pypi
  • cx_oracle >=6.0 test
tests/requirements/postgres.txt pypi
  • psycopg2-binary >=2.5.4 test
tests/requirements/py3.txt pypi
  • 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