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

StringScanner does not accept [:symbol] #3788

Open
onli opened this Issue Mar 17, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@onli
Copy link

onli commented Mar 17, 2018

I'm using the gem http-accept. This gem makes a scan with one of those regexpressions containing named subgroups, here, and then later tries to access its result via [:group] - mri allows that since Ruby 2.1, see here. But in strscan [] does not allow inputs that do not convert to integer, breaking the gem.

I did not find a statement which API version you are targeting, but I thought it was above 2.1? If not, is there a way to make bundler aware which ruby API version rubinius supports?

  1. What command did you run?

I ran bundle exec puma -e development

  1. What behavior did you expect?

My sinatra/puma app that uses the http-accept gem to run

  1. What behavior did you get instead?

I observed a stacktrace.

  1. What version of Rubinius?

Output of rbx -v: rubinius 3.100.c2 (2.3.1 d08bd4e 2018-03-16 3.9.1) [x86_64-linux-gnu]

  1. What version of operating system?

Output of uname -a: Linux Fallout 4.14.12-2 #1 SMP Sun Jan 7 22:35:18 CET 2018 x86_64 AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux

  1. What is your operating system distribution, if your operating system has more than one?

My distribution is funtoo, a gentoo fork.

  1. How did you build your version of Rubinius?
  • I used RVM.
  • I used ruby-build.
  • I used ruby-install.
  • I built manually from a tarball.
  • I built manually from a git clone.
  • I installed a binary.
  1. Does this issue involve proprietary code?
  • Yes, this issue involves proprietary code that I cannot share.
  • Yes, this issue involves proprietary code, but I am able to share it under certain conditions.
  • No, this issue doesn't involve proprietary code.

(It does in the context of my application, but I think all the moving parts here are free)

  1. Are you able to help us debug the issue?
  • Yes, I'm able to help debug, including running commands under lldb.
  • No, I'm not able help debug or I don't have time to help.
@brixen

This comment has been minimized.

Copy link
Member

brixen commented Mar 17, 2018

@onli the supported Ruby version is available in RUBY_VERSION and in the -v output, which should be 2.3.1. However, we fix issues as they are reported due to a combination of incomplete test coverage in MRI and constant, often subtle, changes.

Thanks for opening the issue. We'll take a look at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment