sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Possible memory leak using Deno.Command
Labels: perf,windows,needs investigation

I have this function to extract the information on the battery status of Windows using Power Shell, but I could notice that while periodically executing the function the ram memory usage increased, so it is possible that I am doing something wrong and causing this or it may be a bug in deno.

```typescript
export async function getBatteryInfo(): Promise<BatteryInfo> {
  const command = `
    & {
      $battery = Get-WmiObject Win32_Battery
      if ($battery) {
        $output = @{
          isCharging = $battery.BatteryStatus -eq 2
          chargeLevel = $battery.EstimatedChargeRemaining
          timeRemaining = $battery.EstimatedRunTime
        }
        $output | ConvertTo-Json
      } else {
        Write-Output "null"
      }
    }`;

  const abort = new AbortController();

  const cmd = new Deno.Command("powershell", {
    args: [
      "-Command",
      command,
    ],
    signal: abort.signal,
  });

  const { code, stdout, stderr } = await cmd.output();

  if (code) {
    const errorString = decoder.decode(stderr);
    throw new Error(`Failed to execute PowerShell command: ${errorString}`);
  }

  const output = decoder.decode(stdout);
  const stats: BatteryInfo = parse(output);

  abort.abort();

  return stats;
}
```

Version: Deno 1.45.2
OS: windows 11 23H2
Repository: deno
Issue: Include the label attribute of a WebGPU object in error messages 
Labels: feat,web,upstream,webgpu

Hi! I think it would be helpful if the label attribute of a WebGPU object was included in any validation error messages. 

For example, if I create the following texture:
```js
const texture = device.createTexture({
    label: "Texture 1",
    dimension: "2d",
    sampleCount: 1,
    format: "rgba8unorm-srgb",
    size: { 
        width: 36,
        height: 145,
        depthOrArrayLayers: 34
    },
    mipLevelCount: 10,
    usage: GPUTextureUsage.RENDER_ATTACHMENT.
    viewFormat: ["rgba8unorm"]
});
```

I'll get the error message: `Device::create_texture error: Texture descriptor mip level count 10 is invalid, maximum allowed is 8.`

I think it would be helpful if this error message could include the label e.g. `Texture 1` in this case, to make it easier to debug. Thanks!
Repository: material-ui
Issue: [material-ui][Select] Scroll inside select input
Labels: new feature,design: material,component: select,package: material-ui

### Summary

<img width="395" alt="image" src="https://github.com/user-attachments/assets/b2484733-f51e-441b-8122-73b92b595ea6">

i would like to scroll inside the input my selected values
for now i see only ... but i cant see more because i can't select the text like an textfield and scroll it horizontally with my mouse

this could be a feature, especially if select is disabled



### Examples

for example if i have long text selected, or more than one option selected, i want scroll them and don't see just "..."

### Motivation

UX friendly, like a user i would like to see my selections, without open the dropdown

**Search keywords**: select input
Repository: go
Issue: doc: write release notes for Go 1.24
Labels: Documentation,NeedsFix,release-blocker

This is the tracking issue for writing the Go 1.24 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/go1.24.

When the Go 1.24 Release Notes are complete, this should be closed, and a similar issue should be made for the next release. The previous issue was #65614.

A partial list of changes that were known on 2024-11-26 to need to be added the release notes:
- #26232
- #46477
- #48429
- #50603
- #56378
- #60529
- #64127
- #65199
- #66387
- #69290
- #69393
- #68678
- #70586
Repository: TypeScript
Issue: Types with optional props get implicit index signatures that cannot be made explicit
Labels: Suggestion,In Discussion

### 🔎 Search Terms

implicit index signatures, explicit index signatures, optional partial undefined,

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about index signatures and undefined


### ⏯ Playground Link

