← 输入框|github.com|刷新
Skip to content

Adding new Journey returns internal server error #219

Open

Description

@jarifibrahim

Steps to reproduce

  1. Pull latest pre-dev branch
  2. Run python manage.py migrate
  3. Login to admin console and try to add a new Journey.

Reason for failure - Server returns IntegrityError - NOT NULL constraint failed: main_journey.description

Explanation -
Take a look at 0002_journey.py file. The file represents a model which contains description field, while the actual model has no description field.

To fix the issue - Run python manage.py makemigrations and commit the new migration file.

Activity

  1. tapaswenipathak commented on Dec 29, 2017

    @tapaswenipathak
    Member

    description field needs to be removed from here 👍

    But
    it seems to be handled by heroku admin console and on the local too 👇, I tested this before and now. 🤔

    screen shot 2017-12-29 at 7 00 06 am

    screen shot 2017-12-29 at 7 05 43 am

    Can you share the steps to reproduce? I tried w/ both DEBUG set to True and False.

  2. jarifibrahim commented on Jan 5, 2018

    @jarifibrahim
    MemberAuthor

    @tapasweni-pathak I can confirm that it isn't working.
    Try the following steps

    1. delete the db.sqlite3 file
    2. run python manage.py migrate
    3. Try to add a journey via admin console.
  3. tapaswenipathak commented on Jan 6, 2018

    @tapaswenipathak
    Member

    @jarifibrahim I did it again and it is working for me,

    Adding screenshots so keep track and if anyone sees anything visible
    screen shot 2018-01-06 at 9 13 04 pm
    screen shot 2018-01-06 at 9 12 19 pm

  4. jarifibrahim commented on Jan 11, 2018

    @jarifibrahim
    MemberAuthor

    @tapasweni-pathak

    (venv) ➜  oshc git:(predev) python manage.py migrate
    Operations to perform:
      Apply all migrations: account, admin, auth, contenttypes, main, sessions, sites, socialaccount
    Running migrations:
      Applying contenttypes.0001_initial... OK
      Applying auth.0001_initial... OK
      Applying account.0001_initial... OK
      Applying account.0002_email_max_length... OK
      Applying admin.0001_initial... OK
      Applying admin.0002_logentry_remove_auto_add... OK
      Applying contenttypes.0002_remove_content_type_name... OK
      Applying auth.0002_alter_permission_name_max_length... OK
      Applying auth.0003_alter_user_email_max_length... OK
      Applying auth.0004_alter_user_username_opts... OK
      Applying auth.0005_alter_user_last_login_null... OK
      Applying auth.0006_require_contenttypes_0002... OK
      Applying auth.0007_alter_validators_add_error_messages... OK
      Applying auth.0008_alter_user_username_max_length... OK
      Applying main.0001_initial... OK
      Applying main.0002_journey... OK
      Applying sessions.0001_initial... OK
      Applying sites.0001_initial... OK
      Applying sites.0002_alter_domain_unique... OK
      Applying socialaccount.0001_initial... OK
      Applying socialaccount.0002_token_max_lengths... OK
      Applying socialaccount.0003_extra_data_default_dict... OK
    

    @tapasweni-pathak You have migration 0003 for main. Mirgration 0003_auto for main model isn't there on the predev branch

    (venv) ➜  main git:(predev) ls migrations                
    0001_initial.py  0002_journey.py  __init__.py  __pycache__
    
  5. tapaswenipathak commented on Jan 13, 2018

    @tapaswenipathak
    Member

    gotcha 👍. What are your thoughts on Heroku not having this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions