The extension just won't work.

I haven't been able to get it to work right from the time it was woke before it was rebranded to wake.

@0xSimeon can you please try to run the language serve manually on the command line using wake lsp --port PORT? The default port is 65432.
Set the same port in Tools for Solidity VS Code setting named Wake: Port (Tools-for-Solidity.Wake.port is the full setting ID). Restart VS Code to apply the changed port.
Can you please provide a full crash for the language server on the command line (if any)? Thank you!

Hey, @michprev Thanks for your kind response. I tried the wake lsp --port 65432 command and I got this response:
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /Library/Frameworks/Python.framework/Versions/3.12/bin/wake:8 in <module>                        │
│                                                                                │
│   5 from wake.cli.__main__ import main                                                           │
│   6 if __name__ == '__main__':                                                                   │
│   7 │   sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])                         │
│ ❱ 8 │   sys.exit(main())                                                                         │
│   9                                                                                │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/click/core.py:11 │
│ 57 in __call__                                                                                │
│                                                                                │
│   1154 │                                                                                │
│   1155 │   def __call__(self, *args: t.Any, **kwargs: t.Any) -> t.Any:                           │
│   1156 │   │   """Alias for :meth:`main`."""                                                     │
│ ❱ 1157 │   │   return self.main(*args, **kwargs)                                                 │
│   1158                                                                                │
│   1159                                                                                │
│   1160 class Command(BaseCommand):                                                               │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/rich_click/rich_ │
│ command.py:126 in main                                                                           │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/click/core.py:16 │
│ 88 in invoke                                                                                │
│                                                                                │
│   1685 │   │   │   │   super().invoke(ctx)                                                       │
│   1686 │   │   │   │   sub_ctx = cmd.make_context(cmd_name, args, parent=ctx)                    │
│   1687 │   │   │   │   with sub_ctx:                                                             │
│ ❱ 1688 │   │   │   │   │   return _process_result(sub_ctx.command.invoke(sub_ctx))               │
│   1689 │   │                                                                                │
│   1690 │   │   # In chain mode we create the contexts step by step, but after the                │
│   1691 │   │   # base command has been invoked.  Because at that point we do not                 │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/click/core.py:14 │
│ 34 in invoke                                                                                │
│                                                                                │
│   1431 │   │   │   echo(style(message, fg="red"), err=True)                                      │
│   1432 │   │                                                                                │
│   1433 │   │   if self.callback is not None:                                                     │
│ ❱ 1434 │   │   │   return ctx.invoke(self.callback, **ctx.params)                                │
│   1435 │                                                                                │
│   1436 │   def shell_complete(self, ctx: Context, incomplete: str) -> t.List["CompletionItem"]:  │
│   1437 │   │   """Return a list of completions for the incomplete value. Looks                   │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/click/core.py:78 │
│ 3 in invoke                                                                                │
│                                                                                │
│    780 │   │                                                                                │
│    781 │   │   with augment_usage_errors(__self):                                                │
│    782 │   │   │   with ctx:                                                                     │
│ ❱  783 │   │   │   │   return __callback(*args, **kwargs)                                        │
│    784 │                                                                                │
│    785 │   def forward(                                                                          │
│    786 │   │   __self, __cmd: "Command", *args: t.Any, **kwargs: t.Any  # noqa: B902             │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/click/decorators │
│ .py:33 in new_func                                                                               │
│                                                                                │
│    30 │   """                                                                                │
│    31 │                                                                                │
│    32 │   def new_func(*args: "P.args", **kwargs: "P.kwargs") -> "R":                            │
│ ❱  33 │   │   return f(get_current_context(), *args, **kwargs)                                   │
│    34 │                                                                                │
│    35 │   return update_wrapper(new_func, f)                                                     │
│    36                                                                                │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/cli/lsp.py: │
│ 55 in run_lsp                                                                                │
│                                                                                │
│   52 │   config = WakeConfig(local_config_path=context.obj.get("local_config_path", None))       │
│   53 │   config.load_configs()                                                                   │
│   54 │                                                                                │
│ ❱ 55 │   asyncio.run(run_server(config, port))                                                   │
│   56                                                                                │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/asyncio/runners.py:194 in run  │
│                                                                                │
│   191 │   │   │   "asyncio.run() cannot be called from a running event loop")                    │
│   192 │                                                                                │
│   193 │   with Runner(debug=debug, loop_factory=loop_factory) as runner:                         │
│ ❱ 194 │   │   return runner.run(main)                                                            │
│   195                                                                                │
│   196                                                                                │
│   197 def _cancel_all_tasks(loop):                                                               │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/asyncio/runners.py:118 in run  │
│                                                                                │
│   115 │   │                                                                                │
│   116 │   │   self._interrupt_count = 0                                                          │
│   117 │   │   try:                                                                               │
│ ❱ 118 │   │   │   return self._loop.run_until_complete(task)                                     │
│   119 │   │   except exceptions.CancelledError:                                                  │
│   120 │   │   │   if self._interrupt_count > 0:                                                  │
│   121 │   │   │   │   uncancel = getattr(task, "uncancel", None)                                 │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/asyncio/base_events.py:664 in  │
│ run_until_complete                                                                               │
│                                                                                │
│    661 │   │   if not future.done():                                                             │
│    662 │   │   │   raise RuntimeError('Event loop stopped before Future completed.')             │
│    663 │   │                                                                                │
│ ❱  664 │   │   return future.result()                                                            │
│    665 │                                                                                │
│    666 │   def stop(self):                                                                       │
│    667 │   │   """Stop running the event loop.                                                   │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/cli/lsp.py: │
│ 19 in run_server                                                                                │
│                                                                                │
│   16                                                                                │
│   17                                                                                │
│   18 async def run_server(config: WakeConfig, port: int) -> None:                                │
│ ❱ 19 │   from wake.lsp.server import LspServer                                                   │
│   20 │                                                                                │
│   21 │   async def client_callback(                                                              │
│   22 │   │   reader: asyncio.StreamReader, writer: asyncio.StreamWriter                          │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/lsp/server. │
│ py:28 in <module>                                                                                │
│                                                                                │
│     25 from wake.utils import StrEnum                                                            │
│     26                                                                                │
│     27 from ..config import WakeConfig                                                           │
│ ❱   28 from .commands import (                                                                   │
│     29 │   generate_cfg_handler,                                                                 │
│     30 │   generate_imports_graph_handler,                                                       │
│     31 │   generate_inheritance_graph_handler,                                                   │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/lsp/command │
│ s/__init__.py:1 in <module>                                                                      │
│                                                                                │
│ ❱ 1 from .generate_control_flow_graph import generate_cfg_handler                                │
│   2 from .generate_imports_graph import generate_imports_graph_handler                           │
│   3 from .generate_inheritance_graph import generate_inheritance_graph_handler                   │
│   4 from .generate_linearized_inheritance_graph import (                                         │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/lsp/command │
│ s/generate_control_flow_graph.py:9 in <module>                                                   │
│                                                                                │
│     6 from wake.core import get_logger                                                           │
│     7 from wake.ir import FunctionDefinition, ModifierDefinition, StatementAbc                   │
│     8 from wake.lsp.common_structures import DocumentUri                                         │
│ ❱   9 from wake.lsp.context import LspContext                                                    │
│    10 from wake.lsp.exceptions import LspError                                                   │
│    11 from wake.lsp.protocol_structures import ErrorCodes                                        │
│    12 from wake.lsp.utils import uri_to_path                                                     │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/lsp/context │
│ .py:12 in <module>                                                                               │
│                                                                                │
│    9 from ..utils.openzeppelin import get_contracts_package_version                              │
│   10 from .features.diagnostic import diagnostics_loop                                           │
│   11 from .lsp_compiler import LspCompiler                                                       │
│ ❱ 12 from .lsp_parser import LspParser                                                           │
│   13                                                                                │
│   14 if TYPE_CHECKING:                                                                           │
│   15 │   from .server import LspServer                                                           │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/wake/lsp/lsp_par │
│ ser.py:18 in <module>                                                                            │
│                                                                                │
│    15 │   Union,                                                                                │
│    16 )                                                                                │
│    17                                                                                │
│ ❱  18 from tree_sitter import Parser                                                             │
│    19 from tree_sitter_solidity import get_parser                                                │
│    20                                                                                │
│    21 from .common_structures import (                                                           │
│                                                                                │
│ /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/tree_sitter/__in │
│ it__.py:4 in <module>                                                                            │
│                                                                                │
│    1 """Python bindings for tree-sitter."""                                                      │
│    2                                                                                │
│    3 from ctypes import cdll, c_void_p                                                           │
│ ❱  4 from distutils.ccompiler import new_compiler                                                │
│    5 from distutils.unixccompiler import UnixCCompiler                                           │
│    6 from os import path                                                                         │
│    7 from platform import system                                                                 │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
ModuleNotFoundError: No module named 'distutils'

I added the port 65432 to the Tools for solidity vscode setting and I still got similar error message:
Connecting to running 'wake' server on port 65432
Timed out waiting for port 65432 to open.
[Error - 05:16:28] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 05:16:28] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Info  - 05:16:28] Connection to server got closed. Server will restart.
[Error - 05:16:28] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 05:16:28] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 05:16:28] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 05:16:28] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 05:16:28] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 05:16:28] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 05:16:28] Stopping server failed
Error: Previous start failed. Can't restart server.

@0xSimeon thank you for the log. The issue should be fixed in eth-wake 4.3.0 and Tools for Solidity 1.11.3 (which auto-installs eth-wake 4.3.0). It was caused by the distutils Python package not being pre-installed with Python 3.12.

Thank you, @michprev.
Should I install distutils and try again? Or wait for the new update?

The new update should be available now, feel free to try it out.

The new update should be available now, feel free to try it out.

Thanks for the prompt response, once again @michprev
I added the updated the tools for solidity extension to get the new update. then check the output logs again and got this:
Connecting to running 'wake' server on port 65432
Timed out waiting for port 65432 to open.
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Info  - 22:31:26] Connection to server got closed. Server will restart.
[Error - 22:31:26] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Info  - 22:31:26] Connection to server got closed. Server will restart.
[Error - 22:31:26] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Info  - 22:31:26] Connection to server got closed. Server will restart.
[Error - 22:31:26] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Info  - 22:31:26] Connection to server got closed. Server will restart.
[Error - 22:31:26] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 22:31:26] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 22:31:26] The Tools for Solidity server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 22:31:26] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 22:31:26] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097

I uninstalled, did a clean install, unistalled again and reinstalled. it just doesn't work.

@0xSimeon I'm sorry the last update didn't solve the issue.
Can you please repeat the process with launching the language server in the terminal, setting the port in VS Code and sending the log from the terminal?

Thanks for your prompt response even on christmas. I'm certainly impressed. Thanks for helping me out on this.

As a workaround, you can try a different version of Python. However, I will be glad if you help me track down the issue. Unfortunately, I will need the bottom-most part of the exception, not the top part.

Oh and Merry Christmas to you too! 🎄 Somehow I skipped reading that when I saw the error log 😅

As a workaround, you can try a different version of Python. However, I will be glad if you help me track down the issue. Unfortunately, I will need the bottom-most part of the exception, not the top part.

Hey, @michprev -sorry I got caught up in the festivities. here you go:
Connecting to running 'wake' server on port 65432
Timed out waiting for port 65432 to open.
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Info  - 15:06:44] Connection to server got closed. Server will restart.
[Error - 15:06:44] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Info  - 15:06:44] Connection to server got closed. Server will restart.
[Error - 15:06:44] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Info  - 15:06:44] Connection to server got closed. Server will restart.
[Error - 15:06:44] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Info  - 15:06:44] Connection to server got closed. Server will restart.
[Error - 15:06:44] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Client Tools for Solidity: connection to server is erroring. Shutting down server.
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110766
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at f.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:130386)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:131172)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 15:06:44] Stopping server failed
Error: Previous start failed. Can't restart server.
	at w.$start (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166382)
	at w.shutdown (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163453)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:163228)
	at w.stop (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:321883)
	at w.handleConnectionError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:168806)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:167633
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:166799
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at /Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:110701
	at r.invoke (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:118387)
	at o.fire (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:119152)
	at m.fireError (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:126867)
	at Socket.<anonymous> (/Users/simeonudoh/.vscode/extensions/ackeeblockchain.tools-for-solidity-1.11.3/dist/extension.js:1:128473)
	at Socket.emit (node:events:525:35)
	at Socket.emit (node:domain:489:12)
	at emitErrorNT (node:internal/streams/destroy:151:8)
	at emitErrorCloseNT (node:internal/streams/destroy:116:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Error - 15:06:44] The Tools for Solidity server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 15:06:44] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Tools for Solidity client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097
[Error - 15:06:44] Restarting server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097

Hey @0xSimeon, unfortunately, I need the bottom-most part of the log from your command line, not from VS Code. I.e., this log https://github.com/Ackee-Blockchain/tools-for-solidity-vscode/issues/72#issuecomment-1869130804, but the bottom part.
The instructions are still the same as in https://github.com/Ackee-Blockchain/tools-for-solidity-vscode/issues/72#issuecomment-1866421815.

for me does not work too


Fix getting info whether playbook failed or succeeded

Where/how is the github status set?

In the workflow, by using a third-party GitHub action myrotvorets/set-commit-status-action
See how it's used firstly to set to pending, then to set as skipped for skipped OSes, and then for the results with URL to logs https://github.com/linux-system-roles/network/blob/main/.github/workflows/tft.yml#L117
The code I change here is to set the name of log files so that it's visible which playbooks failed.
I don't like how workflows that fail setup state and don't have any logs still leave a URL that returns 404. This is a subject for change.

In the workflow, by using a third-party GitHub action myrotvorets/set-commit-status-action See how it's used firstly to set to pending, then to set as skipped for skipped OSes, and then for the results with URL to logs https://github.com/linux-system-roles/network/blob/main/.github/workflows/tft.yml#L117 The code I change here is to set the name of log files so that it's visible which playbooks failed.

How/where is ${{ job.status }} set https://github.com/linux-system-roles/network/blob/main/.github/workflows/tft.yml#L174 ?
The reason I ask is that the PR changes the behavior of the test.  Using command || result=FAIL will cause rlRun to always return 0 i.e. it will never fail or report an error.
-        rlRun "DEFAULT_LOG_PATH=$LOGFILE ansible-playbook -i $inventory $skip_tags $tests_path$test_playbook -vv" 0 "Test $test_playbook with ANSIBLE-$ANSIBLE_VER"
+        rlRun "ANSIBLE_LOG_PATH=$LOGFILE ansible-playbook -i $inventory $skip_tags $tests_path$test_playbook -vv || result=FAIL" 0 "Test $test_playbook with ANSIBLE-$ANSIBLE_VER"

try it - if false || result=fail; then echo here; fi - even though false returned a failure code, using the || result=fail makes the pipeline return 0 - success

I don't like how workflows that fail setup state and don't have any logs still leave a URL that returns 404. This is a subject for change.

Right, I switched success and fail so that the inital rc overrides only in the state of success, so that the rc remains 0.

Em, no it doesn't work, doesn't write to file.

I think &> $LOGFILE && result=SUCCESS works fine


Added new Regex for prosiebensat1 Extractor Description. Fixes #11810

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.
Added new Regex for prosiebensat1 Extractor Description. Fixes #11810

Hopefully this one is exactly like you wanted it. Thanks for you patience and your help!

$ youtube-dl -vF http://www.prosieben.de/tv/circus-halligalli/videos/218-staffel-2-episode-18-jahresrueckblick-ganze-folge
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-vF', 'http://www.prosieben.de/tv/circus-halligalli/videos/218-staffel-2-episode-18-jahresrueckblick-ganze-folge']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.01.31
[debug] Git HEAD: 2b2d5d319
[debug] Python version 3.6.0 - Linux-4.9.6-1-ARCH-x86_64-with-arch
[debug] exe versions: ffmpeg 3.2.2, ffprobe 3.2.2, rtmpdump 2.4
[debug] Proxy map: {}
[prosiebensat1] tv/circus-halligalli/videos/218-staffel-2-episode-18-jahresrueckblick-ganze-folge: Downloading webpage
[prosiebensat1] 2104602: Downloading videos JSON
[prosiebensat1] 2104602: Downloading sources JSON
[prosiebensat1] 2104602: Downloading urls JSON
[prosiebensat1] 2104602: Downloading f4m manifest
[prosiebensat1] 2104602: Downloading urls JSON
[prosiebensat1] 2104602: Downloading m3u8 information
[prosiebensat1] 2104602: Downloading urls JSON
[prosiebensat1] 2104602: Downloading MPD manifest
[prosiebensat1] 2104602: Downloading urls JSON
Traceback (most recent call last):
  File "<string>", line 23, in <module>
  File "/home/yen/Projects/youtube-dl/youtube_dl/__init__.py", line 451, in main
    _real_main(argv)
  File "/home/yen/Projects/youtube-dl/youtube_dl/__init__.py", line 441, in _real_main
    retcode = ydl.download(all_urls)
  File "/home/yen/Projects/youtube-dl/youtube_dl/YoutubeDL.py", line 1791, in download
    url, force_generic_extractor=self.params.get('force_generic_extractor', False))
  File "/home/yen/Projects/youtube-dl/youtube_dl/YoutubeDL.py", line 694, in extract_info
    ie_result = ie.extract(url)
  File "/home/yen/Projects/youtube-dl/youtube_dl/extractor/common.py", line 369, in extract
    return self._real_extract(url)
  File "/home/yen/Projects/youtube-dl/youtube_dl/extractor/prosiebensat1.py", line 427, in _real_extract
    return self._extract_clip(url, webpage)
  File "/home/yen/Projects/youtube-dl/youtube_dl/extractor/prosiebensat1.py", line 380, in _extract_clip
    description = self._og_search_description(webpage, fatal=False)
  File "/home/yen/Projects/youtube-dl/youtube_dl/extractor/common.py", line 781, in _og_search_description
    return self._og_search_property('description', html, fatal=False, **kargs)
TypeError: _og_search_property() got multiple values for keyword argument 'fatal'

I forgot _og_search_property already uses fatal=False, so you don't need to pass it.

@yan12125 I've hit the same problem. Sorry, my mistake. Should have tested even such a simple change :-(
All corrected and working now.

Thank you for your patience and your help @yan12125 !


Fix incorrect info if model has custom modules

Fix incorrect params number if model has custom modules
Fix incorrect model size if model has custom modules
Add a switch for printing the model structure
Add support for half precision

Any updates on this? I could take it up if required

@sksq96 It would be great if you have a look


Update the phpunit workflow to start testing on PHP 8.1

This used a experimental flag in the matrix, see: https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error
Type: testing update
Issue: -
Breaking change: no

I suggest we first enable it on PDepend, then we make them pass before we merge:
https://github.com/pdepend/pdepend/pull/594


RuntimeSchema.createFrom occurrence NullPointerException

schema = RuntimeSchema.createFrom(cls);
cls is Object.class
Why is a NullPointerException exception？
How to deal with？

You should directly call that.  Remember that the classes passed to that function must be user-defined pojos and not jdk core classes.


[WIP] Add configuration and enclave dependencies for local_attestation

Signed-off-by: Alin Gabriel Serdean<EMAIL_ADDRESS>

Oh, I had WIP here, feel free to take it: https://github.com/Microsoft/openenclave/commit/358b910614af655d6411be7249878c5d07fe3098

Oh, I had WIP here, feel free to take it: 358b910

Sorry @andschwa I had no idea you were working on this also!
I can close this PR if you want to tackle the issue.

@aserdean Nope, you're good, I wasn't, I was just investigating and that's as far as I got. All yours!

@andschwa 🙇

@aserdean Is this still WIP?


Not working: attempt to get URL to drawingsList.json adn download fro…

…m client
@obergrd @erymski I tried to do it the same way we download BOM.json, but I'm missing a piece somewhere.
There's also a difference from BOM.json, as the drawingsList.json is not dependent on a hash and is stored in attributes (e.g. "attributes/Wheel/drawingsList.json", but the url in MakeProjectDTO looks like "drawingslist/Wheel"
Any help appreciated.

I think we should simply return drawings list along with other basic data.  I'll change it

I changed the code, so the list if locally cached now, and URL to "static file" is passed to the client. Seems to work now:

I decided to stop, and don't spending time on passing array directly.  Maybe later in the sprint.

Just in case - you had to reinitialize projects now (or manually delete cache dir)


chore: bdd-nh-1576596609 to 0.0.1

chore: Promote bdd-nh-1576596609 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Connect to Discord Websocket

Once, the intial gateway endpoint is called, we need to create a websoscket connection to discord so we can have constant communication
https://github.com/denoland/deno/blob/9837d324a7c3f5e1c850dadabfd670edad4aa85b/std/ws/README.md

Done


Microsoft.Azure.Functions.Worker.ApplicationInsights GA Released?

I see a stable release for Microsoft.Azure.Functions.Worker.ApplicationInsights package in Nuget.
--prerelease mentioned in README !!!
https://github.com/Azure/azure-functions-dotnet-worker/blob/79779b64a15265bb3976ac11297c510df44f1b50/src/DotNetWorker.ApplicationInsights/README.md?plain=1#L13C61-L13C61

The stable package was just released. The documentation didn't have a chance to catch up yet.

@renjums, slow your horses 🙂

I've got PRs out for the readme and for the Microsoft Learn docs to fix this.


Add Crypto Utility files that use Python Crypto libraries instead of

…Avalon Crypto functions.

used pycryptodomex and ecdsa libraries

Signed-off-by: divya<EMAIL_ADDRESS>

Can you re-base PR with latest master, it will turn CI job to green.

@divyataori Can you please move the existing openssl based crypo files i.e common/crypto_utils to common/crypto_utils_openssl. This will give the option to choose between pythoncryptodomex and openSSL based implementation if we need to. This PR makes pythoncryptodomex as the default which is ok.

I have copied the crypto files to a new directory. Couldn't do a "git mv" , because my commit was then getting applied to -  common/crypto_utils_openssl

@divyataori Can you please move the existing openssl based crypo files i.e common/crypto_utils to common/crypto_utils_openssl. This will give the option to choose between pythoncryptodomex and openSSL based implementation if we need to. This PR makes pythoncryptodomex as the default which is ok.

This can be done in a separate PR. I'll approve this PR now and merge


Add high level description to e2e tests

Add human readable description of e2e tests

/remove-lifecycle stale

/assign @kashifest

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/lgtm

/test-centos-e2e-integration-main

/retitle 🌱 Add high level description to e2e tests

/hold
to see if we can address the comments with the same PR (feel free to unhold if you want to do them in a follow-up)

/hold

/hold cancel

Thanks @mboukhalfa, looks good. I also noticed, few other e2e tests we have (specifically: IP reuse, ~inspection~) is not covered in this PR while it could be beneficial to add the descriptions for those tests as well. That being said, it is not a blocker and can be done in a follow-up if needed.

Yeah let's do it in follow up


Directory structure

Hello and thanks for this great work !
I am following your procedure, I downloaded the Standford dataset and I am wondering a few things:

Do we have to manually create your directory structure with the files from the datasets or do you have a way to automate it ?
Same for .npy files since the dataset offers .txt files ?

Thanks

The file tools/prepare_s3dis.py does resolve this issue ! My bad !


Feature Request – Full Width Main Area, Nested Layouts

http://www.concrete5.org/community/forums/5-7-discussion/feature-suggestion-full-width-content/#684207

Left a suggestion here: http://www.concrete5.org/community/forums/5-7-discussion/feature-suggestion-full-width-content/

:+1:

:+1:

:+1:


How to add dynamic url to the menu?

I tried to use dynamic url to the menu
like authentic user profile : /user/12.
How can I do that ? do I need to edit config/adminlte.php file or else?
Thanks.

Ohhh I missed Menu configuration at runtime.
solved


updated some tests for tech insights

Fleshing out the tests as part of #20409
Interestingly the larger of the test files never ran against postgres at all. The migrations explicitly sets the dateTime resolution to zero, meaning only whole seconds. Therefore the test turned out to need some pretty hefty tweaking - and some of the tests are still disabled because the old code didn't take time zone differences into account.
@Xantier could you perhaps look into re-enabling those other tests separately?

Therefore the test turned out to need some pretty hefty tweaking - and some of the tests are still disabled because the old code didn't take time zone differences into account.

@freben What were these modifications?


docker service update api throwing mismatched Runtime and *Spec fields

Hello, I'm currently attempting to run an update action on an existing service. Before modifying anything i'm trying to get a 200 response from the update api. On all of my calls i get the following response from docker
mismatched Runtime and *Spec fields

I've included the docker version on the object per other threads. Here is my code
            // https://forums.docker.com/t/solved-force-update-a-service-with-the-rest-api-does-not-work-as-expected/62779/2

            let serviceManager: Dockerode.Service = await this.swarm.docker.getService(serviceName)
            const inspected: ServiceInfoListItem = await serviceManager.inspect();
            console.log('inspected: ', inspected.Version);
            console.log('inspected: ', inspected.CreatedAt);
            console.log('inspected: ', inspected.Spec.Networks);

            // inspected.Spec.Networks = [{Target: this.template.Name}];
            inspected.Spec.TaskTemplate.ForceUpdate = 1
            inspected.version = inspected.Version.Index;

            let response: { Warnings?: string; } = await serviceManager.update(inspected);

I get the following output:
inspected:  { Index: 262 }
inspected:  2019-06-21T14:51:34.011603399Z
inspected:  undefined
{ Error: (HTTP code 400) unexpected - mismatched Runtime and *Spec fields
     at /app/node_modules/docker-modem/lib/modem.js:257:17
     at getCause (/app/node_modules/docker-modem/lib/modem.js:287:7)
     at Modem.buildPayload (/app/node_modules/docker-modem/lib/modem.js:256:5)
     at IncomingMessage.<anonymous> (/app/node_modules/docker-modem/lib/modem.js:232:14)
     at IncomingMessage.emit (events.js:187:15)
     at IncomingMessage.EventEmitter.emit (domain.js:441:20)
     at endReadableNT (_stream_readable.js:1094:12)
     at process._tickCallback (internal/process/next_tick.js:63:19)
   reason: undefined,
   statusCode: 400,
   json: { message: 'mismatched Runtime and *Spec fields' } } Promise {
   <rejected> { Error: (HTTP code 400) unexpected - mismatched Runtime and *Spec fields
       at /app/node_modules/docker-modem/lib/modem.js:257:17
       at getCause (/app/node_modules/docker-modem/lib/modem.js:287:7)
       at Modem.buildPayload (/app/node_modules/docker-modem/lib/modem.js:256:5)
       at IncomingMessage.<anonymous> (/app/node_modules/docker-modem/lib/modem.js:232:14)
       at IncomingMessage.emit (events.js:187:15)
       at IncomingMessage.EventEmitter.emit (domain.js:441:20)
       at endReadableNT (_stream_readable.js:1094:12)
       at process._tickCallback (internal/process/next_tick.js:63:19)
     reason: undefined,
     statusCode: 400,
     json: { message: 'mismatched Runtime and *Spec fields' } } }

This was caused by passing inspect instead of inspect.Spec
            let response: { Warnings?: string; } = await serviceManager.update(inspected.Spec);


PENV-328: test with mock: get jetDrop from DB

- What I did
Test that sends data to heavymock and then checks if db contains jetDrops
- How I did it
- How to verify it
run tests
- Description for the changelog

Codecov Report

Merging #29 into master will decrease coverage by 0.01%.
The diff coverage is 76.00%.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
- Coverage   61.29%   61.28%   -0.02%
==========================================
  Files          29       29
  Lines        1217     1232      +15
==========================================
+ Hits          746      755       +9
- Misses        404      410       +6
  Partials       67       67

Impacted Files
Coverage Δ

testutils/generators.go
88.57% <66.66%> (-8.04%)
:arrow_down:

etl/extractor/mainnet_impl.go
65.95% <100.00%> (ø)

test/heavymock/import_records_impl.go
88.88% <100.00%> (+3.17%)
:arrow_up:

Continue to review full report at Codecov.

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


Empty yulp file causes error

An empty yulp file causes an error: https://github.com/FuelLabs/yulp/blob/37eceb72b696c0e04b209781a11da27fa7a3c153/src/index.test.js#L44
This is making CI fail.

Old compiler work. Tests are updated.


How does weechat integration work?

So I noticed in the gif at the beginning README that it shows using it in weechat. However, I couldn't find instructions on how to set up weechat integration. Could anyone point me to it?

Yeah I understand that. It just so happens that I have been using weechat and would love to get it working.

Hey, do I need to install weechat in order to make the bot work?

I think that what karx1 means is that there is no "Weechat integration", the author of the gif is simply just using the IRC client called Weechat when showing off the IRC part of the bot. You could use any IRC client such as mIRC or irssi to do the same thing.


fix: Branch eval quota fixes for Zig master

The branch quote differs based on the usage of the library. See https://github.com/zigtools/zig-lsp-codegen/issues/16. According to that issue, 2000 is not enough for ZLS.

superseded by 193a210ebe4a090a6f1bf1cb538375b56472688d. Calling @setEvalBranchQuota inside StaticStringMap doesn't work when compiling ZLS.


BZ 63636: Context#findRoleMapping() never called in RealmBase#hasRole()

Please have also an eye on the test. It passes as expected and it fails when I modify it, but I am not certain whether I have build the test they way it should be done.
If all is fine, I'll backport to 8.5.x and 7.0.x as long as the APIs are available.

Tests for master and 8.5.x pass. Ready to merge. Will then backport to 7.0.x if possible.

@markt-asf I have now added proper tests. Please have a look. If they are as expected, I'll rebase, squash, merge and backport.

All tests pass on Tomcat 9.0.x.

Test LGTM.


Minify and autoprefix for scss files imported as modules

In a react file, we can import an scss file as a module. import './myStyles.scss'; will import the styles and inject them as a <style/> tag in the head thanks to the ecmascript package. And the meteor-scss package will transpile scss to css and manage the scss imports.
Great, it works.
But how do we minify and autoprefix those modules ? I tried to add seba:minifiers-autoprefixer without luck.

Great.
Although, minification and source mapping happen. But I don't see the auto-prefixing. I ask on the meteor issue

are you using seba:minifiers-autoprefixer ?
The default meteor minifier doesn't have auto-prefixing

Yep. If I put an scss file in the /client folder, it is auto prefixed and included in the css bundle. But when I import them as a js module, they are not.

Closing, since this is to be solved by Meteor instead of this package


Add additional Blazor migration guidance for upgrading to .NET 8

We've received some feedback that our Blazor migration guidance is too minimalistic and doesn't cover all of the related concerns:

Apps using lazy loading were impacted by the change to webcil, which changed the assembly extension from .dll to .wasm
We changed our authentication guidance in .NET 8, but we didn't give detailed instructions on how to upgrade

Why does the <title> has to be removed? This ensured a consistent title for the web app across all the pages.

@SeanFeldman ... The App component of a BWA doesn't set the page title that way ...
https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorWeb-CSharp/BlazorWeb-CSharp/Components/App.razor
Page titles are specified via the HeadOutlet/PageTitle components ...
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/control-head-content?view=aspnetcore-8.0#control-head-content-in-a-razor-component
I'll cross-link that guidance for that change when I reach this issue.
It might still be possible to use a <title> tag for an app-wide fallback (possibly depending on ordering, too), but I don't recall if there are artifacts of using it ... i.e., 🐉😈. The idea here is to convert the app to a BWA, not try to maintain hosted WASM solution conventions, so that's why we're angling to have devs drop it for the migration guidance. It truly is a conversion to a BWA, not merely an updated/upgraded hosted WASM solution. HOWEVER, note that you can apply a PageTitle component to your layout to get it for all of the components that don't specify their own PageTitle component.
For example in Components/Layout/MainLayout.razor ...
<PageTitle>My layout title</PageTitle>

... any component without a page title specified will get that one. When I reach this issue, I'll see if we mention this fact in the Control <head> content article. If not, I'll make a remark on it there.

@danroth27 ...

We changed our authentication guidance in .NET 8, but we didn't give detailed instructions on how to upgrade

Step-by-step is possible but challenging to resolve going from hosted WASM to BWA. It's just so radically different, and there would be quite a bit of step-by-step guidance to provide, which would take a minute to work out and type out. The simpler approach is to direct users to the BWA+OIDC article, and they're essentially going to re-implement security via that guidance with the help of the sample apps. If you really want step-by-step in the Migration article, you'll need to prioritize the work for me ... I have issues coming out of my 👂👂 right now, and it's going to factor into resolving this pile of backlogged non-.NET 8 issues that I was planning to address over the next several weeks. Also, let me know if we're migrating user to the non-BFF pattern with any APIs in the BWA's server project. It will take even longer if you want conversion to the BFF pattern.

We should consider creating a new Migration node article if we're going to place that much guidance. I can take the current hosted WASM to BWA piece we have now for it, then I can add the auth conversion steps to it in the new article.

@guardrex, another missing guidance is about anti-forgery. The documentation shows half of what needs to be done, omitting the required builder.Services.AddAntiforgery() part

@SeanFeldman ... When AddRazorComponents is called, the antiforgery services are added automatically ...
https://github.com/dotnet/aspnetcore/blob/main/src/Components/Endpoints/src/DependencyInjection/RazorComponentsServiceCollectionExtensions.cs#L40
I'll make a note of it in passing in the migration guidance ... and I know at least one other spot in the Blazor security docs where a remark on this should appear. I'll also check our forms security content to see if a remark should appear there as well. Thanks for mentioning it. 🍻

Coping over my remarks on the auth situation ...

... it sounds like some of the auth targets for migration are still in the works. Later, I'll need clarification on the exact starting points.
Examples of scenarios that we didn't cover in the Blazor node:

Duende backend for Blazor WASM, which I suppose is the 7.0 starting point for the 8.0 Standalone with Identity (MapIdentityApi) article+sample target.
Blazor Server+Duende, which I suppose is the 7.0 starting point for the 8.0 BWA+OIDC (non-BFF?) article+sample.
Blazor Server+Entra, which is obviously the 7.0 starting point for 8.0 BWA+Entra. IIRC, the Azure folks were going to put up samples for BWA+Entra and BWA+B2C. I see you're saying now that Halter will create the target (at least for Entra), so I'll just need to start with a Blazor Server+Entra app.

I think that WASM+Entra/B2C doesn't require more than package and TFM changes, which is already covered by the existing migration guidance.

Just had to go through the Blazor WebAssembly hosted + EntraID documentation and will be blunt - not a pleasant experience at all. The whole business with "go to the repos, switch to a tag, go figure what files you need to look at is falling apart if you're not using the latest .NET. In my case it was .NET 8 and one of the files I just completely failed to locate to see what it looks like. That part of the documentation/guidance has to be revisited. Imagine a car manual sending the reader to the junkyard to look up a car of a specific year to see how things are installed.

@SeanFeldman ... We don't work closed issues/PRs. Open a new issue, and plz be more specific about what file you couldn't find.

@guardrex, this issue is opened, isn't it?

My bad, @SeanFeldman ... I was looking at my phone's tiny screen and didn't see that it was open.
What exactly are you upgrading from and to? Second, what file are you talking about?


feat: new onboarding

Describe the changes you have made in this PR
Some new designs for the onboarding flow that help users explore available options:

we need to adopt this for smaller screens as well


Direct assignment of Variable fails

When directly assigning Variable to main state:
def absorb(self):
    new_val = core.IntegerVariable()
    self.main.state = new_val

it shows CUDA compiler error:
kernel.cu(174): error: expected an expression

The workaround for this case is:
def absorb(self):
    new_val = core.IntegerVariable()
    self.main.state = new_val + 0

Howewer, it also don't work as expected, see details in bug #34.

It is now possible to assign Variable subclasses directly to state properties.
Reason: code class variable was empty for Variable instances. It is overridden with a getter returning variable name. Also, a dummy setter is added to prevent changing of necessary code.


Bug report

Bug description
I am trying to install OpenFAST through conda-forge. I created a new environment and activated it. Then ran the install command and it says
BEGINNING OF ERROR
PackagesNotFoundError: the following packages are not available from current channels: -openfast
Current channels:

https://conda.anaconda.org/conda-forge/win-64
https://conda.anaconda.org/conda-forge/noarch
https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch
END OF ERROR

To Reproduce
conda create -n openfast_env
conda activate openfast_env
conda install -c conda-forge openfast #this is where the error above happens
Windows 10 pro OS
Using anaconda prompt

@anishas26 OpenFAST is not currently available for Windows from conda-forge. We hope to provide this in the future. Until we can get OpenFAST working with conda-forge, please download the Windows version from Releases.

Closing due to lack of response, feel free to reopen.


RuntimeError: ws2811_init failed with code -3 (Hardware revision is not supported)

Hello,
I am struggling to resolve a 'Hardware revision is not supported' error message.
I have installed rpi_ws281x python on a raspberry PI compute module 4 (revision c03141).
The install seems to work successfully using the following command:
sudo pip install rpi_ws281x
However when it comes to running one of the standard examples I get the following error:
RuntimeError: ws2811_init failed with code -3 (Hardware revision is not supported)
Python version: 3.9.2
Python3 version: 3.9.2
Any help / tips will be greatly received :-)
Jon

What CM4 exactly? According to rpihw.c, these are the currently supported CM4´s:
// Compute Module 4
//
{
    .hwver = 0xa03140,
    .type = RPI_HWVER_TYPE_PI4,
    .periph_base = PERIPH_BASE_RPI4,
    .videocore_base = VIDEOCORE_BASE_RPI2,
    .desc = "Compute Module 4 v1.0 eMMC"
},
{
    .hwver = 0xb03140,
    .type = RPI_HWVER_TYPE_PI4,
    .periph_base = PERIPH_BASE_RPI4,
    .videocore_base = VIDEOCORE_BASE_RPI2,
    .desc = "Compute Module 4 v1.0 Lite"
},
{
    .hwver = 0xc03140,
    .type = RPI_HWVER_TYPE_PI4,
    .periph_base = PERIPH_BASE_RPI4,
    .videocore_base = VIDEOCORE_BASE_RPI2,
    .desc = "Compute Module 4 v1.0 WiFi"
},
{
    .hwver = 0xd03140,
    .type = RPI_HWVER_TYPE_PI4,
    .periph_base = PERIPH_BASE_RPI4,
    .videocore_base = VIDEOCORE_BASE_RPI2,
    .desc = "Compute Module 4 v1.0 WiFi 8GB"
},

I am currently using this with a no Wifi, 4gb emmc and 4gb ram version of the CM4

See https://github.com/jgarff/rpi_ws281x/issues/483 for more details.
Newer Raspberry Pis have different configuration values not added into that file. When you buy a new Raspberry Pi and it has this new configuration, it will throw this error.

Any chance to get an updated version of the Python module? jgarff/rpi_ws281x just released a new version, including support for multiple models.

It's on my list. I did the rpi_ws281x release :grimacing:

It's on my list. I did the rpi_ws281x release 😬

Hi all, is this update still on the pipeline? :)

@Gadgetoid We would really appreciate an update here because we are stuck with the jgarff/rpi_ws281x#483 for some time now, and it starts blocking things.

Is this fixed with v5.0.0?

Note- this will not fix Pi 5.
See: https://github.com/jgarff/rpi_ws281x/issues/528


Dynamic Update with Subclasses of Component : Not necessary to add super class Components Traits

When a Component is subclassed by another component, it is not necessary to re-add existing super classe Traits.

Code proposition :
rebuildComponent: aComponent traitsAdding: aList
| classes |
classes := aComponent allSuperclasses reverse.
classes remove: Object; remove: ProtoObject.
classes add: aComponent class.

aList do: [:e | | toBeAddedTrait |
	e ifNotNil:[
		toBeAddedTrait := e.
		"Cannot add the traits if already present"
		classes do: [ :c |
			(c traitComposition includesTrait: e) ifTrue:[toBeAddedTrait := nil].
		].
		toBeAddedTrait ifNotNil:[aComponent addToComposition: toBeAddedTrait].
	].
].

Write a test to :

Create a component (Component 1)
Create a component subclasse (Component 2)
Adding a Trait 1 in the Component 1, and set a ComponentType with a complete contract
Adding a Trait 2 in the Component 2
Check traits structure between Component 1 and Component 2 : Component 2 should have only Trait 2 in the class structure


 It does not update spotbugs because that wasn't a free update, so I decided it was best to keep the changes as minimal as possible, and update that one more intentionally.

It does! I even verified it!


cant access edit functions for role and admin links

BadMethodCallException in Builder.php line 2440: Call to undefined method Illuminate\Database\Query\Builder::lists()

This seems to be related to Laravel 5.3.
I just found this package and also were unable to edit any records.
lists was depreciated, and as far as I know, pluck should be used instead...


su.litvak.chromecast.api.v2.ChromeCastException: Waiting for response timed out

Hello, i try send url to the chromecast.
I know the Chromecast ip address.
Because i don't want my UI freeze i have done an task class.
This is the code
          ChromeCast chromecast = new ChromeCast(ip);
            Status status = null;
            try {
                status = chromecast.getStatus();

            } catch (IOException ex) {
                Logger.getLogger(CoreAction.class.getName()).log(Level.SEVERE, null, ex);
            }
            System.out.println(chromecast.getName());
            System.out.println(status.toString());
            try {
                chromecast.load(qrCodeUrl);
                chromecast.disconnect();
            } catch (IOException ex) {
                Logger.getLogger(CoreAction.class.getName()).log(Level.SEVERE, null, ex);
            }

I guess i have done something wrong because an exeption is trigger.
date program.TaskQrCode sendQrCodeToCCast
GRAVE: null
su.litvak.chromecast.api.v2.ChromeCastException: Waiting for response timed out
	at su.litvak.chromecast.api.v2.Channel.send(Channel.java:393)
	at su.litvak.chromecast.api.v2.Channel.sendStandard(Channel.java:348)
	at su.litvak.chromecast.api.v2.Channel.load(Channel.java:495)
	at su.litvak.chromecast.api.v2.ChromeCast.load(ChromeCast.java:457)
	at su.litvak.chromecast.api.v2.ChromeCast.load(ChromeCast.java:433)
	at program.TaskQrCode.sendQrCodeToCCast(TaskQrCode.java:63)

You need to run the application before loading something. Please refer to the instruction in README.md of this project.

For "standard" usage (send a pic url) i need an app id too ?

Yes, you need to always use an app.

How it's works ?
A chromecast have severals app, each same app have the same id or a same app on several chromecast have the same id. If you know ofc.

AFAIK you can create your own app for free and then run it on several chromecast devices. It's better to read the official ChromeCast documentation from Google.

i already add the code for start & stop the app E8C28D3C from the readme.md.

Not sure where you got this id. It is not present in this project's README.
BTW, I have just tested the library with my simple media receiver app and video from README. It works just fine.

i just try to send an url like https://upload.wikimedia.org/wikipedia/commons/b/b4/JPEG_example_JPG_RIP_100.jpg in order the chromecast.

I close for now, i use an other solutions.
But i guess instead of app i should use send with a custom class and  something like "uri:"/"url:"
thx


Feature list README

Add Features section to README.md:

Timezone, listens for messages that contain 1:30pm UTC and replies with common timezones translation

Set/Get user bio with description and social links

Code of Conduct

Daily standup message consistently formatted

Help

Members role rewards

Platform stats

Firebase (Firestore) integration, allowing people to easily add commands and persist data

GitHub Actions deploys mainline branch to Azure

What content will be populated on these points and whereon the readme file will this feature section be
@eddiejaoude

Great questions @Ruth-ikegah 👍
I think the feature list should be near the top of the readme, above required section.
We could use some information from the help command, this features section is to show the benefits of the project easily and quickly to people visiting the repo.


CI with travis

Setup a Travis build to periodically run integration test against an openwhisk deployment (or the publicly hosted service).

I've now added the basic Travis CI YML to set up running the unit tests for this project.
Talking to @rabbah about getting this module into the NodeJS Action environment, we want to have integration testing set up.

If we install the package in the docker file and replace the tests that do invoke/fire with your library for at least those two it would give us parity with the whisk object.

The project does have integration tests already but I'm not sure what the best way to test these against a live OW platform instance from Travis is.
cc @csantanapr & @bjustin-ibm

This pull request will add the package to the base images: https://github.com/openwhisk/openwhisk/pull/1539. We need to resolve #1 and as a bonus #14 as well.

I've now resolved #1 and #14 with 2.3.0.
What's the next step for this issue?

@csantanapr & @rabbah given some of the recent issues, I'd like to get the Travis CI set up running the integration tests to catch library bugs and platform API changes.
Do we have an integration environment I can point to?

What you mean an integration environment to point.
You need to git clone OpenWhisk from git repo and build and deploy during Travis locally and the run your tests against local OpenWhisk running on Travis
We have several repos that do this already, I did one recently for apigateway and got the build down to 14 minutes to build and deploy OpenWhisk only with nodejs runtime installed.

See the following Travis configuration file
https://github.com/openwhisk/openwhisk-apigateway/blob/master/.travis.yml
The setup and build scripts are the ones related to OpenWhisk
So the direction will be to run
Setup to git clone OpenWhisk
Build to build and deploy OpenWhisk with gradle and ansible
Then configure env and CLI to point to local OpenWhisk apihost using guest namespace
Then run npm tests

Thanks for explaining, I didn't think of that approach.
I'll see if I can set this up.

I can help

Resolved by #59


unit test kcloset #30 fails for v2.26

When I run the tests for closest in v2.26, test #30 in the kcloset sub-directory fails. I don't immediately see why, will have to take a look.

It works OK in the last git version.