[Playground link](https://www.typescriptlang.org/play/?#code/C4TwDgpgBA8gRgKwJIFswBsCWBjTwoC8UA3gFBQVQCGA-AFxQDOwATpgHYDmUAPlAK7sAJhABmHCEIA05SnAbM2XUgF8A3KVCQoSIQA9CJKAG0A1gtYdOAXQtLuK0iOzoqLaNgD27ZlE8N4ZDQsXGANLx98TAZdAyJPNSgAeiTqdHRPAHdJKDgIbCp+RmgAQSgACypGKExgnDwa4QgDRkxOdipgfndSTXBoQIBRPQx6-CIySmp6JksuXgEm8XZJKWTUiBYWTxYAQih2T3wqdKzJWQoUgD8oAB4AWnuoAAVtyBZQKAByKi+-USgWmgX0UVgWghEy0kf0w1UOx0YrXaVDg6GgwE831BXBhTQMQKxc04XwAdBdcnYrDIpmZKVxbLN7KpekA)

### 💻 Code

```ts
// @strict: true
// @exactOptionalPropertyTypes: false
// @noUncheckedIndexedAccess: false

type ObjImplicit = {
    a?: string | undefined,
    b: string
};
type Idx = { [k: string]: string }
declare const o: ObjImplicit;
const i: Idx = o; // allowed because A has implicit index signature

type ObjExplicit = {
    a?: string | undefined, // error! not allowed
    //~ <-- Property 'a' of type 'string | undefined' is not assignable to 'string' index type 'string'.
    b: string,
    [k: string]: string
}
```


### 🙁 Actual behavior

`{ a?: string | undefined }` can implicitly have the index signature `{[k: string]: string}` but cannot explicitly have such an index signature


### 🙂 Expected behavior

I think I expected the implicit index signature to fail? 

### Additional information about the issue

Without `--exactOptionalPropertyTypes`, `{a?: string}` and `{a?: string | undefined}` are the same type. I figured that would mean both implicitly and explicitly adding index signatures would either require or not require `undefined`. 

We also have the situation where `Partial<{[k: string]: string}>` becomes `{[k: string]: string | undefined}` instead of `{[k: string]: string}`, which makes me lean toward "require `undefined`", for consistency. Currently the discrepancy leads to questions like [this one](https://stackoverflow.com/q/78775667/2887218).

Anyway, I expect this to not be a bug, but intended behavior that flew under my radar and which I cannot see explicitly documented anywhere.  Mostly I just want to understand this behavior so I can explain it when people ask questions like the one linked above.
Repository: tauri
Issue: [bug] [v2] Identifier without a dot (.) causes a crash on Linux
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

An app with identifier in the `src-tauri/tauri.conf.json` without a single `.` / dot character causes a program crash in Linux.
Working identifier:
`"identifier": "WhatEver.Identifier",`
failing identifier:
`"identifier": "WhatEverIdentifier",`
The program is just a standard template created with `npm create tauri-app@latest -- --beta` command.

### Reproduction

1. Use Ubuntu Linux 22.04 (will reproduce with others also)
2. Create a program with `npm create tauri-app@latest -- --beta` -command with the following selections:
```
✔ Project name · tauri-gtk
✔ Choose which language to use for your frontend · TypeScript / JavaScript - (pnpm, yarn, npm, bun)
✔ Choose your package manager · npm
✔ Choose your UI template · React - (https://react.dev/)
✔ Choose your UI flavor · TypeScript
✔ Would you like to setup the project for mobile as well? · yes
```
3. Change the identifier in the `src-tauri/tauri.conf.json` to a string without dots (`.` characters).
4. Install npm packages with `npm i`
5. Run the program: `npm run tauri dev`

### Expected behavior

The program should run and display a window with some content.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Ubuntu 22.04 X64
    ✔ webkit2gtk-4.1: 2.44.2
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 22.5.1
    - npm: 10.8.2

[-] Packages
    - tauri [RUST]: 2.0.0-beta.24
    - tauri-build [RUST]: 2.0.0-beta.19
    - wry [RUST]: 0.41.0
    - tao [RUST]: 0.28.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.15
    - @tauri-apps/cli [NPM]: 2.0.0-beta.22

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

```text
(process:60700): Gtk-CRITICAL **: 19:36:28.907: gtk_application_new: assertion 'application_id == NULL || g_application_id_is_valid (application_id)' failed
thread 'main' panicked at /home/billythecat/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gtk-0.18.1/src/auto/application.rs:13:1:
assertion failed: !ptr.is_null()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```


### Additional context

I have tested that the program works in such case in both Windows and macOS correctly, also this works with Tauri v1 including Linux.
Repository: puppeteer
Issue: [Bug]: browser.pages(); doesnt work when there are inactive since the last start pages
Labels: bug,upstream,confirmed,P3

### Minimal, reproducible example

```TypeScript
// Open multiple pages when browser start, then restart script so when it will open again some pages wont be loaded if u wont click on their tab
const puppeteer = require('puppeteer');
(async () => {
    const browser = await puppeteer.launch({
        headless: false, // Show the browser window
        userDataDir: path.join(__dirname, 'profile'), // Path to the user profile directory
    });
    console.log(await browser.pages());
    console.log('Pages received');
})();
```


### Background

get browser pages

### Expectation

receive pages array

### Reality

if there are inactive (not loaded when browser started) pages it fails

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.1.0

### Node version

21.5.0

### Package manager

npm

### Package manager version

10.2.4

### Operating system

Windows
Repository: ui
Issue: [Docs]: While installing shadcn in Next.js project, we need to mention that developers need to`cd` into their project folder.
Labels: bug

### Describe the bug

In [this part](https://github.com/shadcn-ui/ui/blob/main/apps/www/content/docs/installation/next.mdx#run-the-cli), it will be helpful to add a line mentioning that one needs to cd into the project directory before running this command.

### Affected component/components

Docs

### How to reproduce

1. Go to the [docs](https://github.com/shadcn-ui/ui/blob/main/apps/www/content/docs/installation/next.mdx#run-the-cli).
2. Find missing information

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
All browsers
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: Flutter beta 3.24.0-0.1.pre - `android_profile_arm64` timed out generating gn files
Labels: team-release

From https://github.com/flutter/engine/pull/54003/checks?check_run_id=27656678082
Part of https://github.com/flutter/flutter/issues/152118

`Linux mac_android_aot_engine` ([build](https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20mac_android_aot_engine)) -> ci/android_profile_arm64 ([build](https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20Engine%20Drone/1002908/infra)) -> timed out running gn ([logs](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8741995510014572577/+/u/gn_--target-dir_ci_android_profile_arm64_--runtime-mode_profile_--android_--android-cpu_arm64_--rbe_--no-goma_--xcode-symlinks_--rbe-server-address_unix:___Volumes_Work_s_w_ir_x_w_recipe_cleanup_rbe5gwj4o9x_reproxy.sock_--no-lto/stdout), [swarming task](https://chromium-swarm.appspot.com/task?id=6ae3166ae8f6fd10&o=true&w=true))
Repository: pytorch
Issue: [ONNX] opset 11 aten::index_put generating invalid add ops with None args
Labels: module: onnx,triaged,OSS contribution wanted

### 🐛 Describe the bug

While regular torch tensor indexing supports Ellipsis (...) and the `torch.jit` graph represents it with None, the onnx exporter doesnt support this and generates non-functional `Add` ops silently. 

Tangentially related to #119363, but using `torch.onnx.export` in the `torch.jit.trace` flow without a nice error message. 

Heres some sanitized snippets from the `jit.graph` and the corresponding generated onnx nodes with the issue. Apologies in advance for not having a small reproducible test case and being unable to share the entire failing model/scripts. 

The initial PyTorch code:
```
A = torch.tensor(...)
B = torch.tensor(...)
C = torch.tensor(...)
D = [1, 2, 3]
E = torch.tensor(...)

E[..., D] = A * B + C
```

Resulting jit graph nodes:
```
%54807 : NoneType = prim::Constant()

%66300 : Long(3, strides=[1], requires_grad=0, device=cuda:0) = prim::Constant[value= 1  2  3 [ CUDALongType{3} ]]()

%66909 : Tensor?[] = prim::ListConstruct(%54807, %54807, %66300)

%66910 : Float(1, 2, 3, strides=[1, 2, 3], requires_grad=0, device=cuda:0) = aten::index_put(%61234, %66909, %61276, %66754)
```

Problematic exported onnx node from the `aten::index_put` node:
```
%959 : NoneType = prim::Constant()

%3535 : Tensor = onnx::Add(%959, %959)
```

This results in an ONNX op that tries to add two `None` values:
<img width="590" alt="Screenshot 2024-07-22 at 10 48 28 AM" src="https://github.com/user-attachments/assets/3623bfe2-5ef9-42c7-b61c-df37f3337d4c">

Ive debugged this down to: https://github.com/pytorch/pytorch/blob/407c87a32cc16569972c31ddb74e3f0c00f88f2c/torch/onnx/symbolic_opset11.py#L216-L219

We currently have a work around, but ideally we would like it to "just work" with a fix to generate valid onnx, or at least a relevant error message.

### Versions

Using an old nightly build from 2.4:
```
>>> torch.version.git_version
'2995cdef9a6203f0a97c022b875cde5748d06c09'
```
Repository: rust
Issue: global_asm-implemented extern "C" functions are not exported from dylib crates
Labels: A-linkage,T-compiler,C-bug

<!--
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, which is a minimized reproduction of https://github.com/EmbarkStudios/crash-handling/blob/main/crash-context/src/linux/getcontext.rs#L3-L12 and https://github.com/EmbarkStudios/crash-handling/blob/main/crash-context/src/linux/getcontext/x86_64.rs#L48:

```rust
std::arch::global_asm! {
    ".global foo",
"foo:",
    "ret",
}

extern "C" {
    pub fn foo();
}
```

With `lib.crate-type` set to `["dylib"]` or `["cdylib"]`.

I expected to see this happen: When building the example code here as an rdylib or cdylib, I expected to see `foo` present in the output dylib's symbols.

Instead, this happened: The output dylib has no symbols. It seems that for some reason, despite `foo` being a `pub fn`, the function is omitted from the list of extern symbols passed into the version-script. The symbol list file in my local case is completely empty. My guess here is that because `foo` is an `extern "C"` function, it's expected that the symbol is exported in some other object file / archive that would be statically linked in and then (maybe) caught by this https://github.com/rust-lang/rust/blob/20f23abbecd7ac5e04dd7ccadc29c3824e28a269/compiler/rustc_codegen_ssa/src/back/symbol_export.rs#L82-L83 ? But I am no rustc expert to say for sure.

```
$ cargo build
$ nm  target/debug/libdylib_global_asm.dylib | grep foo
target/debug/libdylib_global_asm.dylib: no symbols
```

One way to force the symbol here, as I'm running on an M1 mac, is to do the following:

```
$ RUSTFLAGS="-Clink-arg=-Wl,-exported_symbol,foo" cargo build
$ nm  target/debug/libdylib_global_asm.dylib | grep foo
0000000000003fa4 T foo
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

Tested on both stable + nightly.

`rustc --version --verbose`:
```
rustc 1.79.0 (129f3b996 2024-06-10)
binary: rustc
commit-hash: 129f3b9964af4d4a709d1383930ade12dfe7c081
commit-date: 2024-06-10
host: aarch64-apple-darwin
release: 1.79.0
LLVM version: 18.1.7

and 

rustc 1.82.0-nightly (92c6c0380 2024-07-21)
binary: rustc
commit-hash: 92c6c03805408a1a261b98013304e9bbf59ee428
commit-date: 2024-07-21
host: aarch64-apple-darwin
release: 1.82.0-nightly
LLVM version: 18.1.7
```
Repository: rust
Issue: UdpSocket `recv()` fails after `send()` to a closed port 
Labels: T-libs,C-discussion

Trying to `recv()` on a `UdpSocket` after a `send()` to a closed UDP socket fails

I tried this code:

```rust
use std::net::UdpSocket;

fn main() {
    let client = UdpSocket::bind("127.0.0.1:0").expect("failed to bind");
    let server = UdpSocket::bind("127.0.0.1:8080").expect("failed to bind");

    client.connect("127.0.0.1:1234").expect("connect function failed"); // no server at this address
    client.send(&[0; 10]).expect("couldn't send data"); // no error at this point

    let mut buf = [0; 10];
    match client.recv(&mut buf) {
        Ok(received) => println!("received {received} bytes {:?}", &buf[..received]),
        Err(e) => println!("recv function failed: {e:?}"), // we get an error here
    }
}
```

I expected to see this happen:
We should be able to `recv()` without any error

Instead, this happened:
`recv()` fails

Golang currently handles this using `SIO_UDP_CONNRESET` here: https://github.com/golang/go/blob/e8c5bed7ea43e1a533c322e6b928ed06327721db/src/internal/poll/fd_windows.go#L340-L351

### Meta

`rustc --version --verbose`:
```
rustc 1.79.0 (129f3b996 2024-06-10)
binary: rustc
commit-hash: 129f3b9964af4d4a709d1383930ade12dfe7c081
commit-date: 2024-06-10
host: x86_64-pc-windows-msvc
release: 1.79.0
LLVM version: 18.1.7
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
recv function failed: Os { code: 10054, kind: ConnectionReset, message: "An existing connection was forcibly closed by the remote host." }
```

</p>
</details>
Repository: pytorch
Issue: Follow ups from Increase (4x+) in build times #130744
Labels: triaged,module: devx

Follow ups from https://github.com/pytorch/pytorch/issues/130744 so we can have an open issue but still leave the original one with the sev label

AI:
* check that sccache can write to bucket and error if not
* Better monitoring for increases in build time 
* Better rollout plan for amazonlinux 2023 AMI migration (ex make a new label that uses the new AMI and duplicating jobs to run on that while leaving the old label + original jobs the same)

cc @ZainRizvi @kit1980 @huydhn
Repository: flutter
Issue: Add validator to DropdownMenu
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

There is no `validator` property on DropdownMenu.
It is tricky to show error messages on DropdownMenu because of not knowing when the validation is being ran on the parent form.



### Proposal

When using DropdownMenu, it'd be great to have a `validator` property, as we already do for `FormField`:
https://api.flutter.dev/flutter/widgets/FormField/validator.html
Repository: kubernetes
Issue: Adding additional guards on CRD schema
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

Previously a [issue reported ](https://github.com/kubernetes/kubernetes/issues/126133) for CRD schema conversion. 
We have a [quick fix ](https://github.com/kubernetes/kubernetes/pull/126167) for not panic the cluser.
We would love to have additional guards added to prevent invalid schema from getting in in the future.

From @liggitt : https://github.com/kubernetes/kubernetes/issues/126133#issuecomment-2231712524

### What did you expect to happen?

Validation should prevent this type of schema(Items with type object/ properties with type array) from being accepted at all.

### How can we reproduce it (as minimally and precisely as possible)?

Follow the steps described in https://github.com/kubernetes/kubernetes/issues/126133

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: rust
Issue: The `slice::chunks_exact` iterator does not optimize when the initial slice is non-empty
Labels: I-slow,T-compiler,I-heavy,C-optimization

I tried this code:

```rust
use std::hint::black_box;

pub fn demo(data: &[u8]) {
    assert!(!data.is_empty());

    let mut chunks = data.chunks_exact(1024);

    let last_block = if chunks.remainder().is_empty() {
        chunks.next_back().expect("this is impossible")
    } else {
        chunks.remainder()
    };

    black_box(last_block);
}
```

When compiled with optimizations enabled and viewing the assembly code, I expected to not see a reference to the string `"this is impossible"`. Since there's an assert that the input data is non-empty, then either there will be a remainder, there will be at least one chunk, or both. 

Instead, the assembly contains a reference to the `expect` string and there's a conditional call to `expect_failed`. 

### Meta

- 1.79.0
- 1.81.0-nightly (2024-07-12 c6727fc9b5c64cefa726)
Repository: PowerToys
Issue: PowerToys causes a limit on how many keys that can be pressed at a time
Labels: Issue-Bug,Needs-Repro

### Microsoft PowerToys version

0.82.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

>Run PowerToys
>Open a game
>Try play game
>Can't press more than 3 keys at a time as it doesn't register any more key pressed

### ✔️ Expected Behavior

Allow me to press more than 3 keys and register all.

### ❌ Actual Behavior

Doesn't let me press more than three keys as it does't register anymore.
[Administrator Power Toys Settings.txt](https://github.com/user-attachments/files/16339592/Administrator.Power.Toys.Settings.txt)


### Other Software

_No response_
Repository: kubernetes
Issue: Remove version requirement for recognizeKeywordAsFieldName after update default compatible version
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Follow up PR needed in 1.32 after https://github.com/kubernetes/kubernetes/pull/126188

### Why is this needed?

We would love to support reserved keyword in new expression starting 1.32 to meet compatibility concern.