sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `powerpc64-unknown-freebsd` version in ports has patches to ELF version support and target description
Labels: T-compiler,O-freebsd,O-PowerPC,C-feature-request

The packaged version of rust in FreeBSD patches their release with

```diff
--- compiler/rustc_target/src/abi/call/powerpc64.rs.orig	2020-03-09 22:11:17 UTC
+++ compiler/rustc_target/src/abi/call/powerpc64.rs
@@ -123,7 +123,7 @@ where
         ELFv2
     } else {
         match cx.data_layout().endian {
-            Endian::Big => ELFv1,
+            Endian::Big => ELFv2,
             Endian::Little => ELFv2,
         }
     };
```

https://cgit.freebsd.org/ports/tree/lang/rust/files/patch-compiler_rustc__target_src_abi_call_powerpc64.rs

Immediately before that we have the following:

```
    let abi = if cx.target_spec().env == "musl" {
        ELFv2
    } else {
```

We can add yet another check for them there so that `powerpc64-unknown-freebsd` always uses ELFv2. The platform list page shows this one as "PPC64 FreeBSD (ELFv1 and ELFv2)" on Tier 3.

I do not know if doing this change would cause other issues, maybe with lowest FreeBSD version support?

They've been [carrying this patch since 2019](https://github.com/freebsd/freebsd-ports/commit/2fe55654450880a88824c4b2e80a8ac8a01328ba#diff-bfb7745777d4630ab4f6eec0645cafd9daf37c1a00bb617a76358702110fccc5).

----

https://github.com/freebsd/freebsd-ports/blob/9c64647054c81b8876c7f4f987189427b5858ad6/lang/rust/files/patch-compiler_rustc__target_src_spec_powerpc64__unknown__freebsd.rs#L1-L14

[Since 2020](https://github.com/freebsd/freebsd-ports/commit/b0f1d6430efe60a7d9a3aa11e8ed28a80842469b#diff-104ba766b96e41f5a29bd8cdc26a903b85e34bb38b7de4dd7d4b8adf8fdd17eb).
Repository: rust
Issue: `i686-unknown-freebsd` uses `base.cpu = "pentium4"` but the version in ports patches it to be `base.cpu = "pentiumpro"
Labels: T-compiler,O-freebsd,O-x86_32

https://github.com/freebsd/freebsd-ports/blob/2ed61cbd3997f268d71b7df2a27d026aabb76477/lang/rust/files/patch-compiler_rustc__target_src_spec_i686__unknown__freebsd.rs#L1C4-L11

They've been [carrying this patch since 2017](https://github.com/freebsd/freebsd-ports/commit/d65b2886b1b3b2135f0b8982de4d9754517acf61#diff-9eaed7e3b6a7decc61e5427ee0039891c95f8b37f4e9f2683931d4281dadecbf).
Repository: rust
Issue: `riscv64-unknown-freebsd` patches backtrace support out
Labels: T-compiler,O-freebsd,O-riscv

https://github.com/freebsd/freebsd-ports/blob/main/lang/rust/files/patch-library_backtrace_src_backtrace_mod.rs

[Since late 2021](https://github.com/freebsd/freebsd-ports/commit/237b36fa2e73986dc19284686e80a47cb329bb6f#diff-5514813830c9c7150682ca335cc6b1817d4ec987192ce909d3434a241115cda8).
Repository: deno
Issue: `readAll` deprecation documentation needs improvement
Labels: docs

The docs for https://deno.land/api@v1.37.2?s=Deno.readAll say that it is deprecated, and send you to `deno_std` (https://deno.land/std@0.204.0/streams/read_all.ts).

`deno_std` says that "`readAll` (will be removed after 1.0.0) Use ReadableStream and toArrayBuffer instead."

There is no further link or example to understand how to use `ReadableStream` and `toArrayBuffer` from this page.

Ideally the docs for `Deno.readAll` and `readAll`/`readAllSync` would show how to use `ReadableStream` and `toArrayBuffer` (https://deno.land/std@0.204.0/streams/mod.ts?s=toArrayBuffer).
Repository: PowerToys
Issue: Color Picker HDR Display Support
Labels: Idea-Enhancement,Help Wanted,Product-Color Picker

### Description of the new feature / enhancement

When I use color picker on an HDR (High Dynamic Range) display, because of the increased dynamic range color picker is often reading as #ffffff, or white, or another brightened color. This is true of SDR content that has been brightened up to HDR by windows using the slider in the HDR settings. If the color picker could bypass these settings to find the original color of the pixel that would be amazing.

### Scenario when this would be used?

It is tedious to have to drag a window over to an SDR display if the user even has one. While it would likely be more difficult to get it to work with true HDR content that hasn't been converted from SDR, support for the basic feature of finding the original color of SDR content would assist users workflow greatly.

### Supporting information

_No response_
Repository: godot
Issue: ArrayMesh or ImmediateMesh are not cooperating with MeshInstance3D
Labels: discussion,needs testing

### Godot version

Tested on 4.0, 4.1.2 and 4.2

### System information

Windows 10, Intel iris plus

### Issue description

I am trying to generate mesh using ArrayMesh or ImmediateMesh (I've try both). Mesh seams to be ok, because when I saved it as a resource - it is displayed properly, but when I am trying to use it dynamicly in game, nothing happens whatever I do.
Details are on stackoverflow: https://stackoverflow.com/questions/77351955/godot-procedural-mesh-generation

Edit: It works in godot 3.5, so... probably bug

### Steps to reproduce

Copy that code: https://stackoverflow.com/questions/77351955/godot-procedural-mesh-generation
Create a simple scene setup with dir. light, camera and Chunk (assign a ChunkMesh to it).

### Minimal reproduction project

[Octree.zip](https://github.com/godotengine/godot/files/13169633/Octree.zip)
Repository: node
Issue: deepStrictEqual diff is unhelpful when prototype mismatches
Labels: test_runner

### Version

v20.8.0

### Platform

Darwin Me.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:34 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T8103 arm64

### Subsystem

_No response_

### What steps will reproduce the bug?

Given `repo.js`

```js
import { test } from "node:test";
import { deepStrictEqual, notDeepStrictEqual } from "node:assert";

class ExtendedArray extends Array {
  constructor() {
    super();
  }
}

test("deepStrictEqual should print prototype diff", () => {
  const actual = new ExtendedArray();
  actual[0] = "hello";
  const expected = ["hello"];

  notDeepStrictEqual(
    Object.getPrototypeOf(actual),
    Object.getPrototypeOf(expected)
  );

  deepStrictEqual(actual, expected);
});
```

Run `node --test repo.js`.

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior? Why is that the expected behavior?

deepStrictEquals requires actual and expected to have the same prototype, but fails to show error message describing if they are not the same.

A more helpful diff would be:
```
$ node --test repo.js
✖ deepStrictEqual should print prototype diff (1.581625ms)
  AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
  + actual - expected
  
  + ExtendedArray(1) [
  - [
      'hello'
    ]
      at TestContext.<anonymous> (file://.../repo.js:20:3)
      at Test.runInAsyncScope (node:async_hooks:206:9)
      at Test.run (node:internal/test_runner/test:631:25)
      at Test.start (node:internal/test_runner/test:542:17)
      at startSubtest (node:internal/test_runner/harness:208:17) {
    generatedMessage: true,
    code: 'ERR_ASSERTION',
    actual prototype: Array {}
    expected prototype: Object(0) [],
    operator: 'deepStrictEqual'
  }
```

### What do you see instead?

Only the contents of the arrays are diffed.

```
$ node --test repo.js
✖ deepStrictEqual should print prototype diff (1.581625ms)
  AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
  + actual - expected
  
  + ExtendedArray(1) [
  - [
      'hello'
    ]
      at TestContext.<anonymous> (file://.../repo.js:20:3)
      at Test.runInAsyncScope (node:async_hooks:206:9)
      at Test.run (node:internal/test_runner/test:631:25)
      at Test.start (node:internal/test_runner/test:542:17)
      at startSubtest (node:internal/test_runner/harness:208:17) {
    generatedMessage: true,
    code: 'ERR_ASSERTION',
    actual: [ 'hello' ],
    expected: [ 'hello' ],
    operator: 'deepStrictEqual'
  }
```

### Additional information

_No response_
Repository: terminal
Issue: Cursor width should respect dpi settings
Labels: Help Wanted,Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-3,Area-AtlasEngine

### Windows Terminal version

1.18.2822.0

### Windows build number

10.0.22621.0

### Other Software

None

### Steps to reproduce

Set display scale to 200% and use the bar cursor.

### Expected Behavior

Cursor width should respect dpi settings.

### Actual Behavior

On 200% scale monitor, drawing the bar shape cursor use native 1px, not 1 logical pixel (2px). This makes it a little hard to locate, especially in light theme.

screenshots: terminal, WinUI control, browser <textarea>

![screenshots](https://github.com/microsoft/terminal/assets/402471/9cefbfda-402a-4de9-a29f-fa0637634be3)
Repository: vscode
Issue: Installation trigger for Python extension when Python language is detected in an untitled file 
Labels: feature-request,extensions,extension-recommendations

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Current behavior: If a user opens a Python file (.py) or saves a file with a .py extension and does not have the Python extension installed, VS Code suggests installing the Python extension for Python support. 
<img width="236" alt="image" src="https://github.com/microsoft/vscode/assets/60238438/745eb7ee-3ae3-425d-b0d1-0b0754a49e12">

Proposed behavior: 
It would be nice if we could have an installation trigger/prompt to install the Python extension before they save the file with the appropriate file extension. In this case, if the user creates a new untitled file --> begins typing Python code --> the language model detects this might be Python code -->  the user is prompted to install the Python extension. 
![Python language being detected while typing in untitled file](https://github.com/microsoft/vscode/assets/60238438/48454446-313b-43b7-8de4-1f8ddfa8e4e1)



In user studies, we have observed users struggle to find where to install the Python extension (or do not realize they need an extension for Python support) and do not select Python as the file language before they begin typing. At this point, the user would need to save the file and change the file extension to .py in order to be prompted to install the Python extension. We often see users get stuck here as they do not think to save the file or they forget to change the file extension when they do save the file.
Repository: flutter
Issue: `cupertino.overflow_clipbehavior_none.cupertino.0` flakes
Labels: f: cupertino,P3,c: flake,team-design,triaged-design

The `cupertino.overflow_clipbehavior_none.cupertino.0` golden image test blocked a roll.  It was ignored and the roll was closed.  The next roll did not have a problem.

link to golden failure: https://flutter-gold.skia.org/search?crs=github&include_ignored=true&issue=137187&master=true&negative=true&not_at_head=true&patchsets=2
roll: https://github.com/flutter/flutter/pull/137187

roll includes the following changes:
- https://github.com/flutter/engine/pull/47241
- https://github.com/flutter/engine/pull/47277

Neither of these sound related.  One has to do with canvaskit the other sounds like it is only changing tests.
Repository: PowerToys
Issue: Screen Ruler - Overlay Multiple Screen Measurements
Labels: Idea-Enhancement,Needs-Triage,Product-Screen Ruler

### Description of the new feature / enhancement

Great tool - It would be most excellent if we had the option to capture multiple screen measurements, for the purpose of demonstrating layout abnormalities.

_Example:_
![image](https://github.com/microsoft/PowerToys/assets/94235837/fb97458c-7e1a-4a1b-81d6-422f082737c4)


### Scenario when this would be used?

In my particular use case it is often necessary to identify and provide evidence of visual issues, both in terms of software design and report outputs, in many cases being able to provide comparison measurements would help.  

### Supporting information

_No response_
Repository: material-ui
Issue: [Accordion][material-ui] Selecting all text in one Accordion will unexpectedly select text in other Accordions
Labels: bug 🐛,component: accordion,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://mui.com/material-ui/react-accordion/

Steps:

1. expand the first item
2. double click all the text in the expanded first item to select **all** the text, not just one word
3. expand the second item which should still be collapsed, 
4. all the text in the second item has become selected


### Current behavior 😯

When you select all the text in one of the `AccordionDetail`s, all the text in subsequent unexpanded `AccordionDetail`s are also selected

### Expected behavior 🤔

selecting text in a accordion item should not impact any other item

### Context 🔦

we are using mui/accordion, showing all items, double click one of them to highlight of all.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: macOS 14.0
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 118.0.5993.117
    Edge: 118.0.2088.69
    Safari: 17.0
  npmPackages:
    @emotion/react: ~11.9.0 => 11.9.0
    @emotion/styled: ~11.8.1 => 11.8.1
    @mui/material: ~5.11.12 => 5.11.12
    @mui/x-date-pickers: 5.0.0-alpha.6 => 5.0.0-alpha.6
    @types/react: 18.2.12 => 18.2.12
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 4.6.4 => 4.6.4
```
</details>
Repository: next.js
Issue: Next.js 12.2.6 unhandled rejection: res is undefined
Labels: bug

### Link to the code that reproduces this issue

https://github.com/cb1kenobi/nextjs-v12-2

### To Reproduce

1. `npm install`
2. `npm run dev`
3. `curl http://localhost:3000/edge`

### Current vs. Expected behavior

Next.js 12.2.6 added a monkeypatch around `response.setHeader()` that is causing edge functions to throw and unhandled rejection resulting in the client hanging.

https://github.com/vercel/next.js/compare/v12.2.5...v12.2.6#diff-2b8e3503c1bebf856610a5551d9c5996435b99f45db389d4eeac1b671518875e

The `/edge` page has a config of:

```
export const config = {
  runtime: 'experimental-edge',
};
```

When accessing this `/edge` page, you can see the following in the terminal:

```
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - SWC minify release candidate enabled. https://nextjs.link/swcmin
event - compiled client and server successfully in 636 ms (172 modules)
wait  - compiling...
event - compiled client and server successfully in 34 ms (172 modules)
warn  - You are using an experimental edge runtime, the API might change.
wait  - compiling /edge (client and server)...
event - compiled client and server successfully in 293 ms (287 modules)
error - node_modules/next/dist/server/base-server.js (144:0) @ NextWebServer.handleRequest
error - unhandledRejection: Cannot read properties of undefined (reading 'setHeader')
null
```

I pasted some `console.log()`s and I wasn't able to pinpoint the exact problem spot. The error says line 144, but I don't think that's correct. I do see that the request handler is invoked twice where the first time works, but the second time the response is null. Not sure what up with that.

### Verify canary release

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

### Provide environment information

```bash
Latest macOS, tested both Node 18.18.0 and 16.something.

This issue does not happen with Next.js 12.2.5, 12.3.0, or the latest canary release (maybe). It only happens with 12.2.6.
```


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

Not sure

### Additional context

This issue was found while creating Next.js test fixtures to the framework test matrix.
Repository: pytorch
Issue: The error type `UserError` in dynamo is confusing.
Labels: triaged,export-triage-review,oncall: export

### 🐛 Describe the bug

Currently `UserError` is inherited from `UnsupportedError` and is meant to be interpreted as:
- An error that is unsupported but still has some workarounds that users can use to go past this error while tracing. 

But it could also be interpreted as some error that happened because of user's mistake, like the original function is not runnable in eager. 

To better distinguish, we should do following:
1. Rename `UserError` to something like `MitigitableUnsuppportedError` that still inherits from `UnsupportedError` so that our infra still knows to handle this error as regular graph break signal. The value it provides is still about presenting better error message to end user. Since this is meant to supplement the generic `UnsupportedError`, we shouldn't swallow the original error message. (Related issue: https://github.com/pytorch/pytorch/issues/111075)
2. Make `UserError` not inherit from `UnsupportedError` and only use it when we want to make it clear that the code would have failed in eager, and tell them to re-run it in eager if they want to see the issue.

### Versions

main

cc @avikchaudhuri @gmagogsfm @zhxchen17 @angelayi
Repository: rust
Issue: False negative for trivial_casts with pointer
Labels: A-lints,P-medium,T-compiler,regression-from-stable-to-stable,C-bug,A-raw-pointers

After #113262, this will no longer fail to compile:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=8ee721b21617d98d18c5256778b57efe

```rust
#[deny(trivial_casts)]
fn main() {
    let a = std::ptr::null::<()>();
    let _b = a as *const ();
}
```

The cast is trivial, but we miss it because we have to conservatively assume that raw pointer casts are not trivial. A possible fix would be to check for trivial raw pointer casts in MIR (but correctly considering lifetimes is still not quite easy there I think).
Repository: PowerToys
Issue: Cannot find documentation on the MWB network protocol
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

I've looked high and low and can't find any discussion about the Mouse Without Borders protocol, other than a note in a bug report that it's a "custom TCP protcol".

Publishing the protocol would really help folks like #26154, to say nothing of the entire family of issues merged into #26296.
Repository: material-ui
Issue: [material-ui][Dialog] Pressing enter to close dialog causes partial focus animation of open dialog button
Labels: component: dialog,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: [MUI Dialog Docs -> Basic Dialog](https://mui.com/material-ui/react-dialog/#form-dialogs)

Steps:

1. Go to the MUI Dialog docs page -> Basic dialog section
2. Click "Open simple dialog" and move mouse away
3. Hit enter to "click" the auto-focused "Add account" button
4. The modal will close, and the "open simple dialog" button will be focused with half the on-click animation triggered
5. It will stay that way until you hover over it and move mouse out

![mui-dialog](https://github.com/mui/material-ui/assets/30693802/7de8ed42-a4e8-4cf6-ba08-fd43298abf2a)



### Current behavior 😯

When a dialog closes as a result of hitting enter, the underlying button that opened it gets a frozen partial animation as if it's just been clicked.

### Expected behavior 🤔

The button should not partially animate.

### Context 🔦

In my own project, I'm using a similar simple dialog with a form on it. When the user presses enter to submit the form, the UX looks strange due to this issue.
I'd like to fix this UX glitch.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 18.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 118.0.5993.89
    Edge: Spartan (44.19041.3570.0), Chromium (118.0.2088.61)
  npmPackages:
    @emotion/react: latest => 11.11.1 
    @emotion/styled: latest => 11.11.0 
    @mui/base:  5.0.0-beta.17 
    @mui/core-downloads-tracker:  5.14.11 
    @mui/icons-material: latest => 5.14.11 
    @mui/material: latest => 5.14.11 
    @mui/private-theming:  5.14.11 
    @mui/styled-engine:  5.14.11 
    @mui/system:  5.14.11 
    @mui/types:  7.2.4 
    @mui/utils:  5.14.11 
    @mui/x-data-grid: ^6.14.0 => 6.15.0 
    @types/react: latest => 18.2.23 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: latest => 5.2.2 
```
</details>

Browser: Chrome Version 118.0.5993.89 (Official Build) (64-bit) (on Windows 10)
Repository: go
Issue: x/pkgsite/cmd/pkgsite: Unable to fetch std@Latest Pkgsite documentation for Local Main go Repo : https://go.googlesource.com/go
Labels: pkgsite,pkgsite/cmd

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.21.3
</pre>

### Does this issue reproduce with the latest release?
Yes. But the ultimate intention is to run pkgsite for main go repository - std@latest against master(1.22) branch.


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
Windows, amd64, gcc
</pre></details>

### What did you do?

```
1. git clone https://go.googlesource.com/go/
2. git checkout go1.21.3
3. git switch -c go1.21.3
4. C:\Users\R\golang\go\src> all.bat
------------------------------------
GOARCH: amd64
GOOS: windows
OS Version: 10.0.22621

ALL TESTS PASSED


Installed Go for windows/amd64 in C:\Users\R\golang\go
Installed commands in C:\Users\R\golang\go\bin
*** You need to add C:\Users\R\golang\go\bin to your PATH.

-------------------------------------
5. go install golang.org/x/pkgsite/cmd/pkgsite@latest
6. C:\Users\R\golang\go\src>pkgsite .

C:\Users\R\golang\go\src>pkgsite .
2023/10/25 16:29:15 Info: go/packages.Load(["all"]) loaded 277 packages from . in 655.6654ms
2023/10/25 16:29:15 Info: go/packages.Load(std) loaded 0 packages from C:\Program Files\Go in 9.2327ms
2023/10/25 16:29:15 Error: loading packages from stdlib: err: fork/exec C:\Users\R\golang\go\bin\go.exe: The parameter is incorrect.: stderr:
2023/10/25 16:29:15 Info: Listening on addr http://localhost:8080
2023/10/25 16:29:51 Info: FetchDataSource: fetching std@latest
2023/10/25 16:34:10 Error: serveUnitPage(ctx, w, r, ds, &{std std latest}): FetchDataSource.GetUnitMeta("std", "std", "latest"): FetchDataSource.findModule("std", "std", "latest"): FetchDataSource.getModule("std", "latest"): FetchModule("std", "latest"): stdlib.ContentDir("latest"): remoteGoRepo.clone("v1.21.3"): running git fetch: exit status 128: fatal: refusing to fetch into branch 'refs/heads/main' checked out at 'C:/Users/R/AppData/Local/Temp/1087088232'
```

### What did you expect to see?
I was hoping to see the documentation website like pkg.go.dev and std libs listed and to look at their documentation.


### What did you see instead?

![Screenshot 2023-10-25 165655](https://github.com/golang/go/assets/9973300/0bac0ece-be93-451b-8f92-d1ab699c8631)