sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Display in English (US) layout of keyboard shortcuts in both Help and Settings whatever default keyboard input is
Labels: Issue-Bug,Product-Settings,Area-Localization,Needs-Triage

### Description of the new feature / enhancement

The experience user level of PowerToys is relatively high, they usually understand shortcuts written in English keyboard layout.

Therefore, I suggest using only English (US) keyboard shortcuts in both Help and Settings, even if different default language is used.

### Scenario when this would be used?

- I open PowerToys Help app, I would like to see shortcuts written in English. Latin characters can easily be confused with Cyrillic ones.

![image](https://user-images.githubusercontent.com/12271104/222390879-cebe0fbd-e7af-49ba-a77d-9200d8c8650e.png)


### Supporting information

Happens on:
- PowerToys 0.56+, maybe the older versions, too
- Windows 11 latest stable
Repository: flutter
Issue: [WEB] [Camera] Incorrect recorded video duration issue in Chrome browser
Labels: platform-web,p: camera,package,has reproducible steps,P2,browser: chrome-desktop,browser: chrome-android,found in release: 3.7,found in release: 3.8,team-web,triaged-web

Description: When recording a video using the camera in a Flutter web application, the duration of the recorded video sometimes shows a negative value in the Google Chrome browser. However, the same code works perfectly fine in Mozilla Firefox.

<details>
<summary>Code sample</summary>

```dart

Future<void> startVideoRecording() async {
  final CameraController? cameraController = controller;

  if (cameraController == null || !cameraController.value.isInitialized) {
    showInSnackBar('Error: select a camera first.');
    return;
  }

  if (cameraController.value.isRecordingVideo) {
    // A recording is already started, do nothing.
    return;
  }

  try {
    await cameraController.startVideoRecording();
  } on CameraException catch (e) {
    _showCameraException(e);
    return;
  }
}

void onStopButtonPressed() async {
  XFile? file = await stopVideoRecording();
  if (mounted) {
    setState(() {});
  }

  if (file != null) {
    showInSnackBar('Video recorded');
    videoFile = file;
    await _startVideoPlayer();
  }
}

Future<XFile?> stopVideoRecording() async {
  final CameraController? cameraController = controller;

  if (cameraController == null || !cameraController.value.isRecordingVideo) {
    return null;
  }

  try {
    return cameraController.stopVideoRecording();
  } on CameraException catch (e) {
    _showCameraException(e);
    return null;
  }
}

Widget _buildTimer(controller) {
  Duration position = controller.value.isInitialized ? controller.value.position : Duration.zero;
  Duration duration = controller.value.duration ?? Duration.zero;

  String positionText = position.toString().split('.').first;
  String durationText = duration.toString().split('.').first;

  return Positioned(
    right: 16.0,
    bottom: 24.0,
    child: Text(
      '$positionText / $durationText',
      style: const TextStyle(
        color: Colors.white,
        fontSize: 16.0,
      ),
    ),
  );
}


```

</details>


Expected output: The duration of the recorded video should always show a positive value in all browsers.

Output received: The duration of the recorded video sometimes shows a negative value in the Google Chrome browser.

Steps to reproduce:

Open the above code in a Flutter web application.
Record a video using the camera.
Check the duration of the recorded video.

Additionally, I have attached a screenshot that displays the negative duration issue on Google Chrome while the same code is giving the expected positive value when running on Mozilla Firefox.

![Screenshot 2023-03-02 at 4 31 04 PM](https://user-images.githubusercontent.com/63152979/222410245-b384a735-6b94-4de6-a99f-2f15ed015f48.png)

![Screenshot 2023-03-02 at 4 29 53 PM](https://user-images.githubusercontent.com/63152979/222409997-45c763bd-198e-4e28-ac8b-aa4473ad4a7f.png)
Repository: vscode
Issue: setBreakpoints is called with sourceModified:false when source is dirty and new breakpoint is added
Labels: bug,debug

It's not clear from the DAP spec exactly what the intended behaviour is here, so I've filed https://github.com/microsoft/debug-adapter-protocol/issues/376. However, this part definitely seems like a bug.

I added a breakpoint to a file, modified the file, and then added another. At no point did I save the file.

![Mar-02-2023 11-08-38](https://user-images.githubusercontent.com/1078012/222412148-1f006a92-2abd-4a0b-a277-553102a0ccb0.gif)

In the DAP log, I see that VS Code called `setBreakpoints` after I added the second breakpoint but with `sourceModified: false`. This seems to be incorrect.. The debug adapter now thinks these breakpoints are for a saved file, but they are not.

```
[11:08:17] [DAP] [Info] ==> {"command":"setBreakpoints","arguments":{"source":{"name":"package:flutter_counter/main.dart","path":"/Users/danny/Desktop/dart_samples/flutter_counter/lib/main.dart","sourceReference":0},"lines":[14],"breakpoints":[{"line":14}],"sourceModified":false},"type":"request","seq":8}
[11:08:21] [DAP] [Info] ==> {"command":"setBreakpoints","arguments":{"source":{"name":"package:flutter_counter/main.dart","path":"/Users/danny/Desktop/dart_samples/flutter_counter/lib/main.dart","sourceReference":0},"lines":[14,15],"breakpoints":[{"line":14},{"line":15}],"sourceModified":false},"type":"request","seq":9}
```
Repository: godot
Issue: Normals do not work properly with Shape Keys
Labels: bug,topic:rendering,topic:3d

### Godot version

3.5 and 3.5.1

### System information

Windows 11, GLES3, NVIDIA GeForce RTX 3070 (472.12)

### Issue description

Normals do not appear to work properly with Shape Keys, it breaks apart at the seams and warps in an unsightly way, I have tried this on 3.5 and 3.5.1 and I get the same problem, I do not get this strange warping in Blender, or even Godot 4.0

Here is a video/gif showing the problem https://i.imgur.com/TlyPqpi.mp4

I've been working on a very large game and the ability to have a custom character is a very important part of it. I have tried different ways of importing and nothing seems to make any difference. I'm not looking to swap to 4

In the below zip, all you need to do is go to shape keys and slide the 0 over to 1 and you should see all the many problems appear. The model is slightly different from the above GIF, I changed the seams on the back, but there are still many problems
Thank you for your time!

### Steps to reproduce

I have a human model with baked in normals, and I have shape keys to change the gender of the character, I export as a GLTF, I import and apply the correct materials, and when I change the shape keys, that's when the problem starts.

### Minimal reproduction project

[Godot Shape Keys Problem.zip](https://github.com/godotengine/godot/files/10870815/Godot.Shape.Keys.Problem.zip)
Repository: PowerToys
Issue: FancyZones not working with multiple displays in combination with portable apps
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.67.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

Preinfo:
- The FancyZone feature is working on the Main Display the described Bug appears only at the additional displays in my case the right one or the left one from the main display
- According to my observation the error only occurs with portable programs (in my Case with (putty/kitty=0.76.1.3 or keepass portable=2.53.1)
- Already tried as Administrator


Precondition:
- Use minimum 2 Displays

1.  Create FancyZones with diffrent sizes
2.  Download the Portable Version of Keepass oder Putty or Kitty
3.  Open the Portable Applications
4.  Try to Snap Keepass Putty oder Kitty to a Fancy Zone


Screencast:
https://user-images.githubusercontent.com/22096341/222428178-f0f7bc64-e9c7-4bb0-b056-cb514b0a03a8.mp4




### ✔️ Expected Behavior

Window is adjusting and snapping to the selected Fancy Zone area/zone

### ❌ Actual Behavior

Window is sizing to the choosen fancy zone but shifts to the left

### Other Software

kitty 0.76.1.3
keepass portable 2.53.1
Repository: PowerToys
Issue: Updater turns off PowerToys options
Labels: Issue-Bug,Area-Setup/Install,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.68.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Installer

### Steps to reproduce

I have the Quick Accent and PowerToys Run always on, but when I update the application they are always switched off and I have to go in the settings and turn them on again.

### ✔️ Expected Behavior

The program should remember the set settings and which options were activated when updating so I wouldn't have to reactivate the options everytime the application updates.

### ❌ Actual Behavior

PowerToys Run is off and Quick Accent is off whenever I update the application.

### Other Software

_No response_
Repository: PowerToys
Issue: Reset mouse cursor position
Labels: Idea-Enhancement,Idea-New PowerToy,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

Pressing a certain button combinaton puts the mouse cursor in the middle of the current primary screen.

### Scenario when this would be used?

Working with many monitors, it's possible to lose track of the cursor, and in my opinion this feature would work better than the "find my mouse" feature that currently exists.

### Supporting information

_No response_
Repository: next.js
Issue: App Directory fails if an index file is present in route groups
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: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.12.0
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.3
      eslint-config-next: 13.2.1
      react: 18.3.0-next-6ff1733e6-20230225
      react-dom: 18.3.0-next-6ff1733e6-20230225
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://github.com/imcatwhocode/next-appdir-index-bug

### To Reproduce

1. Run the reproduction as usual.
2. Open the app in a browser.
3. Expect an infinite page loading / waiting for the response.

### Describe the Bug

If an index file is present within a routes group, Next fails to render this segment resulting in an infinite page load. It happens without any visible Next's console output or unhandled exceptions.

Having index files in segments (static or dynamic) doesn't lead to the same behavior. It seems that only routes groups are affected.

### Expected Behavior

If this is a bug – the app directory should allow index files in route groups without failing.

If not, I expect a remark in the documentation regarding this peculiarity.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

------

_Thank you for your work ❤️‍🔥_
Repository: vscode
Issue: v1.76 ZoneWidget right-click context is affected by sash and scrollbar
Labels: bug,menus

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->

- VS Code Version: 1.76.0
- OS Version: windows

![企业微信截图_16777650584363](https://user-images.githubusercontent.com/48614781/222449152-886f905e-24eb-45f3-b93f-7f92feb5f919.png)
![企业微信截图_16777651515813](https://user-images.githubusercontent.com/48614781/222449160-94c29b5c-f054-4820-aa8f-84344b799a1a.png)
Repository: vscode
Issue: Allowing the user to sort part of a JSONC document
Labels: feature-request,json,json-sorting

It would be nice to add the possibility to sort part (a selection) of JSONC documents, not necessarily the whole document
Repository: godot
Issue: Cannot change type of children nodes
Labels: bug,topic:editor,needs testing

### Godot version

4.0 stable

### System information

win 11

### Issue description

when select more than one node in scene tree right click and hit change type only the first node changes.

### Steps to reproduce

make two nodes
select
right click
change type
observe

### Minimal reproduction project

N/A
Repository: three.js
Issue: Cannot override methods when extending WebGLRenderer
Labels: Enhancement

### Description



In my case, I have a `CustomRenderer` class that extends `WebGLRenderer`. I want to dispose of other things in the `dispose()` call, so I created an override method that disposes of my resources and also calls `super.dispose()`.

However, in WebGLRenderer, the method doesn't ever get called, and instead the `WebGLRenderer.dispose()` is called directly.

```js
class CustomRenderer extends WebGLRenderer {
  dispose() {
    super.dispose()
    // the code here is never run..
  }
}

const renderer = new CustomRenderer()
renderer.dispose()
```

This is because the `WebGLRenderer.dispose()`, is not a class method per se.


### Reproduction steps

1. Create a class that extends `WebGLRenderer`
2. Create a method that overrides a `WebGLRenderer` method
3. Instance the class and call the method


### Code

```js
import { WebGLRenderer } from 'three';

class CustomRenderer extends WebGLRenderer {
  dispose() {
    super.dispose()
    
    // custom code goes here...
    console.log('1. I should be logged to the console')
  }
}

const renderer = new CustomRenderer()
renderer.dispose()

console.log('2. The log n. 1 should be present above this ^')
```


### Live example

* [jsfiddle](https://jsfiddle.net/8o9hqef7/7/)


### Screenshots

_No response_

### Version

r150

### Device

_No response_

### Browser

_No response_

### OS

_No response_
Repository: next.js
Issue: Type definitions of exports are invalid
Labels: bug,TypeScript

### 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: #202302091138~1675975749~22.04~f771a7f SMP PREEMPT_DYNAMIC Thu F
    Binaries:
      Node: 19.7.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 7.27.0
    Relevant packages:
      next: 13.2.4-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


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

TypeScript

### Link to the code that reproduces this issue

N/A (not a runtime issue)

### To Reproduce

Create a project with the following files:

```jsonc
// package.json
{
  "dependencies": {
    "@types/node": "^18.0.0",
    "@types/react": "18.0.0",
    "@types/react-dom": "^18.0.0",
    "next": "canary",
    "typescript": "^4.0.0"
  }
}
```

```jsonc
// tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "jsx": "react-jsx",
    "noEmit": true
  }
}
```

```ts
// index.ts
import App from 'next/app'

const app = <App />
```

Run `npm install`, then typecheck using `npx tsc`.

### Describe the Bug

This will show various errors. They are all related to Next.js using `esModuleInterop. Because of this, Next.js packages are affected by https://github.com/microsoft/TypeScript/issues/52779.

Typical Next.js users don’t see this bug, because Next.js enforces people to use `esModuleInterop`, which hides the issue, but shouldn’t be necessary.

### Expected Behavior

Next.js packages have proper type exports. This can be ensured by building without the `esModuleInterop` option.

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

_No response_

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

_No response_
Repository: PowerToys
Issue: Improve the fancyzones padding slider
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

It would be useful if you could write in the amount of padding in pixels instead of using the slider, in cases where you want to have a small padding amount. It makes no sense in my opinion for values between -10 and 10 pixels to be compressed to such a small area on the slider as I would imagine the padding would be quite a small amount in most cases. In any case being able to write in an exact amount of padding would make it easier to get the exact amount of padding you want.

### Scenario when this would be used?

It seems impossible to set the padding accurately if you want an exact amount of pixels, especially for values between 10 and -10. 

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: annot access 'kt' before initialization
Labels: bug,web-components,windows

### Describe the bug

Migrated to v7 and sometimes get errors when expanding a new section in the left pane :
![image](https://user-images.githubusercontent.com/58298382/222473230-9dbafd30-628b-413c-bf44-37ebd6818d73.png)
hitting F5 to reload story and everything is fine. Expand a new section in the left pane, sometime ok and sometime same error...

This only occur production mode, using storybook build. Dev mode - no problem.


### To Reproduce

```
$ storybook build
@storybook/cli v7.0.0-beta.59

info => Cleaning outputDir: \storybook-static
info => Loading presets
info => Building manager..
info => Manager built (393 ms)
info => Compiling preview..
info => Copying static files: C:\Users\MattiasJ\git\xxx-ui-components\node_modules\storybook\node_modules\@storybook\manager\static at C:\Users\MattiasJ\git\xxx-ui-components\storybook-static\sb-common-assets
info => Using implicit CSS loaders
info => Using default Webpack5 setup
info => Copying static files: C:\Users\MattiasJ\git\xxx-ui-components\.storybook\public at C:\Users\MattiasJ\git\xxx-ui-components\storybook-static\
info => Preview built (14 s)
info => Output directory: C:\Users\MattiasJ\git\xxx-ui-components\storybook-static
```

Start local webserver and navigate to localhost. 
Navigate sections in left pane to expand list of stories. Seems like first story in the list (that gets auto selected on expand) is not loaded!?

### System

```shell
Environment Info:

  System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz
  Binaries:
    Node: 18.14.1 - ~\.nvm\versions\node\v18.14.1\bin\node.EXE
    Yarn: 1.22.19 - ~\git\node_modules\.bin\yarn.CMD
    npm: 9.3.1 - ~\.nvm\versions\node\v18.14.1\bin\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (110.0.1587.56)
  npmPackages:
    @storybook/addon-actions: 7.0.0-beta.55 => 7.0.0-beta.55
    @storybook/addon-controls: 7.0.0-beta.55 => 7.0.0-beta.55
    @storybook/addons: 7.0.0-beta.55 => 7.0.0-beta.55
    @storybook/cli: 7.0.0-beta.55 => 7.0.0-beta.55
    @storybook/core: 6.5.16 => 6.5.16
    @storybook/storybook-deployer: ^2.8.16 => 2.8.16
    @storybook/theming: 7.0.0-beta.55 => 7.0.0-beta.55
    @storybook/web-components: 7.0.0-beta.55 => 7.0.0-beta.55
    @storybook/web-components-webpack5: ^7.0.0-beta.55 => 7.0.0-beta.59
```


### Additional context

```
module.exports = {
    staticDirs: ['./public'],
    stories: ['../stories/start.stories.@(js|jsx|ts|tsx)', '../stories/*/**/*.stories.@(js|jsx|ts|tsx)'],
    addons: [
        '@storybook/addon-controls',
        {
            name: 'storybook-addon-turbo-build',
            options: {
                // Please refer below tables for available options
                optimizationLevel: 3,
            },
        },
    ],
    core: {
        builder: 'webpack5',
        disableTelemetry: true,
    },
    framework: {
        name: '@storybook/web-components-webpack5',
        options: {},
    },
};
```
Repository: neovim
Issue: :messages query API, kill "Press ENTER" with fire
Labels: enhancement,api,ui,messages

## Problem

"Press ENTER" prompt is obnoxious. Most messages do not require explicit user confirmation. No, not even error messages.

The prevalence of "Press ENTER" is mostly an accident because of vim's reliance on stale tty state to show a message.

Related:

- https://github.com/neovim/neovim/issues/1029
- https://github.com/neovim/neovim/issues/10879


## Expected behavior



`:messages` should be querable via an API.
All messages emitted by Nvim should have metadata allowing Nvim (and plugins etc) to better decide:

1. which messages genuinely need active user confirmation
2. which messages can be shown passively (in the cmdline/message area)
3. which messages need a pager
4. which messages should be shown for a minimum of X seconds, fading away after some time

### Message metadata

- result (needs pager -- or actual buffer/floating window)
- error (needs message, and be sticky; user cannot silence)
    - most errors don't need confirm. they can be "sticky" by showing them in the cmdline/message area (which may get overwritten by another message, then show `+3 errors` in 'showcmd')
- confirm (invokes "Press ENTER" or something like it)
- info (needs message, but user can decide how it happens)
- progress (be sticky and replaceable)

### Eliminate "Press ENTER" (for 99% of cases)

With the above, Nvim can do smart things like , instead of showing "Press ENTER", show `+3 messages` in the 'showcmd' area (e.g.) and the user can check them if they want (via a mapping like `g<` or `g>`).

"Press ENTER" should be very rare except for actually dangerous situations.
"Editing a readonly file" is not a dangerous situation.
Repository: PowerToys
Issue: Paste As Plain Text - retain original clipboard content
Labels: Idea-Enhancement,Product-Advanced Paste

### Description of the new feature / enhancement

Currently, "the formatted text in the clipboard is replaced with the unformatted text." This feature adds a *Paste As Plain Text* Settings option for the clipboard to contain the original formatted content following the operation.

This feature would allow me to use Ctrl +V to paste formatted and Ctrl + Shift + V to paste as plain text in any order as many times as needed in any application.

### Scenario when this would be used?

When producing technical documentation, I need to have both formatted and unformatted forms of the same content available for pasting without a predictable sequence in various applications.

### Supporting information

I acknowledge the technical challenges to implement this, as discussed in #1684. Based on the collective knowledge shared there, it seems that it is technically infeasible to avoid modifying the clipboard content prior to the system paste operation. There is apparently no callback from the system paste operation, so timing clipboard content changes to replace its content after the operation may also be problematic. The contributors to that discussion mentioned other tools and alternate implementation methods that have their own limitations, but which hint at the possibility of better solutions.

I also realize that the best solution may be outside the scope of this product. I believe that the system paste operation would benefit greatly from some improvements along these lines. The In the meantime, PowerToys may be able to demonstrate the demand and need for such improvements.

I should also note that the Windows Clipboard History feature retains formatted content, but it requires mouse actions to switch between formatted and plain text content, which is an efficiency killer in my usage context. It's actually easier to go back and copy the original formatted content again.

I hope the PM's and the community at large consider this to be challenge worthy of a better solution that allows for a more flexible user experience. I can imagine building additional future features on such a solution that allow for more customized and accelerated actions that leverage the familiar paste functionality.