sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `E0277` Emitted Twice
Labels: A-diagnostics,A-trait-system,T-compiler,D-verbose

### Code

```Rust
fn main() {}

trait Foo {
    type Output;
}

fn baz<I>(x: &<I as Foo>::Output) {}
```


### Current output

```Shell
error[E0277]: the trait bound `I: Foo` is not satisfied
  --> test.rs:23:15
   |
23 | fn baz<I>(x: &<I as Foo>::Output) {}
   |               ^^^^^^^^^^^^^^^^^^ the trait `Foo` is not implemented for `I`
   |
help: consider restricting type parameter `I`
   |
23 | fn baz<I: Foo>(x: &<I as Foo>::Output) {}
   |         +++++

error[E0277]: the trait bound `I: Foo` is not satisfied
  --> test.rs:23:35
   |
23 | fn baz<I>(x: &<I as Foo>::Output) {}
   |                                   ^^ the trait `Foo` is not implemented for `I`
   |
help: consider restricting type parameter `I`
   |
23 | fn baz<I: Foo>(x: &<I as Foo>::Output) {}
   |         +++++

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0277`.
```


### Desired output

```Shell
error[E0277]: the trait bound `I: Foo` is not satisfied
 --> <source>:7:15
  |
7 | fn baz<I>(x: &<I as Foo>::Output) {}
  |               ^^^^^^^^^^^^^^^^^^ the trait `Foo` is not implemented for `I`
  |
help: consider restricting type parameter `I`
  |
7 | fn baz<I: Foo>(x: &<I as Foo>::Output) {}
  |         +++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
```

### Bisect
searched nightlies: from nightly-2024-02-01 to nightly-2024-03-16
regressed nightly: nightly-2024-02-15
searched commit range: https://github.com/rust-lang/rust/compare/a84bb95a1f65bfe25038f188763a18e096a86ab2...ee9c7c940c07d8b67c9a6b2ec930db70dcd23a46
regressed commit: https://github.com/rust-lang/rust/commit/ee9c7c940c07d8b67c9a6b2ec930db70dcd23a46 (PR: https://github.com/rust-lang/rust/pull/120847)

<details>
<summary>bisected with <a href='https://github.com/rust-lang/cargo-bisect-rustc'>cargo-bisect-rustc</a> v0.6.8</summary>


Host triple: x86_64-unknown-linux-gnu
Reproduce with:
```bash
cargo bisect-rustc --prompt --start=1.77.0 --end=1.78.0 
```
</details>

### Rust Version

```Shell
rustc 1.80.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.80.0-dev
LLVM version: 18.1.6
```
Repository: flutter
Issue: [ios][platform_view]Use CALayer directly (rather than UIView) as the clip mask
Labels: platform-ios,a: platform-views,P2,team-ios,triaged-ios

### Use case

UIView comes with overhead unrelated to rendering (e.g. hit testing). As experimented [in this design doc](https://docs.google.com/document/d/1TqG_N4GK_qctuk73Gk3zOdAiILUrwMqxoCMgroK_AeA/edit?resourcekey=0-jUiidfzIS642ngG2w9vSUA&tab=t.0), there can be non-trivial performance improvement. 

Decoupling this from the [software rendering work](https://github.com/flutter/engine/pull/53072) allows us to 
(1) measure the improvement separately for a better understanding
(2) land the software rendering PR sooner

### Proposal

`UIView::mask` likely just calls `CALayer::mask` API. We should directly use CALayer to avoid extra overhead comes with UIView.
Repository: pytorch
Issue: Add option for custom ops to automatically get a FakeTensor kernel (during static shapes)
Labels: triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

@jansel suggested this. If the user didn't register a FakeTensor kernel, we could:
1. generate zero-filled inputs from the FakeTensor information
2. run the operator with real Tensor inputs
3. take the output Tensors and convert them back to FakeTensor

The motivation for this is that sometimes people have a long number of pybind'ed kernels that they want to use with torch.compile and writing FakeTensor kernels (meta kernels) is a pain.

This is actually what the FakeTensor fallback does for built-in (aten/prim) operators. This was the previous default behavior for custom ops, but I turned it off because we were getting segfaults and we decided that we wanted to be more explicit.

Possible things we can do:
- add an option to do the zero-filled meta thing to the new custom ops constructor. I am a bit hesitant to add this because (1) it only works for static shapes, if you want dynamic shapes you need to write a FakeTensor kernel anyways and (2) people cargo cult a lot, they can cargo cult themselves into a segfault this way. We'd have to see if we can raise a good error message here.
- do nothing

Thoughts?

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: kubernetes
Issue: SVM RV Semantics: assert that xline RV semantics match etcd
Labels: sig/api-machinery,triage/accepted

Ref - https://github.com/kubernetes/kubernetes/issues/124641#issuecomment-2089440065

/assign nilekhc
/triage accepted
/sig api-machinery
Repository: next.js
Issue: NextJS 14 HMR Tailwind CSS reloading not working
Labels: bug

### Link to the code that reproduces this issue

https://github.com/krishnerkar/next-intercepting-routes-demo

### To Reproduce

1. Use the example next intercepting routes demo (originally based on Next 13)
2. Update to NextJS 14 (I personally tested 14.2.3 and 14.0.0 and had the same bug on both)
3. Change `/app/@modal/(..)product` to `/app/@modal/(.)product` or `/app/@modal/(...)product` (have to fix path on Next 14)
4. Add `w-full` to `ProductDialogDescription` in `app/@modal/(...)product/[id]/page.tsx`
5. Launch application
6. Try changing this width to `w-2/12` or anything else and notice it won't hot reload the proper width.

### Current vs. Expected behavior

I expected the new CSS class to be applied on hot reload, like it did in NextJS 13. However, the class seems to not be loaded and therefore not applied.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000
Binaries:
  Node: 20.13.0
  npm: 10.5.2
  Yarn: 1.22.18
  pnpm: 9.1.0
Relevant Packages:
  next: 14.0.0
  eslint-config-next: 13.3.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.0.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: vscode
Issue: Back button in the web issue report view
Labels: feature-request,issue-reporter

Testing #213597

It would be nice to include a back or escape button in the issue report window. When operating in full-screen mode, it can be confusing as the report command opens in a new tab, rather than the same one where the command was invoked.

<img width="1792" alt="Screenshot 2024-05-28 at 3 49 09 PM" src="https://github.com/microsoft/vscode/assets/17892325/e1df8528-cf80-4d05-bf47-df3350d7694f">
Repository: pytorch
Issue: `flake8: noqa` disables flake8 linter for the whole file and it's not obvious
Labels: module: lint,triaged,actionable

For example,  test/dynamo/test_misc.py has `flake8: noqa` on line 7285, and it actually completely disables flake8 for the whole file.

Another example, torch/quantization/fx/utils.py has `flake8: noqa: F401`, but it actually again disables flake8 completely, not just rule F401.

Also I believe ruff respects the comment, so ruff is also disabled.

We should audit and fix the current usages, and maybe add a linter to complain about new `flake8: noqa` comments, as it masks real issues.
Repository: transformers
Issue: Caching Past Key values of any length for Vision LLM's
Labels: Feature request,Generation

### Feature request

Allowing passing past key values during the forward pass of more than one token similar to the text large language models. 

### Motivation

According to the documentation [here](https://huggingface.co/docs/transformers/en/model_doc/llava_next#transformers.LlavaNextForConditionalGeneration.forward.past_key_values) one could in theory pass past key values of the prompt to speed up the forward pass. However, I think that the cached forward pass only happens when the input_ids has **only** one new token as described in the condition [here](https://github.com/huggingface/transformers/blob/573565e35a5cc68f6cfb6337f5a93753ab16c65b/src/transformers/models/llava_next/modeling_llava_next.py#L816). Changes to this making it consistent with the text LLMs (thanks for that) would be highly appreciated.

### Your contribution

If you can give me any pointers on how I can realign cache, create the attention masks, etc., It would also be very helpful
Repository: godot
Issue: GraphNode slots don't account for rotation
Labels: bug,topic:gui

### Tested versions

Reproducible in v4.3.dev6.official [89850d553], 4.2.2.stable.official [15073afe3]

### System information

Godot v4.3.dev6 - Windows 10.0.19045 - Vulkan (Forward+)

### Issue description

If a ``GraphNode`` has any kind of rotation in its transform, the slots will behave as if the ``GraphNode`` was not rotated at all, and you will only be able to interact with them from the positions they would have if the ``GraphNode`` was not rotated, despite the slots appearing to be visually rotated. In the example below, the output slots cannot even be interacted with as the ``GraphNode`` itself covers them.

![Godot_v4 3-dev6_win64_7nrnaBT5Rq](https://github.com/godotengine/godot/assets/88390729/6e130b19-53c7-4bfa-a4fe-bc950da0e695)


### Steps to reproduce

* Create a scene with ``GraphEdit`` as the top-level node
* Add a ``GraphNode``
* Add ``Control`` child nodes to the ``GraphNode``
* Enable at least one slot
* Set the rotation in ``GraphNode`` to any number other than 0
* Test the scene and attempt to drag a connection from one of the slots

### Minimal reproduction project (MRP)

[graphnode_rotation.zip](https://github.com/godotengine/godot/files/15476793/graphnode_rotation.zip)
Repository: pytorch
Issue: torch.export.export() throws out an error when dealing weighttying model. 
Labels: oncall: export

### 🐛 Describe the bug


```python
import torch
from torch import nn
import torch.nn.functional as F

class NN_TiedByPassing(nn.Module):
    def __init__(self):
        super().__init__()
        self.encoder = `nn.Linear(5,5,bias=False)
    def forward(self, X):
        encoded_feats = self.encoder(X)
        Y = F.linear(encoded_feats, self.encoder.weight.t())
        return Y

net = NN_TiedByPassing()
exported_program = torch.export.export(net, (torch.ones(1,5),))
``` 
The jit trace could trace the NN_TiedByPassing object but export could not. 
The error message is shown as follow: 
<img width="659" alt="image" src="https://github.com/pytorch/pytorch/assets/96632308/446bfc1d-b0f0-485f-bf21-c04698183698">


### Versions

PyTorch version: 2.3.0+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Enterprise
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect
Libc version: N/A

Python version: 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22621-SP0
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture=9
CurrentClockSpeed=2301
DeviceID=CPU0
Family=107
L2CacheSize=3072
L2CacheSpeed=
Manufacturer=AuthenticAMD
MaxClockSpeed=2301
Name=AMD Ryzen 5 PRO 5650U with Radeon Graphics
ProcessorType=3
Revision=20480

Versions of relevant libraries:
[pip3] numpy==1.26.2
[pip3] onnx==1.15.0
[pip3] onnxruntime==1.16.3
[pip3] torch==2.3.0
[conda] Could not collect

cc @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: flutter
Issue: Release builds can make the (master channel) Flutter build dashboard tree red
Labels: team-infra,P2,triaged-infra

What happened?

