Closed csxuyang closed 3 months ago
Hi, that code was just removed after pushing the legacy changes. It will no longer throw an error, the version of the script that should run is "1.0.3.L"
Downside: This "legacy" code has not been tested and it does not check the extension page anymore, status is based on Dashboard data and confirms if there is ANY working node. Old chromedriver headless mode does not provide a way to access the extension page :(
The :latest works absolutely fine. Just re-capture your cookie and re-deploy the container.
for most cases the :latest
tag is working, but some systems seem to fail to compile to the new chromedriver headless mode, so I tagged a build with it (:legacy
). I have not tested it and I don't really like the fact that it can not browse to the extension pages :(
Difference between latest
and legacy
:
https://github.com/Kellphy/Nodepay/compare/main...legacy
Thank you. I am still yet to test the :legacy on my old Synology... :)
Hi, that code was just removed after pushing the legacy changes. It will no longer throw an error, the version of the script that should run is "1.0.3.L"
Downside: This "legacy" code has not been tested and it does not check the extension page anymore, status is based on Dashboard data and confirms if there is ANY working node. Old chromedriver headless mode does not provide a way to access the extension page :(
I got the old version.The log show is "Starting the script 1.0.2..."
Hi, that code was just removed after pushing the legacy changes. It will no longer throw an error, the version of the script that should run is "1.0.3.L" Downside: This "legacy" code has not been tested and it does not check the extension page anymore, status is based on Dashboard data and confirms if there is ANY working node. Old chromedriver headless mode does not provide a way to access the extension page :(
I got the old version.The log show is "Starting the script 1.0.2..."
I found the new branch legacy
Run lagecy version , Logged in successfully then disconnected after 10s , why ?
2024-06-25 15:13:38,499 - INFO - Starting the script 1.0.3.L...
2024-06-25 15:13:39,919 - INFO - Navigating to https://app.nodepay.ai/ website...
2024-06-25 15:13:41,063 - INFO - Added cookie with value eyJhbGci...wOmYR9_Q to local storage.
2024-06-25 15:13:51,465 - INFO - Refreshing page to check login information...
2024-06-25 15:13:55,265 - INFO - Logged in successfully!
2024-06-25 15:14:05,405 - WARNING - Status: Disonnected!
Using the legacy version as seems the main branch won't work. Although the below doesn't exactly seem to be running quite stable.
It's also hard to debug what's the exact problem.
2024-06-25 04:16:52,251 - INFO - Starting the script 1.0.3.L...
2024-06-25 04:17:03,762 - INFO - Navigating to https://app.nodepay.ai/ website...
2024-06-25 04:17:15,564 - INFO - Added cookie with value eyJhbGci...8-M-z49w to local storage.
2024-06-25 04:17:30,257 - INFO - Refreshing page to check login information...
2024-06-25 04:17:49,954 - INFO - Refreshing page to check login information...
2024-06-25 04:18:10,750 - INFO - Refreshing page to check login information...
2024-06-25 04:18:34,752 - INFO - Refreshing page to check login information...
2024-06-25 04:18:55,050 - INFO - Refreshing page to check login information...
2024-06-25 04:19:11,854 - INFO - Refreshing page to check login information...
2024-06-25 05:15:03,056 - INFO - Refreshing page to check login information...
.
.
.
2024-06-25 05:17:58,657 - INFO - Refreshing page to check login information...
2024-06-25 05:18:22,351 - INFO - Refreshing page to check login information...
2024-06-25 05:19:01,554 - INFO - Logged in successfully!
2024-06-25 05:19:12,564 - WARNING - Status: Disonnected!
2024-06-25 05:29:45,156 - WARNING - Status: Unknown!
2024-06-25 05:40:25,956 - WARNING - Status: Unknown!
2024-06-25 05:50:57,353 - WARNING - Status: Disonnected!
2024-06-25 06:01:40,956 - WARNING - Status: Disonnected!
2024-06-25 06:12:18,655 - WARNING - Status: Disonnected!
2024-06-25 06:22:59,254 - WARNING - Status: Disonnected!
2024-06-25 06:33:36,551 - WARNING - Status: Unknown!
2024-06-25 06:44:10,650 - WARNING - Status: Unknown!
2024-06-25 06:54:48,154 - WARNING - Status: Unknown!
2024-06-25 07:05:24,355 - WARNING - Status: Unknown!
2024-06-25 07:16:03,655 - WARNING - Status: Unknown!
2024-06-25 07:26:36,754 - WARNING - Status: Unknown!
2024-06-25 07:37:14,251 - WARNING - Status: Unknown!
2024-06-25 07:47:50,653 - WARNING - Status: Unknown!
2024-06-25 07:58:31,150 - WARNING - Status: Unknown!
2024-06-25 08:09:10,054 - WARNING - Status: Disonnected!
2024-06-25 08:19:40,053 - WARNING - Status: Unknown!
the same error : 2024-06-25 06:02:15,275 - INFO - Starting the script 1.0.3.L... 2024-06-25 06:02:16,884 - INFO - Navigating to https://app.nodepay.ai/ website... 2024-06-25 06:02:20,005 - INFO - Added cookie with value eyJhbGci...9uHcFurw to local storage. 2024-06-25 06:02:30,261 - INFO - Refreshing page to check login information... 2024-06-25 06:02:37,629 - INFO - Logged in successfully! 2024-06-25 06:02:42,049 - INFO - Status: Connected! 2024-06-25 06:12:52,813 - INFO - Status: Connected! 2024-06-25 06:23:15,156 - WARNING - Status: Unknown! 2024-06-25 06:33:27,728 - INFO - Status: Connected! 2024-06-25 06:43:50,449 - WARNING - Status: Unknown! 2024-06-25 06:54:12,764 - WARNING - Status: Unknown! 2024-06-25 07:01:54,910 - INFO - Starting the script 1.0.3.L... 2024-06-25 07:01:56,576 - INFO - Navigating to https://app.nodepay.ai/ website... 2024-06-25 07:02:00,035 - INFO - Added cookie with value eyJhbGci...9uHcFurw to local storage. 2024-06-25 07:02:10,173 - INFO - Refreshing page to check login information... 2024-06-25 07:02:18,484 - INFO - Logged in successfully! 2024-06-25 07:02:24,610 - INFO - Status: Connected! 2024-06-25 07:12:47,103 - WARNING - Status: Unknown! 2024-06-25 07:23:09,551 - WARNING - Status: Unknown! 2024-06-25 07:33:32,105 - WARNING - Status: Unknown! 2024-06-25 07:43:54,397 - WARNING - Status: Unknown! 2024-06-25 07:54:16,969 - WARNING - Status: Unknown! 2024-06-25 08:02:56,587 - INFO - Starting the script 1.0.3.L... 2024-06-25 08:02:58,212 - INFO - Navigating to https://app.nodepay.ai/ website... 2024-06-25 08:03:02,024 - INFO - Added cookie with value eyJhbGci...9uHcFurw to local storage. 2024-06-25 08:03:12,079 - INFO - Refreshing page to check login information... 2024-06-25 08:03:22,488 - INFO - Logged in successfully! 2024-06-25 08:03:27,899 - INFO - Status: Connected! 2024-06-25 08:13:50,326 - WARNING - Status: Unknown! 2024-06-25 08:24:03,737 - WARNING - Status: Disonnected! 2024-06-25 08:34:25,879 - WARNING - Status: Unknown!
From what I've read here, running the old headless mode, would also make web extensions unavailable. I will take a look, maybe there is a way to keep get the new chromedriver run on a machine that fails it .. unfortunately I have 3 machines and it does not fail on either, so I will base my tests on what I can find :)
I will use the legacy branch for testing.
Resource: https://www.selenium.dev/blog/2023/headless-is-going-away/
Ok, so, I reverted the changes made in legacy, since the old headless mode does not support extensions. I added logs for the chromedriver version just before it breaks. This means that it will still fail, but at least, if the version is the problem, maybe I could force it to get a newer one ... I do not have any device that fails to build the chromedriver, so let's see what you guys get.
Script version should be 1.0.5
Ex: My Logs
2024-06-28T11:46:34.537887455Z 2024-06-28 11:46:34,537 - INFO - Starting the script 1.0.5...
2024-06-28T11:46:34.562455877Z 2024-06-28 11:46:34,562 - INFO - Using ChromeDriver 126.0.6478.114 (044c187ce79bb8a266c5016ce749387a3480f81f-refs/branch-heads/6478@{#1524})
2024-06-28T11:46:37.249797894Z 2024-06-28 11:46:37,249 - INFO - Navigating to https://app.nodepay.ai/ website...
2024-06-28T11:46:43.081252263Z 2024-06-28 11:46:43,080 - INFO - Added cookie with value ebJchGui...h1DCscXB to local storage.
2024-06-28T11:46:53.555301696Z 2024-06-28 11:46:53,554 - INFO - Refreshing page to check login information...
2024-06-28T11:47:06.063373785Z 2024-06-28 11:47:06,062 - INFO - Logged in successfully!
2024-06-28T11:47:06.064055111Z 2024-06-28 11:47:06,063 - INFO - Accessing extension settings page...
2024-06-28T11:47:17.620123715Z 2024-06-28 11:47:17,619 - INFO - Extension is activated!
2024-06-28T11:47:19.543405288Z 2024-06-28 11:47:19,543 - INFO - Status: Connected!
ℹ️ docker image tag: latest
2024-07-01 08:50:50,821 - INFO - Starting the script 1.0.5...
2024-07-01 08:50:50,978 - INFO - Using ChromeDriver 126.0.6478.114 (044c187ce79bb8a266c5016ce749387a3480f81f-refs/branch-heads/6478@{#1524})
2024-07-01 08:51:15,576 - INFO - Navigating to https://app.nodepay.ai/ website...
2024-07-01 08:52:34,377 - INFO - Added cookie with value eyJhbGci...8-M-z49w to local storage.
2024-07-01 08:52:44,475 - INFO - Refreshing page to check login information...
2024-07-01 08:53:34,479 - INFO - Refreshing page to check login information...
2024-07-01 08:54:03,775 - INFO - Refreshing page to check login information...
2024-07-01 08:54:30,888 - INFO - Refreshing page to check login information...
2024-07-01 08:55:03,480 - INFO - Refreshing page to check login information...
2024-07-01 08:55:25,983 - INFO - Refreshing page to check login information...
2024-07-01 08:55:47,876 - INFO - Refreshing page to check login information...
2024-07-01 08:56:09,180 - INFO - Refreshing page to check login information...
2024-07-01 08:56:31,275 - INFO - Refreshing page to check login information...
2024-07-01 08:56:35,078 - ERROR - An error occurred: Message: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: chrome=126.0.6478.114)
Stacktrace:
#0 0x0055926faeac <unknown>
#1 0x00559241649c <unknown>
#2 0x005592404f48 <unknown>
#3 0x005592404868 <unknown>
#4 0x0055924041f0 <unknown>
#5 0x0055924040d0 <unknown>
#6 0x00559240276c <unknown>
#7 0x005592402c0c <unknown>
#8 0x00559240f8b0 <unknown>
#9 0x0055924203fc <unknown>
#10 0x0055924031a0 <unknown>
#11 0x00559242009c <unknown>
#12 0x005592492c90 <unknown>
#13 0x00559244a48c <unknown>
#14 0x00559244b054 <unknown>
#15 0x0055926c9f60 <unknown>
#16 0x0055926ccff0 <unknown>
#17 0x0055926ccbc8 <unknown>
#18 0x0055926bad4c <unknown>
#19 0x0055926cd660 <unknown>
#20 0x0055926a4d84 <unknown>
#21 0x0055926eb0e8 <unknown>
#22 0x0055926eb2f0 <unknown>
#23 0x0055926fa37c <unknown>
#24 0x007f9b99ee58 <unknown>
#25 0x007f9ba07f9c <unknown>
2024-07-01 08:56:35,080 - ERROR - Restarting in 60 seconds...
I think it would be best to merge both legacy
and main
branch together. Have your logic try the main
logic first then failback to legacy
if it crashes or is unsuccessful. This is useful when using compose files and rather than always having to switch tags. So it's wise to have review how you handle these exceptions more intelligently.
I can re-write this myself using JS instead of slow selenium but I don't want to be a maintainer since you already have something that's "kind of" working when it does with only those few hiccups.
Hi,I run the new code,but melt some errors: 2024-06-24 07:42:16,107 - ERROR - Error waiting for element //*[text()='Activated']: Message: Stacktrace:
0 0x558f2aacd8ae
1 0x558f2a79ec57
2 0x558f2a7e4f27
3 0x558f2a7e5001
4 0x558f2a827a84
5 0x558f2a808b3d
6 0x558f2a825920
7 0x558f2a808893
8 0x558f2a7d92ed
9 0x558f2a7da092
10 0x558f2aa9d256
11 0x558f2aaa05f9
12 0x558f2aaa00bf
13 0x558f2aaa0a75
14 0x558f2aa8d79f
15 0x558f2aaa0dc0
16 0x558f2aa766c6
17 0x558f2aabdfb5
18 0x558f2aabe1a2
19 0x558f2aaccd9a
20 0x7f2471cc7134