sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: nvm
Issue: [feature request] display the previous version
Labels: feature requests

When upgrading (or downgrading, either way) NodeJS through `nvm` it would be nice to see the from version, e.g.

```
$ nvm i stable

Current version: v22.0.0 (npm v9.0.0)
Now using node v23.4.0 (npm v10.9.2)
```

(It's just a small satisfaction to see if anything got updated)
Repository: next.js
Issue: React Compiler Causing Hydration Error in Dev Mode When Prop has New Line in Client Component
Labels: Output (export/standalone)

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/sxxov/nextjs-15-and-react-compiler-client-component-prop-with-newline-hydration-error-repro/main?file=%2Fapp%2FHello.tsx%3A3%2C31

### To Reproduce

1. Start the application (`next dev`)
2. Visit the page
3. Observe the hydration error in the console
4. Remove the new line in `Hello.tsx`'s `data-anything` prop
5. Observe successful hydration

### Current vs. Expected behavior

There should be no hydration error.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.12.1
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 15.1.0 // Latest available version is detected (15.1.0).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Output (export/standalone)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: vscode
Issue: Merge editor: add setting to auto navigate to next conflict
Labels: feature-request,merge-editor

This would be exactly the same as `merge-conflict.autoNavigateNextConflict.enabled` but for the merge editor.

Previous issue requesting this for regular in-file merge conflicts: https://github.com/microsoft/vscode/issues/45853
Repository: tauri
Issue: [bug] TypeScript error when creating webviewWindow from the latest documentation example code
Labels: type: bug,good first issue,status: needs triage

### Describe the bug

When I use the following [example code](https://v2.tauri.app/reference/javascript/api/namespacewebviewwindow/) from the latest Tauri documentation to create a `WebviewWindow`:

```typescript
import { Window } from "@tauri-apps/api/window";
import { Webview } from "@tauri-apps/api/webview";

const appWindow = new Window("uniqueLabel");

// loading embedded asset:
const webview = new Webview(appWindow, "theUniqueLabel", {
  url: "path/to/page.html",
});
```

I encounter a TypeScript error that prevents the code from passing lint checks and strict mode compilation:

```
Argument of type '{ url: string; }' is not assignable to parameter of type 'WebviewOptions'.
  Property 'x' is missing in type '{ url: string; }' but required in type 'WebviewOptions'.
```

### Cause of the Issue

The TypeScript definition for `WebviewOptions` in `@tauri-apps/api/webview.d.ts` requires the properties `x`, `y`, `width`, and `height` as mandatory fields. This conflicts with the example code provided in the documentation, where only the url field is specified.

Additionally, the behavior when these parameters are not provided is unclear. Should these values default to specific dimensions and positions, or is their omission invalid? This discrepancy creates confusion when using the API.

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.4.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.16.0
    - npm: 10.8.1

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-http 🦀: 2.0.4
    - @tauri-apps/plugin-http : 2.0.1 (outdated, latest: 2.2.0)
    - tauri-plugin-fs 🦀: 2.1.0
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-os 🦀: 2.0.1
    - @tauri-apps/plugin-os : 2.0.0 (outdated, latest: 2.2.0)
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.1 (outdated, latest: 2.2.0)
    - tauri-plugin-log 🦀: 2.0.2
    - @tauri-apps/plugin-log : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../out
    - devUrl: http://localhost:3000/
    - framework: React (Next.js)
    - bundler: Webpack
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: Reactivating Terminals issue
Labels: bug,terminal,python


Type: <b>Bug</b>

There are an error that is happening to everyone whom use Python with VS and is the 'reactivating terminals issue' it loads forever and never activated the terminals to use python, here is the issue: 
2024-08-07 18:35:35.873 [error] sendStartupTelemetry() failed. s [Error]: Failed to resolve env "/mnt/data-linux/miniconda3"
    at ae (/home/user/.vscode-insiders/extensions/ms-python.python-2024.12.2-linux-x64/out/client/extension.js:2:1968174)
    at oe (/home/user/.vscode-insiders/extensions/ms-python.python-2024.12.2-linux-x64/out/client/extension.js:2:1966134)
    at Immediate.<anonymous> (/home/user/.vscode-insiders/extensions/ms-python.python-2024.12.2-linux-x64/out/client/extension.js:2:1962428)
    at processImmediate (node:internal/timers:478:21) {
  code: -4,
  data: undefined
}

VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.19045
Modes:

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

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx   (8 x 2096)|
|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: enabled<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)|17.88GB (10.34GB free)|
|Process Argv|--crash-reporter-id a98ed04d-4fea-4284-8d86-f9c245e4b2cc|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (16)</summary>

Extension|Author (truncated)|Version
---|---|---
project-manager|ale|12.8.0
python-environment-manager|don|1.2.4
theme-monokai-pro-vscode|mon|2.0.5
debugpy|ms-|2024.14.0
python|ms-|2024.22.0
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2024.11.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
remote-wsl|ms-|0.88.5
LiveServer|rit|5.7.9
synthwave-vscode|Rob|0.1.17
ayu|tea|1.0.5
pdf|tom|1.2.2

(5 theme extensions excluded)

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

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
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

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: Receives ERR_OUT_OF_MEMORY when importing medium sized .ogg files
Labels: bug,topic:audio,topic:import,crash

### Tested versions


Godot version 4.2.2 stable (Official build)

### System information

Godot v4.2.2.stable - Windows 10.0.19044 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; 32.0.15.5585) - 11th Gen Intel(R) Core(TM) i5-11400 @ 2.60GHz (12 Threads)

