sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime: apparent deadlock in TestDebugCallUnsafePoint
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "runtime" && `TestDebugCallUnsafePoint` && `panic: test timed out`
```

https://storage.googleapis.com/go-build-log/e9552219/linux-amd64-nounified_87ac7ca9.log (a TryBot on https://go.dev/cl/457336):
```
panic: test timed out after 3m0s
running tests:
	TestDebugCallUnsafePoint (2m51s)
…
goroutine 23224 [stopping the world]:
runtime.systemstack_switch()
	/workdir/go/src/runtime/asm_amd64.s:463 fp=0xc000077dc0 sp=0xc000077db8 pc=0x478540
runtime.stopTheWorld({0x824124, 0xa})
	/workdir/go/src/runtime/proc.go:1162 +0xa5 fp=0xc000077e10 sp=0xc000077dc0 pc=0x443665
runtime.stopTheWorldGC({0x824124, 0xa})
	/workdir/go/src/runtime/proc.go:1210 +0x45 fp=0xc000077e48 sp=0xc000077e10 pc=0x443865
runtime.GOMAXPROCS(0x10)
	/workdir/go/src/runtime/debug.go:28 +0x85 fp=0xc000077e70 sp=0xc000077e48 pc=0x40ada5
runtime_test.TestDebugCallUnsafePoint.func2()
	/workdir/go/src/runtime/debug_test.go:245 +0x26 fp=0xc000077e88 sp=0xc000077e70 pc=0x6e3ce6
runtime_test.TestDebugCallUnsafePoint(0xc0005b24e0)
	/workdir/go/src/runtime/debug_test.go:267 +0x307 fp=0xc000077f70 sp=0xc000077e88 pc=0x6e3b67
testing.tRunner(0xc0005b24e0, 0x84b578)
	/workdir/go/src/testing/testing.go:1575 +0x10b fp=0xc000077fc0 sp=0xc000077f70 pc=0x50602b
testing.(*T).Run.func1()
	/workdir/go/src/testing/testing.go:1628 +0x2a fp=0xc000077fe0 sp=0xc000077fc0 pc=0x50706a
runtime.goexit()
	/workdir/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc000077fe8 sp=0xc000077fe0 pc=0x47a761
created by testing.(*T).Run
	/workdir/go/src/testing/testing.go:1628 +0x3e5
```
Repository: flutter
Issue: IntrinsicHeight works incorrectly with Images
Labels: framework,a: images,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-framework,triaged-framework

`IntrinsicHeight` fails to calculate its height in various cases (i.e. when `Text` is present #87571), but this issue is about `Image`s.

UPD: the following example is broken, check this one instead: https://github.com/flutter/flutter/issues/117079#issuecomment-1353531070
~~Code snippet:
https://dartpad.dev/?id=41c3233072b062e4f754f253c4326da7~~

~~Code above produces a `Row` of a `VerticalDivider` and a `Column` that contains some 1-line `Text`s and an `Image`. You can tell by the visible height of the `VerticalDivider` the resulting height of the `Row` isn't right:
![image](https://user-images.githubusercontent.com/30569097/207671476-18f5b0ea-2412-426e-b37b-d48843c751b3.png)
Now change the line 40 from this
`width: 100,`
to this
`height: 100,`
and it corrects itself:~~
![image](https://user-images.githubusercontent.com/30569097/207671654-a8d87529-0a35-479b-ac40-9fd3360154c0.png)

~~Seems like `Image`s report their original height to `IntrinsicHeight` without considering that it could've changed due to custom `width` parameter. Changing its `height` pareameter, however, does the trick.~~
Repository: angular
Issue: Remove `@Component#moduleId` as it's a noop
Labels: area: core

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

core

### Is this a regression?

No

### Description

The `moduleId` field in `@Component` is not respected anymore, unlike back with View Engine where it was leveraged for composing a URL based on the module ID + relative URL segments.

