sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Different outputs of `div` and `threshold` with a specific input
Labels: triaged,bug,oncall: pt2,module: decompositions,topic: fuzzer

### 🐛 Describe the bug

with a specific input in [inputs.pkl.zip](https://github.com/pytorch/pytorch/files/14101497/inputs.pkl.zip), `div` and `threshold` meet a inconsistency between eagermode and torch.compile.

```python
import torch
import torch.nn as nn
import os, pickle

with open('inputs.pkl', 'rb') as f:
    inputs = pickle.load(f) 

class Model(nn.Module):
    def __init__(self):
        super().__init__()
    def forward(self, out):
        res = torch.div(out=out, input=inputs[0]['input'],other=inputs[0]['other'],rounding_mode='trunc')        
        res = torch.nn.functional.threshold(input=res, inplace=False,threshold=-1.9,value=5.2)        
        return res
inf = float('inf')
nan = float('nan')
is_valid = True
input1 = torch.randint(-2147483648, 2147483647, [4, 5, 8, 3], dtype=torch.int32)
input2 = input1.clone()

model = Model().to(torch.device('cpu'))
eag = model(input1)
opt = torch.compile(model.forward)(input2)

same_val = torch.allclose(eag.to('cpu'), 
                            opt.to('cpu'), 
                            rtol=1e-3, atol=1e-3, 
                            equal_nan=True)
if same_val == False : 
        raise ValueError('diff value')
```
trace
```
Traceback (most recent call last):
  File "/home/guihuan/LLM/exp_data/torch-2/2024-01-27-10-09/21/repro.py", line 30, in <module>
    raise ValueError('diff value')
ValueError: diff value
```

### Versions

20240130 nightly

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @SherlockNoMad @zou3519
Repository: flutter
Issue: "Сontains disallowed nested bundles" and "Contains disallowed file 'Frameworks'" Flutter with IOS share extension when deploy to TestFlight
Labels: platform-ios,tool,t: xcode,P2,team-ios,triaged-ios

### Type of Request

bug

### Infrastructure Environment

TestFlight

### What is happening?

I'm implementing the "Share" widget in a Flutter application using this guide (https://docs.flutter.dev/platform-integration/ios/app-extensions). To achieve this, it's necessary to embed the Flutter framework (Flutter.xcframework from extension_safe directory) into the extension. 

![Снимок экрана 2024-01-30 в 19 00 03](https://github.com/flutter/flutter/assets/75836663/53df5bd4-a4cb-4e03-a1c4-abb9531fe814)

I have no build issues, but when I try to submit to TestFlight, I encounter the following errors.

Asset validation failed Invalid Bundle. The bundle at 'Runner.app/Plugins/ share_extension.appex' contains disallowed nested bundles. (ID: 25eb4da5-3868-40ab-bb64-d83b73d238c)

Asset validation failed Invalid Bundle. The bundle at 'Runner.app/Plugins/share_extension.appex' contains disallowed file 'Frameworks'. (ID: e94a1815-1314-48f6-9b45-b6917b1fe627)


![telegram-cloud-photo-size-2-5316621067055387349-x](https://github.com/flutter/flutter/assets/75836663/9a3b9fe5-1559-46e0-b10e-aaf49f34c39a)

The only thing that allowed deployment was setting the framework to "Do not embed" but this option is not suitable because it causes the share widget to stop appearing.



### Steps to reproduce

Step 1: Add Target to project "Share Extension"

Step 2: Add project and extension to the same App Group

Step 3: Drag and drop the Flutter.xcframework file (From <path_to_flutter_sdk>/bin/cache/artifacts/engine/ios-release/extension_safe/Flutter.xcframework) into your share extension’s frameworks and libraries list

Step 4: Open the Flutter app project settings in Xcode to share build configurations. For each of these configurations, make sure the value in the Based on configuration file drop-down menu for your extension matches the one selected for the normal app target.

Step 5: Archive project

Stap 6: Try upload it to TestFlight


### Expected results

App uploaded to TestFlight and flutter will be shown in the "Share" widget
Repository: material-ui
Issue: [material-ui][Text Field] Warning about missing id/name with the multiline prop
Labels: external dependency,component: text field,package: material-ui

### Steps to reproduce

Link to live example: (required)

Steps:
1. Navigate here - https://mui.com/material-ui/react-text-field/#multiline
2. Open the debugger tools
3. Open the console and view the issues tab
4. ![image](https://github.com/mui/material-ui/assets/4236686/5a12c342-a977-4897-befb-6e4fab93a1f0)
5. Open the 'A form field element has neither an id nor a name attribute.' and click the first 'violating node'
6. Notice the 2nd textarea dom element with the missing id/name attributes
![image](https://github.com/mui/material-ui/assets/4236686/ebc6e2e0-caa7-444f-a740-ba76c76d4ab9)







### Current behavior

Currently, MUI renders 2 textarea dom elements for each multiline textfield/input.
The 1st textarea component contains the id/name attribute as expected.
The 2nd textarea (hidden) component is missing id/name attributes which raises a browser issue/warning

### Expected behavior

Both textarea dom components should contain unique id/name attributes

### Context

Trying to keep the browser issues/warnings to a minimum.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: TextField multiline warning missing id
Repository: flutter
Issue: [flutter_tools] `PathNotFoundException` when running `flutter create`
Labels: c: crash,P2,team-tool,triaged-tool

Version: `stable/3.16.9`
Command: `flutter create --template app --overwrite .`

```
PathNotFoundException: PathNotFoundException: Creation failed, path = 'C:\Users\xxxx\Documents\xxxxx\flutter_application_1\lib' (OS Error: The system cannot find the file specified.
, errno = 2)
at _Directory.createSync(directory_impl.dart:129)
at _File.createSync(file_impl.dart:303)
at ForwardingFile.createSync(forwarding_file.dart:26)
at ErrorHandlingFile.createSync.<anonymous closure>(error_handling_io.dart:283)
at _runSync(error_handling_io.dart:590)
at ErrorHandlingFile.createSync(error_handling_io.dart:282)
at Template.render.<anonymous closure>(template.dart:321)
at _LinkedHashMapMixin.forEach(compact_hash.dart:633)
at Template.render(template.dart:281)
at CreateBase.renderMerged(create_base.dart:483)
at <asynchronous gap>(async)
at CreateBase.generateApp(create_base.dart:506)
at <asynchronous gap>(async)
at CreateCommand.runCommand(create.dart:361)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1367)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:212)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:348)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:294)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:112)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at main(executable.dart:90)
at <asynchronous gap>(async)
```
Repository: godot
Issue: Enabling Prefer Wayland editor setting on X11 prints errors to console on startup
Labels: bug,platform:linuxbsd,topic:editor,topic:porting

### Tested versions

- Reproducible in: 4.3.dev cae759949

### System information

Godot v4.3.dev (cae759949) - Fedora Linux 39 (KDE Plasma) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 545.29.06) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

Enabling Prefer Wayland editor setting on X11 prints errors to console on startup every time the editor starts.

Given the setting is phrased as *preferring* Wayland as opposed to requiring its use, I suggest silencing those errors or making them verbose-only.

```
ERROR: Can't connect to a Wayland display.
   at: init (platform/linuxbsd/wayland/wayland_thread.cpp:3412)
ERROR: Could not initialize the Wayland thread.
   at: DisplayServerWayland (platform/linuxbsd/wayland/display_server_wayland.cpp:1173)
ERROR: Can't create the Wayland display server.
   at: create_func (platform/linuxbsd/wayland/display_server_wayland.cpp:1148)
```

### Steps to reproduce

Enable the **Prefer Wayland** editor setting then restart the editor on a X11 session while it's running in a terminal.

### Minimal reproduction project (MRP)

N/A
Repository: go
Issue: os: Mkdir ignores perm on Windows
Labels: OS-Windows,NeedsInvestigation

### Go version

go version go1.21.6 windows/amd64

### Output of `go env` in your module/workspace:

```shell
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\xiaqq\AppData\Local\go-build
set GOENV=C:\Users\xiaqq\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\xiaqq\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\xiaqq\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.21.6
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\xiaqq\AppData\Local\Temp\go-build2957556198=/tmp/go-build -gno-record-gcc-switches
```


### What did you do?

```go
package main

import (
	"fmt"
	"os"
)

func main() {
	file, err := os.OpenFile("f", os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0o444)
	if err != nil {
		panic(err)
	}
	file.Close()
	stat("f")

	os.Mkdir("d", 0o555)
	stat("d")
}

func stat(name string) {
	info, err := os.Stat(name)
	if err != nil {
		panic(err)
	}
	fmt.Println(info.Mode())
}
```

### What did you see happen?

Command output:

```
-r--r--r--
dr-xr-xr-x
```

### What did you expect to see?

Command output:

```
-r--r--r--
drwxrwxrwx
```
Repository: godot
Issue: Editor does not use Godot icon on Wayland (uses default Wayland icon instead)
Labels: bug,platform:linuxbsd,topic:editor,topic:porting

### Tested versions

- Reproducible in: 4.3.dev cae759949

### System information

Godot v4.3.dev (cae759949) - Fedora Linux 39 (KDE Plasma) - Wayland - GLES3 (Compatibility) - NVIDIA GeForce RTX 4090 (nvidia; 545.29.06) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

The editor doesn't use Godot icon on Wayland; it uses the default Wayland icon instead. This is printed when the editor starts:

```
WARNING: Icon not supported by this display server.
     at: set_icon (servers/display_server.cpp:587)
```

This isn't printed when running the project directly with the `--path` command line argument.

See the editor icon in top-left corner (default Wayland icon), project icon in bottom-right corner:

![image](https://github.com/godotengine/godot/assets/180032/b35ed3fc-20cd-4d5f-9cab-a701e6430b9b)


### Steps to reproduce

Use a Wayland session, enable the **Prefer Wayland** editor setting then restart the editor.

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Editor splash screen is massive on Wayland compared to X11
Labels: bug,platform:linuxbsd,topic:editor,topic:porting

### Tested versions

- Reproducible in: 4.3.dev cae759949

### System information

Godot v4.3.dev (cae759949) - Fedora Linux 39 (KDE Plasma) - Wayland - GLES3 (Compatibility) - NVIDIA GeForce RTX 4090 (nvidia; 545.29.06) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

The splash screen is rescaled to match the window size, which makes it look massive on a 4K display:

![Screenshot_20240130_185217](https://github.com/godotengine/godot/assets/180032/c0b89edd-3538-4b27-bb5c-72ab9cf1e321)

This doesn't occur on X11 where the splash screen remains pixel-perfect. My Wayland display scale is 100%, and so is the editor scale.

Ideally, we should scale the splash screen according to the OS scale factor (or the editor scale factor) on both X11 and Wayland.

### Steps to reproduce

Use a Wayland session, enable the **Prefer Wayland** editor setting then restart the editor.

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: [flutter_tools] Permissions error on unified analytics related file `dart-flutter-telemetry-session.json`
Labels: P2,team-tool,triaged-tool

Version: `stable/3.16.9`
Command: `flutter upgrade`

```
PathAccessException: PathAccessException: Cannot open file, path = '/Users/username/.dart-tool/dart-flutter-telemetry-session.json' (OS Error: Permission denied, errno = 13)
at _File.throwIfError(file_impl.dart:675)
at _File.openSync(file_impl.dart:490)
at _File.writeAsBytesSync(file_impl.dart:644)
at _File.writeAsStringSync(file_impl.dart:668)
at ForwardingFile.writeAsStringSync(forwarding_file.dart:150)
at Session.getSessionId(session.dart:59)
at UserProperty._toMap(user_property.dart:63)
at UserProperty.preparePayload(user_property.dart:50)
at generateRequestBody(utils.dart:109)
at AnalyticsImpl.send(analytics.dart:599)
at FlutterCommand.verifyThenRunCommand(flutter_command.dart:1684)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1367)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:212)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:348)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:294)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:112)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at main(executable.dart:90)
at <asynchronous gap>(async)
```
Repository: tauri
Issue: [bug] `tauri build` modifies `Cargo.toml`?
Labels: type: bug,status: needs triage

### Describe the bug

Running `stat src-tauri/Cargo.toml && pnpm tauri build --bundles none > /dev/null 2> /dev/null && stat src-tauri/Cargo.toml`

I see the mtime for my Cargo.toml changes after `pnpm tauri build`. If I do the same with only `cargo build --release`, the mtime doesn't change, so I think it must be in Tauri.

![image](https://github.com/tauri-apps/tauri/assets/13400041/19f2754b-60b3-4506-9079-3462bf005238)

My `beforeDevCommand` and `beforeBuildCommand` are empty strings, so I don't think anything else in my build pipeline should be modifying the Cargo.toml manifest.

### Reproduction

I can go back and make a repro repository, I'm just curious if this is intended behavior and if there's anything I can do to disable it.

### Expected behavior

I expect Cargo.toml to not change during the build process.
I'm trying to embed the Git version in my final exe and for some possibly Windows-specific reason, this modification is causing the Git version to show up as dirty / modified

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 120.0.2210.144
    ✔ MSVC:
        - Visual Studio Build Tools 2019
        - Visual Studio Community 2022
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: 1.75.0-x86_64-pc-windows-msvc (overridden by 'C:\cygwin64\home\User\projects\firezone\rust\rust-toolchain.toml')
    - node: 20.10.0
    - pnpm: 8.14.3
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: 1.5.4
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.9

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../src
    - devPath: ../src
```


### Stack trace

```text
N/A
```


### Additional context

I searched in issues and docs but of course "Cargo.toml" and even "manifest" returned a lot of false positives, so maybe I missed something.
Repository: pytorch
Issue: DISABLED test_causal_variants_compile_causal_variant_CausalVariant_LOWER_RIGHT_shape1_cuda (__main__.TestAttnBiasCUDA)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22test_transformers.py%3A%3ATestAttnBiasCUDA%3A%3Atest_causal_variants_compile_causal_variant_CausalVariant_LOWER_RIGHT_shape1_cuda%22%5D)).

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: PowerToys
Issue: Can't set up "Command Not Found" feature
Labels: Issue-Bug,Product-CommandNotFound

### Microsoft PowerToys version

v0.77.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Command not found

### Steps to reproduce

I am trying to setup **Command Not Found** feature, but I get:

>  "EnableModule.ps1: Cannot dot-source this command because it was defined in a different language mode. To invoke this command without importing its contents, omit the '.' operator."

 message at the _Installation logs_  I have attached a video to show the process. As you can see from the video, I have both requirements checked

https://github.com/microsoft/PowerToys/assets/64617514/0831713f-4c0c-4d67-ba37-cf8af5c2d073



### ✔️ Expected Behavior

Command Not Found feature to be installed when hit _Install_ button

### ❌ Actual Behavior

It opens a blank terminal window and  just returns the error message mentioned above.

### Other Software

_No response_
Repository: pytorch
Issue: DISABLED test_causal_variants_compile_causal_variant_CausalVariant_LOWER_RIGHT_shape3_cuda (__main__.TestAttnBiasCUDA)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22test_transformers.py%3A%3ATestAttnBiasCUDA%3A%3Atest_causal_variants_compile_causal_variant_CausalVariant_LOWER_RIGHT_shape3_cuda%22%5D)).

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: next.js
Issue: Newly created NextJS code wont work on any browsers except Firefox.
Labels: Upstream,bug,Runtime

### Link to the code that reproduces this issue

https://github.com/allyn8444/nextjs-issue

### To Reproduce

1. Initialize code by creating new nextjs app
`npx create-next-app@latest`

2. I just copied the instructions in the nextjs docs.
https://nextjs.org/docs/getting-started/installation 

3. cd into your folder and enter `npm run dev`

4. A localhost should appear, you can copy and paste it to your browser or cmd + click (im using MacOS)

5. Since Edge is my default browser, the code should display the template. However, in my case, it won't display.
It should display on other browsers as well but in my device, it only runs on Firefox.

### Current vs. Expected behavior

I worked with nextjs before and had no problem using Edge. This time when I tried to run (npm run dev) my code it wouldn't work. 
I tested it in multiple browsers and I discovered that it won't work on any other browsers except Firefox (I tried it in Google, edge, brave, and Firefox). 

It is weird because it doesn't throw any error, there is nothing in the console.
![image](https://github.com/vercel/next.js/assets/110903853/592fb90a-5865-43cf-86bb-96b8e268d5da)
![image](https://github.com/vercel/next.js/assets/110903853/27d25953-ad94-4988-9b9c-916cc5991efd)

If I try to run the localhost in Firefox, it will start compiling and output the code.
![image](https://github.com/vercel/next.js/assets/110903853/22291c79-d9d5-465d-a053-46896ce0c6be)
![image](https://github.com/vercel/next.js/assets/110903853/e8c043a9-6331-458a-bcba-4877ad7a5b5e)

I concluded that it is a nextjs problem since I created a react-vite code and it works on different browsers. 

I already tried reinstalling my node, deleting .next and node_modules folder, tried using npm run build and npm run start, but still the same issue.

Also already tried surfing the internet for solutions but nothing seems to work.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime), Operating System (Windows, MacOS, Linux)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: next.js
Issue: Navigating after pushState doesn't reset page
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/vercel-next-js-reproduction-template-go8s7s?file=%2Fapp%2Flayout.tsx%3A5%2C13

### To Reproduce

1. Navigate from `/` to `/other` using `location.pushState`
2. Try to navigate back to `/` using `Link` or `router.push`

### Current vs. Expected behavior

After navigating from `/` to `/other` using `location.pushState`, it still renders to content from `/` but shows the URL as `/other`. This is working as expected.

However, when trying to navigate back to `/` (to reset the page), using `Link` or `router.push` changes the URL back to `/` (as expected) but does not reset the page. This also happens with `router.refresh` (either before or after navigation).

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.1-canary.23 // Latest available version is detected (14.1.1-canary.23).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

App Router, Routing (next/router, next/navigation, next/link)

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

next dev (local), next start (local)

### Additional context

_No response_