Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-09-01 Thread Diana Clarke
> upstream issue: > > https://github.com/PyMySQL/PyMySQL/issues/507 A fix for this was merged in pymysql 0.7.8. --diana __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Joshua Harlow
+1 to 4.13.1 I'll get a release review up once https://review.openstack.org/#/c/363828/ merges (seems to be on its way to merging). https://review.openstack.org/#/c/364063/ Enjoy! -Josh __ OpenStack Development

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Joshua Harlow
We need to decide how to handle this: https://review.openstack.org/#/c/362991/ Basically, PyMySQL normally raises an error message like this: (pymysql.err.IntegrityError) (1452, u'Cannot add or update a child row: a foreign key constraint fails (`vaceciqnzs`.`resource_entity`, CONSTRAINT

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Davanum Srinivas
On Wed, Aug 31, 2016 at 12:09 PM, Doug Hellmann wrote: > Excerpts from Ihar Hrachyshka's message of 2016-08-31 16:48:09 +0200: >> Mike Bayer wrote: >> >> > We need to decide how to handle this: >> > >> > https://review.openstack.org/#/c/362991/ >> > >> >

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Doug Hellmann
Excerpts from Ihar Hrachyshka's message of 2016-08-31 16:48:09 +0200: > Mike Bayer wrote: > > > We need to decide how to handle this: > > > > https://review.openstack.org/#/c/362991/ > > > > > > Basically, PyMySQL normally raises an error message like this: > > > >

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Julien Danjou
On Wed, Aug 31 2016, Ihar Hrachyshka wrote: > I suggest we: > - block 0.7.7 to unblock upper-constraints updates; > - land oslo.db fix to cope with pymysql 0.7.7+, in master as well as all > stable > branches; > - release new oslo.db releases for L-N; > - at least for N, bump minimal version of

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Mike Bayer
On 08/31/2016 10:48 AM, Ihar Hrachyshka wrote: Unless we fix the bug in next pymysql, it’s not either/or but both will be needed, and also minimal oslo.db version bump. upstream issue: https://github.com/PyMySQL/PyMySQL/issues/507 PyMySQL tends to be very responsive to issues (plus I

Re: [openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Ihar Hrachyshka
Mike Bayer wrote: We need to decide how to handle this: https://review.openstack.org/#/c/362991/ Basically, PyMySQL normally raises an error message like this: (pymysql.err.IntegrityError) (1452, u'Cannot add or update a child row: a foreign key constraint fails

[openstack-dev] [oslo] pymysql change in error formatting has broken exception handing in oslo.db

2016-08-31 Thread Mike Bayer
We need to decide how to handle this: https://review.openstack.org/#/c/362991/ Basically, PyMySQL normally raises an error message like this: (pymysql.err.IntegrityError) (1452, u'Cannot add or update a child row: a foreign key constraint fails (`vaceciqnzs`.`resource_entity`, CONSTRAINT