sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime: TestSUID hangs with "Password" prompt on FreeBSD
Labels: OS-FreeBSD,NeedsFix,compiler/runtime

@siebenmann [reports](https://mastodon.social/@cks/113601252814952553) that `all.bash` hangs with a "Password:" prompt on their FreeBSD machine due to `runtime.TestSUID`'s [`su` call](https://cs.opensource.google/go/go/+/master:src/runtime/security_test.go;l=33;drc=8b5ed3cdaeba621687c71c19174bb4db0f5713f0).

Our FreeBSD builders allow `su` with no password (I think because our user is in the `wheel` group?). Presumably real FreeBSD systems don't put the main user in `wheel`. Or maybe `su` is asking for the password of the primary user? I'm not sure how this configuration works.

On my Linux workstation, the test skips as `su` seems to automatically exit with error (detects a non-interactive stdin perhaps?). Perhaps FreeBSD's `su` doesn't do this?

cc @golang/freebsd @rolandshoemaker
Repository: pytorch
Issue: torch.fx.GraphModule constructor doesn't copy all parameters/buffers from source graph module
Labels: triaged,oncall: pt2,oncall: fx,export-triage-review,oncall: export

### 🐛 Describe the bug

As can be seen here: https://github.com/pytorch/pytorch/blob/main/torch/fx/graph_module.py#L478 We don't call remove_duplicate=False, so as a result, duplicate parameters get ignored. Not sure if this is intended behaviour or not. 

### Versions

Main

cc @chauhang @penguinwu @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv @avikchaudhuri @gmagogsfm @zhxchen17 @angelayi @suo @ydwu4
Repository: react
Issue: [React 19] codemod fails when ~/.codemod does not exist
Labels: React 19

## Summary

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

When running `npx codemod@latest react/19/migration-recipe` I get an error like...

```
Error: ENOENT: no such file or directory, scandir '/home/xxxx/.codemod'
    at async readdir (node:internal/fs/promises:948:18)
    at async Object.findCredentials (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:32395:12105)
    at async CYn (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:32395:12501)
    at async DYn.get (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:32405:302)
    at async Mne (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:32405:1787)
    at async QCi (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:52988:1393)
    at async R2e (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:52990:377)
    at async Object.handler (/home/xxxx/.npm/_npx/bef22f83919465d9/node_modules/codemod/dist/index.cjs:52990:1075) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: '/home/xxxx/.codemod'
}
```

If I run `mkdir ~/.codemod` and then run the command again, it works normally.
Repository: rust
Issue: E0596 error should suggest adding mut rather than a type signature
Labels: A-diagnostics,T-compiler

### Code

```Rust
struct Bar();

impl Bar {
    fn mutate(&mut self) {}
}

struct Foo(Bar);

fn f() -> Option<Foo> {
    None
}

fn main() {
    while let Some(x) = f() {
        let y = match x {
            Foo(ref bar) => {
                bar
            }
        };
        y.mutate()
    }
}
```

### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0596]: cannot borrow `*y` as mutable, as it is behind a `&` reference
  --> src/main.rs:20:9
   |
20 |         y.mutate()
   |         ^ `y` is a `&` reference, so the data it refers to cannot be borrowed as mutable
   |
help: consider annotating `Bar` with `#[derive(Clone)]`
   |
1  + #[derive(Clone)]
2  | struct Bar();
   |
help: consider specifying this binding's type
   |
15 |         let y: &mut Bar = match x {
   |              ++++++++++

For more information about this error, try `rustc --explain E0596`.
error: could not compile `playground` (bin "playground") due to 1 previous error
```

### Desired output

```Shell
help: consider changing this to be mutable
   |
16 |             Foo(ref mut bar) => {
   |                     +++
```

### Rationale and extra context

If you make rustc's first suggested change, you still get the same error, and if you make the second, you just end up with this error after:
```
error[E0308]: mismatched types
  --> src/main.rs:17:17
   |
17 |                 bar
   |                 ^^^ types differ in mutability
   |
   = note: expected mutable reference `&mut Bar`
                      found reference `&Bar`
```
Which wasn't really any help at all. With my alternative suggested change, you'll still get one more error, but that one will suggest changing `Some(x)` to `Some(mut x)`, and that will make it work.

### Other cases

```Rust

```

### Rust Version

Tested on the Rust Playground with both stable 1.83.0 and 1.85.0-nightly 2024-12-04 acabb5248231987ae1f0 (sorry for the lack of the exact command you wanted, but see rust-lang/rust-playground#1043)

### Anything else?

_No response_
Repository: react
Issue: Portal can't be placed inside img tag
Labels: Status: Unconfirmed

React version: 18.2

## Steps To Reproduce

1. `<img>{ReactDOM.createPortal(<div />, document.body)}</img>`

## The current behavior

    react-dom.development.js:2942 Uncaught Error: img is a void element tag and must neither have `children` nor use `dangerouslySetInnerHTML`.

## The expected behavior

Since portal does not create actual DOM inside the image tag, it does not violate DOM rules, and it would be useful to allow it for event bubbling purposes.
Repository: pytorch
Issue: add `torch._foreach_clone`
Labels: feature,triaged,actionable,module: mta

### 🚀 The feature, motivation and pitch

A "foreach" version of `Tensor.clone()` to clone a list of tensors. Can be nice in situations such as follows:

```python
# optionally transform some tensor_list_1, but tensor_list_1 should not be altered inplace
if do_transform:
    tensor_list_2 = torch._foreach_some_op(tensor_list_1, ...)
else:
    tensor_list_2 = torch._foreach_clone(tensor_list_1)
# do inplace foreach ops on tensor_list_2
...
```

### Alternatives

- "identity foreach ops" like `torch._foreach_add(tensor_list, 0)`, but it feels like a hack and might introduce unnecessary compute;
- `for` loop / list comprehension: `[t.clone() for t in tensor_list]`. But all other `_foreach_*` ops can also be substituted similarly and the hope is that `_foreach` will make things run faster AFAIK. 

### Additional context

_No response_

cc @crcrpar @mcarilli @janeyx99
Repository: ui
Issue: [bug]: SIderbar turn transparent on mobile
Labels: bug

### Describe the bug

When i open the sidebar on mobile i can see the calender but the background is transparent. I'm also getting a warning message: "@radix-ui_react-dialog.js?v=452130b3:336 Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}."

### Affected component/components

Sidebar

### How to reproduce

Open Sidebar on mobile
<img width="477" alt="Screen Shot 2024-12-05 at 11 53 05 PM" src="https://github.com/user-attachments/assets/1db323e3-2305-42b3-bbfb-df568b559a4a">


### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}.
```


### System Info

```bash
Chrome,Mac
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: go
Issue: build: windows/arm (32-bit ARM) port is broken
Labels: OS-Windows,NeedsInvestigation,umbrella,arch-arm

The Go porting policy has a section on broken ports, https://go.dev/wiki/PortingPolicy#broken-ports. The GOOS=windows GOARCH=arm (not arm64) port was marked broken in August 2024 ([CL 601777](https://go.dev/cl/601777)) for the following reasons:

- The port stopped working, failing to build with make.bat, tracked in issue #68552.
- The builder stopped running, and no new running builder has been added yet, tracked in #67308. (A running builder is needed to know whether the port is working.)

This is an umbrella issue to track the status of the port.

CC @golang/windows, @golang/release.
Repository: rust
Issue: E0499 error shouldn't suggest adding a semicolon when there already is one
Labels: A-diagnostics,T-compiler,D-incorrect

### Code

```Rust
use std::marker::PhantomData;

struct Bar<'a>(PhantomData<&'a mut i32>);

impl<'a> Drop for Bar<'a> {
    fn drop(&mut self) {}
}

struct Foo();

impl Foo {
    fn f(&mut self) -> Option<Bar<'_>> {
        None
    }
    
    fn g(&mut self) {}
}

fn main() {
    let mut foo = Foo();
    while let Some(_) = foo.f() {
        foo.g();
    };
}
```

### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0499]: cannot borrow `foo` as mutable more than once at a time
  --> src/main.rs:22:9
   |
21 |     while let Some(_) = foo.f() {
   |                         -------
   |                         |
   |                         first mutable borrow occurs here
   |                         a temporary with access to the first borrow is created here ...
22 |         foo.g();
   |         ^^^ second mutable borrow occurs here
23 |     };
   |     - ... and the first borrow might be used here, when that temporary is dropped and runs the destructor for type `Option<Bar<'_>>`
   |
help: consider adding semicolon after the expression so its temporaries are dropped sooner, before the local variables declared by the block are dropped
   |
23 |     };;
   |      +

For more information about this error, try `rustc --explain E0499`.
error: could not compile `playground` (bin "playground") due to 1 previous error
```

### Desired output

```Shell
Not have the help section since there already is a semicolon
```

### Rationale and extra context

_No response_

### Other cases

```Rust

```

### Rust Version

Tested on the Rust Playground with both stable 1.83.0 and 1.85.0-nightly 2024-12-04 acabb5248231987ae1f0 (sorry for the lack of the exact command you wanted, but see rust-lang/rust-playground#1043)

### Anything else?

_No response_
Repository: go
Issue: x/build/cmd/relnote: improve experience for documenting new standard library packages
Labels: Documentation,Builders,NeedsInvestigation,Friction

The cmd/relnote test requires that all new APIs have a corresponding entry in doc/next/\*-stdlib/\*-minor. This works as intended for most APIs, but some new APIs are entirely new packages. Those are not considered "minor" changes, and get their own heading.

The current approach for new packages is to include a file in \*-minor/nnn.md anyway, but make its content just a comment like "\<!-- This is a new package; covered in 6-stdlib/5-sha3.md. --\>".

This causes some friction down the road, as `relnote generate` ends up creating empty headings like these:

https://cs.opensource.google/go/x/website/+/master:_content/doc/go1.24.md;l=271-277;drc=4ccfb99db16b1419ac640fb08dd654053bd819ee

Those need to eventually be removed.

This is a tracking issue to improve this edge case. A simple fix is to make `relnote generate` detect when a fragment contains nothing but a comment, and in such cases avoid creating a heading. A more involved change would be to make the cmd/relnote test recognize when a new package is documented in \*-stdlib and not require the file with a comment to be added in the first place, if that can be done without risking forgetting to document such changes.

CC @golang/release.
Repository: godot
Issue: Error spam when re-importing a model with a saved `SkeletonProfile`, and model breakage when deleting a resource
Labels: bug,topic:import,topic:animation,topic:3d

### Tested versions

4.4 dev6

### System information

Godot v4.4.dev6 - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 threads)

### Issue description

If we save the SkeletonProfileHumanoid resource in the model import window, then click the re-import button, a spam of errors occurs.
Also, if we delete a previously saved resource and try to open the model in the model import window, it will break and will not open.

![Image](https://github.com/user-attachments/assets/afa16912-631f-4598-b028-8dddf0d1a1ba)


### Steps to reproduce

1. Open the Shibahu_skechfab.fbx model import window
2. Create a new `BoneMap`
3. Create a new `SkeletonProfileHumanoid` and save it as a resource
4. Click the Retry Import button
5. A huge number of errors (You can also clear the `BoneMap` and see the errors again)
6. Delete your previously saved `SkeletonProfileHumanoid` resource and the model breaks and will not open again (Reload the project to make sure).

### Minimal reproduction project (MRP)

The manipulations were carried out with the model from this comment: https://github.com/godotengine/godot/pull/99999#pullrequestreview-2477151374
Model: https://sketchfab.com/3d-models/shibahu-2e9dffd948f747668609a5a477daad86
Repository: godot
Issue: Applying DOF under Camera Attributes in World Environment causes SubViewports with TrasparentBG to not render VisualInstance3D objects
Labels: bug,topic:rendering,topic:3d

### Tested versions

Tested and reproducible in: v4.4.dev5.mono, v4.4vdev6.mono

### System information

Godot v4.4.dev6.mono - Windows 10.0.26100 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Ti (NVIDIA; 32.0.15.6614) - 11th Gen Intel(R) Core(TM) i5-11400 @ 2.60GHz (12 threads)

### Issue description

I came across this bug. If you have a SubViewport with a camera as its child, tick the TransparentBG and go to your CameraAttributes and select turn on DOF (either near or far), then any VisualInstance3D objects won't show up on the SubViewport, whilst correctly showing up when previewing the camera. This happens regardless of cull masks set

![Image](https://github.com/user-attachments/assets/fa28b7a0-5822-4a86-8b21-5f3aa78116bd)
Camera preview is correct

![Image](https://github.com/user-attachments/assets/efda98e5-5fe0-45a4-a779-745039a6a654)
SubViewport is empty (here, as well as when running the project)

### Steps to reproduce

1. Add a SubViewport to your world, tick "TransparentBG"
2. Add a Camera3D as it's child
3. Add a WorldEnvironment
4. Under CameraAttributes, add CameraAttributePractical and tick near or far blur OR just add CameraAttributePhysical
6. Add an object to check the bug
7. Camera should see the object, while the SubViewport should be empty

### Minimal reproduction project (MRP)

[viewport_bug_mrp.zip](https://github.com/user-attachments/files/18030919/viewport_bug_mrp.zip)
Repository: PowerToys
Issue: Hitting F5 in File Explorer turns all preview thumbnails black
Labels: Issue-Bug,Product-File Explorer,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

File Explorer: Thumbnail preview

### Steps to reproduce

Open File Explorer, to a directory with svg files in it that have existing thumbnails.
Press F5.



### ✔️ Expected Behavior

I didn't expect anything to happen, maybe refresh the thumbnails?

### ❌ Actual Behavior

All thumbnails were replaced with black squares. You have to change the thumbnail size and watch the thing laboriously generate thumbnails from scratch.

![Image](https://github.com/user-attachments/assets/20fd36c4-fe01-42e7-8916-e2fcbaa0aec3)


### Other Software

_No response_
Repository: material-ui
Issue: [TextField] Default Webkit autofill color does not use variables or palette
Labels: waiting for 👍,component: text field,package: material-ui,ready to take

https://github.com/mui/material-ui/blob/63896426afaa1a3d9f817b551ca0268afe7d7287/packages/mui-material/src/OutlinedInput/OutlinedInput.js#L141

Looking at this I was having issue with the color of the TextField when autofill was put in (Chrome). The color is hardcoded in and not referenced to any css var or theme.palette. I can of course override this with sx props on the slotProps.htmlInput or globally override in the theme.

It seems like a very odd choice to do a very solid dark blue when someone could have a completely different color theme than the default blue.

**Search keywords**:
Repository: tensorflow
Issue: TensorFlow source code compilation error
Labels: stat:awaiting tensorflower,type:build/install,subtype: ubuntu/linux,TF 2.18

### Issue type

Build/Install

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

tf 2.18.0

### Custom code

Yes

### OS platform and distribution

Ubuntu 24.04.1 LTS

### Mobile device

_No response_

### Python version

3.12.1

### Bazel version

7.3.1

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

My CPU supports AVX512F, I want to build it from source to support my CPU instruction set

### Standalone code to reproduce the issue

```shell
ERROR: Skipping '//tensorflow/tools/pip_package:build_pip_package': no such target '//tensorflow/tools/pip_package:build_pip_package': target 'build_pip_package' not declared in package 'tensorflow/tools/pip_package' defined by /usr/workerdir/workerspace/tensorflow/tensorflow/tools/pip_package/BUILD (did you mean 'build_pip_package.py'? Tip: use `query "//tensorflow/tools/pip_package:*"` to see all the targets in that package)
WARNING: Target pattern parsing failed.
```


### Relevant log output

```shell
ERROR: Skipping '//tensorflow/tools/pip_package:build_pip_package': no such target '//tensorflow/tools/pip_package:build_pip_package': target 'build_pip_package' not declared in package 'tensorflow/tools/pip_package' defined by /usr/workerdir/workerspace/tensorflow/tensorflow/tools/pip_package/BUILD (did you mean 'build_pip_package.py'? Tip: use `query "//tensorflow/tools/pip_package:*"` to see all the targets in that package)
WARNING: Target pattern parsing failed.
```
Repository: rust
Issue: Incorrect diagnostic `error[E0309]: the parameter type `T` may not live long enough`, suggests duplicate bound
Labels: A-diagnostics,A-lifetimes,A-trait-system,T-compiler,A-impl-trait,D-invalid-suggestion,S-has-mcve

### Code

```Rust
use std::marker::PhantomData;

trait Unit<'t, T> {}
trait Trait {
    fn frob<'a, T>() -> impl Unit<'a, T>;
}

struct Wrapper<T>(PhantomData<T>);
impl<'a, T> Unit<'a, T> for Wrapper<T> where T: 'a {}

struct Foo;
impl Trait for Foo {
    fn frob<'a, T: 'a>() -> impl Unit<'a, T> {
        Wrapper(PhantomData)
    }
}
```

### Current output

```
error[E0309]: the parameter type `T` may not live long enough
  --> src/lib.rs:13:29
   |
13 |     fn frob<'a, T: 'a>() -> impl Unit<'a, T> {
   |             --              ^^^^^^^^^^^^^^^^ ...so that the type `T` will meet its required lifetime bounds...
   |             |
   |             the parameter type `T` must be valid for the lifetime `'a` as defined here...
   |
note: ...that is required by this bound
  --> src/lib.rs:13:20
   |
13 |     fn frob<'a, T: 'a>() -> impl Unit<'a, T> {
   |                    ^^
help: consider adding an explicit lifetime bound
   |
13 |     fn frob<'a, T: 'a + 'a>() -> impl Unit<'a, T> {
   |                       ++++

For more information about this error, try `rustc --explain E0309`.
error: could not compile `testing` (lib) due to 1 previous error
```

### Additional Context

The program compiles fine if `frob` is a free function, or if `frob` is not a trait implementation.

```rust
trait Unit<'t, T> {}
trait Trait {
    fn frob<'a, T>() -> impl Unit<'a, T>;
}

struct Wrapper<T>(PhantomData<T>);
impl<'a, T> Unit<'a, T> for Wrapper<T> where T: 'a {}

// Not a trait impl
struct Foo;
impl Foo {
    fn frob<'a, T: 'a>() -> impl Unit<'a, T> {
        Wrapper(PhantomData)
    }
}

