Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

completerlang: quick fix for PLY-3.6 #482

Merged
merged 1 commit into from
May 12, 2015

Conversation

lbudai
Copy link
Collaborator

@lbudai lbudai commented May 12, 2015

Local variable 'state' is not in frame 1 anymore, it is in frame 2 in
PLY-3.6 (there is a callback which calls our function this is the reason why
the state variable is in frame 2).

Note that this is an ugly-ugly hack :-)
We have to eliminate this sitation somehow.

Signed-off-by: Laszlo Budai Laszlo.Budai@balabit.com

Local variable 'state' is not in frame 1 anymore, it is in frame 2 in
PLY-3.6 (there is a callback which calls our function this is the reason why
the state variable is in frame 2).

Note that this is an ugly-ugly hack :-)
We have to eliminate this sitation somehow.

Signed-off-by: Laszlo Budai <Laszlo.Budai@balabit.com>
@bazsi
Copy link
Collaborator

bazsi commented May 12, 2015

I agree it is an ugly hack. The problem is that ply fails to publish this value to our callback, but upstream seems to be responsive so we might get a patch in that sets an attribute in the parser. However this hack is needed until that propagates to distros.

I think this is ok for now.

lbudai added a commit that referenced this pull request May 12, 2015
completerlang: quick fix for PLY-3.6
@lbudai lbudai merged commit e37a7a3 into syslog-ng:master May 12, 2015
@lbudai
Copy link
Collaborator Author

lbudai commented May 12, 2015

I understand the reason behind the patch (and know you wouldn't have wrote that code if there would be better solution) :-)

patch ply : 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants