sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: [Bug]: Calling setAlwaysOnTop(false) and then setAlwaysOnTop(true) seems to cause other always-on-top windows to lose their always on top status
Labels: platform/windows,bug :beetle:,component/BrowserWindow,15-x-y

### Preflight Checklist

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

### Electron Version

15.1.2 -> 2.0.0

### What operating system are you using?

Windows

### Operating System Version

Windows 10

### What arch are you using?

x64

### Last Known Working Electron version

n/a

### Expected Behavior

I expect that calling `setAlwaysOnTop(false); setAlwaysOnTop(true)` on a window will keep other always-on-top windows always on top.

### Actual Behavior

Other windows lose their always-on-top status

### Testcase Gist URL

https://gist.github.com/132060ee8a94ceda7c049187f2ec2dab

### Additional Information

I'm working around [this bug](https://github.com/electron/electron/issues/31505) by detecting focus on an always-on-top window and calling `setAlwaysOnTop(false)` and `setAlwaysOnTop(true)` to bring it back to the front.

It seems like doing that makes the other window that was previously on top not on top anymore (`isAlwaysOnTop()` returns `false`).

1. start main.js
2. open two always on top windows
3. focus on one of them, focus on another
4. click on a background app
5. the main window and the non-focused window (which should be always on top) get sent to the back. Only the focused window is always on top

main.js:
```
const {app, BrowserWindow} = require('electron')

function createWindow () {
  const mainWindow = new BrowserWindow()

  mainWindow.loadFile('index.html')

  mainWindow.webContents.setWindowOpenHandler(_ => {
    return {
      action: "allow",
      overrideBrowserWindowOptions: {
        alwaysOnTop: true,
        parent: mainWindow
      }
    }
  })

  mainWindow.webContents.on("did-create-window", (win) => {
    win.on("focus", () => {
      win.setAlwaysOnTop(false);
      win.setAlwaysOnTop(true);
    })
  });
}

app.on('ready', () => {
  createWindow()
})

app.on('window-all-closed', function () {
  if (process.platform !== 'darwin') app.quit()
})
```

index.html:
```
<button onclick="window.open('https://google.com')">Open Always-on-top Window</button>
```

Possibly related to [this issue](https://github.com/electron/electron/issues/20933)
Repository: create-react-app
Issue: Eslint in "react-scripts" -  "4.0.3" doesn't work
Labels: needs triage,issue: bug report

Added following scripts rule and executed using "npm run lint". Looks like i am not getting any eslint errors/warnings
"lint": "eslint --max-warnings=0 src/**/*.{ts,tsx}"

But if i add "eslint:recommended" to the eslintConfig in package.json, I get errors/warnings.
Repository: vscode
Issue: Add pagination support to `QuickPick` API
Labels: feature-request,api,quick-pick

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

The RemoteHub extension has repository pickers and branch/tag pickers that could contain 1000s of entries. Right now we have a hardcoded limit of 100 results, and it would be great to have an `onDidScrollToEnd` event which we can listen to to smoothly fetch more results into the quickpick.
Repository: material-ui
Issue: [Doc] Add import Option 2 in the Material Icons page
Labels: new feature,docs

<!-- Provide a general summary of the feature in the Title above -->

<!--
  Thank you very much for contributing to MUI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

https://mui.com/components/material-icons/
Right now the following page allows you to 1-click copy the import. Which is very useful to search for an icon and import it immediately. However it only offers Option 1, which is not our prefer way of importing.

Current click-to-copy dialog:
![image](https://github.com/mui/material-ui/assets/84519004/7ca1a345-9cc9-4033-8a2a-4f7ec15e5040)

Options reference from the usage section: https://mui.com/material-ui/icons/#usage
![image](https://github.com/mui/material-ui/assets/84519004/bc0ee5b5-2957-44f1-b54b-79ac7dfd8851)

<!-- Describe how it should work. -->

## Motivation 🔦

<!--
  What are you trying to accomplish? How has the lack of this feature affected you?
  Providing context helps us come up with a solution that is most useful in the real world.
-->
Option 2 is a much better Dev Experience, we use Tree Shaking and bundle size isn't much of an issue for us in the first place, efficient development is.
Repository: create-react-app
Issue: TSC_COMPILE_ON_ERROR causes build to exit with status 0 even when files aren't emitted
Labels: needs triage,issue: bug report

### Describe the bug

When `TSC_COMPILE_ON_ERROR=1` is defined, the `build.js` script always returns an exit code of 0 even when the files are not emitted at all in `/build`.

Using it in production was a mistake in our case, but it's probably used that way by others. If it isn't suited for production builds, a warning would be nice. If it is intended, the return status should still reflect the files being emitted or not.

### Environment

```
  current version of create-react-app: 3.3.1
  running from /usr/local/share/.config/yarn/global/node_modules/create-react-app

  System:
    OS: Linux 4.15 Ubuntu 18.04.6 LTS (Bionic Beaver)
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 12.22.7 - /usr/bin/node
    Yarn: 1.22.15 - /usr/bin/yarn
    npm: 6.14.15 - /usr/bin/npm
  Browsers:
    Chrome: 95.0.4638.54
    Firefox: 93.0
  npmPackages:
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    react-scripts: 4.0.3 => 4.0.3 
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

```
npx create-react-app my-app --template typescript
cd my-app

# edit src/App.tsx, add an import to a file that doesn't exist e.g. `import * from './nope'`

TSC_COMPILE_ON_ERROR=true yarn build && echo ok
```

### Expected behavior

As files are not created in `/build`, exit code should be -1

### Actual behavior

Exit code is 0 and the `echo ok` command executes
Repository: rust
Issue: "one type is more general than the other" with async, generics, Send, and lifetime bounds
Labels: A-lifetimes,T-compiler,C-bug

Consider the following program:

```rust
impl<T: std::future::Future> FutureExt for T {}

pub trait FutureExt: Sized {
    fn with_props<I: IntoIterator<Item = &'static str>>(self, props: I) -> FutureWithProps<I> {
        FutureWithProps { props }
    }
}

pub struct FutureWithProps<I: IntoIterator<Item = &'static str>> {
    props: I,
}

impl<I: IntoIterator<Item = &'static str>> std::future::Future for FutureWithProps<I> {
    type Output = ();
    fn poll(self: std::pin::Pin<&mut Self>, _: &mut std::task::Context<'_>) -> std::task::Poll<Self::Output> {
        std::task::Poll::Pending
    }
}

unsafe impl<I: IntoIterator<Item = &'static str> + Send> Send for FutureWithProps<I> {}

pub async fn foo() -> Box<dyn std::future::Future<Output = ()> + Send> {
    Box::new(async move { async {}.with_props(vec!["foo"]).await })
}
```

This results in the following compiler error, using version 1.56.0:

```
error[E0308]: mismatched types
  --> src/main.rs:33:9
   |
33 |         Box::pin(async move { async {}.with_properties(vec!["foo"]).await })
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ one type is more general than the other
   |
   = note: expected reference `&str`
              found reference `&'static str`
```

The code compiles fine with _any_ of the following modifications:

* Changing `&'static str` into a `String`; or
* Removing the type parameter `I` and using `Vec<&'static str>`; or
* Removing the `Send` impl for `FutureWithProps`; or
* Removing the `Send` bound in `foo()`.

Not sure if this is a known issue, but it seems to happen with this particular mix of features.
Repository: create-react-app
Issue: false positive vulnerabilities
Labels: stale,needs triage,issue: bug report

react-scripts is causing too many false positive vulnerabilities to show up as a result of npm audit. Please fix it. It is annoying & will result in actual attacks being ignored & hidden amongst the false positives.
Repository: godot
Issue: Object.get_property_list() doesn't include constants
Labels: discussion,topic:gdscript

### Godot version

3.3.4 stable

### System information

Ubuntu 20.04.2 LTS

### Issue description

Constant properties are not returned by get_property_list().
In the below example, variable_property is found within get_property_list() but constant_property isn't. If constant_property is changed to a variable, it is included in get_property_list().

```
extends Node

const constant_property: bool = false
var variable_property: bool = false

func _ready():
	
	var const_found: bool = false
	var var_found: bool = false
	
	for property in get_property_list():
		
		if property["name"] == "constant_property":
			const_found = true
		elif property["name"] == "variable_property":
			var_found = true
	
	print("constant_property in get_property_list(): ", const_found) # False
	print("variable_property in get_property_list(): ", var_found)   # True
```

### Steps to reproduce

Add a constant to a script
The created property isn't included in the array returned by get_property_list()
Change the constant to a variable
The same property (this time a variable) is now returned by get_property_list()

### Minimal reproduction project

