sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: `onTap` callback for `DataRow`
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

Currently, there is no way to press on a row in a Datatable. You can only press on the cells. By adding an `onTap` callback for the whole row, developers can use this to e.g. open details of the row



### Proposal

Add an `onTap` callback to the `Datarow` widget, which works similarly to the `onLongPress` callback, just for a long press.
Repository: vscode
Issue: Test: "Execute Using Profile..." should be "Execute Using Test Profile..."
Labels: polish,testing

I was confused how to run unit tests on web with the test runner. Turns out it was this option, but I didn't realize as I thought it was talking about a regular profile.

![Image](https://github.com/user-attachments/assets/8faddbec-2a9a-413e-a1c2-3727ca18d568)

In terminal land we established a rule that any UI reference to "Terminal profiles" must always include the prefix to prevent this confusion.
Repository: flutter
Issue: Class "App" is declared twice in code provided in Step #5 on "main.dart"
Labels: team-codelabs,p: firebase,P2,triaged-codelabs

I ran into this and asked Gemini to review the code as well as the error messages from my terminal.

"App" is declared twice. Once at the top of main.dart and then at the bottom on lines 15,18, and 19 (at the top) and then again on lines 118 and 119 (at the bottom). Lines may vary given comments or other alterations, but in general, these are the locations in the document. 

Fix: I just renamed the top class to "MyApp" on the top 3 lines which removes the errors and enables display of the project output to device. I'm suggesting the top class be renamed for the codelab.

Page that I'm looking at and the code is referenced: https://firebase.google.com/codelabs/firebase-get-to-know-flutter#4
Repository: godot
Issue: Cannot reliably reposition multiple windows using new 4.3 'Enable Multiple Instances'
Labels: bug,topic:editor,confirmed

### Tested versions

v4.3 stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3060 Laptop GPU (NVIDIA; 31.0.15.4630) - AMD Ryzen 7 5800H with Radeon Graphics (16 Threads)

### Issue description

When multiple windows have been created in 4.3 using the 'Customize Run Instances' menu they often refuse to move when repositioned. Error occurs with an empty project, newly created with the 4.3 editor.  

This machine is able to run 4 instances of a not-empty project without any problem in 4.2. Resource usage is not high while reproducing.

https://github.com/user-attachments/assets/71d7b2f0-36ba-46f2-8b7c-5ef5087ea4a6



### Steps to reproduce

In 4.3 stable, create a new project. In 'Debug' > 'Customize Run Instances' toggle 'Enable Multiple Instances' and set number to 4. Launch the project in the editor and try to move around the windows. 

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: Souris sans frontières : problème 
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

2 PC's : one desktop with 2 displays, 1 laptop. 
Mouse pointer is not visible on 1 display

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: vscode
Issue: "Insert into Terminal" button on chat window's shell code blocks is hard to discover
Labels: under-discussion,panel-chat


Type: <b>Feature Request</b>

In the chat window, when the chat handler responds with a shell code block, you can mouse over it and click "Insert into Terminal". This is great but hard to discover--it requires the mouse over. This may also be an accessibility issue.

We'd like to see a permanent button for inserting into terminal (and probably a corresponding button for code blocks' insert into editor).

![Image](https://github.com/user-attachments/assets/718d0b08-47f7-459a-91b1-a1c32035381e)

VS Code version: Code - Insiders 1.93.0-insider (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:13:15.344Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: pytorch
Issue: torch.library.custom_op: should be able to pass in a tags argument to specify tags
Labels: triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

Or maybe a higher-level API for layout

cc @ezyang @chauhang @penguinwu @bdhirsh
Repository: go
Issue: net: TestCloseRead failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestCloseRead"
```

Issue created automatically to collect these failures.

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

    === RUN   TestCloseRead
    === PAUSE TestCloseRead


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: generateStaticParams validation makes react-router migrations difficult 
Labels: bug

### Link to the code that reproduces this issue

https://github.com/GuiBibeau/react-router-nextapp-reproduction

### To Reproduce


While following the [tutorial to migrate](https://nextjs.org/docs/app/building-your-application/upgrading/from-vite) from a Vite SPA (with react-router),  I am able to build and render the application but hot reloading does not work.

1. clone repo, install dependency and start dev server
2. navigate to home page http://localhost:3000/
3. Click on `Data 1` link on the home page, SPA behavior will work as expected
4. refresh page or trigger hot reloading, page will break

### Current vs. Expected behavior

A first render of `next dev` will work. However regular workflows like hot reloading or refreshing the page will cause the validation from `generateStaticParams` will trigger. This makes an inplace migration from a vite react-router spa application difficult since it breaks regular dev workflows while the migration is happening.

It would be great to have away to turn off this error for a few routes in the next config or other ways.

### Provide environment information

```bash
- **Operating System:**
  - Platform: darwin
  - Architecture: arm64
  - Version: Darwin Kernel Version 23.5.0
  - Available memory: 16384 MB
  - Available CPU cores: 8

- **Binaries:**
  - Node: 20.12.2
  - npm: 10.5.0
  - Yarn: 1.22.22
  - pnpm: 9.1.2

- **Relevant Packages:**
  - Next.js: 14.2.8
  - ESLint Config Next: 14.2.8
  - React: 18.3.1
  - React DOM: 18.3.1
  - TypeScript: 5.5.4

- **Next.js Config:**
  - Output: export
```


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

Developer Experience

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

next dev (local)

### Additional context

We are currently on a vite + react-router SPA setup looking to gradually move to next export and then to full SSR hosting with server components and all the modern stuff. Our goal is to migrate gradually over 12-18 months.
Repository: kubernetes
Issue: [flaky test]  [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim 
Labels: sig/storage,kind/flake,triage/accepted

### Which jobs are flaking?

pull-kubernetes-e2e-gce

### Which tests are flaking?

 [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim 


### Since when has it been flaking?

unknown

### Testgrid link

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/127096/pull-kubernetes-e2e-gce/1831734659084455936

### Reason for failure (if possible)

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/127096/pull-kubernetes-e2e-gce/1831734659084455936

```
{ failed [FAILED] client rate limiter Wait returned an error: context deadline exceeded
In [It] at: k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:580 @ 09/05/24 17:16:05.146
}
```

```
  I0905 17:16:03.310459 64689 resource_quota.go:2228] resource persistentvolumeclaims, expected 1, actual 0
  I0905 17:16:05.146348 64689 resource_quota.go:580] Unexpected error: 
      <*fmt.wrapError | 0xc001170b40>: 
      client rate limiter Wait returned an error: context deadline exceeded
      {
          msg: "client rate limiter Wait returned an error: context deadline exceeded",
          err: <context.deadlineExceededError>{},
      }
  [FAILED] in [It] - k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:580 @ 09/05/24 17:16:05.146
```


### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig api-machinery
Repository: vscode
Issue: Allow opening chat code block in full editor
Labels: feature-request,panel-chat

Allow splitting a code block from panel chat into its own editor so the user can explore it further. Can likely be added as a `...` action in the code block menu
Repository: vscode
Issue: Restart extension will not update settings
Labels: extensions,config,under-discussion

<!-- ⚠️⚠️ 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.92.2
- OS Version: Windows 11

Steps to Reproduce:

1. Install [this extension](https://mega.nz/file/bItUVYrK#KERRqXQDCYFEGlkcPddW1ceNvvW9qHJdlhHyKD8bBmc)
2. This extension contains a simple js that sends a notification containing a test setting value.
3. In this 0.0.1 version, the setting is not added, so as expected, it shows `undefined`.
4. Now install [0.0.2](https://mega.nz/file/yZ8VGQgZ#jb_fwVc6Rp89SjBpbh9OaB4gC-j-kaFKI4fh89Qm8ns)
5. In this version, I set a default value 1 to test setting. The code prompts to restart extension, so restart. However, after the restart, the message still shows `undefined`.
6. Restart vscode, now the notification shows the correct default value 1
Repository: TypeScript
Issue: Inferred project that currently use "current directory of tsserver host" needs some special handling
Labels: Needs Investigation

### 🔍 Search Terms

Inferred project, tsserver current directory

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Inferred projects that use tsserver's current directory (eg project root was not specified and is dynamic file or is single inferred project for all loose files). Esp for all the dynamic files (untitled files etc) this means we lookup package.json and files in tsserver current directory (which in most cases is vscode installation location) that seems undesirable but it also involves how to reference these dynamic files and needs some rethinking. it also ends up looking for `node_modules/@types` for auto type directives as well. 

More prominent with #59844 and some of the tests added at https://github.com/microsoft/TypeScript/pull/59869/files#diff-d3671512f8dff77d5eabeb5694d7eae5e9b94e4d50a066c3e0205981fc102e22R59 show this as well.

### 📃 Motivating Example

Incorrect and unnecessary disk references to non existent files and watching those locations

### 💻 Use Cases

1. What do you want to use this for? 
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?
Repository: pytorch
Issue: DISABLED test_allocator_fuzz (__main__.TestCudaMallocAsync)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 5 workflow(s) with 15 failures and 5 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_allocator_fuzz`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 3859, in test_allocator_fuzz
    action()
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 3851, in free
    assert torch.all(v == x)
RuntimeError: Host and device pointer dont match with cudaHostRegister. Please dont use this feature by setting PYTORCH_CUDA_ALLOC_CONF=use_cuda_host_register:False (default)

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCudaMallocAsync.test_allocator_fuzz

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_cuda.py`

cc @ptrblck @msaroufim @clee2000
Repository: pytorch
Issue: Log missed optimization opportunities due to dynamic shapes in Inductor
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

Inductor has some optimizations that it applies only when something is statically known to be true (e.g., it will not introduce a guard to get the optimization). We should log these so that it is possible for a motivated user to see where they could usefully introduce extra guards to unlock more optimizations at the cost of more compile products.

### Versions

main

cc @chauhang @penguinwu
Repository: PowerToys
Issue: PowerToys Run is slow at looking up VS Code workspaces
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Run-Plugin

### Microsoft PowerToys version

0.84.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Open run box, press `{` key to filter to VS Code workspaces, type the name of one, and observe how it takes 1-2 seconds to display results

### ✔️ Expected Behavior

Much faster results (like it used to be)

### ❌ Actual Behavior

Slow results

### Other Software

VS Code Insiders version info:
```
Version: 1.93.0-insider (system setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:13:15.344Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
```
Repository: godot
Issue: HTTPClient SSE requests (text/event-stream): read_response_body_chunk() fails
Labels: bug,topic:network

### Tested versions

4.3.stable.official


### System information

Windows 11 64-bit 4.3.stable.official

### Issue description

If you try to make a SSE requests (text/event-stream) with the object `HTTPClient`, the connection is opened but then `read_response_body_chunk()` fails to return because the object never enters the status `STATUS_BODY`.

My API is fine because I've tested it in Python with the `requests` library and it does work perfectly.


### Steps to reproduce

```gdscript
if httpclient_has_response or httpclient_status == HTTPClient.STATUS_BODY:
	var headers = httpclient.get_response_headers_as_dictionary()

	httpclient.poll()
	var chunk = httpclient.read_response_body_chunk()
```

Error:
```
Condition "status != STATUS_BODY" is true. Returning: PackedByteArray()
  <C++ Source>   core/io/http_client_tcp.cpp:572 @ read_response_body_chunk()```
```

### Minimal reproduction project (MRP)

Try e.g. https://github.com/gxian/HTTPSSEClient
Apparently it was working on old versions of Godot 4?
Repository: kubernetes
Issue: [flaky test] : [It] [sig-storage] In-tree Volumes [Driver: local] [LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data 
Labels: sig/storage,kind/flake,lifecycle/rotten,needs-triage

### Which jobs are flaking?

pull-kubernetes-e2e-gce 

### Which tests are flaking?

 [sig-storage] In-tree Volumes [Driver: local] [LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data 

### Since when has it been flaking?

unknown

### Testgrid link

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/127096/pull-kubernetes-e2e-gce/1831749638269440000

### Reason for failure (if possible)

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/127096/pull-kubernetes-e2e-gce/1831749638269440000

```
{ failed [FAILED] "test -b /opt/0" should fail with exit code 1, but failed with error message "Timeout occurred"
stdout: 
stderr: : Timeout occurred
In [It] at: k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:704 @ 09/05/24
```


### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig storage
Repository: kubernetes
Issue: [FG:InPlacePodVerticalScaling] Emit a events when resize status changes
Labels: sig/node,kind/feature,priority/important-longterm,triage/accepted

/kind feature

To help with debugging in place pod resize, the Kubelet should emit events along with various resize status changes:

1. Resize accepted: report the resource deltas
2. Resize infeasible: which resources were over capacity
3. Resize deferred: which resources were over available capacity
5. Resize completed
6. Resize error

/sig node
/priority important-longterm
/milestone v1.32
/triage accepted
Repository: ollama
Issue: on ollama.com's profile settings page , email addr shown mangled
Labels: bug,ollama.com

### What is the issue?

on that page , where edit name and bio
the after top header , there is first shown :

username \n
email addr

of the logged in user
then there are the editfields

anyway at my email , gmail , ends with 7 , .. that 7 isnt displayes there on the page
just the addr without the ending 7

greets

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: storybook
Issue: [Documentation]: Storybook backend not found when using static build but works in development
Labels: documentation,needs triage

### Describe the problem

Hello. I'm working on an addon that accesses Storybook's backend through a middleware.js file to make requests to external sources. This works perfectly for development, but upon building the static build, any requests made in the frontend give a 404 error and aren't ever reaching the backend. I'm wondering if there is an alternative undocumented method to make requests that I'm unaware of. As the Storybook Designs addon seems to make requests without a middleware.js file. Any help is much appreciated! Thanks!

### Additional context

_No response_
Repository: vscode
Issue: SCM Graph - support incoming/outgoing changes
Labels: feature-request,scm

<!-- ⚠️⚠️ 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. -->
- Version: 1.93.0
- Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
- Date: 2024-09-04T13:02:38.431Z
- Electron: 30.4.0
- ElectronBuildId: 10073054
- Chromium: 124.0.6367.243
- Node.js: 20.15.1
- V8: 12.4.254.20-electron.0
- OS: Linux x64 6.8.0-40-generic snap

Steps to Reproduce:

1. Use 1.93.0
2. Have incoming changes in a source control repository

On 1.92.0 and earlier, when the experimental source control graph/history was disabled (`"scm.showHistoryGraph": false`), it was possible to view incoming changes just as easily as outgoing / staged / unstaged changes. Now that the source control graph is no longer optional, it is not possible to view them in the same way. This seems quite unnecessary to remove, when the source control graph panel itself can be hidden or at least moved out of view. Furthermore, outgoing changes are still viewable with the same interface, so it makes sense to have incoming changes similarly visible.

A repository with incoming changes, but not shown:
![image](https://github.com/user-attachments/assets/31eaf6f3-8ac7-4930-aea2-a20679daf902)

A repository with outgoing changes, which are shown:
![image](https://github.com/user-attachments/assets/d32ae663-3b77-4a43-a35d-81de841dfbde)
Repository: tauri
Issue: [bug] Call to Dynamic Update Server needs to URL encode + in version number
Labels: type: bug,status: needs triage

### Describe the bug

If you have a Dynamic Update Server defined like this: 

```
"endpoints": [ "https://api.mydomain.com/update?current_version={{current_version}}&target={{target}}&arch={{arch}}" ],
```

And a semver version with build number like this: `1.8.0+1`, the request will get sent like this:

```
GET /update?current_version=1.8.0+1&target=windows&arch=x86_64
```

This will cause the `+` to be converted into a blank space in most servers.  Therefore you get an invalid semver of `1.8.0 1`.  I believe it should be sent like this:

```
GET /update?current_version=1.8.0%2B1&target=windows&arch=x86_64
```

### Reproduction

_No response_

### Expected behavior

The ability to verify with an update server using semver build numbers.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 128.0.2739.63
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.80.1 (3f5fd8dd4 2024-08-06)
    ✔ cargo: 1.80.1 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.11.0
    - npm: 10.8.1

[-] Packages
    - tauri [RUST]: 1.7.2
    - tauri-build [RUST]: 1.5.4
    - wry [RUST]: 0.24.11
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.1

[-] App
```
```


### Stack trace

_No response_

### Additional context

_No response_