Unclosed client session

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Microsoft Windows 10 Pro Education 10.0.19045 N/A Build 19045
- Continue: v0.5.0
- VSCode: 1.84.1

Description
Unclosed Client Session,
Logs:--------------------------------------------
INFO:     Started server process [6120]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:65432 (Press CTRL+C to quit)
INFO:     ('<IP_ADDRESS>', 51501) - "WebSocket /socket.io/?window_id=66cc1fdd-f5d0-41e0-b890-ab8c64b2aa5a&EIO=4&transport=websocket" [accepted]
INFO:     connection open
[2023-11-09 14:37:14] [DEBUG] Starting MeiliSearch...
[2023-11-09 14:37:14] [INFO] Meilisearch started at http://localhost:7700
INFO:     ('<IP_ADDRESS>', 51507) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%2266cc1fdd-f5d0-41e0-b890-ab8c64b2aa5a%22%2C%22workspace_directory%22%3A%22d%3A%5C%5CYaz%C4%B1l%C4%B1m%5C%5CWEBS%C4%B0TELER%C4%B0%5C%5CCMHLIFESTYLE%5C%5Cpublic_html%22%2C%22unique_id%22%3A%22f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
INFO:     ('<IP_ADDRESS>', 51515) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%2278720a26-786e-4a0d-b663-1dbd009277b5%22%2C%22workspace_directory%22%3A%22d%3A%5C%5CYaz%C4%B1l%C4%B1m%5C%5CWEBS%C4%B0TELER%C4%B0%5C%5CCMHLIFESTYLE%5C%5Capi%22%2C%22unique_id%22%3A%22f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 51516) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%2266cc1fdd-f5d0-41e0-b890-ab8c64b2aa5a%22%2C%22workspace_directory%22%3A%22d%3A%5C%5CYaz%C4%B1l%C4%B1m%5C%5CWEBS%C4%B0TELER%C4%B0%5C%5CCMHLIFESTYLE%5C%5Cpublic_html%22%2C%22unique_id%22%3A%22f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6846B90>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6846E50>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6846B90>
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 51523) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%2266cc1fdd-f5d0-41e0-b890-ab8c64b2aa5a%22%2C%22workspace_directory%22%3A%22d%3A%5C%5CYaz%C4%B1l%C4%B1m%5C%5CWEBS%C4%B0TELER%C4%B0%5C%5CCMHLIFESTYLE%5C%5Cpublic_html%22%2C%22unique_id%22%3A%22f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F68462D0>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F68465D0>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6844C90>
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 51530) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%2266cc1fdd-f5d0-41e0-b890-ab8c64b2aa5a%22%2C%22workspace_directory%22%3A%22d%3A%5C%5CYaz%C4%B1l%C4%B1m%5C%5CWEBS%C4%B0TELER%C4%B0%5C%5CCMHLIFESTYLE%5C%5Cpublic_html%22%2C%22unique_id%22%3A%22f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F688AC90>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F688B050>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F688BC90>
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 51538) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%2266cc1fdd-f5d0-41e0-b890-ab8c64b2aa5a%22%2C%22workspace_directory%22%3A%22d%3A%5C%5CYaz%C4%B1l%C4%B1m%5C%5CWEBS%C4%B0TELER%C4%B0%5C%5CCMHLIFESTYLE%5C%5Cpublic_html%22%2C%22unique_id%22%3A%22f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6891490>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6890B90>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000227F6892850>
INFO:     Shutting down /* here shutdown is made by me to break infinite loop */
INFO:     connection closed
INFO:     connection closed
INFO:     connection closed
INFO:     Finished server process [6120]
[2023-11-09 14:37:36] [DEBUG] ------ End logs ------
To reproduce
This only occurs from time to time, the service working on port7700 shuts down while im working, i dont notice it, then when i try to reboot, this cycle of connection open/closed starts.
haven't found a way to reproduce yet,
after searching with netstat -ano | findstr 7700;
there are no services found on port 7700.
Log output
9.108 seconds

[2023-11-09 14:13:50] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:13:50] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:13:50] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:13:53] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:13:53] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:13:57] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:02] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:14:02] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:14:15] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:15] [INFO] Loaded Meilisearch index in 48.625 seconds

[2023-11-09 14:14:25] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:28] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:14:28] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:14:28] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:14:29] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:32] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:14:32] [INFO] Loaded Meilisearch index in 29.988 seconds

[2023-11-09 14:14:32] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:14:33] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:14:33] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:14:34] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:14:34] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:35] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:14:37] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:14:37] [INFO] Loaded Meilisearch index in 28.602 seconds

[2023-11-09 14:14:37] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:14:37] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:14:59] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:59] [INFO] Loaded Meilisearch index in 45.235 seconds

[2023-11-09 14:14:59] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:14:59] [INFO] Loaded Meilisearch index in 30.052 seconds

[2023-11-09 14:15:05] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:08] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:08] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:15:17] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:21] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:21] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:15:29] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:29] [INFO] Loaded Meilisearch index in 44.926 seconds

[2023-11-09 14:15:35] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:36] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:15:39] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:39] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:15:42] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:47] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:47] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:15:48] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:51] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:51] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:15:54] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:15:54] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:15:55] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:15:55] [INFO] Loaded Meilisearch index in 27.643 seconds

[2023-11-09 14:15:57] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:57] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:15:57] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:15:57] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:16:00] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:16:05] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:16:05] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:16:19] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:16:20] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:16:20] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:16:20] [INFO] Loaded Meilisearch index in 46.376 seconds

[2023-11-09 14:16:20] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:16:23] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:16:23] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:16:23] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:16:26] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:16:26] [INFO] Loaded Meilisearch index in 46.891 seconds

[2023-11-09 14:16:46] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:16:46] [INFO] Loaded Meilisearch index in 48.005 seconds

[2023-11-09 14:17:01] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:02] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:17:06] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:17:06] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:07] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:17:09] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:17:10] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:17:10] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:10] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:17:10] [INFO] Loaded Meilisearch index in 29.478 seconds

[2023-11-09 14:17:11] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:13] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:17] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:17:17] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:19] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:19] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:17:19] [INFO] Loaded Meilisearch index in 27.260 seconds

[2023-11-09 14:17:22] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:17:22] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:17:22] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:23] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:32] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:32] [INFO] Loaded Meilisearch index in 45.538 seconds

[2023-11-09 14:17:32] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:32] [INFO] Loaded Meilisearch index in 25.479 seconds

[2023-11-09 14:17:50] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:50] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:17:55] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:17:55] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:17:55] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:17:55] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:18:02] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:18:02] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:18:24] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:18:25] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:18:25] [INFO] Loaded Meilisearch index in 55.746 seconds

[2023-11-09 14:18:25] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:18:25] [INFO] Loaded Meilisearch index in 50.093 seconds

[2023-11-09 14:18:29] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:18:29] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:18:30] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:18:34] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:18:34] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:18:36] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:18:37] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:18:37] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:18:37] [INFO] Loaded Meilisearch index in 27.397 seconds

[2023-11-09 14:18:40] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:18:40] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:18:40] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:18:40] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:18:52] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:18:55] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:18:55] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:18:55] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:19:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:19:08] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:19:10] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:19:10] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:19:10] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:19:14] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:19:14] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:19:16] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:19:16] [INFO] Loaded Meilisearch index in 47.222 seconds

[2023-11-09 14:19:41] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:19:41] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:19:44] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:19:44] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:19:44] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:19:56] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:19:59] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:19:59] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:20:00] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:20:12] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:20:12] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:20:15] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:20:15] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:20:15] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:20:18] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:20:18] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:20:21] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:20:21] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:20:26] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:20:26] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:20:49] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:20:49] [INFO] Loaded Meilisearch index in 48.651 seconds

[2023-11-09 14:20:49] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:20:49] [INFO] Loaded Meilisearch index in 37.727 seconds

[2023-11-09 14:21:09] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:21:10] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:21:15] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:21:15] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:21:15] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:21:36] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:21:36] [INFO] Loaded Meilisearch index in 53.846 seconds

[2023-11-09 14:21:51] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:21:52] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:21:54] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:21:54] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:21:55] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:22:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:22:07] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:22:11] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:22:11] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:22:11] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:22:18] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:22:18] [INFO] Loaded Meilisearch index in 49.243 seconds

[2023-11-09 14:22:18] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:22:21] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:22:21] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:22:22] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:22:32] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:22:32] [INFO] Loaded Meilisearch index in 46.746 seconds

[2023-11-09 14:22:32] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:22:36] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:22:36] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:22:59] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:00] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:23:03] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:23:03] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:03] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:23:03] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:16] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:16] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:23:19] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:23:19] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:19] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:26] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:26] [INFO] Loaded Meilisearch index in 49.477 seconds

[2023-11-09 14:23:26] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:29] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:23:29] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:30] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:30] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:31] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:23:31] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:23:31] [INFO] Loaded Meilisearch index in 27.327 seconds

[2023-11-09 14:23:33] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:23:33] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:41] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:41] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:23:41] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:23:41] [INFO] Loaded Meilisearch index in 46.858 seconds

[2023-11-09 14:23:43] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:23:43] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:23:55] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:24:00] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:24:00] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:24:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:24:07] [INFO] Loaded Meilisearch index in 47.152 seconds

[2023-11-09 14:24:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:24:11] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:24:11] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:24:11] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:24:12] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:24:18] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:24:18] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:24:21] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:24:25] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:24:25] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:24:39] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:24:39] [INFO] Loaded Meilisearch index in 47.003 seconds

[2023-11-09 14:25:15] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:25:15] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:25:23] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:25:23] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:25:32] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:25:32] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:25:36] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:25:36] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:25:39] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:25:40] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:25:42] [WARNING] Error adding document to meilisearch: MeilisearchError. Error message: .

[2023-11-09 14:25:45] [WARNING] Error adding document to meilisearch: MeilisearchError. Error message: .

[2023-11-09 14:25:45] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:25:45] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:25:48] [WARNING] Error adding document to meilisearch: MeilisearchError. Error message: .

[2023-11-09 14:25:50] [WARNING] Meilisearch did not restart in less than 20 seconds. Stopping polling.

[2023-11-09 14:25:55] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:25:55] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:25:55] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:25:56] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:25:56] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:25:58] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:26:00] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:26:01] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:26:01] [WARNING] Meilisearch did not start in less than 20 seconds. Stopping polling.

[2023-11-09 14:26:01] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:26:01] [INFO] Loaded Meilisearch index in 66.586 seconds

[2023-11-09 14:26:01] [WARNING] Error adding document to meilisearch: MeilisearchApiError. Client error '408 Request Timeout' for url 'http://localhost:7700/indexes/continue_context_items'

For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408

[2023-11-09 14:26:24] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:26:24] [INFO] Loaded Meilisearch index in 71.407 seconds

[2023-11-09 14:26:54] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:26:54] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:26:56] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:27:05] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:05] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:27:09] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:27:09] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:27:11] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:15] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:27:15] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:27:18] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:18] [INFO] Loaded Meilisearch index in 44.446 seconds

[2023-11-09 14:27:30] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:30] [INFO] Loaded Meilisearch index in 45.646 seconds

[2023-11-09 14:27:37] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:37] [INFO] Loaded Meilisearch index in 45.768 seconds

[2023-11-09 14:27:37] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:42] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:27:42] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:27:56] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:27:56] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:27:59] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:27:59] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:28:00] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:28:04] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:28:04] [INFO] Loaded Meilisearch index in 48.554 seconds

[2023-11-09 14:28:04] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:28:09] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:28:09] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:28:11] [DEBUG] Error loading meilisearch index: unknown async library, or not in async context

[2023-11-09 14:28:12] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:28:12] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:28:12] [WARNING] Error adding documents to meilisearch for context provider URLContextProvider: MeilisearchError. Error message: .

[2023-11-09 14:28:12] [WARNING] Error adding documents to meilisearch for context provider TerminalContextProvider: MeilisearchError. Error message: .

[2023-11-09 14:28:12] [WARNING] Error adding documents to meilisearch for context provider DiffContextProvider: MeilisearchError. Error message: .

[2023-11-09 14:28:12] [WARNING] Error adding documents to meilisearch for context provider URLContextProvider: MeilisearchError. Error message: .

[2023-11-09 14:28:23] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:28:23] [INFO] Loaded Meilisearch index in 49.170 seconds

[2023-11-09 14:28:31] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:28:31] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:28:34] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:28:34] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:28:37] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:28:42] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:28:42] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:28:56] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:28:56] [INFO] Loaded Meilisearch index in 46.043 seconds

[2023-11-09 14:29:16] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:29:16] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:29:19] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:29:19] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:29:19] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:29:31] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:29:31] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:29:34] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:29:34] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:29:35] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:29:46] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:29:47] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:29:50] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:29:50] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:29:50] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:29:57] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:29:57] [INFO] Loaded Meilisearch index in 47.170 seconds

[2023-11-09 14:29:57] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:02] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:04] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:30:04] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:04] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:05] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:13] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:13] [INFO] Loaded Meilisearch index in 47.186 seconds

[2023-11-09 14:30:13] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:13] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:30:16] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:30:16] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:16] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:26] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:26] [INFO] Loaded Meilisearch index in 50.873 seconds

[2023-11-09 14:30:28] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:28] [INFO] Loaded Meilisearch index in 47.329 seconds

[2023-11-09 14:30:49] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:30:49] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:30:50] [DEBUG] Error loading meilisearch index: MeilisearchError. Error message: .

[2023-11-09 14:30:53] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:30:53] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:54] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:30:54] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:31:00] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:31:00] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:31:00] [DEBUG] Error loading meilisearch index: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:31:00] [INFO] Loaded Meilisearch index in 31.732 seconds

[2023-11-09 14:31:01] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:31:01] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:31:06] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:31:06] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:31:29] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:31:29] [INFO] Loaded Meilisearch index in 54.813 seconds

[2023-11-09 14:31:37] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:31:38] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:31:43] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:31:43] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:32:05] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:32:06] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:32:06] [INFO] Loaded Meilisearch index in 49.241 seconds

[2023-11-09 14:32:10] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:32:10] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:32:17] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:32:20] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:32:20] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:32:21] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:32:26] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:32:38] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:32:38] [INFO] Loaded Meilisearch index in 54.645 seconds

[2023-11-09 14:32:38] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:32:38] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:34:39] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:34:39] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:34:53] [INFO] Loaded Meilisearch index in 12.129 seconds

[2023-11-09 14:35:00] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:35:06] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:35:06] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:35:07] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:35:11] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:35:13] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:35:13] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:13] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:35:13] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:15] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:15] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:33] [INFO] Loaded Meilisearch index in 3.881 seconds

[2023-11-09 14:35:38] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:35:40] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:35:41] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:35:41] [INFO] Loaded Meilisearch index in 56.729 seconds

[2023-11-09 14:35:41] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:47] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:35:51] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:35:51] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:35:54] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:36:00] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:36:00] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:36:00] [WARNING] Error adding document to meilisearch: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:36:00] [WARNING] Error adding document to meilisearch: MeilisearchCommunicationError, All connection attempts failed

[2023-11-09 14:36:07] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:36:07] [INFO] Loaded Meilisearch index in 51.471 seconds

[2023-11-09 14:36:13] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:36:13] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:36:16] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:36:16] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:36:17] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:36:21] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:36:22] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:36:22] [INFO] Loaded Meilisearch index in 48.490 seconds

[2023-11-09 14:36:26] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:36:26] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:36:38] [DEBUG] Error loading meilisearch index:

[2023-11-09 14:36:39] [WARNING] Failed to kill process on port 7700 (no such process)

[2023-11-09 14:36:42] [DEBUG] Starting MeiliSearch...

