github-actions[bot] wrote:
<!--LLVM CODE FORMAT COMMENT: {darker}-->
:warning: Python code formatter, darker found issues in your code. :warning:
<details>
<summary>
You can test this locally with the following command:
</summary>
``````````bash
darker --check --diff -r origin/main...HEAD
lldb/packages/Python/lldbsuite/test/tools/lldb-dap/dap_server.py
``````````
:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:
</details>
<details>
<summary>
View the diff from darker here.
</summary>
``````````diff
--- dap_server.py 2026-05-05 09:31:13.000000 +0000
+++ dap_server.py 2026-05-05 09:41:54.089128 +0000
@@ -510,20 +510,24 @@
# default environment, not a full replacement. Merge with
# os.environ so the spawned process inherits PATH etc.
env_dict = os.environ | arguments.get("env", {})
env = [f"{k}={v}" for k, v in env_dict.items()]
self.reverse_process = self.spawn_helper(
- exe, args, env, stdout=subprocess.PIPE, stderr=subprocess.PIPE,
+ exe,
+ args,
+ env,
+ stdout=subprocess.PIPE,
+ stderr=subprocess.PIPE,
# This works around a bug in the macOS job control code where
# a supurious SIGHUP is sent to the the process group of our
# spawned subprocess when it is shutting down.
# While this SIGHUP doesn't cause any issues for our
subprocess,
# it does reach the LIT process and stop the test suite run
# early.
# This parameter forces the spawned process into a new process
# group which prevents the supurious SIGHUP from reaching LIT.
- start_new_session=True
+ start_new_session=True,
)
body = {"processId": self.reverse_process.pid}
self.send_packet(
{
"type": "response",
``````````
</details>
https://github.com/llvm/llvm-project/pull/195816
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
