sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Window surface shifted after resizing window (Godot 4, Windows)
Labels: bug,platform:windows,topic:rendering,topic:porting,topic:thirdparty

### Tested versions

- Reproducible in Godot v4.3.beta (97b8ad1af), v4.2.2.stable, v4.2.1.stable, v4.0.1.stable, v4.0.stable

### System information

Godot v4.3.beta (97b8ad1af) - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2080 (NVIDIA; 32.0.15.5599) - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 Threads)

### Issue description

After resizing the editor or a game window, the render of this window is at an offset.
It is still interactive with hover effects but misaligned. Moving the window fixes it.
The offset is always the same, that is about minus the client area offset in window rect.

Editor settings are vanilla. G-Sync is disabled.
It does not happen with the Compatibility renderer.
It does not happen with "Project Settings/General/Display/Window/V-Sync Mode" on Disabled.

![image](https://github.com/user-attachments/assets/103a450f-7278-46e1-b137-d5f82c51e8e7)

### Steps to reproduce

On Windows 10.
Use any project with Forward+ or Mobile renderer.
In Project Settings, check that "General/Display/Window/V-Sync Mode" is set to Enabled (if not, set it and reload).
Resize the editor from any side or corner until the backbuffer is drawn unaligned.
Release the mouse button and it stays like this until you move the window.

### Minimal reproduction project (MRP)

used empty project.
Repository: ant-design
Issue: v5 的 Checkbox 样式异常
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-lgqzry?file=demo.tsx)

### Steps to reproduce

打开 demo 看到 Checkbox 没有换行，都挤到一起了，但是 v4 时是好的 https://stackblitz.com/edit/react-sybvja?file=demo.tsx

v4 
![image](https://github.com/user-attachments/assets/d5f72ab5-eaa6-478c-9486-458c9e85bd2d)
v5
![image](https://github.com/user-attachments/assets/c9b7f0b7-1b1f-4940-9bd1-33293e493bfb)


### What is expected?

样式无异常

### What is actually happening?

样式异常

| Environment | Info |
| --- | --- |
| antd | 5.19.1 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: kubernetes
Issue: [Failing Test] [sig-node] [Feature:NodeLogQuery] should return the kubelet logs since the current date and time
Labels: sig/node,sig/windows,kind/failing-test,needs-triage

### Failure cluster [c302dcfeb8c00cdd8e31](https://go.k8s.io/triage#c302dcfeb8c00cdd8e31)

`kubelet kubectl get --raw "/api/v1/nodes/<insert-node-name-here>/proxy/logs/?query=/<insert-log-file-name-here> `

https://testgrid.k8s.io/sig-windows-master-release#capz-windows-master-alpha-features

ci-kubernetes-e2e-capz-master-windows-alpha


##### Error text:
```
[FAILED] error getting SSH client to capi@null:22: dial tcp: lookup null on 10.63.240.10:53: no such host
In [It] at: k8s.io/kubernetes/test/e2e/node/kubelet.go:719 @ 07/13/24 07:41:33.258

There were additional failures detected after the initial failure. These are visible in the timeline

```
#### Recent failures:
[2024/7/15 03:19:44 ci-kubernetes-e2e-capz-master-windows-alpha](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-master-windows-alpha/1812567601130246144)
[2024/7/15 00:19:37 ci-kubernetes-e2e-capz-master-windows-alpha](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-master-windows-alpha/1812522302407970816)
[2024/7/14 21:18:37 ci-kubernetes-e2e-capz-master-windows-alpha](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-master-windows-alpha/1812476751587053568)
[2024/7/14 18:17:36 ci-kubernetes-e2e-capz-master-windows-alpha](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-master-windows-alpha/1812431200719998976)
[2024/7/14 15:17:35 ci-kubernetes-e2e-capz-master-windows-alpha](https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-master-windows-alpha/1812385899397255168)


/kind failing-test
sinc 07-12/07-13
/sig node
Repository: ant-design
Issue: Transfer 穿梭框 可以有一个最多选择几项
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

oneWay单向选择模式下，客户需求是最多选4项，如果使用动态禁用目标数据也无法删除重新选择,想要超过maxCount时左侧无法新增选择，右侧还能删除，右侧删除后左侧可以重新选择

### What does the proposed API look like?

maxCount : number

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Converting a numpy array of size larger than 32,768 to a tensor causes a segmentation fault
Labels: needs reproduction,module: crash,triaged,module: macos,module: numpy

### 🐛 Describe the bug

Consider the following code:

```
import numpy as np
import torch

x_array = np.zeros([32769])  # Problem goes away if array is 32,768 elements or smaller
x_list = [x_array[i] for i in range(x_array.shape[0])]
torch.tensor(x_list)  # Works fine
torch.tensor(x_array)  # Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
```

The effects are as the comments indicate. A list works but the numpy array does not. I was initially working with a higher dimensional ndarray but worked my way down to a one dimensional one as I narrowed down the problem. 


### Versions

```
Collecting environment information...
PyTorch version: 2.3.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.5 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.3.9.4)
CMake version: Could not collect
Libc version: N/A

Python version: 3.12.2 | packaged by conda-forge | (main, Feb 16 2024, 20:54:21) [Clang 16.0.6 ] (64-bit runtime)
Python platform: macOS-14.5-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] torch==2.3.1
[conda] numpy                     1.26.4          py312h7f4fdc5_0  
[conda] numpy-base                1.26.4          py312he047099_0  
[conda] torch                     2.3.1                    pypi_0    pypi

```

cc @malfet @albanD @mruberry @rgommers
Repository: vscode
Issue: [VSC-Web] "renameFile" may conflict soft-keyboard
Labels: bug,file-explorer,under-discussion

    With a lengthy Files Explorer list, renaming files near the lower part of screen:
    May cause the on-screen soft-keyboard to repeatedly show/hide.
    .
    Effectively rendering the function unusable.

    Reproducible with: https://github.dev/FFmpeg/FFmpeg ("libavcodec")
    Affects touch input mostly. (not necessarily mobile browsers exclusive)

    Other alike text inputs are also susceptible. (e.g. those in "Settings")

&#x2D;---

Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
User Agent: Firefox 129
Embedder: github.dev

<!-- generated by web issue reporter -->
Repository: flutter
Issue: CupertinoMagnifier is not centered vertically with custom size
Labels: framework,f: cupertino,has reproducible steps,P2,team-design,triaged-design,found in release: 3.22,found in release: 3.24

### Use case

https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/cupertino/magnifier.dart 
class  CupertinoMagnifier  **kDefaultSize** should be **size**, in line 340 
![image](https://github.com/user-attachments/assets/b9b38e63-ef93-4ef7-ae72-b2b3db0c80c7)

if not ,when you custom size, focus not center 

### Proposal

when custom size , focus should be center
Repository: godot
Issue: "Class hides a global script class" script parsing issue
Labels: discussion,topic:gdscript,documentation

### Tested versions

v4.3.beta3.official [82cedc83c]

### System information

Godot v4.3.beta3 - EndeavourOS #1 SMP PREEMPT_DYNAMIC Wed, 12 Jun 2024 20:17:17 +0000 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2080 SUPER (nvidia; 550.90.07) - Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz (6 Threads)

### Issue description

In certain cases, you might decide to remake or otherwise archive a script, but still keep it in the project files in the original place. Usually all you need to do is rename the script to something to indicate it's archive or backup status. This isn't a problem normally, UNLESS you use the `class_name` declaration and want to keep the same name from the old script to the new one. Godot parses ALL scripts regardless of their actual use, so as a result, when two scripts declare the same `class_name` it fails to parse the script and breaks the game. This may be the intended behavior, but IMO, it shouldn't be parsing ALL scripts, but instead ONLY the scripts that will actually be ran.

EDIT: For my personal game project, this behavior doesn't seem to start until 4.2, and 4.3 makes it even more picky. Under 4.1.4, there is no issue in my game. However, I'm not sure what the reason is, and the only differences I see from the MRP are that my scripts are in subfolders, and the difference between 4.2 and 4.3 for my game is that 4.2 didn't have issue with scripts with the same name in different folders even with the same class_name, while 4.3 does have issue.

### Steps to reproduce

Create a script attached to a node.
Use the `class_name` declaration in this script.
Duplicate the script with a different name.
Parse error.

### Minimal reproduction project (MRP)

[global_script_class_issue.zip](https://github.com/user-attachments/files/16229931/global_script_class_issue.zip)
Repository: godot
Issue: Cannot copy-paste ButtonGroup reference in editor, must manually edit *.tscn file
Labels: bug,topic:editor,needs testing,topic:gui

### Tested versions

v4.3.beta3.mono.official [82cedc83c]

### System information

Windows 11 - Vulkan, Mobile | Samsung Galaxy S24 Ultra - Vulkan, Mobile

### Issue description

When trying to create a set of buttons with a shared ButtonGroup, I cannot simply copy-paste the ButtonGroup reference from the first button to the other buttons I want affected. Doing so duplicates it instead of copying the reference. Trying to manually copy the first button's ButtonGroup `resource_path` results in errors:
![image](https://github.com/user-attachments/assets/181bcc8a-9dda-4542-9cdd-1ec59acfc86b)

However, if I open the *.tscn file in a text editor and manually copy the `SubResource("ButtonGroup_a7xba")` between the desired buttons and re-open in the editor, it will work as expected.

### Steps to reproduce

From what I can tell, any attempts at using ButtonGroup in the editor is prone to this issue. I randomly get it to work as expected, but it isn't the common case and does not happen in a reproducible manner.

### Minimal reproduction project (MRP)

N/A
Repository: electron
Issue: [Bug]: Window CSD borders at the wrong position on ozone-wayland
Labels: platform/linux,bug :beetle:,component/BrowserWindow,has-repro-comment,wayland,31-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

31.0.0

### What operating system(s) are you using?

Other Linux

### Operating System Version

Arch Linux, rolling

### What arch are you using?

x64

### Last Known Working Electron version

30

### Expected Behavior

![gambar](https://github.com/user-attachments/assets/c94a26be-4d29-4095-aa88-7e3f2437a908)


### Actual Behavior

![gambar](https://github.com/user-attachments/assets/3e1ab56c-32ce-4bde-bed0-460a8fd4cc94)

https://github.com/user-attachments/assets/f5e2c36f-2df3-44b4-a38e-1cdc593d1ad7




### Testcase Gist URL

_No response_

### Additional Information

Both test cases are run with:  
`--ozone-platform-hint=auto` on GNOME wayland as electron only shows CSD titlebar in GNOME Wayland or Weston compositor. To notice the wrong border either install the rounded-window-corner-reloaded gnome extension and enable outline, or try to drag window titlebar to the top and see where it stops as per video.
Repository: transformers
Issue: Keep Tuple of past key values as an option
Labels: Feature request

### Feature request

I see [llama](https://github.com/huggingface/transformers/blob/main/src/transformers/models/llama/modeling_llama.py#L829-L835) will remove tuple past key values in 4.43.

### Motivation

The model outputs should always keep tuple type as an option. If we remove this, all models will be failed in jit trace.

### Your contribution

@gante Do you mind taking a look at it? Thx!

cc @amyeroberts
Repository: flutter
Issue: Add `onHover` in `Slider`
Labels: c: new feature,framework,f: material design,c: proposal,a: mouse,P3,workaround available,team-design,triaged-design

### Use case

I want to get some [`Slider`](https://api.flutter.dev/flutter/material/Slider-class.html) value when you hover over the `Slider` with the mouse, like [`onChanged`](https://api.flutter.dev/flutter/material/Slider/onChanged.html) but with Hover with the mouse.

### Proposal

I suggest adding `onHover` to the `Slider`.

like this:

```dart
Slider(
  value: _duelCommandment.toDouble(),
  min: 1.0,
  max: 10.0,
  divisions: 10,
  label: '$_duelCommandment',
  onHover: (double newValue) {  // This callback is suggested
    setState(() {
      _duelCommandment = newValue.round();
    });
  },
)
```
Repository: angular
Issue: Missing Portation of Page Managing Data
Labels: state: in investigation,P3,area: docs-infra

### Describe the problem that you experienced

Google Search lead to old Angular Page, which shows the deprecation warning. When clicking on **Head to Angular.dev**, the link to the page does not exist.

Old: https://v17.angular.io/start/start-data
New: https://angular.dev/tutorials/learn-angular/creating-an-injectable-service

### Enter the URL of the topic with the problem

https://angular.dev/tutorials/learn-angular/creating-an-injectable-service

### Describe what you were looking for in the documentation

I wanted a summary on where to handle and process data from a server. Ideally, this would involve a Readonly Signal that I can use in different components.

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

_No response_

### Provide any additional information here in as much as detail as you can

_No response_
Repository: next.js
Issue: Click the browser forward and back, and getServerSideProps does not re-execute
Labels: bug

### Link to the code that reproduces this issue

https://github.com/rick-liruixin/next-getServerSideProps-bug-demo

### To Reproduce

Page: categories/[...url].tsx

When navigating from
https://www.alexandermcqueen.cn/categories/women/ready-to-wear.html
to
https://www.alexandermcqueen.cn/categories/women.html,
and then to
https://www.alexandermcqueen.cn/categories/women/shoes.html,

Clicking the browser's forward and backward buttons to move between these pages sometimes causes getServerSideProps not to trigger.


The code is as follows：
```
export const getServerSideProps: GetServerSideProps<
  ServerSidePropsWithStatus,
  { url: Array<string> }
> = async ({ query, req: serverReq, res: serverRes }) => {
  const serverContext = { req: serverReq, res: serverRes }
  const paramsData = {
    q: '',
    page: 1,
    ...query,
    isAll: true,
  }
    const { data: res } = await api.search.getSearchResultWithLayer(
      paramsData,
      serverContext,
    )
    const initialQueryData = paramsData
    return {
      props: { q: query.q, initialQueryData, ...res.data },
    }
}
```

### Current vs. Expected behavior

Even though it's a single page, getServerSideProps should trigger every time we navigate forward and backward.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
Binaries:
  Node: 18.12.1
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: 8.2.0
Relevant Packages:
  next: 13.5.6
  eslint-config-next: 13.5.6
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.0.2
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next start (local), Vercel (Deployed)

### Additional context

Local recurrence rates are low, so I've listed online environments that can be accessed to see the problem
Repository: kubernetes
Issue: Add 100/1000s buckets for prometheus workqueue histograms QueueLatencyKey and WorkDurationKey
Labels: kind/feature,sig/instrumentation,triage/accepted

### What would you like to be added?

I 'd like to extend the already existing histograms QueueLatencyKey and WorkDurationKey with two additional buckets 100s and 1000s.

### Why is this needed?

Controllers making many external requests in large clusters may have normal operating latency on the order of ~100s. Add buckets that cover the range, allowing metric backends to interpolate percentile estimates properly. A good example is KCM HPA controller when talking to external metrics providers and using hundreds of HPA objects and external metrics..
This was already implemented in controller-runtime, see [issue ](https://github.com/kubernetes-sigs/controller-runtime/issues/2625)and merged [PR](https://github.com/kubernetes-sigs/controller-runtime/pull/2638).
Repository: next.js
Issue: next.config.ts does not support top-level-await
Labels: bug,TypeScript

### Link to the code that reproduces this issue

https://github.com/stefanprobst/issue-next.config.ts-await

### To Reproduce

- clone https://github.com/stefanprobst/issue-next.config.ts-await
- `pnpm install && pnpm run dev`
- see error message:

```
ReferenceError: await is not defined
```

### Current vs. Expected behavior

top-level await works in `next.config.js` but not in `next.config.ts`.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #41~22.04.2-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun  3 11:32:55 UTC 2
  Available memory (MB): 15893
  Available CPU cores: 4
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: N/A
  pnpm: 9.5.0
Relevant Packages:
  next: 15.0.0-canary.67 // Latest available version is detected (15.0.0-canary.67).
  eslint-config-next: N/A
  react: 19.0.0-rc.0
  react-dom: 19.0.0-rc.0
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


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

TypeScript

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

next dev (local)

### Additional context

_No response_
Repository: excalidraw
Issue: super slow when zoomed in with disappearing elements
Labels: bug,performance ⚡️

recording while zooming in with trackpad (notice the fps):

https://github.com/user-attachments/assets/ca1b8c7f-f3ed-47d0-ae7e-d7dcdce681ce

repro scene:
https://excalidraw.com/#json=1SbjsdotedadDg7pM4Ahp,z9uJCfl5W8d73Id6x_xVcw

system info:
- Arc 1.51.0
- MacOS: 14.2.1
Repository: storybook
Issue: [Request]: Add version checksum in main.js 
Labels: feature request,cli

### Problem

We're having trouble figuring out if Storybook users are using the `npx storybook@latest upgrade` to upgrade Storybook, or if they do it manually or via other ways. If we could know for sure whether they've upgraded Storybook correctly, we could provide much better help to fix their issues.

### Solution

Every time someone runs the Storybook upgrade command, we'll track the old and new versions, create a checksum with that info, and add it to `.storybook/main.ts`. This checksum will help us with telemetry so we know if users are using the upgrade command, and we can also use it to check at runtime if Storybook is installed correctly. If some packages don't match the expected version, we'll prompt users to run the upgrade command to fix the issue and update the checksum.

When users run `npx storybook@latest upgrade`, detect the from and to versions, create a checksum string with this info. Here's an example with base64 encoding:

```ts
const encodeChecksum = (fromVersion: string, toVersion: string): string => {
  return Buffer.from(`${fromVersion}|${toVersion}`).toString('base64');
};

const decodeChecksum = (checksum: string): { fromVersion: string, toVersion: string } => {
  const [fromVersion, toVersion] = Buffer.from(checksum, 'base64').toString('utf8').split('|');
  return { fromVersion, toVersion };
};
```

Then add it to `.storybook/main.ts` e.g.:

```ts
import { StorybookConfig } from '@storybook/react-vite'

const config: StorybookConfig = {
  //...
  checksum: 'OC4xLjF8OC4yLjA=' // '8.1.1|8.2.0'
}
export default config
```

Later on, at runtime, the checksum will be parsed to extract the target version.
The extracted version will be compared against the installed Storybook packages.
If discrepancies are found (e.g., some packages match the version while others do not), an error will be thrown, prompting users to run the upgrade command again.
Repository: ant-design
Issue: Opening dropdown in wrong direction
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://codepen.io/RezDmitryDev/pen/mdZeVOp](https://codepen.io/RezDmitryDev/pen/mdZeVOp)

### Steps to reproduce

1) Hover "bugged" button

### What is expected?

Dropdown open from down to up (like top* placements)

### What is actually happening?

Dropdown open from up to down (like bottom* placements)

| Environment | Info |
| --- | --- |
| antd | 5.19.2 |
| React | 18.2.0 |
| System | macOS 14.5 |
| Browser | Chrome 126.0.6478.127 |

---
It reproduced if dropdown window is so closed to right border and down of screen and dropdown can't open how usually (see notBugged case for no-bug case)

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->