`resolveComponentResources` as of Ivy does not respect it and we should remove this field to avoid confusion. Also the documentation/JSDoc mentions CommonJS `module.id` which is something we don't want to encourage.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_
Repository: material-ui
Issue: [Select] Can't fire a click event inside
Labels: bug 🐛,component: select

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Making the chips deleteable would seem to be a straightforward extension of [this example from the docs](https://mui.com/material-ui/react-select/#chip):

```
{selected.map((value) => (
   <Chip 
      key={value} 
      label={value}
      onDelete={(event) => {
        event.preventDefault()
        event.stopPropagation()
        setPersonName(personName.filter(name => name !== value))
      }} 
  />
))}
```




### Current behavior 😯

This fails because the chip never sees a click event -- it's intercepted by the Select, apparently. See [code sandbox example](https://codesandbox.io/s/wizardly-germain-6hvfws?file=/demo.tsx:1992-2382).

### Expected behavior 🤔

The chip should register a click event (which I can stop from propagating if I want).

It seems from [this issue](https://github.com/mui/material-ui/issues/27614) that the solution is to switch to an [Autocomplete](https://mui.com/material-ui/react-autocomplete/#multiple-values) instead. Ok, that looks like it will probably do what I want, but I have some code built around the `Select` component, and it's not clear why the Select needs to work differently here.

Is there some way to make this work with Select?

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```

  System:
    OS: Linux 5.4 Linux Mint 20.3 (Una)
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
    Memory: 895.32 MB / 15.33 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
    Yarn: 3.2.4 - ~/.yarn/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
    Watchman: 20210409.063814.0 - /usr/local/bin/watchman
  Managers:
    Cargo: 1.51.0 - ~/.cargo/bin/cargo
    pip3: 20.0.2 - /usr/bin/pip3
    RubyGems: 3.1.2 - /usr/bin/gem
  Utilities:
    CMake: 3.16.3 - /usr/bin/cmake
    Make: 4.2.1 - /usr/bin/make
    GCC: 9.4.0 - /usr/bin/gcc
    Git: 2.25.1 - /usr/bin/git
    FFmpeg: 4.2.7 - /usr/bin/ffmpeg
  Virtualization:
    Docker: 20.10.21 - /usr/bin/docker
  IDEs:
    Nano: 4.8 - /usr/bin/nano
    Vim: 0.4.3 - /usr/bin/vim
  Languages:
    Bash: 5.0.17 - /usr/bin/bash
    Java: 11.0.11 - /home/rct/.sdkman/candidates/java/current/bin/javac
    Perl: 5.30.0 - /usr/bin/perl
    Protoc: 3.17.0 - /usr/local/bin/protoc
    Python3: 3.8.10 - /usr/bin/python3
    Ruby: 2.7.0 - /usr/bin/ruby
    Rust: 1.51.0 - /home/rct/.cargo/bin/rustc
    Scala: 2.12.12 - /home/rct/.sdkman/candidates/scala/current/bin/scalac
  Databases:
    SQLite: 3.32.2 - /home/rct/Android/Sdk/platform-tools/sqlite3
  Browsers:
    * Chromium: 108.0.5359.94
    Firefox: 107.0.1
  Monorepos:
    Yarn Workspaces: 3.2.4
    Lerna: 5.6.2


```
</details>
Repository: vscode
Issue: Multi-Process Debugger isn't working on VSC 1.74
Labels: bug,debug,tasks

<!-- ⚠️⚠️ 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.74
- OS Version: Ventura 13.0.1

Steps to Reproduce:

1. Install MPI Debugger on your VSCode
2. Run a pytest with multiple processors using MPI.

The issue is we need multiple workers to connect to different debugging ports, thus needing a wait time so the debugging process can start correctly. This works on VSC 1.68 but on 1.74, all processes try to start on their own without waiting for others to connect to the debug ports.
Repository: create-react-app
Issue: CRA test environment no longer compatible with version 6.4.5 of react-router
Labels: needs triage,issue: bug report

### Describe the bug

For a detailed explanation of the problem, see https://github.com/remix-run/react-router/issues/9722#issuecomment-1351771473, which is the issue I originally opened.

CRA [automatically injects](https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/scripts/utils/createJestConfig.js#L33) [fetch](https://github.com/github/fetch) in the Jest test environment. Since [fetch](https://github.com/github/fetch) isn't spec-compliant (it does not expose a `body` property) it fail the [check](https://github.com/remix-run/react-router/pull/9690) introduced by react-router, version 6.4.5, thus making react-router misbehave.

A [suggestion](https://github.com/remix-run/react-router/issues/9722#issuecomment-1349669407) was made by @brophdawg11 to use [@remix-run/web-fetch](https://www.npmjs.com/package/@remix-run/web-fetch) instead, but this isn't necessarily easy to implement as there's no exposed entrypoints in CRA to inject the polyfill **before** [fetch](https://github.com/github/fetch) gets injected.
Repository: next.js
Issue: `'use client'` directive required for unused transpiled components.
Labels: bug

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: linux
      Arch: x64
      Version: Ubuntu 20.04.0 LTS Wed Dec 14 2022 14:26:31 GMT-0500 (Eastern Standard Time)
    Binaries:
      Node: 16.14.2
      npm: 7.17.0
      Yarn: 1.22.19
      pnpm: 7.13.6
    Relevant packages:
      next: 13.0.7-canary.6
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://stackblitz.com/edit/node-bbw2vp

### To Reproduce

1. Run `npx create-turbo@latest` to create the a boilerplate mono-repo structure with a component library and Next apps.
2. In `packages/ui`, create any component that uses code that would require the `'use-client'` directive. Export it from the package.
```
// ClientButton.tsx
import React, { useState } from 'react';

export const ClientButton = () => {
  const [count, setCount] = useState(0);

  return <button onClick={() => setCount((prev) => prev + 1)}>Beep {count}</button>;
};
```
3. In `apps`, run the `pnpm create next-app --experimental-app` tool for a Next app with the app directory features on, or add the corresponding config and folder to the existing ones.
4. Run `pnpm install ui --workspace` to install the ui package into the app, and add the package to the `transpilePackages`
```
/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    appDir: true,
    transpilePackages: ['ui'],
  },
};

module.exports = nextConfig;
```
5. In `page.tsx`, add the _normal_ button from the ui package. _Not_ the button with client side code.
```
// page.tsx
import styles from './page.module.css';
import { Button } from 'ui';

export default function Home() {
  return (
    <div className={styles.container}>
      <main className={styles.main}>
        <Button />
      </main>
    </div>
  );
}
```
6. Run `npm run dev`

### Describe the Bug

App fails to compile with:
```
You're importing a component that needs useState. It only works in a Client Component but none of its parents are marked with "use client", so they're Server Components by default.
```
Error message even when the code with client code isn't used by the app.

### Expected Behavior

When using the `transpilePackages` option, only code that is used by the app that requires it to be marked with `'use-client'` causes this error. Unused code does not cause this error.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: [web] Teach pointer_binding how to understand 3D transformed apps.
Labels: engine,customer: crowd,platform-web,a: mouse,P2,customer: quake (g3),team-web,triaged-web

Once Flutter web apps can be rendered in any custom element, they could potentially be rendered inside an element that has any number of 3D transforms applied to it.

The current implementation only supports 3D transforms if the app doesn't have platform views (with pointer-events), because those ["reset" the `offsetX/offsetY` of the pointer events](https://jsfiddle.net/ditman/xfogdmnu).

This is also a problem in events fired from TalkBack, since they don't contain `offsetX/offsetY` either.

The trick we use to solve this in a non-transformed app doesn't work in a transform-3d world.

There's two potential solutions:

* From the glassPane up (finish and apply [this WIP fix](https://jsfiddle.net/ditman/xeqLjvyr)).
* From the platform view to the glass pane (through flutter's Layer mechanism, apply a reverse transform from the current position of the platform view to retrieve the glass pane position)
Repository: flutter
Issue: Support fixture tests on Linux
Labels: a: tests,engine,platform-linux,a: desktop,P2,c: tech-debt,team-linux,triaged-linux

Add support for writing and running Dart fixture tests for the Linux embedder in the engine repo. 

This is the Linux analogue to https://github.com/flutter/flutter/issues/87299.
Repository: flutter
Issue: [web] Cleanup: Remove code paths where visualViewport may be null.
Labels: engine,platform-web,P2,c: tech-debt,team-web,triaged-web

Remove the code paths where `visualViewport` may be null.

This is only needed for older versions of Safari (Safari 12) that are getting harder and harder to support and test for.

Some examples:

* https://github.com/flutter/engine/blob/256dc78f6d4f868d3f3fe66cfe34da799b0c321e/lib/web_ui/lib/src/engine/window.dart#L237-L240
* https://github.com/flutter/engine/blob/256dc78f6d4f868d3f3fe66cfe34da799b0c321e/lib/web_ui/lib/src/engine/embedder.dart#L329-L358
* https://github.com/flutter/engine/blob/256dc78f6d4f868d3f3fe66cfe34da799b0c321e/lib/web_ui/lib/src/engine/embedder.dart#L363-L366
Repository: flutter
Issue: LUCI shards bury the results behind several clicks
Labels: a: quality,team-infra,P2,triaged-infra

For example, https://github.com/flutter/engine/pull/38148:

![2022-12-14-132345_1094x239_scrot](https://user-images.githubusercontent.com/551196/207717744-ce1dfb39-b813-4d53-9b99-eb24a6ecf907.png)

click [Details](https://github.com/flutter/engine/pull/38148/checks?check_run_id=10100711869:) (this is where I'd expect to stop)

![2022-12-14-132145_950x419_scrot](https://user-images.githubusercontent.com/551196/207717407-24b82935-938e-40f2-afa2-a25042fcf02f.png)

click [View more details on flutter-dashboard](https://ci.chromium.org/b/8794769693634341441)

![2022-12-14-132451_1146x690_scrot](https://user-images.githubusercontent.com/551196/207717942-e316306a-d3ae-449e-ab9b-55667e57ccd8.png)

Click one of the [stdout](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8794769693634341441/+/u/test:_Host_Tests_for_host_profile/stdout) links

![2022-12-14-132854_1080x600_scrot](https://user-images.githubusercontent.com/551196/207718678-49b0274e-473c-42f6-8828-05fe88bcc334.png)

...and scroll to the bottom, then back up until you find what failed.

It would be nice if instead the logs were shown in the Checks page on GitHub (where I say above that I'd expect to stop).
Repository: rust
Issue: Type inference does not work properly when `if let` are nested
Labels: A-diagnostics,T-compiler

<!--
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.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=b0862a23f73c8693280c892ffaf1014b

The current output is:

```
Compiling playground v0.0.1 (/playground)
error[[E0282]](https://doc.rust-lang.org/stable/error-index.html#E0282): type annotations needed
  --> src/main.rs:22:38
   |
22 |             let command: Vec<&str> = h.command.split_ascii_whitespace().collect();
   |                                      ^^^^^^^^^ cannot infer type

error[[E0609]](https://doc.rust-lang.org/stable/error-index.html#E0609): no field `command` on type `&_`
  --> src/main.rs:22:40
   |
22 |             let command: Vec<&str> = h.command.split_ascii_whitespace().collect();
   |                                        ^^^^^^^

Some errors have detailed explanations: E0282, E0609.
For more information about an error, try `rustc --explain E0282`.
error: could not compile `playground` due to 2 previous errors
```

When I change the line 20 like this:
```
    if let Ok(i) = input.parse::<usize>() {
```

The type inference error disappears and the code compiles.
The problem seems to be in `parse()`, where the first `if let` does not give the proper type for `i`: the `h` on lines 21-22 are irrelevant to this problem.
So it would be better to make the error output to say to add a type annotation for `parse()`.
Repository: pytorch
Issue: Support arbitrary masks for _nested_tensor_from_mask in nn.TransformerEncoder
Labels: module: nn,triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

I am working on transformers and am using the Better Transformer. To enjoy the speed improvement, we need to pass a src_key_padding_mask to the nn.TransformerEncoder.

The problem is that, the src_key_padding_mask has to be left-aligned, which means all True values must be in front of all False values. That is the common case in NLP as sentences have different lengths, but in computer vision, the True values in a mask are usually arbitrarily dispersed. I am wondering if you could support transforming a tensor with an arbitrary mask to a nested tensor, and also support transforming the nested tensor back to a normal tensor with 0 paddings according to the same mask.

This feature would be very useful for vision transformers when people want to use masks and enjoy the inference speed improvement for whatever their tasks, for example, dynamic pruning, etc.

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @cpuhrsch @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ @erichan1 @kshitij12345 @saketh-are
Repository: flutter
Issue: DlMaskFilter does not have a bounds method
Labels: engine,P3,team-engine,triaged-engine

The bounds calculation code (currently in [DisplayListBoundsCalculator](https://github.com/flutter/engine/blob/df430c4fd80c8a3e19fd33fae61623cd1577c762/display_list/display_list_utils.cc#L751), but soon [moving to DisplayListBuilder](https://github.com/flutter/engine/pull/34365)) hard-codes modifying the bounds of a primitive by a DlMaskFilter, but really this code should be a method on the DlMaskFilter class.
Repository: godot
Issue: Serialized value in Dictionary is treated as inferred type from .tscn and not the script
Labels: discussion,topic:core,topic:editor

### Godot version

v3.5.stable.official [991bb6ac7]

### System information

Windows 10 build 19045, GLES3

### Issue description

When a serialized value in a `Dictionary` is deserialized and shown in the inspector, whatever type is inferred at that time is forced in the inspector even if it does not match the type of the default value for that key in the dictionary.

test.gd:
```
extends Node2D

export (Dictionary) var test_dict = {
	"a": 1.0,
	"b": 0.0,
}
```

main.tscn:
```
[gd_scene load_steps=2 format=2]

[ext_resource path="res://test.gd" type="Script" id=1]

[node name="Node2D" type="Node2D"]
script = ExtResource( 1 )
example = {
"a": 1.0,
"b": 1
}
```

When the node above is loaded, key `b` in the inspector will not accept float values until the entire property is reset. I don't know if this is technically a bug, per se, but it is odd to stumble into.

### Steps to reproduce

1. Create a script exporting a `Dictionary` with a default numeric value
2. Save a node with that script attached
3. Change the script so that the key has a different implied type
4. Reload the saved node and try to edit that value in the inspector

The inspector ignores the implied type in the script.

### Minimal reproduction project

n/a
Repository: rust
Issue: `run-pass` tests should be disabled for non-executable producing targets
Labels: A-testsuite,T-bootstrap,C-bug

Currently run-pass tests are enabled for non-executable producing targets. This results in a lot of expected failures when running `./x.py test` and forces us to use `./x.py test --run never` for these targets. IMO this should be the default behavior.

Here's a sample target-spec based on `aarch64-unknown-none` with `"executables": false` set.

```json
{
  "arch": "aarch64",
  "data-layout": "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128",
  "disable-redzone": true,
  "features": "+strict-align,+neon,+fp-armv8",
  "is-builtin": true,
  "linker": "rust-lld",
  "linker-flavor": "ld.lld",
  "llvm-target": "aarch64-unknown-none",
  "max-atomic-width": 128,
  "panic-strategy": "abort",
  "relocation-model": "static",
  "target-pointer-width": "64",
  "executables": false
}
```

I expected to see this happen: *`run-pass` tests are ignored and failing tests specific for this target should be presented.*

Instead, this happened: *Static libraries are generated for `run-pass` tests and test fails for all of them saying `fn main()` is never used and causes test failures due to `dead_code` lint. This is an expected failure since we don't ever want to generate executables with main for this target.*



Possible solution: `./x.py test` should expand to `./x.py test --run never` for targets that *CANNOT* produce executables.
Repository: excalidraw
Issue: display error if saving to firestore throws
Labels: UX/UI

Such as due to the 1MB limit, but also in general. We must make sure users are let known that their data were not saved when collaborating.
Repository: stable-diffusion-webui
Issue: [Feature Request]: "Resize and mask" option for img2img inpainting tab
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

When inpaint is on, it should act the same as "resize and fill", but mask the filled space after that. If inpaint is off, and you select this in img2img, it would behave as a regular "resize and fill" to prevent errors.
It could be extremely useful in many different situations, mostly as a quick, cheap and dirty outpaint replacement for aspect ratio change.

Currently you can only mimic this behaviour by running img2img with very low denoising and "resize and fill" mode, then transfer to inpaint, manually mask filled area and run it.
It could be so much better with this option in UI, and there should be a lot of space for a new button even when viewed in 4:3 monitor.

### Proposed workflow

1. Go to img2img
2. Go to "Inpaint" tab
3. Select your inpainting settings as usual
4. Upload image with non-matching aspect ratio
5. Select "resize and mask" in resizing switch row
6. Run SD pass, recieving image with already inpainted filled sections.


### Additional information

_No response_