Closed GrandDuke1106 closed 1 year ago
There is no more output
Please try connecting to port 5000 of the host running the game-abstract-crawler via HTTP. Detailed logs should be displayed, so could you check what kind of errors are occurring?
Here it is
I am currently encountering this exact same issue.
Try to use version 4.2.0 selenium. The usage of MoveToElementOffsetOrigin was changed in 4.3 version. https://github.com/SeleniumHQ/selenium/commit/cb68cf53b2306a4e5d524e789442c0df4f3deda9
@xzdlj Thank you very much. It works!
But now there is a new problem. Can you help me
@xzdlj Thank you very much. It works!
But now there is a new problem. Can you help me
Please post the Screenshots from the monitor webpage.
@xzdlj Thank you very much. Here are Screenshots
I feel that the program may not be able to read the verification code in s3.
I feel that the program may not be able to read the verification code in s3.
I agree with you.
Try to restart the crawler container and then check whether there is the verification email in s3 bucket.(Restart may work somehow) If you find the email in the right place, change the logging level in config.yaml to DEBUG for more information. Otherwise, check your s3 configuration.
@xzdlj I analyzed the log and found that the verification code could not be obtained because the sender of the email could not be matched.
On line 69 of the mahjongsoul_sniffer/mahjongsoul_sniffer /yostar_login.py
file, I changed passport@mail.yostar.co.jp
to info@passport.yostar.co.jp
. After this, I was able to log in successfully.
Thanks for your help.
This issue has been solved.
As pointed out by xzdlj in the comment https://github.com/Cryolite/mahjongsoul_sniffer/issues/88#issuecomment-1667129999, the API specifications have changed in Selenium 4.3. I committed the change addressing this issue to develop
branch, which will soon be merged into master
branch. If using Selenium 4.2 or earlier, revert the change made by the commit https://github.com/Cryolite/mahjongsoul_sniffer/commit/960bc0043d04b36b21e4fd5cf73cbfd63666ca0b.
As pointed out by xzdlj in the comment #88 (comment), the API specifications have changed in Selenium 4.3. I committed the change addressing this issue to
develop
branch, which will soon be merged intomaster
branch. If using Selenium 4.2 or earlier, revert the change made by the commit 960bc00.
Thank you for your update
I followed the instructions to run docker. And I set the mitmproxy version to 7.0.3 to avoid the "Descriptors cannot not be created directly." error.
Although docker ran successfully in the end, there were no more records in s3.