sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: "NVDA Not Reading When I Open a Folder from Within VSCode"
Labels: info-needed


Type: <b>Bug</b>

When I open a folder within Visual Studio Code, NVDA announces the folder as "unknown" instead of reading  anything . i have to restart nvda and alt tab out and back in. This issue prevents me from knowing which folder or files are being opened, making it difficult to navigate effectively within VSCode. note, i am on a mac with a windows VM. I was also able to reproduce on my  other computers.

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT arm64 10.0.26100
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple Silicon (4 x 3200)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: unavailable_off<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.99GB (0.85GB free)|
|Process Argv|--crash-reporter-id c37eff74-c330-4ccb-910b-e92d95621bcc|
|Screen Reader|yes|
|VM|100%|
</details><details><summary>Extensions (4)</summary>

Extension|Author (truncated)|Version
---|---|---
remote-ssh|ms-|0.116.1
remote-ssh-edit|ms-|0.87.0
remote-explorer|ms-|0.4.3
pythagora-vs-code|pyt|1.2.13


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: react
Issue: Bug: Synchronously Restart Render on Error During Async Rendering to Prevent Inconsistencies
Labels: Status: Unconfirmed,Resolution: Needs More Information

Synchronously restart when an error is thrown during async rendering

### Description

In async mode, events are interleaved with rendering. If an event mutates state that is later accessed during render, it can cause inconsistencies. Restarting the render synchronously resolves the inconsistency and prevents further mutations during interleaved events.

### Steps to Reproduce

1. Enable async rendering mode.
2. Trigger an event that mutates state during rendering.
3. Observe inconsistencies during the render process.

### Expected Behavior

The render should restart synchronously to prevent inconsistencies and further mutations from interfering.

### Actual Behavior

Inconsistent rendering occurs, leading to potential UI issues or errors.

### Suggested Fix

Implement synchronous restart of the render when an error is thrown during async rendering to handle the interleaved events and ensure consistency.
Repository: ollama
Issue: API parameter: 'reasoning_effort' (for DeepSeek-R1)
Labels: feature request

When I will be able to use `reasoning_effort` like on DeepSeek-R1? :)

Doc: https://api-docs.deepseek.com/guides/reasoning_model
Repository: react
Issue: Bug: Prevent event log from growing unbounded
Labels: Status: Unconfirmed

When a  Scheduler profile runs without stopping, the event log will grow unbounded. Eventually it will run out of memory and the VM will throw an error.

React version: [v16.9.0](https://github.com/facebook/react/releases/tag/v16.9.0)

## Steps To Reproduce

1. Run Scheduler profile
2. Watch memory resource growing




## The current behavior
When Scheduler profile starts it runs out of memory and the JVM throws an error

## The expected behavior
The event log should not grow unbounded
Repository: flutter
Issue: [go_router] [go_router_builder]  go_router already supports preloading but go_router_builder doesn't
Labels: c: new feature,package,c: proposal,p: go_router_builder,team-go_router

### Use case

Support preload for `StatefulShellBranch` when use `go_router_builder`

### Proposal

Add `preload` field to `go_router_builder` and code gen helper function of `go_router`
Repository: PowerToys
Issue: Keeps forgetting that I have fancy zones turned on.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Other (please specify in "Steps to Reproduce")

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Installation method don't remember. From Google search. 
It randomly forgets that I have fancy zones turned on (great feature, b.t.w. :) ), and I have to manually turn it on again. 

### ✔️ Expected Behavior

It remembers that I have fancy zones turned on, for each user. 

### ❌ Actual Behavior

It randomly forgets. 

### Other Software

_No response_
Repository: react
Issue: Bug: Fix Buffer - Write Chunks to Separate Buffers
Labels: Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->
The bug happens when using ReactDOMFizzServer.renderToReadableStream to render big chunks of data. If a chunk is bigger than the buffer (default: 512 bytes), the buffer overflows or uses incomplete data. This causes wrong or cut-off output because the renderer doesn’t handle buffer size properly.

React version:
React 19.0.0

## Steps To Reproduce
1. Create a large chunk of data that is bigger than the buffer size.
2. Start processing the data using `ReactDOMFizzServer.renderToReadableStream`.  
3. Observe the behavior when the chunks exceed the buffer size.  

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->
```
import ReactDOMFizzServer from 'react-dom/server';

// Minimal data to reproduce the problem
const largeChunk = 'A'.repeat(2049); // A chunk exceeding  default 512 bytes

async function testStream() {
  //  simple React structure with the large chunk
  const stream = await ReactDOMFizzServer.renderToReadableStream(
    <div>{largeChunk}</div>
  );

  // function to read the stream
  const decoder = new TextDecoder();
  const reader = stream.getReader();
  let result = '';
  while (true) {
    const { done, value } = await reader.read();
    if (done) break;
    result += decoder.decode(value);
  }

  console.log(result);
}

testStream();
```

## The current behavior
Right now, when chunks are sent to a `ReadableStream`, they are enqueued directly without checking the buffer size. If a chunk is too big (like 2049 bytes, while the buffer is only 512 bytes), it reuses old buffers, which messes up the output. For example, instead of properly rendering, we get something like ```<div>AAAAA...</div>```.

## The expected behavior
Chunks should be written to their own buffer and split into smaller parts if they are too big. The buffer should only be sent once it's full or the writing is complete. This way, even large chunks (like 2049 bytes) will render correctly, for example: ```<div>AAAAAAAAAAAAAAAAA...</div>```.
Repository: pytorch
Issue: torch._dynamo.exc.Unsupported: Graph break due to unsupported builtin torch._C._dynamo.eval_frame.set_eval_frame.
Labels: oncall: pt2,export-triaged,oncall: export

### 🐛 Describe the bug

Part of an example as the following:

```python
from torch_mlir import fx

module = fx.export_and_import(
    model,
    input_tensor,
    output_type="tosa",
    func_name="forward",
)

``` 
when I use pyinstaller to pack the fx graph export and import to a binary file, it encounters the following problem. Actually, when I run the unpacked python code, it works well.
![Image](https://github.com/user-attachments/assets/d0dc84cb-9ae8-4c25-afe5-0cf43e41667d)

### Versions

`torch==2.6.0.dev20241216+cpu`

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: pytorch
Issue: DISABLED test_tensor_subclass_basic (__main__.TestCompiledAutograd)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: asan, linux, rocm, mac, macos, slow



This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_tensor_subclass_basic&suite=TestCompiledAutograd&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/36028557832).

Over the past 3 hours, it has been determined flaky in 20 workflow(s) with 40 failures and 20 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_tensor_subclass_basic`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `inductor/test_compiled_autograd.py`

cc @clee2000 @wdvr @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov
Repository: electron
Issue: I am currently upgrading the project from Electron 15 to 29, but the embedded document websites consistently pop up a font download popup window
Labels: platform/macOS,blocked/need-info ❌,bug :beetle:,has-repro-gist

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

29.4.26

### What operating system(s) are you using?

macOS

### Operating System Version

13.2.1 (22D68)

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

30.0.0

### Expected Behavior

I hope that, just like in Electron 15, this pop - up can be skipped entirely, and the default font can be used directly. This is because such an experience is really bad for users.


### Actual Behavior

Request for Support Background: I am currently upgrading the project from Electron 15 to Electron 29, but the embedded document websites consistently pop up a font download popup window. Problem: When using BrowserView, WebView, or iframe in the project to reference external websites, this popup window will appear when a specific font does not exist on Mac. This font download popup window did not exist in version 15. I want to keep it consistent with version 15. Which feature of Electron or Chrome has led to this phenomenon? How should I set it? Below is a screenshot.


Additionally, through my tests in fiddle, I found that this issue still persists in the last version 29.4.26 of Electron 29. However, this problem does not occur in version 30.0.0. Also, there is no such problem in the last version of Electron 28

![Image](https://github.com/user-attachments/assets/a4568b5c-413b-42a2-936d-aefd99e539a8)

### Testcase Gist URL

https://gist.github.com/Tsite2007/aee74ff4afe6f14148d88a1aacb74364

### Additional Information

_No response_
Repository: flutter
Issue: Engine `local_engine_builds` failing since #161825
Labels: engine,P1,c: tech-debt,team-engine,triaged-engine,fyi-web,e: engine-tool

`local_engine_builds` has been in bringup, which means https://github.com/flutter/flutter/pull/161825 broke it without knowing.

(https://github.com/flutter/flutter/pull/160627 initially marked it as `bringup: true`, @jonahwilliams was this intended to be permanent?)

@eyebrowsoffire can you fix this (or revert your changes if you don't imagine this happening for some time)?
Repository: vscode
Issue: Terminal font ligatures doesn't render as expected
Labels: info-needed,terminal-ligatures

In terminal
![Image](https://github.com/user-attachments/assets/2f91f1d0-3c7f-4d73-ae0e-c8aa7d805f2d)

In editor
![Image](https://github.com/user-attachments/assets/ff35a66e-7c3e-42fe-b576-997f38d3aca5)



Version: 1.97.0-insider (user setup)
Commit: d226a2a497b928d78aa654f74c8af5317d3becfb
Date: 2025-01-22T05:05:14.565Z
Electron: 32.2.7
ElectronBuildId: 10660205
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22621
Repository: godot
Issue: (4.4.beta1) Android app crashes when exported with .NET 9
Labels: bug,platform:android,topic:dotnet,regression,topic:export

### Tested versions

**Reproducible:**
4.4.beta1
4.4.dev7

**Not Reproducible:**
4.4.dev3

### System information

Godot v4.4.beta1.mono - Windows 10 (build 19045) - OpenGL 3 (Compatibility)

### Issue description

When exporting to Android with .NET 9 using Gradle Build via the Remote Deploy, the app crashes immediately at startup.

Note:  .NET 8 works fine, but .NET 9 causes the app to crash

using the command at runtime:
**adb logcat|grep godot**

> 01-22 19:27:18.818  1895  3450 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN flg=0x10000000 cmp=com.example.test_android/com.godot.game.GodotApp} from uid 2000
01-22 19:27:18.857  1895  2224 I ActivityManager: Start proc 1876:com.example.test_android/u0a411 for next-top-activity {com.example.test_android/com.godot.game.GodotApp}
01-22 19:27:19.885  1895  2006 W ActivityTaskManager:   Force finishing activity com.example.test_android/com.godot.game.GodotApp
01-22 19:27:19.987  1895  2220 I GameServiceProviderInstance: Failed to remove task overlay. This is expected if the task is already destroyed: GameSessionRecord{mTaskId=306, mState=GAME_SESSION_ATTACHED, mRootComponentName=ComponentInfo{com.example.test_android/com.godot.game.GodotApp}, mIGameSession=android.service.games.IGameSession$Stub$Proxy@3a45eaa, mSurfacePackage=android.view.SurfaceControlViewHost$SurfacePackage@3504a9b}
01-22 19:27:20.386  1895  2200 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{691de90 u0 com.example.test_android/com.godot.game.GodotApp} t-1 f}}







### Steps to reproduce

1. Godot 4.4.beta1
2. Create a new project
3. Create C# script and attach to a node in the main scene
4. Update the visual studio project to target .NET 9: 
` <TargetFramework>net9.0</TargetFramework>`
4. Remote Deploy to Android with Gradle Build

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Squash Merge will list a lot of commits msg that lead to crash in some cases
Labels: info-needed,git

<!-- ⚠️⚠️ 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?: Yes

<!-- 🪓 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.3
- OS Version: MacOS 14.5 (23F79)

Steps to Reproduce:

Assumes that have so many commits and need to merge into a branch with squash mode.
Repository: go
Issue: x/tools/go/ssa: TestGenericFunctionSelector fails with EADDR (netbsd)
Labels: NeedsInvestigation,Tools

```
#!watchflakes
default <- pkg == "golang.org/x/tools/go/ssa" && test == "TestGenericFunctionSelector"
```

Issue created automatically to collect these failures.

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

    === RUN   TestGenericFunctionSelector
        builder_test.go:799: err: fork/exec /home/swarming/.swarming/w/ir/x/w/goroot/bin/go: bad address: stderr: 
    --- FAIL: TestGenericFunctionSelector (0.74s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/compile: worse performance when built with pgo
Labels: NeedsInvestigation,compiler/runtime,BugReport

### Go version

go version go1.23.5 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/transaction/.cache/go-build'
GOENV='/home/transaction/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/transaction/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/transaction/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/transaction/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.5.linux-amd64'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/transaction/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.5.linux-amd64/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.5'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/transaction/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/transaction/tidb/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-build338251587=/tmp/go-build -gno-record-gcc-switches'
```

### What did you do?

Building with [PGO](https://go.dev/doc/pgo), but result in performance regressions.

The build flag is:

```
CGO_ENABLED=1  GO111MODULE=on go build -tags codes -pgo=default.pgo  -ldflags '-X "github.com/pingcap/tidb/pkg/parser/mysql.TiDBReleaseVersion=v9.0.0-alpha-206-gaccc969cd5" -X "github.com/pingcap/tidb/pkg/util/versioninfo.TiDBBuildTS=2025-01-23 06:01:16" -X "github.com/pingcap/tidb/pkg/util/versioninfo.TiDBGitHash=accc969cd5e95a992368249fcf86f11887e7b11a" -X "github.com/pingcap/tidb/pkg/util/versioninfo.TiDBGitBranch=pgo-read-only-dev5" -X "github.com/pingcap/tidb/pkg/util/versioninfo.TiDBEdition=Community" ' -o bin/tidb-server ./cmd/tidb-server
```

Then start the TiDB and run sysbench test, following is the test result, the QPS of building with PGO is  lower.

workload | thread | Version | QPS 
-- | -- | -- | -- 
batch_get | 64 | without-pgo | 23165 
batch_get | 64 | with-pgo | 21077 

</byte-sheet-html-origin><!--EndFragment-->

</byte-sheet-html-origin><!--EndFragment-->

### What did you see happen?

The performance of build with PGO is worse because `newstack` appeared during execution.

[profile.zip](https://github.com/user-attachments/files/18515784/profile.zip)

CPU profile of building without PGO:

<img width="3006" alt="Image" src="https://github.com/user-attachments/assets/70a9f8f5-921f-4264-8ca6-1d777d9b20ae" />



CPU profile of building with PGO:

<img width="3003" alt="Image" src="https://github.com/user-attachments/assets/d401353e-db38-4c6e-ba2b-9cae189ddf55" />




### What did you expect to see?

no `newstack` during execution.

Is there any way to avoid `newstack` during execution, such as set stack size when creating goroutine?
Repository: PowerToys
Issue: 在edge上无法反馈
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

在标题栏输入任意键会跳转至出现错误页面
Repository: PowerToys
Issue: 鼠标荧光笔无法置于 always on top上
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

在置顶窗口后鼠标移至置顶的窗口会导致荧光笔无法使用，而在置顶窗口之外的区域依旧能够使用
Repository: react
Issue: Title  Unnecessary updates to defaultValue and checked properties in <textarea> and <input> elements
Labels: Status: Unconfirmed

###  Description
It looks like React is updating the defaultValue of <textarea> elements and the checked property of <input> elements even when their values haven’t changed. This leads to unnecessary DOM mutations, which can impact performance, especially when there are many components that re-render frequently.

### Steps to Reproduce
Render a controlled <textarea> or <input> with defaultValue or checked set.
Trigger a re-render by updating some other unrelated props.
Notice that React still updates the defaultValue or checked properties, even though the values haven't changed.

### Expected Behavior
React should only update the defaultValue or checked properties when the values actually change, avoiding unnecessary DOM updates.

### Actual Behavior
The properties are being updated unnecessarily, even if the values remain unchanged, leading to redundant DOM mutations.

### Suggested Solution
React should add a check to only update the defaultValue and checked properties if their values have changed. This would reduce unnecessary updates and improve overall performance.

### Environment
React version: [Insert React version]
Browser: [Insert browser and version]
Operating System: [Insert OS name and version]

### Key Words / Search Terms
defaultValue, checked, textarea, input, performance, DOM mutations, unnecessary updates

### Repository Version
[v19.0.0](https://github.com/facebook/react/releases/tag/v19.0.0)