sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: copy_() produces wrong results for boolean tensors on mps
Labels: triaged,module: correctness (silent),module: mps,bug

### 🐛 Describe the bug

`copy_()` generates wrong results on mps backend for boolean tensors of certain shapes. A minimal example is:

```python
import torch

def f(device):
    data = torch.zeros((2,2,1,1,1,1), device=device, dtype=torch.bool)
    ones = torch.ones((2,1,1,1,1,1), device=device, dtype=torch.bool)
    data.narrow(1, 0, 1).copy_(ones)
    print("device:", device, ', out:', data)

f('cpu')
f('mps')
```

The code above produces wrong results on mps backend:
```
device: cpu , out: tensor([[[[[[ True]]]],
         [[[[False]]]]],
        [[[[[ True]]]],
         [[[[False]]]]]])
device: mps , out: tensor([[[[[[False]]]],
         [[[[False]]]]],
        [[[[[False]]]],
         [[[[False]]]]]], device='mps:0')
```


### Versions

Collecting environment information...
PyTorch version: 2.3.0a0+git1018ce2
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.3 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.1.0.2.5)
CMake version: Could not collect
Libc version: N/A

Python version: 3.11.6 (v3.11.6:8b6ee5ba3b, Oct  2 2023, 11:18:21) [Clang 13.0.0 (clang-1300.0.29.30)] (64-bit runtime)
Python platform: macOS-14.3-arm64-arm-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 M1 Pro

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] optree==0.10.0
[pip3] torch==2.3.0a0+gitaa51b3f
[conda] numpy                     1.26.4          py311he598dae_0  
[conda] numpy-base                1.26.4          py311hfbfe69c_0  
[conda] numpydoc                  1.5.0           py311hca03da5_0  

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen @razarmehr
Repository: material-ui
Issue: [joy-ui] Make the size prop breakpoint-aware
Labels: new feature,waiting for 👍,package: joy-ui

### Summary

Take a look at this code snippet:

```jsx
<IconButton size="lg">{icon}</IconButton>
```

If you want to change the size prop on certain screen sizes with Material UI, you can use hooks:

```jsx
import { useTheme } from '@mui/material/styles';
import useMediaQuery from '@mui/material/useMediaQuery';

function MyComponent() {
  const theme = useTheme();
  const matches = useMediaQuery(theme.breakpoints.up('sm'));

  return <IconButton size={matches ? "sm" : "lg"}>{icon}</IconButton>;
}
```

Often it might be too complicated for a simple task. However, it helps us reuse the predefined settings in Material UI's design system. The size prop not only changes the font size but could also affects other properties like margin, padding, height, and width etc ...

With Joy UI, we have to redefine each property separately, which can lead to inconsistencies:

```jsx
<IconButton
  sx={{
    "--Icon-fontSize": {xs: "new val", md: "new val"},
    "--IconButton-size": {xs: "new val", md: "new val"},
    and other vars ...
  }}
>
```

It would be better to stay within the design system and respect the predefined settings that were already set up.

One suggestion is to add support for props to handle breakpoint changes, similar to how `ButtonGroup` already supports this:

```jsx
<ButtonGroup spacing={{ xs: 0, sm: 1, md: '2rem' }}>...</ButtonGroup>
```

This approach would allow you to write something like:

```jsx
<IconButton size={{xs: "lg", md: "lg"}}>{icon}</IconButton>;
```

This way, we can easily change the size prop based on different screen sizes while still using the predefined settings in the design system.

### Examples

_No response_

### Motivation

_No response_

**Search keywords**: breakpoint
Repository: tailwindcss
Issue: v4: Automatic content detection in monorepos only finds direct package
Labels: v4

**What version of Tailwind CSS are you using?**
4.0.0-alpha.6

**What build tool (or framework if it abstracts the build tool) are you using?**
"next": "^14.1.1"
"@tailwindcss/postcss": "^4.0.0-alpha.6",
"postcss": "^8.4.35",

**What version of Node.js are you using?**
v18.18.2

**What browser are you using?**
N/A

**What operating system are you using?**
macOS

**Reproduction URL**
Attempting to do this inside an existing project, feel free to request a reproduction if you feel it will help and I'll make one (just takes a good chunk of time so wanted to check this level of detail was required first).

**Describe your issue**
I'm using tailwind in a mono repo, there is a basic design system which is just a bunch of components with tailwind classes and some config for styles (e.g. `bg-primary`). Upgrading to v4 was seamless for this, we were able to build and publish the design system.

When using the design system in the monorepo in a Next.js project we're transpiling the components (rather than using the built version).

I noticed that the styles were not being generated, I assumed this was because the automatic detection was not picking it up. Looking at the config code, it seems like we should be passing through the `base` as the config variable based on the config:
```
type PluginOptions = {
  // The base directory to scan for class candidates.
  base?: string
}
```

At first I tried putting in `"../.."` so that it would map to a relative root directory, but it seems like the only way to use base is with an absolute path eg `"/Users/me/Code/monorepo/" which does work.

It would just be nice to be able to use a relative directory here so that when we look at deploying/cloning the repo it's not hard coded to a user directory.

I imagine this might be solved when:
> We’ll introduce a way to configure content paths explicitly in the future for sure, but we’re curious to see how well this automatic approach works for everyone — it’s working awesome in our own projects.

So feel free to also close this and I can be patient 😅
Repository: rust
Issue: unhelpful suggestion: consider using a semicolon here
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,D-invalid-suggestion

### Code

```Rust
fn f() -> Result<u8, ()> {
    match true {
        true => {},
        _ => {g()?},
    }
    g()
}

fn g() -> Result<u8, ()> {unimplemented!()}
```


### Current output

```
error[E0308]: mismatched types
 --> src/lib.rs:4:15
  |
2 | /     match true {
3 | |         true => {},
4 | |         _ => {g()?},
  | |               ^^^^ expected `()`, found `u8`
5 | |     }
  | |_____- expected this to be `()`
  |
help: consider using a semicolon here
  |
4 |         _ => {g()?;},
  |                   +
help: consider using a semicolon here
  |
5 |     };
  |      +

For more information about this error, try `rustc --explain E0308`.
```


### Desired output

This suggestion should *not* be be displayed because the first suggestion is the correct one. This second suggestion does not fix the compile error and makes the next compile error worse. 
```
help: consider using a semicolon here
  |
5 |     };
  |      +
```

### Rationale and extra context

If the second suggestion is applied, the code still doesn't compile. Even worse, it no longer suggests the first (correct) fix if the second one has been applied. This is the output after adding the semicolon on line 5:

### Other cases

```Rust
error[E0308]: `match` arms have incompatible types
 --> src/lib.rs:4:15
  |
2 | /     match true {
3 | |         true => {},
  | |                 -- this is found to be of type `()`
4 | |         _ => {g()?},
  | |               ^^^^ expected `()`, found `u8`
5 | |     };
  | |_____- `match` arms have incompatible types

For more information about this error, try `rustc --explain E0308`.
```


### Rust Version

```Shell
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-unknown-linux-gnu
release: 1.76.0
LLVM version: 17.0.6
```
Repository: flutter
Issue: [video_player_web] wasm update errors out, pegs CPU at 100%
Labels: platform-web,p: video_player,P2,e: wasm,e: web_skwasm,team-web,triaged-web

![image](https://github.com/flutter/flutter/assets/17034/ffa17b1b-f2a0-4aa0-82b3-737e5886f068)

packages repo at 903f03add169c39d3f19bc70980af3f0862869a9

Flutter 3.21.0-1.0.pre.59 • channel master • git@github.com:flutter/flutter.git
Framework • revision 487d42f9ee (78 minutes ago) • 2024-03-07 15:28:23 -0500
Engine • revision c2863530ce
Tools • Dart 3.4.0 (build 3.4.0-211.0.dev) • DevTools 2.33.1
Repository: rust
Issue: inconsistent and confusing error message about first argument of `assert!`
Labels: A-diagnostics,T-compiler,D-confusing

### Code

```Rust
fn f(x: Result<i8, Box<dyn std::error::Error>>) {
    assert!(x.unwrap(), "expected Ok");      // expected `bool`, found `i8`
    assert!(x.unwrap_err(), "expected Err"); // cannot apply unary operator `!`
}
```


### Current output

```Shell
error[E0308]: mismatched types
 --> src/lib.rs:2:5
  |
