sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: Cannot use Arrows Up and Down in `textarea` inside `AutoComplete`
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/templating-in-antd-fsywpq?file=/demo.js)

### Steps to reproduce

1. Type some text with a couple of line breaks in the `textarea`.
2. Try to navigate the `textarea` with the up and down arrows.
2. Type two slashes to trigger the autocomplete dropdown.
3. Use the up and down arrow keys then select an option from the dropdown.
4. Once dropdown is closed, try to navigate the `textarea` with the arrow up and down keys.

### What is expected?

Navigating the `textarea` with the up and down arrows when the autocomplete dropdown is closed.

### What is actually happening?

The `textarea` cannot be navigated with the up and down arrows even when the autocomplete dropdown is closed.

| Environment | Info |
| --- | --- |
| antd | 4.19.5 |
| React | 17.0.2 |
| System | Windows 10 Version 21H2 (OS Build 19044, 1706) |
| Browser | Version 103.0.5060.66 (Official Build) (64-bit) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: storybook
Issue: YARN PnP - Storybook/angular - Error EROFS: read-only filesystem, open '/node_modules/.ngcc_lock_file'
Labels: bug,needs triage

**Describe the bug**
When using Yarn PnP, `start-storybook` or `build-storybook` won't work. Here's the error:  
```
return Object.assign(new Error(`${code}: ${message}`), {code});
                       ^

Error: EROFS: read-only filesystem, open '/node_modules/.ngcc_lock_file'
    at makeError$1 (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:28401:24)
    at EROFS (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:28428:10)
    at ZipFS.prepareWriteFile (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:30213:13)
    at ZipFS.writeFileSync (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:30197:53)
    at /Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:31244:20
    at /Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:31442:60
    at ZipOpenFS.getZipSync (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:31571:14)
    at ZipOpenFS.makeCallSync (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:31442:17)
    at ZipOpenFS.writeFileSync (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:31241:17)
    at VirtualFS.writeFileSync (/Users/tfassolis/Documents/Git/pnptest/.pnp.cjs:30598:24) {
  code: 'EROFS'
}
```

**To Reproduce**
Here is a reproduction repo : https://github.com/ld210/yarnpnp-storybook-angular-repro
Do a `yarn install`, and then try `yarn run storybook` or `yarn ng run pnptest:storybook`

**System**
Environment Info:

  System:
    OS: macOS 12.4
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 16.13.1 - /private/var/folders/pp/hlwx4ttn1gn30q105lb_b800tt2glm/T/xfs-6c9ce97e/node
    Yarn: 3.2.1 - /private/var/folders/pp/hlwx4ttn1gn30q105lb_b800tt2glm/T/xfs-6c9ce97e/yarn
    npm: 8.1.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 103.0.5060.53
    Firefox: 101.0
    Safari: 15.5

**Couple things worth noting**
- there is a node_modules folder in the reproduction repo, that contains a fake cache folder(.pnp). This node_modules folder is only here to keep the Angular CLI happy, until this Pull-Request is published in a future Angular release : https://github.com/angular/angular-cli/pull/23487
- The fake cache folder (node_modules/.pnp) is there only to prevent `yarn install` command to delete node_modules folder
- Everything Angular relate (ng serve, ng build, ng test, ng lint) works fine.
Repository: flutter
Issue: [Proposal] check if widget is `mounted` before calling `element!.markNeedsBuild();` internally so as to prevent errors like `setState` called on a widget no longer in a widget tree
Labels: framework,c: proposal,P3,team-framework,triaged-framework

On multiple pages in the app the data is loaded asynchronously when a page is pushed, and after loading the page is rebuild by calling `setState`. But in some cases the page can be closed before the data has been loaded, this results in the setState being called on a widget which is no longer in the tree. The solution to this problem is to check for the `mounted` property of a widget before calling setState. Instead of checking mounted every time before calling setState,  why doesn't the setState function check for mounted property internally and just return if it is not true?
Repository: neovim
Issue: cursor shape changes after formatting HTML text with `gq`
Labels: bug-regression