[get_property_list_Test.zip](https://github.com/godotengine/godot/files/7393798/get_property_list_Test.zip)
Repository: neovim
Issue: terminal: "fx" command breaks Shell display
Labels: bug,status:blocked-external,terminal,has:repro

### Neovim version (nvim -v)

Nvim v0.5.1

### Vim (not Nvim) behaves the same?

yes(vim 8.2)

### Operating system/version

Linux on WSL2(Linux acm-envy2-win-wsl 5.10.43.3-microsoft-standard-WSL2 #1 SMP Wed Jun 16 23:47:55 UTC 2021 x86_64 GNU/Linux)

### Terminal name/version

Both of Windows Terminal and Alacritty

### $TERM environment variable

xtrem-256color

### Installation

AUR

### How to reproduce the issue

fx: https://github.com/antonmedv/fx

```
nvim --clean
:term
echo '{}' | fx
q                   # exit from fx
                    # Shell broken
```

### Expected behavior

Cursor is back after exiting from fx. When I use fx without NeoVim(use Bash from Alacritty directly), works as expected.

### Actual behavior

After exit from fx, two problems happens:

- Cursor disappeared
- The cursor is reset to the top of the window(but the text is not flushed, like the movie).

https://user-images.githubusercontent.com/1362750/138397033-eaf82da5-e083-4a4b-a5c8-314f25a04c57.mp4
Repository: TypeScript
Issue: Suggestion: Allow trailing comma in class implementation list
Labels: Suggestion,Awaiting More Feedback

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

trailing comma class implements list

## ⭐ Suggestion

Allow a trailing comma at the end of `implements` lists, so that the following would not throw an Error:

```ts
interface A {}
interface B {}
interface C {}
class Foo implements A, B, C, {}
//                          ^ Error: Trailing comma not allowed.(1009)
```


<!-- A summary of what you'd like to see added or changed -->

## 📃 Motivating Example

<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->
This is just a minor quality of life improvement. 

If one gets really serious about leveraging Typescript's interfaces, they might find themselves with implementations lists broken into several lines.

If you were to reorder things by moving lines around you'll most likely get yourself one of those :


<img width="911" alt="Code_2021-10-22_0aaa" src="https://user-images.githubusercontent.com/30108880/138399058-c5e76719-71b7-4df5-86ad-6e7aca0b58f6.png">


For reference in other languages, `where` clauses in Rust are structured somewhat similarly to `implements` and allow trailing commas, the official formatter actually inserts one by default as soon as they span several lines.

<img width="464" alt="Code_2021-10-22_07-42-04" src="https://user-images.githubusercontent.com/30108880/138399413-d248facf-90a8-4dd4-a64f-09041e40257c.png">
Repository: rust
Issue: Suggest 2021 edition upgrade on attempt to use disjoint capture
Labels: A-diagnostics,A-closures,T-compiler,A-edition-2021

<!--
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](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=06977ded857d45a45b6cacf27facbe26), compiled using Rust 2018 edition: <!-- Please provide a link to play.rust-lang.org -->

```rust
fn main() {
    let mut x = ("a".to_string(), "b".to_string());
    let mut f = || x.0 += "...";
    x.1 += "...";
    f();
}
```

The current output is:

```
error[E0499]: cannot borrow `x.1` as mutable more than once at a time
 --> src/main.rs:4:5
  |
3 |     let mut f = || x.0 += "...";
  |                 -- --- first borrow occurs due to use of `x` in closure
  |                 |
  |                 first mutable borrow occurs here
4 |     x.1 += "...";
  |     ^^^ second mutable borrow occurs here
5 |     f();
  |     - first borrow later used here

For more information about this error, try `rustc --explain E0499`.
```

<!-- The following is not always necessary. -->
Ideally the output should look include:

```
Note: disjoint capture is available in Rust 2021 edition; see https://doc.rust-lang.org/edition-guide/rust-2021/disjoint-capture-in-closures.html
```

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->
Repository: vscode
Issue: Enable to comment out an entire block by simply placing the cursor on the first line of the block
Labels: feature-request,editor-comments

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
`blockCommentCommand` comments out the selected area, but it's a pain to select the entire area before you comment out. 

So we need to have a feature that you can comment out an entire block by simply placing the cursor on the first line of the block.

This issue is linked to the pull request (#135533 )
Repository: TypeScript
Issue: URLSearchParams allows runtime error initializing parameters
Labels: Suggestion,Domain: lib.d.ts,Experience Enhancement

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

- [searchparams](https://github.com/microsoft/TypeScript/search?q=searchparams&type=Issues)
- [urlsearch](https://github.com/microsoft/TypeScript/search?q=urlsearch&type=Issues)

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- ~~This is a crash~~
- ~~This changed between versions ______ and _______~~
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about: **Common "Bugs" That Aren't Bugs**, **all other headings in FAQ** 👍
- ~~I was unable to test this on prior versions because _______~~

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/HYUw7gBAqgSgMgZRAQwE4GMAWAFNyC2AzgBQDapARAPYDWFANBNXYxQHIDyAKgPq0UBdAQEoA3EA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
new URLSearchParams([["ok", "ok", "NOT_ok"]]);
                                  // ^^ can't handle more than two elements
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
TypeScript allows any length array of any length arrays as arguments, but this throws a JS runtime error.

**Current:** string[][] 👎 

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
`Argument of type '[string, string, string][]' is not assignable to parameter of type...`
If a JavaScript runtime error is produced, TypeScript should warn of incorrect arguments.

**Suggested:** [string, string][] 👍 

Perhaps worth noting that `@node/types` handle this error: [@node/types URLSearchParams contructor](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/87f7309dff4529375e3b0335160991adf9ecae3a/types/node/url.d.ts#L710)

<hr />

PR incoming if this gets **Backlogged** 🙇
Repository: node
Issue: doc: main `perf_hooks` example throws when async
Labels: doc,perf_hooks

# 📗 API Reference Docs Problem

<!--

Thank you for wanting to make nodejs.org better!

This template is for issues with the Node.js API
reference documentation.

For problems with nodejs.org beyond the API
reference documentation, please open an issue
using the issue tracker for our site repository.

  https://github.com/nodejs/nodejs.org

For more general support, please open an issue
using the issue tracker for our help repository.

  https://github.com/nodejs/help

---

For the issue title, please enter a one-line
summary after “doc: ” (preferably 50 characters
or less and no more than 72).

The “✍️” are placeholders signifying requests for
input. Replace them with your responses.

If you are unsure of something, do your best.

-->

<!-- The output of “node --version”. -->

- **Version**: v16.12.0

<!-- The output of “uname -a” (UNIX) or version
and 32-bit or 64-bit (Windows). -->

- **Platform**: Darwin Martins-MBP.lan 20.6.0 Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64 x86_64

<!-- The name of affected core module. -->

- **Subsystem**: `perf_hooks`

## Location

_Section of the site where the content exists_

Affected URL(s):

- https://nodejs.org/api/perf_hooks.html

## Description

_Concise explanation of the problem_

<!-- If applicable, include any screenshots that
may help solve the problem. -->

Simply defining
```js
const doSomeLongRunningProcess = (cb) => global.setTimeout(cb, 1e3)
```
will make the example throw.

The available fixes are, to my knowledge
1. make `doSomeLongRunningProcess` sync (e.g. `const doSomeLongRunningProcess = (f) => f()`)
2. remove `performance.measure('Start to Now')`
3. remove `performance.clearMarks()`

I think the proper solution is 3.

Additionally, the performance observer only emits the first entry.

A more proper example would be the following, as it handles the edge cases gracefully:

```js
const { PerformanceObserver, performance } = require('perf_hooks');

const obs = new PerformanceObserver((items) => {
  console.log(
    items.getEntries().map(({ name, duration }) => `${name}: ${duration}`),
  )
})
obs.observe({ type: 'measure' })
performance.measure('Start to Now')

performance.mark('A')
// const doSomeLongRunningProcess = (cb) => setTimeout(cb, 1e3)
// const doSomeLongRunningProcess = (cb) => cb()
doSomeLongRunningProcess(() => {
  performance.measure('A to Now', 'A')

  performance.mark('B')
  performance.measure('A to B', 'A', 'B')
  
  performance.clearMarks();
})
```


---

<!-- Use “[x]” to check the box below if you are
interested in contributing. -->

- [x] I would like to work on this issue and
      submit a pull request.
Repository: flutter
Issue: Can’t use Bluetooth Keyboard on flutter webview
Labels: p: webview,package,team-ecosystem,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,triaged-ecosystem

sdk: ">=2.13.0 <3.0.0"
dependencies:
webview_flutter: ^2.1.2

Test platform：
Android、IOS

We embed the code editor into the web page, but when we use WebView to load the URL, we can't control the cursor through the direction key of the Bluetooth keyboard

ps:We loaded our URL on safari successfully
Repository: godot
Issue: Empty scene indicates that there are unsaved changes
Labels: bug,topic:editor

### Godot version

3.4 rc1 mono

### System information

w10 64

### Issue description

The empty scene is behaving like a user generated scene when a change is registered.
Watch the video, I move the order of the scripts in autoload and the unsaved changes icon appears in the scene tab.


https://user-images.githubusercontent.com/19652075/138430050-ce5976e2-a0a1-492c-9757-7dd4d0d73701.mp4


### Steps to reproduce

...

### Minimal reproduction project

...