3
0%
master: 0%

Ran 02 Jun 2016 09:18PM UTC

Files 15

Run time 8s

Badge

Embed ▾

Committed 02 Jun 2016 07:27PM UTC coverage: 82.095%. Remained the same

Job # 1786.3

Build Type

push

travis-ci

Committed by

mistercrunch

Commit Message

Fix #529 2 - "This Session's transaction has been rolled back" (#531)

* Created migration to fix the bug

* Working also on MySQL

* Added support for Vertica Grains (#515)

* Fix #529 1 "This Session's transaction has been rolled back" (#530)

* Fixing the specific issue

* Added an additional fix for a similar error in #529

Background:
- When an object is modified by SQLAlchemy, it is invalidated so need to be fetched again from the DB
- If there's an exception during a transaction, SQLAlchemy performs a rollback and mark the connection as dirty.

Bug:
- When handling exceptions, the exception handler tries to access the name of the cluster in the main object. Since the name has been invalidated due to a write, SQLAlchemy tries to fetch it on a 'dirty' connection and spits out an error. Solution:
- Fetch the information for handling the exception before starting the process.

* Modified the migration function to to automatically detect the the foreign keys based on the signature.
It supports also sqlite using batch migrations

* i18n: Fix typo in Druid cluster broker port label (#512)

* Update models.py (#541)

removing duplicated `user_id` def

Run Details

2343 of 2854 relevant lines covered (82.1%)

0.82 hits per line

airbnb / superset / 1786 / 3
0%
master: 0%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1786.3

airbnb / superset / 1786 / 3 0% master: 0%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1786.3

airbnb / superset / 1786 / 3
0%
master: 0%

README BADGES
x