Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(): remove wrong param in traceback.format_exc #39

Merged
merged 1 commit into from
Feb 3, 2017
Merged

fix(): remove wrong param in traceback.format_exc #39

merged 1 commit into from
Feb 3, 2017

Conversation

triat
Copy link
Contributor

@triat triat commented Feb 3, 2017

Based on the documentation, format_exc is expecting an int value, it's supposed to fix the PR #18

@coveralls
Copy link

coveralls commented Feb 3, 2017

Coverage Status

Changes Unknown when pulling 949163c on Pix4D:handle_500 into ** on aschn:handle_500**.

@avelis avelis merged commit 46e5bbb into aschn:handle_500 Feb 3, 2017
@avelis
Copy link
Collaborator

avelis commented Feb 3, 2017

@triat Thanks for the contribution.

avelis pushed a commit that referenced this pull request Mar 1, 2017
* add errors field

* log exception in view

* Resets migration dependency and file name

Changes migration file and dependency back to the initial migration file. The project moved forward with a backwards incompatible change and this PR was not updated to reflect that change. All migrations were squashed into the initial migration for simplicity.

* Fixes incorrect indentation to pass lint check

Through user error, the indentation of this test method was incorrectly added. Likely, due to merging conflicts from the master branch using the GIthub UI.

* fix(): remove wrong param in traceback.format_exc (#39)

* Updates and renames migration file

Updating the order number of the file and the migration dependency resolves the migration conflict in the PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants