sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: snapshot generate on Macbook with extended display contains diffs
Labels: bug,needs triage

### Describe the bug

The image snapshot generated on Macbook without an extended display (i.e. without connecting to a monitor or mirror the Macbook display) is different then the one generated on the same Macbook connected to an external display (e.g. to a 34 inch Dell monitor).

This holds true even when the viewport size is fixed to a certain resolution (by default it is already fixed to a certain resolution, and setting to a fixed resolution with `page.setViewportSize()` does not mitigate the issue).

My guess is that, this is caused by the screen scaling mechanism in Macbook or in Chromium.
Maybe things like `--force-device-scale-factor=1`or something like disabling hardware acceleration could address that.

But currently, I don't see a way to control that from storybook (or playwright).

Marking this as a bug as optimally this should be handled with zero-config by `test-storybook` to eliminate these differences.

### To Reproduce

Will see if I can create an open source repro for this. But basically any repro with image snapshot on a macbook with external display should be able to repro this.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.3.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.20.2 - ~/.nvm/versions/node/v16.20.2/bin/node
    npm: 8.19.4 - ~/.nvm/versions/node/v16.20.2/bin/npm
    pnpm: 8.13.1 - ~/.nvm/versions/node/v16.20.2/bin/pnpm <----- active
  Browsers:
    Chrome: 122.0.6261.129
    Safari: 17.3.1
  npmGlobalPackages:
    storybook: 7.6.6
```


### Additional context

_No response_
Repository: tauri
Issue: [docs] Broken example for WebDriverIO
Labels: type: documentation

As suggested on Discord, I am opening an issue here. You can find relevant information about it on the original issue linked here https://github.com/chippers/hello_tauri/issues/4
Repository: go
Issue: x/build: consider transitioning from Corellium based iOS builders to Apple Simulator based builders
Labels: Builders,NeedsInvestigation,new-builder,OS-iOS

The iOS builders are currently broken, and have been for quite a while (see https://ci.chromium.org/ui/p/golang/builders?q=ios and https://farmer.golang.org/#active). It's unclear what work is necessary to fix them.

Corellium is a somewhat strange platform to be testing on, as it is (a) emulating jailbroken iOS, which is likely to be representative of a minority of Go code run on iOS, and (b) unclear what version of iOS is being emulated. It is also a commercial product, so spinning up more builders, or better builders etc, is likely to incur some financial burden.

This issue proposes moving away from the Corellium based builders, and instead using the official Apple iOS Simulator, for which we already have _most_ of the required machinery to do. This would allow us to use existing darwin builders (or new darwin builders that come from the same source) to run iOS tests, instead of relying on the current third-party maintained builders.

[misc/ios](https://github.com/golang/go/tree/master/misc/ios) contains slightly out of date tools that allow executing Go binaries on the iOS simulator by wrapping them in an app bundle and using the `xcrun simctl` tools to run them. These tools predate the arm Apple silicon, so need a little updating to work on newer machines, but I was able to quickly update them to reliably work on arm64 macos.

Most of the complexity of these tools is because they are written to work on both the iOS simulator and real devices, but could be reasonably updated to be somewhat more streamlined and efficient (i.e. only supporting the simulator, or split into tools specifically for the simulator and real devices, and removing the reliance on the debugger which doesn't seem strictly necessary. There is probably also some work to be done to reduce the need to move large parts of the source tree back and forth from the simulator when testing the entire tree).

The only delta between the existing darwin builders and iOS specific builders would be additionally installing the xcode simulator runtime, and setting `GOOS=ios`.

cc @golang/release @changkun
Repository: go
Issue: proposal: maps,cmd/compile: special case and/or add function for getting an arbitrary entry from a map
Labels: Proposal,compiler/runtime

### Proposal Details

Sometimes people try to get a random key/value out of a map, writing:

```go
       for k, v = range m {
            break
       }
```

One example is/was in `database/sql`. Unfortunately, it uses a lot of CPU:

<img width="633" alt="Screenshot 2024-03-16 at 8 57 01 PM" src="https://github.com/golang/go/assets/2621/37ca0d0d-6965-41d8-a5dd-519e20b9cd19">

So I rewrote it in https://go-review.googlesource.com/c/go/+/572119

An alternative is the compiler could recognize that pattern: a range with a body containing only a `break`.

If so, the compiler could insert a call to a runtime func that takes 2 pointers (either/both of which may be nil) and updates them to a random map value if the map has non-zero length. If it's empty, the pointers are unmodified.

/cc @golang/compiler @maisem @raggi
Repository: kubernetes
Issue: nfs umount gets stuck when pod is destroyed
Labels: kind/bug,sig/storage,needs-triage

### What happened?

when deleting a statefulset, the pod gets stuck in "terminating" state. The node where the pod is scheduled, develops a high iowait time. If another pod on that node fails to terminate then iowait increases with the multiple stuck nfs mounts. no way to clear the iowait, have to reboot the node.  `kubectl delete pods podname --force -n namespace` does remove the pod k8s, but does not fix the stuck nfs mount. If I dont't force delete the pod, the pod can't be restarted.

### What did you expect to happen?

when pod is deleted the node should be able to umount the nfs mount.

### How can we reproduce it (as minimally and precisely as possible)?

I can't reproduce the error. I have many statefulsets that are created and deleted with a random pod which gets stuck.

### Anything else we need to know?

I am mounting a nfs volume from an external nfs server. I am not using a nfs provisioner.

```
spec:
  volumes:
    - name: data
      nfs:
        server: nfs1.storage.server.com
        path: /home/brad
```


nfs client config on node
```
[ NFSMount_Global_Options ]
        #rsize=1048576
        #wsize=1048576
        soft
        timeo=50
        nfsvers=4.1
        retry=5
```

nfs server export
```
/home  10.10.30.0/24(rw,sync,no_wdelay,no_root_squash,no_subtree_check,insecure)
```

### Kubernetes version

<details>

```console
$ kubectl version
#Client Version: v1.28.7
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.2

```

</details>


### Cloud provider

<details>
bare metal
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

$ uname -a
Linux adm-wk1 5.15.0-1051-kvm #56-Ubuntu SMP Thu Feb 8 23:30:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux


# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>
kubeadm
</details>


### Container runtime (CRI) and version (if applicable)

<details>
containerd 1.7.2
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>
cni - flannel
csi - none
</details>
Repository: pytorch
Issue: [MPS] torch.nn.functional.linear produces non-negligible error when input size is large enough
Labels: triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

Running `F.linear` in MPS produces non-negligible (stddev > 1) error when input size is large enough. (see the following code snippet to reproduce)

However, when we use `torch.stack([F.linear(...)])` to perform effectively the same operation in MPS, there is no error, proving that there is side effect when the input to `F.linear` is large enough. (In this case, using a batch size of `9` causes the error to surface, while batch size of `1` doesn't)

Minimal code to reproduce:

```python
import torch
import torch.nn.functional as F

torch.manual_seed(1234)
w = torch.randn(50304, 1)
x = torch.randn(9, 1024, 1)

# these 5 operations should be equivalent
linear_out_cpu = F.linear(x, w, None)
linear_out_mps = F.linear(x.to('mps'), w.to('mps'), None).to('cpu')
linear_out_mps_split_and_stack = torch.stack([F.linear(xb.to('mps'), w.to('mps')) for xb in x]).to('cpu')
matmul_out_cpu = x@w.T
matmul_out_mps = (x.to('mps')@w.T.to('mps')).to('cpu')

# All True, as expected
print(f'{linear_out_cpu.allclose(matmul_out_cpu)=}')
print(f'{linear_out_cpu.allclose(matmul_out_mps)=}')

print('=== BUG ===')
# BUG ==> Expect this to be True, got False instead
print(f'{linear_out_cpu.allclose(linear_out_mps)=}')
print(f'{(linear_out_cpu - linear_out_mps).std()=}')

print('=== PROOF (& WORKAROUND) ===')
# Splitting the batches can "workaround" the above BUG
print(f'{linear_out_cpu.allclose(linear_out_mps_split_and_stack)=}')

# Example output:
'''
linear_out_cpu.allclose(matmul_out_cpu)=True
linear_out_cpu.allclose(matmul_out_mps)=True
=== BUG ===
linear_out_cpu.allclose(linear_out_mps)=False
(linear_out_cpu - linear_out_mps).std()=tensor(1.2962)
=== PROOF (& WORKAROUND) ===
linear_out_cpu.allclose(linear_out_mps_split_and_stack)=True
'''
```

I think #109457 is related, and possibly #117826

### Versions

```
PyTorch version: 2.4.0.dev20240316
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.2.1 (arm64)
GCC version: Could not collect
Clang version: 17.0.1
CMake version: version 3.27.1
Libc version: N/A

Python version: 3.12.1 | packaged by Anaconda, Inc. | (main, Jan 19 2024, 09:45:58) [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-14.2.1-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 M2 Ultra

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.2.1
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] pytorch                   2.4.0.dev20240316        py3.12_0    pytorch-nightly
[conda] torch                     2.2.1                    pypi_0    pypi
```

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen @razarmehr
Repository: godot
Issue: SkeletonIK3D target rotates on incorrect axis
Labels: bug,topic:animation,topic:3d

### Tested versions

reproducible in 4.1.1 and 4.2.1 (IK was nonfunctional in 4.0)

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3090 (NVIDIA; 31.0.15.3713) - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)

### Issue description

The rotation of the target rotates the end effector on what seems to be an incorrect axis. For example, rotating about the Y axis seems to rotate the bone about the Z axis instead.

May be related to #54891

### Steps to reproduce

1. Open the test project (Imported VRM + SkeletonIK3D node + Node3D target)
2. Open test.tscn
3. Select SkeletonIK3D
4. Click "Play IK" in the 3d scene toolbar
5. Select the target "Node3D"
6. rotate it on the red or blue axes
7. You will see the foot rotates about the incorrect axis.

### Minimal reproduction project (MRP)

[skeletonik3d_issue.zip](https://github.com/godotengine/godot/files/14626299/skeletonik3d_issue.zip)
Repository: PowerToys
Issue: [KBM] enable "chords" for "send to" as well (now it's only available for keys mapped from
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

enable chords for "send to" so that the destination combo can also use 4+ keys

![image](https://github.com/microsoft/PowerToys/assets/133556394/b8fbc9a2-4924-44f3-9875-db93d378f148)


### Scenario when this would be used?

to delete a line on mac, you can simply do cmd+delete

on win 11, this is shift + home + del. if i want to map ctrl + del to shift + home + del, i couldn't do that because only the "from" part supports chords. the "to" part doesn't have chords option

### Supporting information

tried latest 0.79 version. chords is only available for "map from"
Repository: ui
Issue: [Bug]:  Parsing error: Cannot find module 'next/babel'
Labels: bug

### Describe the bug

next.config.mjs throws error

Make sure that all the Babel plugins and presets you are using
are defined as dependencies or devDependencies in your package.json
file. It's possible that the missing plugin is loaded by a preset
you are using that forgot to add the plugin to its dependencies: you
can workaround this problem by explicitly adding the missing package
to your top-level package.json

### Affected component/components

next/babel error

### How to reproduce

Create file called .babelrc in your root directory and add this code: 
`{
  "presets": ["next/babel"],
  "plugins": []
}`
you can skip creating .babelrc file and go directly to .eslintrc and change the code inside, And in .eslintrc, replace the existing code with:
`{
  "extends": ["next/babel","next/core-web-vitals"]
}`

### Codesandbox/StackBlitz link

please add a reproduction

### Logs

```bash
nothing
```


### System Info

```bash
3301
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [ ] I've searched for existing issues
Repository: ui
Issue: [Bug]:  Cloudinary Unhandled Runtime Error 
Labels: bug

