On Tue, Jun 26, 2018 at 5:14 PM Vladyslav Drok wrote:
>
> On Tue, Jun 26, 2018 at 4:58 PM Takashi Yamamoto
> wrote:
>
>> On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann
>> wrote:
>> > Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500:
>> >> Thanks a bunch for digging into
On Tue, Jun 26, 2018 at 4:58 PM Takashi Yamamoto
wrote:
> On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann
> wrote:
> > Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500:
> >> Thanks a bunch for digging into this, Tony. I'll follow up with the
> >> oauthlib maintainers and see
On 06/26/2018 08:57 AM, Takashi Yamamoto wrote:
> On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann wrote:
>> Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500:
>>> Thanks a bunch for digging into this, Tony. I'll follow up with the
>>> oauthlib maintainers and see if they'd be
On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann wrote:
> Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500:
>> Thanks a bunch for digging into this, Tony. I'll follow up with the
>> oauthlib maintainers and see if they'd be interested in these changes
>> upstream. If so, I can
Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500:
> Thanks a bunch for digging into this, Tony. I'll follow up with the
> oauthlib maintainers and see if they'd be interested in these changes
> upstream. If so, I can chip away at it. For now we'll have to settle for
> not
Thanks a bunch for digging into this, Tony. I'll follow up with the
oauthlib maintainers and see if they'd be interested in these changes
upstream. If so, I can chip away at it. For now we'll have to settle for
not treating warnings as errors to unblock our documentation gate [0].
[0]
On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote:
> Keystone is hitting this, too [0]. I attempted the same solution that
> Tony posted, but no luck. I've even gone so far as removing every
> comment from the module to see if that helps narrow down the problem
> area, but sphinx
Keystone is hitting this, too [0]. I attempted the same solution that
Tony posted, but no luck. I've even gone so far as removing every
comment from the module to see if that helps narrow down the problem
area, but sphinx still trips. The output from the error message isn't
very descriptive
On Thu, Jun 21, 2018 at 12:13 PM, Tony Breeds wrote:
> On Wed, Jun 20, 2018 at 08:54:56PM +0900, Takashi Yamamoto wrote:
>
>> do you have a plan to submit these changes on gerrit?
>
> I didn't but I have now:
>
> * https://review.openstack.org/577028
> * https://review.openstack.org/577029
>
>
On Wed, Jun 20, 2018 at 08:54:56PM +0900, Takashi Yamamoto wrote:
> do you have a plan to submit these changes on gerrit?
I didn't but I have now:
* https://review.openstack.org/577028
* https://review.openstack.org/577029
Feel free to edit/test as you like.
Yours Tony.
signature.asc
hi,
On Thu, May 17, 2018 at 12:51 PM, Tony Breeds wrote:
> On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote:
>> On 18-05-16 17:07:09, Doug Hellmann wrote:
>> > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
>> > > Sphinx has breaking changes (yet again) and we
Sphinx is being updated from 1.6.7 to 1.7.5. You may need to update
your docs/templates to work with it.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not
On 18-05-17 13:51:06, Tony Breeds wrote:
> On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote:
> > On 18-05-16 17:07:09, Doug Hellmann wrote:
> > > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > > > Sphinx has breaking changes (yet again) and we need to figure
On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote:
> On 18-05-16 17:07:09, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > > Sphinx has breaking changes (yet again) and we need to figure out how to
> > > deal with it. I think the fix
The Octavia project had other breakage due to sphinx > 1.7 but we have
already resolved those issues.
Back story: the way arguments are handled for apidoc changed.
An example patch for the fix would be: https://review.openstack.org/#/c/568383/
Michael (johnsom)
On Wed, May 16, 2018 at 1:59 PM,
On 18-05-16 17:07:09, Doug Hellmann wrote:
> Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > Sphinx has breaking changes (yet again) and we need to figure out how to
> > deal with it. I think the fix will be simple for affected projects, but
> > we should probably move
Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> Sphinx has breaking changes (yet again) and we need to figure out how to
> deal with it. I think the fix will be simple for affected projects, but
> we should probably move forward on this. The error people are getting
> seems
Sphinx has breaking changes (yet again) and we need to figure out how to
deal with it. I think the fix will be simple for affected projects, but
we should probably move forward on this. The error people are getting
seems to be 'Field list ends without a blank line; unexpected unindent.'
I'd
18 matches
Mail list logo