2 |     assert!(x.unwrap(), "expected Ok");      // expected `bool`, found `i8`
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `bool`, found `i8`

error[E0600]: cannot apply unary operator `!` to type `Box<dyn std::error::Error>`
 --> src/lib.rs:3:5
  |
3 |     assert!(x.unwrap_err(), "expected Err"); // cannot apply unary operator `!` to type `Box<dyn std::error::Error>`
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot apply unary operator `!`
  |
  = note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)

Some errors have detailed explanations: E0308, E0600.
For more information about an error, try `rustc --explain E0308`.
```


### Desired output

_No response_

### Rationale and extra context

The macro `assert!` is documented as taking a bool as its first parameter. Therefore I suggest the error message be ``expected `bool`, found `i8` `` in both cases.

The very different error messages are very confusing, because `Result::unwrap` and `Result::unwrap_err` are basically the same. While I understand both error messages, I do not understand why they are different.

*Edit: I just realized it's probably because `i8` has an implementation of `std::ops::Not`. Still weird.*

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-unknown-linux-gnu
release: 1.76.0
LLVM version: 17.0.6
```


### Anything else?

_No response_
Repository: godot
Issue: CameraAttributes exposure doesn't affect unshaded materials, but auto exposure does
Labels: discussion,topic:rendering,topic:3d

### Tested versions

Reproducible in: 4.2.1,stable.official, 4.3.dev4.official

### System information

Godot v4.3.dev4 - Windows 10.0.22000 - Vulkan (Forward+) - integrated Intel(R) UHD Graphics (Intel Corporation; 26.20.100.7926) - Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8 Threads)

### Issue description

Unshaded materials will correctly stay unshaded when manually adjusting a CameraAttributes' exposure, but enabling auto exposure will brighten/darken them. Additionally, the exposure shader parameter doesn't seem to be affected by auto exposure.
Happens in both Forward+ and Mobile renderers.

### Steps to reproduce

Make a mesh with an unshaded material. Make a WorldEnvironment, give it camera attributes, enable Auto Exposure. Put them in the same scene and watch the magic happen.

### Minimal reproduction project (MRP)

