sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: For C# script,  the editor always append generated function signature to the end of file when connecting signal, even if the method already exists.
Labels: bug,topic:editor,usability,topic:dotnet

### Godot version

4.1-dev

### System information

macOS 13.3 M1 Pro

### Issue description

Related to https://github.com/godotengine/godot/issues/18721. 

I'm using C# for scripting. When I connect signal from editor, the editor always append generated function signature to the end of file, even if the method already exists.

I look at the code and found the editor DOES check the existance of method before try to modify script source.
https://github.com/godotengine/godot/blob/605e25656f81b8683d4bd0a521840c0f025a9136/editor/connections_dialog.cpp#L873

I can pick a method of C# class, but ClassDB::has_method returns false.
I tried to modify the code and found ClassDB::has_method and Script::has_method returns different result at this point.

I'm not sure if this behaviour is expected, but it looks strange.


### Steps to reproduce

Modify the source, check Script::has_method after ClassDB::has_method returns false.

```cpp
if (!scr.is_null() && !ClassDB::has_method(target->get_class(), cd.method)) {
    if (scr->has_method(cd.method)) {
	throw "Why";
    }
 //...
}
```

The exception will be triggered when try to pick and connect a signal to an existing C# method.

### Minimal reproduction project

The godot source code.
Repository: flutter
Issue: [go_router] Figure out how to deal with inline GoRouter creation in MaterialApp.router
Labels: package,P3,p: go_router,team-go_router,triaged-go_router

### 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

It is possible to create GoRouter inline with MaterialApp
```dart
void main() {
  runApp(MaterialApp.router(routerConfig: GoRouter()));
}
```

This will break hot reload because the gorouter will be recreate and loss all its state.

Another example is

```dart
class MyWidget extends StatelessWidget {
  @override
  Widget build(context) {
    return MaterialApp.router(routerConfig: GoRouter());
  }
}
```

Which would lose the state every time MyWidget is rebuilt.

### Proposal

We should figure out how to avoid this situation. One idea can be writing a lint to warn user and advise putting the goRouter into a permanent variable
Repository: pytorch
Issue: torch.quantile on MPS doesn't sort values when dim is not None
Labels: triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

MPS implementation of `torch.quantile` doesn't sort the input when there's the `dim` argument is not `None`, giving nonsense results.

```
import torch
device = torch.device("mps")
A = torch.randn(1000, 10)

#need to use "nearest", "lower", or "higher" interpolation methods
#"linear" and "midpoint" fail due to operator `aten::lerp.Tensor_out` not being implemented for MPS
#when dim=None, CPU and MPS give same result
torch.quantile(A, .5, interpolation = "nearest")
torch.quantile(A.to(device), .5, interpolation = "nearest")

#when dim is not None, MPS gives nonsense result
torch.quantile(A, .5, 0, interpolation = "nearest")
torch.quantile(A.to(device), .5, 0, interpolation = "nearest")

#MPS output is same as middle row of tensor
#so torch.quantile must just be pulling 500th index without sorting first
A[500]

#inelegant workaround is to sort the tensor before calling quantile
torch.quantile(torch.sort(A.to(device), dim = 0).values, .5, 0, interpolation = "nearest")
```

### Versions

PyTorch version: 2.0.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 13.3.1 (x86_64)
GCC version: Could not collect
Clang version: 14.0.6
CMake version: version 3.22.1
Libc version: N/A

Python version: 3.11.3 (main, Apr 19 2023, 18:51:09) [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M2 Pro

Versions of relevant libraries:
[pip3] numpy==1.24.3
[pip3] torch==2.0.1
[pip3] torchmetrics==0.11.4
[conda] nomkl                     3.0                           0  
[conda] numpy                     1.24.3          py311hd0e4f0d_0  
[conda] numpy-base                1.24.3          py311h947b413_0  
[conda] torch                     2.0.1                    pypi_0    pypi
[conda] torchmetrics              0.11.4                   pypi_0    pypi

cc @ezyang @gchanan @zou3519 @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: next.js
Issue: Browser caching doesn't work if the page contains a Link to itself
Labels: Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
# npx next info

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Wed, 26 Apr 2023 20:50:14 +0000
    Binaries:
      Node: 18.14.2
      npm: 9.1.2
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.3-canary.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

warn  - Latest canary version not detected, detected: "13.4.3-canary.3", newest: "13.4.3".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue or a replay of the bug

https://gist.github.com/szmarczak/4cf98e97c1f25693fedf1b1d4efbe45c#file-page-tsx

### To Reproduce

`npx create-next-app` and replace `app/page.tsx` with the file above.


### Describe the Bug

Next.js sends a request to the `Link` destination with a `content-type` of `text/x-component`. Expectedly, two different ETags are generated. However, since the destination is the same as the current page, there is a conflict:

```
/ { etag: 'A', 'content-type': 'text/html; charset=utf-8' } // browser now stores response only for A
/ { etag: 'B', 'content-type': 'text/x-component' }         // browser now stores response only for B
[refresh]
/ { etag: 'A', 'content-type': 'text/html; charset=utf-8' } // MISS, as browser remembers only B and after the page loads it remembers only A
/ { etag: 'B', 'content-type': 'text/x-component' }         // MISS, as browser remembers only A and after the page loads it remembers only B
```

As per [RFC 9111](https://www.rfc-editor.org/rfc/rfc9111#name-overview-of-cache-operation) browsers don't have to use `content-type` for key computation:

```
many HTTP caches in common use today only cache GET responses and therefore only use the URI as the cache key.
```

### Expected Behavior

`304 Not Modified` instead of `200 OK`

### Which browser are you using? (if relevant)

not relevant

### How are you deploying your application? (if relevant)

not relevant
Repository: kubernetes
Issue: Implement common interface in applyconfigs to make them identifiable as such
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Make all generated applyconfigs implement some common interface that makes them identifiable as such, similiar to `runtime.Object`. How exactly that interface looks doesn't matter, it could be a simple `IsApplyConfig() bool`.

### Why is this needed?

In order to be able to offer a good UX for SSA, dynamic clients such as controller-runtimes need a first-class `Apply` or similiar method. In order for that method to be easy to use, it needs to only accept applyconfigs. Because applyconfigs do not implement a common interface, this isn't possible today and such a method needs to accept `any`.
Repository: flutter
Issue: Clarify support for virtualized environments in documentation.
Labels: d: api docs,P2,team-engine,triaged-engine

Flutters ["Supported deployment platforms"](https://docs.flutter.dev/reference/supported-platforms) page makes no mention of virtualized environments. I suspect it is "Best Effort" at best. Though I doubt the Flutter Engine team at Google can even say this with confidence since the policies on running virtualization software on Google issued hardware are so restrictive.

But [virtualization is common on CI environments](https://github.com/flutter/flutter/issues/126768#issuecomment-1554622884) and is going to be used no matter the support level. Beyond the call to document the support for such environments, we should investigate how to bring this to at least the "Best Effort" level.

We go to great lengths to support some test environments to the point where some stuff running on CI is significantly different from whats deployed on devices. So I don't think we should (or can) restrict virtualization environments. We just need to document our support and occasionally be able to debug on environments we know developers will run applications on.
Repository: vscode
Issue: Incorrectly placed diff scrollbar
Labels: diff-editor

Type: <b>Bug</b>

When diff editor have "Non ASCII Highlight" banner, then diff scrollbar placed incorrectly and cover most of close banner button.

VS Code version: Code - Insiders 1.79.0-insider (2d416df5f00253f5ebd60d2f08508a440747fd8d, 2023-05-19T05:25:00.632Z)
OS version: Windows_NT x64 10.0.22621
Modes: Restricted

Extensions: none
<!-- generated by issue reporter -->
![Screenshot (1)](https://github.com/microsoft/vscode/assets/17184058/efa203b5-a9d1-43bc-85df-dd3d392fbd86)
![Screenshot (2)](https://github.com/microsoft/vscode/assets/17184058/1e470b02-7828-4a12-925d-2a16dadc3419)
Repository: go
Issue: net/http: TestContentEncodingNoSniffing failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestContentEncodingNoSniffing"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/580b3e9b417939ab1acd6fdad42c954ca812f0a7)):

    2023/05/19 13:26:16 httptest.Server blocked in Close after 5 seconds, waiting for connections:
      *net.TCPConn 0xc000190548 127.0.0.1:50294 in state active
    2023/05/19 13:26:25 httptest.Server blocked in Close after 5 seconds, waiting for connections:
    --- FAIL: TestContentEncodingNoSniffing (0.00s)
        --- FAIL: TestContentEncodingNoSniffing/h1 (10.26s)
            --- FAIL: TestContentEncodingNoSniffing/h1/zlib_content-encoding,_zlibbed (10.10s)
                serve_test.go:6222: Failed to fetch URL: Get "https://127.0.0.1:50731": unexpected EOF


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: nvm
Issue: Support for Custom Patches and Environment Files in nvm
Labels: installing node,feature requests

 I am using an experimental Gentoo setup with LLVM/Clang as the default compiler and without GCC. In this environment, I have encountered some issues while trying to use different versions of Node.js with nvm.

To make Node.js versions work correctly in such environments, it would be extremely helpful if nvm supported the application of custom patches. I would like to propose the implementation of a patch directory, perhaps located at .nvm/patches/${patchname}.patch, where users could place patches to address compatibility issues specific to their environment.

Additionally, having an environment file, such as .nvm/env, would be beneficial. This file would allow users to define custom environment variables like CC=clang++ and CXX=clang++, which would be automatically sourced by nvm when switching between Node.js versions. This would simplify the process and make it more expeditious for users in similar situations.

I understand that this feature may be applicable to only a few situations, but I believe it could greatly assist users working with non-standard setups, particularly those utilizing LLVM/Clang as the primary compiler without GCC.

While I recognize that this request is not urgent, I believe that implementing these features could not only resolve my own challenges, but also help others facing similar issues in the future.
Repository: flutter
Issue: [Impeller] Optimize surfaces / offscreen buffers to be 40 bits/pixel.
Labels: engine,c: proposal,P3,e: impeller,team-engine,triaged-engine

[When investigating the regression](https://github.com/flutter/flutter/issues/127118) in performance caused by wide gamut support we found two things:
1) The regression didn't show up on A15, but did on A13
1) The majority of additional time was in the blur fragment shader

We knew 64 bits/pixel is documented to be slower.  Apple's recommendation is to use 40bits/pixel instead (a BGR10_XR color buffer with an u8 alpha buffer).  That should make those operations faster.

The difficulty with that change is that using that scheme would require:
1)  a second set of shaders since it would be reading from 2 samplers to get full color
1) all the logic that uploads and downloads textures would have to be updated to manage two textures
1) the blit operations to the surface would need to be updated to do 2 blits
1) the surface would have to be changed to match the 40bits/pixel scheme

Maybe in a future where we don't have to support non-wide gamut devices it will be more palatable to throw away the old code and just embrace the 40bits/pixel path.  However, it seems that in that same future the cost of 64bits/pixel vs 40bits/pixel is negligible.  64 bits/pixel may even be faster on newer hardware since it's just using one sampler.

cc @jonahwilliams
Repository: next.js
Issue: next/image fill sets image width to browser width instead of parent
Labels: bug,Image (next/image)

### 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 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
  Binaries:
   Node: 18.14.0
   npm: 9.3.1
   Yarn: 1.22.19
   pnpm: 8.4.0
  Relevant packages:
   next: 13.4.3
   eslint-config-next: 13.0.6
   react: 18.2.0
   react-dom: 18.2.0
   typescript: 5.1.0-beta
```


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

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/loving-payne-qk8vmk?file=%2Fapp%2Fpage.tsx%3A12%2C77

### To Reproduce

The code is linked in the codesandbox.

1) Go to https://qk8vmk-3000.csb.app/ on a wide desktop browser (1920 or wider to see problem)
2) See the two Image components
3) Open up Network tab and reload
4) See the 2 network calls to the image
5) The first call (the one with the "fill" and relative parent): https://qk8vmk-3000.csb.app/_next/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1538991383142-36c4edeaffde%3Fixlib%3Drb-4.0.3%26ixid%3DM3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%253D%253D&w=1920&q=75
6) The second call (Image with the fixed width/height): https://qk8vmk-3000.csb.app/_next/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1538991383142-36c4edeaffde%3Fixlib%3Drb-4.0.3%26ixid%3DM3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%253D%253D&w=640&q=75
7) Notice the difference in the urls. The first one has `w=1920` while the second has `w-640`

### Describe the Bug

Image component with "fill" property does not load the proper image size, leading for heavier image than desired.
For example:
```
<div style={{ width: "480px", height: "320px", position: "relative" }}>
          <Image
            alt="pic"
            src="https://images.unsplash.com/photo-1538991383142-36c4edeaffde?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D"
            fill
          />
</div>
```

### Expected Behavior

<Image fill> with relative parent should not use the browser's max width for the `w=?` query. It should determine the width from its parents.

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

_No response_

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

_No response_
Repository: godot
Issue: Conditionally exported variable set in editor runtime but not exported runtime
Labels: bug,discussion,topic:editor

### Godot version

4.0.3

### System information

Windows 11

### Issue description

When conditionally exporting a variable using `_get_property_list`, the variable is set in the editor runtime but not in the exported runtime.

While debugging, you may have to close the scene and re-open it to prevent false positives.

### Steps to reproduce

1. Download the minimal repro
2. Open the project and press run project
3. You will see "Passed!" rendered in a window because the test passes
4. Now export the project (I exported to windows) and run it
5. You will see "Failed" because the test has failed

### Minimal reproduction project

[dynamic-export-bug.zip](https://github.com/godotengine/godot/files/11520867/dynamic-export-bug.zip)
Repository: vscode
Issue: Remote integration test timeout: replaceOutput to different cell
Labels: bug,integration-test-failure,notebook

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=215315&view=logs&j=9833cdaa-2e92-5f8d-56a8-239fd18fd628&t=efbaf268-cf98-50c2-bb3c-7950770fd6bc&l=490
Repository: flutter
Issue: Flutter assumes all linux is debian-based.
Labels: tool,platform-linux,c: proposal,P3,team-tool,triaged-tool

### 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)

### Steps to reproduce

1. Be using a non-debian-based linux distro that does not have the esoteric `unzip` command available.
2. Have flutter installed.
3. Have there be a newer version of flutter available.
4. Attempt to upgrade via the `flutter upgrade` command.

### Actual results

![image](https://github.com/flutter/flutter/assets/99218361/669c33d9-dbc2-41cc-bc3b-cff44e546a12)

While I think this is cute it is also unhelpful and inflexible. My system already has `bsdtar` so I could easily decompress the file _without_ a command/package named `unzip`.

What would be great is that instead of a failure, there would be some sort of stop-gap where it explains where the compressed file is, where to extract it and how to continue after that is done.

Nevertheless I just wanted to bring this oversight to the attention of the crew because I doubt it is a large impediment for those on non-debian-based systems, just an annoyance really.

### Logs

<details>
<summary>Logs</summary>

```console

$ flutter upgrade
Upgrading Flutter to 3.10.1 from 3.7.10 in /home/loki/projects/flutter...

Missing "unzip" tool. Unable to extract Dart SDK.
Consider running "sudo apt-get install unzip".

```

</details>


### Flutter Doctor output

<details>
<summary>Doctor output</summary>

```console

Missing "unzip" tool. Unable to extract Dart SDK.
Consider running "sudo apt-get install unzip".

```

</details>
Repository: terminal
Issue: REP of SP characters produces incorrect results
Labels: Help Wanted,Area-Output,Issue-Bug,Product-Terminal

### Windows Terminal version

1.17.1023

### Details

1.16.10261 had significant problems with REP of Unicode block graphics and other such characters.  That's mostly fixed in 1.17.1023, with one exception: REP of Supplementary Plane characters still produces incorrect results, with the characters repeated in the wrong places on the line or sometimes not at all.

I've experienced this with MouseText characters like U+0001FB81 in particular, and have not (of course!) tested every SP code point.

[I did some screenshots.](https://tty0.social/@JdeBP/110307055376583641)
Repository: rust
Issue: Compilation regression on nightly with `i686-unknown-linux-gnu`
Labels: P-low,T-compiler,regression-from-stable-to-stable,C-bug,O-x86_32

An existing Tokio test started to fail with a stack overflow when updating nightly on target `i686-unknown-linux-gnu`

https://github.com/tokio-rs/tokio/actions/runs/5029230797/jobs/9020678779?pr=5706


### Code

This test started failing on the latest nightly:

https://github.com/tokio-rs/tokio/blob/master/tokio/src/sync/mpsc/block.rs#L433-L448

To run the test, from the `tokio` directory in the Tokio repo:

`cross +nightly test --all-features --target i686-unknown-linux-gnu --lib mpsc::block -- --nocapture`

### Version it worked on

Version 1.69

### Version with regression

rustc 1.71.0-nightly (d3f416dc0 2023-05-18)
Repository: material-ui
Issue: [ESM] Feature a distribution compatible with Node in "type": "module"
Labels: breaking change,enhancement,scope: code-infra


### Steps to reproduce 🕹

Hi MUI team,

**Steps to Reproduce:**

You can reproduce the problem using the below repository:

```shell
git clone https://github.com/garronej/mui-import-esm  
cd mui-import-esm
yarn install
node index.mjs
```

### Current behavior 😯

Node is unable to import MUI in the type: "module" environment.

We're getting `Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/Users/joseph/github/mui-import-esm/node_modules/@mui/material/styles'` when importing any submodule of `@mui/material`.  



### Expected behavior 🤔

MUI should be correctly imported when running under Node's ESM environment.

### Context 🔦

As the publisher of modules that depend on MUI, such as [tss-react](https://github.com/garronej/tss-react) and [onyxia-ui](https://github.com/InseeFrLab/onyxia-ui), I've encountered some problems with distributing real ECMAScript Modules (ESM) due to MUI's lack of a functional ESM distribution compatible with a `"type": "module"` node environment. While MUI does provide an ESM distribution that works with bundlers, it unfortunately fails to do the same for node. 

## Proposed Solutions:  

To resolve the above issue, an additional entry to `node_modules/@mui/material/package.json` could potentially fix the problem:

```json
  "exports": {
    "./styles": {
      "default": "./node/styles/index.js"
    },
    "./Button": {
      "default": "./node/Button/index.js"
    }
  }
```

Implementing this works for `import { useStyles } from "@mui/material/styles"` but doesn't function correctly for `import Button from "@mui/material/Button"`. This issue arises as Button is represented as an object, rather than as the default function.

For the above scenario, there are two possible strategies:

- Adopt @Andarist's Emotion strategy: Expose a .mjs file that reexports everything from the CommonJS ESModuleInterop distribution (See an example [here](https://unpkg.com/browse/@emotion/styled@11.11.0/dist/emotion-styled.cjs.mjs)). This strategy allows for correct defaults. And avoiding the dual package hazard. MUI also stands to gain nothing by being a real ESM, as it does not support lazy imports.

- Publish a full, standards-compliant ESM distribution: Similar to [tsafe](https://github.com/garronej/tsafe/blob/6d08839c3b0695edbc3443d21b256043cd98787b/package.json#L12).

The popularity of [this comment](https://github.com/mui/material-ui/issues/27120#issuecomment-925660165) based on its upvotes demonstrates that other developers are experiencing similar issues.

Regardless, I appreciate all the hard work done by the MUI team. Thank you!

### Your environment 🌎

_No response_