Use “reply-all” so the thread stays on the list.
> On Nov 14, 2016, at Nov 14, 4:33 AM, Azam Mohammed wrote:
>
> Hi Bryan,
>
> Thanks for your email.
>
> I was doing a bit of testing on haproxy.
>
> I used hdr to match the subdomain in frontend but I got 503 "503 Service
> Unavailable" No s
Hi,
On 14.11.2016 18:26, Willy Tarreau wrote:
> Hi Thomas,
>
> On Fri, Nov 11, 2016 at 05:33:55PM +0100, Thomas Heil wrote:
>>> Lede has OPENSSL_WITH_DEPRECATED menuconfig [1], which defaults to yes
>>> (so a default LEDE build should be fine).
>>>
>>> Can you confirm your config has OPENSSL_WITH
Hi Thomas,
On Fri, Nov 11, 2016 at 05:33:55PM +0100, Thomas Heil wrote:
> > Lede has OPENSSL_WITH_DEPRECATED menuconfig [1], which defaults to yes
> > (so a default LEDE build should be fine).
> >
> > Can you confirm your config has OPENSSL_WITH_DEPRECATED = y?
> >
>
> Wow, nice hint. Well I ad
Hi Bertrand,
On Mon, Nov 14, 2016 at 08:49:28AM +0100, Willy Tarreau wrote:
> I'll pick your fixes from the patchset though ;-)
OK, patches 4 to 8 applied, and 1-3 kept for later, thanks!
Willy
Hi,
On Mon, Nov 14, 2016 at 03:29:58PM +, Mirek Svoboda wrote:
> What if we have the descriptions in the source code, serving as a single
> source of truth, and generate the JSON schema file from the source code
> upon build?
... or on the fly. That's what I was thinking as well. Ie
"show sta
Hi
> > OK. So does this mean that a schema will have to be maintained by hand in
> > parallel or will it be deduced from the dump ? I'm starting to be worried
> > about something not being kept up to date if we have to maintain it, or
> > causing a slow down in adoption of new stats entries.
>
> I
On Mon, Nov 14, 2016 at 08:50:54AM -0500, hapr...@stormcloud9.net wrote:
> Might help to see an example of what the results look like when using
> this schema, however I do have one comment below.
Yes, agreed. I plan to work on making that so.
> On 2016/11/14 03:09, Simon Horman wrote:
> > Hi Wil
Hi Willy,
On Mon, Nov 14, 2016 at 03:10:18PM +0100, Willy Tarreau wrote:
> On Mon, Nov 14, 2016 at 11:34:18AM +0100, Simon Horman wrote:
> > > Sometimes a description like above appears in your example, is it just
> > > for a few fields or do you intend to describe all of them ? I'm asking
> > > b
On Mon, Nov 14, 2016 at 11:34:18AM +0100, Simon Horman wrote:
> > Sometimes a description like above appears in your example, is it just
> > for a few fields or do you intend to describe all of them ? I'm asking
> > because we don't have such descriptions right now, and while I won't
> > deny that
Might help to see an example of what the results look like when using
this schema, however I do have one comment below.
On 2016/11/14 03:09, Simon Horman wrote:
> Hi Willy, Hi All,
>
> On Thu, Nov 10, 2016 at 04:52:56PM +0100, Willy Tarreau wrote:
>> Hi Simon!
>>
>> On Thu, Nov 10, 2016 at 04:27:1
Hi Willy,
On Mon, Nov 14, 2016 at 11:11:12AM +0100, Willy Tarreau wrote:
> Hi Simon,
>
> On Mon, Nov 14, 2016 at 09:09:21AM +0100, Simon Horman wrote:
> > I took a first pass at defining a schema.
> >
> > * The schema follows what is described on json-schema.org (or at least
> > tries to). Is
Hi Simon,
On Mon, Nov 14, 2016 at 09:09:21AM +0100, Simon Horman wrote:
> I took a first pass at defining a schema.
>
> * The schema follows what is described on json-schema.org (or at least
> tries to). Is this a suitable approach?
I'll let others respond as I have no idea since I never need
Hi Willy, Hi All,
On Thu, Nov 10, 2016 at 04:52:56PM +0100, Willy Tarreau wrote:
> Hi Simon!
>
> On Thu, Nov 10, 2016 at 04:27:15PM +0100, Simon Horman wrote:
> > My preference is to take things calmly as TBH I am only just getting
> > started on this and I think the schema could take a little ti
13 matches
Mail list logo