### Describe the bug

While uploading an image from your computer files using cloudinary provider, it throws you an error saying:
Error: Invalid src prop. 

### Affected component/components

Cloudinary image uplaoding box

### How to reproduce

Go to your next.config.mjs file 
replace the code inside with this instead :
`/** @type {import('next').NextConfig} */
const nextConfig = {
    images: {
        domains: [
            /** @host */
            "res.cloudinary.com"
        ]
    }
};

export default nextConfig;`

Your problem has been solved .

### Codesandbox/StackBlitz link

please add a reproduction

### Logs

```bash
nothing
```


### System Info

```bash
3301
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: Use JPEG XL instead of PNG for golden tests to save repo space
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Use case

We have a lot of golden tests in our projects, and they keep changing. As they are commited to source control, I feel like we can use a better format to save repo space. Currently, flutter uses PNG.

### Proposal

Simply use lossless JPEG XL instead of PNG. It offers around 40%~50% savings per file. [ref](https://docs.google.com/spreadsheets/d/1ju4q1WkaXT7WoxZINmQpf4ElgMD2VMlqeDN2DuZ6yJ8/edit#gid=1919028011)
Repository: rust
Issue: WASM+simd128 codegen of `a.simd_eq(Simd::splat(b)).any()` deteriorates as width increases
Labels: A-LLVM,I-slow,A-codegen,O-wasm,A-SIMD,I-heavy,requires-nightly,PG-portable-simd,S-has-mcve,C-optimization

The compiler lowers the following code to a [200+ instruction long scalar sequence](https://godbolt.org/z/45naET7cW) on WASM+simd128:

```rust
#![feature(portable_simd)]
use core::simd::prelude::*;

fn f(a: u16x32, b: u16) -> bool {
    a.simd_eq(Simd::splat(b)).any()
}
```

The 256-bit wide version could also arguably use some work (for example could be compiled like [this](https://godbolt.org/z/z6szEvxjo)), but it's not catastrophically heavy and I don't really have any benchmarks to claim that it's slow.

### Meta
`rustc --version --verbose`:
```
rustc 1.78.0-nightly (c67326b06 2024-03-15)
binary: rustc
commit-hash: c67326b063bd27ed04f306ba2e372cd92e0a8751
commit-date: 2024-03-15
host: x86_64-unknown-linux-gnu
release: 1.78.0-nightly
LLVM version: 18.1.0
Compiler returned: 0
```
Repository: PowerToys
Issue: The movement of the window is severely lagged and slow
Labels: Issue-Bug,Product-Settings,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

GitHub, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

General, File Locksmith, Settings, Welcome / PowerToys Tour window

### Steps to reproduce

The latency is very bad when I drag the window with the mouse, it's still moving slowly after my action is already done.
[PowerToysReport_2024-03-17-15-30-22.zip](https://github.com/microsoft/PowerToys/files/14626554/PowerToysReport_2024-03-17-15-30-22.zip)

### ✔️ Expected Behavior

Should be normal fast clean and fluent dragging of windows.

### ❌ Actual Behavior

The movement of the window is severely lagged and slow.

### Other Software

null
Repository: ollama
Issue: Request for using RyzenAI
Labels: feature request

### What are you trying to do?

Hi, Are there any plans to incorporate RyzenAi into Ollama? It would be great breakthrought in running larger models.
As in demo from AMD it seems quite fast.
https://www.youtube.com/watch?v=AlZXBlLYSDE

Thank you.
BR
Krzysztof

### How should we solve this?

_No response_

### What is the impact of not solving this?

_No response_

### Anything else?

_No response_
Repository: neovim
Issue: autocommand event when a mark is created
Labels: enhancement,events

### Problem

I am writing a plugin for neovim that aims to provide training for new users. A task I would like to implement eventually is the creation of marks. My code uses autocommands to act after the user has interacted with neovim. As far as I can tell, there is no autocommand-event that fires after a mark has been created. 

### Expected behavior

The solution seems straightforward from the outside: Add a autocommand-event that is triggered after mark creation. Since I am not familiar with the codebase, I have trouble deciding how much effort this actually is. If there is some positive feedback, I might attempt a pr for this use case myself.
Repository: deno
Issue: `addInitializer` doesn't work on class field decorators
Labels: bug,upstream,swc

Version: Deno 1.41.3

```ts
function FieldDec(_: undefined, context: ClassFieldDecoratorContext) {
  const name = context.name;

  context.addInitializer(function () {
    // Will never be called
    console.log(name, "Hello field");
  });
}

