Closed leoarnold closed 2 years ago
Who does khow how fix this BUG? Pipelines are falling, work is slowing down)
This is now fixed on #45. Waiting for @lubc or @bronzdoc to review and approve my changes.
You can add new tag?
https://github.com/rubymem/bundler-leak/issues/44#issue-1116903529
I fixed it like this
module Psych
class ClassLoader
class Restricted < ClassLoader
private
def find(klassname)
return super if (@classes.include? klassname) || (klassname == 'Date')
raise DisallowedClass.new('load', klassname)
end
end
end
end
Still have this problem.. Is it fixed on https://github.com/rubymem/bundler-leak/pull/45? I see that it is merged, but problem is still actual, as i understand..
I just released bundler-leak
0.3.0 please install the latest version and try again, thanks!
I just released
bundler-leak
0.3.0 please install the latest version and try again, thanks!
Yeah, @bronzdoc, but I receive new exception like this
bundler-leak-0.3.0/data/ruby-mem-advisory-db" is not a directory (ArgumentError)
also I use last version redis
@Quitehours Try bundler-leak update
if that doesn't help please open a new issue, with the steps to reproduce. Thanks
Thanks. Working now good.
For the record: When using Docker, prefer
bash -lc "bundle exec bundler-leak update && bundle exec bundler-leak"
Otherwise the downloaded database may be gone in the second invocation because the file system layer was not persisted.
Before we start...:
Branch/Commit:
I am not using
Skunk.fyi
at all. This is aboutbundler-leak (0.2.0)
.Expected behavior:
I can run
bundle leak
without runtime error.Actual behavior:
Steps to reproduce:
Install Ruby 3.1.0 and try to run
bundle leak
.I will abide by the [code of conduct] (code_of_conduct.md)