[Auto Exposure MRP.zip](https://github.com/godotengine/godot/files/14530919/Auto.Exposure.MRP.zip)
Repository: flutter
Issue: Stop codesigning Flutter iOS and macOS frameworks when they are already codesigned
Labels: platform-ios,tool,P2,team-ios,triaged-ios

The tool is codesigning the Flutter.framework with the app developer cert on every build.

https://github.com/flutter/flutter/blob/d2ab6d9ac78bece19e111b37ef36ad4376dc7c6e/packages/flutter_tools/lib/src/build_system/targets/ios.dart#L299

However, with Apple's new 3rd party SDK codesigning requirements it seems like the more correct thing to do it leave the Flutter org codesigning instead of overwriting it with the developer cert.  However, this may block App Store submission of Flutter apps when the cert renews (old cert is revoked).  In that scenario if we release a signed version of the SDK in March, but the cert is refreshed in April, then potentially apps even on current stable would not be submittable to the App Store?

https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks
https://developer.apple.com/videos/play/wwdc2023/10060/

See https://github.com/flutter/flutter/issues/140934 for context.

Make sure we don't regress https://github.com/flutter/flutter/pull/93556. We need to sign the framework if it's not already codesigned (on the master channel).
Repository: flutter
Issue: Add new multi-view embedder APIs
Labels: engine,P3,a: multi window,team-engine,triaged-engine

Design doc: https://flutter.dev/go/multi-view-embedder-apis

* [x] https://github.com/flutter/engine/pull/51523
* [x] https://github.com/flutter/engine/pull/51400
* [x] https://github.com/flutter/engine/pull/51267
* [x] https://github.com/flutter/engine/pull/46174
* [x] https://github.com/flutter/engine/pull/46213 
* [ ] Dispatch semantics action
* [ ] Update semantics callback
* [ ] Option to disable the implicit view
* [ ] Verify embedder does not register callbacks that are incompatible with multiple views when using multi-view embedder APIs. Example callbacks that are incompatible: `FlutterProjectArgs.update_semantics_node_callback`, `FlutterProjectArgs.update_semantics_custom_action_callback` `FlutterProjectArgs.update_semantics_callback`, `FlutterOpenGLRendererConfig.present_with_info`



Part of https://github.com/flutter/flutter/issues/142845
Repository: flutter
Issue: A test suite I expect to be running (as part of a `bringup` build) is missing
Labels: team-infra,P2,triaged-infra

### Type of Request

bug

### Infrastructure Environment

LUCI

### What is happening?

A variant (different set of arguments) of a test does not appear on LUCI.

1. [Configuration](https://github.com/search?q=repo%3Aflutter%2Fengine+path%3Aci%2Fbuilders+%22--impeller-backend%3Dopengles%22+%22run_android_tests.dart%22+%22--force-surface-producer-surface-texture%22&type=code)
2. It's partner set, without a flag set, is [here](https://github.com/search?q=repo%3Aflutter%2Fengine+path%3Aci%2Fbuilders+%22--impeller-backend%3Dopengles%22+%22run_android_tests.dart%22&type=code).

However, only the second set (without "SurfaceTexture") appears to be running on CI:
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux%20Staging%20Engine%20Drone/92083/overview.

Maybe this is a "feature" of bringup where a failed test means all of the steps are skipped? I'm not sure. As a result of one of the sets not running, I can't approve the digests for Skia Gold.

### Steps to reproduce

_No response_

### Expected results

I expect to see both sets of tests run.
Repository: vscode
Issue: Web issue reporter does not respect the `options.issueBody` setting
Labels: bug,issue-reporter

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: (Technically no, but is related to API so yes)

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.88.0-insiders
- OS Version: Mac Sonoma 14.3.1

Steps to Reproduce:

1. Call the command `workbench.action.openIssueReporter` with the option `issueBody` set
2. Observe that this works in VS Code desktop version and not in vscode.dev

See https://github.com/microsoft/vscode/blob/main/src/vs/workbench/services/issue/browser/issueService.ts#L35, it seems like we can handle this parameter here by at least prepending/appending to the static template.
Repository: flutter
Issue: Update embedders to use new multi-view embedder APIs
Labels: engine,platform-mac,platform-windows,P2,a: multi window,team-linux,triaged-linux

Part of https://github.com/flutter/flutter/issues/142845

Requires https://github.com/flutter/flutter/issues/144806

Design doc: https://flutter.dev/go/multi-view-embedder-apis

* [ ] Windows
    * [x] Add view
    * [x] Remove view
    * [x] Present to view callback that's multi-view compatible
    * [x] Window metrics with view ID
    * [x] Pointer events with view ID
    * [ ] Accessibility
    * [ ] Disable the implicit view
* [ ] macOS
Repository: godot
Issue: DisplayServer.window_is_focused returns true for unfocused window after calling DisplayServer.window_set_flag
Labels: bug,platform:windows,topic:porting,topic:gui

### Tested versions

- Reproducible in v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3090 (NVIDIA; 31.0.15.5161) - 12th Gen Intel(R) Core(TM) i9-12900K (24 Threads)

### Issue description

DisplayServer.window_is_focused returns true for unfocused window after calling DisplayServer.window_set_flag. I expect DisplayServer.window_is_focused to return false when window is out of focus.

### Steps to reproduce

1. Start MRP
2. Press "ui_accept" event (space on keyboard)
3. Quickly switch to other window (on second monitor if possible, it's easier to observe)
4. Wait 5+ seconds
5. Stop MRP
6. Observer log in editor with dedup

### Minimal reproduction project (MRP)

[WindowFlagsBugMRP.zip](https://github.com/godotengine/godot/files/14531620/WindowFlagsBugMRP.zip)
Repository: rust
Issue: Confusing diagnostics when using RPIT in `Fn` return type
Labels: A-diagnostics,T-compiler,A-impl-trait,F-impl_trait_in_fn_trait_return

### Code

```Rust
#![feature(impl_trait_in_fn_trait_return)]

use std::future::Future;

//  ↓↓↓  remove this parameter and it works
fn f<H>() -> impl Fn() -> impl Future {
    || async {}
}
```


### Current output

```rust
error: concrete type differs from previous defining opaque type use
 --> src/lib.rs:6:8
  |
6 |     || async {}
  |        ^^^^^^^^ expected `impl Future`, got `{async block@src/lib.rs:6:8: 6:16}`
  |
note: previous use here
 --> src/lib.rs:6:5
  |
6 |     || async {}
  |     ^^^^^^^^^^^

error[E0720]: cannot resolve opaque type
 --> src/lib.rs:5:27
  |
5 | fn f<H>() -> impl Fn() -> impl Future {
  |                           ^^^^^^^^^^^ cannot resolve opaque type
```

This error message doesn't mention `<H>` or explain why it is a problem.

I tried reproducing the same error message with other chains of `impl`, but I could only reproduce with `FnOnce`, `Fn` and `FnMut`.


### Rust Version

```Shell
rustc 1.78.0-nightly (b6d2d841b 2024-03-05)
binary: rustc
commit-hash: b6d2d841bcf4b77343b159f134c7d39c2dd4ceaa
commit-date: 2024-03-05
host: x86_64-unknown-linux-gnu
release: 1.78.0-nightly
LLVM version: 18.1.0
```
Repository: PowerToys
Issue: Mouse without border copy and paste not working after lock screen a period of time later
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.79.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1. Enable mouse without border, everything is fine
2. lock the PC for a period of time, no matter sleep of just lock screen
3. wake both of PC, cursor movement is fine. But copy and paste feature is completely not working
4. restart Powertoy, everything work well again.

### ✔️ Expected Behavior

Copy and paste should be able to work at anytime

### ❌ Actual Behavior

Copy and paste feature is completely not working after lock screen

### Other Software

Windows 11, build 22631.3235
Repository: go
Issue: proposal: cmd/vet: reject unary min and max calls
Labels: Proposal

### Proposal Details

A unary `min` and `max` call is an identity function and its presence suggests a bug.

I had code that was doing the following:
```go
blockSize = min(max(r.minBlockSize, blockSize, r.maxBlockSize))
```
where the intent is to clamp `blockSize` within a certain range.

However, due to a single misplaced `)`, this does not work.
It should have been:
```go
blockSize = min(max(r.minBlockSize, blockSize), r.maxBlockSize)
```

I propose that `go vet` flag any unary calls to `min` or `max`, which would have caught my bug where I had 3 arguments passed to `max`, but only 1 argument passed to `min`.
Repository: PowerToys
Issue: Crop and Lock for screenshot 
Labels: Idea-Enhancement,Product-CropAndLock

### Description of the new feature / enhancement

add option to Crop and Lock to take a screenshot and make it always on top.

### Scenario when this would be used?

when I want to compare between two situations like previous output result and current output result.

### Supporting information

you can make a shortcut win+ctrl+shift+s
Repository: go
Issue: testing: TestDeepSubtestRace failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "testing" && test == "TestDeepSubtestRace"
```

Issue created automatically to collect these failures.

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

    --- FAIL: TestDeepSubtestRace (0.02s)
        testing_test.go:485: C:\Users\gopher\AppData\Local\Temp\1\go-build686162820\b001\testing.test.exe -test.run=^TestDeepSubtestRace$ -test.bench=TestDeepSubtestRace -test.v -test.parallel=2 -test.benchtime=2x: exit status 1
            === RUN   TestDeepSubtestRace
            === RUN   TestDeepSubtestRace/sub
            === RUN   TestDeepSubtestRace/sub/subsub
            === RUN   TestDeepSubtestRace/sub/subsub/subsubsub
            ==================
            WARNING: DATA RACE
            Write at 0x00c00000aa48 by goroutine 11:
              testing_test.doRace.func1()
    ...
              testing.(*T).Run.gowrap1()
                  C:/workdir/go/src/testing/testing.go:1742 +0x44
            ==================
                testing.go:1398: race detected during execution of test
            --- FAIL: TestDeepSubtestRace (0.00s)
                --- FAIL: TestDeepSubtestRace/sub (0.00s)
                    --- FAIL: TestDeepSubtestRace/sub/subsub (0.00s)
                        --- FAIL: TestDeepSubtestRace/sub/subsub/subsubsub (0.00s)
            FAIL
        testing_test.go:494: got 1 race reports, want 2


— [watchflakes](https://go.dev/wiki/Watchflakes)