SWE-bench-Live/Windows huggingface dataset:
Repository: lima-vm/lima (Go)

Issue:
[WSL2] experimental/wsl2 template has systemd misconfigured and integration test is fainling
### Description

For out of the box configured machine systemd has startup issues. This results in failing integration test.

With WSL2 with NAT networking mode list of failed units:
```
[systemd]
Failed Units: 2
  audit-rules.service
  auditd.service
```

With WSL2 with mirrored networking mode list of failed units:
```
[systemd]
Failed Units: 3
  audit-rules.service
  auditd.service
  NetworkManager-wait-online.service
```

Example output from shell:
```bat
limactl shell wsl2 systemctl is-system-running --wait
time="2025-02-22T16:35:59+02:00" level=warning msg="treating lima version \"4e0539cb.m\" from \"C:\\\\Users\\\\Arthu\\\\.lima\\\\wsl2\\\\lima-version\" as very latest release"
degraded

echo %ERRORLEVEL%
-1
```

Potentially this is an issue for the upstream provider of the base system, but it is unclear if there is a more suitable place to report this. Failing integration test still has place.


Discussion:
There sources stating that WSL2 kernel doesn't include auditing support in their default build https://randombytes.substack.com/p/problematic-systemd-units-under-wsl

So, auditd services have to be either disabled or uninstalled in the upstream root fs.

There is also occasional failure of getty-console, but this is attributed to some bug in systemd https://github.com/util-linux/util-linux/issues/2896#issuecomment-2036765992 Current WSL2 template is Fedora 40 image, Fedora 41 or soon to be released Fedora 42 might resolve this entirely.



Patch:
diff --git a/templates/experimental/wsl2.yaml b/templates/experimental/wsl2.yaml
index b95e3d8cf5e..ae67e332ed8 100644
--- a/templates/experimental/wsl2.yaml
+++ b/templates/experimental/wsl2.yaml
@@ -4,9 +4,9 @@ vmType: wsl2
 
 images:
 # Source: https://github.com/runfinch/finch-core/blob/main/Dockerfile
-- location: "https://deps.runfinch.com/common/x86-64/finch-rootfs-production-amd64-1738856482.tar.gz"
+- location: "https://deps.runfinch.com/common/x86-64/finch-rootfs-production-amd64-1741837119.tar.gz"
   arch: "x86_64"
-  digest: "sha256:efbe5fc2b2ec94bbf9e4a6c184bf2b36040faf939c15a016f8d7931de9a481c3"
+  digest: "sha256:1ebee4c785fc4d31fd514365694a7d4d50a95093526c051f76dc63d8ba9fafe6"
 
 mountType: wsl2
 


Test patch:
diff --git a/hack/test-templates.sh b/hack/test-templates.sh
index cf9d7f9f530..4b38ac0f183 100755
--- a/hack/test-templates.sh
+++ b/hack/test-templates.sh
@@ -91,8 +91,6 @@ case "$NAME" in
 	CONTAINER_ENGINE="docker"
 	;;
 "wsl2")
-	# TODO https://github.com/lima-vm/lima/issues/3267
-	CHECKS["systemd"]=
 	# TODO https://github.com/lima-vm/lima/issues/3268
 	CHECKS["proxy-settings"]=
 	CHECKS["port-forwards"]=
Repository: helidon-io/helidon (Java)

Issue:
4.x: `TestTracerAtStartup#checkForFullFeaturedTracerAtStartup` fails on Windows
## Environment Details
* Helidon Version: 4.x
* Helidon MP
* JDK version: 21
* OS: Windows
* Docker version (if applicable): n/a

----------

## Problem Description

Test is failing with following exception: 

```bash
Global tracer from start-up extension
Expected: not a string containing "Default"
     but: was "io.opentelemetry.api.trace.DefaultTracer"
```

## Steps to reproduce

```bash
cd microprofile/telemetry
mvn test
```




Discussion:

Patch:
diff --git a/microprofile/telemetry/pom.xml b/microprofile/telemetry/pom.xml
index 690cea95a99..d0f7eb3d156 100644
--- a/microprofile/telemetry/pom.xml
+++ b/microprofile/telemetry/pom.xml
@@ -152,7 +152,26 @@
                         <configuration>
                             <systemPropertyVariables>
                                 <otel.bsp.schedule.delay>${otel.bsp.schedule.delay}</otel.bsp.schedule.delay>
+                                <otel.sdk.disabled>false</otel.sdk.disabled>
                             </systemPropertyVariables>
+                            <excludes>
+                                <exclude>**/AgentDetectorTest.java</exclude>
+                            </excludes>
+                        </configuration>
+                    </execution>
+                    <execution>
+                        <!--
+                        This test does not need an active OTel SDK so run it separately to prevent it from running first
+                        and leaving other tests with a no-op Otel which will cause them to fail.
+                         -->
+                        <id>agent-detector-tests</id>
+                        <goals>
+                            <goal>test</goal>
+                        </goals>
+                        <configuration>
+                            <includes>
+                                <include>**/AgentDetectorTest.java</include>
+                            </includes>
                         </configuration>
                     </execution>
                 </executions>


Test patch:
diff --git a/microprofile/telemetry/src/test/java/io/helidon/microprofile/telemetry/TestTracerAtStartup.java b/microprofile/telemetry/src/test/java/io/helidon/microprofile/telemetry/TestTracerAtStartup.java
index f43cfa313e7..abc9a9f02bc 100644
--- a/microprofile/telemetry/src/test/java/io/helidon/microprofile/telemetry/TestTracerAtStartup.java
+++ b/microprofile/telemetry/src/test/java/io/helidon/microprofile/telemetry/TestTracerAtStartup.java
@@ -31,7 +31,6 @@
 class TestTracerAtStartup {
 
     @Test
-    @DisabledOnOs(value = OS.WINDOWS, disabledReason = "https://github.com/helidon-io/helidon/issues/9513")
     void checkForFullFeaturedTracerAtStartup() {
         assertThat("Global tracer from start-up extension",
                    TestExtension.globalTracerAtStartup.unwrap(io.opentelemetry.api.trace.Tracer.class).getClass().getName(),
Repository: pingdotgg/t3code (TypeScript)

Issue:
[Bug]: CTRL+J not closing terminal on Windows
### Before submitting

- [x] I searched existing issues and did not find a duplicate.
- [x] I included enough detail to reproduce or investigate the problem.

### Area

apps/desktop

### Steps to reproduce

1. Hit CTRL+J to open the terminal (Focus goes to the terminal)
2. Hit CTRL+J again to close the terminal (Terminal does not close)
3. Focus on the chat and hit CTRL+J again (Terminal closes)

### Expected behavior

Repeatedly hitting CTRL+J should open and close the terminal without having to manually change focus back to the chat.

### Actual behavior

The CTRL+J keyboard shortcut on Windows does not work as expected.

- Opening the terminal with CTRL+J works fine.
- Closing the terminal with CTRL+J does only work when focused on the chat.
- When the focus is inside of the terminal, CTRL+J does not do anything.
- No problem when clicking the UI button to toggle the terminal

CMD+J on Mac works as expected.


### Impact

Minor bug or occasional failure

### Version or commit

Release 0.0.20

### Environment

Windows

### Logs or stack traces

```shell

```

### Screenshots, recordings, or supporting files

_No response_

### Workaround

_No response_


Discussion:
Submitted a fix in https://github.com/pingdotgg/t3code/pull/2142. The global keydown listener now runs in the capture phase, so the terminal toggle fires before xterm.js can process the event on Windows.



Patch:
diff --git a/apps/web/src/components/ChatView.tsx b/apps/web/src/components/ChatView.tsx
index 06d8e8db5d..47dad09ea2 100644
--- a/apps/web/src/components/ChatView.tsx
+++ b/apps/web/src/components/ChatView.tsx
@@ -2290,8 +2290,8 @@ export default function ChatView(props: ChatViewProps) {
       event.stopPropagation();
       void runProjectScript(script);
     };
-    window.addEventListener("keydown", handler);
-    return () => window.removeEventListener("keydown", handler);
+    window.addEventListener("keydown", handler, true);
+    return () => window.removeEventListener("keydown", handler, true);
   }, [
     activeProject,
     terminalState.terminalOpen,


Test patch:
diff --git a/apps/web/src/keybindings.test.ts b/apps/web/src/keybindings.test.ts
index 2c968e6bc3..683afbbfe4 100644
--- a/apps/web/src/keybindings.test.ts
+++ b/apps/web/src/keybindings.test.ts
@@ -131,6 +131,15 @@ describe("isTerminalToggleShortcut", () => {
       isTerminalToggleShortcut(event({ ctrlKey: true }), DEFAULT_BINDINGS, { platform: "Win32" }),
     );
   });
+
+  it("matches Ctrl+J on non-macOS while terminalFocus is true", () => {
+    assert.isTrue(
+      isTerminalToggleShortcut(event({ ctrlKey: true }), DEFAULT_BINDINGS, {
+        platform: "Win32",
+        context: { terminalFocus: true },
+      }),
+    );
+  });
 });
 
 describe("split/new/close terminal shortcuts", () => {