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

Issue with JRuby #3650

Closed
bryanvpham opened this issue Sep 15, 2017 · 7 comments
Closed

Issue with JRuby #3650

bryanvpham opened this issue Sep 15, 2017 · 7 comments
Assignees

Comments

@bryanvpham
Copy link

Used protoc to generate at.rb. My main.rb literally just includes at.rb and outputs "hello world".

I built the gem from scratch following the instructions in the readme. Tried running my simple ruby program that

RuntimeError: headers.key: "key" is already defined in "headers".
    build at com/google/protobuf/jruby/RubyDescriptorPool.java:84
   <main> at /root/work/at/at.rb:6
  require at org/jruby/RubyKernel.java:955
   (root) at uri:classloader:/jruby/kernel/kernel.rb:1
   <main> at main.rb:1
@liujisi
Copy link
Contributor

liujisi commented Sep 15, 2017

My impression is Jruby is currently broken and not maintained by anyone.. Adding @haberman for more info.

@TeBoring TeBoring added the jruby label Sep 20, 2017
@felixcuello
Copy link

The workaround I found (for now) is to rename map structures and have unique names for all of them. Because as soon as I repeat the map name we get the exact same error.

@mjmateuci
Copy link

Do you guys found another way to solve this issue? @bryanvpham @pherl

@headius
Copy link

headius commented Oct 2, 2019

JRuby has been continuously maintained for over ten years and is still in very active use at many organizations. Can we get this fixed?

@acozzette
Copy link
Member

At the moment I don't think we have anyone working on protobuf who is knowledgeable about JRuby unfortunately, but we would be glad to accept pull requests with fixes.

@jthack
Copy link

jthack commented May 6, 2020

Pretty crazy this issue is still around.

@haberman
Copy link
Member

I believe this is fixed in #7923.

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

No branches or pull requests

10 participants