// Regular function
fn frob<'a, T: 'a>() -> impl Unit<'a, T> {
    Wrapper(PhantomData)
}
```

### Rust Version

```Shell
rustc 1.85.0-nightly (acabb5248 2024-12-04)
binary: rustc
commit-hash: acabb5248231987ae1f0c215208d1005a5db402d
commit-date: 2024-12-04
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.5
```
Repository: go
Issue: x/build: add doas package on NetBSD systems
Labels: OS-NetBSD,Builders,NeedsFix

### Go version

devel

### Output of `go env` in your module/workspace:

```shell
N/A
```


### What did you do?

#70702 reports that su asks for a password on some FreeBSD systems, causing the runtime test `TestSUID` to fail and leaving the terminal in a broken state.  Using the `doas` command with the `-n` option avoids this problem.  `doas` is available as a separate package on FreeBSD and perhaps also NetBSD.  Let's add it to the builders, and switch the test to use it.  It's OK to run the test on systems where there is no `doas` command; the test will be skipped.

### What did you see happen?

```
/bin/sh: doas: not found
```

### What did you expect to see?

A passing test.

CC @golang/release
Repository: vscode
Issue: Unit test failure: Ternery Search Tree
Labels: bug,freeze-slow-crash-leak,unit-test-failure

OOM from Javascript heap https://dev.azure.com/monacotools/Monaco/_build/results?buildId=308771&view=logs&j=55ac390b-ffb1-50ea-3650-525dd9a3fd80&t=a0dd9636-50d2-5f8a-f17f-6bcaa254d802

Crash might not be from this suite given we run all suites in the same renderer process, but what should be checked is for any abnormal memory allocation over the course of the run to eliminate any leaks or rule this out as legitimate oom
Repository: pytorch
Issue: MacOS tests has not been running for few weeks
Labels: high priority,module: ci,triaged,module: regression

https://github.com/pytorch/pytorch/pull/135386 rendered regular MacOS test shard useless


I.e. https://github.com/pytorch/pytorch/actions/runs/12191328925/job/34010247281?pr=141921 finishes in 18 sec for PR https://github.com/pytorch/pytorch/pull/141921 that could have some effect on Mac tests




### Versions

CI

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @seemethere @pytorch/pytorch-dev-infra
Repository: TypeScript
Issue: [bug] declaration files have invalid class member generics with mixin & multiple layer inheritance
Labels: Bug

### 🔎 Search Terms

declaration .d.ts invalid class member field generic mixin inherit

### 🕗 Version & Regression Information

- This changed between versions ______ and _______
- This changed in commit or PR _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because _______


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/MYGwhgzhAEBCkFMA8AVAfNA3gKGn6EArgA4IBOAsggLYBG50AvFgL7STQrYvbAD2AOwgAXaBQCWAD3ECm0JABEwwsABpoAYXBRoCScIQCAJjAEIA7tAAUAOjtHlYAFzsBATwDaAXQCUTDPAQyEoqaGi4+FYAyiTkLlqQEH6MGKCJuvqGJtAxpGRYEfj41FIyVHQMzACMhdAsQA

### 💻 Code

```ts
class Base<T> {
    superMember = {} as T
}
const Mixin = <Data, Class extends new (...data: any[]) => Base<Data>>
    (Super: Class) => class extends Super {
        mixinMember = 1
    }
```

### 🙁 Actual behavior

```ts
declare class Base<T> {
    superMember: T;
}
declare const Mixin: <Data, Class extends new (...data: any[]) => Base<Data>>(Super: Class) => {
    new (...data: any[]): {
        mixinMember: number;
        superMember: T;  // invalid generic variable in .d.ts
    };
} & Class;
```

### 🙂 Expected behavior

`tsc` generates completely valid `.d.ts` files with mixin inheritance.

### Additional information about the issue

_No response_