You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't have knowledge or expertise in this project to know what this r10k project does or how it uses rugged. It does look like it could be a bug in rugged or libgit2 as it shouldn't ever segfault, but without seeing the code or how rugged was called, I don't see how we can investigate. The project that is crashing for you should be able to move on this.
I'm running /opt/puppetlabs/puppet/bin/r10k deploy environment but this results in
/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.5.8p224 (2020-03-31 revision 67882) [x86_64-linux]
-- Control frame information -----------------------------------------------
c:0027 p:---- s:0175 e:000174 CFUNC :fetch
c:0026 p:0060 s:0169 e:000168 METHOD /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257
c:0025 p:0015 s:0162 e:000161 BLOCK /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/r10k-3.7.0/lib/r10k/git/rugged/bare_repository.rb:67
The text was updated successfully, but these errors were encountered: