sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Installation Does Not Support Local User Account Folder Redirection
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Installer

### Steps to reproduce

1. In File Explorer right click the local user account's Desktop, Documents, Pictures, Etc folders and click properties.
2. In Location tab change the folder location.  In my case it is a folder on a mapped network drive N:.
3. Try to install Power toys using the machine (all users) installer from GitHub.

### ✔️ Expected Behavior

PowerToys should install regardless of where the users' folders are pointing at.




### ❌ Actual Behavior

Powertoys Installer errors and fails with error:  Invalid Drive N:\

Workaround is to logout and install on an account that does not use folder redirection.  Power toys will still run and operate fine on the redirected account, only installation is the issue.

![PTError](https://github.com/microsoft/PowerToys/assets/99924349/3b4c26ac-ed11-46cc-a9b9-9ed1e8953c71)

/

### Other Software

None
Repository: neovim
Issue: quickfix: incremental search/replace (substitution)
Labels: enhancement,cmdline-mode,quickfix

### Problem

Incremental searching is amazing for a single file. However, when I want to substitute across all files in my quickfix list (e.g. `cfdo %s/foo/bar`), I am not given the same incremental search experience. 

### Expected behavior

Incremental searching should work for the quickfix list.
Repository: material-ui
Issue: [docs] react in jsx scope
Labels: docs,dx

### Summary

<img width="837" alt="SCR-20240906-ofzf" src="https://github.com/user-attachments/assets/3370ece9-9cf8-41a9-b958-945755839af2">

https://mui.com/material-ui/react-button/#basic-button

See the:

```jsx
import * as React from 'react';
```

What is this for? Since React 17.0.0 https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html#removing-unused-react-imports and the introduction of a new JSX transform, the import of React doesn't no longer need to be in the scope. We don't support older versions now:

https://github.com/mui/material-ui/blob/44e3ce3034de19f81aaec36c7a866cf9d45d9885/packages/mui-material/package.json#L82

So most of the demos in the docs could be written without the import of React. This would be simpler. It's actually a DX problem because of https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/react-in-jsx-scope.md.

- Vite (latest version) warns when starting a new project and copying and pasting our demos in the docs:
<img width="901" alt="SCR-20240511-oeqy" src="https://github.com/mui/material-ui/assets/3165635/3517617b-24cb-43ea-8908-33873d282d24">

- Next.js (latest version) doesn't say anything, it's happy with having `import * as React from 'react'` or not having it.

### Examples

They don't have those imports:

- https://mantine.dev/core/chip/
- https://ui.shadcn.com/docs/components/dialog

### Motivation

In the past, we didn't make the change because there were too many React users <17.0.0. But this seems to be mostly OK now:

<img width="223" alt="SCR-20240906-opdn" src="https://github.com/user-attachments/assets/9abe5f3c-cbf6-4d62-8709-8b7d63e5097b">

https://tools-public.mui.com/prod/pages/npmVersion?package=react

I assume that all bundlers use the new JSX transform.

### Context

Related a bit to #38966.
Repository: ollama
Issue: Partial pruning does not wrok
Labels: bug

### What is the issue?

```
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:660 msg="couldn't get file path for 'sha256:cfcf93119280c4a10c1df57335bad341e000cabbc4faff125531d941a5b0befa:partial:13': invalid digest format"
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:660 msg="couldn't get file path for 'sha256:cfcf93119280c4a10c1df57335bad341e000cabbc4faff125531d941a5b0befa:partial:67': invalid digest format"
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:660 msg="couldn't get file path for 'sha256:4fe022a8902336d3c452c88f7aca5590f5b5b02ccfd06320fdefab02412e1f0b:partial:18': invalid digest format"
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:660 msg="couldn't get file path for 'sha256:431800fe7a30f378018e76cdec8ed5f99e6f81b22fc5f63b0486e326f0b25545:partial:37': invalid digest format"
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:660 msg="couldn't get file path for 'sha256:4fe022a8902336d3c452c88f7aca5590f5b5b02ccfd06320fdefab02412e1f0b:partial:23': invalid digest format"
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:660 msg="couldn't get file path for 'sha256:4fe022a8902336d3c452c88f7aca5590f5b5b02ccfd06320fdefab02412e1f0b:partial:8': invalid digest format"
time=2024-05-08T21:17:41.854-04:00 level=INFO source=images.go:704 msg="total unused blobs removed: 190"
```

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: PowerToys
Issue: PowerToys Run Web Search plugin can't open Arc
Labels: Issue-Bug,Help Wanted,Product-PowerToys Run,Run-Plugin

### Microsoft PowerToys version

0.80.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. Set the default browser as Arc.
2. Enable PoerToys Run and the built-in Web Search plugin with direct activation command set to "??". 
3. Trigger PowerToys Run, type "?? my search query".
4. Select the "Search the web in Arc" option.

### ✔️ Expected Behavior

Open a new tab in Arc and navigate to search results page for "my search query".

### ❌ Actual Behavior

Sometimes an error message appears saying "Failed to open Arc". Other times focus switches to Arc, but no new tab is opened.

### Other Software

[Arc from The Browser Company](https://arc.net/)
- Build Info: 1.0.1.24682 (0000)
- OS Version: 10.0.22621
- Chromium Engine Version 124.0.6367.92
Repository: vscode
Issue: Logpoints printed twice when debugging VS Code
Labels: bug,debug

Debug VS Code, set logpoints, look at "internal" debug console.

I don't remember seeing this, did something change with logpoints?

<img width="614" alt="image" src="https://github.com/microsoft/vscode/assets/323878/f113de4b-a73a-42a7-bdb7-c70721e7cc19">
Repository: godot
Issue: Camera2D's editor draw doesn't respect window stretch scale
Labels: bug,topic:editor,usability,topic:2d

### Tested versions

- Reproducible in: 4.3-dev6, 4.2.2-stable, 4.1-stable, 4.0-stable, 3.5.3-stable

### System information

Godot v4.3.dev6 - macOS 14.4.1 - Vulkan (Mobile) - integrated Apple M1 Max - Apple M1 Max (10 Threads)

### Issue description

Camera2D's ```editor_draw_screen``` preview does not accurately reflect the screen rectangle when using a non-unity scaling factor for the ```display/window/stretch/scale``` project setting.

Editor preview (actual):
<img width="1608" alt="Editor preview (actual)" src="https://github.com/godotengine/godot/assets/29121925/86413ba6-2443-4160-a0da-e6b0900608f1">

Running the scene:
<img width="688" alt="Scene" src="https://github.com/godotengine/godot/assets/29121925/05563a93-db52-43e6-b439-ea3cc94baaba">
Note how the drawn screen rectangle in the editor contains the entire sprite, whereas running the scene shows that the sprite actually eclipses the screen rectangle.

Expected editor preview, simulated by setting the Camera2D's ```zoom``` to the stretch scale:
<img width="1608" alt="Simulated expected editor preview" src="https://github.com/godotengine/godot/assets/29121925/e14683e1-7e0d-4bdf-9031-e6bc3653321e">

### Steps to reproduce

- Add a Camera2D
- Under project settings → display → window → stretch, set ```scale``` to a value other than 1

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Code selection does not allow scrolling while moving the mouse
Labels: bug,topic:gui

### Tested versions

v3.5.stable.official [991bb6ac7]
v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3070 Ti Laptop GPU (NVIDIA; 31.0.15.5222) - 12th Gen Intel(R) Core(TM) i9-12900H (20 Threads)

### Issue description

When editing a gdscript and selecting lines of code. If you move the mouse, it works. Or if you scroll, it works. However, if you try to move the mouse and scroll, then the scroll does nothing.

### Steps to reproduce

Highlight some code holding left mouse button, and while moving the mouse left and right, try to scroll, and it will not.

### Minimal reproduction project (MRP)

Any project with a script will work
Repository: pytorch
Issue: Is it possible to serialize a torch.cuda.CUDAGraph into disk or CPU memory
Labels: module: cuda,triaged,module: cuda graphs

Is it possible to save a `torch.cuda.CUDAGraph` into disk or CPU memory and load it back later for replay?

cc @ptrblck @msaroufim @mcarilli @ezyang @eellison @peterbell10
Repository: ollama
Issue: Update command for Linux version
Labels: feature request,linux,install

Would be cool to see an update command to the Linux CLI like the update button on Mac. Would be way easier to run`ollama --update`` instead of having to run the entire installation command again manually.
Repository: bitcoin
Issue: Load PSBT error: Unable to decode PSBT
Labels: Wallet,PSBT

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

"Load PSBT from ..." from menu, error shows:
`Unable to decode PSBT 
Unsigned tx does not have empty scriptSigs and scriptWitnesses.: unspecified iostream_category error`

decodepsbt and analyzepsbt show the same error too:
`TX decode failed Unsigned tx does not have empty scriptSigs and scriptWitnesses.: unspecified iostream_category error (code -22)`

### Expected behaviour

I expect Load PSBT success.

And same procedure works fine in another wallet of test net. Both wallets are not watch-only

### Steps to reproduce

I test PSBT in my wallet today, create a transaction in Bitcoin Core, click "send" and "create unsigned", then "Load PSBT from ..." from menu

I'm using prune mode for block chain. This address I made tx was obtained by importprivkey, and then covert to Descriptor Wallets by migratewallet.

I found the [source code](https://github.com/bitcoin/bitcoin/blob/master/src/psbt.h):

>                  case PSBT_GLOBAL_UNSIGNED_TX:
>                 {
>                     if (!key_lookup.emplace(key).second) {
>                         throw std::ios_base::failure("Duplicate Key, unsigned tx already provided");
>                     } else if (key.size() != 1) {
>                         throw std::ios_base::failure("Global unsigned tx key is more than one byte type");
>                     }
>                     CMutableTransaction mtx;
>                     // Set the stream to serialize with non-witness since this should always be non-witness
>                     UnserializeFromVector(s, TX_NO_WITNESS(mtx));
>                     tx = std::move(mtx);
>                     // Make sure that all scriptSigs and scriptWitnesses are empty
>                     for (const CTxIn& txin : tx->vin) {
>                         if (!txin.scriptSig.empty() || !txin.scriptWitness.IsNull()) {
>      ---->                  throw std::ios_base::failure("Unsigned tx does not have empty scriptSigs and scriptWitnesses.");
>                         }
>                     }
>                     break;
>                 }

### Relevant log output

no relevant log.

### How did you obtain Bitcoin Core

Pre-built binaries

### What version of Bitcoin Core are you using?

Bitcoin Core version v27.0.0

### Operating system and version

MacOS 14.4.1

### Machine specifications

_No response_
Repository: next.js
Issue: server actions block navigation
Labels: create-next-app,bug,Navigation

### Link to the code that reproduces this issue

https://github.com/scrabase/bug-next-server-actions-block-navigation

### To Reproduce

1. clone above reproduced github repo
2. go to the cloned folder
3. in command terminal, type [pnpm install]
4. go to localhost:3000 in web browser
5. click button
6. while pending, try to navigate by clicking a link
7. you can see the bug

### Current vs. Expected behavior

current: navigation blocked when server action running
expected: navigation should not blocked when server action long running

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: 1.22.18
  pnpm: 8.15.1
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

create-next-app, Navigation

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

https://github.com/vercel/next.js/issues/49425 resolved this issue.
But in next@14.2.3 this bug this bug occurred again.
I have checked that canary versions also have this bug.


I just copied https://github.com/Fredkiss3/bug-next-server-actions-blocking-navigation this repo and did just chagned to latest next version and bug occured

in summary:
next@13.4.20-canary.1 -> no bug
next@14.2.3 -> bug
Repository: react
Issue: [React 19] allow opting out of automatic form reset when Form Actions are used
Labels: React 19

## Summary

repo: https://github.com/stefanprobst/issue-react-19-form-reset

react 19@beta currently will automatically reset a form with uncontrolled components after submission. it would be really cool if there was a way to opt out of this behavior, without having to fall back to using controlled components - especially since component libraries (e.g. [`react-aria`](https://react-spectrum.adobe.com/react-aria/forms.html)) have invested quite a bit of time to work well as uncontrolled form elements.

the main usecase i am thinking of are forms which allow saving progress, or saving a draft, before final submit. currently, every "save progress" would reset the form.
Repository: kubernetes
Issue: Allow labels feature.node.kubernetes.io by cloud provider
Labels: sig/cloud-provider,triage/accepted

Hello

Can we add capability to set `feature.node.kubernetes.io/<feature-name>` by cloud provider?
I believe they was designed for that https://kubernetes.io/docs/reference/labels-annotations-taints/#feature-node-kubernetes-io

And probably `node.cloudprovider.kubernetes.io/` 

@mmerkes
Thank you.

https://github.com/kubernetes/kubernetes/blob/eeb42fa54306d1956b7df8d855b1e8219c9f9a53/staging/src/k8s.io/cloud-provider/controllers/node/node_controller.go#L545-L558
Repository: next.js
Issue: navigation from `pages` directory to `app` does not refresh page which results in a blank page
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/bestLessons/next-js-routing-issue

### To Reproduce

1. Open `/me` page. There should be 2 buttons. Each of them  uses `router.push` to navigate to different pages which are located in the `app` directory
<img width="400" alt="image" src="https://github.com/vercel/next.js/assets/16179389/04efa61c-8f9d-410c-b0a3-45754dfe5364">

2. Click on `Go to /john/posts/lorem-slug` button - page is blank
3. Press reload the page button in the browser 
<img width="202" alt="image" src="https://github.com/vercel/next.js/assets/16179389/42e48521-8fb7-4c18-b642-4200ffa1d224">

4. Page loads correctly and there should be some content 
<img width="400" alt="image" src="https://github.com/vercel/next.js/assets/16179389/6a4f4f98-bd28-4716-91bd-c75a7366c91d">

Attaching also video reproduction of the issue
https://github.com/vercel/next.js/assets/16179389/ddcd4612-6eb4-47fc-a7d7-ce787ba3e876





### Current vs. Expected behavior

When navigating from `pages` directory to `app` I expect full page reload which will load page correctly instead of seeing the blank page as it is now

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed)

### Additional context

Seems like issue happens because of `catchAll` route which is in the pages directory
<img width="385" alt="image" src="https://github.com/vercel/next.js/assets/16179389/cb3ac7e1-caf7-4dfc-b3fe-7ff2dd890fdd">

there are 2 routes which are similar 
```
app      [username]/posts/[slug]/page.tsx
pages  [username]/[...directLinkId].tsx
```
Repository: ollama
Issue: bge-m3 
Labels: model request

https://huggingface.co/vonjack/bge-m3-gguf
from: https://github.com/ggerganov/llama.cpp/issues/6007
I am looking for recommendations on a high-quality multilingual embedder that includes support for Portuguese. Anything better than https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2 would be nice.
Repository: node
Issue: [DOC] : Error Handling Missing in fs.copyFile() Documentation
Labels: doc,fs

# Error Handling Missing in fs.copyFile Callback Documentation
![node-doc-1](https://github.com/nodejs/node/assets/112153702/6e1740cd-0683-40bf-8369-453074c5b6b4)

## Description
The Node.js documentation for the `fs.copyFile()` method lacks information about potential errors that may occur in the callback function. Specifically, there is no mention of how errors within the callback are handled.



## Context
When using the `fs.copyFile()` method in Node.js, developers rely on the documentation to understand how to handle potential errors. However, the current documentation does not adequately address error handling within the callback function.
![node-doc-2](https://github.com/nodejs/node/assets/112153702/0c44de76-c441-4f9c-9efc-f2e70a92a8b0)


## Expected Behavior
The documentation for `fs.copyFile()` should provide information about potential errors that may occur within the callback function, along with guidance on how to handle them.
![image](https://github.com/nodejs/node/assets/112153702/ce34ba35-9de4-47a5-bc55-9978c2c6c5d5)


## Actual Behavior
The documentation does not mention anything about errors that may occur within the callback function.

![error](https://github.com/nodejs/node/assets/112153702/8cefd92d-ad00-4f5d-b863-96dc93de24b4)


## Steps to Reproduce (if applicable)
1. Refer to the Node.js documentation for `https://nodejs.org/api/fs.html#fscopyfilesrc-dest-mode-callback`.
2. Note the absence of information regarding error handling within the callback function.
Repository: vscode
Issue: Terminal file link detection can't detect paths containing spaces
Labels: bug,confirmed,terminal-links

<!-- ⚠️⚠️ 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.89.0 (user setup)
Commit: b58957e67ee1e712cebf466b995adf4c5307b2bd
Date: 2024-05-01T02:09:22.859Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.19045
```

https://github.com/microsoft/vscode/assets/68118705/5263e7d5-e9a8-412e-b3bf-e7454481500d
Repository: vscode
Issue: BUG: When copy and pasting a comment into code, align it with the current indentation
Labels: bug,editor-autoindent

<!-- ⚠️⚠️ 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.89.0 (user setup)
Commit: b58957e67ee1e712cebf466b995adf4c5307b2bd
Date: 2024-05-01T02:09:22.859Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10

Steps to Reproduce:

1. Copy comment
2. Paste it

ER:
Comment is pasted with same indentation as code

AR:
Comment is pasted with spaces before it or not indentation at all
Repository: storybook
Issue: [Bug]: Viewports aren’t reset when navigating away from a story with a default viewport
Labels: bug,addon: viewport

### Describe the bug

When navigating to a story with a `defaultViewport`, that viewport is correctly applied, and the `globals` query param in the URL is updated accordingly. When navigating away to a story without an explicit viewport, the global stays there, meaning that the viewport is still applied, even though the story doesn't have a default viewport.

### To Reproduce

- Open a regular story without a viewport: [https://next--635781f3500dd2c49e189caf.chromatic.com/?path=/story/components-modal--fixed-height](https://next--635781f3500dd2c49e189caf.chromatic.com/?path=/story/components-modal--fixed-height&globals=viewport:mobile1)
- Navigate to the story Manager/Mobile/About/Default - which has a default mobile viewport
- Navigate to a story without a viewport like Components/Modal/Default
- See that the mobile viewport is still applied even though it’s not part of that story

### System

```bash
Storybook 8.1.0-alpha.8
```


### Additional context

_No response_