sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [go_router] log method should execute when both debugLogDiagnostics and hierarchicalLoggingEnabled set to true 
Labels: package,c: proposal,P2,p: go_router,team-go_router,triaged-go_router

### What package does this bug report belong to?

go_router

### What target platforms are you seeing this bug on?

Android, iOS

### Have you already upgraded your packages?

Yes

### Dependency versions

<details><summary>pubspec.lock</summary>

```lock
version: "14.2.1"
```

</details>


### Steps to reproduce

The change at https://github.com/flutter/packages/pull/6019 by @ValentinVignal disabled logging from `Logger('GoRouter')` when `hierarchicalLoggingEnabled` is set true even when `debugLogDiagnostics` is set to true too.

I think the change supposed that the user will handle logging at `Logger.root` listener but I don't think this is necessary as per https://github.com/dart-lang/logging/blob/8752902b75a476d2c7b64dcf01aaaee885f35c4c/README.md#configuration (Loggers can be individually configured and listened to. When an individual logger has no specific configuration, it uses the configuration and any listeners found at Logger.root)

So in my case I configure the logging individually at each logger's listener and I need the `Logger('GoRouter')` to work at its level to as `debugLogDiagnostics` is set to true.

### Expected results

I expect `Logger('GoRouter')` to log its results when `debugLogDiagnostics` is set to true regardless of `hierarchicalLoggingEnabled` value.

### Actual results

`Logger('GoRouter')` only log its result when `debugLogDiagnostics` is set to true and `hierarchicalLoggingEnabled` is set to false.

### Code sample

Not needed.

### Screenshots or Videos

_No response_

### Logs

_No response_

### Flutter Doctor output

Not needed.
Repository: next.js
Issue: loading file in app/ directory causes components to lose state on router.refresh()
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/emerylin/nextjs/

### To Reproduce

1. npm run dev
2. Goto localhost:3000/playground
3. Click "Set" button, observe that "value" state variable is set to "set"
4. Click "Refresh" button, which calls router.refresh(), and observe that "value" state variable is reset to its initial value of "none"
5. Remove app/loading.js file, or move loading.js under app/playground folder
6. Repeat steps 3-4 and observe that the "value" state variable maintains its value through router.refresh()

### Current vs. Expected behavior

Expected: state variables should maintain their value through router.refresh() even when app/loading.js file is present.

Current: When app/loading.js file is present, state variables lose their value on the first call to router.refresh(), but maintain their value on subsequent calls to router.refresh(). 

Uploaded code example is from a clean install of create-next-app

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: 14.2.5
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: vscode
Issue: OnClick and hover events on gutter icons
Labels: feature-request,editor-api

How could I handle OnClick ad hover events on gutter icons, similar to how breakpoints does?

The intention was to connect it with a decorator (previously created with vscode.window.createTextEditorDecorationType) so the user should **click or hover on the gutter** and create/destroy the decorator assigned to the line where the user clicked.
Repository: godot
Issue: The project setting "Enable Long Press as Right Click" prevents holding down a TouchScreenButton node on exported Android projects
Labels: bug,topic:input

### Tested versions

- Reproducible in: v4.2.stable.official [46dc27791]
- Reproducible in: v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Windows 10.0.22631 (I'm actually using Windows 11) - GLES3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 31.0.15.3623) - 13th Gen Intel(R) Core(TM) i7-13650HX (20 Threads)

### Issue description

In Project Settings > Input Devices > Pointing > Android there is an option called "Enable Long Press as Right Click." If you enable this option, then you will no longer be able to hold down directly on TouchScreenButton node. If you hold in one place, then it will let go of the button as soon as the 'right click' is activated.

The issue does not happen while playtesting. During playtesting, the TouchScreenButton nodes will work as expected. But after I exported the project for Android (apk), I noticed that the buttons would be let go if I held down directly on it. This happened while testing it on my phone, and on BlueStacks on PC (an emulator that can run APKs).

If I moved my finger a little bit or if I held down another finger outside of the TouchScreenButton, then I could hold it down for as long as I wanted. It would only happen when keeping the touch directly on the button in the same spot (so it would initiate a 'right click').

I also tweaked several settings for the TouchScreenButton nodes and exported it each time, but the issue still happened for each export. The issue stopped happening right after I disabled the "Enable Long Press as Right Click" option in the project settings.

Here is a video of the issue happening while running the exported project (APK) on BlueStacks on my PC:

https://github.com/user-attachments/assets/9a5b451b-5a8a-49e6-b30a-ccb0cfdbadcf



### Steps to reproduce

- Enable the option Project Settings > Input Devices > Pointing > Android > Enable Long Press as Right Click
- Create a TouchScreenButton node (it's easier to see the issue if there is a different texture for normal and pressed)
- Export the project for Android as an APK
- Run the exported project
- Hold down in one spot of the TouchScreenButton (do not drag or use multiple fingers)
- The button should be let go after about half a second

### Minimal reproduction project (MRP)

[TouchScreenButton bug.zip](https://github.com/user-attachments/files/16405536/TouchScreenButton.bug.zip)
Repository: vscode
Issue: Catch-all check for deletion of nameless folder
Labels: bug,file-explorer,confirmation-pending

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

### Context
While I was developing over SSH, I lost the connection to the remote server just as I attempted to create a new folder. After reconnection, the file sidebar in Visual Studio Code still had the folder in it, but there was no name next to the icon; just the icon itself. In an effort to remove this "ghost" folder, I right-clicked the entry in the sidebar and chose "Delete Permanently." Just as I hit "Delete" in the confirmation dialog, I realized it was probably not a good idea, and my fears soon came true: the parent of the nameless folder, including ~80% of the project I had open, was deleted. Shortly thereafter, Visual Studio Code became unresponsive and had to be restarted.
Luckily, external backups combined with Visual Studio Code's local history feature were enough to restore all but the last few minutes worth of code, but another person in a similar situation might not be quite so lucky.

### Theory
Not knowing VSC's internals, I would imagine that, somewhere along the line, VSC concatenated the path to the parent folder (/parent" with the name of the child in an effort to get "/parent/child" and delete the child folder using that path; however, because VSC believed I had selected a folder with no name/an empty string for a name, the result of this concatenation was just "/parent", leading to the recursive deletion of the parent folder.

### Suggestion
I understand the bug that led to this occurrence is far too specific and unreproducable for a proper bug report or fix to be possible. However, would it be feasible for a sort of "catch-all" check to be implemented in the UI code that would prevent deletion of a nameless folder brought about by any situation? (I would assume there are more ways this could occur than just the way it did in my instance).
I acknowledge that this may be seen as an ideologically poor solution, but, given the catastrophic results it could prevent for what seems like little maintenance, I make this suggestion nonetheless.

### System/installation info
Ubuntu 23.10 locally, 24.04 on server
Local extensions enabled: None other than the official ones for development over SSH
Server extensions: `ESLint`, `Vue - Official`
<details>
<summary> Detailed information </summary>
<pre>
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-44-generic
</pre>
</details>
Repository: flutter
Issue: Potential double-free of OpenGL texture in SurfaceTexture interop.
Labels: platform-android,P2,team-engine,triaged-engine

In Flutters SurfaceTexture based interop ([Skia](https://github.com/flutter/engine/blob/7f7ad741fefa9b3ae3bc436e0663d606bf7c664d/shell/platform/android/surface_texture_external_texture_gl_skia.cc), [Impeller](https://github.com/flutter/engine/blob/7f7ad741fefa9b3ae3bc436e0663d606bf7c664d/shell/platform/android/surface_texture_external_texture_vk_impeller.cc)), we use [`attachToGLContext`](https://developer.android.com/reference/android/graphics/SurfaceTexture#attachToGLContext(int)) and [`detachFromGLContext`](https://developer.android.com/reference/android/graphics/SurfaceTexture#attachToGLContext(int)). The pattern is that we give SurfaceTexture a GL handle that has no backing store before `attachToGLContext` and delete the handle after `detachFromGLContext`.

But, the docstring for [`detachFromGLContext`](https://developer.android.com/reference/android/graphics/SurfaceTexture#detachFromGLContext()) states, "The OpenGL ES texture object will be deleted as a result of this call.".

This means that we are double-freeing the GL texture ([Skia](https://github.com/flutter/engine/blob/7f7ad741fefa9b3ae3bc436e0663d606bf7c664d/shell/platform/android/surface_texture_external_texture_gl_skia.cc#L55), [Impeller](https://github.com/flutter/engine/blob/7f7ad741fefa9b3ae3bc436e0663d606bf7c664d/shell/platform/android/surface_texture_external_texture_vk_impeller.cc#L168)). The detach happens in `SurfaceTextureExternalTexture::Detach` for reference.

We may be depending on the OpenGL implementation not re-using handles and ensuring that deleted handles are not double-freed. On handle re-use, we could be nuking an unrelated handle and causing corruption.

We should verify that the documented Android guidance is correct and ensure we don't free those textures.
Repository: vscode
Issue: extension error
Labels: info-needed

<!-- ⚠️⚠️ 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?: I do not know. (exntension list keep loading with a clock at the left bottom of the extension icon.)

<!-- 🪓 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: win 10
- OS Version: 1.91.1

Steps to Reproduce:

1. Error "A shared background process terminated unexpectedly. Please restart the application to recover" appears when starting VSCode while restarting not works.

PS: Extension may be the Key of the error. Several days before, my Copilot expired and I installed activated Codeium extension. After that I did not use VSCode until now and the error appears.

Thanks for your help!
Repository: pytorch
Issue: 2:4 semi structured sparsity matmul not supported on hopper
Labels: oncall: quantization,module: cuda

### 🐛 Describe the bug

i am trying to benchmark semi structured matmuls on hopper (sm90) and trying out the pytorch semi structured tutorial to get a understand of the torch sparsity APIs but unfortunately pytorch sparsity doesnt support anything besides sm80. i tried both the cutlass code path and the cusparseLt code path but none of them work.

https://pytorch.org/tutorials/prototype/semi_structured_sparse.html

## error msg
```python
python3 structured.py 
Traceback (most recent call last):
  File "/home/ubuntu/clusterMAX/structured.py", line 51, in <module>
    linear.weight = torch.nn.Parameter(to_sparse_semi_structured(linear.weight))
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/sparse/semi_structured.py", line 378, in to_sparse_semi_structured
    return SPARSE_SUBCLASS.from_dense(original_tensor)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/sparse/semi_structured.py", line 537, in from_dense
    packed=torch._cslt_compress(original_tensor),
RuntimeError: CUDA error: architecture mismatch when calling `cusparseLtInit(&handle)`
```

## reprod
```python
import torch
from torch.sparse import to_sparse_semi_structured, SparseSemiStructuredTensor
from torch.utils.benchmark import Timer
SparseSemiStructuredTensor._FORCE_CUTLASS = False

# mask Linear weight to be 2:4 sparse
mask = torch.Tensor([0, 0, 1, 1]).tile((3072, 2560)).cuda().bool()
linear = torch.nn.Linear(10240, 3072).half().cuda().eval()
linear.weight = torch.nn.Parameter(mask * linear.weight)

x = torch.rand(3072, 10240).half().cuda()

with torch.inference_mode():
    dense_output = linear(x)
    dense_t = Timer(stmt="linear(x)",
                    globals={"linear": linear,
                             "x": x}).blocked_autorange().median * 1e3

    # accelerate via SparseSemiStructuredTensor
    linear.weight = torch.nn.Parameter(to_sparse_semi_structured(linear.weight))

    sparse_output = linear(x)
    sparse_t = Timer(stmt="linear(x)",
                    globals={"linear": linear,
                             "x": x}).blocked_autorange().median * 1e3

    # sparse and dense matmul are numerically equivalent
    assert torch.allclose(sparse_output, dense_output, atol=1e-3)
    print(f"Dense: {dense_t:.3f}ms Sparse: {sparse_t:.3f}ms | Speedup: {(dense_t / sparse_t):.3f}x")
```

### Versions

h100, nightly

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @msaroufim @ptrblck
Repository: vscode
Issue: Slashes in `terminal.integrated.cwd` converted to backslashes on Linux remote host and Windows host
Labels: bug,remote,confirmation-pending,terminal-process

<!-- ⚠️⚠️ 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 except remote extension

<!-- 🪓 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.91.1 x64
- OS Version: Windows 11 22631

Steps to Reproduce:

1. Open a workspace of a linux remote host
2. Set `"terminal.integrated.cwd"` in the workspace settings to a path, e.g. "/data/user/"
3. Launch a new terminal

The terminal process failed to launch: Starting directory (cwd) "\data\user" does not exist.
![image](https://github.com/user-attachments/assets/b3d0d533-7293-48ec-8b08-77e04b12072a)
Repository: pytorch
Issue: failed to build v2.3.0 docker image
Labels: module: build,triaged,module: docker

### 🐛 Describe the bug

```
git checkout v2.3.0
make -f docker.Makefile
```
Error message:
```
 => [build 3/5] COPY --from=submodule-update /opt/pytorch /opt/pytorch                                                                                                 10.8s 
 => ERROR [build 4/5] RUN make triton                                                                                                                                   2.7s 
------                                                                                                                                                                       
 > [build 4/5] RUN make triton:                                                                                                                                              
#25 0.312 pip3 uninstall -y triton                                                                                                                                           
#25 0.793 WARNING: Skipping triton as it is not installed.
#25 0.793 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
#25 1.319 Looking in indexes: https://download.pytorch.org/whl/nightly/
#25 2.651 ERROR: Could not find a version that satisfies the requirement pytorch-triton==2.3.0+79c6c9b209 (from versions: 2.0.0+0d7e753227, 2.0.0+3aa3d7024e, 2.0.0+af76c989eb, 2.0.0+b8b470bc59, 2.0.0+c8bfe3f548, 2.0.0+d54c04abe2, 2.1.0, 2.1.0+2c32f43999, 2.1.0+3c400e7818, 2.1.0+440fd1bf20, 2.1.0+46672772b4, 2.1.0+6e4932cda8, 2.1.0+7d1a95b046, 2.1.0+9820899b38, 2.1.0+9e3e10c5ed, 2.1.0+bcad9dabe1, 2.1.0+e6216047b8, 2.1.0+e650d3708b, 2.2.0+e28a256d71, 3.0.0+45fff310c8, 3.0.0+901819d2b6, 3.0.0+989adb9a29, 3.0.0+a9bc1a3647, 3.0.0+dedb7bdf33)
#25 2.651 ERROR: No matching distribution found for pytorch-triton==2.3.0+79c6c9b209
#25 2.716 make: *** [Makefile:37: triton] Error 1
------
executor failed running [/bin/sh -c make triton]: exit code: 2
make: *** [docker.Makefile:78: devel-image] Error 1

```

### Versions

v2.3.0

cc @malfet @seemethere
Repository: go
Issue: proposal: io,net: add WriteMany interface
Labels: Proposal

### Proposal Details

This proposal aims at making a user-implementable version of [`net.Buffers`](https://pkg.go.dev/net#Buffers).

Add a new interface to `io` and implement it on `net.*` which implement `net.buffersWriter`:
```go
type ManyWriter interface {
 // WriteMany has the same semantics as appending the buffers back to back into one buffer and calling [Writer.Write] method,
 // but it allows to remove the need to allocate and copy all the buffers in one contiguous memory region.
 // The implementation cannot write to any of the passed buffer or buffers slice.
 WriteMany(...[]byte) (n int64, err error)
}
```
note: this return `int64` because it would be easy to build let's say 16GiB buffer on a 32bits pointer architecture by having the byte arrays alias each other.

`(*net.Buffers).WriteTo` would also check if the underlying implementation supports `io.ManyWriter` as well as `net.buffersWriter`.
Repository: rust
Issue: `./x test <path_to_test>` does not work on msys2
Labels: T-bootstrap,E-medium,C-bug,A-contributor-roadblock,A-compiletest,E-needs-investigation

Currently, the `run-make` test suite on windows [still can only run in msys2](https://rustc-dev-guide.rust-lang.org/tests/running.html?highlight=msys2#windows).

When trying to use `./x test <path_to_specific_test>` inside the MSYS2 MSYS program, the usual test path/filters that works on other platforms (including outside of msys2 but in powershell or cmd) does not work within MSYS2 MSYS. This is not specific to the run-make test suite, but run-make tests are mentioned because they caused the requirement of msys2 in the first place.

For example, for a test `tests/run-make/CURRENT_RUSTC_VERSION`:

### Examples that doesn't work

These *do* work outside MSYS2 MSYS on windows (for backslash path separators) and on other platforms, but not within MSYS2 MSYS:

```
./x test tests/run-make/CURRENT_RUSTC_VERSION
./x test tests\\run-make\\CURRENT_RUSTC_VERSION
```

This doesn't work in MSYS2 MSYS either

```
./x test tests\run-make\CURRENT_RUSTC_VERSION
```

### Examples that do work

This incantation *does* work, but it is annoying to type

```
./x test run-make --test-args="tests/run-make/CURRENT_RUSTC_VERSION"
```
Repository: ui
Issue: [bug]: Chadcn/UI Combobox code doesn't work at all
Labels: bug

### Describe the bug

I have been attempting to use the Combobox provided at:
https://ui.shadcn.com/docs/components/combobox

I have tried several versions of the Combobox, only to discover that they all fail in different ways!

My first attempt was to use the code under the "Usage" section. Folks should be aware that there is a typo in that code. The <Command> tag is missing a "/" in its closing tag.

Once I corrected the Command closing tag, I ran the page. It displayed with no problems, but for some reason I cannot select any of the items in its list. They do not change color when the mouse moves over them, and they aren't electe when they are clicked. It is almost as if they are all disabled.

I next tried to use some of the Comboboxes in the Examples section. After installing the @radix-ui/react-icons (instruction of the installation of which would have been good if included with the installation instructions), I ran the Combobox. It worked well enough until I clicked on it. It disappeared.

Running it while monitoring a console, I am seeing that the component is crashing for the following reason:

`Uncaught TypeError: items is undefined

    A index.mjs:1
    U2 index.mjs:1
    item index.mjs:1
    Me index.mjs:1
    Me index.mjs:1
    React 13
    useCallbackRef useCallbackRef.tsx:15
    setValue useControllableState.tsx:27
    onOpenToggle Popover.tsx:82
    handleEvent primitive.tsx:10
    React 23
    <anonymous> main.tsx:6
`
This "item" is not anywhere in the component. It is obviously missing from one of the dependencies.


### Affected component/components

Combobox

### How to reproduce

1. Copy the shadcn Combox code and write it into a file in the Vite project
2. Place the Combobox's tag into the App.tsx file
3. Run the application
4. Attempt to use the Combobox.

### Codesandbox/StackBlitz link

https://stackblitz.com/edit/vitejs-vite-8ucaux?file=index.html&terminal=dev

### Logs

_No response_

### System Info

```bash
Problem occurs on all major browsers
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues