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.

Sign up for GitHub

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

Jump to bottom

pure ruby regexp <capture:int> coercion does not work #164

Open
kares opened this issue Aug 11, 2020 · 0 comments
Open

pure ruby regexp <capture:int> coercion does not work #164

kares opened this issue Aug 11, 2020 · 0 comments

Comments

@kares
Copy link
Contributor

kares commented Aug 11, 2020 •
edited
Loading

sample (?<throughputtime:int>[0-9]+) instead of captuing

  • "throughputtime" => 1760 in LS 1.4.2
  • ends up capturing "int" => "1760" tested LS 6.8 and 7.7

seems to have been working (coercing) at some point around LS 1.4.2 but not since 1.5

the cause seems to be the 'optimization' in grok gem (since 0.11.0):
jordansissel/ruby-grok@288fcc2#diff-0badcaad3c9a90480e7857e04b49fb3cR145

origin bug report: elastic/logstash#3557

NOTE: Grok.new is also used in multi-line - require "grok-pure" directly!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kares