sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Enabling `http.fetchAdditionalSupport` may break extensions using global `fetch`
Labels: bug,proxy

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.96.0
- OS Version: MacOS Sonoma 14.7.2

Unfortunately this is entirely extension-dependent, but most of the context is in https://github.com/microsoft/vscode-discussions/discussions/2438.

The main points:
- we noticed [our extension](https://github.com/confluentinc/vscode) was throwing `fetch failed` errors with the above setting **enabled** (after the 1.96 update, where it looks to be enabled by default), but only for requests that were using the local Docker socket path to interact with the Docker engine API
  - sample error info:
    ```
    TypeError: fetch failed
        at node:internal/deps/undici/undici:13392:13
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
        at globalThis.fetch (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:159:19800) 
    ...
    cause:
    ECONNREFUSED: fetch failed
    AggregateError
        at internalConnectMultiple (node:net:1122:18)
        at afterConnectMultiple (node:net:1689:7)
        at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
    ```
  - example request init:
    ```typescript
    import { Agent } from "undici";
    // ...
    const init = {
      dispatcher: new Agent({
        connect: {
          socketPath: "/var/run/docker.sock",
        },
      })
    }
    ```
- `http.fetchAdditionalSupport` enabled and `http.systemCertificates` enabled: requests fail with the above error ❌
- `http.fetchAdditionalSupport` enabled and `http.systemCertificates` disabled: requests return successful responses ✅ 
(Toggling `http.proxySupport` seems to have no effect here.)

I'm happy to hop on a call and/or provide more information if needed.

Are there any specific changes extension developers should take in response to this setting?
Repository: godot
Issue: RayCast3D is not working with trimesh collision
Labels: bug,topic:physics,topic:3d

### Tested versions

4.3 stable

### System information

Windows 10

### Issue description

RayCast3D collision detection is not working with terrain generated from **_ArrayMesh_** and its collision generated using trimesh strategy.

It works when terrain is generated from **_PlaneMesh_** and trimesh strategy as well.

All collision masks are good (default 1).

### Steps to reproduce

Create ray cast and add it the main node.

```c#
RayCast3D rayCast = new RayCast3D();
rayCast.TargetPosition = new Vector3(0, -50, 0);
rayCast.Enabled = true;
rayCast.HitBackFaces = true;
rayCast.CollideWithAreas = true;
rayCast.DebugShapeCustomColor = new Color(0,0,1);
rayCast.DebugShapeThickness = 1;
```

Generate ArrayMesh adding vertices, UVs, indexes and normals:
```c#
public ArrayMesh FromHeightmap()
{
    float HeightScale = 50.0f;
    float TerrainScale = 1.0f;

    Texture2D texture = GD.Load<Texture2D>($"res://heightmap.jpg");
    Image img = texture.GetImage();
    int width = img.GetWidth();
    int height = img.GetHeight();

    SurfaceTool surfaceTool = new SurfaceTool();
    surfaceTool.Begin(Mesh.PrimitiveType.Triangles);

    for (int z = 0; z < height; z++)
    {
        for (int x = 0; x < width; x++)
        {
            Color pixel = img.GetPixel(x, z);
            float h = pixel.R;
            float worldHeight = h * HeightScale;

            Vector2 uv = new Vector2((float) x / (width - 1), (float) z / (height - 1));
            surfaceTool.SetUV(uv);
            
            Vector3 vertex = new Vector3(x * TerrainScale, worldHeight, z * TerrainScale);
            surfaceTool.AddVertex(vertex);
        }
    }

    for (int z = 0; z < height - 1; z++)
    {
        for (int x = 0; x < width - 1; x++)
        {
            int topLeft = z * width + x;
            int topRight = z * width + (x + 1);
            int bottomLeft = (z + 1) * width + x;
            int bottomRight = (z + 1) * width + (x + 1);

            surfaceTool.AddIndex(topLeft);
            surfaceTool.AddIndex(bottomLeft);
            surfaceTool.AddIndex(topRight);

            surfaceTool.AddIndex(topRight);
            surfaceTool.AddIndex(bottomLeft);
            surfaceTool.AddIndex(bottomRight);
        }
    }

    surfaceTool.GenerateNormals();

    return surfaceTool.Commit();
}
```

Create the terrain and add it to the main node:
```c#
ArrayMesh arrayMesh = mapReader.FromHeightmap();

MeshInstance3D meshInstance = new MeshInstance3D();
meshInstance.Position = new Vector3(0,0,0);
meshInstance.Mesh = arrayMesh;
meshInstance.CreateTrimeshCollision();
```

Enable `Visible Collision Shapes` in project settings.

### Minimal reproduction project (MRP)

I have absolutely no idea how to use GDScript or even the godot app itself so I will just post project in C# which is 100% code based.
Move camera by W A S D.
Blue ray = no collision
Red ray = collision

[raycast3d.zip](https://github.com/user-attachments/files/18172798/raycast3d.zip)
Repository: pytorch
Issue: Compiler Bisector Improvements
Labels: triaged,module: inductor

### 🚀 The feature, motivation and pitch

@ezyang has been using Compiler Bisector internally and run it into a few feature requests. 

- [ ] Query for backend, subsystems
- [ ] Config option to check meta stride for all ops, not just custom ops
- [ ] Option to specify particular backend/subsystem to iterate over
- [ ] Better print outs of how to manually run a particular bisect - for instance, if we bisected lowerings it should inform user to compare: `TORCH_BISECT_SUBSYSTEM=lowerings TORCH_BISECT_BACKEND=inductor TORCH_BISECT_MAX=21` and `TORCH_BISECT_SUBSYSTEM=lowerings TORCH_BISECT_BACKEND=inductor TORCH_BISECT_MAX=20` 

Other requests 
- [ ] Option to bisect which compiled graph is causing the issue first. Potentially we would bisect to the bad fwd/backward. then see if fwd, back, or joint graph passes/partitioner is the issue.


cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov @exclamaforte who was interested

### Alternatives

_No response_

### Additional context

_No response_
Repository: rust
Issue: Document the contextual keyword `raw`
Labels: C-enhancement,T-compiler,A-docs,T-libs,A-raw-pointers

Related with https://github.com/rust-lang/rust/issues/34601, https://github.com/rust-lang/rust/pull/127679.
Repository: tauri
Issue: [feat] Add tauri://pageLoad event listener support in frontend
Labels: type: feature request

### Describe the problem

When creating a new window using `WebviewWindow`, I can only use `tauri://created` to listen for window creation. However, this event triggers much earlier than the actual page load completion. 

Currently, if I need to inject JavaScript after the page is fully loaded, I have to:
1. Use `WebviewWindowBuilder::new(&app_handle, &label, url_parse).on_page_load` in the backend
2. Emit an event to notify the frontend

The challenge is that I'm not familiar with backend development in Rust, and I have to rely on my friend to help implement these backend methods.

Technical Context:
- Current approach requires backend implementation
- Frontend developers need a more accessible way to handle post-load operations
- Similar to how browsers provide `window.onload` event

thanks

### Describe the solution you'd like

1. Add a frontend event listener for page load completion (similar to `tauri://pageLoad`)
2. Add frontend API for JavaScript injection

This would greatly improve the developer experience for frontend developers who are not yet proficient in Rust but need these functionalities for their projects.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: rust
Issue: cfg resolve diagnostic doesn't show up for axum macro
Labels: A-diagnostics,A-resolve,T-compiler,D-terse,A-cfg

### Code

Without the macro feature enabled.

```Rust
use axum::extract::FromRef;

#[derive(Clone, FromRef)]
struct AppState {
    db: SqlitePool,
}
```

### Current output

```Shell
error: cannot find derive macro `FromRef` in this scope
  --> src/main.rs:33:17
   |
33 | #[derive(Clone, FromRef)]
   |                 ^^^^^^^
   |
note: `FromRef` is imported here, but it is only a trait, without a derive macro
  --> src/main.rs:1:12
   |
1  | use axum::{extract::FromRef, Router};
   |            ^^^^^^^^^^^^^^^^
```

### Desired output

```Shell
error[E0432]: unresolved import `axum::extract::FromRef`
  --> src/main.rs:2:5
   |
2  | use axum::extract::FromRef;
   |     ^^^^^^^^^^^^^^^^^ no `FromRef` in `extract`
   |
note: found an item that was configured out
  --> /Users/joshka/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-0.7.9/src/extract/mod.rs:xx:yy
   |
xx | macro_rules! FromRef;
   |         ^^
note: the item is gated behind the `macros` feature
  --> /Users/joshka/.cargo/registry/src/index.crates.io-6f17d22bba15001f/axum-0.7.9/src/extract/mod.rs:xx:yy
```

### Rationale and extra context

The detection of cfg'd out items should treat items that match the expected type (e.g. a macro) as higher priority than items which match the name (e.g. `FromRef`)

### Other cases

```Rust

```

### Rust Version

```Shell
rustc --version --verbose
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: aarch64-apple-darwin
release: 1.83.0
LLVM version: 19.1.1
```

### Anything else?

Similar to but not the same as https://github.com/rust-lang/rust/issues/132166
Possibly relevant to https://github.com/rust-lang/rust/pull/129183
Repository: ant-design
Issue: 如何修改Splitter分割线的样式？
Labels: 💡 Feature Request,6.x

### Reproduction link

[https://ant-design.antgroup.com/components/splitter-cn](https://ant-design.antgroup.com/components/splitter-cn)

### Steps to reproduce

无

### What is expected?

1. Splitter组件左右两侧中间有个分割线，在不禁用resizable的情况下，如何隐藏分割线中间的灰色长方形方框？如下：
<img width="438" alt="image" src="https://github.com/user-attachments/assets/e3843cd1-0ebe-4730-b07b-e71d990bcf94" />

2. 希望可以增加两个按钮，点击按钮可以将左侧（或右侧）区域折叠或展开



### What is actually happening?

无

| Environment | Info |
| --- | --- |
| antd | 5.22.5 |
| React | lastest |
| System | macos |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: terminal
Issue: South Asian Languages characters are incorrect in spacing
Labels: Needs-Triage,Needs-Tag-Fix

> The issue is that we rely on the "East Asian With" spec by Unicode, like pretty much all terminals: https://www.unicode.org/reports/tr11/
> As the name suggests, for southeastern languages it just says, "no designated width", which we by convention have to assume is 1 column wide. If you can find >1 terminal that solve this issue (= which we could use as reference), please let us know by opening a new issue for it. 🙂 

 _Originally posted by @lhecker in [#9490](https://github.com/microsoft/terminal/issues/9490#issuecomment-2549050353)_

---
WT Version: 1.21.3231.0; 
Microsoft Windows [Version 10.0.22631.4541]

![Image](https://github.com/user-attachments/assets/f77c95df-6c00-4b9e-919e-118dc404437c)

---

Readable in [Cmder ](https://github.com/cmderdev/cmder)

![Image](https://github.com/user-attachments/assets/cf740610-87d2-4439-8f5e-547a93a163a7)
Repository: tauri
Issue: [bug]  Error failed to bundle project: error running appimage.sh
Labels: type: bug,help wanted,platform: Linux,status: needs triage

### Describe the bug

Operation steps:
1 .  "targets": ["deb","updater", "appimage"],
2.  npm run tauri build

result：
 Finished `release` profile [optimized] target(s) in 1m 10s
        Warn Signing, by default, is only supported on Windows hosts, but you can specify a custom signing command in `bundler &gt; windows &gt; sign_command`, for now, skipping signing the installer...
    Bundling pt-system-student_1.0.0_amd64.deb (path/src-tauri/target/release/bundle/deb/test_1.0.0_amd64.deb)
    Bundling pt-system-student_1.0.0_amd64.AppImage (path/src-tauri/target/release/bundle/appimage/test_1.0.0_amd64.AppImage)
       Error failed to bundle project: error running appimage.sh

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
> mock_student@0.0.0 tauri
> tauri info


[✔] Environment
    - OS: Ubuntu 18.4.0 X64
    ✔ webkit2gtk-4.0: 2.32.4
    ✔ rsvg2: 2.40.20
    ✔ rustc: 1.83.0 (90b35a623 2024-11-26)
    ✔ cargo: 1.83.0 (5ffbef321 2024-10-29)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 16.20.2
    - pnpm: 8.15.9
    - npm: 8.19.4

[-] Packages
    - tauri [RUST]: 1.5.4
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.6.0 (outdated, latest: 2.1.1)
    - @tauri-apps/cli [NPM]: 1.6.3 (outdated, latest: 2.1.0)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1421/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: go
Issue: syscall: unable to use the full length for abstract socket starting with null
Labels: NeedsFix,compiler/runtime

### Go version

go version go1.23.3 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/albert/.cache/go-build'
GOENV='/home/albert/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/albert/go/pkg/mod'
GONOPROXY='bitbucket.org/vivcourt/*'
GONOSUMDB='bitbucket.org/vivcourt/*'
GOOS='linux'
GOPATH='/home/albert/go'
GOPRIVATE='bitbucket.org/vivcourt/*'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/albert/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.3.linux-amd64'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/albert/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.3.linux-amd64/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.3'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/albert/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/albert/glue/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3031541326=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

https://go.dev/play/p/Lro4QrH5-BK

### What did you see happen?

padded addr1 (@begins-with-at) with length: 108 
padded addr2 (begins-with-null) with length: 108
panic: listen unix begins-with-null: bind: invalid argument

goroutine 1 [running]:
main.main()
	/tmp/sandbox3694864181/prog.go:27 +0x294

### What did you expect to see?

both address  (beginning with `@` and `null or 0`) should be useable to specify abstract unix domain socket with length of 108 (full path length)

the issue seems to be this line of code that checks for `@` for abstract domain socket but not for `0`
https://github.com/golang/go/blob/master/src/syscall/syscall_linux.go#L557

considering how the next part of the code checks for `0 and sl > 3` https://github.com/golang/go/blob/master/src/syscall/syscall_linux.go#L569
I would expect that specifying `0` to indicate it's a domain socket to be a valid way of doing so

let me know if this is something that should be fixed, I would be more than happy to create a PR. Thanks!
Repository: pytorch
Issue: [ROCm] MI300X FP8 scaled_mm is extremely slow on nightly
Labels: module: performance,module: rocm,triaged

### 🐛 Describe the bug

Hi AMD Team,

`torch._scaled_mm` is extremely slow on MI300X at ~100TFLOP/s verus ~1200TFLOP/s on H100

Can you look into this?

cc: @hliuca

## ROCm
```
m=16384 n=8192 k=1280: 108.07154472843483
m=16384 n=1024 k=8192: 110.56206220309926
m=16384 n=8192 k=7168: 109.66662842248034
m=16384 n=3584 k=8192: 110.59228182207659
m=8192 n=8192 k=8192: 109.86138366796457
```

## H100
```
m=16384 n=8192 k=1280: 1239.4133451945781
m=16384 n=1024 k=8192: 1347.0844475792383
m=16384 n=8192 k=7168: 1332.2623882545472
m=16384 n=3584 k=8192: 1309.4453003269748
m=8192 n=8192 k=8192: 1304.5406858844613
```

## Reprod
```
import time
import torch
from triton.testing import do_bench

torch.manual_seed(0)
repeats = 200
warmup = 30
timeout = 0.5

device = 'cuda'

# GEMM Shapes
shapes = [
    (16384, 8192, 1280),
    (16384, 1024, 8192),
    (16384, 8192, 7168),
    (16384, 3584, 8192),
    (8192, 8192, 8192)
]

results = []

for (m, n, k) in shapes:
    # FLOPS
    nFLOPS = 2 * m * n * k
    a_fp8_e5m2 = torch.randn(m, k, device=device).to(torch.float8_e5m2fnuz)
    b_fp8_e5m2 = torch.randn(n, k, device=device).to(torch.float8_e4m3fnuz).transpose(-1, -2)
    scale_a = torch.tensor(1.0, device=device, dtype=torch.float32)
    scale_b = torch.tensor(1.0, device=device, dtype=torch.float32)
    ms_fp8_scaled_mm_e4m3 = do_bench(lambda: torch._scaled_mm(a_fp8_e5m2, b_fp8_e5m2, scale_a, scale_b), warmup=warmup, rep=repeats)
    tflops_fp8_scaled_mm_e4m3 = nFLOPS / ms_fp8_scaled_mm_e4m3 * 1e-9
    time.sleep(timeout)

    print(f"{m=} {n=} {k=}: {tflops_fp8_scaled_mm_e4m3}")
```

cc: @hliuca

### Versions

```bash
pip list | grep torch
pytorch-triton-rocm      3.2.0+git35c6c7c6
torch                    2.6.0.dev20241216+rocm6.2.4
```

cc @msaroufim @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
Repository: svelte
Issue: False positive of ownership_invalid_mutation after hot reload
Labels: bug

### Describe the bug

In the example code, it seems to behave correctly, unless CounterDisplay.svelte content is changed to cause a vite module hot-reload. After the hot reload, every state change causes "ownership_invalid_mutation" warnings.

This particular issue is only reproducible locally, [clone this repo to test it out.](https://github.com/goldentoaste/sanityTest)

```html
+page.svelte
<script>
    import CounterDisplay from "./CounterDisplay.svelte";
    let counter = $state({
        count: 0,
    }); 
</script>

<CounterDisplay bind:counter></CounterDisplay>
```

```html
CounterDisplay.svelte
<script>
	import Incrementer from "./Incrementer.svelte"
	let {counter = $bindable()} = $props()
</script>
<!-- Warning shows when this component is hot reloaded. For example added a new div here.  -->
<p>Counter is {counter.count}</p>
<Incrementer bind:count={counter.count}></Incrementer>
```

```html
Incrementer.svelte
<script>
	let {count = $bindable()} = $props();
</script>

<button onclick={()=>{count += 1}}>Go up</button>
```

### Reproduction

Reproducible in [this repo](https://github.com/goldentoaste/sanityTest).

1. Load root page to see counter working correctly, without warning
2. In `CounterDisplay.svelte`, make any html change, such as added a new div, in order to trigger a vite hot reload.
3. Further state change to the counter now raises `ownership_invalid_mutation` warning in browser console.

### Logs

```shell
ownership_invalid_mutation 
src/routes/test/CounterDisplay.svelte mutated a value owned by src/routes/test/+page.svelte. This is strongly discouraged. Consider passing values to child components with `bind:`, or use a callback insteadlback instead
https://svelte.dev/e/ownership_invalid_mutation
```


### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-1360P
    Memory: 3.14 GB / 15.57 GB
  Binaries:
    Node: 22.1.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.3 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.98)
    Internet Explorer: 11.0.22621.3527
```


### Severity

annoyance
Repository: go
Issue: build: build failure on gotip-linux-arm64_c4as16-perf_vs_release
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "gotip-linux-arm64_c4as16-perf_vs_release" && repo == "go" && mode == "build"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8728267415754195281)):

    go: downloading github.com/BurntSushi/toml v1.0.0
    go: downloading github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51
    2024/12/17 21:56:19 Load average: 0.10 2.50 5.72 1/409 1782864
    2024/12/17 21:56:19 Running Go test benchmarks for experiment
    go: downloading github.com/dustin/go-wikiparse v0.0.0-20211018054215-c01ec186f20c
    go: downloading github.com/blevesearch/bleve v1.0.14
    go: downloading github.com/biogo/biogo v1.0.4
    go: downloading github.com/yuin/gopher-lua v0.0.0-20210529063254-f4c35e4016d9
    go: downloading golang.org/x/sync v0.10.0
    go: downloading gitlab.com/golang-commonmark/markdown v0.0.0-20211110145824-bf3e522c626a
    ...
    [sweet] Running benchmark tile38 for experiment: run 8
    [sweet] Running benchmark tile38 for baseline: run 8
    [sweet] Running benchmark tile38 for experiment: run 9
    [sweet] Running benchmark tile38 for baseline: run 9
    [sweet] Running benchmark tile38 for experiment: run 10
    [sweet] Running benchmark tile38 for baseline: run 10
    [sweet] error: failed to execute benchmarks: esbuild go-build
    2024/12/18 03:27:33 Error running sweet: error running sweet run: exit status 1
    2024/12/18 03:27:33 FAIL
    exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: react
Issue: [React 19] Proposal: Enhancing useTransition Hook with Timed Start Transition Feature
Labels: React 19

## Summary
We propose enhancing React's startTransition function to accept an optional second parameter: a timeout duration (durationInMs). This will ensure the transition runs for at least the specified time, even if the internal logic resolves earlier, enabling smoother UI updates and animations.

#Proposed API
`startTransition(callback, durationInMs);`

- callback: Executes state updates or operations as a transition.
- durationInMs (Optional): Ensures the transition takes a minimum time, adding a delay if the callback resolves sooner.

`
startTransition(() => {
  setData(fetchData());
}, 500); // Ensures a minimum 500ms transition
`
If fetchData resolves in 200ms, the UI remains in a "pending" state for 500ms, ensuring a smoother experience.

#Benefits

- Enhanced UX: Prevents abrupt UI updates by synchronizing transitions with animations or loaders.
- Simplified Code: Reduces reliance on setTimeout hacks for timing.
- Backward Compatible: Fully optional, retaining existing functionality.
- This addition aligns with React's goal of delivering seamless developer and user experiences. We invite the community to discuss and refine this idea.