sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [bug] iOS LaunchScreen storyboard ignored
Labels: type: bug,status: needs triage

### Describe the bug

```
warning: “View Controller“ is unreachable because it has no entry points, and no identifier for runtime access via -[UIStoryboard instantiateViewControllerWithIdentifier:].
```

Getting this warning when initializing and running (dev + release) my tauri v2 app. Any changes to the LaunchScreen.storyboard are ignored.

### Reproduction

1. Add labels or any other static info to the LaunchScreen storyboard in the xcode project
2. Build the app, pay attention to the startup
3. In the short time when launch story board should be visible one can only see the white screen

### Expected behavior

Changes to the story board should be picked up in debug and release builds.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 15.1.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.83.0 (90b35a623 2024-11-26)
    ✔ cargo: 1.83.0 (5ffbef321 2024-10-29)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.12.2
    - yarn: 4.4.1
    - npm: 10.5.0

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.0.0-beta.11 (outdated, latest: 2.2.0)
    - @tauri-apps/cli : 2.1.0 (outdated, latest: 2.2.7)

[-] Plugins
    - tauri-plugin-fs 🦀: 2.2.0
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-log 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#83b65072695477a595026fe3b035e2f669fc188b (2.2.0)
    - @tauri-apps/plugin-log : 2.0.0-rc.1 (outdated, latest: 2.2.0)
    - tauri-plugin-shell 🦀: 2.2.0
    - @tauri-apps/plugin-shell : 2.2.0
    - tauri-plugin-dialog 🦀: 2.2.0
    - @tauri-apps/plugin-dialog : not installed!
    - tauri-plugin-updater 🦀: 2.3.0
    - @tauri-apps/plugin-updater : 2.0.0 (outdated, latest: 2.3.1)
    - tauri-plugin-store 🦀: 2.2.0
    - @tauri-apps/plugin-store : 2.2.0
    - tauri-plugin-process 🦀: 2.2.0
    - @tauri-apps/plugin-process : 2.2.0
    - tauri-plugin-os 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#83b65072695477a595026fe3b035e2f669fc188b (2.2.0)
    - @tauri-apps/plugin-os : 2.0.0-beta.3 (outdated, latest: 2.2.0)
    - tauri-plugin-positioner 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#83b65072695477a595026fe3b035e2f669fc188b (2.2.0)
    - @tauri-apps/plugin-positioner : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: SolidJS
    - bundler: Vite

[-] iOS
    - Developer Teams: Snowstorm Inc. (ID: FXX28NQXMK), Timur Amirov (ID: C8A8ALV8K5)
```

### Stack trace

```text

```

### Additional context

Easiest way to fix is to add `initialViewController="Y6W-OH-hqX"` to the storyboard template.
Repository: vscode
Issue: Editor GPU: Scrolling through long comment causes noticeable lag
Labels: bug,editor-gpu

From https://github.com/microsoft/vscode/issues/221145#issuecomment-2612075061

https://github.com/paritytech/polkadot-sdk/blob/e9393a9afc3b33cc2d01b7820a8f186434196758/substrate/frame/nis/src/lib.rs#L1-L75
Repository: kubernetes
Issue: [Flaking Test] [sig-network] LoadBalancers ExternalTrafficPolicy: Local [Feature:LoadBalancer] [Slow] should only target nodes with endpoints
Labels: sig/network,kind/flake,needs-triage

### Which jobs are flaking?

master-informing
- gce-master-scale-correctness

### Which tests are flaking?


Kubernetes e2e suite: [It] [sig-network] LoadBalancers ExternalTrafficPolicy: Local [Feature:LoadBalancer] [Slow] should only target nodes with endpoints. 
[Prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-scale-correctness/1883560971318857728)
[Triage](https://storage.googleapis.com/k8s-triage/index.html?test=should%20only%20target%20nodes%20with%20endpoints)

### Since when has it been flaking?

- [Jan 26, 10:31 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-scale-correctness/1883560971318857728)

### Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness

### Reason for failure (if possible)

```
{ failed [FAILED] timed out waiting for service "external-local-nodes" to have a load balancer: context deadline exceeded
In [It] at: k8s.io/kubernetes/test/e2e/network/loadbalancer.go:1094 @ 01/26/25 18:39:43.152
}
```

### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig network
cc: @kubernetes/release-team-release-signal
Repository: transformers
Issue: ForSequenceClassification models assume right-padding
Labels: bug

We have `ForSequenceClassification` variants for several of our CLMs, and this line is commonly copied between them:

`sequence_lengths = torch.eq(input_ids, self.config.pad_token_id).int().argmax(-1) - 1`

However, this line assumes **right-padding**, because it treats the length of the sequence as the number of tokens before the first pad token (when multiple values have the max value, then `argmax` returns the first index with that value).

If we have left-padding instead, then this will break because it will compute a sequence length of -1. This was reported as a bug in Gemma [here](https://github.com/huggingface/transformers/issues/30004), but it likely affects other models as well.

`tokenizer.padding_side` is probably not accessible to the model, because it is stored in `tokenizer_config` and not `config`. As a result, I think the solution here will have to be rewriting this code so that it can handle either left- or right-padding.
Repository: kubernetes
Issue: hack/local-up-cluster.sh fails with emulation version needs to be greater or equal to 1.31
Labels: kind/bug,sig/testing,sig/release,needs-triage

### What happened?

Tried to create local Kubernetes cluster using hack/local-up-cluster.sh script but the api-server fails to come up.

### What did you expect to happen?

Successfully create a local Kubernetes cluster.

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

1. Clone the Kubernetes repository
```
https://github.com/kubernetes/kubernetes.git
```

2. Run the local cluster create script
```
./hack/local-up-cluster.sh
```
[Install the missing dependencies reported by the script]

3. Error

```
2025/01/27 20:08:25 [INFO] received CSR
2025/01/27 20:08:25 [INFO] generating key: rsa-2048
2025/01/27 20:08:25 [INFO] encoded CSR
2025/01/27 20:08:25 [INFO] signed certificate with serial number xxxxxxxxx
Waiting for apiserver to come up
!!! [0127 20:09:29] Timed out waiting for apiserver:  to answer at https://127.0.0.1:6443/healthz; tried 60 waiting 1 between each
check apiserver logs: /tmp/kube-apiserver.log
Cleaning up...
```

4. API server Log
```
$ cat /tmp/kube-apiserver.log
I0127 20:08:28.017237   63752 flags.go:64] FLAG: --v="3"
I0127 20:08:28.017240   63752 flags.go:64] FLAG: --version="false"
I0127 20:08:28.017243   63752 flags.go:64] FLAG: --vmodule=""
I0127 20:08:28.017246   63752 flags.go:64] FLAG: --watch-cache="true"
I0127 20:08:28.017248   63752 flags.go:64] FLAG: --watch-cache-sizes="[]"
W0127 20:08:28.017278   63752 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
E0127 20:08:28.017662   63752 run.go:72] "command failed" err="emulation version needs to be greater or equal to 1.31, got 1.23.0-alpha.1.24689"
```

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.31.2
Kustomize Version: v5.4.2
The connection to the server 127.0.0.1:62205 was refused - did you specify the right host or port?
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On mac
Darwin KMacBook-Pro.local 24.1.0 Darwin Kernel Version 24.1.0
</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>
containerd
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: go
Issue: runtime: reportZombies throws "found pointer to free object" in sweeper
Labels: NeedsInvestigation,Tools,gopls/telemetry-wins,BugReport

```
#!stacks
"reportZombies:+34" && "runtime.goexit"
```
Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).

This stack `Ytavxw` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2025-01-25.json):

- `crash/crash`
- [`runtime.throw:+9`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/panic.go;l=1067)
- [`runtime.(*mspan).reportZombies:+34`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=890)
- [`runtime.(*sweepLocked).sweep:+160`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=658)
- [`runtime.sweepone:+37`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=389)
- [`runtime.bgsweep:+28`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=298)
- [`runtime.gcenable.gowrap1:+0`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgc.go;l=204)
- `runtime.goexit:+0`
```
golang.org/x/tools/gopls@v0.17.1 go1.23.4 linux/amd64 vscode (1)
```

@prattmic
Repository: rust
Issue: Suggested fix for "cannot find macro `...` in this scope" does not compile
Labels: C-bug,needs-triage

I tried this code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a095133990477eb48c9b42343e5593f4

I expected to see this happen: Using a suggestion "just works".

Instead, this happened: Unexpected and even more confusing error message caused because of #98291.

### Meta

Tested on playground with `1.84.0` (stable) and `1.86.0-nightly (2025-01-26 f85c6de55206dbee5ffe)`.
Repository: pytorch
Issue: "AssertionError: Guard check failed" on PyTorch nightlies after 2025-01-22 when running torchao tests
Labels: high priority,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Running the following command introduces an assertion error on recent versions of PyTorch nightlies:

```
// run a test in torchao repo
// test source code: https://github.com/pytorch/ao/blob/main/test/prototype/test_smoothquant.py

