sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
Labels: Runtime

### Link to the code that reproduces this issue

https://github.com/kuanjiahong/deprecation-warning-app

### To Reproduce

**Development mode**
1. Start the application in development `npm run dev`
2. Go to `http://localhost:3000`
3. Click the button to rewrite the url
4. Check the console for the deprecation warning

**Deployment - Node.js Server**
1. Build the application `npm run build`
2. Run the application `npm run start`
3. Go to `http://localhost:3000`
4. Click the button to rewrite the url
5. Check the console for the deprecation warning

**Deployment - Docker image**
1. Build container `docker build -t nextjs-docker .`
2. Run container: `docker run -p 3000:3000 nextjs-docker`
3. Go to `http://localhost:3000`
4. Click the button to rewrite the url
5. Check the console for the deprecation warning


### Current vs. Expected behavior

Current behaviour:

A deprecation warning is shown:

```bash
[DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
```
When used node --trace-deprecation to show where the warning was created:
```
(node:1) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
    at ProxyServer.<anonymous> (/app/node_modules/next/dist/compiled/http-proxy/index.js:13:2607)
    at proxyRequest (/app/node_modules/next/dist/server/lib/router-utils/proxy-request.js:108:15)
    at handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:332:61)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async requestHandlerImpl (/app/node_modules/next/dist/server/lib/router-server.js:441:13)
    at async Server.requestListener (/app/node_modules/next/dist/server/lib/start-server.js:155:13)
```

Expected behaviour:
No deprecation warning.



### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Enterprise
  Available memory (MB): 32562
  Available CPU cores: 8
Binaries:
  Node: 22.12.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.1.1-canary.23 // Latest available version is detected (15.1.1-canary.23).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

Runtime

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Other (Deployed)

### Additional context

I found these related issue: #72220 #71374

I found that this issue start to occur when using Node version >= 22.

This issue does not occur when using Node v20.
Repository: deno
Issue: `node:crypto` implementation doesn't support ECDSA secp256k1
Labels: bug,node compat,crypto

Version: Deno 2.1.4
Related: https://github.com/denoland/deno/issues/24989#issuecomment-2567191851

Deno, with its `node:crypto` implementation, doesn't support doing ECDSA with secp256k1, only ECDH is supported (which is a different thing).

This code works on Node.js but throws on Deno:

```ts
import * as crypt from 'node:crypto';
crypt.generateKeyPair('ec', { namedCurve: 'secp256k1' }, console.log);
```

