sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: rustdoc-json: `impl dyn Trait` gets discarded
Labels: T-rustdoc,C-bug,A-rustdoc-json,A-trait-objects

For the following code:

```rust
pub trait T1 {
    fn number(&self) -> i32;
}

impl dyn T1 {
    pub fn number_plus_one(&self) {
        self.number() + 1
    }
}
```

generates

```json
{
  "format_version": 36,
  "includes_private": false,
  "index": {
    "0": {
      "attrs": [],
      "crate_id": 0,
      "deprecation": null,
      "docs": null,
      "id": 0,
      "inner": {"function": { ... }},
      "name": "number",
      "visibility": "default"
    },
    "1": {
      "attrs": [],
      "crate_id": 0,
      "deprecation": null,
      "docs": null,
      "id": 1,
      "inner": {
        "trait": {
          "bounds": [],
          "generics": {"params": [], "where_predicates": []},
          "implementations": [],
          "is_auto": false,
          "is_dyn_compatible": true,
          "is_unsafe": false,
          "items": [0]
        }
      },
      "name": "T1",
      "visibility": "public"
    },
    "2": {
      "attrs": [],
      "crate_id": 0,
      "deprecation": null,
      "docs": null,
      "id": 2,
      "inner": {"module": {"is_crate": true, "is_stripped": false, "items": [1]}},
      "name": "on_dyn_trait",
      "visibility": "public"
    }
  },
  "root": 2
}
```