> pytest test/prototype/test_smoothquant.py -s -x

...
        if not output_graph.export:
            if not self.guard_manager.check(output_graph.local_scope):
                reasons = get_guard_fail_reason_helper(
                    self.guard_manager,  # type: ignore[arg-type]
                    output_graph.local_scope,
                    CompileContext.current_compile_id(),
                )
>               raise AssertionError(f"Guard check failed: {reasons}")
E               AssertionError: Guard check failed: 0/0: ___check_metadata_139942440334048_c0/0                      
E               
E               
E               You can suppress this exception and fall back to eager by setting:
E                   import torch._dynamo
E                   torch._dynamo.config.suppress_errors = True
```

Full output: https://gist.github.com/vkuzo/b50ac59aa0936fd072250d7544aaa2a9

The nightly from `20250122` does not have this failure, but the nightlies from `20250123` and after do.

### Versions

https://gist.github.com/vkuzo/ddcaa43948a96cf63e58fb71fbdcbf68

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @amjames
Repository: vscode
Issue: Editor GPU: Ghost text is regular foreground color
Labels: bug,editor-gpu

Example:

![Image](https://github.com/user-attachments/assets/f725ea7e-47cf-444b-a220-7ecf662dd0c7)
Repository: flutter
Issue: Investigate what android builds/tests can be faster by not installing xcode
Labels: team,platform-android,team-android,fyi-infra

"[Contributor] has upstreamed a change to our recipes that will allow mac targets in our .ci.yaml configs to opt out of installing Xcode (obviously provided your test doesn't require it) with a property" 

https://flutter-review.googlesource.com/c/recipes/+/62500 


https://groups.google.com/a/google.com/g/flutter-team/c/fKuizPWBI58/m/Z8IQT248EgAJ?utm_medium=email&utm_source=footer
Repository: rust
Issue: "expected opaque type, found ..." when trait impl with type_alias_impl_trait
Labels: C-bug,needs-triage

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

I tried this code:

```rust
type U32Iter = impl Iterator<Item = u32>;

struct Foo {
    iter: U32Iter,
}

impl From<u32> for Foo {
    fn from(value: u32) -> Self {
        Self {
            iter: std::iter::once(value),
        }
    }
}
```

I expected to see this happen: Compiles

Instead, this happened:
```
12 |             iter: std::iter::once(value),
   |                   ^^^^^^^^^^^^^^^^^^^^^^ expected opaque type, found `Once<u32>`
```

### 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.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.84.0
LLVM version: 19.1.5
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
   Compiling smth v0.1.0 (/tmp/smth)
error[E0308]: mismatched types
  --> src/main.rs:12:19
   |
3  | type U32Iter = impl Iterator<Item = u32>;
   |                ------------------------- the expected opaque type
...
12 |             iter: std::iter::once(value),
   |                   ^^^^^^^^^^^^^^^^^^^^^^ expected opaque type, found `Once<u32>`
   |
   = note: expected opaque type `U32Iter`
                   found struct `std::iter::Once<u32>`
note: this item must have the opaque type in its signature in order to be able to register hidden types
  --> src/main.rs:10:8
   |
10 |     fn from(value: u32) -> Self {
   |        ^^^^

For more information about this error, try `rustc --explain E0308`.
error: could not compile `smth` (bin "smth") due to 1 previous error
```

</p>
</details>
Repository: godot
Issue: Objects whose `_init()` takes arguments fail to be decoded when sent over RPC
Labels: discussion,documentation,topic:network

### Tested versions

4.4dev7

### System information

Godot v4.4.dev7 - Windows 10 (build 19045) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 32.0.15.6636) - AMD Ryzen 7 5800X 8-Core Processor (8 threads)

### Issue description

Let's say you have a `PlayerData` `Object` that for convenience defines a constructor:

```gdscript
class_name PlayerData extends Object

var position: Vector3
var rotation: Vector3

func _init(position_: Vector3, rotation_: Vector3) -> void:
    self.position = position_
    self.rotation = rotation_
```

When you try to send a `PlayerData` over RPC, the receiving side fails to decode it because it doesn't know what to put into these arguments.

### Steps to reproduce

Download the MRP. Open Debug > Customize Run Instances and configure it as shown here:

![Image](https://github.com/user-attachments/assets/111ce9e1-a9f9-4da9-8219-c00135ddc71a)

Run the project. Observe the errors.


### Minimal reproduction project (MRP)

[netbug.zip](https://github.com/user-attachments/files/18561226/netbug.zip)
Repository: go
Issue: runtime: spurious SEGV in package initializer (darwin/amd64)
Labels: NeedsInvestigation,Tools,compiler/runtime

```
#!watchflakes
default <- pkg == "golang.org/x/tools/go/analysis/passes/loopclosure" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8724618820959648753)):

    panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x4d0537d]
    
    goroutine 1 [running]:
    go/types.init.2()
    	/Users/swarming/.swarming/w/ir/x/w/goroot/src/go/types/universe.go:282 +0x1dd
    FAIL	golang.org/x/tools/go/analysis/passes/loopclosure	0.030s


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: while_loop fails to export when strict=False
Labels: oncall: pt2,export-triaged,oncall: export

Repro:
Apply the following patch, then run `python test/export/test_export.py -k  test_while_loop_simple` and the test fails when `strict=False`
```
diff --git a/test/export/test_export.py b/test/export/test_export.py
index 9b070141ac3..22096a68a1b 100755
--- a/test/export/test_export.py
+++ b/test/export/test_export.py
@@ -66,6 +66,8 @@ from torch.testing._internal.common_utils import (
     IS_MACOS,
     IS_SANDCASTLE,
     IS_WINDOWS,
+    instantiate_parametrized_tests,
+    parametrize,
     run_tests,
     skipIfCrossRef,
     skipIfXpu,
@@ -12162,6 +12164,26 @@ class TestExportCustomClass(TorchTestCase):
             "torch.ops.aten.upsample_bilinear2d.vec", 1, exactly=True
         ).run(ep.graph_module.code)
 
+    @parametrize("strict", [False, True])
+    def test_while_loop_simple(self, strict):
+        class Simple(torch.nn.Module):
+            def forward(self, ci, a, b):
+                def cond_fn(i, x, y):
+                    return i > 0
+
+                def body_fn(i, x, y):
+                    return i - 1, x + y, y - x
+
+                return torch._higher_order_ops.while_loop(cond_fn, body_fn, [ci, a, b])
+
+        example_inputs = (
+            torch.tensor(1),
+            torch.randn(10, 20),
+            torch.randn(10, 20),
+        )
+        ep = export(Simple(), example_inputs, strict=strict)
+
+instantiate_parametrized_tests(TestExportCustomClass)
 
 if __name__ == "__main__":
     run_tests()
```



cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: godot
Issue: Custom objects' fields are not transferred when sent over RPC
Labels: discussion,topic:network

### Tested versions

4.4dev7

### System information

Godot v4.4.dev7 - Windows 10 (build 19045) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 32.0.15.6636) - AMD Ryzen 7 5800X 8-Core Processor (8 threads)

### Issue description

Let's say you have a `PlayerData` `Object`:

```gdscript
class_name PlayerData extends Object

var username: String = "default_user"
var position: Vector3
var rotation: Vector3
```

If we create a dummy `PlayerData` like this:

```gdscript
var data := PlayerData.new()

data.username = "lena"
data.position = Vector3.FORWARD
data.rotation = Vector3.BACK
```

And try to send it over RPC, the receiving side will instead get a `PlayerData` object equivalent to just `PlayerData.new()`, i.e. the fields are not transferred.

### Steps to reproduce

Download the MRP. Open Debug > Customize Run Instances and configure it as shown here:

![Image](https://github.com/user-attachments/assets/111ce9e1-a9f9-4da9-8219-c00135ddc71a)

Run the project. Observe the errors.


### Minimal reproduction project (MRP)

[netbug.zip](https://github.com/user-attachments/files/18561405/netbug.zip)
Repository: pytorch
Issue: No broadcasting by default.
Labels: triage review

### 🚀 The feature, motivation and pitch

I actually ran into shape bug but pytorch guessed it would be some broadcasting intentionally, and wasted a bit time( like hours, but still acceptable).
Then I decide to print the shape and denote it in the variable name, like g_reshaped__batch_1_output. 
I prefer the no-broadcasting to be the by default, and when I need it, I write a line to tell pytorch to do it.
Although the variable names will still be very long in my code.

![Image](https://github.com/user-attachments/assets/56d558a7-d466-4787-9ece-e55b1fbb076e)

### Alternatives

The default behavior now is the alternative.
Another alternative is like, specify a batch dimention for everywhere, so pytorch knows the xth dim is batch, and it never touches the batch dim.

### Additional context

It's ok if you guys decide not to make this change. 
The only problem I can remember is, when I use mseloss or any loss that automatically reduce the shape to scalar, I always have to print the shape to make sure it's correct. 
My personal convention is a explicit batch dim everywhere and assert it in every function. It makes all my test code have one extra layer of [], but it makes me much more confident about my code.
Repository: godot
Issue: Godot 4.3 becomes highly unresponsive, likely due to Windows 11 24H2 update
Labels: bug,platform:windows,topic:editor,needs testing,performance

### Tested versions

- This issue is on Godot 4.3.stable.official [77dcf97d8], unsure of other versions. This issue didn't seem to happen with the limited testing I did with v4.2.stable.official [46dc27791]
- Windows 11 version 24H2





### System information

Windows 11 - Godot 4.3.stable.official - Vulkan (Forward+) - AMD Ryzen 7 5800X3D 8-Core Processor - 3.40 GHz - NVIDIA GeForce RTX 2070

### Issue description

After my pc installed the latest Windows update yesterday (24H2), all Godot projects in 4.3 become highly unresponsive on launch. Even opening new blank projects seems to create unresponsiveness. Even after long load times, if a project does manage to launch to the editor, the editor is also highly unresponsive. 

Fixes attempted:
- restarting the editor
- restarting the pc
- deleting the .godot folder and re-importing files
- deleting the entire project and re-cloning it from version control
- running Godot as administrator

### Steps to reproduce

On the newest feature update to Windows 11, 24H2. Create a new project and try to interact with the editor on v4.3.stable.official [77dcf97d8].

### Minimal reproduction project (MRP)

On the newest feature update to Windows 11, 24H2. Create a new project and try to interact with the editor on v4.3.stable.official [77dcf97d8].
Repository: rust
Issue: Associated Type Bounds on Trait Bounds on GAT produce error
Labels: A-trait-system,A-associated-items,C-bug,F-associated_type_bounds,needs-triage

<!--
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.
-->
I hope this is a genuine bug and not just working as intended🙈

I tried this code:

```rust
trait Assoc {
	type Type;
}

trait Static: 'static {
	type Same<T>: Assoc<Type: Static>;
}
```

I expected to see this happen: The code compiles.
Instead, this happened: The code produces the following compile error:
```
error[E0310]: the associated type `<<Self as Static>::Same<T> as Assoc>::Type` may not live long enough
 --> src/lib.rs:6:28
  |
6 |     type Same<T>: Assoc<Type: Static>;
  |                               ^^^^^^
  |                               |
  |                               the associated type `<<Self as Static>::Same<T> as Assoc>::Type` must be valid for the static lifetime...
  |                               ...so that the type `<<Self as Static>::Same<T> as Assoc>::Type` will meet its required lifetime bounds...
  |
note: ...that is required by this bound
 --> src/lib.rs:5:15
  |
5 | trait Static: 'static {
  |               ^^^^^^^
help: consider adding an explicit lifetime bound
  |
6 |     type Same<T>: Assoc<Type: Static> where <<Self as Static>::Same<T> as Assoc>::Type: 'static;
  |
```

Note that either removing `<T>` or replacing it with `<T: 'static>` makes the error go away.

### 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.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.84.0
LLVM version: 19.1.5
```
Also persists on latest nightly:
```
rustc 1.86.0-nightly (f85c6de55 2025-01-26)
binary: rustc
commit-hash: f85c6de55206dbee5ffedfd821df1503a7b92346
commit-date: 2025-01-26
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
```