sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Variables exported as Resource severely slow down inspector
Labels: bug,topic:editor,performance

### Godot version

4.1.2 stable, 4.2 RC1

### System information

macOS Ventura

### Issue description

If you export a variable of type Resource, like this:

`@export var something : Resource`

Then dragging and dropping a resource into this slot in the inspector is choppy. There's a noticeable delay on the resource's icon appearing on the start of the drag, and then hovering it over the slot is choppy and the actual drop is slow as well. Variables exported as a specific resource, such as Texture or PackedScene, aren't affected.

Also, and this only happens when these export variables are populated, the inspector can become very slow to load. 

These issues get progressively worse as the number of such exported variables increases, and you don't need a lot to affect usability.

https://github.com/godotengine/godot/assets/33777501/d3600886-75e7-4237-a937-9ab338bf6a15



### Steps to reproduce

Export a variable as type Resource (several will make it easier to notice).
Drag resources into them, note choppy drag and drop.
Then note loading delay on selecting the node.

MRP is created in 4.2 RC1

### Minimal reproduction project

[ExportResourceIssue.zip](https://github.com/godotengine/godot/files/13417750/ExportResourceIssue.zip)
Repository: go
Issue: cmd/go/internal/test: compile error for `go test` on package with no test files does not output package-level "FAIL" error
Labels: NeedsFix,GoCommand

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/jzheng/Library/Caches/go-build"
GOENV="/Users/jzheng/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/jzheng/Plaid/go/pkg/mod"
GONOPROXY="github.plaid.com"
GONOSUMDB="github.plaid.com"
GOOS="darwin"
GOPATH="/Users/jzheng/Plaid/go"
GOPRIVATE="github.plaid.com"
GOPROXY="https://proxy.golang.org"
GOROOT="/usr/local/Cellar/go/1.20.6/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.20.6/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.20.6"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="cc"
CXX="c++"
CGO_ENABLED="0"
GOMOD="/Users/jzheng/Plaid/go/src/github.plaid.com/plaid/go.git/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/mw/swflvd316dl67xycd2lmfzhcll7jtg/T/go-build3323119429=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

Run `go test ./pkg ./pkg2` on the following directory:

```
go.mod
pkg/main.go
pkg2/main.go
```

go.mod:
```
module foo

go 1.21.4
```

pkg/main.go:
```
package pkg

import "fmt"

func main() {
	fmt.Println("Hello, world")
}
```

package pkg2/main.go (**does not compile**)
```
package pkg2

import "fmt"

func main() {
	fmt.Println("Hello, world")
	foo
}
```

### What did you expect to see?
```jzheng-mbp:foo jzheng$ go test ./pkg ./pkg2
# foo/pkg2 [foo/pkg2.test]
pkg2/main.go:7:2: undefined: foo
?   	foo/pkg	[no test files]
FAIL	foo/pkg2 [build failed]
FAIL
```

The above is the output that shows up if I add a `pkg2/main_test.go` file with a line `package pkg2 line in the file.

### What did you see instead?
```
go test ./pkg ./pkg2
# foo/pkg2
pkg2/main.go:7:2: undefined: foo
?   	foo/pkg	[no test files]
FAIL
```

The `FAIL	foo/pkg2 [build failed]` line is missing. This is true in both regular and `-json` output formats, which makes it harder to parse the results of CI runs on many packages to see which packages resulted in failures.
Repository: ui
Issue: [Alert] : Headings must have content and the content must be accessible by a screen reader |  jsx-a11y/heading-has-content
Labels: bug,component: alert

Thank you @shadcn for this amazing library. It helped us a lot to improve our UI and reduce the development time of components.

I used the [alert](https://ui.shadcn.com/docs/components/alert) component for displaying an important information, however, I found that it does not pass a the accessibility rule by ESLINT A11Y plugin which displays this error:

![image](https://github.com/shadcn-ui/ui/assets/20143684/f0538abf-9bb3-485d-aa08-d9a8f8168ddd)

The line of code behind this issue:

```jsx

<h5
    ref={ref}
    className={cn("mb-1 font-medium leading-none tracking-tight", className)}
    {...props}
  />
```

Is it safe to disable the rule or should I resolve it within the component?

Thank you
Repository: pytorch
Issue: [Tracker] Inconsistencies between CPU and GPU computation
Labels: module: numerical-stability,module: cuda,triaged

This issue tracks inconsistencies between CPU / GPU op computation, gathering reports under a single umbrella.

In general, resolution will go one of two directions:
* Inconsistency is expected (see [numerical accuracy docs](https://pytorch.org/docs/stable/notes/numerical_accuracy.html)); we should close the issue
* A real bug exists that causes the discrepancy; we should fix the bug

Investigation should be done on a per-issue basis to determine whether a fix is needed or not. The following lists summarize the status for these individual issues.

**Needs Investigation:**
* #132031
* #132041
* #132045
* #132047

**Needs Fix:**
* #142466 - behavior with `out_channels=0` should be consistent across devices

**Resolved:**
* #120875
* #114081
* #114085 
* #114052
* #114076
* #114028
* #114032
* #114033
* #114038
* #114039
* #114043
* #114045
* #114046
* #114055
* #114074
* #114078
* #114092
* #114051
* #114087

cc @ptrblck
Repository: go
Issue: github.com/yuin/goldmark/util: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "github.com/yuin/goldmark/util" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/2c298132ae2bdb13b053c49c60d871244ad65139)):

    ../../../../pkg/mod/github.com/yuin/goldmark@v1.4.13/util/html5entities.go:18:53: internal compiler error: 'init': panic during regalloc while compiling init:
    
    runtime error: index out of range [134432465] with length 262144
    
    goroutine 37 [running]:
    cmd/compile/internal/ssa.Compile.func1()
    	/workdir/go/src/cmd/compile/internal/ssa/compile.go:49 +0x7c
    panic({0x939de0, 0xc003e42000})
    	/workdir/go/src/runtime/panic.go:884 +0x240
    cmd/compile/internal/ssa.(*sparseMapPos).set(...)
    ...
    	/workdir/go/src/cmd/compile/internal/gc/compile.go:171 +0x4c
    cmd/compile/internal/gc.compileFunctions.func3.1()
    	/workdir/go/src/cmd/compile/internal/gc/compile.go:153 +0x44
    created by cmd/compile/internal/gc.compileFunctions.func3
    	/workdir/go/src/cmd/compile/internal/gc/compile.go:152 +0x1f4
    
    
    
    Please file a bug report including a short program that triggers the error.
    https://go.dev/issue/new


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: charSet meta tag is camelCased in the server HTML causing a server/client difference
Labels: bug

### Link to the code that reproduces this issue

https://github.com/FoggDev/reproduction-app

### To Reproduce

1. Run your Next project.
2. Right click > View Page Source

See the charset meta tag:

`<meta charSet="utf-8"/>`

It should be:

`<meta charset="utf-8"/>`

Causing this issue:
![image](https://github.com/vercel/next.js/assets/51180821/f3495cb0-4895-4061-bc6d-d3659f25a112)


### Current vs. Expected behavior

See the charset meta tag:

`<meta charSet="utf-8"/>`

It should be:

`<meta charset="utf-8"/>`

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:34 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T8103
Binaries:
  Node: 20.8.1
  npm: 10.1.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.3
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


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

App Router

### Additional context

_No response_
Repository: go
Issue: x/tools/gopls: include anonymized stacks in `gopls stats -anon` output
Labels: gopls,Tools

The `gopls stats -anon` command filters out bug reports, because their error message may theoretically reference user code.

But the existence of bug reports is important to capture. Refine this scrubbing to leave the gopls stack involved in the report (similar to what we do for telemetry reporting via #62249).

CC @hyangah
Repository: next.js
Issue: PPR + revalidate → hydration errors
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/dayblox/ppr-isr

### To Reproduce

1. Build the application (next build)
2. Start the application (next start)
3. Navigate to [localhost:3000](http://localhost:3000)
4. Open Console (F12)
5. Keep refreshing for a few seconds and observe hydration errors when the page is revalidated

### Current vs. Expected behavior

Current
> There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering.

> Hydration failed because the initial UI does not match what was rendered on the server.

> Text content does not match server-rendered HTML.

Expected no errors

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.10.5
Relevant Packages:
  next: 14.0.4-canary.5
  eslint-config-next: 14.0.3-canary.5
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.2
Next.js Config:
  output: N/A
```


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

App Router, Data fetching (gS(S)P, getInitialProps)

### Additional context

_No response_
Repository: godot
Issue: Silent crash while using a SubViewport
Labels: bug,topic:core,confirmed,crash

### Godot version

4.2.rc1

### System information

Godot v4.2.rc1 - Linux Mint 21.2 (Victoria) - X11 - Vulkan (Forward+) - dedicated AMD Unknown (RADV ICELAND) () - AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8 Threads)