Used in [`@atcute/crypto`](https://github.com/mary-ext/atcute/tree/trunk/packages/utilities/crypto) to [validate most signatures in AT Protocol](https://atproto.com/specs/cryptography), as secp256k1 is more readily available in KMS/HSMs.

Currently, `@atcute/crypto` mitigates this lack of support by adding an [imports condition for Deno](https://github.com/mary-ext/atcute/blob/7fc523522bdd13c6562b06cf47ad87a715414743/packages/utilities/crypto/package.json#L28-L35), it would be nice if Deno actually supported this to avoid using the JS-based [`@noble/secp256k1`](https://github.com/paulmillr/noble-secp256k1) library for signing and verification.
Repository: ui
Issue: [bug]: Chart Legend Vertical
Labels: bug

### Describe the bug

Layout prop is being ignored in the ChartLegend component. 

![image](https://github.com/user-attachments/assets/a966c767-49b3-447a-bcc0-ad1bd37818df)


### Affected component/components

Chart

### How to reproduce

 <ChartLegend content={<ChartLegendContent nameKey="category" />}  layout='vertical' verticalAlign='middle' align="right"/>

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Firefox
Windows
Next 15+React19
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: react
Issue: Bug: Wrong address for empty string message
Labels: Status: Unconfirmed

### Steps to reproduce

I don't know where the problem could be. Therefore I can't create an MRE.
This is a video I captured:

https://github.com/user-attachments/assets/1c21e144-2ccc-4fce-84af-2af15b8fe0b8

The point is, the message complaints that:

> An empty string ("") was passed to the src attribute. This may cause the browser to download the whole page again over the network. To fix this, either do not render the element at all or pass null to src instead of an empty string.

When I open that message to see the stack, it guides me to a component of mine called `ToggleView` and the line specified contains this code:

    setViewStyle("cards")

And the `ToggleView.jsx` does not contain `src` attribute at all in it. Of course, I have `src` in many other places. But how can I know which one is causing the problem? The address is wrong.

### Current behavior

React provides misleading addresses that do not help at all in finding the problem, and litters the console for long time until we find the problem accidentally or through heuristics (trial & error).

### Expected behavior

React should provide accurate addresses.

### Your environment

```
  System:
    OS: Linux 6.8 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
  Binaries:
    Node: 22.12.0 - /usr/local/bin/node
    npm: 11.0.0 - /usr/local/bin/npm
  Browsers:
    Firefox: 133.0.3 (64-bit)
  npmPackages:
    react: ^19.0.0 => 19.0.0 
    react-dom: ^19.0.0 => 19.0.0 

```
Repository: godot
Issue: AnimatedSprite2D can call `queue_free()` in the editor in response to a signal without a tool script
Labels: bug,topic:editor

### Tested versions

- Reproducable in 4.4.dev7, 4.3.stable, 4.0.4.stable, 3.6.stable

### System information

Fedora Linux 41

### Issue description

An AnimatedSprite2D node with an `animation_finished` signal linked to `queue_free()` on any node will actually shoot that signal off in the editor and delete the node from the scene tree in the editor, even without a tool script (or even any script) involved.  If this method is specified on the root of the scene, it will crash the entire editor.

If you instead attach to a script and link to a receiver method in that script, the removal does not happen.  It only happens if you link directly to `queue_free()`, as far as I've been able to reproduce.

### Steps to reproduce

* Open a fresh project
* Create a Node2D
* Create a child AnimatedSprite2D and select it
* Go to the Node panel, and double-click on `animation_finished`
* Click "AnimatedSprite2D (Connecting From)"
* Change the "Receiver Method" to `queue_free`
* Click Connect
* Go to the Inspector panel
* Create a new SpriteFrames
* Add an empty frame to the `default` animation (there must be at least one frame, but it doesn't have to be empty)
* Disable looping on the `default` animation
* Press play
* Watch the sprite disappear from the tree when the animation finishes

### Minimal reproduction project (MRP)

This reproduction project has a DoesNotRemoveSelf node and a RemovesSelf node showing the behaviors.  DoesNotRemoveSelf's signal calls `queue_free()` through an attached script, which does not cause any issues.  RemovesSelf's signal calls `queue_free()` directly.  Select RemovesSelf and click Play to see it free itself in the editor.

[queue_free-bug.zip](https://github.com/user-attachments/files/18288292/queue_free-bug.zip)
Repository: PowerToys
Issue: Ability to fix long paths (Alternative to Long Path Tool)
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

I'm expecting a feature that would allow users to more-easily fix issues that arise with having files (and folders?) with long paths.

- Renaming the file
- Renaming the file path itself (maybe even the specified (nested) folder(s)
- Moving the file elsewhere

### Scenario when this would be used?

This would be very useful for when explorer _breaks_ and you can't manually rename a file. Currently, I have a file with a long file name and I noticed now that I can't rename the file to be shorter because anytime I try to rename it, it reverts right back to the original file path. Inspecting the file properties shows that the location prefix is `\\?\G:` and looking into it seems to be because of a broken long file path.

### Supporting information

I tried doing `ren "\\?\G:\folder\folder 2\long-file-name" "new-file-name"` and I was able to finally rename the file. Would be nice if I could do this with PowerTools instead. Perhaps the tool can automatically find broken file paths inside a specified directory and attempt to rename the files for you with similar options to the file rename tool.
Repository: flutter
Issue: Request for documentation on configuration options, “backfill”
Labels: team-infra

### Type of Request

infra task

### Infrastructure Environment

Regarding ci.yaml


https://github.com/flutter/flutter/blob/d9b7e5664604a55a3e900b0c619ee319065abb0e/.ci.yaml#L591

I think this needs more context to clarify impact and effects of this setting. The entire configuration file is quite massive as are the dependencies, testing frameworks, code base, etc. I'll attempt to try to put some thought into it because this project is pretty major, but any explanations would be appreciated, thanks!

### Steps to reproduce

Step 1:
Step 2:
..
Step n:


### Expected results

I would like to request more information or comments to understand configuration.
Repository: opencv
Issue: CUDA function is combined with opencv for onnx inference
Labels: category: documentation

### Describe the doc issue

I encountered problems when I tried to combine cuda programming with ONNX inference. After image processing with CUDA function, I obtained CUDA data of uchar*. Instead of GPU-->CPU-->GPU operations, I wanted to use opencv to directly reason my data, but I had no idea. Is there a simple demo?
this is my code:
 {
 Mat src = imread(ImagePath);
 int row = src.rows;
 int col = src.cols;
 uchar* src_cuda = ToGpu(src,col,row);
 Mat show_dst(640,640,CV_8UC3);
 uchar* dst_cuda = Resize(src_cuda,row,col,640,640);   // GPU Resze 
 }
 I want to read yolov8n.onnx for inference

### Fix suggestion

_No response_
Repository: pytorch
Issue: torch-nightly doesn't support tesla v100
Labels: needs reproduction,module: binaries,module: cuda,triaged

### 🐛 Describe the bug

env:TeslaV100,driver 560.35.03 cuda 12.4
use pip3 install --pre torch torchvision torchaudio --index-url https://download.pytorch.org/whl/nightly/cu124
python:
import torch
print(torch.randn(5, 5).to(device)+torch.randn(5, 5).to(device))

but cuda12.4 supports v100,i can't find which torch version supports v100+cuda12.4 or other gpu
<img width="569" alt="1·33" src="https://github.com/user-attachments/assets/b7b0c42d-65ee-412a-aabf-cc1f2fc502c2" />

### Versions

2.6.0

cc @seemethere @malfet @osalpekar @atalman @ptrblck @msaroufim @eqy @ezyang @gchanan @zou3519 @kadeng
Repository: svelte
Issue: Using clsx incorporating class declaration with tailwind-merge causes error
Labels: types / typescript

### Describe the bug

Combining the latest clsx supporting `HTMLAttributes` with tailwind-merge creates type incompatibility. 

**HTMLAttributes declared by svelte**
```
export interface HTMLAttributes<T extends EventTarget> extends AriaAttributes, DOMAttributes<T> {
	class?: string | import('clsx').ClassArray | import('clsx').ClassDictionary | undefined | null;
	...
}
```

**Expected type from tailwind-merge**

```export type ClassNameValue = ClassNameArray | string | 0 | 0n | false | undefined | null```


### Error Logs

```shell
Argument of type 'string | ClassArray | ClassDictionary | null | undefined' is not assignable to parameter of type 'ClassNameValue'.
  Type 'ClassArray' is not assignable to type 'ClassNameValue'.
    Type 'ClassValue[]' is not assignable to type 'ClassNameArray'.
      Type 'ClassValue' is not assignable to type 'ClassNameValue'.
        Type 'number' is not assignable to type 'ClassNameValue'. (ts)
          : 'size-12',
    cssClass,
  )}
```


### Reproduction

```
<script lang="ts">
  import { twMerge } from 'tailwind-merge'
  import type { HTMLButtonAttributes } from 'svelte/elements'
  import type { Snippet } from 'svelte'

  interface Props extends HTMLButtonAttributes {
    children?: Snippet
  }

  let { class: cssClass, children, ...rest }: Props = $props()
</script>

<button {...rest} class={twMerge('rounded', cssClass)}>
  {@render children?.()}
</button>

```

### System Info

```shell
npmPackages:
    svelte: ^5.16.0
    tailwind-merge: ^2.6.0
```


### Severity

blocking an upgrade

### Hacky workaround

One possibility is to redefine the `class` property as a common type (eg a simple `string`).

```
  interface Props extends HTMLButtonAttributes {
    children?: Snippet
    class?: string
  }
```
Repository: rust
Issue: Placing an attribute on a generic argument confuses the parser
Labels: A-diagnostics,A-parser,T-compiler

### Code

```Rust
struct Foo<T>(T);

fn main() {
    let foo: Foo<#[cfg(not(wrong))] String> = todo!();
}
```

### Current output

```Shell
error: invalid const generic expression
 --> /playground/src/main.rs:8:37
  |
8 |     let foo: Foo<#[cfg(not(wrong))] String> = todo!();
  |                                     ^^^^^^
  |
help: expressions must be enclosed in braces to be used as const generic arguments
  |
8 |     let foo: Foo<#[cfg(not(wrong))] { String }> = todo!();
```

### Desired output

```Shell
error: attributes are not allowed on generic arguments 
--> /playground/src/main.rs:8:37
  |
8 |     let foo: Foo<#[cfg(not(wrong))] String> = todo!();
  |                  ^^^^^^^^^^^^^^^^^^
  |                  attribute not allowed in this context
help: remove the attribute to allow the code to compile:
8 |     let foo: Foo<String> = todo!();
```

### Rationale and extra context

Playground link: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=eaf1097ff4efa3734d3a5e3faa3cb10f

### Other cases

```Rust
If one applies the suggestion made in the current error, you get the "same" error message suggesting to add another level of brackets.
```

### Rust Version

```Shell
Build using the Nightly version: 1.85.0-nightly

(2025-01-01 45d11e51bb66c2deb63a)
```

### Anything else?

_No response_
Repository: vscode
Issue: {Linked:Bug9528434} The interactive control in the @workspace tooltip is not accessible using keyboard (Tab or Arrow) keys: A11y_VS Code_Copilot Chat_Keyboard
Labels: bug,accessibility,chat

### GitHub Tags:
#A11yMAS; #A11yTCS; #A11ySev2; #DesktopApp; #BM-VisualStudioCodeClient-Win32-Jan2024; #Visual Studio Code Client; #Win32; #Win11; #WCAG2.1.1; #FTP; #Keyboard; #ED:Bug9528434

### Environment and OS details:
Version: 1.97.0-insider (user setup)
Windows 11 Enterprise Version 24H2
OS Build: 26100.2605

### Repro Steps:

1. Open Visual Studio Code Insiders editor.
2. Tab till Copilot chat Window and press enter.
3. Navigate to Chat(Ctrl+Alt+I) in Left Nav and activate it.
4. Navigate to Ask copilot text field type /Help Command and press enter.
5. Navigate to @workspace Bulleted List.
6. Observed that the interactive control in the @workspace tooltip is not accessible using keyboard.

### Actual Result:
 The interactive control in the @workspace tooltip is not accessible using keyboard (Tab or Arrow) keys.

### Expected Result:
 The interactive control in the @workspace tooltip should be accessible with keyboard (Tab or Arrow) keys.

### User Impact:
Keyboard users will face difficulty if the interactive control in the @workspace tooltip is not accessible using keyboard.

### Attachment:
![Image](https://github.com/user-attachments/assets/e6f99d83-71b0-4cc0-b965-962183c2c337)
Repository: vscode
Issue: {Linked:Bug9577427} When a list item is selected in Pick Model, the list box closes and reopens without any user interaction:  A11y_VS Code_Copilot Chat_Pick model_Usability
Labels: bug,accessibility,windows

### GitHub Tags:
#A11yUsable; #A11yTCS; #DesktopApp; #BM-VisualStudioCodeClient-Win32-Jan2024; #Visual Studio Code Client; #Win32; #Win11; #FTP; #ED:Bug9577427

### Environment and OS details:
Version: 1.97.0-insider (user setup)
Windows 11 Enterprise Version 24H2
OS Build: 26100.2605

### Repro Steps:

1. Open Visual Studio Code Insiders editor.
2. Tab till Copilot chat Window and press enter.
3. Navigate to Chat(Ctrl+Alt+I) in Left Nav and and activate it.
4. Navigate to Pick Model and press enter.
5. Select the any List item.
6. Observe that when a list item is selected in Pick Model, the list box closes and reopens without any user interaction.

### Actual Result:
When a list item is selected in Pick Model, the list box closes and reopens without any user interaction.

### Expected Result:
Upon selecting an item in the Pick Model list, the list box should close and remain closed until further user interaction occurs.

### User Impact:
Users will face difficulty if when a list item is selected in Pick Model, the list box closes and reopens without any user interaction.

### Attachment:
![Image](https://github.com/user-attachments/assets/f2ab4b23-0c8a-4944-b947-a896560d14a5)
Repository: transformers
Issue: Possible bug when using cosine lr scheduler with gradient accumulation
Labels: bug

### System Info

transforme 4.47
deepspeed

### Who can help?

@muellerzr @SunMarc

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

[UPDATE} Turns out the issue is that I need to explicitly set "gradient_accumulation_steps": "auto" in the deepspeed config. Initially in my config I set most things to "auto" but I did not set gradient_accumulation_steps explictly, assuming it will be treated the same way as auto, otherwise will report error. FYI, would appreciate any good resource on what other parameters should be set as "auto" in deepspeed config.... I have not found a good reference. Thanks!


### Reproduction
I am running a trianing script with deepspeed as 
```
deepspeed training.py
```

When using official trainer with gradient_accumulation_steps = 2 and lr_scheduler_type = cosine, I got following learning rate curve (training epoch = 1):

![image](https://github.com/user-attachments/assets/f86f250a-9567-49a9-96c1-272f10247771)

So seems the scheduler stepped more than one cycle. When digging through the source code, seems the issue is that in:
```
def _get_cosine_schedule_with_warmup_lr_lambda(
    current_step: int, *, num_warmup_steps: int, num_training_steps: int, num_cycles: float, min_lr_rate: float = 0.0
):
    if current_step < num_warmup_steps:
        return float(current_step) / float(max(1, num_warmup_steps))
    progress = float(current_step - num_warmup_steps) / float(max(1, num_training_steps - num_warmup_steps))
    factor = 0.5 * (1.0 + math.cos(math.pi * float(num_cycles) * 2.0 * progress))
    factor = factor * (1 - min_lr_rate) + min_lr_rate
    return max(0, factor)
```
num_training_steps is 
```
num_update_steps_per_epoch = len_dataloader // args.gradient_accumulation_steps
max_steps = math.ceil(args.num_train_epochs * num_update_steps_per_epoch)
self.create_optimizer_and_scheduler(num_training_steps=max_steps)
self.create_scheduler(num_training_steps=num_training_steps, optimizer=optimizer)
```


Therefore current_step is the global step without taking into account for gradient_accumulation, while num_training_steps did account for gradient_accumulation. As an example, if we train 1000 cases on one GPU for 1 epoch with a accumulation step of 2, the num_training_steps is 500, but current_step can go up to 1000.

Wondering if this is expected behavior or something that should be fixed?

Many thanks.


### Expected behavior

![image](https://github.com/user-attachments/assets/0199dec9-cebf-4779-91e2-800bdfaa6327)
Repository: rust
Issue: slice::contains is not general in the key like HashMap::get
Labels: T-libs,C-discussion

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
fn main() {
    let words = ["hello", "world"].map(|s| s.to_string());

    // this works fine
    let hm: std::collections::HashMap<String, usize> = words
        .iter()
        .cloned()
        .zip(words.iter().map(|w| w.len()))
        .collect();
    assert_eq!(hm.get("hello"), Some(&5));

    // this does NOT work
    assert!(words.contains("hello"));
    // but has this simple workaround
    assert!(words.iter().any(|e| e == "hello"));
}

```

I expected to see this happen: works

Instead, this happened: slice::contains does not accept a `&str` instead of a `&String`, like HashMap::get does. I tried searching for older issues to see if there may be a good reason for this, but I did not find anything.