sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [A11y] Identify Flutter semantics performance issues.
Labels: a: accessibility,from: performance template,P1,customer: castaway,team-framework,triaged-framework

### Steps to reproduce

tldr: the goal is to find out how to improve the performance when turning on semantics and scope out work to improve that.


When turning on semantics in Flutter, the app may suffer performance issue due to semantics tree compilation.

We used to only turn on semantics conditionally when needed, but we started to get use cases where we want to turn on by default. For example

1. web platform can't tell whether a assistive technology is running
2. web SEO uses semantics tree to index
3. android app crawl also use accessibilitynodes to crawl the app.

There the things we should do now is to figure out
1. Whether the performance is really bad enough to prevent us from doing that
4. if the answer to 1 is yes, What causes the performance issue
5. if the answer to 1 is yes, What needs to be done to make it run faster.

### related issues

Scrolling jank https://github.com/flutter/flutter/issues/61193
Repository: rust
Issue: recommending the wrong Arbitrary
Labels: A-diagnostics,T-compiler,S-needs-repro

### Code

```Rust
// sorry, can't replicate this one with just rust, it needs multiple crates.
// specifically, proptest with the derive feature disabled,
// and arbitrary with the derive feature enabled.
// if you import the proptest prelude then try to derive Arbitrary,
// it will suggest using the wrong derive macro
```


### Current output

```Shell
error: cannot find derive macro `Arbitrary` in this scope
   --> src/lib.rs:163:11
    |
163 |     #[derive(Arbitrary, Debug)]
    |              ^^^^^^^^^
    |
note: `Arbitrary` is imported here, but it is only a trait, without a derive macro
   --> src/lib.rs:161:6
    |
161 |     use proptest::prelude::*;
    |         ^^^^^^^^^^^^^^^^^^^^
help: consider importing this derive macro
    |
159 +     use arbitrary::Arbitrary;
    |
```


### Desired output

```Shell
error: cannot find derive macro `Arbitrary` in this scope
   --> src/lib.rs:163:11
    |
163 |     #[derive(Arbitrary, Debug)]
    |              ^^^^^^^^^
    |
note: `Arbitrary` is imported here, but it is only a trait, without a derive macro
   --> src/lib.rs:161:6
    |
161 |     use proptest::prelude::*;
    |         ^^^^^^^^^^^^^^^^^^^^
help: consider enabling the "derive" feature on the proptest crate
```


### Rationale and extra context

I think the best way of handling this is not suggesting a derive macro with the same name as a trait if that macro has the same *path* as another trait.

### Rust Version

```Shell
rustc 1.80.0-nightly (debd22da6 2024-05-29)
binary: rustc
commit-hash: debd22da66cfa97c74040ebf68e420672ac8560e
commit-date: 2024-05-29
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.6
```


### Anything else?

_No response_
Repository: pytorch
Issue: [RFC][pipelining] PipelineStage should let user control send/recv endpoints
Labels: oncall: distributed,triaged,module: pipelining

Currently the PipelineStage will assume that forward outputs are sent to the 'next_stage_rank' which is determined automatically as pp_rank + 1 % pp_size.  This assumption holds for simple and looped schedules, but breaks for 'V' schedules (e.g. Zero-bubble 'ZBV' as pictured [here](https://huggingface.co/spaces/sail/zero-bubble-pipeline-parallellism)

The proposal would require PipelineStage to accept a different destination for forward outputs than the modular next pp rank.  The forward outputs could instead stay on the same rank (for the first chunk on the last pp_rank), or go to the previous pp_rank (for the second chunk on the last N-1 pp_ranks).

**Option 1**
possibly the easiest short term option-

add new optional arguments to PipelineStage that configures which rank to use for each of the inputs and outputs of that stage.

input_args_rank: Optional[Union[int, Tuple[int, …]]]=None,
output_args_rank: Optional[Union[int, Tuple[int, …]]]=None,

if specified, these arguments must match up with the corresponding input_args and output_args and indicate which pp_rank those args either send to are recv from.

if unspecified, we default to ‘send to next rank’ and ‘recv from prev rank’ as we currently do

**Option 2**
might be better directionally but also more work

Fully consolidate the implementations of PipelineStage and _PipelineStage, and genericize the pipe_info struct to strip out graph stuff and make the information about arguments and endpoints explicit.  Let the tracer frontend generate a pipe_info by processing the graph, but let users also manually construct a pipe_info and configure a PipelineStage from it.  In this way, we can support any pattern of connectivity (including skip-connections).

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @yf225 @chauhang @d4l3k
Repository: tensorflow
Issue: What is preventing TF to use GPU when used in native windows?
Labels: stat:awaiting tensorflower,type:build/install,subtype:windows,TF 2.16

We keep getting told, repeatedly that TF no longer "supports" using GPU on versions `>2.10`. However, the reason why this is so, is nowhere to be found. 

**Can someone from the TF community please explain what is the problem with TF having GPU support for native windows environment?**

* https://github.com/tensorflow/tensorflow/issues/64881
* https://github.com/tensorflow/tensorflow/issues/63362
* https://www.tensorflow.org/install/pip#windows-native

Finally, since the wording is "supported" (and it was supported before), how can we go about implementing this support on our own? 

What are the python package requirements, and native windows C/C++/C# compiler requirements?
Repository: stable-diffusion-webui
Issue: [Feature Request]: Since the SD3 effect is so poor, can we support the use of HunyuanDIT?
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Support the inference use of the HunyuanDIT model.

### Proposed workflow

Able to perform t2i

### Additional information

Since the SD3 effect is so poor, can we support the use of HunyuanDIT?
https://www.reddit.com/r/StableDiffusion/comments/1dehbpo/sd3_vs_hunyuandit/#lightbox

https://huggingface.co/Tencent-Hunyuan/HunyuanDiT
https://github.com/Tencent/HunyuanDiT
https://dit.hunyuan.tencent.com/

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/131428984/9eeb36e6-41a3-4a4b-8e1e-882cef34de87)
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/131428984/af2496a2-295b-495c-8bc6-b8e32acb14a6)
Repository: PowerToys
Issue: FancyZone activated automatically without holding Shift when dragging window for the first time after logging via RDP after update
Labels: Issue-Bug,Product-FancyZones,Needs-Repro,Needs-Triage

### Microsoft PowerToys version

