sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: rust compiler suggests to add lifetime to macro: `#'static[...]`
Labels: A-diagnostics,T-compiler

### Code

https://github.com/Anatoly03/Netz/tree/bf8c6917b68c70cc0677b540402c4d64707670bc/util-parser

(The token stream generated by the broken macro is logged into the console.)

### Current output

```
error[E0106]: missing lifetime specifier
 --> util-parser/tests/whitespace.rs:5:5
  |
5 |     #[grammar(~)]
  |     ^ expected named lifetime parameter
  |
  = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from
  = note: this error originates in the attribute macro `grammar` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static`
  |
5 |     #'static [grammar(~)]
  |      +++++++
help: instead, you are more likely to want to return an owned value
  |
5 |     String
  |
```

### Desired output

```
  [expand macro code with broken lines displayed]

error[????]: could not compile macro `grammar` due to ... errors
```

### Rationale and extra context

![Image](https://github.com/user-attachments/assets/d0c8f218-9c5e-45ca-b113-cfcbbaee8f41)


### 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-apple-darwin
release: 1.81.0
LLVM version: 18.1.7

### Anything else?

_No response_
Repository: rust
Issue: ambiguous name when glob importing an enum into a block when variant has same name as enum
Labels: A-resolve,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.
-->

related: https://github.com/rust-lang/rust/issues/102855

I tried this code:

```rust
enum En {
    En
}

