Visitar URL original
no settings.yml file · Issue #3 · quantifiedcode/quantifiedcode · GitHub
Skip to content

no settings.yml file #3

Open
Open

Description

@brycekallen

It looks like in .gitignore you have ignored the settings.yml file which is necessary for the python manage.py setup step. Any way this can be added back?

Thanks

Activity

  1. adewes commented on Aug 15, 2017

    @adewes
    Member

    Hey Bryce, can you try to create an empty settings.yml and then run python manage.py setup (which should create the correct entries)?

    Sorry the installer is still very rough around the edges and I'm working on a better one as well as a Docker version, I will update you as soon as those are online.

  2. brycekallen commented on Aug 15, 2017

    @brycekallen
    Author

    @adewes Thanks for getting back to me. Its funny I tried that exact fix before raising the issue and still got an error:

    ballen:quantifiedcode ballen$ touch settings.yml
    ballen:quantifiedcode ballen$ python manage.py setup
    Loading settings from /Users/ballen/quantifiedcode/quantifiedcode/settings/default.yml
    Loading settings from /Users/ballen/quantifiedcode/settings.yml
    Traceback (most recent call last):
      File "manage.py", line 2, in <module>
        from quantifiedcode.backend.commands import commands
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/commands/__init__.py", line 6, in <module>
        from .server import runserver
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/commands/server.py", line 2, in <module>
        from quantifiedcode.app import get_app
      File "/Users/ballen/quantifiedcode/quantifiedcode/app.py", line 21, in <module>
        from quantifiedcode.backend.app import get_app as get_backend_app
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/app.py", line 22, in <module>
        from .api.v1 import routes as routes_v1
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/api/v1/__init__.py", line 1, in <module>
        from .routes import routes
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/api/v1/routes.py", line 51, in <module>
        from .issue import (
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/api/v1/issue.py", line 18, in <module>
        from .forms.issue_status import IssueStatusForm
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/api/v1/forms/issue_status.py", line 6, in <module>
        class IssueStatusForm(Form):
      File "/Users/ballen/quantifiedcode/quantifiedcode/backend/api/v1/forms/issue_status.py", line 9, in IssueStatusForm
        ignore_reason = SelectField(u"Ignore Reason", choices=[(str(Issue.IgnoreReason.false_positive),"false positive"),
    AttributeError: type object 'Issue' has no attribute 'IgnoreReason'
    

    At that point I just figured I'd reach out to see if it was worth proceeding further

  3. adewes commented on Aug 15, 2017

    @adewes
    Member

    Ah okay this might be an issue with the checkmate version, please do not invest more time in this (as I think it needs to be resolved on our side) and let me get back to you as soon as I have the installer ready.

  4. IBestuzhev commented on Aug 16, 2017

    @IBestuzhev

    I had the same issue - installing checkmate from GitHub instead of pypi helped with this traceback.
    BTW, it was not added to requirements.txt and neither described in readme.

    Later it fails with blank settings.yml file. I had to put backend: {} there for commands to start. However setup did not modify the file, so I had to put DB and Rabbit URLs manually

  5. wolfy1339 commented on Sep 12, 2017

    @wolfy1339

    This issue is very well still present

  6. jrial commented on Oct 3, 2017

    @jrial

    Could you please add a sample file so we know what kind of settings can be defined, and what the structure looks like?

    Writing a better installer takes time (as evidenced by the fact that this issue is now open for over six weeks), while a sample file is something you can literally sanitise from your local settings file and commit in 5-10 minutes.

  7. adewes commented on Oct 3, 2017

    @adewes
    Member

    Hi @jrial and @wolfy1339, sorry I was very busy in the last week, I'll add/fix the install instructions and the problems with the settings file as soon as possible.

  8. jrial commented on Oct 5, 2017

    @jrial

    @wolfy1339 thanks, I've found that one as well in the meantime, while looking at the setup procedure.

    Onto the next problem: Celery! ;)

  9. adewes commented on Oct 6, 2017

    @adewes
    Member

    Thanks for helping with this, I'm working on a Python-3 compatible version that should solve the current issues and hope to release it this weekend!

  10. adewes commented on Oct 6, 2017

    @adewes
    Member

    @jrial you should be able to switch to Celery 4 (in the requirements) now as they finally fixed the upstream bug which prevented this. I'll also upgrade that in the new release.

  11. haoshenzhang commented on Oct 12, 2017

    @haoshenzhang

    @wolfy1339 when I analyze an project I got http 404 error the ression is that I coun't get snapshot

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions