-
Notifications
You must be signed in to change notification settings - Fork 154
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
Unable to use Ruby 3.x #66
Comments
Hey ! I have the exact same problem. I don't see any commit for almost 2 years on this repo, is this project not maintained anymore ? |
https://github.com/n-studio/kimuraframework/tree/dev/ruby-3 <- this branch might help. I can't guarantee it's production ready though. You also need to add: |
Similar problem here, the error message around "given 2, expected 1" argument is thrown for colorizer.rb. Have updated my Gemfile as follows:
Here's the full error stack:
So above solution doesn't seem to work? |
@tkhobbes Did you |
Weird. Yes it's updated, if I do bundle info kimurai I get
But when I run my program with "ruby myprog.rb" I still get this message:
I simply have a "require 'kimurai'" line in my program... so I am not 100% sure why it's using the OLD gem (1.4.0) and not the NEW one. Seems like some sort of other problem going on. |
@tkhobbes Running |
Thanks. Rookie mistake I guess. However the error is still there, this time with selenium-webdriver:
|
@tkhobbes Good catch, I fixed it: n-studio@545ced3 |
Perfect - works like charm now :) |
Thanks for posting the branch. I tried it out, and it looks like the crawl method works well, but I think you have an issue with the |
Currently unable to use Kimurai with Ruby 3.x. I'm able to use the same code when downgrading the Ruby version to 2.x. Getting the error
wrong number of arguments (given 2, expected 1; required keyword: url) (ArgumentError)
when trying to run the crawl/parse methods. I had issues with rbcat as well. Any plans to add Ruby 3.x support? I think this issue is likely related: #58=== Full error ===
The text was updated successfully, but these errors were encountered: