sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Remove newline and use non “smart” characters from clipboard
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Paste as Plain Text is a much welcome feature addition. However, I see two related (hence both in the same issue) potential enhancements that could be individually enabled/disabled:

1. Convert curly apostrophes and quotation marks to straight ones
2. Remove carriage returns/line feeds from text

### Scenario when this would be used?

For suggestion (1), I often copy and paste text from rich formatted documents (Word, PDF, etc.) and I need to replace all fancy typographic curly quotes to straight ones just like if it was typed at the keyboard.

For suggestion (2), when pasting selected paragraphs from PDFs, it happens frequently that each line is ended with a CR/LF that needs to be manually removed after pasting the text.

For example, when both options are enabled, the following text

```
It’s too bad that curly quotes are
not converted to straight ones and
that CR/LF at the end of each line
are not automatically eliminated
from the pasted plain text.
```

would be pasted as follows:

```
It's too bad that curly quotes are not converted to straight ones and that CR/LF at the end of each line are not automatically eliminated from the pasted plain text.
```

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: SB@6.5.16 not rendering Angular 15 components in docs or canvas iframes
Labels: bug

### Describe the bug

Hi! After migrating my setup to use Angular 15.1.5. Storybook 6.5.16 and Webpack 5, I was finally able to get the full application to build 🎉🎉🎉

However, it seems the SB iframes are not rendering the Angular components on the docs or canvas pages correctly, and I'm seeing a JIT compilation error:

`Errors during JIT compilation of template for FieldComponent: Opening tag "label\n" not terminated. ("export default "[ERROR ->]<label\n  *ngIf=\"!!_labelChildren?.length\"\n  class=\"field-label typography-component-input-label\"): ng:///FieldComponent/template.html@0:16, Opening tag "ng-content" not terminated. ("abled ? 'field-label-disabled' : ''\n  ]\"\n  [attr.for]=\"_control.id\"\n  [id]=\"_labelId\"\n>\n  [ERROR ->]<ng-content select=\"halo-field-label\"></ng-content>\n  <span\n    class=\"field-label-required\"\n "): ng:///FieldComponent/template.html@0:366, Unexpected closing tag "ng-content". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags `

This repeats for quite a bit for every component using Angular's muilti slot content projection style.

Example of component:
 `<ng-content select="field-label"></ng-content>`. 

Example of implementation:

`<field-label>Label</field-label>`


The components mentioned in the stack trace were working before the migration and are working now in a separate ng 15 application consumption test.



### To Reproduce

-- migrate SB using the script from docs
-- migrate NG using the script and guide from docs
-- upgrade to Webpack 5.75.0
-- upgrade to Typescript 4.9.5

### System

```shell
Environment Info:

  System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
  Browsers:
    Chrome: 105.0.5195.125
    Edge: 110.0.1587.57
    Firefox: 109.0.1
    Safari: 16.2
  npmPackages:
    @storybook/addon-actions: ~6.5.16 => 6.5.16
    @storybook/addon-essentials: ~6.5.16 => 6.5.16
    @storybook/addon-links: ~6.5.16 => 6.5.16
    @storybook/addons: ~6.5.16 => 6.5.16
    @storybook/angular: ~6.5.16 => 6.5.16
    @storybook/builder-webpack5: ~6.5.16 => 6.5.16
    @storybook/manager-webpack5: ~6.5.16 => 6.5.16
    @storybook/theming: ~6.5.16 => 6.5.16
```


### Additional context

Thanks in advance for your time!
Repository: vscode
Issue: Clean up legacy remote indicator menu
Labels: debt,remote

Re: comment about removing the legacy remote indicator menu: 
https://github.com/microsoft/vscode/blob/9abc735ffd1e07fecb8011661640fa1a27ae376b/src/vs/workbench/contrib/remote/browser/remoteIndicator.ts#L58
Repository: godot
Issue: 30+ seconds starting godot, opening/running project on Intel Arc A750, Windows 11
Labels: platform:windows,discussion,topic:rendering,topic:thirdparty,needs testing

### Godot version

4.0 stable

### System information

Windows 11, ???, Intel Arc A750 (31.0.101.4146)

### Issue description

Freshly downloaded Godot 4.0.
When I start Godot 4.0 it takes 31 seconds. All I see is a grey window.
Opening a project and running a project takes just as long.
Doesn't improve when I restart my computer.
Had similar issues with earlier versions of Godot and my Intel Arc A750 graphics card.
Had no problems with my previous graphics card (RX 470 4GB).

### Steps to reproduce

Start Godot 4.0 || Open a project || Run a project

### Minimal reproduction project

nt
Repository: vscode
Issue: Quick open renders icons from file names
Labels: bug,quick-open

Type: <b>Bug</b>

1. Create a file called `$(zap).ts`
2. Trigger quick open and type `zap`

**bug**
The icon is rendered in quick open

![Screenshot 2023-03-02 at 9 53 21 AM](https://user-images.githubusercontent.com/12821956/222511415-8e10eabd-8a93-4c67-b202-c626aa57eada.png)

VS Code version: Code - Insiders 1.77.0-insider (Universal) (155cd6db223feb1f8c734ca70e108b9efec7b054, 2023-03-02T12:44:52.544Z)
OS version: Darwin x64 22.3.0
Modes:
Sandboxed: Yes

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|4, 4, 4|
|Memory (System)|32.00GB (0.01GB free)|
|Process Argv|--crash-reporter-id 48781ca2-1705-4f64-9bab-325055aab55d|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: godot
Issue: `emulate_touch_from_mouse` doesn't work on Android.
Labels: bug,platform:android,topic:porting,topic:input

### Godot version

4.0.stable.official (92bee43)

### System information

Windows 10

### Issue description

`input_devices/pointing/emulate_touch_from_mouse` doesn't work on Android.
But `input_devices/pointing/emulate_mouse_from_touch` works on Android (only first touch in multi touching).
Both work on Windows 10.

### Steps to reproduce

``` GDScript
func _input(event):
	print(event)
```

### Minimal reproduction project

[emulate touch issue reproduction project.zip](https://github.com/godotengine/godot/files/11019551/emulate.touch.issue.reproduction.project.zip)
Repository: go
Issue: go/parser: poor error recovery after missing function call argument
Labels: NeedsInvestigation,gopls/parsing

This program contains a syntax error in `Abs(,)` that causes the parser's recovery to generate a BadExpr for `math.Lde`.
```
func g() {
        math.Abs(,)

        //

        math.Lde()
}
```
This causes go/types not to recognize `math` as a reference to a package, and causes completions in gopls to misbehave.


![Screenshot 2023-03-02 at 1 06 40 PM](https://user-images.githubusercontent.com/5658175/222514213-a14e4d7c-6b62-4969-bf22-2a48592c9e9a.png)


I think the parser could do a better job of recovery. @griesemer gives reasons why this is difficult in https://github.com/golang/go/issues/24327#issuecomment-378414555:

> go/parser is likely falling behind the compiler due to the compiler's parser (package syntax) being actively improved whenever we run into unsatisfying error messages. It's fairly time-consuming to back-port those fixes because the parsers don't have the same structure, and small local changes sometimes have unexpected consequences with respect to error handling (hence those changes, even if small, are time-consuming to get right).
> 
> Ideally, in the long run we should migrate to package syntax. Failing that, one option might be to replace go/parser with the syntax package parser while keeping the same API. That might be not too hard since the syntax trees are reasonably close.

Related issue of gopls completion after a syntax error:
- https://github.com/golang/go/issues/24327
- https://github.com/golang/go/issues/39721
- https://github.com/golang/go/issues/36595
- https://github.com/golang/go/issues/45408
Repository: vscode
Issue: Explore using CSS highlighting API for HighlightedLabel
Labels: debt,perf

`HighlightedLabel` currently supports highlighting by creating custom dom nodes with the highlighted ranges:

![Screenshot 2023-03-02 at 10 09 11 AM](https://user-images.githubusercontent.com/12821956/222514789-50e4f738-2100-42ac-9e8f-8c5b6e209205.png)

This results in more dom nodes than needed and also means that whenever highlighting changes, we have to recreate the entire `HighlightedLabel`, resulting in extra DOM layout computations 

Instead we should explore using the [new CSS highlighting API](https://developer.mozilla.org/en-US/docs/Web/API/CSS/highlights) for this. This should let us update highlighting in the label and only trigger repaints
Repository: PowerToys
Issue: Mouse Jump enhancement - support for virtual desktops
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be cool if Mouse Jump could support virtual desktops. When activating Mouse Jump it would bring up small windows of not just the complete current desktop, but also (optionally through PowerToys settings) all virtual desktops.

Clicking on a spot on a different virtual desktop would switch to that virtual desktop and place the mouse cursor where you pointed.

### Scenario when this would be used?

Any time you are using virtual desktops.

### Supporting information

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: Img2Img API returns image with unexpected size when a mask is present in the request
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

When using a mask in a request, the resulting image has size different from the specified.
In detail, the image with size 1280x760  has been downscaled to 1024x512.
This problem occurs when using the API, everything works correctly through the form.

### Steps to reproduce the problem

Just add a mask to request.

### What should have happened?

It would be nice if the API will return image with specified size, like WebUI form do.

### Commit where the problem happens

0cc0ee1bcb4c24a8c9715f66cede06601bfc00c8

### What platforms do you use to access the UI ?

Windows

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
set COMMANDLINE_ARGS=
call webui.bat --api
```


### List of extensions

sd-webui-controlnet

### Console logs

```Shell
venv "D:\SD\new sd\stable-diffusion-webui\venv\Scripts\Python.exe"
Python 3.10.9 (tags/v3.10.9:1dd9be6, Dec  6 2022, 20:01:21) [MSC v.1934 64 bit (AMD64)]
Commit hash: 0cc0ee1bcb4c24a8c9715f66cede06601bfc00c8
Installing requirements for Web UI

Launching Web UI with arguments: --api
No module 'xformers'. Proceeding without it.
Loading weights [0aecbcfa2c] from D:\SD\new sd\stable-diffusion-webui\models\Stable-diffusion\dreamlike-diffusion-1.0.ckpt
Creating model from config: D:\SD\new sd\stable-diffusion-webui\configs\v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Applying cross attention optimization (Doggettx).
Textual inversion embeddings loaded(0):
Model loaded in 4.1s (load weights from disk: 0.8s, create model: 0.4s, apply weights to model: 0.5s, apply half(): 0.8s, move model to device: 0.7s, load textual inversion embeddings: 0.9s).
Running on local URL:  http://127.0.0.1:7860

To create a public link, set `share=True` in `launch()`.
100%|██████████████████████████████████████████████████████████████████████████████████| 46/46 [01:58<00:00,  2.57s/it]
100%|██████████████████████████████████████████████████████████████████████████████████| 46/46 [01:56<00:00,  2.54s/it]
Total progress: 92it [05:31,  2.62s/it]
```


### Additional information

Here is ths request
`{
	"init_images":["img"],
	"mask":"img",
	"width":1280,
	"height":760,
	"denoising_strength":0,75,
	"resize_mode":1,
	"mask_blur":1,
	"inpainting_mask_invert":0,
	"inpainting_fill":0,
	"inpaint_full_res":true,
	"inpaint_full_res_padding":0,
	"batch_size":1,
	"n_iter":1,
	"steps":60,
	"cfg_scale":10,
	"prompt":"text",
	"negative_prompt":"text",
	"style":[],
	"seed":7777,
	"subseed":-1,
	"subseed_strength":0,
	"seed_resize_from_h":-1,
	"seed_resize_from_w":-1,
	"restore_faces":false,
	"sampler_index":"Euler a",
	"batch_count":1
}`
Repository: PowerToys
Issue: FancyZones does not notice when taskbar auto-hide is disabled
Labels: Issue-Bug,Product-FancyZones

### Microsoft PowerToys version

0.68.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. Set the taskbar to auto-hide.
2. Reboot so that as FancyZones starts, it records that the taskbar is hidden, meaning the available desktop space includes the taskbar zone.
3. Notice that when shift-dragging windows into a zone bordering the bottom of the screen, they snap all the way to the bottom including the taskbar zone.
4. Now disable taskbar auto-hide, so the taskbar is once again permanently occupying space on the bottom.
5. Shift drag a window into a zone. 

### ✔️ Expected Behavior

The shift-dragged window should fill only the currently available space, which does not include the taskbar.

### ❌ Actual Behavior

The shift-dragged window snaps to the originally available space, including the portion now occupied by the taskbar, so that the window bottom including the resize corners are now out of reach behind the taskbar.

This issue can be resolved by restarting windows, which apparently causes FancyZones to realize the taskbar is no longer auto-hiding and needs to be accounted for.

### Other Software

_No response_
Repository: pytorch
Issue: [PTD] dist.barrier() unreliable when using collectives from multiple threads.
Labels: oncall: distributed,module: c10d

### 🐛 Describe the bug

This is a hang that happens with https://github.com/pytorch/pytorch/pull/95819 but it's a reliability issue with any code that emits collectives from multiple threads including calls to dist.barrier.

This is likely to be common with PTD tests that uses CUDA, trigger backward in some model and do collectives from them (like when doing DDP or FSDP).

The work around is to replace the barrier call with `dist.all_reduce(torch.zeros((1,), device="cuda" if torch.cuda.is_available() else "cpu"))`.


### Versions

master

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: flutter
Issue: [packages] Consider building examples with `--fatal-warnings`
Labels: team,p: tooling,package,team-ecosystem,P3,triaged-ecosystem

See discussion in https://github.com/flutter/plugins/pull/7062 for background.

We have solutions in place now for code warnings as errors in all platforms, but `--fatal-warnings` would cover cases that we don't currently cover. However, it's also not clear how useful it is; it may catch things that we can't control, with no way of suppressing them.

We should try a full run across the whole repo on all platforms, and see what it turns up, and then evaluate whether it's something that would make sense in addition to the settings we already have.
Repository: next.js
Issue: Custom page extensions (e.g. page.page.tsx) do not import CSS in AppDir
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Introduced in 13.2.2-canary.4
Specifically this change: https://github.com/vercel/next.js/pull/46571 "Fix CSS imports not included in entries with a custom extension"
This change should account for custom page extensions.

Still present in 13.2.4-canary.0
```


### 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://stackblitz.com/edit/vercel-next-js-bxppz3

### To Reproduce

In `next.config.js`, add a custom extension that looks like this:

`pageExtensions: ['customextension.tsx', 'customextension.ts'],`
This works with any extension of this format, but the version recommended in the stable NextJS docs recommend `page.tsx`: https://nextjs.org/docs/api-reference/next.config.js/custom-page-extensions#including-non-page-files-in-the-pages-directory

Create a page in `/app`. Import any `.css` file. See how it does not get imported into the page.

In the reproduction I have given, `/app/page.tsx` works when there is no custom extension, and `/app/page.customextension.tsx` does not import the CSS.

### Describe the Bug

When not using custom page extensions, pages correctly import CSS:
<img width="132" alt="image" src="https://user-images.githubusercontent.com/840549/222532638-abff8159-e5ef-4994-8f4a-a3a5799fb930.png">

When using a custom page extension, the CSS appears to be dropped completely:
<img width="190" alt="image" src="https://user-images.githubusercontent.com/840549/222532696-b65127fd-478c-4e46-9654-4e326e01d0a1.png">

I have a legacy NextJS application that relies on a custom extension of `page.tsx` to allow me to colocate components and other files in the `/pages` directory, as [recommended in the docs](https://nextjs.org/docs/api-reference/next.config.js/custom-page-extensions#including-non-page-files-in-the-pages-directory).

Due to the size of the project, it is not feasible to migrate to `/app` or move all the components out of `/pages` quickly (though it is a long-term goal)

(Side note, the NextJS Typescript plugin also does not understanding custom page extensions - I intend to open a separate issue for that.)

### Expected Behavior

CSS should import on files with custom page extensions, like `mypage.page.tsx`.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: vscode
Issue: Allow to fork utility process from a worker thread
Labels: feature-request,upstream,perf,electron,sandbox

An idea @Tyriar and Electron team discussed is whether we could fork Electron utility processes from a node.js worker to stop the main process from being stopped synchronously until the fork has completed.

If we had a way to fork from a worker thread we can:
* potentially avoid blocking file I/O and user input during that time
* consider reducing the [artificial delay](https://github.com/microsoft/vscode/blob/b0b73ee333534add58d2fe48dc48b46b3533a221/src/vs/workbench/services/sharedProcess/electron-sandbox/sharedProcessService.ts#L35-L42) we now put onto process spawning
Repository: godot
Issue: Some node parameters aren't updating fully at runtime (TileMap.modulate/self_modulate and CollisionShape2D.disabled at least)
Labels: bug,topic:core,topic:physics,needs testing

### Godot version

4.0 Stable 

### System information

MacOS 13.2 M1Max

### Issue description

When I call CollisionShape2D.disabled from code at runtime, the node's property will update (verified via the remote scene, print statement, and visuals) however, the collision doesn't go away. It only becomes invisible.

https://user-images.githubusercontent.com/7057201/222544175-2792f732-6c7e-466d-a700-7b1518f4ccfb.mp4

```gdscript
func update_collision_shape_enabled(is_enabled):
	for child in get_children():
		if child is CollisionShape2D:
			child.disabled = !is_enabled
```

### Steps to reproduce

This issue is very hard to nail down. I've only been able to produce it in my own project. Any attempts to do so in a separate minimal project have been fruitless. If someone would like to look at my project I'm happy to screenshare or send more code snippets or something, just let me know. 

### Minimal reproduction project

Unfortunately ive been unable to make one.
Repository: flutter
Issue: Create migrator for updating compileSdkVersion for developer owned projects 
Labels: c: new feature,platform-android,P3,team-android,triaged-android

Consider adding a migrator for this so developers on older Flutter created projects don't need to change it manually:
https://github.com/flutter/flutter/tree/master/packages/flutter_tools/lib/src/ios/migrations
https://github.com/flutter/flutter/tree/master/packages/flutter_tools/lib/src/migrations

See https://github.com/flutter/flutter/issues/121425#issuecomment-1444639799 for inspiration. 
See https://github.com/flutter/packages/pull/3271 as an example of migrating the entire packages repo.
Repository: ant-design
Issue: Theme: controlPaddingHorizontal issues
Labels: Inactive,improvement

### Link to reproduce

https://codesandbox.io/s/antd-reproduction-template-forked-f5d5ez?file=/index.js

### Steps to reproduce

1. add a few controls to the Form, e.g.: Input, InputNumber, AutoComplete, Select, DatePicker, Input.Textarea with `size="large"` and some `placeholder` or input values; 
2. set `controlPaddingHorizontal: 50` into the theme token (or component token). 

### What is expected?

I expect all the inputs would apply horizontal padding into the control view.


### What is actually happening?

Only Input and Input.Textarea will apply horizontal padding.

| Environment | Info |
| --- | --- |
| antd | 5.2.3 |
| React | react@^18.2.0 |
| System | macOS Ventura 13.2.1 |
| Browser | Chrome Version 110.0.5481.100  |

---
I would also expect to have `controlPaddingHorizontalLG` available, so I can set padding depending on form size.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->