### Issue description

The code used on the minimal reproduction project, may crash randomly the game while starting to run on Debug mode
While developing the game, I saw these two kinds of crashes on the Godot logs
![image](https://github.com/godotengine/godot/assets/50798713/5b95e312-af0a-4aa9-9315-4d058f45504e)
![image](https://github.com/godotengine/godot/assets/50798713/ea6b97e2-d7c2-4cf6-acd5-18ad42ccc9a6)


### Steps to reproduce

Rerun the minimal reproduction project until it crashes

### Minimal reproduction project

[GodotCrash.zip](https://github.com/godotengine/godot/files/13443232/GodotCrash.zip)
Repository: flutter
Issue: Convert "module loader plugin" Gradle script into a proper Gradle plugin
Labels: c: new feature,platform-android,tool,t: gradle,c: proposal,P2,team-android,triaged-android

### Description

The [`module_plugin_loader.gradle`](https://github.com/flutter/flutter/blob/3.16.0/packages/flutter_tools/gradle/module_plugin_loader.gradle) file is a Gradle script. It should be a Gradle plugin instead, for all reasons mentioned in #121552 and #125009.

### More context

For an example of 2 similar conversions that already happened, see:
- [flutter/flutter#121552](https://github.com/flutter/flutter/issues/121552) (for [`flutter.gradle`](https://github.com/flutter/flutter/blob/3.16.0/packages/flutter_tools/gradle/flutter.gradle))
- [flutter/flutter#125009](https://github.com/flutter/flutter/issues/125009) (for [`app_plugin_loader.gradle`](https://github.com/flutter/flutter/blob/3.16.0/packages/flutter_tools/gradle/app_plugin_loader.gradle))

This issue is about doing the very same thing but for `module_plugin_loader.gradle` (including providing backward compatibility).

See also #135392, which should be updated once this issue is fixed.
Repository: pytorch
Issue: Unable to build on CUDA 11.8 due to cutlass incompatibility
Labels: module: build,module: cuda,triaged

### 🐛 Describe the bug

cutlass is seemingly incompatible with CUDA 11.8 but we don't have detection for when this is the case to disable it.

I used https://gist.github.com/ezyang/aacb7b3cdad9264e3a3d4492973d5ce3 to "fix" this

cc @malfet @seemethere @ptrblck @drisspg 

### Versions

main
Repository: flutter
Issue: Add itemExtentBuilder to ListView.separated
Labels: c: new feature,framework,f: scrolling,c: proposal,P3,team-framework,triaged-framework

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

For me, and I'm sure a lot of other developers, using ListView.separated is pretty common. I use its `separatorBuilder` to provide a `SizedBox` of a fixed height in between my fixed-height items and the `itemBuilder` to build said items. I was pretty happy to see #131393 get merged into the framework, but I was disappointed to see it wasn't in `ListView.separated`. The widgets that they build are of two possible extents, depending on whether the index is even or not and I think that'd be a perfect case for `itemExtentBuilder`.

### Proposal

My proposal is to add the ability to use `itemExtentBuilder` in the `ListView.separated` constructor.
Repository: neovim
Issue: Preserve SELinux file context on saving
Labels: enhancement,has:vim-patch,filesystem

### Problem

This happens on SELinux-enabled Fedora 39 system.
I edit /etc/crontab with neovim.
After I edit it, crond fails to read it:

```
Nov 20 22:48:01 homeserver crond[2538]: (*system*) RELOAD (/etc/crontab)
Nov 20 22:48:01 homeserver crond[2538]: ((null)) Unauthorized SELinux context=system_u:system_r:system_cronjob_t:s0-s0:c0.c1023 file_context=unconfined_u:obje>
Nov 20 22:48:01 homeserver crond[2538]: (root) FAILED (loading cron table)
```
The workaround is to restore that file's expected context with `restorecon -Fv /etc/crontab`.

Before editing, the file has this context:
```
 # ls -lZ /etc/crontab
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 938 Nov 20 22:51 /etc/crontab
```
After:
```
 # ls -lZ /etc/crontab
-rw-r--r--. 1 root root unconfined_u:object_r:etc_t:s0 938 Nov 20 23:10 /etc/crontab
```

I guess it's because the file is edited and saved not in place, but using a copy which is then "moved into" the old name.

This is a common reoccurring problem: people apparently edit system cron configs and later find they stop working:
https://bugzilla.redhat.com/show_bug.cgi?id=1625645
https://bugzilla.redhat.com/show_bug.cgi?id=1547368

We can't immediately fix this for all editors, and I am not even completely sure the editor is the best party to take responsibility. But I believe NeoVIM can set the precedent for others to follow.

### Expected behavior

SELinux context remains the same after saving.
Repository: flutter
Issue: Double-down on the `ndk_helpers` pattern for NDK dlsym lookups
Labels: engine,P2,c: tech-debt,team-engine,triaged-engine

We avoid importing the NDK statically (i.e. `#include <media/NdkImageReader.h>`), because our [`__ANDROID__VERISON__` is only 22](https://github.com/flutter/buildroot/blob/master/build/config/android/config.gni#L47), meaning we cannot access many NDK APIs. Instead, we use `dlsym` lookups.

However, we do so in at least 3 different places:

- `shell/platform/android/android_choreographer.cc`
- `shell/platform/android/flutter_main.cc`
- `shell/platform/android/ndk_helpers.cc`

The latter, `shell/platform/android/ndk_helpers.cc`, is probably the pattern we should be using across the SDK. In addition, it would be nice to use macros to avoid the amount of easy-to-make mistakes in typing the functions/setup code.
Repository: deno
Issue: `deno test` ignores dangling rejected promises when `--coverage` is used.
Labels: bug,testing

1. Save the following in `foo.test.js`:
```js
async function throwsAsync() {
    throw new Error("oh no");
}

Deno.test("test", () => {
    throwsAsync();
});
```
2. Run `deno test foo.test.js`, note that the error is printed as expected
3. Run `deno test --coverage=.coverage foo.test.js`, the test now passes even though it shouldn't.

This started happening somewhere between 1.32.4 and 1.33.0

Of course the solution is to make the test function async and `await` the `throwsAsync()` call, but it's easy to miss this.
Repository: rust
Issue: Using `let` pattern with `ref` results in 'mismatched types' when combined with 'panic!()'
Labels: T-lang,T-compiler,C-bug,A-coercions

<!--
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
struct Foo {
    bar: u8
}

fn main() {
    let Foo { ref bar } = panic!();
}
```

I expected to see this happen: The code should compile successfully by coercing the `!` from `panic!()` to `Foo`.

Instead, this happened: rustc produces the following error:

```
error[E0308]: mismatched types
 --> src/main.rs:6:9
  |
6 |     let Foo { ref bar } = panic!();
  |         ^^^^^^^^^^^^^^^   -------- this expression has type `!`
  |         |
  |         expected `!`, found `Foo`
  |
  = note: expected type `!`
           found struct `Foo`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` (bin "playground") due to previous error
```

The code compiles successfully if the `ref` keyword is removed.

### 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.76.0-nightly (2b603f95a 2023-11-12)
binary: rustc
commit-hash: 2b603f95a48f10f931a61dd208fe3e5ffd64e491
commit-date: 2023-11-12
host: x86_64-unknown-linux-gnu
release: 1.76.0-nightly
LLVM version: 17.0.4

```
Repository: go
Issue: x/tools/gopls: incorporate pgo into release process
Labels: gopls,Tools

Reminder issue: we should use [pgo](https://go.dev/blog/pgo) with gopls.

We can either calibrate using our [benchmarks](https://perf.golang.org/dashboard/?benchmark=all&repository=tools&branch=release-branch.go1.20), or by collecting/merging real editing sessions.
Repository: rust
Issue: Closures needlessly capture all generic parameters from parent item in TAIT
Labels: C-enhancement,A-closures,A-impl-trait,T-types

<!--
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
#![feature(type_alias_impl_trait)]

type Tait = impl Sized + 'static;

fn capture<T>() -> Tait {
    || 0u8
}
```

I expected to see this happen:

Successful compilation, since the generic parameter `T` is not used in the returned closure.

Instead, this happened:

```
   Compiling playground v0.0.1 (/playground)
error: type parameter `T` is part of concrete type but not used in parameter list for the `impl Trait` type alias
 --> src/lib.rs:6:5
  |
6 |     || 0u8
  |     ^^^^^^
```

This error also happens when returning async blocks:

```rust
// same error
fn capture_async<T>() -> Tait {
    async {
        0u8
    }
}
```

Also, this appears to only affect generic type parameters, as lifetimes aren't captured if the closure doesn't use them:

```rust
// compiles
fn capture_lt<'a>(_: &'a ()) -> Tait {
    || 0u8
}
```

### 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.
-->

`Version`:

```
rustc 1.76.0-nightly (2023-11-19 9a66e4471f71283fd54d)
```
Repository: vscode
Issue: SCM: dirty diff decorator sometimes shows lines as added when they are not actually added
Labels: bug,diff-editor

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.85.0-insider
- OS Version: macOS Sonoma 14.0

Steps to Reproduce:

1. Create a new file with the following text and stage it:
```
1
2
2
3
4
```
2. Edit lines 1, 4, and 5 as follows:
```
5
2
2
5
2
```
3. Then the second line appears as added
<img width="128" alt="Screenshot 2023-11-21 at 13 08 33" src="https://github.com/microsoft/vscode/assets/107108195/79c59f67-d925-4805-9763-6615f1814f2e">