sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Feature Request: Clear All Terminal consoles at Once
Labels: feature-request,terminal

<!-- ⚠️⚠️ 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. -->

#### Description
I would like to request a feature that allows users to clear all open terminal consoles in VSCode with a single command.

Currently, we can clear individual terminals using the command `workbench.action.terminal.clear`, but there is no native way to clear all open terminal consoles at once. This feature would greatly improve productivity, especially for developers who manage multiple terminals simultaneously in their workspace.

#### Suggested Solution
When a user runs the command to clear multiple terminals, they should be presented with a list of all open terminal instances. The user can then select one or more terminals they wish to clear.

- Display Terminal Selection
- Clear Selected Terminals


#### Why This Feature is Needed
- **Efficiency**: When working with multiple terminal windows (e.g., during development or debugging), it becomes tedious to manually clear each terminal one by one.
- **Consistency**: Having a way to reset the terminal windows across the workspace can help maintain a clean and organized development environment.

#### Use Cases
- A developer working with several terminal instances for different tasks (e.g., running a server, executing commands, and logging) can clear all the terminals at once after a deployment or cleanup operation.
- Teams using multiple terminals to monitor logs and processes can benefit from an easy reset mechanism.
Repository: rust
Issue: Add rationale for `rustc_lint` behind allowing rustc::potential-query-instability lint
Labels: C-cleanup,T-compiler

**Context:** https://github.com/rust-lang/rust/issues/84447

**Motivation:**

1. This lint asks to do so. An example:
    ```rs
    error: using `values` can result in unstable query results
       --> compiler/rustc_query_system/src/dep_graph/serialized.rs:654:50
        |
    654 |             let mut stats: Vec<_> = record_stats.values().collect();
        |                                                  ^^^^^^
        |
        = note: if you believe this case to be fine, allow this lint and add a comment explaining your rationale
    ```
2. This would prevent further fix attempts so wastes of time as well.
3. Nearly all of those allowances has a comment which explains the rationale.