[2023-11-09 14:36:42] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:36:42] [INFO] Meilisearch started at http://localhost:7700

[2023-11-09 14:37:14] [DEBUG] Starting MeiliSearch...
[2023-11-09 14:37:14] [INFO] Meilisearch started at http://localhost:7700
[2023-11-09 14:37:36] [DEBUG] ------ End logs ------

@gecexgokyuzu I know the potential source of the unclosed session, so I should be able to fix this for the next release.
Are there any critical side-effects of this error, or is Continue able to operate as usual?

the continue server fails but restarting the pc does close that unclosed session rarely happens btwSent from my iPhoneOn 9 Nov 2023, at 23:27, Nate Sesti @.***> wrote:
@gecexgokyuzu I know the potential source of the unclosed session, so I should be able to fix this for the next release.
Are there any critical side-effects of this error, or is Continue able to operate as usual?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I’ve found the issues root, it specifically happens when im on a different repository and click on the selected line range label above the prompt box. so it opens the file from the other directory and the unclosed session loop starts rolling in the terminal.Sent from my iPhoneOn 10 Nov 2023, at 08:52, Hakan Yüksel Derin (gecexgokyuzu) @.> wrote:the continue server fails but restarting the pc does close that unclosed session rarely happens btwSent from my iPhoneOn 9 Nov 2023, at 23:27, Nate Sesti @.> wrote:
@gecexgokyuzu I know the potential source of the unclosed session, so I should be able to fix this for the next release.
Are there any critical side-effects of this error, or is Continue able to operate as usual?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@gecexgokyuzu I just cleaned up what I think was the source of the unclosed client session and checked by doing the same "open file from another directory" flow as you described. Now not seeing the unclosed client session loop.
Can you verify in the latest versions (pre-release is 0.7.4+) whether this is fixed for you?

hey Nate!
the issue seems to persist, and this time it directly gets into the
infinite loop without even doing anything,
here is the console output:
PS D:\Yazılım\WEBSİTELERİ\CMHLIFESTYLE\api> python -m continuedev

