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

Syntax error with latest version 0.14.0 #237

Open
castro1688 opened this issue May 29, 2020 · 13 comments
Open

Syntax error with latest version 0.14.0 #237

castro1688 opened this issue May 29, 2020 · 13 comments

Comments

@castro1688
Copy link

The latest release is throwing syntax errors

/usr/local/share/gems/gems/vault-0.14.0/lib/vault/api.rb:12:in `require_relative': /usr/local/share/gems/gems/vault-0.14.0/lib/vault/api/transform.rb:14: syntax error, unexpected ',' (SyntaxError)
    def encode(role_name:, **opts)
                          ^
/usr/local/share/gems/gems/vault-0.14.0/lib/vault/api/transform.rb:19: syntax error, unexpected ','
    def decode(role_name:, **opts)
                          ^
/usr/local/share/gems/gems/vault-0.14.0/lib/vault/api/transform.rb:23: syntax error, unexpected keyword_end, expecting end-of-input
	from /usr/local/share/gems/gems/vault-0.14.0/lib/vault/api.rb:12:in `<module:API>'
	from /usr/local/share/gems/gems/vault-0.14.0/lib/vault/api.rb:2:in `<module:Vault>'
	from /usr/local/share/gems/gems/vault-0.14.0/lib/vault/api.rb:1:in `<top (required)>'
	from /usr/local/share/gems/gems/vault-0.14.0/lib/vault.rb:9:in `require_relative'
	from /usr/local/share/gems/gems/vault-0.14.0/lib/vault.rb:9:in `<module:Vault>'
	from /usr/local/share/gems/gems/vault-0.14.0/lib/vault.rb:1:in `<top (required)>'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:135:in `require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:144:in `require'
	from /XXXXXXXXXXX.rb:9:in `<top (required)>'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /XXXXXXXXXXX:9:in `<top (required)>'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /XXXXXXXXXXX.rb:13:in `<top (required)>'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /XXXXXXXXXXX.rb:13:in `<main>'
@laserguy2020
Copy link

Same issue with 0.15.0

@Valarissa
Copy link
Contributor

Can I ask what version of Ruby you are both using?

@Valarissa
Copy link
Contributor

I ask because this syntax is valid as of Ruby 2.0 https://thoughtbot.com/blog/ruby-2-keyword-arguments and Ruby 1.9.3 was EOL'd back in 2015: https://www.ruby-lang.org/en/news/2014/01/10/ruby-1-9-3-will-end-on-2015/

@laserguy2020
Copy link

ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]

@laserguy2020
Copy link

I have no issues with 0.13.0 but 0.14.0 and 0.15.0 I run into this issue.

@Valarissa
Copy link
Contributor

Are you certain that the version of ruby that is running the code isn't a distribution provided ruby? I ask this because I still have passing tests and am able to manually test with the same version of Ruby and a syntax error would most definitely not allow tests to pass since the code is loaded and parsed successfully.

@laserguy2020
Copy link

It was a CentOS provided Ruby

@Valarissa
Copy link
Contributor

So, confirming, are you saying that the code was running on a different version of Ruby? Or are you saying that the 2.7.0p0 was provided by CentOS?

@laserguy2020
Copy link

I am saying the 2.7.0p0 was provided by CentOS

@Valarissa
Copy link
Contributor

Are you able to pull the code here and run bundle exec rspec? Does the issues present itself there?

@laserguy2020
Copy link

What do you want me to run rspec on? Do you mean this library?

@Valarissa
Copy link
Contributor

Yup! Just to see what kind of outputs you get from running the tests for vault ruby, because I'm not able to reproduce.

@laserguy2020
Copy link

I will do this first thing in the morning :)

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

No branches or pull requests

3 participants