LtCMDstone / MS-Rewards-Farmer-Docker

Dockerized bot for MS-Rewards
16 stars 6 forks source link

Chrome Version #6

Closed Wob76 closed 5 months ago

Wob76 commented 5 months ago

Hi, First, thanks for the for the repo.

I think Chrome needs a version bump, as of a few days ago I am getting the following error and it is no longer working.

2024-04-26 05:29:52,045 [WARNING] Error occurred: Message: unknown error: cannot connect to chrome at 127.0.0.1:41799 from session not created: This version of ChromeDriver only supports Chrome version 124 Current browser version is 123.0.6312.58

Thanks

rakosi2 commented 5 months ago

I am also getting this error. @LtCMDstone, can you please rerun the Action to update Chrome to at least 124.

Wob76 commented 5 months ago

I did a fork so I could run my own build, for some reason I couldn't work out, I had errors related to blinker, even when using Chrome 123.

After some testing I worked out if I kept blinker to v1.7.0 it works, so I added a pip install for that prior to the requirements.txt call (it installs v1.8.1 by default as part of the dependences).

@rakosi2 if you want, while you wait for @LtCMDstone to update, you can try the package from my fork that is working with Chrome 124.

ghcr.io/wob76/ms-rewards-farmer-docker:latest

LtCMDstone commented 5 months ago

Hey, I'm sorry, was on vacation. Version 124 is ready now :-)

Wob76 commented 5 months ago

Hey, I'm sorry, was on vacation. Version 124 is ready now :-)

No Drama... Thanks...

Out of interest, any idea on why my build would have errors related to blinker 1.8.1 but yours seems to build fine?

I just forked your repo and then configured the token, I haven't used the actions in GitHub so I might have missed something but just thought it was odd.

rakosi2 commented 5 months ago

I am also getting that error with @LtCMDstone's repo image

LtCMDstone commented 5 months ago

Hmm good question, it seema to be related to the bots python packages, since the bot will start. I only built the docker "wrapper". Needs some investigation why out of sudden the package is missing

Wob76 commented 5 months ago

Ah ok, if it is happening to your repo then I am less confused :)

It doesn't specify blinker in the requirements but it must be a pre-req for one of the requirements. By default it pulls 1.8.1, 1.7.0 doesn't have the error (1.8.0 still does). 1.7.0 meets the check so it doesn't force an update.

That said, something else has changed, as looking at your 123 package, it also pulled 1.8.1 blinker, so there must be some conflict that has caused the error.

You can look at my fork, but all I did was just before the RUN pip for the requirements.txt I added RUN pip install --root-user-action=ignore blinker==1.7.0

rakosi2 commented 5 months ago

That said, something else has changed, as looking at your 123 package, it also pulled 1.8.1 blinker, so there must be some conflict that has caused the error.

The previous action was also 1.7.0. Sounds like this should be changed in @klept0's repo to limit the version to 1.7.0

Wob76 commented 5 months ago

I stand corrected, I thought I checked that but I can see now that the 123 run is pulling 1.7.0.

It appears that 1.8.0 and 1.8.1 are new both released in the last week.

https://pypi.org/project/blinker/#history

Wob76 commented 5 months ago

FYI Blinker has been locked to a version in the requirements.txt over on @klept0's repo.

https://github.com/klept0/MS-Rewards-Farmer/commit/6a72ffa7797063ad14dcfbfc98dabba57f35075a

LtCMDstone commented 5 months ago

Ah perfect 😁