On Wed, Jun 01, 2016 at 02:28:02PM +0200, Thierry FOURNIER wrote:
> I forgot the patches in attachment ;)
Just merged right now.
Thanks Thierry!
Willy
Hi Michael,
On Tue, Jun 07, 2016 at 03:35:06PM -0400, Michael Ezzell wrote:
> On Tue, Jun 7, 2016 at 2:27 PM, Willy Tarreau wrote:
>
> > Hi Michael,
> >
> > Please do not forget to test Thierry's patches to confirm or invalidate
> > that they fix your issue. If you don't have the
On Tue, Jun 7, 2016 at 2:27 PM, Willy Tarreau wrote:
> Hi Michael,
>
> Please do not forget to test Thierry's patches to confirm or invalidate
> that they fix your issue. If you don't have the time, that's fine, just
> say so and I'll merge them.
>
Confirmed,
tested,
the issue
Hi Michael,
On Wed, Jun 01, 2016 at 02:03:51PM +0200, Thierry FOURNIER wrote:
> Hi Willy,
>
> I join a serie of 3 patches. With these patches, I can't reproduce the
> bug.
>
> Michael, can you test the patches and confirm or not that the bug
> disappear ?
>
> All the patches must be backported
I forgot the patches in attachment ;)
On Wed, 1 Jun 2016 14:03:51 +0200
Thierry FOURNIER wrote:
> Hi Willy,
>
> I join a serie of 3 patches. With these patches, I can't reproduce the
> bug.
>
> Michael, can you test the patches and confirm or not that the bug
>
Hi Willy,
I join a serie of 3 patches. With these patches, I can't reproduce the
bug.
Michael, can you test the patches and confirm or not that the bug
disappear ?
All the patches must be backported in the 1.6 version, an onr of these
must be also backported in the 1.5 version.
Thierry
On
On Mon, May 30, 2016 at 04:26:11PM +0200, Thierry FOURNIER wrote:
> Thank you for the bug report;
>
> I catch it. I join a temporary fix, I suspect that the problem to be more
> tricky.
Thierry, just to be clear, I preferred not to pick your patches for now
since you're still debugging. However
Thank you for the bug report;
I catch it. I join a temporary fix, I suspect that the problem to be more
tricky.
Thierry
On Fri, 27 May 2016 16:22:41 -0400
Michael Ezzell wrote:
>
> On Fri, May 27, 2016 at 10:41 AM, Thierry FOURNIER
> wrote:
>
On Fri, May 27, 2016 at 10:41 AM, Thierry FOURNIER
wrote:
> Hi,
>
> Thank you for the bug repport. It was perfect. I found and fixed the
> bug. You can try the patch in attachement.
>
>
Thanks, Thierry.
The converter is now able to be called, and returns a value as
Hi,
Thank you for the bug repport. It was perfect. I found and fixed the
bug. You can try the patch in attachement.
Willy, you can integrate it in the main stream, and do the backport in
the 1.6 version (I tried the backport, and it is easyly applied).
Thierry
On Thu, 26 May 2016 18:05:50
On Tue, May 24, 2016 at 02:19:06PM -0400, Michael Ezzell wrote:
> I'm trying to create a Lua converter, but every time I try to call the
> converter, I get this:
>
> May 24 17:59:34 localhost haproxy[31077]: Lua converter 'testconv': runtime
> error: attempt to call a nil value.
>
> I've
I'm trying to create a Lua converter, but every time I try to call the
converter, I get this:
May 24 17:59:34 localhost haproxy[31077]: Lua converter 'testconv': runtime
error: attempt to call a nil value.
I've simplified this down to a minimal test case:
--
testfn = function(str)
12 matches
Mail list logo