1. the internal google roll team created a new flutter/flutter branch, named [flutter-3.23-candidate.10](https://github.com/flutter/flutter/tree/flutter-3.23-candidate.10)
2. Step 1 also triggered a corresponding [branch](https://flutter.googlesource.com/recipes/+/refs/heads/flutter-3.23-candidate.10) to be created on the recipes repo, which then triggered a recipes bundle job to be kicked off to upload the recipe to CIPD ([build](https://ci.chromium.org/ui/p/flutter/builders/prod/recipes-bundler/b8746659936919381953/infra))
3. Step 1 also triggered set of release builds, in dart-internal, under the Linux flutter_release_builder ([build](https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Linux%20flutter_release_builder/625/infra))
4. A Linux flutter_release_builder job from step 3 tried to schedule a Linux docs_publish build with the flutter-3.23-candidate.10 bundle of the recipes BEFORE step 2 had finished (race condition), and thus failed ([swarming task](https://chrome-swarming.appspot.com/task?id=69d9f4bc065fb510&o=true&w=true))
5. The build dashboard detected this release build failure as part of its check for post-submit builds on the master channel, and thus determined that the tree should be red (even though this builder does not appear in flutter/flutter's .ci.yaml, AND that it was for a release branch)
6. The PR https://github.com/flutter/flutter/pull/149198 is manually merged, which immediately leads to the tree becoming green (why?)

Root causes:

1. Creating a new release candidate branch should not trigger release builds (internally tracked as https://b/340303879)
2. Should we need to trigger release builds as soon as an RC branch is created, the build should not start *until* the recipe bundle has been uploaded (how?)
3. There is a bug where Cocoon interprets the build result from a release build as affecting the framework master channel.
Repository: godot
Issue: Putting Godot editor in fullscreen stops game window from opening in fullscreen
Labels: discussion,topic:porting

### Tested versions

- Reproducible in: 4.3.dev6 [89850d553], 3.6.beta5 [2a347ab86]

### System information

Godot v4.3.dev6 - macOS 14.1.1 - Vulkan (Forward+) - integrated Apple M1 - Apple M1 (8 Threads)

### Issue description

Setting the game window to Fullscreen or Exclusive Fullscreen doesn't run the window in fullscreen if the Godot editor itself is in fullscreen. The attached video shows this in action in 4.3.dev6.

I also tested this on a computer running Fedora Linux Workstation 40 with GNOME and Wayland, and couldn't reproduce the bug there.

https://github.com/godotengine/godot/assets/99846997/260d39af-1ef7-4e6d-a73f-618e52148d03



### Steps to reproduce

1. Create a new project
2. Set the game window to run in Fullscreen or Exclusive Fullscreen
3. Put the Godot editor in fullscreen
4. Run the project

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Accessing nonexistent properties on inner classes doesn't raise UNSAFE_PROPERTY_ACCESS
Labels: bug,topic:gdscript

### Tested versions

- Reproducible in 4.2 stable

### System information

Godot v4.2.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 (NVIDIA; 31.0.15.3699) - AMD Ryzen 9 5900X 12-Core Processor (24 Threads)

### Issue description

The last two lines of this should raise `UNSAFE_PROPERTY_ACCESS` when the associated preference is set, but they don't:

```gdscript
class Foo:
	pass

func do_thing_with_new_foo() -> void:
	var foo = Foo.new()
	foo.nonexistent_property = 1
	print(foo.other_nonexistent_property)
```


### Steps to reproduce

I'm using VSCode. `UNSAFE_PROPERTY_ACCESS` is properly raised as a squiggly red underline on named/global classes, but not on inner classes.

### Minimal reproduction project (MRP)

N/A
Repository: TypeScript
Issue: TypeScript emits d.ts file that is invalid for complex mapped type.
Labels: Bug

### 🔎 Search Terms

d.ts emit type error

### 🕗 Version & Regression Information

This is a compile error when consuming a d.ts file emitting by the same version and configuration of TypeScript
This in 3.5.1, 4.0.5, 5.4.5 and 5.5.0-dev.20240528, but NOT in 3.3.3

### ⏯ Playground Link

https://www.typescriptlang.org/play/?module=1&ts=5.4.5&ssl=11&ssc=1&pln=1&pc=1#code/KYDwDg9gTgLgBAMwK4DsDGMCWEVwIYAmeYMAoikgLYA8AKuVXKDMCgQM5wBKwa0B1djCiYUAcwA0cISPEA+OQAoAUAEo4Ab2UBIGAE8wwOAAU8sAIxwAvJp3aA2sagRDsPXFFwA1sD0QEcPQUlAC6AFxwiupWcoEMlI7OrvohOgC+ANw6fChCiHgY0HoA8kjwNlHWsVra2lDAMEhQuIoADPicqF4oEADuuHic+ob++YVQJWVwAGQmZjDmqvbtg3BdPf0d3r6jQVQhlelZdQ1NuAgFMEWlMFlpykA

### 💻 Code

```ts
export function adaptEnum<TEnum extends Record<string, string>>(
) {
	type Part1 = {
		[Property in keyof TEnum]: () => TEnum[Property]
	};
	const factoryOut = () => {
		return (0 as unknown as typeof factoryOut & Part1)[0 as unknown as keyof TEnum]() 
	};
	return factoryOut;
}
```

### 🙁 Actual behavior

Emits:

```typescript
export declare function adaptEnum<TEnum extends Record<string, string>>(): () => TEnum[string] | TEnum[number] | TEnum[symbol];
```

Which Errors:
`Type 'number' cannot be used to index type 'TEnum'.(2536)`

### 🙂 Expected behavior

I expect TypeScript to either error when trying to emit a d.ts file, or generate a valid d.ts file it can consume without error.

### Additional information about the issue

This issue report is derived from minimizing the same code that produced https://github.com/microsoft/TypeScript/issues/56718 (which is now fixed) and is similar to that issue. The same workaround I have from that case still works, so this isn't blocking anything except removing that workaround.
Repository: vscode
Issue: Weird rendering on undo after format
Labels: bug,notebook-format

Testing #213608

![image](https://github.com/microsoft/vscode/assets/3840081/e0a769c4-07de-47e7-a90c-86ec1fc11ba9)
Repository: vscode
Issue: Need a way to get the notebook JSON to send to black
Labels: under-discussion,notebook-format,notebook-code-actions

Testing #213608

Currently all we get is NotebookDocument. When cells are run that is an edit, and format on save is triggered. This means that we will need access to the JSON that VS Code uses to serialize the notebook. `black` either takes the on disk path or JSON to format, same is the case with `ruff`. without the current unsaved JSON, the formatting will delete the output.
Repository: vscode
Issue: Linux: "Open Folder" shows a "Select Folder" dropdown that seems a no-op
Labels: upstream,linux,polish,electron,native-file-dialog

Testing #213763

See bottom right corner:

![image](https://github.com/microsoft/vscode/assets/900690/0462ce9e-4541-44d1-a03c-78f6be62d358)

That does not exist in stable, not sure what its for.
Repository: deno
Issue: Perf: `mocha` runs slow in Deno compared to Node
Labels: perf,node compat

Noticed that running the [`preact-render-to-string`](https://github.com/preactjs/preact-render-to-string) test suite is slower in Deno (1s) compared to Node (75ms).

https://github.com/denoland/deno/assets/1062408/3ba6eff7-3039-487f-81f0-d9815e102807

## Steps to reproduce

1. Clone https://github.com/preactjs/preact-render-to-string
2. Run `cd preact-render-to-string`
3. Run `npm i`
4. Run `DENO_FUTURE=1 deno task test:mocha`

Recording a profile with samply reveals that half the time is spent polling in Tokio.

<img width="1800" alt="Screenshot 2024-05-29 at 06 47 55" src="https://github.com/denoland/deno/assets/1062408/a3ee80ca-67e7-4b3f-a21c-a742c3e4cfaa">


Version: Deno 1.43.6
Repository: ollama
Issue: always fail to push models
Labels: bug,networking

### What is the issue?

I have tried many times

```
pushing 6d1c7eba2686...   0% ▕     ▏ 1.2 MB/ 74 GB                  
Error: max retries exceeded: http status 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>cloudflare</center>
</body>
</html>
```

### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

1.38
Repository: deno
Issue: Missing indentation for named JSDoc examples
Labels: bug,lsp

Relevant: https://github.com/denoland/deno/pull/23927

Version: Deno 1.43.6

Given the following JSDoc:

```ts
/**
 * @example
 * ```ts
 * fn1(
 *     "item"
 * )
 * ```
 */
declare function fn1(arg: string): void

/**
 * @example Name
 * ```ts
 * fn2(
 *     "item"
 * )
 * ```
 */
declare function fn2(arg: string): void
```

JSDoc output for `fn1` has the expected indentation, whereas `fn2` lacks the expected leading indentation before `"item"`.

![image](https://github.com/denoland/deno/assets/26078826/49a94169-ab8a-4c7b-8b11-30748677dc24)
Repository: rust
Issue: Inconsistent recursive fn call elimination
Labels: A-LLVM,T-compiler,C-bug,F-explicit_tail_calls

I tried this code:

```rust
#[inline(never)]
#[no_mangle]
const fn deep(n: usize) {
    match n {
        0 => (),
        _ => deep(n - 1),
    }
}

#[inline(always)]
const fn inf() -> ! {
    inf()
}

fn main() {
    deep(usize::MAX);
    println!("✅");
    inf();
}
```

I expected to see this happen: prints `"✅"` fast and successfully, then hangs in an infinite loop.

Instead, this happened: prints `"✅"` fast and panics with `stderr`:
```
   Compiling playground v0.0.1 (/playground)
    Finished `release` profile [optimized] target(s) in 0.38s
     Running `target/release/playground`

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
```

It seems commenting-out the attributes is no-op here.

### Meta

https://play.rust-lang.org/?version=nightly&mode=release&edition=2021&gist=ed0941cd328e49d8737fdff01cd4a4aa

`rustc --version --verbose`:
```
1.80.0-nightly

(2024-05-28 da159eb331b27df52818)
```

<details><summary>Backtrace</summary>
<p>

```
<no diff>
```

</p>
</details>

Apologies in advance, if this issue is a dupe. I tried my best to find similar ones