sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Font choice can cause ui misalignment
Labels: topic:gui

### Godot version

v4.2.dev.custom_build [eca6f0eb5]

### System information

Windows 10, Forward+, NVIDIA GeForce GTX 1050 Ti (31.0.15.3179)

### Issue description

When placing a LineEdit and a HSlider into a VBoxContainer inside a HBoxContainer, the LineEdit and the HSlider can become misaligned depending on the font that is used for the LineEdit box.

The issue is probably not limited to this setup, but this is my test case.

![font-align-issue](https://github.com/godotengine/godot/assets/10490534/31bb8481-1151-4ce0-a1e6-0f413f8d64d8)
Notice how the upper box (LineEdit) is closer to the red line on the right side than the lower box (HSlider)
I have given the boxes custom style boxes to showcase the issue easier with hard edges. However, the issue is the same with default style boxes.

### Steps to reproduce

- Control node that spans the screen
    - Create a child HBoxContainer centered in the Control node's region
        - Create a child VBoxContainer centered in the HBoxContainer node's region
            - Create a child LineEdit with fill horizontal alignment in the VBoxContainer's region
            - Create a child HSlider with fill horizontal alignment in the VBoxContainer's region
- Give the root Control node a theme
- Change the font of the theme - the alignment of the LineEdit and the HSlider nodes will differ depending on the font

### Minimal reproduction project

This MRP has the setup listed in the Steps to Reproduce.
Additionally, the LineEdit and HSlider have custom themes to make the issue more visible.
[test theme align.zip](https://github.com/godotengine/godot/files/12296808/test.theme.align.zip)
Repository: flutter
Issue: [Impeller] Make uniform buffer offset alignments dynamically calculated.
Labels: P3,e: impeller,team-engine,triaged-engine

Today, the [offset alignments are hardcoded](https://github.com/flutter/engine/blob/29b117aa4192fbe1757d98ed37913675ff4390d3/impeller/core/platform.h#L14) and only really make sense for Metal. This must be made dynamic per platform and client rendering API. Without this, applications are susceptible to running into validation errors like:

```
E/flutter ( 7530): [ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure:
E/flutter ( 7530): --- Vulkan Debug Report  ----------------------------------------
E/flutter ( 7530): |                Severity: Error
E/flutter ( 7530): |                    Type: { Validation }
E/flutter ( 7530): |                 ID Name: VUID-VkWriteDescriptorSet-descriptorType-00327
E/flutter ( 7530): |               ID Number: -36706146
E/flutter ( 7530): |       Queue Breadcrumbs: [NONE]
E/flutter ( 7530): |  CMD Buffer Breadcrumbs: [NONE]
E/flutter ( 7530): |         Related Objects: Device [12970367432599348128] [ImpellerDevice]
E/flutter ( 7530): |                 Trigger: Validation Error: [ VUID-VkWriteDescriptorSet-descriptorType-00327 ] Object 0: handle = 0xb4000075c26123a0, name = ImpellerDevice, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xfdcfe89e | vkUpdateDescriptorSets(): pDescriptorWrites[0].pBufferInfo[0].offset (0x340) must be a multiple of device limit minUniformBufferOffsetAlignment 0x100. The Vulkan spec states: If descriptorType is VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, the offset member of each element of pBufferInfo must be a multiple of VkPhysicalDeviceLimits::minUniformBufferOffsetAlignment (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkWriteDescriptorSet-descriptorType-00327)
E/flutter ( 7530): -----------------------------------------------------------------
```
Repository: pytorch
Issue: Use expect tests for error inputs
Labels: triaged,better-engineering,module: testing

### 🐛 Describe the bug

If I change an error message, it shouldn't be necessary to go manually update every single error input for the new format. This is exactly what expect tests are designed to do.

Example of this in practice: https://github.com/pytorch/pytorch/pull/106788

### Versions

master
Repository: next.js
Issue: Full page reload on save / on keystroke if autosave is on
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2
    Binaries:
      Node: 16.15.1
      npm: 8.11.0
      Yarn: 1.22.19
      pnpm: 8.6.12
    Relevant Packages:
      next: 13.4.13
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

n/a

### To Reproduce

- Run the latest next package in dev mode with pages router

### Describe the Bug

- Once you save your changes, the entire page reloads. 
- If you have autosave on, then there is full page reloads on each keystroke

### Expected Behavior

- No full-page reload on save / on keystroke when autosave is enabled

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: deno
Issue: `removeEventListener` removes listeners with different `capture`
Labels: bug

`EventTarget.prototype.removeEventListener` removes a listener even if it has a different `capture`.

```ts
const target = new EventTarget();
const fn = () => {
  fn.called = true;
};
declare const event: string;
target.addEventListener(event, fn, true);
target.removeEventListener(event, fn, false);
target.dispatchEvent(new Event(event));

console.assert(fn.called);
```

The same listener is always removed.

https://github.com/denoland/deno/blob/03e963f57831367a39996c7d88bc9875e97d52d7/ext/web/02_event.js#L1040-L1042

Spec ref: https://dom.spec.whatwg.org/#dom-eventtarget-removeeventlistener
Repository: next.js
Issue: nextjs failed to run the development server (npm run dev)
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
$ npx --no-install next info

    Operating System:
      Platform: win32
      Arch: ia32
      Version: Windows 10 Home
    Binaries:
      Node: 18.16.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

npm run dev

### To Reproduce

I installed the nextjs `npx create-next-app@latest`. 
Then I run 'npm run dev'. 

### Describe the Bug

**Here's the terminal message:**
`$ npm run dev`

`> salon@0.1.0 dev`
`> next dev`

`- ready started server on 0.0.0.0:3000, url: http://localhost:3000`
`- info Using wasm build of next-swc`

**And then within a second, the command automatically stopped and closes itself in the terminal (no other errors or messages, just simply auto terminates).** 

**Here are what I have tried to resolve and nothing works - I work in PC:**
- uninstalled node and re-installed the latest node package 
- restarted pc multiple times
- added .babelrc per nextjs documentation [here](https://nextjs.org/docs/messages/failed-loading-swc)
- reinstalled microsoft visual c++
- deleting the node moduls and package-lock and reinstalling
- deleting everything and restarting download the packages
- deleted folder and try in a brand new folder

### Expected Behavior

I expect the `npm run dev` will compile in the terminal -> so when I open 3000 server, I will see something running in the webpage. However it never compiles. 

### Which browser are you using? (if relevant)

Chrome

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: HtmlElementView Scroll Onclick event conflict
Labels: engine,platform-web,has reproducible steps,P2,found in release: 3.10,team-web,triaged-web,found in release: 3.13

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

This is an inevitable problem, I wrote a demo for reference.https://github.com/zjrwdl/html_element_view_scroll_issue
In this issue https://github.com/flutter/flutter/issues/68903, Although the sliding problem can be solved, it leads to the problem that the player cannot be played. @bwysistemas
In my sample, You can use the sd parameter usePointerIntercept to control whether to enable point_intercept
` IframeYoutubePlayer(
      url: url,
      usePointerIntercept: false,
  ),`

@ditman 

### Expected results

My expectation is that when the mouse stays in the youtube list, it can scroll normally, and at the same time click the youtube video play button to play normally

### Actual results

1. The default result is that the mouse stays on the youtute list and cannot scroll
2. If the [point_intercept](https://pub.dev/packages/pointer_interceptor/example) component is used, the scrolling problem can be solved, but the youtube player cannot be clicked to play normally

### Code sample

https://github.com/zjrwdl/html_element_view_scroll_issue

### Screenshots or Video

before use point_intercept

<img width="1417" alt="image" src="https://github.com/flutter/flutter/assets/6874049/8cbd44be-2a77-45dd-98ca-d07a4a0857c4">

after use point_intercept:

<img width="676" alt="image" src="https://github.com/flutter/flutter/assets/6874049/0e54493d-2d1d-48ab-b3ce-d8c5c40a2826">



### Logs

_No response_

### Flutter Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.2, on macOS 11.6 20G165 darwin-x64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] Connected device (2 available)
[✓] Network resources
Repository: PowerToys
Issue: Feature request: Mouse Without Keyboard
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

To be able to select anything on the screen with keyboard shortcuts

Example:

App that has this feature:
Fluent Search
https://www.fluentsearch.net/


https://github.com/microsoft/PowerToys/assets/52963184/bac320fb-cb8c-43bd-83c8-03e000cd0653

Pressed 'Ctrl+Space' to bring the shortcuts overlay
Then SQ(Desktop) -> KA(Home) -> G(Win (A:)) -> KS (Windows)


Works on All apps
Word-
![image](https://github.com/microsoft/PowerToys/assets/52963184/5a06a92f-29bf-4fde-b2fd-ff23789c558a)

MS Edge-
![image](https://github.com/microsoft/PowerToys/assets/52963184/8169f360-620d-4f06-b0c2-7d36c732b6e7)

Spotify
![image](https://github.com/microsoft/PowerToys/assets/52963184/e8055e7f-90b6-4441-900d-311c44d0c52f)


### Scenario when this would be used?

When user would like to press one thing on the screen without reaching for the mouse

### Supporting information

App that has this feature:
Fluent Search
https://www.fluentsearch.net/
https://github.com/adirh3/Fluent-Search
Repository: next.js
Issue: How to adjust the generation order of UI Components library styles and custom styles? 
Labels: bug

### Verify canary release

- [x] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 20.6.0: Thu Jul  6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_X86_64
    Binaries:
      Node: 18.14.0
      npm: 9.3.1
      Yarn: 1.22.19
      pnpm: 7.16.0
    Relevant packages:
      next: 13.4.6
      eslint-config-next: 13.4.6
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/strange-darkness-cc7pjp?file=%2Fpages%2Ftest%2Findex.tsx

### To Reproduce

Please see here: https://github.com/vercel/next.js/discussions/53714

### Describe the Bug

I have noticed that when utilizing the `antd ui ` library, the default component styles may take precedence over the custom styles applied to the page.

![image](https://github.com/vercel/next.js/assets/12181423/a8ac11f9-0c43-42e9-b26b-af7b66674607)

![image](https://github.com/vercel/next.js/assets/12181423/9d3a8fbb-b1da-4df9-8ddf-36f4107caa00)
![image](https://github.com/vercel/next.js/assets/12181423/e7f1aa37-edc6-4826-ad63-857bdcfebf2a)
![image](https://github.com/vercel/next.js/assets/12181423/8081f44b-4dac-4a42-b410-1b9d8e1261de)


### Expected Behavior

Component library styles should be on top of all `<style>...</style>` tags.

### Which browser are you using? (if relevant)

Google Chrome 115.0.5790.170

### How are you deploying your application? (if relevant)

next start
Repository: storybook
Issue: [Bug]: Title doc block doesn't work without a primary story
Labels: bug,needs triage

### Describe the bug

The `<Title />` doc block is throwing the following error when there is no primary story.  I would expect the title to render.

<img width="1047" alt="Screenshot 2023-08-08 at 9 50 10 PM" src="https://github.com/storybookjs/storybook/assets/10190567/75630301-300a-4694-b9c5-653e8d97170a">


### To Reproduce

Below is the code for my RatingComponent API page.  You could use any component and it will fail.  If you remove the `<Title />` doc block it will render the page as I would expect (without the title obviously).  The other doc blocks are working as expected as I have storybook configured with compodoc.  
```
// rating.api.stories.mdx
import { Meta, Title, Description, ArgsTable } from '@storybook/addon-docs';
import { RatingComponent } from '../rating.component';
import { moduleMetadata } from '@storybook/angular';

<Meta
  title="Components/Rating/API"
  decorators={[
    moduleMetadata({
      imports: [RatingComponent],
    }),
  ]}
/>

<Title />
<Description of={RatingComponent} />
<ArgsTable of={RatingComponent} />

```

### System

```shell
Environment Info:

  System:
    OS: macOS 13.4.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.16.0/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 115.0.5790.170
    Safari: 16.5.2
  npmPackages:
    @storybook/addon-docs: 7.2.1 => 7.2.1 
    @storybook/addon-essentials: 7.2.1 => 7.2.1 
    @storybook/angular: 7.2.1 => 7.2.1 
    @storybook/core-server: 7.2.1 => 7.2.1 
    @storybook/test-runner: 0.13.0 => 0.13.0
```


### Additional context

_No response_
Repository: axios
Issue: Can't transpile es6 class syntax to es5 syntax.
Labels: priority::low

### Describe the issue

In order to support the old version browsers, I am going to use webpack+babel-loader to transpile all es6+ syntax to es5 syntax. However, everything is running fine until I import Axios. All `classes` come back.

### Example Code

```js
import axios from "axios";

window.onload = () => {
  alert(1);
  // Tea.start()
  apiGetContent().then((data) => {
     console.log(data)
  });

  const dd = new Test();
  dd.say();
};

class Test {
  constructor() {}
  say() {
    console.log("test");
  }
}

function apiGetContent(): Promise<Data[]> {
  return axios.get("https://test.com").then((res) => {
    if (res.status === 200) {
      return res.data.map(
        (item: { title: string; pureText: string; draftName: string }) => {
          return {
            id: item.draftName,
            title: item.title,
            content: item.pureText,
          };
        }
      );
    } else {
      return [];
    }
  });
}
```


### Expected behavior

no class syntax

### Axios Version

1.4.0

### Adapter Version

_No response_

### Browser

_No response_

### Browser Version

_No response_

### Node.js Version

16.15.1

### OS

_No response_

### Additional Library Versions

_No response_

### Additional context/Screenshots

_No response_
Repository: kubernetes
Issue: NodeResourcesFit support multi strategy
Labels: sig/scheduling,kind/feature,needs-triage

### What would you like to be added?

There are different kinds of nodes in our clusters.
We want to use a binpack strategy for gpu nodes and use a spread strategy for cpu nodes.

Support to set different binpack or spread strategy for different nodes.

### Why is this needed?

If we set the a binpack strategy for nvidia.com/gpu in our cluster, nodeResourceFit will score 0 for all nodes and all pods without gpu requests. As a result, these pods maybe scheduled on one node.

You can see the resource consumption:
> k inspect resource 
Resource                          Requested          Limit               Allocatable  Free
 cpu                              37150m (79.4%)     55500m (118.6%)     46800m       9650m
 ├─ nodeA   15150m (97.1%)     27300m (175.0%)     15600m       450m
 ├─ nodeB   7 (44.9%)          11100m (71.2%)      15600m       8600m
 └─ nodeC  15 (96.2%)         17100m (109.6%)     15600m       600m
Repository: pytorch
Issue: untimeError: The following operation failed in the TorchScript interpreter. Traceback of TorchScript (most recent call last): RuntimeError: nvrtc: error: invalid value for --gpu-architecture (-arch)
Labels: needs reproduction,oncall: jit

### 🐛 Describe the bug

  pos[:2] += torch_rand_float(-1., 1., (2, 1),
                              device=self.device).squeeze(1)


untimeError: The following operation failed in the TorchScript interpreter. Traceback of TorchScript (most recent call last): RuntimeError: nvrtc: error: invalid value for --gpu-architecture (-arch)

### Versions

ubuntu:20.04:
NVIDIA GeForce RTX 4060 Ti
cuda :11.3
- torch==1.10.0+cu113 
- torchvision==0.11.1+cu113
- torchaudio==0.10.0+cu113

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: PowerToys
Issue: Fancy Zones > Snap point at the top
Labels: FancyZones-Layouts,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

Hi,
I think it's a good idea to be able to set the snapping point of your zone at the top of the zone.
This way you can easily switch a window from zones when you want vertically maximazed zones.

### Scenario when this would be used?

When you have 1 or more wide monitors, you often want to max out the vertical dimension of your windows next to each other.
When you want to move a window to another zone (to adjust its dimensions obviously) then
- 1: You (mostly) take your mouse at the title bar
- 2: Right click (if enabled ... )
- 3: Drag it to the center vertically
- 4: Move horizontally to pick your new zone

-----
If you could have your snapping points of your zones to be adjusted to the top, and want to move a window to another zone then
- 1: You (mostly) take your mouse at the title bar
- 2: Right click (if enabled ... )
- 3: Move horizontally to pick your new zone

-----
I guess then it would be necessary to be able to have multiple zones with different set snap-positions in one configuration.
Because you also still want to keep zones with a snapping point in the center (to align vertically on top of each other).
The big point here is that you wouldn't have to drag your mouse from the top to the middle of your screen.

-----
Maybe it would be even better to automatically add this functionality when a zone uses the full vertical height?

-----
Example view of vertically maxed out windows next to each other.

![fancy zones](https://github.com/microsoft/PowerToys/assets/132269491/1547f59d-ad05-445c-acca-ac82b82e84ad)


### Supporting information

_No response_
Repository: vscode
Issue: Provide a more visible menu for the important actions
Labels: feature-request,editor-contrib,menus

**Use Case:** The Java extension supports decompiling a class file when no source is available. However, some users may also want to manually configure a source jar for their class files. Currently the UI elements we can use in VS Code is the context menu or notification message box. But they are not discoverable or intuitive. The feature request is to provide a more visible editor menu for important actions. For example, IJ provides a better UI option for this feature, where it uses a floating inline bar to show some important actions for the user such as decompiling and attaching sources. If VS Code can offer a similar UI element, it would greatly improve the feature discovery and usability of the Java extension.

![image](https://github.com/microsoft/vscode/assets/14052197/8eb3055a-8fbd-4655-96cb-76b753cf59ab)
Repository: next.js
Issue: Scroll is not restored after navigating with back button after swipe to top
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Current https://nextjs.org version is 13.4.17-canary.2
```

### Which example does this report relate to?

https://nextjs.org

### What browser are you using? (if relevant)

IOS Safari 16.6

### Describe the Bug

When using the browser's provided back button following a quick upward swipe, the scroll position resets for the previous page.
Please note that this issue only occurs in iOS Safari and cannot be replicated in IOS Chrome.

### Expected Behavior

Scroll position should be restored.

### To Reproduce

1. Visit https://nextjs.org.
2. Scroll down to a sufficiently distant link.
3. Click on that link.
4. The navigation bar has disappeared. To return, swipe up quickly and then click the back navigation. (Usually, the combination of those actions performed quickly)
5. The scroll position is not restored.

Please look at the following video.

https://github.com/vercel/next.js/assets/32598874/9c245a29-d8c8-4aff-a434-dc021ec6d2c1

Update: 
Seems like a general bug for every website for both `manual` and `auto` scroll restoration only on IOS Safari.
Here is screen recording of reproduction on google.com website.


https://github.com/vercel/next.js/assets/32598874/f017e150-b7d1-4d36-a88c-2955e5bad265
Repository: ant-design
Issue: tree控件 支持框选
Labels: 💡 Feature Request,Inactive,🧶 Low Priority

### What problem does this feature solve?

当树控件数据量较多时，并且开启checkable状态下，想要选中大批量树节点时，点击选中就显得超级麻烦，框选能便捷用户操作

### What does the proposed API look like?

frameCheckable ： boolean 
只在checkable为true时候生效

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: stable-diffusion-webui
Issue: [Feature Request]: If issue cuda out of memory stayed with SDXL models you will lose to much users 
Labels: enhancement,sdxl

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

hi i'm big fan of sd webui but i'm now using comfy ui because "cuda out of memory" which is not apearing in comfyui so plz fix this issue or give one solution for this 

### Proposed workflow

1. Go to .... 
2. Press ....
3. ...


### Additional information

_No response_