mod m {
    use super::En;
    const _ = {
        use En::*;
        1
    };
}
```

I expected to see this happen: exact path shadows glob import

Instead, this happened: compile error:
```
Compiling playground v0.0.1 (/playground)
error[[E0659]](https://doc.rust-lang.org/nightly/error_codes/E0659.html): `En` is ambiguous
 --> src/lib.rs:8:13
  |
8 |         use En::*;
  |             ^^ ambiguous name
  |
  = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
note: `En` could refer to the variant imported here
 --> src/lib.rs:8:13
  |
8 |         use En::*;
  |             ^^^^^
  = help: consider adding an explicit import of `En` to disambiguate
note: `En` could also refer to the enum imported here
 --> src/lib.rs:6:9
  |
6 |     use super::En;
  |         ^^^^^^^^^
  = help: use `self::En` to refer to this enum unambiguously

error: missing type for `const` item
 --> src/lib.rs:7:12
  |
7 |     const _ = {
  |            ^ help: provide a type for the constant: `: i32`

For more information about this error, try `rustc --explain E0659`.
error: could not compile `playground` (lib) due to 2 previous errors
```

### 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.
-->

`rustc --version --verbose`:
```
rustc 1.83.0-nightly (2bd1e894e 2024-09-26)
binary: rustc
commit-hash: 2bd1e894efde3b6be857ad345914a3b1cea51def
commit-date: 2024-09-26
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```
Repository: PowerToys
Issue: Daily copy, paste and text manipulation tasks
Labels: Needs-Triage

### Description of the new feature / enhancement

Hello, :)

_I apologize in advance if this is not the correct way to use this communication channel, as I am completely newbie to Github_

**I would like to suggest implementing a new feature:** quick and easy text manipulation shortcuts for the mouse.

This is a function that can optimize the productivity of all Windows users via Power Toys and those who need more accessibility features.

Just like the **[PopClip (MacOS)](https://www.popclip.app/)** and **[SnipDo (Windows)](https://snipdo-app.com/)** applications, it would be interesting if there was a feature which, after selecting text, quick action buttons would appear for tasks that we frequently and exhaustively do using keyboard shortcuts, such as example, CTRL+C , CTRL+V, CTRL+X, etc.

Currently, there is only one (freemium) app that does this on Windows: SnipDo. However, every month features are removed for monetization reasons (which there is nothing wrong with that). But, it would be interesting to have these same functions for free within Power Toys.

Furthermore, this feature could also be integrated into the advanced paste in future projects.

### Scenario when this would be used?

By every user. Every minute, hour and day.

### Supporting information

This is a small example of how this works through the SnipDo app:


![image](https://github.com/user-attachments/assets/9251dd19-79d4-4146-928f-c9d0419b7684)


After selecting any text, a small popup appears with shortcut options that we frequently use.
Repository: pytorch
Issue: Context manager to skip checks inside decompositions
Labels: triaged,oncall: pt2,module: dynamic shapes,module: decompositions

### 🚀 The feature, motivation and pitch

When calling a decomposition from another decomposition, we might be running checks with `torch._check` when we know that those checks are unnecessary. For eg: using `narrow` in `split_with_sizes` added about `15*N` checks for `N` number of splits, but none of them were necessary. Removing those checks made a good performance improvement as seen in https://github.com/pytorch/pytorch/pull/135728/files.

Does it make sense to have a context manager that makes `torch._check` a no-op?

cc @ezyang @chauhang @penguinwu @bobrenjc93 @SherlockNoMad @amjames 

### Alternatives

_No response_

### Additional context

_No response_
Repository: rust
Issue: rustdoc --json output format contains no doc comments
Labels: T-rustdoc,A-cross-crate-reexports,A-rustdoc-json,S-needs-repro,S-needs-info

What's the right way to invoke `rustdoc` so that it outputs in JSON format but also with doc comments?

I'm doing `cargo +nightly rustdoc -- --output-format json -Z unstable-options` and the resulting JSON file has `"docs": null` for all items! 😅

Please let me know how to tell rustdoc to include doc comments 🙂
Thanks 🙏
Repository: godot
Issue: More helpful error message for `Condition "!v.is_finite()" is true`
Labels: enhancement,topic:rendering,usability

### Tested versions

- Reproducible in: v4.3.stable (77dcf97d8)

### System information

Godot v4.3.stable (77dcf97d8) - Windows 10.0.22631 - GLES3 (Compatibility) - Intel(R) Iris(R) Xe Graphics (Intel Corporation; 32.0.101.5972) - 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 Threads)

### Issue description

Moving MeshInstance to an infinite or NaN coordinate causes this error

```
E 0:00:02:0077   instance_set_transform: Condition "!v.is_finite()" is true.
  <C++ Source>   servers/rendering/renderer_scene_cull.cpp:935 @ instance_set_transform()
```

That's great, but it's difficult to understand what does it mean. It would be better if error message read "Infinite coordinate provided to a mesh" or something like that so developers could more easily understand what happened and what do they need to look for in their code (i.e. divisions by zero)

### Steps to reproduce

1. Create a MeshInstance3D
2. Set mesh to Cube
3. Assign a new script to it
```gdscript
extends Node3D


func _ready() -> void:
	self.position.x = NAN
```

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Highlight outline jumps around on toggle visibility with flexible layout
Labels: bug,topic:gui

### Tested versions

Reproducible in 4.3-stable

### System information

Godot v4.3.stable - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) - AMD Ryzen 7 7700X 8-Core Processor (16 Threads)

### Issue description

When toggling the visibility of items in a flex layout, in a way that adjusts the size of the enveloping container, the outlines of the items (initially) appear in the wrong place 

### Steps to reproduce

Method A:
1. Adjust the 2D editor so the 4 Buttons are centered and big enough to see
2. shift+click all the buttons with text 'A'
3. In the Inspector, toggle CanvasItem>Visibility>visible twice

Method B:
1. Adjust the 2D editor so the 4 Buttons are centered and big enough to see
2. in the scene tree select all the buttons in the HBoxContainer
3. click the visibility icon twice

### Minimal reproduction project (MRP)

[MWE.zip](https://github.com/user-attachments/files/17215355/MWE.zip)
Repository: neovim
Issue: StatusLineNC, Folded, and CursorLine highlights are indistinguishable in default colorscheme
Labels: defaults

### Problem

This can make the UI confusing, and difficult to tell what is what at a glance, especially if you have a lot of windows open and/or folded lines.

### Steps to reproduce

Here's an example with the following highlights being displayed right next to each other

1. StatusLineNC
2. Folded
3. CursorLine

<img width="1018" alt="image" src="https://github.com/user-attachments/assets/841d9aee-ecbe-4a84-bbe2-be76a715076b">


### Expected behavior

Here is the same example where the highlights are different making it easier/quicker to tell what is what at a glance:

<img width="1018" alt="image" src="https://github.com/user-attachments/assets/f5ebd4fd-fd36-4690-8f19-919be4706034">


### Nvim version (nvim -v)

NVIM v0.11.0-dev-4005+g69553f7bf5-Homebrew

### Vim (not Nvim) behaves the same?

no, vim 9.1

### Operating system/version

macOS 14.5

### Terminal name/version

kitty 0.36.4

### $TERM environment variable

xterm-kitty

### Installation

homebrew
Repository: pytorch
Issue: FSDP2 equivalent of FSDP.summon_full_params contextmanager
Labels: oncall: distributed,module: fsdp

### 🚀 The feature, motivation and pitch

In FSDP1 there is the `FSDP.summon_full_params` [function](https://pytorch.org/docs/stable/fsdp.html#torch.distributed.fsdp.FullyShardedDataParallel.summon_full_params) for wrapping a module with a `contextmanager` within which all sharded parameters are automatically unsharded and modifications to the unsharded tensor are written back to the original shards. The FSDP2 documentation says to use the `DTensor` `full_tensor` API for this but `full_tensor` will only work on an individual tensor rather than recursively unsharding all parameters within a module. Are there plans for introducing a similar API for FSDP2? Or do you recommend any alternative approach?

### Alternatives

_No response_

### Additional context

_No response_

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @zhaojuanmao @mrshenli @rohan-varma @chauhang
Repository: rust
Issue: Tracking Issue for `inherent_str_constructors `
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

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

This is a tracking issue for inherent `str` constructors.

### Public API

* `str::from_utf8`
* `str::from_utf8_mut`
* `str::from_utf8_unchecked`
* `str::from_utf8_unchecked_mut`

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] ACP: https://github.com/rust-lang/libs-team/issues/398
- [ ] Implementation: #...
- [ ] 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: rust
Issue: importing an item into the module it was defined in is described as "multiple definitions"
Labels: A-diagnostics,T-compiler

### Code

```
pub struct St;
use St;
```

### Current output

```
error[E0255]: the name `St` is defined multiple times
 --> src/lib.rs:2:5
  |
1 | pub struct St;
  | -------------- previous definition of the type `St` here
2 | use St;
  |     ^^ `St` reimported here
  |
  = note: `St` must be defined only once in the type namespace of this module
help: you can use `as` to change the binding name of the import
  |
2 | use St as OtherSt;
  |        ++++++++++

warning: unused import: `St`
 --> src/lib.rs:2:5
  |
2 | use St;
  |     ^^
  |
  = note: `#[warn(unused_imports)]` on by default
```

### Desired output

```
error[E0255]: the name `St` is defined multiple times
 --> src/lib.rs:2:5
  |
1 | pub struct St;
  | -------------- previous definition of the type `St` here
2 | use St;
  |     ^^ `St` reimported here
  |
  = note: `St` must be defined only once in the type namespace of this module
help: remove the import
  |
2 | use St;
  | ------

warning: unused import: `St`
 --> src/lib.rs:2:5
  |
2 | use St;
  |     ^^
  |
  = note: `#[warn(unused_imports)]` on by default
```

### Rationale and extra context

_No response_

### Other cases

this should also be handled for circular reimports:

```rust
pub use m::St;
mod m {
    pub struct St;
    use crate::St;
}
```

### Rust Version

rustc 1.83.0-nightly (2bd1e894e 2024-09-26)
binary: rustc
commit-hash: 2bd1e894efde3b6be857ad345914a3b1cea51def
commit-date: 2024-09-26
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0


### Anything else?

_No response_
Repository: PowerToys
Issue: PowerToys control panel does not save any settings
Labels: Issue-Bug,Product-Settings,Product-FancyZones,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.84.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

It just says access denied. Same thing after running as admin.

### ✔️ Expected Behavior

Settings to save

### ❌ Actual Behavior

No setting seems to be saving, not just fancyzones, everything was not saving, had to edit the json file manually and it works.

### Other Software

_No response_
Repository: kubernetes
Issue: [SidecarContainers] Failed to get proper phase after the node reboot
Labels: kind/bug,priority/important-soon,sig/node,triage/accepted

### What happened?

If a pod has an init container with restartPolicy "Always" (sidecar), it may lose the pending phase after the node reboot and start the regular containers before initializing the init containers.

/sig node
/priority important-soon
/kind bug

This is similar to https://github.com/kubernetes/kubernetes/issues/126650, but separated as it only affects the pod with restartable init containers.

### What did you expect to happen?

After the node reboot, the remaining pod should start from the pending phase and run the init containers one by one to initialize.

### How can we reproduce it (as minimally and precisely as possible)?

1. Create and initialize the pod with an init container with "Always" container restart policy.
2. Restart the node.

### 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: tensorflow
Issue: Tf_lite fails to compile in v2.18.0-rc0 in Ubuntu
Labels: stat:awaiting tensorflower,type:build/install,comp:lite,2.17,2.18.rc

### Issue type

Build/Install

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.18.0-rc0

### Custom code

No

### OS platform and distribution

ubuntu 22.04, ubuntu 24.04

### Mobile device

_No response_

### Python version

3.10, 3.12

### Bazel version

6.5

### GCC/compiler version

_No response_

### CUDA/cuDNN version

-

### GPU model and memory

-

### Current behavior?

When follow the [normal instructions to build tf_lite](https://ai.google.dev/edge/litert/build/cmake_pip) as indicated, compilation fails, log is attached.

### Standalone code to reproduce the issue

```shell
Follow the normal instructions to build tf_lite as indicated here: https://ai.google.dev/edge/litert/build/cmake_pip

Compilation fails, log is attached.
```


### Relevant log output
Full log:
[ubuntu22.04.log](https://github.com/user-attachments/files/17216590/ubuntu22.04.log)
[ubuntu24.04.log](https://github.com/user-attachments/files/17216593/ubuntu24.04.log)


```
/usr/bin/ranlib libmicrokernels-prod.a
gmake[3]: Leaving directory '/tensorflow/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3.12/cmake_build'
[ 69%] Built target microkernels-prod
gmake[2]: Leaving directory '/tensorflow/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3.12/cmake_build'
gmake[1]: *** [CMakeFiles/Makefile2:1526: CMakeFiles/_pywrap_tensorflow_interpreter_wrapper.dir/rule] Error 2
gmake[1]: Leaving directory '/tensorflow/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3.12/cmake_build'
gmake: *** [Makefile:208: _pywrap_tensorflow_interpreter_wrapper] Error 2

make: *** [Makefile:72: docker-build] Error 2
make: Leaving directory '/home/----/Software/tensorflow-dir/tflite_runtime/tensorflow/tensorflow/lite/tools/pip_package'
```
Repository: tauri
Issue: [feat] [v2] [macOS] Move hidden files/folder out of DMG window's view
Labels: type: feature request,platform: macOS

### Describe the problem

This is a low priority request and is same as something discussed in electron-userland/electron-builder#1121. If users have `AppleShowAllFiles` on in Finder, the hidden files/folders in DMG window would show and be placed improperly as the following image shows.
<img width="656" alt="Screenshot 2024-10-02 04 26 49" src="https://github.com/user-attachments/assets/dcf7ccb9-bd52-4cb5-8401-d54f2f947a59">


### Describe the solution you'd like

The intuitive solution would be moving any file/folder with a name starting with a dot to a position out of DMG window by giving larger x value and y value than DMG window's width and height respectively. Electron did this by maintaining a list of hidden files/folders internally. I personally think it is good enough but I am not sure if anyone would want some customization in this. Feel free to share any use case of customization or any alternative solution.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: rust
Issue: Coverage information is wrong when using tracing
Labels: T-compiler,C-bug,A-proc-macros,A-code-coverage

So found an interesting thing when developing cargo-tarpaulin and confirmed it exists also with cargo-llvm-cov and using the raw llvm tools. When `#[tracing::instrument]` is added to a function the function body is not included in the coverage instrumentation. This doesn't happen with `#[tokio::main]` and I'm yet to create a more minimal reproduction with a less intense proc macro.

Project setup:

```
cargo new --lib tracing-instrument
cargo add tracing
```

In `src/lib.rs`

```rust
use tracing::instrument;

#[instrument]
fn instrumented_function() {
    println!("Hello");
}

#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn is_it_hit() {
        instrumented_function();
    }
}
```

If you run something like `cargo llvm-cov --html` on this project you'll see only `#[instrument]` is marked as covered. If we comment out `#[instrument]` then the function signature, body and closing brace are marked as covered regions of codes.

This suggests to me there's something a bit wrong with the llvm instrumentation setup and how it interacts with procedural macros.
Repository: TypeScript
Issue: JSDoc with @extends, type parameter and member expression gives wrong dts output
Labels: Bug,Help Wanted

### 🔎 Search Terms

jsdoc type parameter generics extends superclass template

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about JSDoc type parameters with `@extends`

I tried with TypeScript `5.0.0`, `5.6.2`, and `5.7.0-dev.20241001`.

### ⏯ Minimal repro link

I needed more than one file to reproduce, which I can't do on the playground. Here's a simple reproducer:

https://github.com/blutorange/issue-repro/tree/issue-typescript-missing-type-param

```
git clone https://github.com/blutorange/issue-repro
cd issue-repro
git checkout issue-typescript-missing-type-param
npm install
npm run build
```

Then open `dist/index.d.ts`.

### 💻 Code

```js
/**
 * @template {0|1|2} T
 * @extends {Scope.sub.Box<T>}
 */
export class MyComponent extends Scope.sub.Box {
    more() {
        return "foo";
    }
}
```


### 🙁 Actual behavior

The class in the `extends` clause is missing the type parameter. This is a compile error when you validate the `.d.ts` file.
 
```ts
declare const MyComponent_base: typeof import("./header.js").Box;
/**
 * @template {0|1|2} T
 * @extends {Scope.sub.Box<T>}
 */
export class MyComponent<T extends 0 | 1 | 2> extends MyComponent_base {
    constructor();
    more(): string;
}
export {};
```

### 🙂 Expected behavior

TypeScript should include the type parameter in the `extends` clause.

```ts
declare const MyComponent_base: typeof import("./header.js").Box;
/**
 * @template {0|1|2} T
 * @extends {Scope.sub.Box<T>}
 */
export class MyComponent<T extends 0 | 1 | 2> extends MyComponent_base<T> {
    constructor();
    more(): string;
}
export {};
```


### Additional information about the issue

Only seems to happen when the extends clause is a member expression where TS generate an intermediate `declare const ...`.

Fyi, I came across this issue while investigating how to setup a project for generating type declarations from js files for primefaces/primefaces#12500