sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `doc_auto_cfg` obfuscates documentation formatting
Labels: C-bug,A-rustdoc-ui,T-rustdoc-frontend

### Problem

I generated documentation for my project, first using stable and then nightly (to document features). The doc generated by the nightly toolchain is formatted very strangely. After removing / adding the `doc_auto_cfg` nightly feature, it seems that the feature is the cause of this:

| Stable & Beta | Nightly (with `doc_auto_cfg`) | Nightly (no `doc_auto_cfg`) |
|---|---|---|
| ![stable-and-beta](https://github.com/user-attachments/assets/e9dcb7ac-f900-4dc5-a991-2cef9c2d8911) | ![nightly](https://github.com/user-attachments/assets/3e6c8e3a-a26f-44e5-910a-78ce531e95b5) | ![nightly-no-feat](https://github.com/user-attachments/assets/2b96963e-e395-4978-9533-a426893413df) |

While I would expect feature-dependent items to have their formatting altered, it seems that every item is affected here.

### Steps

1. Document an item that is both 
    - accessible through public modules
    - re-exported publicly (e.g. in a prelude)
2. generate the doc using `cargo +nightly doc`, see result
3. enable the `doc_auto_cfg` feature, repeat step 2

### Possible Solution(s)

FWIW I'm guessing there is some hard-coded html/css somewhere to handle the small feature note; maybe the position of the note puts a constraint on text width?

### Notes

I'm guessing the issue occurs whenever there is a public re-exports of an tiem that "has a public path".

I have a custom build script to conditionally enable some gated features depending on the toolchain used to build:

```rust
// build.rs

#[rustversion::nightly]
fn set_rustc_channel_cfg() -> &'static str {
    "nightly"
}

#[rustversion::beta]
fn set_rustc_channel_cfg() -> &'static str {
    "beta"
}

#[rustversion::stable]
fn set_rustc_channel_cfg() -> &'static str {
    "stable"
}

fn main() {
    println!("cargo:rustc-cfg={}", set_rustc_channel_cfg());
}
```

```rust
// lib.rs

// ...

#![allow(unexpected_cfgs)]
#![cfg_attr(nightly, feature(doc_auto_cfg))]

// ...
```

### Version

Nightly
```
cargo 1.83.0-nightly (8f40fc59f 2024-08-21)
release: 1.83.0-nightly
commit-hash: 8f40fc59fb0c8df91c97405785197f3c630304ea
commit-date: 2024-08-21
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: AlmaLinux 9.4.0 [64-bit]
```
Repository: kubernetes
Issue: kubectl get nodes with JSONPath doesn't report node.kubernetes.io/unschedulable taint
Labels: kind/bug,sig/cli,lifecycle/rotten,needs-triage

### What happened?

I cordoned a node, then ran the following command to list all nodes that have the `node.kubernetes.io/unschedulable` taint:

```bash
kubectl get nodes -o jsonpath="{.items[?(@.spec.taints[].key=='node.kubernetes.io/unschedulable')].metadata.name}"
```

the cordoned node was not included in the list, even though describing the node I can see that it does have the taint and the field `.spec.unschedulable` is set to `true`.

### What did you expect to happen?

I expected to get `metadata.name` of the node that has been marked as unschedulable instead.

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

### Common

1. Cordon a node.

### Test 1

2. Run the command:

```bash
kubectl get nodes -o jsonpath="{.items[?(@.spec.taints[].key=='node.kubernetes.io/unschedulable')].metadata.name}"
```

3. The node is **not** listed.

### Test 2

4. Run the command:

```bash
kubectl get nodes -o jsonpath="{.items[?(@.spec.unschedulable)].metadata.name}"
```

5. The node's `metadata.name` is printed.

### Test 3

6. Run the command:

```bash
kubectl get nodes -ojsonpath='{}' |  jq  -r '.items[] | select(try .spec.taints[].key == "node.kubernetes.io/unschedulable") .metadata.name'
```

7. The node's `metadata.name` is printed.

### Anything else we need to know?

THe following also works:

```bash
kubectl get nodes -ojson | jq -r '.items[] | select(try .spec.taints[].key == ("node.kubernetes.io/unschedulable")) .metadata.name'
```

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.31.0
Kustomize Version: v5.4.2
Server Version: v1.29.3
```

</details>


### Cloud provider

<details>
Kubeadm cluster
</details>


### OS version

<details>

```console
Client running on macos, Kubernetes API server running on:

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
$ uname -a
Linux master1 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 23:26:06 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
```

</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: godot
Issue: Loading large RichtTextLabel takes a long time
Labels: bug,needs testing,topic:gui,performance

### Tested versions

4.3.stable

### System information

Pop!_OS 22.04

### Issue description

My app starting more slowly with every version I released. I've been debugging it for most of the day only to find out that my change-log was the culprit. I've been using a RichtTextLabel and just added to this label with every release. Right now loading the scene which includes the release notes takes about 6 seconds on my 11th gen i7. 



### Steps to reproduce

1. Add a RichtTextLabel to a scene.
2. Create a nice Lorem Ipsum and copy it a few dozen times into this RichTextLabel.
3. See your scene loading slower with every paragraph added.

### Minimal reproduction project (MRP)

[RichTextLabel.zip](https://github.com/user-attachments/files/16838332/RichTextLabel.zip)
Repository: flutter
Issue: Offer a deep linking solution for the News toolkit
Labels: c: proposal,team-news

### Use case

As an active user of the News Toolkit, I’ve used it twice, and on both occasions, clients specifically requested the implementation of a deep linking solution. In my experience, deep linking is an essential feature for news applications to enhance user engagement and provide a seamless user experience. A common scenario is when a user shares a link to a news article, but instead of opening directly in the app, the link redirects to the web, even if the app is installed. I believe adding deep linking functionality would increase the value of the toolkit.

### Proposal

This feature request stems from an existing PR I created for the News Toolkit. The toolkit currently uses Firebase Dynamic Links to handle sign-in with email links. However, with the announcement that Dynamic Links are being deprecated, I created a PR that adds an abstraction for the deep link client, DeepLinkClient, and implements this abstraction using the current Dynamic Links setup. The abstraction would enable an easy transition from Dynamic Links to a new solution. 

But then Firebase communicated that this functionality will be replaced, not deprecated. Still, adding the abstraction could be a first step toward integrating deep link handling into the toolkit.

My proposal is to build on top of the existing PR ([#1158](https://github.com/flutter/news_toolkit/pull/1158)) and implement the simplest form of deep link handling for the News Toolkit: opening a news article based on the link that opened the app. The most common scenario would involve extracting the slug from the link, which is usually the string following the last forward slash. For example:

```
https://blog.google/technology/ai/google-io-2024-100-announcements/
```

The slug for this link would be google-io-2024-100-announcements.

The initial scope of this feature would be to extract the slug from the link and add a search by slug API to the dart frog server.
Repository: awesome-mac
Issue: 🎉 Add Blip
Labels: addition

### 🪩 Provide a link to the proposed addition

https://blip.net/

### 😳 Explain why it should be added

In cases where people have a Mac but not an iPhone, or have an iPad but not a Mac, this app helps us send files seamlessly through various devices and covers many such cases.

### 📖 Additional context

_No response_

### 🧨 Issue Checklist

- [X] I have checked for other similar issues
- [X] I have explained why this change is important
- [ ] I have added necessary documentation (if appropriate)
Repository: storybook
Issue: [Bug]: Control loses focus if subcomponents are defined
Labels: bug,needs triage

### Describe the bug

Declaring a subcomponent for a component makes controls on the `docs` page lose focus when updating values. This is the most apparent when typing, but any value change causes the control to lose focus.

I forked [the vite + react + ts stackblitz](https://stackblitz.com/github/storybookjs/sandboxes/tree/next/react-vite/default-ts/after-storybook?file=README.md&preset=node) and the only thing I altered was to add a subcomponent for the `Button` component.

### Reproduction link

https://stackblitz.com/edit/github-ygdrxf

### Reproduction steps

1. Go to above link
2. Go to Button docs page
3. Try to type in `label` control

```
Expected: Typing to work as per normal
Actual: Loses focus whenever a character is typed/removed
```

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/addon-interactions: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/addon-links: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/addon-onboarding: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/blocks: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/react: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/react-vite: ^8.3.0-beta.1 => 8.3.0-beta.1 
    @storybook/test: ^8.3.0-beta.1 => 8.3.0-beta.1 
    storybook: ^8.3.0-beta.1 => 8.3.0-beta.1
```


### Additional context

_No response_
Repository: node
Issue: Reuse Blob Registry in Workers
Labels: feature request,worker

Node.js currently lacks support for sharing blob object URLs within Workers. This feature request aims to enable that capability, allowing blob URLs to be used in Workers. Implementing this change would also integrate well #54647.

Ref: <https://openjs-foundation.slack.com/archives/C053UCCP940/p1725223124157009?thread_ts=1725214637.560639&cid=C053UCCP940>
Ref: #54647

---

Currently, most browser runtimes support sharing Blobs in web workers, however, Deno does not support this behavior.
Repository: rust
Issue: -Csoft-float flag is unsound
Labels: A-LLVM,A-codegen,O-Arm,P-medium,T-compiler,I-unsound,A-ABI

Current status: all use of the flag causes a warning (will be shipped in 1.83), announcing that it will become a hard error in the future.

---

@bjorn3 just made me aware of this amazing flag:
```
    -C               soft-float=val -- use soft float ABI (*eabihf targets only) (default: no)
```
This is quite unsound: if code gets compiled with `-Csoft-float` and calls code from the standard library that uses the hard float ABI, we have UB. Generally we need different target triples for softfloat vs hardfloat ABIs, since (as per the discussion in https://github.com/rust-lang/lang-team/issues/235) code within a single target should be ABI compatible. Cargo even (unstably) allows overwriting `RUSTFLAGS` on a per-crate basis, so we better make sure crates compiled with different flags can be linked with each other.

This was added a looooong time ago in https://github.com/rust-lang/rust/pull/9617. I couldn't find any discussion regarding its soundness.

We have e.g. `arm-unknown-linux-musleabi` and `arm-unknown-linux-musleabihf`, so using the `*hf` target but with `-Csoft-float` also seems kind of unnecessary. (But I have not checked whether all `eabihf` targets have a corresponding `eabi` target.)

According to the documentation, this can only be used by ARM targets. So paging in some ARM folks -- is this used in practice, and if yes, how do people avoid the soundness problems?
@rustbot ping arm

Note that this issue is **not about `-Ctarget-feature=+soft-float`**, see https://github.com/rust-lang/rust/issues/116344 for that.
Repository: pytorch
Issue: _rebuild_sparse_tensor
Labels: module: sparse,triaged

### 🚀 The feature, motivation and pitch

I am using a distribution framework to accelerate training process. But when I transfer an object contains Sparse CSR, An error occured:

```
ray.exceptions.RaySystemError: System error: rebuilding sparse tensor for layout torch.sparse_csr
traceback: Traceback (most recent call last):
  File "~/.conda/envs/pytorch_base/lib/python3.10/site-packages/torch/_utils.py", line 210, in _rebuild_sparse_tensor
    raise NotImplementedError("rebuilding sparse tensor for layout %s" % (layout))
NotImplementedError: rebuilding sparse tensor for layout torch.sparse_csr
```

Since the interface is not custom, but provided for many other modules, we have to give up the module using sparse tensors which broke our workflow.

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: TypeScript
Issue: NoInfer doesn't work in string template types
Labels: Bug

### 🔎 Search Terms

NoInfer string template

### 🕗 Version & Regression Information

This issue exists in every Playground-accessible version that has `NoInfer`.

### ⏯ Playground Link

[here](https://www.typescriptlang.org/play/?ts=5.5.4#code/GYVwdgxgLglg9mABMAPAQQHwAoCGAuRAOTgEkxgBTAJ3QwBpEAjAtRCgDygrABMBnRHyhUYYAOaIA-IgAGVCgBs8AEgDeaAL4zEBMBQBu1AJSJVGgFDAsAIgCs1htflKA7NaMBuRAHpvbKlRwVIgAtIgQQfLQDFAAngAOFIhwwIisMALWbuaW4NDwSGK0uCwMzGlsnNz8gsKiEtJyiiqqxGSUNJhaOoh6hlQmZua+yHmwCIhFmCVpZSyVXLwCQiLiUkSk5NQoTUpqmjIYPX3GphYjoJDjhcX4s0wEbVudC9XLdWuNzi0HxwbUGEGFjENnsjm+bk8Pj8YDg-kCwTCfBAVHiIj49VCiDiiWSqXSAlB1kQAB9EFl3EA)

### 💻 Code

```ts
function f<A>(a: NoInfer<A>, b: A extends string ? `rel:${A}` : never) {}
f("5", "rel:7"); // error - correct, type of A is "7"
```

but 

```ts
function g<A>(a: A, b: A extends string ? `rel:${NoInfer<A>}` : never) {}
g("5", "rel:7"); // no error - surprising - type of A is inferred to be ("5" | "7")
```

### 🙁 Actual behavior

no type error on `g()` above, because the `A` type is being inferred via the string template in spite of the `NoInfer` marker.

### 🙂 Expected behavior

Both of the example calls should be recognized as wrong?

### Additional information about the issue

Also tried 

```ts
function g<A>(a: A, b: A extends string ? NoInfer<`rel:${A}`> : never) {}
function g<A>(a: A, b: NoInfer<A extends string ? `rel:${A}` : never>) {}
```

no luck.
Repository: godot
Issue: Begin Rotate/Scale/Translate Transformation wrapping doesn't keep the cursor inside the editor and fails.
Labels: bug,topic:editor,topic:3d

- *Production edit: Related to
https://github.com/godotengine/godot/issues/57119 and
https://github.com/godotengine/godot/issues/78768.*

### Tested versions

4.3

### System information

Windows 11 - Vulkan - Nvidia RTX 4070 - intel i5 13600KF

### Issue description

If you use any of the Transformation shortcuts and move your mouse outside right/left the cursor will almost always leave the editor window the movement is then not tracked thus the transformation fails to continue.

### Steps to reproduce

1. Add a shortcut to any of the transformations above in the Editor Settings (default is None).
2. Add a MeshInstance3D and assign it any mesh so you can observe when the commands work and when they don't.
3. Use the shortcut command and move the mouse outside the godot editor.
4. Observe that you don't even need to move it fast for it to not wrap properly.

Expected correct result:
Mouse cursor wraps  - never leaves the Editor window - from right to left/left to right.

### Minimal reproduction project (MRP)

None, you need to change Editor Settings.
Repository: godot
Issue: App hangs on splash screen when running on iOS simulators
Labels: bug,platform:ios,topic:thirdparty,needs testing,topic:export

### Tested versions

4.3.stable.mono

### System information

Godot v4.3.stable.mono - macOS 14.6.1 - GLES3 (Compatibility) - Apple M2 - Apple M2 (8 Threads)

### Issue description

After exporting the project in Compatibility mode, running the generated Xcode project on the iPhone 13 (and iPhone 15) simulator causes the app to hang on the Godot splash screen. The following error occurs in libsystem_platform.dylib

Thread 4: EXC_BAD_ACCESS (code=2, address=0x1070d0000)

I have no problem running exports on an actual device but I really need to test on different screen sizes, particularly on devices where the safe area needs to be considered. I'm at the stage where my game is ready to be submitted for review and fixing any device specific issues would be far easier if I could use the simulators.

### Steps to reproduce

Reproducible with a minimal Godot project.
No code, just a single Node2D scene containing a ColorRect.

### Minimal reproduction project (MRP)

N/A
Repository: TypeScript
Issue: Move to file incorrectly adds import for type available in destination file
Labels: Bug

### 🔎 Search Terms

move to file self imports

### 🕗 Version & Regression Information

- This is the behavior in every version I tried
- I tried in 5.7.0-dev.20240826


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
// file _a.ts
export interface ISomething {
}
```
```ts
// file _b.ts
import { ISomething } from './a';

export function func(something: ISomething) {
}
```
Select `func` and move it to `_a.ts`
🐛 Observe the result:


### 🙁 Actual behavior

```ts
// file _a.ts
import { ISomething } from './a'; // <------------------ incorrect import from itself

export interface ISomething {

}
export function func(something: ISomething) {
}
```

### 🙂 Expected behavior

```ts
// file _a.ts
export interface ISomething {

}
export function func(something: ISomething) {
}
```

### Additional information about the issue

_No response_
Repository: ollama
Issue: Model whitelisting for generate endpoint
Labels: feature request

I would like to support the ability to whitelist models that are usable with the generate endpoint.

The model list should be provided via an env variable and be checked against before running the generate function.

With this feature, the admins will gain more control over the models that can used by auto coding, f.e.: [continue ](https://www.continue.dev/) or other services. High frequent request from those applications will lead to huge delays, if the wrong model is selected.
Repository: ui
Issue: [bug]: request to https://ui.shadcn.com/r/styles/index.json failed
Labels: bug

### Describe the bug

While trying to exec  `shadn@latest init`, the index.json is timing out:

```
npx shadcn@latest init
✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS.
✔ Validating import alias.


Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

request to https://ui.shadcn.com/r/styles/index.json failed, reason: connect ETIMEDOUT 76.76.21.164:443
```

I'm able to acccess the json via web browser:

```[
  {
    "name": "new-york",
    "label": "New York"
  },
  {
    "name": "default",
    "label": "Default"
  }
]
```


### Affected component/components

core

### How to reproduce

`npx shadcn@latest init`

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
macOS Sonoma
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Docs: Improve info on prelaunch tasks for debug configurations?
Labels: bug

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.91.1
- OS Version: Archlinux (rolling)

Steps to Reproduce:

The documentation around "attach" debug configurations and "preLaunchTask" is quite limited.

I want to debug a large python (fastapi) project with debugpy; and launching the project within the debugger takes over one minute. To speed up iteration, I want to just start the process, and after everything is loaded and initialized, `attach` the debugger to it - this brings down startup time to <10 sec. 

However I can't find good documentation on how to do this: I was able to set a preLaunchTask as:


```
    {
      "label": "Start Chat Servers",
      "type": "shell",
      "command": "poetry run python -Xfrozen_modules=off -m uvicorn mymodule:myapp",
      "options": {
        "cwd": "${workspaceFolder}/project",
        "env": {
          "DEBUG": "true"
        }
      },
      "problemMatcher": [],
      "isBackground": true
    }
  ]
```

And reference it in the debug config:

```
    {
      "name": "Chat Servers",
      "type": "debugpy",
      "request": "attach",
      "connect": {
        "host": "localhost",
        "port": 5678,
      },
      "preLaunchTask": "Start Chat Server",
      "justMyCode": false
    }
```

This "works", however I get the following error message: 
![image](https://github.com/user-attachments/assets/53f25b0e-463b-4c12-8f94-94a4a5040f73)

If I click on "debug anyway", it works as long as I gave enough time for the server to start and reach the point where we listen for the debugger. Otherwise, or if I click on "demembed my choice", it fails with a weird error: 

![image](https://github.com/user-attachments/assets/92ce7292-8c85-4eed-8b9b-06a918bb65e4)

I couldn't find any information on adding a timeout to the attach or on a way to wait for a specific event before trying to attach...
If it is possible to do this, maybe it would be good to add some info to the docs.
Repository: deno
Issue: Improve error message when TLS certificate is not trusted to suggest running with `DENO_TLS_CA_STORE=mozilla,system`
Labels: feat,cli,tls