### Neovim version (nvim -v)

NVIM v0.7.2

### Vim (not Nvim) behaves the same?

NO, VIM - Vi IMproved 9.0

### Operating system/version

Arch Linux

### Terminal name/version

foot version: 1.12.1, alacritty 0.10.1

### $TERM environment variable

tmux-256color when using foot, xterm-256color when using alacritty

### Installation

[Arch Linux Official Repositories](https://archlinux.org/packages/community/x86_64/neovim/)

### How to reproduce the issue

1. Open `nvim --clean sample.html` and select the entire text mentioned below and wrap it/format it using `gq`.

```
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Pellentesque habitant morbi tristique senectus. Volutpat blandit aliquam etiam erat velit scelerisque in
dictum. Lorem ipsum dolor sit amet consectetur adipiscing. Mattis nunc sed blandit <code>volutpat sed</code> cras.
Ultrices dui sapien eget mi proin sed libero enim. Consectetur adipiscing elit ut aliquam purus sit. Id faucibus nisl
tincidunt eget nullam non nisi est sit. Scelerisque purus <a href="/">semper eget</a> duis at tellus
at urna. Enim sit amet venenatis urna cursus eget nunc scelerisque. Eu non diam phasellus vestibulum lorem sed. Enim
sit amet venenatis urna cursus eget. <a href="/"><code>Scelerisque</code></a> varius morbi enim nunc
faucibus a pellentesque sit amet. Faucibus purus in massa tempor nec feugiat nisl pretium fusce. Enim tortor at auctor
urna nunc id. Blandit massa enim nec dui nunc mattis. Arcu non odio euismod lacinia at quis risus. Donec adipiscing
<mark>tristique risus</mark> nec feugiat in fermentum posuere. Magna eget est lorem ipsum dolor sit. Amet nisl suscipit
adipiscing bibendum est ultricies integer quis.<sup><a href="https://sample.com">note 1</a></sup></p>
```

2. The cursor shape will change from block to vertical.


https://user-images.githubusercontent.com/79408161/177176429-4fe3bd8e-9b41-4b70-9f6c-7ba5c36db2b5.mp4



### Expected behavior

The cursor shape shouldn't change from block to vertical. This is how `vim` behaves out of the box with `-u DEFAULTS` and `--clean` as well.


https://user-images.githubusercontent.com/79408161/177176566-5de95b4f-3692-4532-aa59-e1ad7c160ad9.mp4



### Actual behavior

The shape of the cursor changes from block to vertical bar.

I tried changing `guicursor` from the nvim default of `guicursor=n-v-c-sm:block,i-ci-ve:ver25,r-cr-o:hor20` to the vim default of `guicursor=n-v-c:block,o:hor50,i-ci:hor15,r-cr:hor30,sm:block` but that didn't help.
Repository: godot
Issue: Improve error message when WebP fails to load in exported project due to the module being disabled
Labels: enhancement,topic:core,topic:export

### Godot version

3.4.4-stable

### System information

Windows 10 GLES3

### Issue description

When importing png files as Texture, I get ERR_FILE_CORRUPT (texture.cpp:566) when I'm running the exported project, but it works fine from the editor. 

It either runs the wrong (webp) unpacker, or the png unpacker fails for some reason, or the exported file is, indeed, corrupt.

The actual export succeeds, it only gives me error when I'm running the game exe.

### Steps to reproduce

See description.

### Minimal reproduction project

_No response_
Repository: vscode
Issue: iPadOS: Input focus bug when using multitasking like 'split view' or 'slide over'
Labels: bug,editor-input,confirmed,web,ios-ipados

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- vscode.dev: 1.68.1
- code-server: 4.5.0
- OS Version: iPadOS 15.5

Steps to Reproduce:

1. Open `vscode.dev` and open any application that allows input with `split view` or `slide over`.
2. Do any input in a window opened with `split view` or `slide over`.
3. If you input after touching the `vscode.dev` screen, the input focus does not go over and stays in `split view` or `slide over`.

https://user-images.githubusercontent.com/47618653/177188713-753029b0-b0a4-4c73-99ef-8f01951b1850.mp4

When that problem occurs, if I leave and re-enter the open document, the input works fine.


They are similar but work well.
1. If I do the same thing with the mouse, it works fine.
2. If I touch the terminal it works fine.
3. If I close `split view` or `slide over` it works fine.
Repository: rust
Issue: Performance regression with 1.62 vs 1.60
Labels: P-low,T-compiler,regression-from-stable-to-stable,C-bug,E-needs-mcve

In running this code with 1.62, vs 1.60, there is an appreciable slowdown in performance.

https://gist.github.com/jzakiya/b96b0b70cf377dfd8feb3f35eb437225

Below are example times, from multiple runs, using an input of 10^14, to really see the accumulation of the regression.

`echo 100000000000000 | ./twinprimes_ssoz`
The times are: `1.60 - 3734 secs` (1hr 2m 14s): `1.62 - 3977 secs` (1hr 6m 17s)

This was  run on a Linux based  Lenovo Legion Slimjet 7 laptop, with AMD Ryzen 9 5900HX, 3.3GHz - 4.6GHZ, 8C|16T cpu.
Repository: deno
Issue: import.meta.resolve second argument
Labels: suggestion,runtime

Chrome is now moving towards shipping `import.meta.resolve` as discussed in https://github.com/denoland/deno/issues/7296.

The current form takes a single argument to resolve.

Node.js implements the ability to pass an optional second argument to `import.meta.resolve` for a custom parentURL to resolve against, allowing `import.meta.resolve` to act as a generic resolver in various contexts, which may be useful as a generic way to expose the global resolver.

I wanted to post this as a tracking bug for Deno to implement this along with https://github.com/denoland/deno/issues/7296. Further discussion welcome.
Repository: godot
Issue: 2d collision mask and layer bug
Labels: topic:physics,topic:2d

### Godot version

3.4.4 and 3.5

### System information

macos m1

### Issue description

I have two area2ds: A and B
A's layer is set to 1, mask set to 2
B's layer is set to 2, mask set to nothing
The expected result is A's collision callback is triggered, but B's callback should not be triggered.
The actual result is both A and B's call back are triggered.



### Steps to reproduce

I have a attached the test scene, if you run the scene, you will find both callback are triggered.

### Minimal reproduction project

[test_layer.zip](https://github.com/godotengine/godot/files/9041662/test_layer.zip)
Repository: create-react-app
Issue: After upgrading to react-scripts 5.0.1 - Babel caching error in start & build
Labels: needs triage

Aloha, 
After upgrading to `react-scripts 5.0.1` I'm getting the Babel caching error 
```
Line 0:  Parsing error: Caching was left unconfigured. Babel's plugins, presets, and .babelrc.js files can be configured...
```

This error was not happening before upgrading.

To resolve, I added `cache` commands to `babel.config.js` and although this works, it works on the initial `start` but on subsequent `starts` fails. To resolve this, I need to toggle between different `caching` commands before each `start` (or simply adding a new line and saving the file (!!!))).  It fails to resolve the error occurring on `build`.

My `babel.config.js` 
```
module.exports = function (api) {
	// api.cache(true);
	// api.cache.forever();
	api.cache.never();
	return {
		plugins: ["macros"],
	};
};
```

Also tried using `.babelrc` file instead, but the outcome is similar.

I'm using `CRACO` and `env-cmd` with CRA, which may be the culprit? 

Any insight anyone can offer would be greatly appreciated.
Repository: rust
Issue: Error Report on Unused Generic Parameters
Labels: A-diagnostics,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: [code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=c9d54a17c9086dd4f7d66d00262ddb5d)

```rust
pub trait SomeGenericTrait<Struct>{
    fn do_something(&self,data: &Struct) -> String;
}

pub struct SomeOtherStruct<T: SomeGenericTrait<S>, S>{
    placeholder: PhantomData<S>, //a placeholder variable is required here for the compiler to remain calm
    pub abc: T
}
```

If we were to remove the `PhantomData<S>` typed member `placeholder` in `SomeOtherStruct`, the compiler would spit out the following error
```
 |
7 | pub struct SomeOtherStruct<T: SomeGenericTrait<S>, S>{
  |                                                    ^ unused parameter
  |
  = help: consider removing `S`, referring to it in a field, or using a marker such as `PhantomData`
  = help: if you intended `S` to be a const parameter, use `const S: usize` instead
```

But if we follow the direction of the compiler and further remove the `S` type parameter in `SomeOtherStruct`, we get 

```
error[[E0412]](https://doc.rust-lang.org/nightly/error-index.html#E0412): cannot find type `S` in this scope
 --> src/main.rs:7:48
  |
7 | pub struct SomeOtherStruct<T: SomeGenericTrait<S>>{
  |                                                ^ not found in this scope

For more information about this error, try `rustc --explain E0412`.
```

So I was wondering if there's a better way for the compiler to either:
1. not output an error since `S` was used as a type parameter for `T`
2. add support to place holder type parameters to enable semantics like `pub struct SomeOtherStruct<T: SomeGenericTrait<_>>{...}`
Repository: godot
Issue: 'Editable Children' or 'Load as Placeholder' don't mark the scene as dirty (asterisk)
Labels: bug,topic:editor,confirmed

### Godot version

3.5 rc5 mono

### System information

Windows 10

### Issue description

When toggling 'Load as Placeholder' or 'Editable Children' the containing scene is not marked with an asterisk that indicates that something has changed and needs to be saved, not sure if that also applies to internal dirty checks, but atleast visually it's missing.

### Steps to reproduce

Open a scene, instantiate a packedscene in it, make sure the outer scene is not in a 'changed' state (no asterisk in title-tab) by saving it once somewhere, then change one of the mentioned toggles on the instanced scene in it and notice the asterisk/dirty indicator not appearing even though toggling those options should produce a change in the resulting file.

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: Compatibility List
Labels: module: binaries,module: docs,triaged

### 🚀 The feature, motivation and pitch

Have an easily to find (e.g. in the previous-versions page) compatibility list. If it has to be in the form of commands and comments ( just like in the previous-versions page), instead of a proper table, then this would be fine, too. 

However I believe many people wont know what version to use. and a proper tabulation would help. 

### Alternatives

wasting good nights sleep to find out it doesn't work, after jumping through all the hoops was not a good alternative. 

### Additional context

this is no "help request" or anything, but simply a feature request for a general professional table (or some list of arbitrary commands)

for context: 

Even though my pytorch version and "CUDA SDK version" are valid and below the max supported driver version as reported by smi (max = 11.4, installed 11.3) ( `pytorch==1.11.0 torchvision==0.12.0 torchaudio==0.11.0 cudatoolkit=11.3` ) pytorch slams the GC max supported "CUDA version" as 3.7 ... nothing you can actually find out until after the fact based on looking at the installation information 


cc @seemethere @malfet @osalpekar @atalman @svekars @carljparker @ezyang @holly1238
Repository: ant-design
Issue: typography editable参数onChange和onEnd都在输入结束后触发
Labels: help wanted,Inactive

### Reproduction link

[https://ant.design/components/typography-cn/#components-typography-demo-interactive](https://ant.design/components/typography-cn/#components-typography-demo-interactive)

### Steps to reproduce

官网链接即可, 在onChange回调添加 console.log(), 在编辑时, 并不会触发onChange, 而是在按了回车后才会触发onChange

### What is expected?

与文档介绍不符, 不是每次文本变化就触发onChange, 期望与文档一致

### What is actually happening?

在onChange回调添加 console.log(), 在编辑时, 并不会触发onChange, 而是在按了回车后才会触发onChange

| Environment | Info |
| --- | --- |
| antd | 4.20.7 |
| React | 18.1.0 |
| System | macOS 11.6.1 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [file_selector] getSavePath doesn't return the selected extension group
Labels: c: new feature,platform-linux,package,a: desktop,P2,p: file_selector,team-linux,triaged-linux

https://github.com/flutter/plugins/blob/main/packages/file_selector/file_selector/lib/file_selector.dart#L89

Currently call getSavePath, set multiple acceptedTypeGroups, and when user changes suggested name, it will not take the selected extension with it.
Repository: go
Issue: proposal: syscall: make use of StartupInfo.Reserved2 on Windows
Labels: OS-Windows,Proposal

### Background

This is a follow-up of #21085. The inheritance part of that issue has been addressed by #44011. But the discovery part remains. This proposal tries to address the discovery part of that issue.

### The Proposal

On Windows, it's a de facto to use [_get_osfhandle](https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/get-osfhandle?view=msvc-170) to discover the inherited file descriptors in the child process. For example, Chromium uses it to support its `--remote-debugging-pipe` option (see [devtools_pipe_handler.cc](https://github.com/chromium/chromium/blob/2ccca58fea8f1ebe8af6c3d2f9a90e15f06f0775/content/browser/devtools/devtools_pipe_handler.cc#L102-L106)). This C Runtime function depends on the information passed by the [lpReserved2](https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/ns-processthreadsapi-startupinfow) field of the `STARTUPINFOW` struct. The MSDN just states that this field is `Reserved for use by the C Run-time; must be NULL.` Luckily, the implementation can be found at least in two projects:
- nodejs: https://github.com/nodejs/node/blob/71691e53/deps/uv/src/win/process-stdio.c#L32-L37
- ReactOS: https://github.com/reactos/reactos/blob/57c84dd6/sdk/lib/crt/stdio/file.c#L405-L532

As of now, the corresponding field in Go is omitted. So I propose to make use of this field to make the inherited file descriptors discoverable by the child process. Here is the change to the `StartupInfo` struct:

```diff
 type StartupInfo struct {
    Cb            uint32
    _             *uint16
    Desktop       *uint16
    Title         *uint16
    X             uint32
    Y             uint32
    XSize         uint32
    YSize         uint32
    XCountChars   uint32
    YCountChars   uint32
    FillAttribute uint32
    Flags         uint32
    ShowWindow    uint16
-   _             uint16
-   _             *byte
+   CbReserved2   uint16
+   Reserved2     *byte
    StdInput      Handle
    StdOutput     Handle
    StdErr        Handle
 }
```

 I will send a CL to show the implementation later. If the CL is landed, the child process can get the inherited file descriptor like this (taking from the test in the upcoming CL):

```go
func cmdCRTPipeHandle(args ...string) {
	get_osfhandle := syscall.NewLazyDLL("msvcrt.dll").NewProc("_get_osfhandle")

	h3, _, _ := get_osfhandle.Call(3)
	if h3 == uintptr(syscall.InvalidHandle) {
		fmt.Fprintf(os.Stderr, "_get_osfhandle: pipe 3 is invalid\n")
		os.Exit(1)
	}
	pipe3 := os.NewFile(h3, "in")
	defer pipe3.Close()

	h4, _, _ := get_osfhandle.Call(4)
	if h4 == uintptr(syscall.InvalidHandle) {
		fmt.Fprintf(os.Stderr, "_get_osfhandle: pipe 4 is invalid\n")
		os.Exit(1)
	}
	pipe4 := os.NewFile(h4, "out")
	defer pipe4.Close()

	// use the pipes, truncated
}
```

### Credits

The idea is inspired by the comments in #21085. Thank you @zombiezen @alexbrainman @glasser @tv42 and all others who were taking part in the discussion!