0.81.1

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. Enable "Hold Shift key to activate areas when dragging windows" (I'm using Chinese version so translation may not be 100% correct)
2. Login the account via RDP, then drag any window (only hold left button), FancyZone is activated automaticaly.
3. After the first time, this won't happen anymore, it behaves normally.

Logfile exported:
[PowerToysReport_2024-06-14-09-27-31.zip](https://github.com/user-attachments/files/15830555/PowerToysReport_2024-06-14-09-27-31.zip)

Settings:
![2024-06-14_095448](https://github.com/microsoft/PowerToys/assets/48206733/1daf9f87-c5f7-4a02-af31-c453947e8d4c)


### ✔️ Expected Behavior

FancyZone only triggered when holding Shift

### ❌ Actual Behavior

FancyZone is triggered without holding Shift although it is set to do so.
This was not the case before I update, but I couldn't recall the version before the update.

### Other Software

_No response_
Repository: godot
Issue: Moving A Script That Extends Resources Lead To Missing Dependecy
Labels: bug,topic:editor

### Tested versions

Reproducible in 4.2.2

### System information

Windows 11, Godot v4.2.2 Forward Renderer

### Issue description

When moving a folder or a script that extends Resources, it could result in missing dependencies.

### Steps to reproduce

I was able to reproduced this issue using my dialogue system, which relies on resources. Based on the reproduction project, follow these steps: 

1. Open the project.
2. Move the dialogue_res_scripts folder to a different location (e.g., dialogue_resources folder).
3. Reload the project.

Video Guide

https://github.com/godotengine/godot/assets/45304248/91c54af3-6a5a-4d39-91d7-ad1f88aaf180



### Minimal reproduction project (MRP)

[ResMissingDependecy.zip](https://github.com/user-attachments/files/15830627/ResMissingDependecy.zip)
Repository: next.js
Issue: navigating back from multiple intercepted route breaks routing
Labels: bug,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/roksui/my-nextagram

### To Reproduce

1. Clone the repository and checkout to the master branch.
2. Start the application in dev mode using `npm run dev`.
3. Click on `View my notifications` link.
4. Click on `View photo 1`.
5. Do a browser refresh (pressing F5).
6. Press the browser back button (once or twice).
7. The url changes to the previous route but the page does not.

### Current vs. Expected behavior

When I press the back button in step 6 above, I expected the browser to navigate back to the intercepted route for `/notifications`. However, only the URL changes and the page stays the same, showing the intercepted route of `/photos`.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 32545
  Available CPU cores: 16
Binaries:
  Node: 18.17.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.0-canary.29 // Latest available version is detected (15.0.0-canary.29).
  eslint-config-next: 15.0.0-canary.29
  react: 19.0.0-rc-f994737d14-20240522
  react-dom: 19.0.0-rc-f994737d14-20240522
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

Basically my use case is to open two modals A and B, where modal B is opened from modal A. I have it structured as:
```
app
  @modal
    (.)notifications
    (.)photos
  notifications
    page.tsx
  photos
    page.tsx
```
I could not find any documentation on implementing multiple intercepted routes, so not sure if this structure is the way to go.

With this structure, the intercepting works with no problems with the two modals. Also, refreshing on the first intercepting route and navigating back works too. However, refreshing on the second intercepting route and navigating back causes an issue.
Repository: kubernetes
Issue: Distinguish PDB error separately in eviction API
Labels: sig/api-machinery,kind/feature,help wanted,triage/accepted

### What would you like to be added?

Currently in eviction API, when violating PDB, we'll have two common errors, see https://github.com/kubernetes/kubernetes/blob/eb6840928df59bf8203b1eda839ccd3da68fb37d/pkg/registry/core/pod/storage/eviction.go#L423-L432

We can't easily distinguish them with other `forbidden` or `tooManyRequests` errors, we do have different messages but that's not an appropriate criteria for judgement.

When detecting `update conflicts`, we have a conflict reason for it, maybe we can do the same thing here like **A Forbidden status code with different Reasons**, have no idea whether this is acceptable. but at least it's feasible because we maintain the status reasons ourself in kubernetes.

/kind api-machineary

### Why is this needed?

It would be great if we can tell them when calling eviction API, like in https://github.com/kubernetes/enhancements/pull/4329#discussion_r1637925556, this can be an important metric for users to know the reason why Pods can't be evicted, because of PDB constraints or others.
Repository: godot
Issue: interaction with GitHub desktop: indirect resource changes not detected
Labels: topic:editor,needs testing

### Tested versions

v4.2.stable.official [46dc27791]

### System information

Godot v4.2.stable - Windows 10.0.22631 - GLES3 (Compatibility) - Intel(R) Iris(R) Plus Graphics (Intel Corporation; 27.20.100.9664) - Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 Threads)

### Issue description

when you extend a custom resource type, then modify the resource's script so that exported variables are changed, GitHub desktop only detects change to the script and not the resources

### Steps to reproduce

1. make a script with this code:
```
extends Resource
class_name Foo
@export var color : Color = Color.BLACK
@export var weight : int = 1
```
2. create a resource file extending Foo.
3. set the resource's `color` and `weight` to arbitrary non-default value
4. commit and push to GitHub via GitHub desktop
5. delete `@export var color : Color = Color.BLACK` in the script for Foo
6. you should see that GitHub desktop detects a change in the script, but not in the resource
7. if you change the `weight` in the resource, you should see that GitHub desktop now detects both the removal of the color attribute in the resource file as well as the change in the weight attribute

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: Inappropriate `unused_parens` for inline `const` inside `vec!`/macros
Labels: A-lints,A-macros,T-compiler,C-bug,D-incorrect,F-inline_const,S-has-mcve,L-unused_parens

https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Weird.20interaction.20between.20vec!.5B.5D.20macro.20and.20inline.20const

In this example, the inline `const` must be wrapped in parentheses, in order to work inside `vec!` under editions <2024:

```rust
fn main() {
    // Works fine, no warning.
    let _: [Vec<String>; 10] = [const { vec![] }; 10];
    // Works fine, no warning.
    let _: Vec<Vec<String>> = vec![(const { vec![] })];

    // Works, but warns about unnecessary parentheses.
    let _: Vec<Vec<String>> = vec![(const { vec![] }); 10]; // <=== THIS

    // These fail on stable79/beta80/nightly81 with edition 2021.
    // They work on nightly81 with edition 2024.
    let _: Vec<Vec<String>> = vec![const { vec![] }];
    let _: Vec<Vec<String>> = vec![const { vec![] }; 10];
}
```

[(playground)](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=4d3e1e8c99e8d64a8a2b336b0f4c5353)

However, notice that in the case of `vec![(const { vec![] }); 10]`, the compiler accepts the code but warns that the parentheses are unnecessary:

```text
warning: unnecessary parentheses around function argument
 --> src/main.rs:8:36
  |
8 |     let _: Vec<Vec<String>> = vec![(const { vec![] }); 10];
  |                                    ^                ^
  |
  = note: `#[warn(unused_parens)]` on by default
help: remove these parentheses
  |
8 -     let _: Vec<Vec<String>> = vec![(const { vec![] }); 10];
8 +     let _: Vec<Vec<String>> = vec![const { vec![] }; 10];
  |
```

The warning is incorrect, because removing the parentheses would result in an error under edition <2024.

(The `vec![(const { vec![] })]` case correctly reports no warning.)
Repository: rust
Issue: Inline `const` expression inside `vec!`/macros should suggest adding parentheses under edition <2024
Labels: A-diagnostics,A-macros,T-compiler,A-suggestion-diagnostics,D-newcomer-roadblock,F-inline_const,S-has-mcve

### Code

```Rust
fn main() {
    // Works fine, no warning.
    let _: [Vec<String>; 10] = [const { vec![] }; 10];
    // Works fine, no warning.
    let _: Vec<Vec<String>> = vec![(const { vec![] })];

    // Works, but warns about unnecessary parentheses.
    let _: Vec<Vec<String>> = vec![(const { vec![] }); 10];

    // These fail on stable79/beta80/nightly81 with edition 2021.
    // They work on nightly81 with edition 2024.
    let _: Vec<Vec<String>> = vec![const { vec![] }];
    let _: Vec<Vec<String>> = vec![const { vec![] }; 10];
}
```


### Current output

```Shell
error: no rules expected the token `const`
  --> src/main.rs:12:36
   |
12 |     let _: Vec<Vec<String>> = vec![const { vec![] }];
   |                                    ^^^^^ no rules expected this token in macro call
   |
   = note: while trying to match end of macro

error: no rules expected the token `const`
  --> src/main.rs:13:36
   |
13 |     let _: Vec<Vec<String>> = vec![const { vec![] }; 10];
   |                                    ^^^^^ no rules expected this token in macro call
   |
   = note: while trying to match end of macro
```


### Desired output

```Shell
help: consider surrounding the const expression with parentheses
   |
12 -     let _: Vec<Vec<String>> = vec![const { vec![] }];
12 +     let _: Vec<Vec<String>> = vec![(const { vec![] })];
   |
```


### Rationale and extra context

For compatibility reasons, macros under edition <2024 do not treat `const` as the start of an `expr`, so a layer of parentheses is needed to convince the macro to treat inline-const as an expression.

### Other cases

_No response_

### Rust Version

```Shell
(Stable Rust 1.79.0 on playground.)
```


### Anything else?

https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Weird.20interaction.20between.20vec!.5B.5D.20macro.20and.20inline.20const
Repository: ollama
Issue: Easy troubleshooting for Windows internal networks - known as "Connection refused" issue 
Labels: feature request

There is a very general issue with the sub networks that comes from the Automatically created networks in Windows:

if you have installed docker installed - you need to try to use as host address: **host.docker.internal**
if you have WSL installed and ollama on the Windows host - we need to use the IP that windows assigned IP for vEthernet(WSL) so WSL can find it - **172.X.X.X** 
if we use ollama on the WSL we need to use **127.0.0.1** to access it from the Windows host.

In any case we need to find Where ollama is "announced" by 0.0.0.0 

Is there a way from the ollama Windows app - lets say as it is to indicate how ollama can be accessed so it will enable fast troubleshooting.

What I mean is, would it be possible to include indication in the taskbar icon to have that information easily?

 For example something like this:
![image](https://github.com/ollama/ollama/assets/126105457/f45f1f14-1890-4aff-8dc3-d8f8a5584779)

I believe that would be really useful
Repository: TypeScript
Issue: Inverted union type narrowing was broken in 4.9
Labels: Bug,Help Wanted

### 🔎 Search Terms

"union type", "narrowing", "inverted", "4.9"

### 🕗 Version & Regression Information

- This changed between versions 4.8.4 and 4.9.5 (probably caused by https://github.com/microsoft/TypeScript/pull/50397?)

### ⏯ Playground Link

[Playground link](https://www.typescriptlang.org/play/?ts=4.9.5#code/JYOwLgpgTgZghgYwgAgGIHt3IN7JpgLmQGcwpQBzAbmQF8Aoe0SWRFAITih2QCMuipciGp1GzaPCTJOALx79ZgspRoN6MAK4gEYYOhDIAtgE9U23fpAAKUAAdNYIhiwAfGV2Tu5AShz1kQOQEA1JkYGI5ZABeZAByRTjww3tHKgCgkJAwiM5uWIyg5AB6YoSuJNBkhzAaUuQAFQALCOQAd3QoAGtiZDAsEC4odDbkAAN+KDH2pohDMk0UOBAAE2RBqGHRsfx0aaqwWeQIABtiFF4T9AQuwqCAQly4eQAyF+R76zjdypSQGp8dWKjRavQ63V6-XWQxG40m0zas3mUEWfEcyBW6AgvRA6DA0M2sJ2mH28yOp3OfCuNzuJwg+IAHsphNQ7sAYMhbJFnn5sHdAgyYtVHAA6RTpIq0Y5nFDszlPKC8-nIQWxVJgMVcCVBKUUlB8oqBeoASUMABYRQAOEVm5DLNYQLgnYDQAA043V+xxMLaEDWULGLjGypN5pFAE4RQBWO2rZAnOAsd1jT3hb2E33+rCBzBeTnWFx5vJ+d4AJQgISgKwAPAAiRS193aLq4togAB8PmDhpVQvVIt22sCDFoQA)

### 💻 Code

```ts
interface Foo { foo: string; }

interface Bar { bar: string; }

interface Baz { baz: string; }

function myFunction(input: Foo | Bar | Baz) {
    const isBaz = 'baz' in input;
    const isBar = 
      //'bar' in input; // This works to narrow `bar` when true and narrow `foo` in the else block
      !('foo' in input) && !isBaz; // This works to narrow `bar` when true but does not narrow `foo` in the else block
    let x: string;
    if (isBaz) {
      x = input.baz;
    } else if (isBar) {
      x = input.bar;
    } else {
      // In 4.8.4 and earlier, `input` is narrowed to `Foo`
      // In 4.9.5 and later, `input` is narrowed to `Foo | ((Foo | Bar) & Record<"baz", unknown>)`
      x = input.foo;
    }
}
```


### 🙁 Actual behavior

In 4.9.5 and later, in the else block, `input.foo` incorrectly narrows and errors

### 🙂 Expected behavior

In 4.8.4 and earlier, in the else block, `input.foo` correctly narrows

### Additional information about the issue

_No response_
Repository: go
Issue: proposal: net: export listenerBacklog
Labels: Proposal

### Proposal Details

The `listenerBacklog` function returns a cached value of the ~~optimal~~ maximum permitted listener backlog on the current system, obtained in platform-specific ways. This is useful for user code that makes direct `listen(2)` syscalls and then calls `net.FileListener` to create a `net.Listener`.

Since the function signature is unlikely to change in the future, and we already [had it exempted from the linkname restriction](https://github.com/golang/go/issues/67401#issuecomment-2126175774), I propose we add:

```go
// MaxListenerBacklog returns the maximum permitted listener backlog value on the current system.
// The return value may be used as the backlog argument to the listen(2) syscall.
func MaxListenerBacklog() int
```
Repository: deno
Issue: thread 'main' panicked at runtime\worker.rs:701:7
Labels: bug,windows,compile,node compat

**NestJs**

Platform: windows11 x64
Version: 1.44.2

run **`deno run --watch -A src/main.ts`** success
![image](https://github.com/denoland/deno/assets/101572433/cd144570-9915-4111-935a-67fb70c11e9d)

but run **`deno compile --output dist/main --target x86_64-pc-windows-msvc src/main.ts`**
run `main.exe` failed

error message:

thread 'main' panicked at runtime\worker.rs:701:7:
Bootstrap exception: TypeError: testEnabled is not a function
    at init (ext:deno_node/internal/util/debuglog.ts:51:15)
    at debug (ext:deno_node/internal/util/debuglog.ts:54:5)
    at logger (ext:deno_node/internal/util/debuglog.ts:69:29)
    at readableAddChunk (ext:deno_node/_stream.mjs:2797:7)
    at Readable.push (ext:deno_node/_stream.mjs:2791:14)
    at initStdin (ext:deno_node/_process/streams.mjs:185:13)
    at Object.internals.__bootstrapNodeProcess (node:process:652:22)
    at initialize (ext:deno_node/02_init.js:34:15)
    at bootstrapMainRuntime (ext:runtime_main/js/99_main.js:873:7)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at C:\a\deno\deno\runtime\tokio_util.rs:103:36:
called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(1), ...)
thread 'main' panicked at ext\io\lib.rs:131:38:
called `Result::unwrap()` on an `Err` value: Os { code: 50, kind: Uncategorized, message: "The request is not supported。" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at C:\a\deno\deno\runtime\tokio_util.rs:103:36:
called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(1), ...)