Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Renat Akhmerov
Ok, thanks. We’ll fix it in Mistral accordingly. Renat Akhmerov @ Mirantis Inc. > On 26 Aug 2015, at 15:12, Dmitry Tantsur wrote: > > On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote: >> On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent wrote: >>> On Wed, 26 Aug 2015, Dmitry Tantsur wrote: >>> >

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Dmitry Tantsur
On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote: On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent wrote: On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should communicate this po

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Lucas Alvares Gomes
Hi, > > +1, yeah I kinda agree with the major version bump. But also it's > important to note that Ironic which was affected by that was relying > on be able to POST nonexistent fields to create resources and WSME > would just ignore those on versions <= 0.8.0. That's a legitimate bug > that have

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Lucas Alvares Gomes
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent wrote: > On Wed, 26 Aug 2015, Dmitry Tantsur wrote: > >> Note that this is an API breaking change, which can potentially break >> random users of all projects using wsme. I think we should communicate this >> point a bit louder, and I also believe it sho

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Chris Dent
On Wed, 26 Aug 2015, Renat Akhmerov wrote: What would be your recommendation for now? Just to cap wsme version and hold on with changes adjusting to WSME 0.8.0? Or you think most likely these changes in new WSME will remain on? The fixes in WSME are fixes for genuine bugs. If code using WSME w

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Renat Akhmerov
Chris, What would be your recommendation for now? Just to cap wsme version and hold on with changes adjusting to WSME 0.8.0? Or you think most likely these changes in new WSME will remain on? Thanks Renat Akhmerov @ Mirantis Inc. > On 26 Aug 2015, at 14:27, Chris Dent wrote: > > On Wed, 26

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Chris Dent
On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should communicate this point a bit louder, and I also believe it should have warranted a major version bump. Yeah, Lucas and I

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Renat Akhmerov
> On 26 Aug 2015, at 13:40, Dmitry Tantsur wrote: > > On 08/25/2015 07:38 PM, Chris Dent wrote: >> >> WSME version 0.8.0 was released today with several fixes to error >> handling and error messages. These fixes make WSME behave more in >> the way it says it would like to behave (and should beh

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Dmitry Tantsur
On 08/25/2015 07:38 PM, Chris Dent wrote: WSME version 0.8.0 was released today with several fixes to error handling and error messages. These fixes make WSME behave more in the way it says it would like to behave (and should behave) with regard to input validation and HTTP handling. You want th

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-26 Thread Lingxian Kong
Hi, Chris, Thanks for bringing this up, and let us know. The same issues also affected Mistral :-( On Wed, Aug 26, 2015 at 1:38 AM, Chris Dent wrote: > > WSME version 0.8.0 was released today with several fixes to error > handling and error messages. These fixes make WSME behave more in > the w

[openstack-dev] [wsme] potential issues with WSME 0.8.0

2015-08-25 Thread Chris Dent
WSME version 0.8.0 was released today with several fixes to error handling and error messages. These fixes make WSME behave more in the way it says it would like to behave (and should behave) with regard to input validation and HTTP handling. You want these changes. Unfortunately we've discovere