sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: E0106 "missing lifetime specifier" should be omitted when the signature is incorrect in an `impl` (E0186)
Labels: A-diagnostics,T-compiler

### Code

```Rust
trait Foo {
    fn foo(&self) -> &str;
}

struct Example;
impl Foo for Example {
    fn foo() -> &str {
        "example"
    }
}
```

### Current output

```Shell
error[E0106]: missing lifetime specifier
 --> src/lib.rs:7:17
  |
7 |     fn foo() -> &str {
  |                 ^ 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
help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static`
  |
7 |     fn foo() -> &'static str {
  |                  +++++++
help: instead, you are more likely to want to return an owned value
  |
7 |     fn foo() -> String {
  |                 ~~~~~~

error[E0186]: method `foo` has a `&self` declaration in the trait, but not in the impl
 --> src/lib.rs:7:5
  |
2 |     fn foo(&self) -> &str;
  |     ---------------------- `&self` used in trait
...
7 |     fn foo() -> &str {
  |     ^^^^^^^^^^^^^^^^ expected `&self` in impl
```

### Desired output

```Shell
error[E0186]: method `foo` has a `&self` declaration in the trait, but not in the impl
 --> src/lib.rs:7:5
  |
2 |     fn foo(&self) -> &str;
  |     ---------------------- `&self` used in trait
...
7 |     fn foo() -> &str {
  |     ^^^^^^^^^^^^^^^^ expected `&self` in impl
```

### Rationale and extra context

When the function is a trait associated function, the signature must match (or refine) the trait’s, so E0106 and any other errors that would propose changes to the signature are misleading or at least not nearly as relevant as E0186 (or E0050 or E0053 or any other such mismatch). Therefore, they should be hidden.

This is particularly important for situations involving a missing `self` parameter, because (in my personal experience) it’s easy to forget to write `self` in the parameter list.

### Rust Version

```Shell
1.84.0
```
Repository: react-native
Issue: Zooming in ScrollView causes incorrect offset of content
Labels: Issue: Author Provided Repro,Component: ScrollView,Needs: Version Info

### Description

When using the zoom and pinchGestureEnabled on a ScrollView, the content shifts to the side after re-rendering the component when zoomed in.

### Steps to reproduce

1) Toggle the ScrollView on
2) Zoom in
3) Toggle the ScrollView off
4) Toggle the ScrollView on

### React Native Version

0.76.6

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: Windows 11 10.0.22631
  CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
  Memory: 3.26 GB / 15.78 GB
Binaries:
  Node:
    version: 22.8.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 1.22.22
    path: C:\Program Files\nodejs\yarn.CMD
  npm:
    version: 10.8.2
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: Version     2021.1.0.0 AI-211.7628.21.2111.8193401
  Visual Studio:
    - 17.3.32804.467 (Visual Studio Community 2022)
Languages:
  Java:
    version: 17.0.8
    path: /c/Program Files/Common Files/Oracle/Java/javapath/javac
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.3
    wanted: ^15.1.3
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.6
    wanted: 0.76.6
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```

### Stacktrace or Logs

```text
Visual bug
```

### Reproducer

https://snack.expo.dev/@bram-dc/scrollview-zoom-offset

### Screenshots and Videos

https://github.com/user-attachments/assets/7eaed09f-1b25-4cb1-bb7d-379bf86b29d4
Repository: go
Issue: x/build/cmd/relui: add support for making release announcement posts on Bluesky
Labels: Builders,NeedsInvestigation,Automation

During Go releases, relui takes on posting on 2 social sites using their APIs (#47403 and #65046). By now we have an account on one more social site, Bluesky, where we've also started to post links to Go release announcements (for example, https://bsky.app/profile/golang.org/post/3lfvcgeox7c2c).

This is the tracking issue for automating Go release announcement posts on [Bluesky](https://docs.bsky.app/).

CC @golang/release, @mknyszek, @fflewddur.
Repository: flutter
Issue: [flutter_test] gestures can leak from test to test
Labels: a: tests,framework,P1,team-framework,triaged-framework

Steps to reproduce:

* Check out this revision of Flutter: https://github.com/flutter/flutter/commit/bb2d34126cc8161dbe4a1bf23c925e48b732f670
* `cd packages/flutter`
* `flutter test  --reporter=expanded --test-randomize-ordering-seed=20250118 --fatal-warnings --track-widget-creation  test/material/reorderable_list_test.dart`
* Observe the test passing.
* Now change the seed: `flutter test  --reporter=expanded --test-randomize-ordering-seed=20250117 --fatal-warnings --track-widget-creation  test/material/reorderable_list_test.dart`
* Observe the test failing.

The reason it's failing is because a test in `reorderable_list_test.dart` created a `TestGesture` but never finalized it by cancelling it or by calling `drag.up()`. Because tests that are sensitive to dangling gestures could be anywhere, this issue did not immediately reproduce until, by chance, we rolled a seed that sorts tests such that the sensitive test was run immediately after the test that leaves the gesture hanging (which took about 1 month). This was fixed in https://github.com/flutter/flutter/pull/161836. However, the issue should have been caught immediately when `reorderable_list_test.dart` was added for the first time. `flutter_test` could validate that when a test ends, there are not dangling gestures and `VelocityTrackers` left.
Repository: flutter
Issue: Engine git-hooks are executed even for framework-only PRs
Labels: team-infra,P2,monorepo

```sh
matanl@matanl-macbookpro4 flutter % git push -f
The clang-tidy check is disabled. To enable set the environment variable PRE_PUSH_CLANG_TIDY to any value.
Starting formatting checks.
```

Not only is this taking forever (I believe unrelated), there is nothing it could be checking in this PR.
Repository: ant-design
Issue: Buttons with variant "link" or "text" use the `info` color when the color is set to `primary`
Labels: unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-t3ejzn?file=demo.tsx)

### Steps to reproduce

- Customize primary color and info color
- Use a button and pass the props color="primary" variant="text"

### What is expected?

The text color should be the primary color

### What is actually happening?

The text color is the info color

| Environment | Info |
| --- | --- |
| antd | 5.23.1 |
| React | doesn't matter |
| System | doesn't matter |
| Browser | doesn't matter |

---
So it is basically the same issue as https://github.com/ant-design/ant-design/issues/51343.
I know you closed it but I really want you to reconsider it.
With the new colors of buttons (which released in version `5.23.0`) the `text` variant is working great.
I think that if you explicitly set the button color to `primary` it must have a primary color.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Use `DEPS` to bootstrap the GitHub Actions Dart SDK
Labels: team-infra,P3,c: tech-debt,monorepo

Some pondering on if initializing the Dart SDK can be vastly simplified, potentially also removing the need for the engine to create a copy of the Dart SDK as part of vended artifacts. One of the reasons this _could_ be beneficial is we'd like to explore using GitHub actions in the Flutter repo.

A GitHub action would _not_ wait for the engine to be built, therefore it would not have access to the engine binaries for the current SHA, and for the action to be written in Dart (instead of say, Python or Bash), it would need a version of the Dart SDK from somewhere - and ideally that would be the same version as pinned in Flutter for compatibility reasons.

In https://github.com/flutter/flutter/pull/161788 I experiment with an override, `FLUTTER_ENGINE_VERSION`, that allows the GitHub action to use the Dart SDK from the base-ref (which merged commit the PR was branched off originally). This will work _until the Dart SDK revs_, in which case now we'll be using an older Dart SDK to evaluate the Flutter repo.

Potential issues: what if we wanted to run `dart format` on a GitHub action? We'd be using an older version of Dart format than the one potentially being changed/updated in `DEPS`.

The proposal below is an _idea_ of what we could do, but we could imagine other ideas/overrides, for example, we could just have the GitHub _action_ self-bootstrap the Dart SDK from `DEPS` and _not_ change how `bin/dart` works at all.

---

Today, `bin/dart` (part of the tools shipped in the Flutter SDK) is a wrapper script that self-bootstraps:

https://github.com/flutter/flutter/blob/78c62b00cc58b785ae1d6fca44291634b0c8b3c0/bin/dart#L46-L59

It, if necessary, downloads the Dart SDK, by writing a `engine.version` file:

https://github.com/flutter/flutter/blob/78c62b00cc58b785ae1d6fca44291634b0c8b3c0/bin/internal/update_engine_version.sh#L41

... and then using that value in a later shell script to download a Dart SDK:

https://github.com/flutter/flutter/blob/d59d02c014428ac71eb347165d4616043354b7f4/bin/internal/shared.sh#L147

https://github.com/flutter/flutter/blob/78c62b00cc58b785ae1d6fca44291634b0c8b3c0/bin/internal/update_dart_sdk.sh#L126-L161

Lots of this logic is due to the fact that the engine and framework repos were separate, there was no (canonical) way to identify which Dart SDK to use, but now there is a single canonical number that is used:

https://github.com/flutter/flutter/blob/78c62b00cc58b785ae1d6fca44291634b0c8b3c0/DEPS#L59
Repository: angular
Issue: ⚠️ Local development bugs with HMR
Labels: area: core,core: hot module replacement (HMR)

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

compiler-cli

### Is this a regression?

Yes

### Description

We're aware of reports of local development bugs arising from Angular template HMR in 19.1.x, which has been enabled by default.

List of known issues:

* [Fixed in 19.1.2] ~~#59581~~
* [Fixed in 19.1.2] ~~#59592~~
* [Fixed in 19.1.2] ~~angular/angular-cli#29248~~
* [Fixed in 19.1.3(CLI)] ~~#59605~~
* [Fixed in 19.1.4(CLI)] ~~angular/angular-cli#29424~~
* [Fixed in 19.1.3] ~~#59632~~
* [Fixed in 19.1.3] ~~#59634~~
* [Fixed in 19.1.3] ~~#59639~~
* [Fixed in 19.1.3] ~~#59640~~

We're actively investigating and fixing these issues to create a smooth HMR experience out of the box. Production builds and releases are not affected. If you discover any additional HMR challenges which don't appear to be related to the linked issues above, verify that you are on a recent version (19.1.3+), and please [file a new issue](http://github.com/angular/angular/issues/) and link it here so we can triage and investigate.

### Workarounds

In the meantime, if you encounter any problems relating to HMR, you can work around them in three ways:

1. Refresh the page \- This loads a fresh copy of your application with up to date code.  
2. `ng serve --no-hmr` \- This disables HMR for your local devserver and automatically refreshes the page on any code changes.  
3. Disable HMR for your project \- Configuring `angular.json` will disable HMR for all `ng serve` invocations by default.  
   * This is useful for a project with a large number of developers without needing to communicate these workarounds to all contributors.  
   * Remember to re-enable once the relevant issues are fixed\!

```json
{
  "projects": {
    "my-project": {
      "architect": {
        "serve": {
          "options": {
            "hmr": false
          }
        }
      }
    }
  }
}
```

Thank you for sharing any HMR issues and helping improve Angular one bugfix at a time. We're committed to fully stabilizing this feature and excited to bring improved build performance to everyone.
Repository: flutter
Issue: A label to track approval of `c: proposal` issues?
Labels: team,will need additional triage,c: proposal,fyi-infra

For example, in https://github.com/flutter/flutter/issues/161843, I propose making a change.

It would be nice for us to mark proposals as approved, even if it's just a GitHub label, so that folks can know "this is a proposal, and the domain owner(s) agree with it being implemented" versus "this is a proposal, and we haven't reviewed/rejected/approved it yet".
Repository: godot
Issue: Editor crash while refactoring scripts
Labels: bug,topic:gdscript,topic:editor,crash

### Tested versions

- Occurred in v4.4.dev7.official [46c8f8c5c]

### System information

Godot v4.4.dev7 - Windows 11 (build 22631) - Multi-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 3080 Ti (NVIDIA; 32.0.15.6636) - AMD Ryzen 9 5900X 12-Core Processor (24 threads)

### Issue description

I experienced two crashes while performing some script/class refactoring in the Godot editor.  The exact repro steps are unknown, however, I have two crash dumps from Windows.  Both are double frees, so my best guess is an issue with saving and compiling scripts sharing resources improperly.

[Godot_v4.4-dev7_win64.exe.10648.dmp](https://github.com/user-attachments/files/18462120/Godot_v4.4-dev7_win64.exe.10648.dmp)
[Godot_v4.4-dev7_win64.exe.25672.dmp](https://github.com/user-attachments/files/18462119/Godot_v4.4-dev7_win64.exe.25672.dmp)

### Steps to reproduce

Some combination of the following actions in quick succession in an unknown order: (e.g. when duplicating `wall_*.gd` for a new type)
- Ctrl+D (duplicate) a script with a `class_name`
- Double click to open the script
- Ctrl+S to save the script
- Updating the `class_name {name}` name

### Minimal reproduction project (MRP)

Sample project to bootstrap reproduction
[poc.zip](https://github.com/user-attachments/files/18462323/poc.zip)
Repository: rust
Issue: LLVM assertion failure on Wasm exceptions
Labels: I-crash,A-LLVM,T-compiler,O-wasm,C-bug,O-wasi,O-emscripten

### Code

```Rust
fn main() {}
```

:/


### Meta

I'm building rustc on the current master (bcd0683e5dce1945b5d940714742e7502883bb5c) with LLVM assertions enabled. I'm compiling the program above like this:

```
RUSTFLAGS="-C panic=unwind" cargo +stage1 build --target wasm32-wasip1 -Z build-std
```

I'm using the 23.0 WASI sysroot, downloaded from their GitHub releases, if that matters.

### Error output

```
rustc: /checkout/src/llvm-project/llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:1378: void mapWasmLandingPadIndex(MachineBasicBlock *, const CatchPadInst *): Assertion `IntrFound && "wasm.landingpad.index intrinsic not found!"' failed.
```

like, everywhere, on all sorts of standard crates like `libc` and `unwind`.

Disabling assertions hides the bug, and user code works fine. This also does not reproduce on rustup's nightly, probably for the same reason. I have no idea, really. Please tell me I'm doing something wrong.

For context, this seems more important because Emscripten is supposed to switch to Wasm exceptions soon-ish, and I imagine the same problem occurs there (but I haven't checked). Unlike wasm32-wasip1, unwinding is enabled there by default.

@rustbot label +A-LLVM
Repository: tauri
Issue: linux development often show blank screen.
Labels: type: bug,platform: Linux,status: needs triage

when modify some code , sometimes the `webview` component show nothing.
I need restart `pnpm run dev` and restart the rust `backend` to make it working again.
Anyone else have the same problem???
Repository: PowerToys
Issue: Technical glitches while running the powertoy
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run, General

### Steps to reproduce

when my pc is in idle state and after some time when i try to run the powertoys run using alt + space it don't register the action and fail to open 

### ✔️ Expected Behavior

when i open my pc with in 10 sec maximum it should open the powertoys run 

### ❌ Actual Behavior

It does not open the powertoys run and it some time it open directly using space button , also experienced at the same time that the it is unable to register my keyboard input and no keyword input seen 
sorry i don't have the screenshots right now 

### Other Software

_No response_
Repository: rust
Issue: Tracking issue for release notes of #133700: const-eval: detect more pointers as definitely not-null
Labels: T-lang,T-compiler,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #133700.

### Steps

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

### Release notes text

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

````markdown
# Language
- [const-eval: detect more pointers as definitely not-null based on their alignment](https://github.com/rust-lang/rust/pull/133700)
````

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

### Release blog section

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

````markdown
````

cc @RalfJung, @lcnr -- origin issue/PR authors and assignees for starting to draft text
Repository: neovim
Issue: AI/LLM/GenAI related features
Labels: ui,lua

This is a stub issue, will update it over time.

## Problem

Although "AI features" are not something we see a need for in Nvim core, I'm looking at the space and have noticed some "primitives" that are missing and require every plugin to reimplement things that are generally useful, even for non-AI plugins. 


## Expected behavior

- A way to mark a buffer or window as "busy" or "in progress".
    - Default 'statusline' shows the busy indicator (optionally progress "spinner"?).
    - https://github.com/neovim/neovim/issues/28809
- `vim.ui` interface for showing progress.
- ✅ blink/highlight of a region will be helpful https://github.com/neovim/neovim/pull/32012 cc @siddhantdev
- multiline completion https://github.com/neovim/neovim/issues/7769
Repository: godot
Issue: [godot3.6] Compile web platform runtime error
Labels: bug,platform:web,needs testing,topic:dotnet

### Tested versions

3.6

### System information

godot3.6 v3.6.1.rc.mono.custom_build [4c1514c7f]

### Issue description

compile for the Web platform
`scons platform=javascript tools=no target=release 
scons platform=javascript tools=no target=release_debug 
`
set compiled  webassembly_debug.zip and webassembly_release.zip
![Image](https://github.com/user-attachments/assets/e709f2e0-c805-4191-b187-5538c20777a1)

run web  got a error
 modules\mono\glue\gd_glue.cpp:249 - Failed to export project: Missing BCL (Base Class Library) for platform: javascript

![Image](https://github.com/user-attachments/assets/660aed03-7105-4de6-a43f-29641158737e)

![Image](https://github.com/user-attachments/assets/5aee6efc-7566-4769-86ab-d64c4c17b2f2)

### Steps to reproduce

-

### Minimal reproduction project (MRP)

-
Repository: PowerToys
Issue: Not able to copy certain info
Labels: Issue-Bug,Needs-Triage,Product-Text Extractor

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

TextExtractor

### Steps to reproduce

Tried to copy info.  Text Extractor failed to copy.

![Image](https://github.com/user-attachments/assets/82602d10-57fa-4d60-8b57-b27306b2342b)

### ✔️ Expected Behavior

Successful copy

### ❌ Actual Behavior

Failed to copy particular info.  Copied everything else on the page successfully.

### Other Software

COMODO - Internet Security - 12.2.2.7036
Repository: react
Issue: [DevTools Bug] Cannot add child "301" to parent "155" because parent node was not found in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

www.github.com

### Repro steps

The error was thrown at chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1173126
    at v.emit (chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1140783)
    at chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1142390
    at bridgeListener (chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1552662)

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.0.1-c7c68ef842

### Error message (automated)

Cannot add child "301" to parent "155" because parent node was not found in the Store.

### Error call stack (automated)

```text
at chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1173126
    at v.emit (chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1140783)
    at chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1142390
    at bridgeListener (chrome-extension://gpphkfbcpidddadnkolkpfckpihlkkil/build/main.js:1:1552662)
```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add child  to parent  because parent node was not found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: godot
Issue: [v4.4-dev7_win64] Failure to launch
Labels: bug,platform:windows,crash,regression

### Tested versions

Reproducible in: Godot_v4.4-dev7_win64, Godot_v4.4-beta1_win64
Not reproducible in: Godot_v4.4-dev6_win64

### System information

Windows 11 - RTX 4090 (Thunderbolt 4) - Driver 566.36

### Issue description

Upon running the Godot application, the cursor spins for a second, then stops without ever launching the application. When utilizing onboard graphics (Radeon 680M), this problem is not present. However, when utilizing an RTX 4090 over Thunderbolt 4 (eGPU), it occurs. Just to clarify, this is a full-size card, not a 4090 mobile.

Logging doesn't appear out of the ordinary to me. If there is additional logging or information I can gather to assist, please do share.

```
PS C:\Users\kaboo\Desktop> .\Godot_v4.4-dev7_win64_console.exe --verbose
WorkerThreadPool: 16 threads, 4 max low-priority.
Godot Engine v4.4.dev7.official.46c8f8c5c - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
Native OpenGL API detected: 3.3: NVIDIA - NVIDIA GeForce RTX 4090
NVAPI: Init OK!
NVAPI: Disabled OpenGL threaded optimization successfully
NVAPI: Disabled G-SYNC for windowed mode successfully
PS C:\Users\kaboo\Desktop>
```

### Steps to reproduce

Appears to possibly be hardware related. Steps are as simple as launching the application.

### Minimal reproduction project (MRP)

Not Applicable
Repository: rust
Issue: regression: ICE: Failed to normalize Alias(Opaque, AliasTy
Labels: I-ICE,P-low,T-compiler,regression-from-stable-to-beta

- https://crater-reports.s3.amazonaws.com/beta-1.85-1/beta-2025-01-12/gh/Menestis.Skynet/log.txt
```
[INFO] [stdout] error: internal compiler error: compiler/rustc_middle/src/ty/normalize_erasing_regions.rs:168:90: Failed to normalize Alias(Opaque, AliasTy { args: [], def_id: DefId(0:850 ~ skynet[716d]::web::create_task::{opaque#0}::{opaque#0}), .. }), maybe try to call `try_normalize_erasing_regions` instead
```