function ClassDec(_: unknown, context: ClassDecoratorContext) {
  context.addInitializer(function () {
    // Will be called
    console.log("Hello Class");
  });
}

@ClassDec
class A {
  @FieldDec
  a: number = 0;
}

new A();
```

I expect Deno to print both "Hello Class" and "Hello field" in this reproduction code, however, only "Hello Class" is being printed.
Repository: PowerToys
Issue: AlwaysOnTop - Unclear notification message 
Labels: Issue-Bug,Product-Always On Top,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

So now and then I get a notification from "Always on Top" that's unclear. If i click on the notification message it's disappear and nothing else happend. 

The message in Dutch: "We hebben een toepassing gevonden die wordt". Freely translated in English: "We found an application that" 

### ✔️ Expected Behavior

That the notification message is displaying the full message and not a phase of a message.

That when I click on the notofication message, something happend to explain it (dialog box or something) and/or with options how to response for solving it.

### ❌ Actual Behavior

Notification message is just a phrase of a sentence, not the full message.
 When click on the notification message, nothing happend, the message just disappear.

![Schermafbeelding 2024-03-17 105934](https://github.com/microsoft/PowerToys/assets/79010792/d9624ade-3b3d-4920-8c76-8bf2e77028b4)




### Other Software

Editie	Windows 11 Pro
Versie	24H2
Installatiedatum	‎13-‎3-‎2024
Build van besturingssysteem	26080.1201
Ervaring	Windows Feature Experience Pack 1000.26100.1.0
Repository: TypeScript
Issue: TypeScript right adapt constructor
Labels: Needs More Info

### 🔍 Search Terms

I have implemented a function `JavaAdapter` to inherit classes and return instantiated objects. Now I'm creating a declaration for it.

```typescript
type ProxyMethods<T extends object> = { [K in keyof T]?: T[K] } | {};

declare function JavaAdapter<T, K extends ProxyMethods<T>, Args>(
  className: new (...args: Args) => T,
  override: K,
  ...args: Args
): K & T;
```

In most cases, it works fine. However, when the inherited object has multiple constructor functions with different parameter counts, it cannot accurately match, for example:
```typescript
JavaAdapter(
  android.widget.Button,
  {
    setOnClickListener(view) {
      console.log(view);
    },
  },
  activity,
  // new android.util.AttributeSet()
);
```
This usage is correct and matches one of the constructor functions, but TypeScript prompts "Expected 4 arguments, but got 3." It works only when I add new android.util.AttributeSet(). The partial declaration of `android.widget.Button` is as follows:
```typescript
declare module android {
  export module widget {
    class Button {
      public setOnClickListener(view: this): void;
      public constructor(context: android.content.Context);
      public constructor(context: android.content.Context, attribute: android.util.AttributeSet);
    }
  }
}
```
Besides changing to `constructor(context: android.content.Context, attribute?: android.util.AttributeSet);`, can TypeScript better adapt?

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

TypeScript matches correctly based on parameters

### 📃 Motivating Example

Enhance the user experience of typescript

### 💻 Use Cases

1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?