__  /__ _______ __  /()____ ____  _______
_  /     _  __ __  __ _  /  / __  __ _  / / /_  _
/ /___   / // /  / / // /_  _  /  _  / / // // / /  /
_/   _/ // // _/  //   // // _,_/  ___/
INFO:     Started server process [16980]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:65432 (Press CTRL+C to quit)
INFO:     ('<IP_ADDRESS>', 5103) - "WebSocket /
socket.io/?window_id=ffdc47f4-eefa-414d-8819-a1656cd9b0f1&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
INFO:     <IP_ADDRESS>:5111 - "GET /slash_commands HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:5112 - "GET /context_providers HTTP/1.1" 200 OK
INFO:     ('<IP_ADDRESS>', 5114) - "WebSocket /
socket.io/?window_info={"window_id"%3A"ffdc47f4-eefa-414d-8819-a1656cd9b0f1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\public_html"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
INFO:     ('<IP_ADDRESS>', 5115) - "WebSocket /
socket.io/?window_info={"window_id"%3A"3cdb068a-4a96-4bf7-8820-f53784cfb5a1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\api"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
[2023-11-20 13:33:08] [DEBUG] Starting MeiliSearch...
[2023-11-20 13:33:08] [INFO] Meilisearch started at http://localhost:7700
Cancelled task listDirectoryContents
INFO:     ('<IP_ADDRESS>', 5354) - "WebSocket /
socket.io/?window_info={"window_id"%3A"ffdc47f4-eefa-414d-8819-a1656cd9b0f1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\public_html"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD2A7050>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD187890>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD2A5710>
INFO:     connection closed
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 5375) - "WebSocket /
socket.io/?window_info={"window_id"%3A"ffdc47f4-eefa-414d-8819-a1656cd9b0f1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\public_html"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD1A5690>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD1A6E90>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD1A5690>
On Thu, 16 Nov 2023 at 23:06, Nate Sesti @.***> wrote:

@gecexgokyuzu https://github.com/gecexgokyuzu I just cleaned up what I
think was the source of the unclosed client session and checked by doing
the same "open file from another directory" flow as you described. Now not
seeing the unclosed client session loop.
Can you verify in the latest versions (pre-release is 0.7.4+) whether this
is fixed for you?
—
Reply to this email directly, view it on GitHub
https://github.com/continuedev/continue/issues/611#issuecomment-1815315712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYWPMVDA2ZAL5AB6QYYRDLLYEZ56ZAVCNFSM6AAAAAA7EQGRTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJVGMYTKNZRGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

also my local server version is like below:
Name: continuedev
Version: 0.1.75
Summary:
Home-page:
Author: Nate Sesti
Author-email: @.***
License:
Location:
C:\Users\gecexgokyuzu\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages
Requires: anthropic, boltons, bs4, chevron, chromadb, directory-tree,
fastapi, huggingface-hub, jsonref, jsonschema, meilisearch-python-async,
nest-asyncio, openai, posthog, psutil, pydantic, pygithub, python-dotenv,
python-lsp-server, python-socketio, redbaron, replicate, ripgrepy, socksio,
tiktoken, tree-sitter, tree-sitter-languages, typer, urllib3, uvicorn,
websockets
Required-by:
On Mon, 20 Nov 2023 at 13:35, Hakan Yüksel Derin @.***>
wrote:

hey Nate!
the issue seems to persist, and this time it directly gets into the
infinite loop without even doing anything,
here is the console output:
PS D:\Yazılım\WEBSİTELERİ\CMHLIFESTYLE\api> python -m continuedev

__  /__ _______ __  /()____ ____  _______
_  /     _  __ __  __ _  /  / __  __ _  / / /_  _
/ /___   / // /  / / // /_  _  /  _  / / // // / /  /
_/   _/ // // _/  //   // // _,_/  ___/
INFO:     Started server process [16980]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:65432 (Press CTRL+C to quit)
INFO:     ('<IP_ADDRESS>', 5103) - "WebSocket /
socket.io/?window_id=ffdc47f4-eefa-414d-8819-a1656cd9b0f1&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
INFO:     <IP_ADDRESS>:5111 - "GET /slash_commands HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:5112 - "GET /context_providers HTTP/1.1" 200 OK
INFO:     ('<IP_ADDRESS>', 5114) - "WebSocket /
socket.io/?window_info={"window_id"%3A"ffdc47f4-eefa-414d-8819-a1656cd9b0f1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\public_html"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
INFO:     ('<IP_ADDRESS>', 5115) - "WebSocket /
socket.io/?window_info={"window_id"%3A"3cdb068a-4a96-4bf7-8820-f53784cfb5a1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\api"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
[2023-11-20 13:33:08] [DEBUG] Starting MeiliSearch...
[2023-11-20 13:33:08] [INFO] Meilisearch started at http://localhost:7700
Cancelled task listDirectoryContents
INFO:     ('<IP_ADDRESS>', 5354) - "WebSocket /
socket.io/?window_info={"window_id"%3A"ffdc47f4-eefa-414d-8819-a1656cd9b0f1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\public_html"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD2A7050>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD187890>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD2A5710>
INFO:     connection closed
INFO:     connection closed
INFO:     ('<IP_ADDRESS>', 5375) - "WebSocket /
socket.io/?window_info={"window_id"%3A"ffdc47f4-eefa-414d-8819-a1656cd9b0f1"%2C"workspace_directory"%3A"d%3A\\Yazılım\\WEBSİTELERİ\\CMHLIFESTYLE\\public_html"%2C"unique_id"%3A"f99ccc5d3fc7a95d4ff2f2c568ce8daf11356f41cbcd9328cb0169a304ecb42a"%2C"ide_info"%3A{"name"%3A"vscode"%2C"version"%3A"1.84.2"}}&EIO=4&transport=websocket"
[accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD1A5690>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD1A6E90>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x00000214CD1A5690>
On Thu, 16 Nov 2023 at 23:06, Nate Sesti @.***> wrote:

@gecexgokyuzu https://github.com/gecexgokyuzu I just cleaned up what I
think was the source of the unclosed client session and checked by doing
the same "open file from another directory" flow as you described. Now not
seeing the unclosed client session loop.
Can you verify in the latest versions (pre-release is 0.7.4+) whether
this is fixed for you?
—
Reply to this email directly, view it on GitHub
https://github.com/continuedev/continue/issues/611#issuecomment-1815315712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYWPMVDA2ZAL5AB6QYYRDLLYEZ56ZAVCNFSM6AAAAAA7EQGRTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJVGMYTKNZRGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

same here even on server 0.1.100, any news?
output:

_________               _____ _____
__  ____/______ _______ __  /____(_)_______ ____  _______
_  /     _  __ \__  __ \_  __/__  / __  __ \_  / / /_  _ \
/ /___   / /_/ /_  / / // /_  _  /  _  / / // /_/ / /  __/
\____/   \____/ /_/ /_/ \__/  /_/   /_/ /_/ \__,_/  \___/

[2023-11-29 21:21:11] [DEBUG] ------ Begin Logs ------
INFO:     Started server process [121442]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:65432 (Press CTRL+C to quit)
[2023-11-29 21:21:11] [DEBUG] Starting MeiliSearch...
[2023-11-29 21:21:11] [INFO] Meilisearch started at http://localhost:7700
INFO:     ('<IP_ADDRESS>', 59128) - "WebSocket /socket.io/?window_info=%7B%22window_id%22%3A%223e1064f3-af83-4f02-ba40-41b97feecace%22%2C%22workspace_directory%22%3A%22%2Fvar%2Fhome%2Fsfc%2FProjects%2Fshiso%22%2C%22unique_id%22%3A%22d6c8360a245ac1523d636aacd41d2b255f52c028ebc471afc5e9526ad9a34ae0%22%2C%22ide_info%22%3A%7B%22name%22%3A%22vscode%22%2C%22version%22%3A%221.84.1%22%7D%7D&EIO=4&transport=websocket" [accepted]
INFO:     connection open
INFO:     ('<IP_ADDRESS>', 36894) - "WebSocket /socket.io/?window_id=3e1064f3-af83-4f02-ba40-41b97feecace&EIO=4&transport=websocket" [accepted]
INFO:     connection open
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f65ddd78250>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f65ddd0d350>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f65e08acf90>

then the server does not accept any connection, even Ctrl-C does not work.  I have very good news. The Continue Python server is no longer necessary as of version 0.7.50 (VS Code pre-release), which means that none of this connection nonsense will even be necessary. Just download the extension and you're good to go.
I'm going to close this issue since the errors here aren't really possible in the newest version without any use of Meilisearch or socket.io, but if you're running into separate issues please let me know!


DBeaver: Final touch on the Generate UUID function

DBeaver - Version 5.3.2 CE
DBeaver driver: MS SQL Server  / Microsoft Driver, PostgreSQL Driver, etc.
Operating System: Windows 7 / Windows 8.1 / Windows 10
Database Server: Microsoft SQL Express 2014, 2016, 2017
Minor improvement to the Generate UUID function from the #4818 issue, might be:
o Add the keyboard shortcut to the Edit Cell function popup Form dialog.

If I right click on the grid cell and choose Edit -> Edit Cell (Shift+Enter) that Form dialog does not react on the Ctrl+Shift+U keyboard shortcut.

PS. Strange that the dialog is named just Form. Should it not be named Edit cell or something?

o Add a menue choice in the data grid context menu for Generate UUID (Ctrl+Shift+U).

Yeah it seems like the Generate UUID option only generates the same UUID for all rows in v21.1.0

Yeah it seems like the Generate UUID option only generates the same UUID for all rows as well in v21.1.0

This issue still persists in v22.2.1, will there be any fixes for this?


Add testing

I have basic DB access and CRUD requests working. Next I'd like to test such that:

I can test individual endpoints.
For each test, I can set up the scenario directly interacting with the database ("it responds with the correct JSON when x users are in the database", "it inserts a new user into the database", etc.).
Tests run in their own database transaction so there's no state leaked across tests (and they could run in parallel using the same database instance without interfering with each other).

There was a talk on the topic at EuroRust as well: https://www.youtube.com/watch?v=_VB1fLLtZfQ

The talk suggest using database closing instead of transactions which seems interesting.

done


Old documentation links are 404

🐛 Bug
Our transition to versioned docs has meant that many (all?) old links to the docs are 404. (e.g. https://napari.org/docs/developers/GOVERNANCE.html). Currently Google is still finding them. They should instead redirect to or contain a copy of dev, imho. (or latest stable release.)

Good catch! I'd probably link to dev as that will be stable moving forward

i.e. https://napari.org/docs/developers/GOVERNANCE.html should become https://napari.org/docs/dev/developers/GOVERNANCE.html

This was closed by #1750 that fixed the main links in our readme by adding dev. There had been some discussion at one point with @jni about trying to do redirects from old links (see https://github.com/napari/napari/issues/1702#issuecomment-709616237) but I think we're probably ok now. Google searches have started surfacing real links again. While we've got more website reorganization ahead, we'll likely keep this main url naming convention the same, so fine to leave closed.


Update missed connection management return values

Missed updating some of the actual function implementations in https://github.com/microsoft/azuredatastudio/pull/14660/files

Pull Request Test Coverage Report for Build 647813563

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

Totals

Change from base Build 647781520:
-0.001%

Covered Lines:
25401

Relevant Lines:
53455

💛  - Coveralls


预训练模型和测试视频的网盘链接有误？

大佬您好，感谢开源您的优秀工作。项目中的谷歌网盘链接，有误。

Data and models haven't been uploaded yet, thanks for your attention.

Data and models haven't been uploaded yet, thanks for your attention.

are you going to upload in the near future?

Maybe you will add instruction for new models?

Data and models have been uploaded. Feel free to comment if you have any questions. Close since it is solved.

Data and models have been uploaded. Feel free to comment if you have any questions. Close since it is solved.

谢谢大佬

@YuanxunLu GoogleDrive在国内下载非常困难，经常中断。能否提供其他网盘（如123盘之类）分流下载？


Hi, I am a newbie, I can't use TabNine in my VSCode

I install the TabNine extension in my VSCode for python, but it's not work for me, it must be used with any setting, but the completion window still not show out, what can I do??

what's step can I verify the TabNine is worked ??

Same issue, I think this project is dead.

Same same

same. it did not show the belief of prediction as the TabNine ads. I am not sure whether it is activated.

Same thing for me

Same thing!
There is no auto-completion for Javascript, PHP nor even Python.
Its is giving all the things same as emmet.

Hi @SwastikBhattacharjee , can you please share a screenshot of your status-bar, a screenshot of the extensions section in vscode where Tabnine is installed, and the vscode console log (Help -> Toggle Developer Tools)?
Thanks


New update appending port to url, breaking production.

          This line basically adds to all urls `:80` and breaks them.

Originally posted by @KevinEdry in https://github.com/clerkinc/javascript/pull/1394#discussion_r1241164591
This basically breaks my app both in development and production, with the exception of localhost, I don't see a reason for appending a port to the url.

@dimkl Awesome to see a fix so quickly, I am glad to have been of some help! 👍.
I'll close this issue once https://github.com/clerkinc/javascript/pull/1415 will be merged and a new version of @clerk/nextjs is released.

Fix released in version<EMAIL_ADDRESS>@KevinEdry could you verify that version and close this issue? :)

@dimkl Can confirm this fixes the issue, thanks for the help!
Closing this issue for now.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


🐞 Bug Small Screen can't see notifications Mark all as read and See All buttons

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Some Notifications and Mark all as read and See All button is not accessable .

Inaccessible Notifications:

Some users are encountering difficulties accessing specific notifications within their notification feed.
The "Mark all as read" and "See All" buttons do not appear to be functioning as expected for these users, leading to inconvenience in managing notifications.

Design and Layout Issues:

There is a design issue with the notification icon and count, as it appears that these elements are spaced too far apart.
The excessive spacing creates a visual inconsistency and affects the overall user experience by making it less aesthetically pleasing.

Steps To Reproduce

Convert CircuitVerse website to small screen ( <990 px)
Click on navbar toggler icon
Click on Notification icon

See that notification dropdown is overflowing
Expected Behavior
Notification should be on top with level of Simulator so that it is easily accessable.
Screenshots
Before:

After:

Device Information [optional]
- OS:
- Browser:
- version:

Additional context
No response
Are you working on this issue?
Yes

@tanmoysrt @vedant-jain03 @VaibhavUpreti please review the issue

@shauryag2002 @vedant-jain03 @tanmoysrt please assign me this issue

Hi @shauryag2002 go ahead !


measuring objects with the D435i without a chessboard

I want to measure objects in 3D with D435i without chessboard. For this, I used the python files in the box_dimensioner_multicam folder. Is it possible to do this without a chessboard?

Hi @mehmetwashere  If you are using a single D435i camera then https://github.com/IntelRealSense/librealsense/issues/9951 should be a useful reference for adapting box_dimensioner_multicam for use without a chessboard.

Thank you for your help dear @MartyG-RealSense


"there's no self in this scope"???

When compiling the following code:
class Test
	def fn
		with self yield
	end
end

Test.new.fn do
	puts self
end

Why do I get the error there's no self in this scope? How can I implement DSLs in the absence of self?
Suffice it to say that any attempt to call self-local methods within the block also fails, naturally.

Methods called in such a block do work: http://play.crystal-lang.org/#/r/9kf
As long as the methods aren't protected or private, there shouldn't be anything preventing you from implementing a DSL with with self yield.

Nope!
http://play.crystal-lang.org/#/r/9kj

Actually, I think it's the initialize method at fault:
class TestGroup
	def initialize
		with self yield
	end
	def test()
	end
end

TestGroup.new do
 	test
end

Yeah pretty much. Look at this... http://play.crystal-lang.org/#/r/9km

So why doesn't this work?
http://play.crystal-lang.org/#/r/9kn

I honestly don't know! Perhaps @asterite could enlighten us :)

@stugol @Exilor Acording to the docs:

A yield expression can be modified, using the with keyword, to specify an object to use as the default receiver of method calls within the block

That is, self isn't changed. The only thing that with obj yield gives you is that when you do foo(...) (without an explicit receiver), that foo method is first looked up in obj.
self at the top-level doesn't exist (unlike Ruby), so that's the error.
@stugol What DSL are you trying to build?

And the explanation to why self isn't changed, is because we (me and others) stumbled across too many bugs where you had:
class Foo
  def bar
    # This method is executed via instance_eval, but maybe you don't know that
    some_obj.some_innocent_method do
      puts @x # oops, @x is not Foo's @x
      puts self # oops, self is not Foo
   end
end

@asterite I still don't understand, however, why the code at http://play.crystal-lang.org/#/r/9kn doesn't work.
I'm trying to write a testing framework, based on my Ruby one. And then, I'm trying to write a smart client/server delta-based backup program in Crystal ;)
Why? Because C++ seems to be designed for the express purpose of annoying me.

@stugol You can do it like this.
The thing is, TestGroup.new do ... end doesn't change self inside the block. If you want to forward the object sent by with ... yield you also have to pass it as a block argument.

@asterite Why doesn't the group = new line cause infinite recursion?
Also, why is it necessary to with group yield group? Surely yield group would be sufficient here? Besides, if we're doing with group yield in new, why is it necessary to pass the parameter in any case? Is there some technical reason why with yield doesn't work inside new? What am I missing here?
Also, doesn't self.new have to return self?

@stugol group = new doesn't cause infinite recursion because it's calling the new without a block overload (methods also overload based on whether they receive a block or not). But this particular case is a bit controversial because if you don't define an "initialize" then the compiler will automatically define an empty one for you.
Yes, yield group is enough. But if you don't use with ...  then inside the TestGroup.new do |group|, invoking test (wihtout a receiver) won't work. But if you don't need that, it's not needed.
with yield is working inside new, at least in my example it does.
I don't understand the "self.new has to return self" question.

@asterite Ah, I see what you mean. Without with group yield there is no "implicit self" so I can't call DSL methods in my block; and without yield group there is no "explicit self" so I can't with self yield inside my block. Gotcha.
So, essentially, with yield never provides an actual self value to the block - you always have to pass it as a parameter to the block if you need to refer to it? Unlike Ruby. Why did you decide to do things that way?
As to the other question....doesn't the new method have to return the new object to the caller? Otherwise value = TestGroup.new wouldn't work. Or does it implicitly return itself?
Incidentally... I don't fully understand the &block syntax. I understand it in Ruby, but in Crystal it's a bit confusing. Given the following code:
def fn(&block)
   yield if block
end

Firstly, is it valid to query the existence of the block in this manner? Secondly, can I call it without a block? Thirdly, does Crystal have a block_given??
def fn
   yield if block_given?
end

I'm a bit confused about captured- vs non-captured blocks as well.

Unlike Ruby. Why did you decide to do things that way?

https://github.com/manastech/crystal/issues/1095#issuecomment-127098048

@stugol It's all in the docs. Please read all the sections.
I know things aren't exactly like Ruby, but that's the price we have to pay if we want a statically typed and checked language.

@ozra that's not a reason. Ruby does it that way, and seems to work perfectly fine. Why should bugs in Crystal be any more likely?
@asterite I have read the docs.

@stugol ...because Ruby code can occasionally be an insane bug magnet?
Coming from Python, the reason I use Crystal and not Ruby is because Crystal is so much more strict, so those weird errors don't happen.

@stugol Ruby allows you to invoke non-existent methods at runtime, and you get an exception. In Crystal we chose not being able to do that. So because Ruby does some things in a way shouldn't mean we should do exactly the same.

I'll close this one. The language works as expected here and for now there are no intentions of changing the behaviour of with ... yield. And you can do what you want if you forward the scope in a block argument.


pull request for e2e test at 11/24/2016 02:56:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Help Output Formatting in 1.0.25

The help command's output is somewhat unreadable. Screenshot is from Windows 10, AutoSaliens version 1.0.25. I assume this isn't the intended format of the help command. :)
In case it's relevant, the window width is 150, height 30.

Ouch, that definitely isn't supposed to happen. I'll take a look into it.

When I included colors, I changed some more things in the console. New lines were probably broken because of that, depending what OS you're running it on.
I fixed it, you can find the latest build at the same url: https://ci.appveyor.com/project/Archomeda/AutoSaliens/branch/master/artifacts
Let me know if some other outputs are broken.

Verified fixed in 1.0.37. Excellent! Thank you!


Does authorization code have an expiration date?

Good evening. Could you tell me if the authorization code has an expiration date, and if so, how long will it be valid?

It definitely can expire, but it doesn't matter for an app, when exactly the code expires.


Aerospace seems unable to control the main Steam window?

I'm new to Aerospace, but one of the very first times I launch it, it's immediately unable to control half of the windows I have open.
Some of those I am unsurprised by. The Console.app interface by Universal Audio for their Apollo consoles (download), for instance, is famously poorly-behaved, with a window that's utterly inaccessible and forces itself into strange shapes and configurations without any user-input. But others, like the Steam gaming store, I was more surprised by.
This particular Issue is about Steam specifically; but while I'm at it - is there any known workaround for applications like this that are difficult to control? Elevating the process or anything like that?

I think what you faced is that Steam window is floating, you can make it tiled by running layout tiling command.
The reason why it's floated is because AeroSpace dialog heuristics detected it as a dialog. All windows without a fullscreen button are floated by default (except for some hardcoded exceptions). Steam shows a maximize button instead of a fullscreen button.

except for some hardcoded exceptions

Actually, Steam was part of these hardcoded exceptions. AeroSpace specifically tiled windows with com.valvesoftware.steam bundle ID https://github.com/nikitabobko/AeroSpace/blob/a20ea2b4578c385a2774cc56360578e049372dce/Sources/AppBundle/tree/MacWindow.swift#L217
I rechecked Steam app and I see that they changed bundled ID to com.valvesoftware.steam.helper
I have two things to say:

It makes me sad applications as big as Steam just change their bundle ID. It's not the way developers are supposed to use bundle ID :(
I think I would like to keep Steam floating and I will remove the hardcoded outdated Steam bundle ID.  But hardcoding Steam bundle ID will make "special offers" dialogs tiling

you can make it tiled by running layout tiling command

If you want to tile Steam windows by default you can use on-window-detected callback
[[on-window-detected]]
if.app-id = 'com.valvesoftware.steam.helper'
run = 'layout tiling'


Store size of annexed files as int

Store size of annexed files in working tree as an integer

thanks!


[Breaking change] Apply naming conventions to DTO types

Codecov Report

Merging #14 into master will not change coverage.
The diff coverage is 67.85%.

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


Grafana 7.2.1 - Metrics List does not show currently selected metric

Steps:
Create new Panel, add at least one metric.
Save Panel and Dashboard.
View Dashboard.
Edit Panel.
Notice, that Metrics lists does not show the selected time series.
Environment:

Docker (on Azure as WebApp)
Plugin: 0.2.1

Should be fixed on master


logging: Remove long interrupt locking when immediate mode is used.

Changed behavior of the logger in immediate mode. Previously, context was lock for whole string processing and sending which resulted in log output being clean and not interleaved but at the cost of very long period of interrupt locking. It is changed to lock interrupts only for single byte sending over transport (e.g. uart). With this approach long locking time is removed but log output may be garbled since one log message can be interrupted by another.
Added test suite for log immediate mode which checks if logger is stable when log is preempted by another log.
Log output buffer is fixed to be single byte in immediate mode. It does not make sense to have longer buffer, saves ram and simplifies processing.
Fixes #20770.

Can you give some detail on why you are using interrupt locking here, instead of a semaphore or something like that?
If the answer is because there could be contention with interrupt handlers that are trying to possibly log something, I don't think preventing those interrupt handlers from running is desirable from a system latency perspective.

Can you give some detail on why you are using interrupt locking here, instead of a semaphore or something like that?

That's because log can be called from any context.

I don't think preventing those interrupt handlers from running is desirable from a system latency perspective.

Immediate mode introduces huge system latency, each log message is processed in the context of the call, blocking for hundred of microseconds in given context (https://github.com/zephyrproject-rtos/zephyr/blob/d5314b8387bbd8b29ed9efbd57e2bf045e78b25f/subsys/logging/Kconfig#L123)

Can you give some detail on why you are using interrupt locking here, instead of a semaphore or something like that?

That's because log can be called from any context.

I don't think preventing those interrupt handlers from running is desirable from a system latency perspective.

Immediate mode introduces huge system latency, each log message is processed in the context of the call, blocking for hundred of microseconds in given context (
https://github.com/zephyrproject-rtos/zephyr/blob/d5314b8387bbd8b29ed9efbd57e2bf045e78b25f/subsys/logging/Kconfig#L123
)

Why are you using irq_lock/unlock instead of a spinlock?

basically I think we should keep the original lock interrupts here to keep the output of logger clean for immediate mode, users should enable logging thread if the application take care system latency.
for saving more buffer, current design handles the string format exactly before the really output, I haven't the latency data of this part, if it takes long, I don't think we should fix it because there will be huge change for logging subsystem, users definitely should use logging thread; but I would like to think it's the uart(for uart backend example) cause more system latency, I'm not sure if there is good way to handle it, I just imagine one when uart is doing the transfer we can have CPU to handle the next format, not sure if it works and if it's implementable.

@wentongwu

basically I think we should keep the original lock interrupts here to keep the output of logger clean for immediate mode, users should enable logging thread if the application take care system latency.

Unfortunately, there will be those who prefer to have no interrupts locked and interleaved output and those preferring to have clean output. Some may expect that log_immediate will behave like printk which does not lock.
I will add this as an option then.

@andrewboie can you take a look at @nordic-krch's latest proposal in this PR?

@wentongwu

AFAIK the LOG_PRINTK is used to overcome printk's no lock.

and that works well when deferred mode is used. Some may want to use immediate mode but locking context is a problem for them (yet they can accept that log processing takes multiple milliseconds in any context, including interrupts).
Personally, i think that immediate mode works well for emulator, tests or single apps where there is not much going on and becomes unacceptable in more complex real time application.

@andrewboie ping

@andrewboie mind taking a look at this one?


[CodeCompletion] NFC: rename CallParameter* to CallArgument*

Since these chunks are for call sites, the correct term is "argument".
(Subset of #38453)

@swift-ci Please smoke test

@swift-ci Please smoke test


Error in the English output of the fromNow() method

Describe the bug
Whenever the function fromNow() is use with a date and a locale the English string that is generated produce a duplicate.
To Reproduce
Use the following method with those parameters :
Function:
Moment(publishedAt).locale(i18n.language).fromNow()

Parameters:
- publishedAt   = 2023-07-17
- i18n.language = "en"

Result:

the "ago ago" string is return two time
On the other hand, only using the following method work:
Moment(publishedAt).fromNow()

Results:

Expected behavior
A well formatted string based on the language provided
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information if applicable):

Device: iPhone 11 Pro
OS:  iOS 16.4
"react-native": "0.72.1"
"moment": "2.29.4",

Moment-specific environment

The time zone setting of the machine the code is running on : Eastern Daylight Saving time
The time and date at which the code was run: every day since 6 months

Please run the following code in your environment and include the output:
console.log((new Date()).toString())
console.log((new Date()).toLocaleString())
console.log((new Date()).getTimezoneOffset())
console.log(navigator.userAgent)
console.log(moment.version)

 LOG  ________________________________
 LOG  Tue Jul 18 2023 00:08:38 GMT-0400
 LOG  7/18/2023, 12:08:38 AM
 LOG  240
 LOG  2.29.4
 LOG  ________________________________

Additional context
Add any other context about the problem here.

Hey @jguipi, the cases mentioned above are working fine for me. Could you please elaborate more or check if the issue still persists?
(CASE-1 and CASE-2 are respective outputs)

Sorry everyone, just got back from vacation.
That's very strange, unfortunately I can't share my code since it's part of the business code...
I upgraded to the latest version, and it seems like it still happen. If I'm the only one that face that issues, I guess we can close it. I'll investigate on my side and see if I can found the solution and post it here.


Please invite me to the community

Name
dev0614
Additional Context
I am blockchain developer.
I want to join this organization.

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is a remarkable open-source solution tailored for serverless platforms, aimed at empowering creators to craft their infrastructure solutions. 💻 We're thrilled to welcome you into our vibrant community! ✨ We eagerly anticipate your valuable contributions! 🤓 Don't forget to explore our community on Github and connect with us on LinkedIn 💜 Feel free to spread the word about our community to like-minded individuals interested in development, DevOps, technology, and collaborative contributions. 👉💜👈


feat: name change

Description
Replace this text with a summary of the changes in this PR. Include why the changes are needed and context about the changes. List required dependencies. If there is a Git issue for the change, please link to it.
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[ ] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

@jor2 - pre-commit issue in this PR in case you've not seen it already.
Add module repository to go.mod..........................................Failed

hook id: go-mod-module-repository
files were modified by this hook
helmlint.................................................................Passed
make: *** [Makefile:98: pre-commit] Error 1
Error: Process completed with exit code 2.


run CI on all PR branches

This is a follow-up to https://github.com/dart-lang/tools/pull/280#issuecomment-2189941102. In summary, we only run CI checks on PRs against the main branch. However, in cases where an older major version of a package needs to be patched, it doesn't make sense to PR against main. CI won't run for these PRs, but it probably should.
This updates our GitHub CI configs to run checks against PRs against any branch.

[X] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

FYI: I've created a release for unified_analytics-v6.1.2 since it looks like that never got made after https://github.com/dart-lang/tools/pull/277 merged. I did this as I didn't want this PR merging to trigger a release from CI.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
252

Relevant Lines:
252

💛  - Coveralls


Problem: there is a lot of clippy errors in rust

Solution: fix all clippy errors and run cargo fmt

Okay I have fixed as many implicit arg capture as I can but there are still a lot remaining in the code. I only focused on those who trigger a clippy errors when running cargo clippy


Rework NavigationMeshGenerator

Implements proposal https://github.com/godotengine/godot-proposals/issues/5138
Supersedes https://github.com/godotengine/godot/pull/64682 and https://github.com/godotengine/godot/pull/70174
The NavigationMeshGenerator singleton is responsible for navigation mesh baking and source geometry parsing from the SceneTree.

This pr turns NavigationMeshGenerator singleton into a server independent from "navigation" pathfinding module and NavigationServer.
This is primarly done to solve odd dependency issues in NavigationServer and NavigationRegion but also for future developments like better threading support for navigation mesh baking. Currently every single NavigationRegion3D node spawns its own thread for baking its own navigation mesh in the background and parses the same SceneTree again and again which is peak inefficiency and creates unsolvable framerate issues with (re)baking at runtime.
Adds NavigationMeshGeneratorManager to make generator implementation selectable in ProjectSettings.
Basically a straight copy from other servers like pyhsics and navigation that allows for other implementations of the generator for games that need a different navigation mesh baking than the default one that uses ReCast and is currently 3D only.
Adds GodotNavigationMeshGenerator module as the default implementation of a NavigationMeshGenerator.
Adds dummy NavigationMeshGenerator implementation so minimalist Godot can be build without including the module.
Moves the NavigationMeshGenerator up in the init chain so modules that want to extend the navigation mesh baking can work with SERVER / SCENE module init levels.
Adds NavigationGeometryParser3D class that makes it possibility for modules and addons to extend the navigation mesh baking by contributing their own source geometry.
Adds NavigationMeshSourceGeometryData resource and new functions to the generator that makes it possibility to split the source geometry parsing process from the navigation mesh baking process and reuse the same source data to bake multiple meshes with different parameters.
Baking can happen in a background thread while parsing requires a snapshot of the nodes in the SceneTree so must happen in a safe idle frame with a flushed queue. Previously both parsing and baking were forced into the same function and frame which resulted in unavoidable runtime stutter.

The NavigationGeometryParser3D class can be extended and registered on the NavigationMeshGenerator singleton to contribute 3D geometry from specified node class(es) for navigation mesh baking.
var parser : NavigationGeometryParser3D = NavigationGeometryParser3D.new()
NavigationMeshGenerator.register_geometry_parser_3d(parser)
NavigationMeshGenerator.unregister_geometry_parser_3d(parser)

Modules can use the parses_node() and parse_geometry() directly while scripts can override the underscore _parses_node() and _parse_geometry() functions. Since navmesh baking with ReCast requires specific, triangulated mesh data helper functions are exposed to add mesh resources or mesh arrays or single faces to the source geometry.
GDScript example with function override:
extends NavigationGeometryParser3D

func _parses_node(node : Node):
    # return true if this node wants to add baking geometry
    return node is CustomNode3D

func _parse_geometry(node: Node, navigationmesh : NavigationMesh, source_geometry : NavigationMeshSourceGeometryData):
    var mesh : Mesh = PlaneMesh.new()
    mesh.size = Vector2(10.0,10.0)
    var mesh_xfrom : Transform3D = node.global_transform
    source_geometry.add_mesh(mesh, mesh_xfrom)

    var mesh_array : Array = mesh.get_mesh_arrays()
    mesh_xfrom.origin.x += 5.0
    mesh_xfrom.origin.z += 5.0
     source_geometry.add_mesh_array(mesh_array, mesh_xfrom)

    mesh_xfrom.origin.x -= 10.0
    mesh_xfrom.origin.z -= 10.0
    var faces : PackedVector3Array = mesh.get_faces()
    source_geometry.add_faces(faces, mesh_xfrom)

Generally I'm onboard with this approach, but I think there is a little confusion around having both the bake and parse_source_geometry_data paths that I'd like to see unified.  There really should be only one way to get geometry data into the NavigationMeshGenerator for processing into a navigation mesh.

For those that are wondering why it was linked here but is not included rightnow. This pr will get updated with the 2D navmesh baking as it is more or less fully entangled in the NavigationMeshGenerator rework. Did not find time to finish and push the full update for this pr but will get there.

Will include a TileMap parser that bakes an optimized navigation polygon from used TileMap collision shapes and navigation polygons.
This optimized navigation polygon can then also be offset for different agent sizes, something that does not work when navigation polygons are splintered for each TileMap cell or TileMap quadrant.

Will include a TileMap parser that bakes an optimized navigation polygon from used TileMap collision shapes and navigation polygons.
This optimized and merged navigation polygon can then also be offset for different agent sizes. This is something that does not work by default for the TileMap while navigation polygons are splintered between each TileMap cell or TileMap quadrant.

Could the same approach be used for baking collision (in a separate PR)? This would avoid issues with RigidBodies bouncing between tile seams, while also improving performance in some scenarios.

@Calinou
Yes it can be used to merge collision. In fact the parser already reads all the collision polygons as obstructions for the navigation polygon baking. It is therefor just a matter of someone repurposing this implementing for collision and TileMap.
There was always the plan to merge the TileMap internals per e.g. quadrant but since Groud is currently reworking the TileMap internals this is all postponed until the rework is done.

A parser to create a nav polygon from my tile map made visuals would be huge.
I could easily implement this into my workflow.
Yes please and thank you.
My hero

Any info on when can we expect this?

This pr is now broken due to more recent changes in core related to SceneTree and threading.
There is no easy or fast fix. A bulk of the pr needs to be redone from scratch. No ETA.

EvenOdd is closest to the old NavigationPolygon outline behavior minus all the old polygon overlap errors. This fillrule turns inner outlines that are even numbered into obstacles (holes) and odd numbered into traversable surfaces.

Is this mode really needed ? It looks kind of hard to use and not really useful. Unless i misunderstood something.
From the original post and the code, it seems like some properties to NavigationPolygon do not really belong there. Things like agent_radius, collision_mask, etc... should be decided at bake time, if I am not mistaking ? I feel it should be more like "bake profiles" than properties of the polygon themselves ?
Regarding NavigationGeometryParsers, I think the idea is good, but it does not really look like the Godot-way to do the things. Instead of a custom class to extend, it would be a lot easier to simply allow 2D or 3D node to expose a _parse_navigation_geometry virtual method if they want to, instead of relying on another class.
For TileMap mesh baking, the approach looks quite good to me. As I mentioned in chat, I am unsure whether if, like, being able to define "walkable areas" make a lot of sense when you can define "non-walkable areas" using collision shapes. It might be a bit confusing  to users IMO. However, if we want to keep it, I believe that, by default, we should probably make it that the default shape on tiles is the tile's shape. That would avoid having to define the shape for all tiles.

The NavigationMeshGenerator singleton is now its own module and server, independent from the "navigation" pathfinding module and NavigationServer. The NavigationMeshGenerator now also has a dummy NavigationMeshGenerator implementation so minimalist Godot can be build without including the module

What is the point of this ? Is it to reduce the executable size ? Because, in terms of features, it makes it a bit weird to have navigation without the possibility to bake things at some point.
Or maybe is it mainly to make it swappable ?

I need tilemap navigation mesh baking in my life 🙇♂
But what do you mean with on the first layer? That's one of the main problems I have currently, I have dozens of layers. Most are painted on the ground, which I have to mark as navigation, so collisions are marked as well in some locations. It would be nice if it could "merge" all layers, just take all collisions together, and bake a navigation mesh from that.

Superseded by https://github.com/godotengine/godot/pull/80796.

Sorry to post this after all this time, but I keep coming back to this problem, and was waiting on this PR. Now it was closed, but the one superseeding it only about 2D. So it seems everything raised about 3D is back to nobody working on it?

@Zylann I removed this from the PR because as you see from the history the PR was always to big and never got reviewed (as is tradition with navigation PRs). The general idea is not abandoned but I simply had no time to get back to it. We already talked in godot dev chat but can continue talk in godot dev navigation channel if you want because I see you made a lot of comments and "issues" on different repos in the past days regarding this and other navigation problems.


[Feature] Support for files (sending images directly and more)

Hey, first of all, thanks for this repo, works well out of the box without needing any work
Would be nice to be able to use the file API to send the file and also add it as an attachment. Here's the best doc I found on it https://birdie0.github.io/discord-webhooks-guide/structure/file.html
But basically it needs to use Content-Type: multipart/form-data so it can't be done with only embeds currently, and I can't simply add a struct because it would also slightly affect how the payload is sent afaik.
The struct that would be handled a bit differently than others would need fields for fileName, fileType and fileExtension at least I think.
namespace Lumpn.Discord
{
    [Serializable]
    public struct File
    {
        public string fileName;

        public string fileType; // example: "image/png"

        public string fileExtension; // exemple: ".png" or "png" depending on the implemention you prefer
    }
}

And then, for it to be attached it would also need to be in the embeded, which can most likely already be done with the current code base

Would be nice to be able to use the file API to send the file and also add it as an attachment. Here's the best doc I found on it https://birdie0.github.io/discord-webhooks-guide/structure/file.html

Oh, nice! I didn't know it was possible to attach files via webhooks.

The struct that would be handled a bit differently than others would need fields for fileName, fileType and fileExtension at least I think.

It was quite a bit more complicated than that, but it works now.
IEnumerator Start()
{
    var img = ImageData.Create(MediaType.PNG, imageBytes);

    var webhook = webhookData.CreateWebhook();
    return webhook.Send(text, img);
}

Nice implementation, easier to use than what I expected, only issue I see is that limits the feature to only working with images. For example you currently can't send a file with ".txt" extension for an error log which is also an important use-case since messages are limited to 2000 characters while files can contain much more data.
You went for a much cleaner image implementation that really takes into account the image type instead of strings for type "image/png", extension ".png" and letting the user figure it out though!

you currently can't send a file with ".txt" extension for an error log which is also an important use-case because messages are limited to 2000 characters, while files can contain much more data.

Fixed. You can now attach text files and ".zip" archives.

you currently can't send a file with ".txt" extension for an error log which is also an important use-case because messages are limited to 2000 characters, while files can contain much more data.

Fixed. You can now attach text files and ".zip" archives.

I think you should be able to send an embed with attachments too?
I'm doing a few tests right now but not sure if it'll work, I'll post the code here if it does

For some reason does not seem I can change a signature or add a method temporarily in an external package, although I can modify what's inside one, I think something like that should work?
        public static IEnumerator Send(this Webhook webhook, Embed embed, FileData[] files)
        {
            var message = new Message
            {
                username = webhook.name,
                embeds = new[] { embed },
                files = files,
            };
            return Send(webhook, message);
        }

I think you should be able to send an embed with attachments too?

I don't think so, no. This is not a limitation of webhooks but of Discord. I've never seen an embed with an attachment on Discord and the official Discord documentation does not mention anything like that.

It does seem to work with the code above and possibly small tweaks, only weird thing is that the file is at the top instead of the bottom, but that's really a detail at this point!

Yes, you can send a message and embeds at the same time. It's highly unusual and nobody ever does that, but the API allows it. It just ends up looking... not great in Discord.
In your case I wouldn't use embeds. Throw the stack trace in the message, attach the log and the screenshot, done.
var screenshot = FileData.Create(MediaType.JPEG, screenshotBytes);
var log = FileData.Create(MediaType.Text, logFileBytes);
webhook.Send(stackTrace, new[] { screenshot, log });

Yeah, probably unusual, although an example of file (image outside) + embeds is shown in the unofficial doc I sent you, not that it looks super good.. Haven't seen much info on how all of this works from the official documentation when I was searching.
Either ways, huge thanks for the fast replies and file updates, I hope more people find this!

Yeah, probably unusual, although an example of file (image outside) + embeds is shown in the unofficial doc I sent you

Sorry, I can't find it. Can you link me to the example you're referencing?

Oh wait, I think I misunderstood you. You said:

I think you should be able to send an embed with attachments too?

And I understood "an embed containing attachments". I don't think embeds can contain attachments, meaning there can be lots of things inside the frame of an embed, like a title, a thumbnail, a footer, and an image, but not an attachment.
But you never said you wanted the attachment to show up inside the box. You just want to send it together with the embed, right?
If so, that's totally doable, and you're right, the code you posted does exactly that. 👍
public static IEnumerator Send(this Webhook webhook, Embed embed, FileData[] files)
{
  var message = new Message
  {
    username = webhook.name,
    embeds = new[] { embed },
    files = files,
  };
  return Send(webhook, message, files);
}

Ah yeah definitely a misunderstanding!
Did mean having an embed AND an attachment in the same payload, although the idea of having the attachment within the embed might be nice, I don't think it's supported or possible.
You can see an example of what I meant here (first example)
https://birdie0.github.io/discord-webhooks-guide/structure/file.html


Add ROS service for executing shell commands

Shortcomings for now:

stderr is not captured
timeout is not implemented

Also thinking about renaming output to something else.

sigh
Where do I even begin?
Okay, let's start with the API.
Almost every language (or should I say, every real language?) has a way to start a subprocess. There's also typically a way to provide something for standard input (typically a string) and capture output from both stdout and stderr. Some APIs even allow you to spawn a shell and execute your commands there - this might be somewhat unorthodox, but it has some uses. Out of those three things, your API does only one. Now, you might say that this API is limited by design, but why not limit it further and do just what you need?
And that brings me to another point: what is the purpose of this?
Why do a weird, incomplete API that will be used in exactly two cases: getting a version and running selfcheck? And it won't even be good at that, because selfcheck will time out and you'll have to fall back to reading /rosout. I'd rather see selfcheck split into two parts: a "backend" that would post all of the diagnostic info in a topic and a "frontend" that would just read the report.
In short, I strongly believe this is both over-engineered and underdeveloped. I am against such an interface and in favor of smaller, simplier services. Want a version? Write a service that will only post a version. Even better, write a service that would post diagnostics and read version from there. We already have at least two ways of getting a shell, do we really need a third, inferior one?

Absolutely not, I never said this is only for getting the version and running selfcheck. Instead, this API is for doing all the stuff in web-based apps for Clover, that cannot be done another way.
Off course you can write a service for every little task and have 1000 nodes running, but you can have simpler solution that covers a lot of cases without the need of writing a custom think.
Consider this like the MAVLink interface  for encapsulating data to the autopilot shell (SERIAL_CONTROL message).

Sending stdin is possible with echo foo | cmd.


Add buy & sell points [Feature Suggestion]

First of all, thank you for this awesome package.
It would be very useful if buy & sell points could be added into the tachart.AddOverlay(), e.g.  a single entry and exit points tachart.NewBuy() and tachart.NewSell() or even the pair tachart.NewBuySell().

You can use "events" for this purpose. Note the small colorful boxes right above the time axis. The example in the README shows how to add events.


Added Vision object parameter to VisionOnToggle.java

I also changed a whenPressed command in RobotContainer

Also, I think the command needs to end immediately and not stay running for this to work properly.

Heads up: This PR is not ready to be merged in. I just wanted to commit what I worked on to see if there are any comments and advice. This is the link to the RioLog where I tested it and got a few errors.


Regex usage

Is there any doc about regex description usage ?  Appreciate for any advice and thanks you very much to offer so great plugin .

Use usual regex in filter fields, for example: ^(srv1|srv2)

See https://github.com/alexanderzobnin/grafana-zabbix/wiki/Usage#filters.