### Issue description

The engine crashes and closes when importing medium-sized (approx, 60 MB) .ogg files.

### Steps to reproduce

Replication steps:
- Create a new project
- Add a .ogg file to the project folder. The .ogg file should be at least 60MB in size.
- Then the following error is received and the engine will crash.

![Image](https://github.com/user-attachments/assets/458bab83-d54f-4dcf-bf2e-b0174d205320)

### Minimal reproduction project (MRP)

N/A
Repository: react
Issue: Bug: `use` function doesn't warn about uncached promise when promise doesn't resolve immediately
Labels: Status: Unconfirmed

When I pass an uncached promise that doesn't resolve immediately to the `use` function, (e. g. `use(new Promise(resolve => setTimeout(resolve, 1000)))`), I _**don't**_ get the "A component was suspended by an uncached promise. Creating promises inside a Client Component or hook is not yet supported, except via a Suspense-compatible library or framework." warning.

Instead, I get into an infinite loop as the Promise keeps getting recreated.

(When I use a promise that gets resolved immediately, like `use(new Promise(resolve => resolve())`, I do get the warning message as expected)

React version: `^19.0.0`

## Steps To Reproduce

1. Go to https://codesandbox.io/p/sandbox/modest-merkle-cr7qcn
2. Open the preview and devtools
3. See there's no warning message about an uncached promise
4. See that the "hi from Promise" gets logged indefinitely 

<!--
  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.
-->

Link to code example:
https://codesandbox.io/p/sandbox/modest-merkle-cr7qcn

## The current behavior
No warning message gets logged 

## The expected behavior
I get the "A component was suspended by an uncached promise. Creating promises inside a Client Component or hook is not yet supported, except via a Suspense-compatible library or framework." warning regardless of how long the promise passed to the `use` function takes to resolve.
Repository: vscode
Issue: Customize shortcut to show the context menu for the highlighted File/Folder in the Files Explorer
Labels: keybindings,file-explorer,under-discussion

<!-- ⚠️⚠️ 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. -->

A Shortcut to show the context menu for the highlighted File/Folder in the Files Explorer would be nice. 

Just like editor.action.showContextMenu, but just for the files explorer (filesExplorer.action.showContextMenu). 
I often switch the focus between the editor and the files explorer using shortcuts and then often need the context menu f.e. for creating a new file/ folder or open in integrated terminal.
The desired behavior is already implemented with the shortcut "shift+f10", but I only found an option to customize the shortcut for the editor and not files explorer.
Repository: svelte
Issue: Improvement for documentation
Labels: documentation

### Describe the problem

- how JS expressions are converted to a string in markup (about the fact that it is simply converted to a string, you can use toString, undefined and null become an empty string, what about the attributes)
- when a prop is set to the default value (if the value is undefined or not specified, about $bindable, does the expression run every time)


### Describe the proposed solution

I would like to see these important details written about in the documentation.

### Importance

nice to have
Repository: vscode
Issue: Open Workspace in current window using `code .` from the Terminal
Labels: under-discussion,workbench-cli

<!-- ⚠️⚠️ 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. -->

My current workflow is as follows on remote hosts (but also applies when coding on my machine):

1. Open VSCode and connect to the remote
2. Open a terminal and move to the project folder with no current folder opened
3. Enter `code .` to open the folder from the terminal in VSCode
4. Close the old instance of VSCode, since `code .` opens the folder in a new window.

My suggestion would be that you can open a folder in the same window with `code .` in the VSCode Terminal if there isn't currently a folder opened.
Repository: rust
Issue: compiletest: `./x test <filter>` is a substring match
Labels: E-hard,T-bootstrap,C-bug,A-compiletest,E-needs-investigation

This is very non-intuitive...

I tried on native `x86_64-pc-windows-msvc`:

```
./x test tests/run-make/exp/ --stage 1
```

This showed me 8 tests were ignored (incl. a local `tests/run-make/exp/` test I added for testing) even though I would've expected an *exact* match for only the local test I added:

```
[23:37] Joe:rust (return-adjustment-target) | ls -d tests/run-make/*exp*
tests/run-make/export-executable-symbols/             tests/run-make/share-generics-export-again/
tests/run-make/extern-fn-explicit-align/              tests/run-make/wasm-export-all-symbols/
tests/run-make/mingw-export-call-convention/          tests/run-make/wasm-symbols-not-exported/
tests/run-make/rustdoc-scrape-examples-invalid-expr/
```

I almost never want this substring match behavior, at least not unless I explicitly write some kind of `--test-name="exp"`, for example.

I suspect this is some behavior related to the test name constructed by compiletest, which is fed to libtest which probably handles the test filtering... Ah, it might be the test name constructed from the test path...
Repository: godot
Issue: Default project and editor template for Node will not override built-in default
Labels: bug,topic:editor

### Tested versions

-Reproducible in 4.3.stable.official on MacOS 

### System information

MacOS Sonoma 14.7.1

### Issue description

Using the `# meta-default: true` header will work for any class except Node. For instance, it works for CharacterBody2D as described in the documentation, but if the file is put in a Node folder under `res://script_templates`, the editor does not pick up the header and defaults to the built-in Node template. 

Also tested in the editor templates folder. The editor picks up that the templates exist in both locations, but seems to ignore the header for Node only.

### Steps to reproduce

1. Create `script_templates` folder in res://
2. Create `Node` folder in `script_templates`
3. Create a template file
4. Add `# meta-default: true` to header
5. Attempt to create a new script with the Node base class


### Minimal reproduction project (MRP)

N/A
Repository: electron
Issue: Per-OS methods such as BrowserWindow.setHiddenInMissionControl do not match TypeScript signatures
Labels: bug :beetle:,platform/all,status/confirmed,33-x-y,34-x-y

### 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

33.2.1

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

Windows, macOS, Other Linux

### Operating System Version

n/a

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Methods like `setHiddenInMissionControl` appear to be defined according to the TypeScript definitions, but are not defined on certain platforms. Rather than leaving these undefined, all APIs should be defined on all platforms and simply no-op on ones that don't make any sense.

### Actual Behavior

Calling `setHiddenInMissionControl` on Windows results in method not defined, which is a Surprising Behavior

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: transformers
Issue: Vision models don't work for non-square object
Labels: Good First Issue,Vision

### System Info

- `transformers` version: 4.47.0
- Platform: Linux-6.8.0-50-generic-x86_64-with-glibc2.39
- Python version: 3.9.20
- Huggingface_hub version: 0.26.5
- Safetensors version: 0.4.5
- Accelerate version: 1.2.0
- Accelerate config: 	not found
- PyTorch version (GPU?): 2.5.1 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using distributed or parallel set-up in script?: <fill in>
- Using GPU in script?: <fill in>
- GPU type: NVIDIA GeForce RTX 4060 Ti


### Who can help?

 @amyeroberts, @qubvel

### Information

- [X] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [X] My own task or dataset (give details below)

### Reproduction

```
from transformers import ViTMAEConfig,ViTMAEForPreTraining
config = ViTMAEConfig(image_size=tuple((16,1024)),patch_size=tuple((4,256)))
model = ViTMAEForPreTraining(config)
```

```
TypeError                                 Traceback (most recent call last)
Cell In[40], line 3
      1 from transformers import ViTMAEConfig,ViTMAEForPreTraining
      2 config = ViTMAEConfig(image_size=tuple((16,1024)),patch_size=tuple((4,256)))
----> 3 model = ViTMAEForPreTraining(config)

File ~/miniconda3/lib/python3.9/site-packages/transformers/models/vit_mae/modeling_vit_mae.py:994, in ViTMAEForPreTraining.__init__(self, config)
    991 self.config = config
    993 self.vit = ViTMAEModel(config)
--> 994 self.decoder = ViTMAEDecoder(config, num_patches=self.vit.embeddings.num_patches)
    996 # Initialize weights and apply final processing
    997 self.post_init()

File ~/miniconda3/lib/python3.9/site-packages/transformers/models/vit_mae/modeling_vit_mae.py:852, in ViTMAEDecoder.__init__(self, config, num_patches)
    846 self.decoder_layers = nn.ModuleList(
    847     [ViTMAELayer(decoder_config) for _ in range(config.decoder_num_hidden_layers)]
    848 )
    850 self.decoder_norm = nn.LayerNorm(config.decoder_hidden_size, eps=config.layer_norm_eps)
    851 self.decoder_pred = nn.Linear(
--> 852     config.decoder_hidden_size, config.patch_size**2 * config.num_channels, bias=True
    853 )  # encoder to decoder
    854 self.gradient_checkpointing = False
    855 self.config = config

TypeError: unsupported operand type(s) for ** or pow(): 'tuple' and 'int'

```

### Expected behavior

I want ViTMAEForPreTraining to analyze my biological data, which should get a normal output even though it's not a real image. I've noticed that your model doesn't take into account some irregular inputs, such as non-square images, resulting in errors. So, hopefully the code can be improved to accommodate a wider range of inputs.
Repository: material-ui
Issue: [TextField] add show password feature
Labels: new feature,docs,waiting for 👍,component: text field

### Summary

add show password feature when typing a password in sign in form and signup form (it s not apper in chrome)

### Examples

_No response_

### Motivation

_No response_

**Search keywords**: show password
Repository: neovim
Issue: Figure out why escape sequences aren't working in tty-test on Windows
Labels: platform:windows,test,terminal

Ref: https://github.com/neovim/neovim/pull/31562#issuecomment-2543942863

Addressing this issue should cause all tests that have `skip(is_os('windows'), '#31587')` to pass (with that line removed) on Windows.

```console
$ git grep '#31587'
```
Repository: material-ui
Issue: [Dialog] Focus not moving into dialog content when talkback is on
Labels: accessibility,component: dialog,package: material-ui,ready to take

### Steps to reproduce

Steps:
1. Go to [ https://stackblitz.com/edit/vitejs-vite-uyj92zhd?file=src%2FApp.tsx,package.json&terminal=dev](url) or  [https://mui.com/material-ui/react-dialog/](url)
2. Turn on talkback
3. Try to access dialog content using swipe.


### Current behavior

When talkback is on, the focus does not move inside the content of the dialog. This may be due to the tabIndex=-1 applied to the TransitionComponent. I overrode the TransitionComponent, but after that, the focus is no longer trapped inside the dialog; it moves out, and the focus order becomes incorrect. Please refer to the screen recording for more details.

### Expected behavior

When talkback is on, the focus should move into the dialog content automatically when the dialog opens.
The focus should remain trapped within the dialog while it is open, preventing it from moving to elements outside the dialog.
The focus order inside the dialog should follow a logical and meaningful sequence, ensuring accessibility and usability for screen reader users.

### Context

Access the content of the dialog when talkback is on.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: Android 14
  Browsers:
    Chrome: Not Found
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @emotion/react: ^11.10.5 => 11.11.1
    @emotion/styled: ^11.10.5 => 11.11.0
    @mui/base:  5.0.0-alpha.113
    @mui/core-downloads-tracker:  5.15.4
    @mui/icons-material: ^5.11.0 => 5.14.11
    @mui/material: ^5.11.4 => 5.11.4
    @mui/private-theming:  5.15.4
    @mui/styled-engine:  5.14.11
    @mui/styles: ^5.11.4 => 5.15.4
    @mui/system: ^5.11.4 => 5.14.11
    @mui/types:  7.2.13
    @mui/utils:  5.15.4
    @types/react: ^18.0.26 => 18.2.24
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: ^4.9.4 => 4.9.5
```
</details>


**Search keywords**: A11y
Repository: ollama
Issue: Error: llama runner process has terminated: error:/opt/rocm/lib/libhipblas.so.2: undefined symbol: rocblas_sgbmv_64
Labels: bug,linux,amd,needs more info

### What is the issue?

When I start llama3.2 with `ollama run llama3.2` this error spawns:
`Error: llama runner process has terminated: error:/opt/rocm/lib/libhipblas.so.2: undefined symbol: rocblas_sgbmv_64`

I am on Cachy OS with ollama and ollama-rocm installed from extra repo and a AMD RX6800 is the GPU

### OS

Linux

### GPU

AMD

### CPU

AMD

### Ollama version

0.5.2