Recoil issue

So since i cant record a quick video i have to describe the problem.
The recoil issue happens when shooting with a gun (at least for me) when shooting without a target (a player) it randomly shoots the ground or under the crosshair which is weird. idk how to make it more clear but the recoil just behaves how it shouldnt.
Ive noticed this while playing TDM (Team vs Team mode).

experiencing the same problem, any idea / solution?

@SluXzZ @danielkrupinski

Hey any solutions ?


error post install in  cmd reva-chat

hello , i have it error in post all installation
⠼ 🐉 Searching for Ghidra extension...I0000 00:00:1721436171.636379   10688 subchannel.cc:806] subchannel 000002437C2006B0 {address=ipv4:<IP_ADDRESS>:13228, args={grpc.client_channel_factory=0x2437a525390, grpc.default_authority=<IP_ADDRESS>:13228, grpc.internal.channel_credentials=0x2437c2d47f0, grpc.internal.client_channel_call_destination=0x7ffb8e7f64c8, grpc.internal.event_engine=0x2437c2d5530, grpc.internal.security_connector=0x2437a1085a0, grpc.internal.subchannel_pool=0x2437a1abdc0, grpc.primary_user_agent=grpc-python/1.65.1, grpc.resource_quota=0x2437a1ab500, grpc.server_uri=dns:///<IP_ADDRESS>:13228}}: connect failed (UNAVAILABLE:ConnectEx: Connection refused (Unable to retrieve error string -- 10061) {created_time:"2024-07-20T00:42:51.6003684+00:00", grpc_status:14}), backing off for -1035 ms
I0000 00:00:1721436171.646862   17808 subchannel.cc:761] subchannel 000002437C2006B0 {address=ipv4:<IP_ADDRESS>:13228, args={grpc.client_channel_factory=0x2437a525390, grpc.default_authority=<IP_ADDRESS>:13228, grpc.internal.channel_credentials=0x2437c2d47f0, grpc.internal.client_channel_call_destination=0x7ffb8e7f64c8, grpc.internal.event_engine=0x2437c2d5530, grpc.internal.security_connector=0x2437a1085a0, grpc.internal.subchannel_pool=0x2437a1abdc0, grpc.primary_user_agent=grpc-python/1.65.1, grpc.resource_quota=0x2437a1ab500, grpc.server_uri=dns:///<IP_ADDRESS>:13228}}: backoff delay elapsed, reporting IDLE
you have any fast chat? like telegram?

Was the extension running? This is what I would expect if the extension is not running.

Please run with debugging enabled and attach the log as a file. Please be careful not to include your API keys.
reva-chat --debug will run with debugging enabled. You will also find a log file in /tmp/reva-server with more information, be careful, if you are using OpenAI this file can contain your API key.

reva-chat --debug
⠇ 🐉 Searching for Ghidra extension...I0000 00:00:1721483473.409348   12296 subchannel.cc:761] subchannel 0000017F6DA4D0A0 {address=ipv4:<IP_ADDRESS>:13228, args={grpc.client_channel_factory=0x17f6acd2f00, grpc.default_authority=<IP_ADDRESS>:13228, grpc.internal.channel_credentials=0x17f6cb41dc0, grpc.internal.client_channel_call_destination=0x7ffb982964c8, grpc.internal.event_engine=0x17f6da47c00, grpc.internal.security_connector=0x17f6a482c90, grpc.internal.subchannel_pool=0x17f6ac7c450, grpc.primary_user_agent=grpc-python/1.65.1, grpc.resource_quota=0x17f6ac7c490, grpc.server_uri=dns:///<IP_ADDRESS>:13228}}: backoff delay elapsed, reporting IDLE
I0000 00:00:1721483473.553311   17656 subchannel.cc:806] subchannel 0000017F6DA4D410 {address=ipv4:<IP_ADDRESS>:2338, args={grpc.client_channel_factory=0x17f6acd2f00, grpc.default_authority=<IP_ADDRESS>:2338, grpc.internal.channel_credentials=0x17f6cb41dc0, grpc.internal.client_channel_call_destination=0x7ffb982964c8, grpc.internal.event_engine=0x17f6da48400, grpc.internal.security_connector=0x17f6daba360, grpc.internal.subchannel_pool=0x17f6ac7c450, grpc.primary_user_agent=grpc-python/1.65.1, grpc.resource_quota=0x17f6ac7c490, grpc.server_uri=dns:///<IP_ADDRESS>:2338}}: connect failed (UNAVAILABLE:ConnectEx: Connection refused (Unable to retrieve error string -- 10061) {grpc_status:14, created_time:"2024-07-20T13:51:13.5186631+00:00"}), backing off for 523 ms
C:\Users\work\AppData\Local\Temp
2024-07-19 19:21:13,078 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 19:21:13,133 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 19:21:13,133 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 19:21:13,136 - reva-chat - DEBUG - Checking 9 connectable extensions
2024-07-19 19:21:13,136 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 19:21:15,237 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:21:15,237 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-19 19:21:17,358 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:21:17,358 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-19 19:21:19,430 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:21:19,430 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 19:21:21,514 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:21:21,514 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 19:21:23,591 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:21:23,592 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 19:21:23,845 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:21:23,845 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 19:21:25,893 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:21:25,893 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-19 19:21:27,963 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:21:27,963 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 19:21:30,018 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:21:32,110 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:21:34,199 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:21:36,314 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:21:38,412 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:21:40,501 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:21:40,529 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:21:42,592 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:21:44,669 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:21:46,764 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:21:48,840 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:21:50,937 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:21:53,014 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:21:55,114 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:21:57,173 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:21:57,198 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:21:59,333 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:22:01,454 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:22:03,548 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:22:05,628 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:22:07,716 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:22:09,791 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:22:11,866 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:22:13,942 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:22:13,969 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:22:16,056 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:22:18,152 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:22:20,239 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:22:22,360 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:22:24,462 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:22:26,552 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:22:28,629 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:22:30,700 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:22:32,791 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:22:34,877 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:22:36,956 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:22:39,043 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:28:48,810 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 19:28:48,826 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 19:28:48,827 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 19:28:48,827 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 19:28:48,828 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 19:28:50,973 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:28:50,973 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 19:28:53,262 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:28:53,262 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 19:28:53,437 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 19:28:53,438 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 19:28:55,554 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:28:55,554 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 19:28:57,632 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:28:57,632 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 19:28:59,717 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:28:59,717 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 19:29:01,797 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:29:01,797 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-19 19:29:03,882 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:29:03,882 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-19 19:29:05,976 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:29:05,976 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-19 19:29:08,116 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:29:10,213 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:29:12,302 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:29:12,334 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 19:37:19,192 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 19:37:19,206 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 19:37:19,206 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 19:37:19,207 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 19:37:19,207 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 19:37:21,364 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:37:21,365 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 19:37:23,472 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:37:23,472 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 19:37:23,502 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 19:37:23,502 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 19:37:25,601 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:37:25,601 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 19:37:27,718 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:37:27,718 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 19:37:29,836 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:37:29,836 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 19:37:31,942 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:37:31,942 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-19 19:37:34,058 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:37:34,058 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-19 19:37:36,195 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 19:37:36,195 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-19 19:37:38,297 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 19:37:40,426 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:37:42,520 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:37:42,548 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 19:37:44,638 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:40:17,122 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 19:40:17,135 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 19:40:17,135 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 19:40:17,136 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 19:40:17,136 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 19:40:19,305 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 19:40:19,305 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 19:40:21,389 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 19:40:21,389 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 19:40:21,413 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 19:40:21,414 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 19:40:23,554 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 19:40:23,554 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 19:40:25,657 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 19:40:25,657 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 19:40:27,754 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 19:40:27,754 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 19:40:29,873 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 19:40:29,874 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-19 19:40:31,948 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 19:40:31,948 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-19 20:01:20,683 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 20:01:20,695 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 20:01:20,696 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 20:01:20,696 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 20:01:20,697 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 20:01:22,856 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 20:01:22,856 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 20:01:24,989 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 20:01:24,989 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 20:01:25,014 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 20:01:25,014 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 20:01:27,084 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 20:01:27,084 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 20:05:07,262 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 20:05:07,274 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 20:05:07,274 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 20:05:07,276 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 20:05:07,276 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 20:05:09,373 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 20:05:09,373 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 20:05:11,438 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 20:05:11,438 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 20:05:11,463 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 20:05:11,463 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 20:05:13,550 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 20:05:13,550 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 20:05:15,662 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 20:05:15,662 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 20:05:17,762 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 20:05:17,762 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 20:06:49,742 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 20:06:49,759 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 20:06:49,760 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 20:06:49,760 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 20:06:49,761 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 20:06:51,944 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 20:06:51,944 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-19 20:06:54,076 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 20:06:54,076 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 20:06:56,190 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 20:06:56,190 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 20:06:58,281 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 20:06:58,282 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-19 20:07:00,365 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 20:07:00,365 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 20:07:02,498 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 20:07:02,499 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-19 20:07:04,605 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 20:07:04,605 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 20:07:06,714 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 20:07:06,714 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 20:07:08,831 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 20:07:08,831 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 20:07:08,860 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 20:07:10,982 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 20:07:13,061 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 20:07:15,169 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 20:07:17,284 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 20:07:19,385 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 20:07:21,482 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 20:07:23,617 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 20:07:25,693 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 20:07:27,770 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 20:07:27,796 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 20:07:29,884 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 20:07:31,995 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 20:07:34,096 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 20:07:36,183 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 20:07:38,258 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 20:07:40,341 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 20:07:42,469 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 20:07:44,596 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 20:07:46,673 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 20:07:46,698 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 20:07:48,778 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 20:07:50,898 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 20:08:03,264 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 20:08:05,333 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 20:08:07,436 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 21:41:17,880 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 21:41:17,932 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 21:41:17,933 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 21:41:17,933 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 21:41:17,934 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 21:41:20,065 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 21:41:20,065 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 21:41:22,174 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 21:41:22,174 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 21:41:22,201 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 21:41:22,201 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 21:42:49,546 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-19 21:42:49,558 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-19 21:42:49,558 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-19 21:42:49,559 - reva-chat - DEBUG - Checking 10 connectable extensions
2024-07-19 21:42:49,559 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-19 21:42:51,677 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 21:42:51,677 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-19 21:42:53,745 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 21:42:53,745 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-19 21:42:53,771 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 21:42:53,772 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-19 21:42:55,843 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 21:42:55,843 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-19 21:42:58,000 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 21:42:58,000 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-19 21:43:00,106 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 21:43:00,106 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-19 21:43:02,226 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 21:43:02,227 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-19 21:43:04,302 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 21:43:04,302 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-19 21:43:06,389 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 21:43:06,389 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-19 21:43:08,448 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 21:43:10,522 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 21:43:12,640 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 21:43:12,669 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 21:43:14,748 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 21:43:16,882 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 21:43:18,980 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 21:43:21,124 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 21:43:23,230 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 21:43:25,339 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 21:43:27,431 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 21:43:29,552 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 21:43:31,681 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 21:43:31,715 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 21:43:33,825 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 21:43:35,929 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 21:43:38,027 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 21:43:40,122 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 21:43:42,187 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 21:43:44,296 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-19 21:43:46,422 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-19 21:43:48,513 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-19 21:43:50,595 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-19 21:43:50,620 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-19 21:43:52,706 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-19 21:43:54,831 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-19 21:44:28,714 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-19 21:44:30,834 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-19 21:44:32,935 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-19 21:44:37,397 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-20 00:43:00,453 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-20 00:43:00,473 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-6009.connection'), '<IP_ADDRESS>', '6009'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-20 00:43:00,474 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-20 00:43:00,475 - reva-chat - DEBUG - Checking 11 connectable extensions
2024-07-20 00:43:00,475 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-20 00:43:02,638 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-20 00:43:02,638 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-20 00:43:04,728 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-20 00:43:04,729 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-20 00:54:16,268 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-20 00:54:16,284 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-6009.connection'), '<IP_ADDRESS>', '6009'), (WindowsPath('C:/Users/work/.reva/reva-connection-6109.connection'), '<IP_ADDRESS>', '6109'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-20 00:54:16,285 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-20 00:54:16,285 - reva-chat - DEBUG - Checking 12 connectable extensions
2024-07-20 00:54:16,286 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-20 00:54:18,389 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-20 00:54:18,389 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-20 00:54:20,528 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-20 00:54:20,528 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-20 00:54:22,635 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-20 00:54:22,635 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-20 00:54:24,713 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-20 00:54:24,713 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:6109 from C:\Users\work.reva\reva-connection-6109.connection
2024-07-20 00:54:24,879 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:6109. Retrying in 1 second.
2024-07-20 00:54:24,879 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-20 00:54:26,974 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-20 00:54:26,974 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-20 00:54:29,104 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-20 00:54:29,104 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-20 00:54:31,201 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-20 00:54:31,201 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-20 00:54:33,330 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-20 00:54:33,331 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:6009 from C:\Users\work.reva\reva-connection-6009.connection
2024-07-20 00:54:35,443 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:6009. Retrying in 1 second.
2024-07-20 00:54:35,443 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
2024-07-20 00:54:37,589 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-20 00:54:37,589 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7675 from C:\Users\work.reva\reva-connection-7675.connection
2024-07-20 00:54:39,672 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-20 00:54:41,755 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-20 00:54:43,863 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-20 00:54:45,966 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-20 00:54:48,066 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-20 00:54:48,093 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:6109. Retrying in 1 second.
2024-07-20 00:54:50,219 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-20 00:54:52,323 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-20 00:54:54,429 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-20 00:54:56,554 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-20 00:54:58,733 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:6009. Retrying in 1 second.
2024-07-20 00:55:00,856 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1078. Retrying in 1 second.
2024-07-20 00:55:02,964 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7675. Retrying in 1 second.
2024-07-20 10:51:02,973 - reva-chat - INFO - --model was not specified. Selecting default model for ollama: llama3
2024-07-20 10:51:03,041 - reva-chat - DEBUG - Found connection details: [(WindowsPath('C:/Users/work/.reva/reva-connection-1078.connection'), '<IP_ADDRESS>', '1078'), (WindowsPath('C:/Users/work/.reva/reva-connection-12387.connection'), '<IP_ADDRESS>', '12387'), (WindowsPath('C:/Users/work/.reva/reva-connection-13228.connection'), '<IP_ADDRESS>', '13228'), (WindowsPath('C:/Users/work/.reva/reva-connection-1429.connection'), '<IP_ADDRESS>', '1429'), (WindowsPath('C:/Users/work/.reva/reva-connection-2338.connection'), '<IP_ADDRESS>', '2338'), (WindowsPath('C:/Users/work/.reva/reva-connection-6009.connection'), '<IP_ADDRESS>', '6009'), (WindowsPath('C:/Users/work/.reva/reva-connection-6109.connection'), '<IP_ADDRESS>', '6109'), (WindowsPath('C:/Users/work/.reva/reva-connection-7675.connection'), '<IP_ADDRESS>', '7675'), (WindowsPath('C:/Users/work/.reva/reva-connection-7688.connection'), '<IP_ADDRESS>', '7688'), (WindowsPath('C:/Users/work/.reva/reva-connection-7717.connection'), '<IP_ADDRESS>', '7717'), (WindowsPath('C:/Users/work/.reva/reva-connection-7734.connection'), '<IP_ADDRESS>', '7734'), (WindowsPath('C:/Users/work/.reva/reva-connection-7814.connection'), '<IP_ADDRESS>', '7814')]
2024-07-20 10:51:03,042 - asyncio - DEBUG - Using proactor: IocpProactor
2024-07-20 10:51:03,073 - reva-chat - DEBUG - Checking 12 connectable extensions
2024-07-20 10:51:03,127 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:13228 from C:\Users\work.reva\reva-connection-13228.connection
2024-07-20 10:51:05,254 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:13228. Retrying in 1 second.
2024-07-20 10:51:05,255 - asyncio - WARNING - Executing <Task pending name='Task-2' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.125 seconds
2024-07-20 10:51:05,255 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7717 from C:\Users\work.reva\reva-connection-7717.connection
2024-07-20 10:51:07,333 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7717. Retrying in 1 second.
2024-07-20 10:51:07,334 - asyncio - WARNING - Executing <Task pending name='Task-3' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.078 seconds
2024-07-20 10:51:07,334 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:2338 from C:\Users\work.reva\reva-connection-2338.connection
2024-07-20 10:51:09,418 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:2338. Retrying in 1 second.
2024-07-20 10:51:09,419 - asyncio - WARNING - Executing <Task pending name='Task-4' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.094 seconds
2024-07-20 10:51:09,419 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7814 from C:\Users\work.reva\reva-connection-7814.connection
2024-07-20 10:51:11,515 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7814. Retrying in 1 second.
2024-07-20 10:51:11,516 - asyncio - WARNING - Executing <Task pending name='Task-5' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.094 seconds
2024-07-20 10:51:11,516 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:6109 from C:\Users\work.reva\reva-connection-6109.connection
2024-07-20 10:51:13,626 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:6109. Retrying in 1 second.
2024-07-20 10:51:13,627 - asyncio - WARNING - Executing <Task pending name='Task-6' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.109 seconds
2024-07-20 10:51:13,627 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:12387 from C:\Users\work.reva\reva-connection-12387.connection
2024-07-20 10:51:15,738 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:12387. Retrying in 1 second.
2024-07-20 10:51:15,739 - asyncio - WARNING - Executing <Task pending name='Task-7' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.109 seconds
2024-07-20 10:51:15,740 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7688 from C:\Users\work.reva\reva-connection-7688.connection
2024-07-20 10:51:52,454 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7688. Retrying in 1 second.
2024-07-20 10:51:52,455 - asyncio - WARNING - Executing <Task pending name='Task-8' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 36.719 seconds
2024-07-20 10:51:52,455 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1429 from C:\Users\work.reva\reva-connection-1429.connection
2024-07-20 10:51:54,600 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:1429. Retrying in 1 second.
2024-07-20 10:51:54,600 - asyncio - WARNING - Executing <Task pending name='Task-9' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.141 seconds
2024-07-20 10:51:54,600 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:7734 from C:\Users\work.reva\reva-connection-7734.connection
2024-07-20 10:51:56,705 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:7734. Retrying in 1 second.
2024-07-20 10:51:56,706 - asyncio - WARNING - Executing <Task pending name='Task-10' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.109 seconds
2024-07-20 10:51:56,706 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:6009 from C:\Users\work.reva\reva-connection-6009.connection
2024-07-20 10:51:58,879 - reva-chat - WARNING - Failed to connect to <IP_ADDRESS>:6009. Retrying in 1 second.
2024-07-20 10:51:58,880 - asyncio - WARNING - Executing <Task pending name='Task-11' coro=<check_connectivity() running at C:\Users\work\pipx\venvs\reverse-engineering-assistant\Lib\site-packages\reverse_engineering_assistant\chat_client.py:107> wait_for=<Future pending cb=[Task.task_wakeup()] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\base_events.py:449> cb=[as_completed.._on_completion() at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:618] created at C:\Users\work\AppData\Local\Programs\Python\Python312\Lib\asyncio\tasks.py:695> took 2.172 seconds
2024-07-20 10:51:58,880 - reva-chat - DEBUG - Checking connection to <IP_ADDRESS>:1078 from C:\Users\work.reva\reva-connection-1078.connection
I'm using
ghidra_11.1.1_PUBLIC
when starting file > install extension >
https://github.com/cyberkaida/reverse-engineering-assistant/releases/download/v2024-07-11/ghidra_11.1.1_PUBLIC_20240711_ghidra-assistant.zip
reset
after loading ghidra
file configure extension activate reva plugin
still the same error, I think I followed all the steps correctly
I have the api installed too


Localize me

add a button for geolocation

I'm not sure what this PR was for, but I've pulled in a newer version of the map app that includes geolocation. Does that do what you want?

I wish creates a button to locate us directly because once the software launch The location must write if we did not locate in the beginning . after its software scan around us

I think this is already covered in the latest releases. Closing for now, please re-open if it doesn't fix the issue.

Good job
On Sun, Jul 31, 2016, 03:01 Mike Christopher<EMAIL_ADDRESS>wrote:

Closed #343
https://github.com/mchristopher/PokemonGo-DesktopMap/pull/343.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mchristopher/PokemonGo-DesktopMap/pull/343#event-740150255,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP6od3_Bh6-fn6tFtllhsAk6zqcovvdKks5qa_PmgaJpZM4JXCv4
.


Update Unicode database to version 14.0

Thanks for the PR, @cor3ntin changed his repository and generated equivalent change.

Thanks for the library! :)


Some .schema files were not in a schema folder

This results in .schema files showing up in the root of the project, even when people aren't using declarative.
The fix is to put them in .Schemas folder.  This is in .AI.LUIS and .AI.QNA projects

Pull Request Test Coverage Report for Build 86518

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.07%) to 76.484%

Totals

Change from base Build 86287:
-1.07%

Covered Lines:
8066

Relevant Lines:
10546

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


PyConWeb 2017

Fixes #303

Thank you! Could you add the names of the speakers in the JSON files?

@fding253 can you take a look at it? Any fixes/improvements?
For me, it's ready to merge if you see it OK.


Broken link to Node sample code

Currently the documentation in the README links users to
https://github.com/Azure/azure-documentdb-node/tree/master/samples/DocumentDB.Samples.ServerSideScripts
but it's probable that it should link to
https://github.com/Azure/azure-documentdb-node/tree/master/samples/ServerSideScripts

Actually, maybe this shouldn't link to the repo at all? From this README:

Our server-side javascript samples have moved to: https://github.com/Azure/azure-documentdb-js-server/tree/master/samples


#33: add plural handling for SeeAnyOf/SeeAllOf.

Addressing #33.
This PR adds plural (and empty!) handling for SeeAnyOf and SeeAllOf. I thought i'd add some cheek if someone tries to do SeeAnyOf() or SeeAllOf() with no tests. It also adds tests for the describe method, which directly uses the new log_message attribute that handles logging the correct string.

I noticed marcel.shall(SeeAllOf()) will pass but marcel.shall(SeeAnyOf()) will fail.
I would expect these two to be consistent.

I'm going to be touching See/any/all in the Quietly branch, so I can address the inconsistency there.


Feature Request: Changing Storage Location + External Disks

Hello.
I think it would be really beneficial if Aerial allowed to store the downloaded videos in a different location; especially, an external disk.
My computer stands still almost always and it doesn't have a lot of storage space; let alone for 4K videos. Rather than downloading videos into it or keep streaming them so that my bandwidth gets unnecessarily used, it would be much more efficient to store them in an external drive where storage is no issue. Sure, there is caching as well but I really don't want to waste any space when I really have to carefully consider how to manage 256 GBs.
Obviously, in the end, it is the taste of every Aerial user but it is worthwhile to develop such an option.
Plus, as an additional feature to the above, there could be a one single video stored locally on the computer to play continuously if the external drive could not be located so that the user isn't left alone with a black screen.
What do you think?
Best regards.

Hey @cansurmeli
This is possible but only on some operating systems, because of sandboxing restrictions. Anything before Catalina (Mojave etc) you can set your folder as you wish in the cache settings. However on both Catalina and Big Sur, Apple imposed some restrictions on screensaver that made that impossible.
The good news is, they fixed it in Monterey. And Aerial is already updated for that, so that option is available again for users on the macOS beta, and it will be for everyone else this fall.

Hey @glouel
Thanks for the quick answer.
Oh, shoot, I forgot about all of Apple's restrictions for a second. You're right. But it's nice to hear about changes in Monterey! I hope that's not something momentary on Apple's side and makes it into the release.

They added some extra entitlements to the new thing that sandboxes screensaver, so I think it's here to stay. But fingers crossed 🙈


Generate swagger files on sync and manually

@Jason918 @michaeljmarshall how do we currently use swagger files?
I'm going to remove files under the main repo and only generate on sync or manually (on release) in the site repo.
It seems that we generate swagger files for each minor release and I wonder why. (BTW, some site logic depends on restApiVersions.json to resolve real versions so if we want to change the strategy, it can take extra effort.)

I'm going to add a pytool to generate swagger files and move the sources there.

@tisonkun - sorry for the delay. I support moving the generated files to the pulsar-site repo.

how do we currently use swagger files?

Some people use the swagger files to generate clients. This is something that @visortelle has worked on and has contributed fixes to our annotations to make the generated clients work better. Here is a sample third party generated client: https://github.com/tealtools/pulsar-admin-client-js.
Since APIs can change slightly for each minor version, even with things like improved annotations, I personally think it makes sense to generate the swagger files for every release.


proposal: reflect: permit setting struct methods/functions

What version of Go are you using (go version)?
go version go1.11.5 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/docker/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build140522671=/tmp/go-build -gno-record-gcc-switches"

What did you do?
package main

import (
	"fmt"
	"reflect"
)

type Foo struct {
}

func (Foo) Test() int {
	fmt.Println("original")
	return 0
}

func main() {
	mock := func(in []reflect.Value) []reflect.Value {
		fmt.Printf("false")
		return []reflect.Value{reflect.ValueOf(1).Elem()}
	}

	a := reflect.New(reflect.TypeOf(Foo{}))
	fmt.Printf("%v\n", a.Interface().(*Foo).Test())

	fn := a.MethodByName("Test")
	v := reflect.MakeFunc(fn.Type(), mock)

	fmt.Printf("%v\n", fn.CanAddr())
	fmt.Printf("%v\n", fn.CanSet())

	fn.Set(v)

	fmt.Printf("%v\n", a.Interface().(*Foo).Test())
}

https://play.golang.org/p/Onjw6KMe0gv
What did you expect to see?
I would like to propose the ability to set struct functions/methods. I know that #16522 is similar but is not the same, I want to override, and not add.
What did you see instead?
panic: reflect: reflect.Value.Set using unaddressable value

In general the reflect package lets you do the kinds of things you can do in the language directly.  But the language does not permit overriding the methods of an existing type.

My propose on this is create a mocker  library for unit tests like we see in other languages.
An other way to do this is create a dummy struct that is composed by the aimed struct that should be mocked and so add methods/functions in order to override those child methods/functions
whould be awesome if one of these 2 approaches is implemented in the reflect pack.

In general it's not possible to do this to a running binary. Function calls have been inlined and otherwise are scattered all over the program, pre-resolved. There's no way to just jam in a new function in place of an existing one. Reflect is about looking at the program, not modifying it.
You may be interested to look at https://github.com/golang/mock, either to use directly or for inspiration.

Ok thanks, I just made https://github.com/reisraff/mockings if someone is interested.


Wrong Italian translation on Undo create new folder

Issue Type: Translation Bug
Steps to reproduce:

Create new folder with the button in top of File Explorer;
Press Ctrl + Z to Undo the operation;

Result:
The confirm dialog show two "Annulla" buttons. In english we have "Cancel" and "Undo".
Proposal:
Translate "Undo" with "Elimina".
Screenshots:

VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:44.518Z)
OS version: Linux x64 5.4.0-65-generic snap (Elementary OS 5.1.7 Hera)
Extensions (2)

Extension
Author (truncated)
Version

vscode-language-pack-it
MS-
1.53.2

hexeditor
ms-
1.4.0

(1 theme extensions excluded)

Yeah, even when I want to undo a rename it's not really clear.
Undo could also be "ripristina".
I'd keep "annulla" for the "cancel" button instead of "cancella" because the Italian translation means both abort and delete (mostly) so in this case, it could lead this too to confusion.

bug opened 117239

bug 117239 resolved - closing


Fastnlight: Watch cyber[\W_]+constable[\W_]+intelligence

Fastnlight requests the watch of the watch_keyword cyber[\W_]*+constable[\W_]*+intelligence. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

cyber[\W_]*+constable[\W_]*+intelligence has been seen in 3 true positives, 0 false positives, and 0 NAAs.

Approved by Dragonrage in Charcoal HQ


Explicitly add rpath for lib_InternalSwiftSyntaxParser.dylib

Previously, we were relying on SwiftPM adding the toolchain’s stdlib to the rpaths and we were finding lib_InternalSwiftSyntaxParser.dylib inside the stdlib directory. This behavior was removed in apple/swift-package-manager#4208.
Explicitly add the directory that contains lib_InternalSwiftSyntaxParser.dylib as an rpath to SwiftSyntaxParser when compiling SwiftSyntax using build-script.py.
The major downsides of this approach are

You can no longer run SwiftSyntaxParser tests for SwiftSyntax in Xcode with an open source toolchain

Maybe this isn’t too bad because it only affects SwiftSyntaxParser tests and those can be run from the command line

All adopters of SwiftSyntax also need to explicitly specify the lib_InternalSwiftSyntaxParser.dylib rpath

Maybe this isn’t too bad because on Linux lib_InternalSwiftSyntaxParser.dylib is in the standard search paths and on macOS we start shipping lib_InternalSwiftSyntaxParser.dylib as a binary dependency.

@swift-ci Please test

https://github.com/apple/swift-stress-tester/pull/175
@swift-ci Please test

This change made the package un-buildable for users with the following errors

the target 'SwiftSyntax' in product 'SwiftSyntax' contains unsafe build flags

Test manifest
// swift-tools-version:5.5

import PackageDescription

let package = Package(
    name: "SwiftSyntaxProblem",
    products: [
        .executable(
            name: "SwiftSyntaxProblem",
            targets: ["SwiftSyntaxProblem"]
        ),
    ],
    dependencies: [
        .package(
            name: "SwiftSyntax",
            url: "https://github.com/apple/swift-syntax.git",
            .exact("0.50600.0")
        ),
    ],
    targets: [
        .executableTarget(
            name: "SwiftSyntaxProblem",
            dependencies: ["SwiftSyntax"]),
    ]
)

swift-driver version: 1.26.21 Apple Swift version 5.5.2 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)
Target: arm64-apple-macosx12.0

https://bugs.swift.org/browse/SR-15989


v5.1.0 cannot be obtained from the maven repository

That's because it hasn't been released yet.
I've removed the tag to remove confusion, and I've also force pushed to dev so that the unnecessary commits are gone.


Git tab feature

Add Git tab.
Style the links bar to fit new tab, and not overlap when resizing screen.
Add setup instructions to README.

The styling on the "Change Commit Authorship" list item looks strange. It's the only two line list item, and looks like there are two separate items: 'Change Commit' and 'Authorship'. I'm not sure what a better solution would be that would keep the styling consistent, though.


⭐FEAT: Add link to labels on the issue card

Currently, the issue card displays a list of labels for each issue. But, this is just text and doesn't lead to anything.  I think it would be nice if the issue card's labels were links, to the corresponding GitHub label page, for this project.
Example: A label called "hold" could open the page https://github.com/ArslanYM/StarterHive/labels/hold

If it's okay to add this modification, I would like to work on this.

If it's okay to add this modification, I would like to work on this.

Sure thing , assigned to you.


85 - Create test event registry account for Example projects

Current coverage is 96.85% (diff: 100%)

Merging #88 into master will decrease coverage by 0.41%

@@             master        #88   diff @@
==========================================
  Files            25         25
  Lines           954        954
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            928        924     -4
- Misses           26         30     +4
  Partials          0          0

Powered by Codecov. Last update 09ccbb3...50009f2


Add Joe Wagner to Contributors list

@joseph-wagner, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?


Segmentation Fault (core dumped) Issue

System information

I have written custom code
OS Platform and Distribution: CentOS Linux release 7.7.1908 (AltArch), Power9 PC with 4 GPU nodes, 1 login node and 1 compute node and it has little endian architecture
TensorFlow installed from (source or binary): https://public.dhe.ibm.com/ibmdl/export/pub/software/server/ibm-ai/conda/
TensorFlow version (use command below): 2.1.3 (tensorflow-gpu)
Python version:3.6.13
Bazel version (if compiling from source):
python compiler version: GCC 7.3.0
CUDA/cuDNN version:10.2
GPU model and memory: NVIDIA Tesla V100, Total memory: 379140608 kB =379.140608 GB (in one of the node)

I use Supercomputer at our organization for training. I am facing the Segmentation Fault (core dumped) Issue, when I attempt to train a CNN model. The model gets trained for a smaller number of Epochs. Eg if epochs=50 the model runs fine and outputs the trained model file (using callbacks in model.fit). But when epochs are increased, to 75 then segmentation fault occurs at 54th epoch for the same dataset. I ran .py file by submitting it as a job through slurm script. Dataset size is 80,000*5600, around 9GB.
Code
import os
import os.path
import sys

import h5py
import numpy as np
import tensorflow as tf
from tensorflow import keras

def load_file(database_file, load_data=False):
    in_file  = h5py.File(database_file, "r")
    X_train = np.array(in_file['training/data'],dtype=np.int8)
    Y_train = np.array(in_file['training/label'])
    X_test = np.array(in_file['testing/data'], dtype=np.int8)
    Y_test = np.array(in_file['testing/label'])
    if load_data == False:
        return (X_train, Y_train), (X_test, Y_test)
    else:
        return (X_train, Y_train), (X_test, Y_test), (in_file['train/data'], in_file['test/data'])

database = "/home/..../dataset.h5"
trained_model = "/home..../trained_epoch_test.h5"

(X_train, Y_train), (X_test, Y_test) = load_file(database_file)

X_train_scaled = X_train.reshape((X_train.shape[0], X_train.shape[1], 1))
X_test_scaled = X_test.reshape((X_test.shape[0], X_test.shape[1], 1))

y_train_categorical = keras.utils.to_categorical(Y_train, num_classes=256)
y_test_categorical    = keras.utils.to_categorical(Y_test, num_classes=256)

batch_size = 300
epochs = 100

classes=256
input_shape = (5600,1)
img_input = keras.layers.Input(shape=input_shape)

x = keras.layers.Conv1D(64, 11, activation='relu', padding='same', name='block1_conv1')(img_input)
x = keras.layers.AveragePooling1D(2, strides=2, name='block1_pool')(x)

x = keras.layers.Conv1D(128, 11, activation='relu', padding='same', name='block2_conv1')(x)
x = keras.layers.AveragePooling1D(2, strides=2, name='block2_pool')(x)

x = keras.layers.Conv1D(256, 11, activation='relu', padding='same', name='block3_conv1')(x)
x = keras.layers.AveragePooling1D(2, strides=2, name='block3_pool')(x)

x = keras.layers.Conv1D(512, 11, activation='relu', padding='same', name='block4_conv1')(x)
x = keras.layers.AveragePooling1D(2, strides=2, name='block4_pool')(x)

x = keras.layers.Conv1D(512, 11, activation='relu', padding='same', name='block5_conv1')(x)
x = keras.layers.AveragePooling1D(2, strides=2, name='block5_pool')(x)

x = keras.layers.Flatten(name='flatten')(x)
x = keras.layers.Dense(4096, activation='relu', name='fc1')(x)
x = keras.layers.Dense(4096, activation='relu', name='fc2')(x)
x = keras.layers.Dense(classes, activation='softmax', name='predictions')(x)

model = keras.models.Model(img_input, x, name='cnn_best')
optimizer = keras.optimizers.RMSprop(lr=0.00001)
model.compile(loss='categorical_crossentropy', optimizer=optimizer, metrics=['accuracy'])

save_model = keras.callbacks.ModelCheckpoint(trained_model)
callbacks=[save_model]

model.fit(x=X_train_scaled, y=y_train_categorical, batch_size=batch_size, verbose = 1, epochs=epochs, callbacks=callbacks)

Following is the logs generated after enabling fault handler() function:

Slurm Script used to submit the job
#!/bin/bash
#SBATCH --partition=GPU_three
#SBATCH --nodelist=Node_03
#SBATCH --output=output
python3 train.py

Hi @peter-jp! Thanks for reporting this issue. You can reduce reduce the batch size to 30 or 60  and input size to (100,1) to see the difference. You can also use tf.device to force run the entire process in GPU mode.
Please post this issue on keras-team/keras repo. for further assistance.
To know more see;
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999 . Thanks!

I can reduce the batch size but cannot reduce the input size (as it must be equal to the number of columns in the dataset).
In IBM conda, the latest version available for Tensorflow-gpu is 2.1.3, no other versions like TF 2.8 is available for ppcle64 arch.
I will use tf.device and will update the result.

@peter-jp ! Did it get resolved in GPU mode in 2.8 version?

There is no TF2.8 version for PPCLE64 architecture. I use the following channel for installing packages
conda config --prepend channels
https://public.dhe.ibm.com/ibmdl/export/pub/software/server/ibm-ai/conda/

Hi @chunduriv ! Could you please look at this issue?

yes sure

Thanks for opening this issue. Development of keras moved to separate repository https://github.com/keras-team/keras/issues
Please post this issue on keras-team/keras repo.
To know more see;
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999
Thank you!

@mohantym I tried with 30 as batch size for 400 epochs but it also resulted in segmentation fault at 130th epoch.
Following is the result of enabling fault handler
Current thread 0x0000200000044cd0 (most recent call first):
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/h5py/_hl/files.py", line 443 in close
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/saving/hdf5_format.py", line 120 in save_model_to_hdf5
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/saving/save.py", line 112 in save_model
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/network.py", line 1011 in save
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/callbacks.py", line 1040 in _save_model
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/callbacks.py", line 992 in on_epoch_end
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/callbacks.py", line 302 in on_epoch_end
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_v2.py", line 771 in on_epoch
File "/home/peter/.conda/envs/peter_env/lib/python3.6/contextlib.py", line 88 in exit
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_v2.py", line 397 in fit
File "/home/peter/.conda/envs/peter_env/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training.py", line 819 in fit
File "/home/peter/analysis/for_Training_gpu.py", line 100 in
/var/spool/slurm/d/job03321/slurm_script: line 8:  3921 Segmentation fault      (core dumped) python3 ~/analysis/for_Training_gpu.py

Hi, Could you please refer this comment and post the issue in Keras repo for faster resolution. Thanks!

Thanks for opening this issue. Development of keras moved to separate repository https://github.com/keras-team/keras/issues
Please post this issue on keras-team/keras repo. To know more see; https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999 Thank you!


Feature Request: Generate tests with jasmine.pending()

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

@angular/cli: 1.1.1
node: 7.10.0
os: darwin x64
@angular/animations: 4.2.2
@angular/common: 4.2.2
@angular/compiler: 4.2.2
@angular/core: 4.2.2
@angular/flex-layout: 2.0.0-rc.1
@angular/forms: 4.2.2
@angular/http: 4.2.2
@angular/material: 2.0.0-beta.6
@angular/platform-browser: 4.2.2
@angular/platform-browser-dynamic: 4.2.2
@angular/router: 4.2.2
@angular/cli: 1.1.1
@angular/compiler-cli: 4.2.2
@angular/language-service: 4.2.2

Repro steps.

ng g c componentName
The log given by the failure.

(no logs)
Desired functionality.

Instead of generating a test that only passes:
it('should be created', () => {
    expect(component).toBeTruthy();
});

We could write a test that indicates is pending. Something like so:
it('pending...should be created', () => {
    expect(component).toBeTruthy();
    pending();
});

or just add a new spec, like so:
it('pending...write tests', () => {
    pending();
});

Mention any other details that might be useful.

More about the pending method: https://jasmine.github.io/2.0/introduction.html#section-Pending_Specs

My suggestion is to avoid cases when the developer uses the generator from angular-cli, but doesn't re-write the test when it should.

I'm curious what others have to say, this is interesting. I was not aware of the pending function.

👍  I quite like this as the tests generated by the CLI, while they will pass, generally aren't really testing anything.
Marking them as pending() or xit by default lets developers know that they haven't actually implemented tests for the generated items yet.

It's possible to fork the existing schematics and customize them according to your use case. Let us keep this outside the scope of the CLI for now.
Please feel free to open a new issue in case I'm missing something.


[Feature] Ability to toggle sequential nodePool rolling

What
Ability to toggle in your cluster.yaml  file at a nodePool: or worker: level whether nodePools are going to be rolled out / rolled in sequentially or concurrently
Why
After doing a fair share of rolls, it was noticed that at times, platforms are more resilient to a full Availability Zone going down rather than having 1 nodePool going down in each respective Availability Zone. Since sometimes it is needed to roll out nodePools in sequential order, it would be easier to have it as a toggleable option in your cluster.yaml.
This should allow for easier switching between rolling out workers sequentially or concurrently.
How

In the root stack-template, I made it so that when we loop through our currently declared nodePools we store their index. In the DependsOn field, I have added control flow to check if the current nodePool  has sequentialRoll enabled, and if it does, the previous nodePool is added as a dependency.

To toggle sequentialRoll globally, I have added the sequentialRoll field in the Worker struct. When the config is read from a file, if the sequentialRoll field is enabled at a Worker level, then it overwrites all values of sequentialRoll false at a nodePool level, setting them to true. This ensures that if declared at a global level, then all of the nodePools are going to be rolled out sequentially. If that is not the desired behaviour, simply set the targeted nodePools to roll out sequentially on an individual basis.

The TemplateParams NodePools function now returns a slice of nodePool instead of a slice of NestedStack interfaces, this was done in order to be able to use the sequentialRoll flags in the stack-template.

Notes

I tested this in cluster with 2 sets of nodePools (3 nodePools per set), one concurrent and one sequential, across 3 different AZs and it worked perfectly. There is a caveat, however, if there are nodePools being rolled out sequentially and concurrently, the nodePools declared sequentially will have to be declared before the concurrent ones, otherwise the first declared sequential nodePool will dependend on the last declared concurrent nodePool.

If nodePools are to be rolled sequentially, they will roll out in order of declaration in your cluster.yaml (unsure if I specified that anywhere) e.g if you have A, B, C declared in that order, thats the order they will also roll out in.

Codecov Report

Merging #1428 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1428   +/-   ##
=======================================
  Coverage   37.57%   37.57%
=======================================
  Files          74       74
  Lines        4546     4546
=======================================
  Hits         1708     1708
  Misses       2603     2603
  Partials      235      235

Impacted Files
Coverage Δ

model/node_pool_config.go
20.58% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2dea8dd...dc45611. Read the comment docs.

@Matei207 Hey! Thanks a lot for your work. You seem to have interesting use-cases.
Just for clarification,

platforms are more resilient to a full Availability Zone going down rather than having 1 nodePool going down in each respective Availability Zone

Regarding your use-case, I wondered if what you would like the most is something like nodePoolRollingStrategy: BatchPerAvailabilityZone. It is an imaginary rolling strategy, which will basically group up node pools per az, and adds corresponding DependsOn to ASGs.

I think that the essence of this change is rather simpler than it sounds - that is "sometimes a customer will prefer to roll out updates one node at a time irrespective of AZ's".  The default strategy of nodepools in parallel is good for most customers, but it is useful to be able to change the behaviour on clusters where less unavailable nodes are desired.
I don't think this sounds like 'BatchPerAvailabilityZone' but more like: -
nodePoolRollingStrategy: Parallel
nodePoolRollingStrategy: Sequential
I don't have an issue with this being a boolean, but it could changed to something like above.
An added complication is that this PR also allows for the sequential strategy to be applied to specific nodepools, so some pools can roll using the parallel strategy and others can be set for sequential rolling.  This seems like it could be useful for some users/teams.

I quite like the idea of changing it to nodePoolRollingStrategy: and have it default to "Parallel". I think that would be more self-explanatory and easier to use in your cluster.yaml.
Also, @davidmccormick  is right regarding the use-case. In this particular case, the issue we faced is with one of our internal teams and their usage of Kafka. Whenever the cluster is rolled out, it is more desirable for us to have a full AZ going down (by rolling the nodePools in sequential order). If the nodePools are rolled in parallel, then we risk data loss in our Kafka queue because we could have multiple replicas of the same queue that can go down at the same time across multiple AZs. Inside the AZ, the team in question told us that it is ok to increase the maxBatchSize so we can upgrade multiple workers at the same time in that AZ.

Update:

Based on the previous comments, I have now updated the branch/PR to reflect the suggestions.

The structs were all updated to now have a nodePoolRollingStrategy field of type string. My assumption is that at this stage it will either be Parallel or Sequential.

In the ConfigFromBytes method I have changed the initialisation/control flow of the nodePoolRollingStrategy (previously sequentialRoll). As before, if there is no explicit value passed in your cluster.yaml file, the nodePool will inherit whatever value was declared in Worker (which should act as a global value). In case Worker does not have a value either, we default to Parallel to keep the default behaviour.

Since the sequentialRoll field was changed to nodePoolRollingStrategy, at a Worker level, the globalSequentialRoll field was also removed. I have chosen not to prepend a "global" prefix to the worker-level field, I think that would make it a bit more confusing.

The functionality/behaviour should be the same as before. I think this looks a lot cleaner so thank you for the suggestions! Hopefully, this will make the PR better, waiting to hear some more feedback.
e.g cluster.yaml
worker:
nodePoolRollingStrategy: Parallel
  nodePools:
     - &my-data-nodepool
       name: my-data-nodepool-a
       nodePoolRollingStrategy: Sequential

Update

I've made some changes to the cluster.yaml template as requested, and have also added in tests.
For the cluster.yaml file:

Removed the following from the documentation at both Worker and nodePool level:

"across all availability zones"

Hopefully it is a bit more intuitive now and will avoid any confusions :) If there is anything else that I should change regarding the docs, do let me know.
Tests:
I was unsure of how to proceed with the tests, so I followed the format in the file.

There are now three test functions: hasDefaultNodePoolRollingStrategy, hasSpecificNodePoolRollingStrategy and hasNodePoolAndWorkerStrategy.  The first function tests if a nodePool has the roll-out strategy set to parallel by default (with no explicit declarations in the cluster.yaml file whatsoever). The other two assert if the expected roll-out strategy equals the actual roll-out strategy specified in the cluster.yaml file.

The three test functions form the basis for four test cases that I came up with (if there are any more cases that I haven't considered do let me know and I will add them in!): testing for default values at a nodePool level, testing if the strategy is set at a worker level and then inherited by a nodePool, testing for a specific roll-out strategy, and finally, a test case that has two nodePool groups with inherited and explicit declarations. The tests all passed and hopefully they will add value to the overall test class.

Again, I am quite unsure if the tests cover enough and if they follow the format, if there is anything that should be changed, do let me know.

@mumoshu  regarding the following question:

@Matei207 Thanks for the clarification on your use-case! The kafka thing made sense to me. Out of curiosity, does it relate to how repartitioning and/or rebalancing works?

According to one of the guys that works with Kafka, "rebalance/repartition are admin tasks that should run when scaling the cluster up, but not when rolling the cluster".  I don't really know the details on how they do the rebalance/reparation right now, but I don't think it relates much to this particular use-case as I believe their kafka brokers are doing neither (rebalance/repartition) when they're evicted as part of the nodeDrain before a worker is killed and replaced.
To offer a bit more background on the issue, one of the teams we support run a kafka cluster of 66 brokers split over 3 AZ's in a single AWS region. Those brokers support 72 topics split over 812 partitions, with each partition replicated 3 times, so 2436 total replicas. I think because the kafka cluster is so big, rebalancing/repartioning takes a while so it wouldn't be done on every cluster roll/node upgrade.