**To do:** Add a comment explaning the rationale behind allowing rustc::potential-query-instability lint for this occurrence in the file [`compiler/rustc_lint/src/context/diagnostics/check_cfg.rs`](https://github.com/rust-lang/rust/blob/master/compiler/rustc_lint/src/context/diagnostics/check_cfg.rs):

```rs
pub(super) fn unexpected_cfg_name(
    sess: &Session,
    (name, name_span): (Symbol, Span),
    value: Option<(Symbol, Span)>,
) -> lints::UnexpectedCfgName {
    #[allow(rustc::potential_query_instability)]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    let possibilities: Vec<Symbol> = sess.psess.check_config.expecteds.keys().copied().collect();

    let mut names_possibilities: Vec<_> = if value.is_none() {
```
Repository: rust
Issue: Add rationale for `rustc_type_ir` behind allowing rustc::potential-query-instability lint
Labels: C-cleanup,T-compiler

**Context:** https://github.com/rust-lang/rust/issues/84447

**Motivation:**

1. This lint asks to do so. An example:
    ```rs
    error: using `values` can result in unstable query results
       --> compiler/rustc_query_system/src/dep_graph/serialized.rs:654:50
        |
    654 |             let mut stats: Vec<_> = record_stats.values().collect();
        |                                                  ^^^^^^
        |
        = note: if you believe this case to be fine, allow this lint and add a comment explaining your rationale
    ```
2. This would prevent further fix attempts so wastes of time as well.
3. Nearly all of those allowances has a comment which explains the rationale.

**To do:** Add a comment explaning the rationale behind allowing rustc::potential-query-instability lint for all occurrences in the file [`compiler/rustc_type_ir/src/search_graph/mod.rs`](https://github.com/rust-lang/rust/blob/master/compiler/rustc_type_ir/src/search_graph/mod.rs). You can find the places where this lint is triggered by searching with `#[allow(rustc::potential_query_instability)]` in this file.
Repository: kubernetes
Issue: Avoid adding a dependency to k8s.io/api on an apimachinery constant
Labels: sig/api-machinery,area/code-organization,triage/accepted

https://github.com/kubernetes/kubernetes/blob/7b28a115ba04651bc31aa1d7089abbd67ec5c067/staging/src/k8s.io/api/resource/v1alpha3/types.go#L186

If we define a constant as a public API, we should assume it will never change, so avoiding the import and just referencing it in the comment should be enough

/area code-organization
Repository: godot
Issue: Web-Export HTTP-Request link parser doesn't parse IPv6 links correctly
Labels: bug,platform:web,topic:core

### Tested versions

- Reproducible in 4.3

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3050 Laptop GPU (NVIDIA; 32.0.15.6109) - 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 Threads) - Web-Browser: Firefox

### Issue description

When sending a HTTP-Request (also happens with Websocket I think?) in the Web-Export, IPv6 Links dont get parsed correctly: for example the link: http://[1234:1234:1234:1234:1234:1234:1234:1234]:80/post gets parsed to http://1234:1234:1234:1234:1234:1234:1234:1234:80/post in the Web-Export. To get the connection correctly you would have to give the link: http://[[1234:1234:1234:1234:1234:1234:1234:1234]]:80/post
I can confirm that this will work for both Websocket and http and will actually connect correctly.

### Steps to reproduce

Send an HTTP-Request over IPv6 in the program, export that for the web and host it, with this: https://raw.githubusercontent.com/godotengine/godot/master/platform/web/serve.py for example. open the console in your browser before opening the Export. When the HTTP Request is send it should give the error message: TypeError: Window.fetch: http://1234:1234:1234:1234:1234:1234:1234:1234:80/post is not a valid URL. and the post request is not send. If the request was valid a cross-origin error would be raised instead.

### Minimal reproduction project (MRP)

[http_util.zip](https://github.com/user-attachments/files/17268803/http_util.zip)
this programm sends a HTTP Post-Request to the address given in the text input, after the button is pressed. used the browser-terminal to see if the request worked or not.
Repository: ollama
Issue: Adrenalin Edition 24.9.1/24.10.1 slow ollama performance
Labels: bug,performance,windows,amd

### What is the issue?

Both Adrenalin Edition drivers (24.9.1 and 24.10.1) significantly slows windows performance. GPU acceleration appears disabled.

No issues with ollama on Adrenalin 24.8.1 (slightly older driver)

My system
Windows 11 24H2
GPU: RX6800 XT
CPU: Ryzen 5900XT
32GB RAM
Ollama version: Latest
Repository: kubernetes
Issue: Allow go k8s client to accept KUBECONFIG env readily
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

The kubeconfig environment variable typically uses a colon-separated format for specifying multiple paths. However, the Kubernetes Go client library currently only supports a single path. This inconsistency can be confusing for developers. To simplify things, let's make the Go client accept the colon-separated format for kubeconfig paths, making it consistent with the standard environment variable format.

KUBECONFIG env doc: https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable

Following is the simple example to explain the issue:
![image](https://github.com/user-attachments/assets/0d439b43-0220-4501-bd25-eb72a56e425b)


### Why is this needed?

Currently, users have to do extra work to get the config-path value from `KUBECONFIG` env. The Go client library expects a single value, but the system environment variables for `KUBECONFIG` are separated by colons. Let's make the Go client accept the `KUBECONFIG` env value readily. This would make it consistent with how the system handles these variables and make things easier for developers
Repository: TypeScript
Issue: Use string literal type in `ArrayBuffer`'s `Symbol.toStringTag`
Labels: Fix Available

### ⚙ Compilation target

ES2023

### ⚙ Library

N/A

### Missing / Incorrect Definition

For ES2023 or lower targets, it is acceptable to assign `SharedArrayBuffer` to an `ArrayBuffer` type. On the other hand, the reverse is not possible because `Symbol.toStringTag` of `SharedArrayBuffer` is a string literal type. 

This problem can be solved by making `Symbol.toStringTag` of `ArrayBuffer` a string literal type. `Set`, `Map`, and `Promise` use the `string` type for library compatibility (#19006), while `ArrayBuffer` is not intended to be extended by the user, and indeed `Symbol.species` support for `InitializeTypedArrayFromTypedArray` has been removed (https://github.com/tc39/ecma262/pull/2719), so there should be no problem.

This issue was reported by #59417 and has been addressed by making TypedArrays generic for the ES2024 target.

### Sample Code

```TypeScript
// ES2023 or lower targets, no type error
const buffer: ArrayBuffer = new SharedArrayBuffer(256);
```


### Documentation Link

_No response_
Repository: godot
Issue: TilemapLayer flickers in CanvasModulate
Labels: bug,topic:rendering,topic:2d

### Tested versions

4.3.stable

### System information

Win10 v4.3 Vulkan(Forward+)

### Issue description


https://github.com/user-attachments/assets/7e9dab57-2d4b-4b9d-b731-2660dbac8d6a

![cd71245b-2d76-4c30-9ad9-e958e429d899](https://github.com/user-attachments/assets/51e7e09b-34b4-46c5-a2e7-051ec17c8003)

Recently  I was trying to find a way to make a lot of lights in a dark environment, and I came across this problem. The screenshot has 3 parts. Part B is a Light2D, which works fine. Part C is a Sprite2D with a shader, which flickers badly. So at first, I guessed it was a shader problem. But I found that Part A also flickers, although not as bad as Part C because it is too dark.
For comparison, the Sprite2D on the right also flickers, and is not as bad as the TilemapLayer on the left.

Removing the Light2D and lighting Sprite2D does not help, and the TilemapLayer still flickers in the CanvasModulate.

Also, if CanvasModulate wasn't so dark, this wouldn't be as much of a problem.
![image](https://github.com/user-attachments/assets/050a203e-e20b-452e-bc71-0b67e08d8e6a)
You can select the commented out config to see the effect.

### Steps to reproduce

I posted a minimal reproduction project.

### Minimal reproduction project (MRP)

[lightshader.zip](https://github.com/user-attachments/files/17269162/lightshader.zip)
Repository: rust
Issue: Wrongly suggests error E0029 in match range
Labels: A-diagnostics,T-compiler

### Code
```rust
fn cmp<T: PartialOrd, R>(x: T, y: T, smaller: R, equal: R, greater: R) -> R {
    match x {
        ..y => smaller,
        y   => equal,
        _   => greater
    }
}
```
### Current output
```
error[E0029]: only `char` and numeric types are allowed in range patterns
 --> src/main.rs:3:11
  |
3 |         ..y => smaller,
  |           ^ this is of type `T` but it should be `char` or numeric
```
### Desired output
```
error[E0080]: runtime values cannot be referenced in patterns
 --> src/main.rs:3:11
  |
3 |         ..y => smaller,
  |           ^
```
### Rationale and extra context

The second output comes when following that wrong suggestion and changing to
```rust
fn cmp<R>(x: char, y: char, smaller: R, equal: R, greater: R) -> R {
    match x {
        ..y => smaller,
        y   => equal,
        _   => greater
    }
}
```
cf. [forum](https://internals.rust-lang.org/t/overly-limited-match/21651)

### Other cases

_No response_

### Rust Version

rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7

### Anything else?

_No response_
Repository: node
Issue: Accepting `CryptoKey` in `node:crypto` APIs
Labels: crypto,discuss,webcrypto,never-stale

The following APIs accept a `CryptoKey` instance and process the operation despite the restrictions put forth on the `CryptoKey` instance (e.g. algorithm, usages, extractable)

- KeyObject.from (ignores `extractable`)
- crypto.publicDecrypt
- crypto.publicEncrypt
- crypto.privateDecrypt
- crypto.privateEncrypt
- crypto.sign
- crypto.verify
- Sign.sign
- Verify.verify
- Cipher.final
- Decipher.final
- Hmac.digest

This list is according to the docs, but i suspect it's possible that hkdf and pbkdf2 allow this too.

This issue is to discuss a way forward to deal with this issues.

## KeyObject.from

https://github.com/nodejs/node/pull/37240 attempted to do something about KeyObject.from but i think the outcome would not solve the issues above.

I believe that converting key representations is not an issue so long as the more restrictive key representation's properties are upheld.

We can take a drastic stance and deprecate / in due time remove KeyObject.from entirely, or make KeyObject.from respect the `extractable` property and duly document that once the key is converted the CryptoKey restrictions are not upheld anymore. I'd much rather see the latter.

Another possible approach would be to disable KeyObject.export on keys that came from non-extractable CryptoKey.

## APIs accepting CryptoKey but ignoring its parameters.

We could deprecate the use of CryptoKey in these APIs entirely or emulate WebCryptoAPI behaviour and check the CryptoKey usages and algorithm slots, either way this would be a doc-only deprecation at first, then --pending-deprecation, runtime deprecation, throw behaviour at the end.
Repository: ui
Issue: [bug]: The chart color picker on blocks page does not change chart color
Labels: bug

### Describe the bug

On the [Blocks](https://ui.shadcn.com/blocks) page, the color picker to the right that is supposed to change the color of the charts does nothing as far as I can see. Feels very broken, and I assume it is broken

https://github.com/user-attachments/assets/125fb15f-c96d-4ee4-84b7-c87e84ebdda1

### Affected component/components

Blocks

### How to reproduce

1. Go to [Blocks](https://ui.shadcn.com/blocks) page
2. Click one of the color pickers to the right
3. Nothing happens to the charts

### Codesandbox/StackBlitz link

There is not sandbox as its on the main website

### Logs

_No response_

### System Info

```bash
MacBook Pro M2

Arc browser 1.61.1 
Chromium Engine Version 129.0.6668.59
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: The scrollable part of the scrollbar has low contrast with the background
Labels: O-windows,T-rustdoc,A-rustdoc-ui,T-rustdoc-frontend

I thought I was going mad but indeed, the dark bit is the part of the scrollbar here that is grabbable:

![Image](https://github.com/user-attachments/assets/8825dc65-c76e-4847-9fd8-a2f9e895e1a2)
Repository: deno
Issue: 🐛(WinOS) unable to open network or device paths without `--allow-all`
Labels: needs discussion

```shell
❯ deno --version
deno 2.0.0-rc.10 (release candidate, release, x86_64-pc-windows-msvc)
v8 12.9.202.13-rusty
typescript 5.6.2
```

For WinOS, network file paths such as "//server/path/to/foo", drive mounted network paths, and device paths (eg, "//./device/path") require `--allow-all` permissions to open/manipulate. If `--allow-all` isn't provided, no permission prompt is supplied; instead, a "NotCapable" error/panic is produced.

These paths, when opened, should instead require some specific permission or permission set (`--allow-sys`?, `--allow-net`?, possibly on top of `--allow-read` and/or `--allow-write`). ~~POSIX-type network paths don't seem to have the same issue.~~

It seems that, now, as of Deno-v1.46.3, POSIX-like device paths such as '/dev/tty' also have the same permission issue.

From testing, on Linux (? MacOS), mounted remote shares only seem to need read/write permissions.

### related issues/PRs (all stalled)

PR <https://github.com/denoland/deno/pull/25132> as a solution to <https://github.com/denoland/deno/issues/24703>.
PR <https://github.com/denoland/deno/pull/25851> as a solution to <https://github.com/denoland/deno/issues/24791>.
Repository: godot
Issue: when the chosen language is a right-to-left language(Persian in my case) the placement of elements inside the 2D scene editor is different from when the project is run
Labels: bug,topic:editor

### Tested versions

Reproducible in: v4.3.stable.official [77dcf97d8] and v4.2.stable.official [46dc27791]. pretty sure in earlier versions as well

### System information

windows 10, i5 9400F, GT 1030 driver version: 31.0.15.3623

### Issue description

when the editor is in a RTL language(Persian in this instance) while the UI flips as it should(the scene tree moving to right and so on) the elements inside the scene editor also flip horizontally meaning when you put a node on the left side of the screen you're actually putting it on the right side, which you can see when you run the project you're working on.
![Screenshot (168)](https://github.com/user-attachments/assets/25483bf1-e1e0-4549-b867-eb25b050579e)
![Screenshot (170)](https://github.com/user-attachments/assets/d70e84d0-0773-450d-9f37-45ce25fdbf1e)
additionally the problem also includes control nodes; when using any type of placement option offered by control nodes whether in the inspector or top of the scene editor(anchor presets, container sizing, etc...) they will work oppositely. 
take into account that I've only tested 2D and while not completely sure i believe the problem also affects 3D to some degree.
keep in mind that this is a seriously huge problem, rendering the engine borderline unusable in RTL languages.


Unrelated note: if you're translating the engine to Persian or are interested in doing so please contact me in discord: kushyar.n

### Steps to reproduce

change the language to Persian and place the Godot logo on the left side of editor, then run the project.

### Minimal reproduction project (MRP)

N/A
Repository: bitcoin
Issue: Crash upon RPC v1 connection in v28.0.0
Labels: Linux/Unix,Resource usage

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

On RPC v1 connection, after the block sync and mempool read is complete, a crash happens (see logs). I used mempool fork of electrs indexer which did an RPC request. 

Original report can be found here: https://github.com/bitcoin/bitcoin/issues/31039#issuecomment-2395525458

### Expected behaviour

No crash is expected

### Steps to reproduce

Run Bitcoin Core (I used machine with 8 cores, and 4GB or 8GB of memory)

### Relevant log output

```
Oct 06 17:54:18 core bitcoind[16532]: 2024-10-06T17:54:18Z initload thread exit
Oct 06 17:55:43 core systemd[1]: bitcoind.service: A process of this unit has been killed by the OOM killer.
░░ Subject: A process of bitcoind.service unit has been killed by the OOM killer.
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM)
░░ killer logic. This usually indicates that the system is low on memory and that
░░ memory needed to be freed. A process associated with bitcoind.service has been determined
░░ as the best process to terminate and has been forcibly terminated by the
░░ kernel.
░░ 
░░ Note that the memory pressure might or might not have been caused by bitcoind.service.
Oct 06 17:55:43 core systemd[1]: bitcoind.service: Main process exited, code=killed, status=9/KILL
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit bitcoind.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 9.
Oct 06 17:55:43 core systemd[1]: bitcoind.service: Failed with result 'oom-kill'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit bitcoind.service has entered the 'failed' state with result 'oom-kill'.
Oct 06 17:55:43 core systemd[1]: bitcoind.service: Consumed 3min 18.749s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit bitcoind.service completed and consumed the indicated resources.
Oct 06 17:55:43 core systemd[1]: bitcoind.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit bitcoind.service has been scheduled, as the result for
```

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

v28.0.0

### Operating system and version

Debian Bookworm

### Machine specifications

8 CPUs; 4GB RAM
Repository: tauri
Issue: [bug] tauri ios init fails on M1 mac if homebrew is not installed
Labels: type: bug,platform: macOS,status: needs triage,platform: iOS

### Describe the bug

After installing prerequisites, running `bun run tauri ios init`, results in:

```zsh
$ tauri ios init
    Warn No code signing certificates found. You must add one and set the certificate development team ID on the `bundle > iOS > developmentTeam` config value or the `APPLE_DEVELOPMENT_TEAM` environment variable. To list the available certificates, run `tauri info`.
    Info detected rustc version 1.81.0 (eeb90cda1 2024-9-4)
/usr/local/bin/xcodegen
    Info package `xcodegen` present: true
/opt/local/bin/idevicesyslog
    Info package `libimobiledevice` present: true
/usr/local/bin/pod
    Info package `cocoapods` present: true
failed to install Apple dependencies: Failed to check for outdated packages: No such file or directory (os error 2): No such file or directory (os error 2)
    Error failed to install Apple dependencies: Failed to check for outdated packages: No such file or directory (os error 2): No such file or directory (os error 2)
error: script "tauri" exited with code 1
```

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 15.0.0 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 18.18.2
    - pnpm: 9.6.0
    - npm: 9.8.1
    - bun: 1.1.29

[-] Packages
    - tauri 🦀: 2.0.0
    - tauri-build 🦀: No version detected
    - wry 🦀: No version detected
    - tao 🦀: No version detected
    - @tauri-apps/api : 2.0.1
    - @tauri-apps/cli : 2.0.1

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.0
    - @tauri-apps/plugin-shell : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_