([full](https://gist.github.com/aDotInTheVoid/d94786d8b58a6be9bbda6a3cde8f9252)).

There's nothing included for the `number_plus_one` method, but there should be.

The HTML backend get this right, so the releavent info is availible in `clean`:

![Image](https://github.com/user-attachments/assets/d4c3a64e-4bfd-4045-9139-e23bb4000519)

I'm not sure what's the best way to store this is in the format: Putting it into the `implementations` field seems wrong, as `impl dyn T1` isn't an implementation of `T1`, but an implementation **on** `dyn T1`. I'd love to hear people's thoughts on this.
Repository: godot
Issue: Corruption of .import ConfigFile settings when an external BoneMap was renamed or deleted.
Labels: bug,topic:core,topic:import,high priority,topic:3d

### Tested versions

- 4.3.stable
- All older versions of 4.x (crashes)

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3090 (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)

### Issue description

#93284 was merged as an emergency fix for 4.3. It avoids a crash, but does not prevent corruption of import settings or avoid import failures due to the same underlying issues.

In particular, this quote from the description should highlight why it is important that a bug still be open:
**i think all these issues also have another underlying issue to them, this just turns the crashes into error prints**

The following bugs were incorrectly closed as part of the fix:
* #90014
* #92940
* #84371

Therefore I'm opening this issue so that we can track the underlying problem and attempt to address it in a better way for 4.4.

Note that the underlying issue relates to `var_to_str()` and `ConfigFile` APIs and their mishandling of missing resources as well as lack of UID serialization, so I'm going to include this as a core issue since it is critical.

This issue caused by deleting referenced files from .import blocks making improvements to the advanced importer and material editing:
* #86430

![Image](https://github.com/user-attachments/assets/03cbeade-03e0-4645-b232-8c41eaddf039)


### Steps to reproduce

1. Import a 3D model with a Skeleton.
2. Create a bone map for it and right click it to save it externally.
3. Rename the external resource of the new bone map.
4. Attempt to open the advanced import dialog for the model.


### Minimal reproduction project (MRP)

https://github.com/godotengine/godot/files/14803641/bone_map_crash.zip
Repository: tauri
Issue: [bug] running `tauri android init` returns `NDK_HOME` environment variable isn't set, but the NDK is installed
Labels: type: bug,platform: macOS,status: needs triage,platform: Android

### Describe the bug

After following the [prerequisites](https://tauri.app/start/prerequisites/) doc to the letter, installing Android Studio and downloading all the latest SDKs and NDKs, I'm still getting this error when running `tauri android init`:

```
action request:  to initialize Android environment; Android support won't be usable until you
fix the issue below and re-run `tauri android init`!
    Have you installed the NDK? The `NDK_HOME` environment variable isn't set, and is
    required: environment variable not found
```

What can be causing this to KEEP happening? This results in Android Studio reporting `Error running 'app' Default Activity not found` after running `tauri android dev`

### Reproduction

_No response_

### Expected behavior

Tauri should be able to detect the installed NDK

### Full `tauri info` output

```text
action request:  to initialize Android environment; Android support won't be usable until you
fix the issue below and re-run `tauri android init`!
    Have you installed the NDK? The `NDK_HOME` environment variable isn't set, and is
    required: environment variable not found
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: MongoDB TLS connection still has problems
Labels: bug,tls,node compat

              I just updated “deno” to “deno-2.1.2” and found that this problem (https://github.com/denoland/deno/issues/26660) is still there.
![image](https://github.com/user-attachments/assets/7b906514-3e7b-4a95-a246-dd0f20cf68fe)
![image](https://github.com/user-attachments/assets/cd2ccb60-c95b-4d87-b2a2-f3c0ce8b9add)
MongodB log:
![image](https://github.com/user-attachments/assets/185eeded-c9e6-4fc1-a301-9e22d50755b2)

_Originally posted by @LP1994 in https://github.com/denoland/deno/issues/26660#issuecomment-2508845166_
Repository: rust
Issue: Tracking Issue for `breakpoint` feature (`core::arch::breakpoint`)
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(breakpoint)]`

This is a tracking issue for the `breakpoint` feature, which gates the `core::arch::breakpoint` function. This feature was approved in [ACP 491](https://github.com/rust-lang/libs-team/issues/491).

### Public API

```rust
// core::arch

/// Compiles to a target-specific software breakpoint instruction or equivalent.
///
/// (Long description elided.)
#[inline(always)]
pub fn breakpoint() {
    unsafe {
        core::intrinsics::breakpoint();
    }
}
```

### Steps / History

- [x] ACP: https://github.com/rust-lang/libs-team/issues/491
- [x] Implementation: https://github.com/rust-lang/rust/pull/133726
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: pytorch
Issue: Using torch.func with saved tensor hooks
Labels: module: autograd,triaged,module: functorch

### 🚀 The feature, motivation and pitch

Context

I am developing a generative model that requires analyzing input-output sensitivity through Jacobian computations. In scenarios like flow-matching and denoising diffusion models, using torch.func.jacrev leads to high memory consumption because the computation graph involves hundreds of network evaluations.

Problem

To reduce memory usage, gradient checkpointing via torch.utils.checkpoint is an ideal solution since individual update steps are independent. However, torch.func.jacrev currently does not support saved tensor hooks, which are essential for implementing gradient checkpointing. Attempting to use this combination results in the following error:

```
RuntimeError: torch.func.{grad, vjp, jacrev, hessian} don't yet support saved tensor hooks. Please open an issue with your use case.
```

Proposed Solution

Enhance torch.func.jacrev and related functions (grad, vjp, hessian) to support saved tensor hooks. This addition would enable the use of gradient checkpointing techniques to manage memory more efficiently during Jacobian computations.

Benefits

Memory Efficiency: Significantly reduces memory requirements for models that involve extensive Jacobian calculations.
Broader Applicability: Allows researchers to work with more complex models that were previously constrained by memory limitations.
Resource Optimization: Improves computational resource utilization, making it feasible to run larger experiments on existing hardware.

### Alternatives

Using a for loop over the individual 

### Additional context

_No response_

cc @ezyang @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7 @xmfan @zou3519 @Chillee @samdow @kshitij12345
Repository: angular
Issue: Skip Initial Entry Animation when Hydration Enabled
Labels: area: animations,needs reproduction,area: core,core: hydration

### Which @angular/* package(s) are relevant/related to the feature request?

animations

### Description

When hydration is enabled, the initial entry animation will not be played until hydration is complete, resulting in a very wierd visual effect, where the elements appear at their final position before they are animated.

### Proposed solution

Provide an option to skip the initial entry animations when hydration is enabled. A possible syntax might be:
```ts
provideClientHydration(withInitialAnimationSkipped())
```

### Alternatives considered

Alternatively, document this behavior as expected at angular.dev and provide viablae solutions.
See below for an example workaround:
```ts
@Component({
  host: { '[@.disabled]': '!stable()' },
})
export class AppComponent {
  #router = inject(Router);

  stable = toSignal(
    this.#router.events.pipe(
      pickType(NavigationEnd),
      first(),
      switchMap(() => new Promise((r) => setTimeout(r))),
      map(() => true),
      startWith(false),
    ),
    { requireSync: true },
  );
}

```
Repository: angular
Issue: `::ng-deep` becomes `:is()` with CSS files
Labels: area: core,core: stylesheets,core: CSS encapsulation

### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

Yes

### Description

In CSS file (not SCSS), when using `::ng-deep` the result is broken.


```css
pre {
    white-space: pre-wrap;

    ::ng-deep {
        h3 {
            margin: 0px;
            border-bottom: 1px solid;
            padding: 0 6px 6px;
        }

        .license {
            margin-right: 5px;
            font-size: 20px;
            text-align: right;
        }
    }
}
```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
**In build**


▲ [WARNING] 1 rules skipped due to selector errors:
  :is() -> Empty sub-selector


**In browser**


pre[_ngcontent-ng-c2840326293] {
    white-space:pre-wrap
}
:is()   h3[_ngcontent-ng-c2840326293] {
    margin:0;
    border-bottom:1px solid;
    padding:0 6px 6px
}
:is()   .license[_ngcontent-ng-c2840326293] {
    margin-right:5px;
    font-size:20px;
    text-align:right
}
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 19.0.2
Node: 20.11.1
Package Manager: npm 10.2.4
OS: linux x64

Angular: 19.0.1
... animations, cdk, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.2
@angular-devkit/build-angular   19.0.2
@angular-devkit/core            19.0.2 (cli-only)
@angular-devkit/schematics      19.0.2
@angular/cli                    19.0.2
@schematics/angular             19.0.2
rxjs                            7.8.1
typescript                      5.6.3
zone.js                         0.15.0
```

### Anything else?

_No response_
Repository: ant-design
Issue: The arrow position of the datePicker is incorrect
Labels: Inactive,improvement

### Reproduction link

[https://ant.design/components/date-picker-cn](https://ant.design/components/date-picker-cn)

### Steps to reproduce

Narrowing the width of your browser and clicking on the datepicker box will reveal the wrong arrow position

### What is expected?

Arrow position correct

### What is actually happening?

Arrow offset
![image](https://github.com/user-attachments/assets/5ebbfbd9-fd43-4474-a34b-31c7c9163898)


| Environment | Info |
| --- | --- |
| antd | 5.22.1 |
| React | 17 |
| System | windows 11 |
| Browser | edge 131.0.2903.70  |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: compiletest: normalization replacement strings don't support newlines
Labels: E-hard,C-enhancement,T-bootstrap,A-compiletest

>  It will affect every `normalize-` header, but since none of those currently have a `\n` in them, no other tests will be affected (other than the one I'm adding).
>
> There is currently no way to a new-line in the replacement string, I tried a bunch of things and just gave up and added this mini logic.

_Originally posted by @Urgau in https://github.com/rust-lang/rust/pull/133710#discussion_r1865295125_
Repository: tensorflow
Issue: XLA recompilation every time when shape changed on GPU
Labels: stat:awaiting tensorflower,type:support,comp:xla,TF 2.18

### Issue type

Support

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

binary

### TensorFlow version

tf2.18

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I have seen a lot of dynamic dim configurations in the OpenXLA repo. I am using TF GPU-XLA. How should I configure it so that recompilation is not triggered during GPU dynamic dim?

### Standalone code to reproduce the issue

```shell
@tf.function(input_signature=[tf.TensorSpec(shape=[2, None], dtype=tf.float32),
                              tf.TensorSpec(shape=[None, 2], dtype=tf.float32),
                              tf.TensorSpec(shape=[], dtype=tf.float32),],
             jit_compile=True)
def foo(x, y, z):
    exp = tf.add(x, z)
    abs = tf.sin(exp)
    add = tf.add(abs, tf.transpose(y, ))
    mm = tf.matmul(add, y)
    return mm

x = tf.ones([2, 3]).gpu()
y = tf.ones([3, 2]).gpu()
z = tf.ones([]).gpu()

out = foo(x, y, z) # Compile

x = tf.ones([2, 4]).gpu()
y = tf.ones([4, 2]).gpu()
z = tf.ones([]).gpu()

out = foo(x, y, z)  # Compile

x = tf.ones([2, 5]).gpu()
y = tf.ones([5, 2]).gpu()
z = tf.ones([]).gpu()

out = foo(x, y, z)  # Compile
```


### Relevant log output

_No response_
Repository: godot
Issue: Resize window bug in viewport mode with compatibility renderer
Labels: bug,topic:rendering

### Tested versions

Reproducible in Godot v4.3.stable (77dcf97d8)
No problems at Godot v3.5.stable

### System information

Godot v4.3.stable (77dcf97d8) - Windows 11 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4060 (NVIDIA; 32.0.15.6603) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads) - The system uses 2 monitors

### Issue description

At certain project settings, window resizing breaks and the screen goes black.

### Steps to reproduce

1) Set the renderer to Compatibility
2) Then in Projects Settings -> Display -> Window: 
Stretch -> Mode set to Viewport,
Size -> Mode set to Windowed,
Size -> Resizable set to True.
3) Next, start the project and try to resize the window.

The application screen will become black.

I also recorded a video demonstration:
https://youtu.be/Nw5Qs0URLH4

### Minimal reproduction project (MRP)

[Viewport Resize Bug.zip](https://github.com/user-attachments/files/17974252/Viewport.Resize.Bug.zip)
Repository: node
Issue: `Writable.write(buf, sourceOffset, sourceLength)`
Labels: stream,feature request

I want to add a `Writable.write(sourceBuf, sourceOffset, sourceLength)` API to `Writable` to get a bit of extra performance in the following case:

```js
writable.write(buf.subarray(offset, length))
```

The `subarray` call (particularly regarding allocating `Buffer`) can be quite slow and avoided in this API. Hence I would like to be able to do something like:

```js
writable.write(buf, offset, length)
```


I'm not sure how the API should look, though, or whether adding another signature to `write` would break anyone.

Internally stream implementation would need to explicitly support this by implementing something like `_writeSlice` and `_writevSlice`
Repository: angular
Issue: Missing instructions in Routing Overview tutorial
Labels: area: docs

### Describe the problem that you experienced

In the first step of the tutorial, the instructions to import and making changes to ./app/routes.ts appears missing.
![Image](https://github.com/user-attachments/assets/72d6283e-62b9-491d-9c74-4f39cddb0218)


### Enter the URL of the topic with the problem

https://angular.dev/tutorials/learn-angular/12-enable-routing

### Describe what you were looking for in the documentation

The instructions for importing `Routes` from `@angular/router` and the exporting of the routes property should be mentioned instead of the empty text. 

### Describe the actions that led you to experience the problem

Follow the Learn Angular tutorials

### Describe what you want to experience that would fix the problem

The steps to import the dependencies and export routes property should be clearly mentioned in Step 1

### Add a screenshot if that helps illustrate the problem

![Image](https://github.com/user-attachments/assets/09303c21-db18-4047-aeb0-30c3c80f9009)


### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: rust
Issue: Tracking issue for release notes of #131713: Stabilize `const_maybe_uninit_write`
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #131713.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Const stabilized APIs
- [`MaybeUninit::write`](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#method.write)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @tgross35, @dtolnay -- origin issue/PR authors and assignees for starting to draft text
Repository: pytorch
Issue: RuntimeError: quantized::conv2d_relu (ONEDNN): data type of input should be QUint8.
Labels: module: onnx,oncall: quantization

### 🐛 Describe the bug

I am using PyTorch's quantification feature and I want to obtain an onnx model of type int8. Here are my main lines of code, but an error occurred
`backend_config = get_qnnpack_backend_config()`
`qconfig_mapping = _get_symmetric_qnnpack_qat_qconfig_mapping()`
`dummy_input = torch.randn(1, 3, 224, 224)`
`model_prepared = quantize_fx.prepare_qat_fx(quantized_model, qconfig_mapping=qconfig_mapping, example_inputs=dummy_input, backend_config=backend_config)`
`model_quantized = quantize_fx.convert_fx(model_prepared, qconfig_mapping=qconfig_mapping, backend_config=backend_config)`
`torch.onnx.export(model_quantized .to('cpu'), example_inputs, 'tmp.onnx')`

### Versions

onnx 1.12.0
torch 2.1.0


cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @msaroufim
Repository: PowerToys
Issue: roman numerals support in quick accent
Labels: Idea-Enhancement,Needs-Triage,Product-Quick Accent

### Description of the new feature / enhancement

In Unicode, Roman numerals have their corresponding characters, and in many cases Roman numerals are used. So can they be added to Quick Accent. Otherwise using Roman numerals would be so cumbersome that I would have to use something like III (3 capitalized I's), which troubles me a lot in format :cry:.

### Scenario when this would be used?

In cases when the roman numerals are needed.

### Supporting information

Roman numerals in Unicode are between U+2160 to U+217F
Repository: ant-design
Issue: Carousel 走马灯需要支持受控模式
Labels: 💡 Feature Request,Inactive,🧶 Low Priority

### What problem does this feature solve?

受控模式获得以下功能：
1. 指定默认显示的面板，而不是默认显示第一个
2. 可以控制面板切换的逻辑

### What does the proposed API look like?

新增 value 和 onChange 属性

```tsx
const [index, setIndex] = useState(0)
<Carousel index={1} onChange={setIndex}>
...
</Carousel>
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Tracking issue for release notes of #133631: Add new target for supporting Neutrino QNX 7.1 with `io-socket` netwo…
Labels: T-compiler,relnotes,O-unix,O-neutrino,relnotes-tracking-issue


This issue tracks the release notes text for #133631.

### Steps

- [x] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Compiler
- [Add new Tier 3 targets `{aarch64-unknown,x86_64-pc}-nto-qnx710_iosock` for supporting Neutrino QNX 7.1 with `io-socket` network stack.](https://github.com/rust-lang/rust/pull/133631)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @flba-eb, @pnkfelix -- origin issue/PR authors and assignees for starting to draft text