sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: Add Promise-based versions for some functions in child_process
Labels: feature request

### What is the problem this feature will solve?

It would be nice if child_process functionality, such as `exec` and `execFile`, had Promised based versions by default. Currently it does not, see https://nodejs.org/api/child_process.html

Note that only child_process functions that can be async/await should be considered. This does not include things such as `fork` or `spawn`.

### What is the feature you are proposing to solve the problem?

A new `child_process/promises` import path that can be used similar to how [fs promises](https://nodejs.org/api/fs.html#fs_promise_example) are used:

```js
// Using ESM Module syntax:
import { exec } from 'child_process/promises';

try {
  const { stdout } = await exec(
    'sysctl -n net.ipv4.ip_local_port_range'
  );
  console.log('successfully executed the child process command');
} catch (error) {
  console.error('there was an error:', error.message);
}
```

The ask is basically that `child_process/promises` could just return a variant such as `const exec = util.promisify(process.exec);` as a convenience. 

### What alternatives have you considered?

I am already using `const exec = util.promisify(process.exec);` but that is not as nice. And this new proposal follows along what is happening in other Node.js APIs.

(The original ask in https://github.com/nodejs/node/issues/38823 was perceived as asking for the entire module and all APIs to be async/await. This issue here narrows it down to only focus on the functions that can be.)
Repository: vscode
Issue: Consider using experiment friendly name when using `Report Issue` command
Labels: feature-request,issue-reporter

<!-- ⚠️⚠️ 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. -->
"A/B experiments" under issues: https://github.com/microsoft/vscode-python/issues/22100

![e677f3e4-58ee-417c-b885-942df7ad464c](https://github.com/microsoft/vscode/assets/13199757/05bafb33-4467-46f1-b600-d7e74a86f8af)

don't seem very useful. They don't seem to contain the user friendly experiment name that I can recognize, rather an encoded one.

We should be able to change that to the feature gate name, the one thing is that this is more specific in the sense that it maps to a specific stage (e.g. public or insider) and step (10% or 20% etc). cc/ @luabud
Repository: PowerToys
Issue: Always On Top - Follow
Labels: Idea-Enhancement,Product-Always On Top,Needs-Triage

### Description of the new feature / enhancement

When activated, the window will remain always on top and stay in it's position when desktops are switched, mirroring the behavior of "Always on Top" when using task manager. 
This is especially useful for when users have multiple screens.

For further clarification, currently Task Manager is the only application that remains always on top and remains in a fixed position if you switch desktops (using Windows key + arrow) and the current "Always on Top" feature through PowerToys only pins windows on the same desktop and cannot affect other desktops or carry from one desktop to another like Task Manager does. 

### Scenario when this would be used?

This would be used whenever a user wants something to stay in it's position when switching desktops. 

Example 1:  A software engineer using Visual Studio has many windows they need to look at for comparison but Visual Studio is the only thing they need to keep on one of their screens visible at all times. They activate the feature and can now flip through multiple pages without having to look away from Visual Studio and can clearly see the information they need to. 

Example 2: A streamer with 2 monitors wants to keep his game running on the same monitor and needs to keep it open and visible, but also wants to change to other windows on his other monitors while keeping his current game window always on top. He activates the feature and his selected window remains maximized and on top and moves from desktop1 with his game open and twitch tools on his second monitor to desktop2 with his game open on his first monitor and discord on his second monitor.

Example 3: A Stock trader has 3 monitors and needs to keep her scanning/news software visible and open on her middle monitor at all times and switch the charts/windows on her other screens to something else. 

There are many scenarios where someone might want to keep a certain program Always on Top and be visible across multiple desktops for productivity and enhanced workflow.

### Supporting information

![image](https://github.com/microsoft/PowerToys/assets/105891869/19e90562-877f-4c95-944b-f7831ba32537)
Repository: pytorch
Issue: Module-level bufferization for torch dynamo module spanning multiple `fx.GraphModule`
Labels: feature,triaged,needs research,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

### 🚀 The feature, motivation and pitch

Some details across:
https://github.com/pytorch/pytorch/issues/109240#issuecomment-1737764251
https://github.com/pytorch/pytorch/issues/106596#issuecomment-1737835937

In summary:
1. It is likely that since we do not analyze buffer aliases (read/write) which may occur in graph breaks, we require copying inputs whenever they are mutated by the fx graphs. (TODO: add source reference?)
2. This can be complicated for scenarios like https://github.com/pytorch/pytorch/issues/109240#issuecomment-1737764251 where we are unsure when we want to commit the mutations back to the original buffer - which would be unnecessarily constrained by the time-sensitive nature of potential eager-mode mutations.

Solution:
1. If we can analyze the code in the eager mode computations (r/w accesses to given buffer), then we can better plan for bufferization across the entire module, reducing copies in between graph breaks and fx graphs. However, pointer alias analysis is generally impossible to do in opaque code (due to pointer encapsulation), so this may be completely infeasible.

However, it _may_ be the case that we know that _certain_ fx graph ouputs can _never_ be mutated by eager code - because they are **owned** (i.e. created) by the graph, hence there can be no pointer alias to it without explicit reference to the pointer in the eager code.

### Alternatives

Unclear

### Additional context
Unclear if any of this is already tracked in torch dynamo [`SideEffects`](https://github.com/pytorch/pytorch/blob/main/torch/_dynamo/side_effects.py)

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519
Repository: go
Issue: x/tools/gopls: optimize deep completion
Labels: gopls,Tools

Noticed while looking into a regression that caused deep completions to run spuriously (#62665): there appeared to be a lot of low-hanging fruit to optimize the performance of deep completions.  For example, I analyzed one of our completion benchmarks on Kubernetes, and observed that type checking was only 65ms, while deep completion took an *additional* 100-200ms. I think we can get completion latency much closer to type checking latency, even while scanning many deep candidates.

The potential optimizations I see are very similar to what we did for workspace/symbol requests:
1. Add concurrency: completion is single-threaded at present.
2. Avoid pre-building strings, by performing fuzzy match before assembling the fully qualified symbol path.
3. Use a faster fuzzy matcher (and fix ranking [edge cases](https://go.dev/issue/60201))
4. Exclude deep candidates earlier, once their score is too low (we only ever serve 3 candidates!).  If we make scores only decrease throughout 'addCandidate', and exit early, we can likely avoid a lot of unnecessary type inference.

_Originally posted by @findleyr in https://github.com/golang/go/issues/62665#issuecomment-1734437430_
Repository: create-react-app
Issue: React scripts ( "react-scripts": "^5.0.1") is using semver@6.3.0 which has security vulnerability 
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

React scripts ( "react-scripts": "^5.0.1") is using semver@6.3.0 which has security vulnerability 

(react-scripts@5.0.1
└─┬ react-scripts@5.0.1
  ├─┬ @babel/core@7.19.6
  │ ├─┬ @babel/helper-compilation-targets@7.20.0
  │ │ └── semver@6.3.0 
  │ └── semver@6.3.0      <=====
  ├─┬ @svgr/webpack@5.5.0
  │ └─┬ @babel/preset-env@7.19.4
  │   ├─┬ babel-plugin-polyfill-corejs2@0.3.3
  │   │ ├─┬ @babel/helper-define-polyfill-provider@0.3.3
  │   │ │ └── semver@6.3.0 
  │   │ └── semver@6.3.0 
  │   └── semver@6.3.0 
  ├─┬ babel-jest@27.5.1
  │ └─┬ babel-plugin-istanbul@6.1.1
  │   └─┬ istanbul-lib-instrument@5.2.1
  │     └── semver@6.3.0 
  ├─┬ babel-loader@8.3.0
  │ └─┬ make-dir@3.1.0
  │   └── semver@6.3.0 
  ├─┬ babel-preset-react-app@10.0.1
  │ └─┬ @babel/plugin-transform-runtime@7.19.6
  │   └── semver@6.3.0 
  ├─┬ css-loader@6.7.1
  │ └── semver@7.5.4  deduped
  ├─┬ eslint-config-react-app@7.0.1
  │ ├─┬ @babel/eslint-parser@7.19.1
  │ │ └── semver@6.3.0 
  │ ├─┬ @typescript-eslint/eslint-plugin@5.42.0
  │ │ ├─┬ @typescript-eslint/utils@5.42.0
  │ │ │ └── semver@7.3.8 
  │ │ └── semver@7.3.8 
  │ ├─┬ @typescript-eslint/parser@5.42.0
  │ │ └─┬ @typescript-eslint/typescript-estree@5.42.0
  │ │   └── semver@7.3.8 
  │ ├─┬ eslint-plugin-jsx-a11y@6.6.1
  │ │ └── semver@6.3.0 
  │ └─┬ eslint-plugin-react@7.31.10
  │   └── semver@6.3.0 

Recommend by White scans, Upgrade to version: semver - 5.7.2,6.3.1,7.5.2;org.webjars.npm:semver:7.5.2.
Repository: go
Issue: x/website/tour: light mode links not underlined on hover
Labels: NeedsInvestigation

Navigate to go.dev/tour.
On light mode, links are not underlined when hovering over them:
<img width="404" alt="Screenshot 2023-09-27 at 12 32 02 PM" src="https://github.com/golang/go/assets/6634754/5f87dea9-0f5d-4fca-b2e8-5ec4086db16e">

vs dark mode on tour and other docs that do underline:
<img width="421" alt="Screenshot 2023-09-27 at 12 31 55 PM" src="https://github.com/golang/go/assets/6634754/2862337f-8bea-4c56-8f58-79e0314c3591">
<img width="1193" alt="Screenshot 2023-09-27 at 12 33 01 PM" src="https://github.com/golang/go/assets/6634754/8b56ce53-31c6-42ce-857c-8a4fe82607f0">
Repository: go
Issue: x/website/tour: dark mode button color contrast too low
Labels: NeedsInvestigation,website

The `Run`/`Kill` button has low contrast:
<img width="65" alt="Screenshot 2023-09-27 at 12 35 59 PM" src="https://github.com/golang/go/assets/6634754/24e118ae-5e0e-4c52-9fe4-da657d381c94">

<img width="210" alt="Screenshot 2023-09-27 at 12 35 49 PM" src="https://github.com/golang/go/assets/6634754/0869b5b4-71ee-4d76-b78a-3a8126f43e67">

The other menu buttons on hover, display low contrast (`Reset`, `Format`, `Syntax On/Off`, `Imports On/Off`):
<img width="68" alt="Screenshot 2023-09-27 at 12 36 32 PM" src="https://github.com/golang/go/assets/6634754/6da8c1ca-636b-4942-bbe6-dddb7adca534">
<img width="230" alt="Screenshot 2023-09-27 at 12 36 46 PM" src="https://github.com/golang/go/assets/6634754/03344c16-4108-457b-abce-4bb116ac0b03">
Repository: go
Issue: x/website/tour: dark mode file name colors change on hover / click 
Labels: NeedsInvestigation,website

Navigate to https://go.dev/tour/welcome/1 and switch to dark mode. Hover and click on the `hello.go` filename.

Normal:
<img width="131" alt="Screenshot 2023-09-27 at 12 43 14 PM" src="https://github.com/golang/go/assets/6634754/387e9556-b864-4b5c-8b49-6401f435325d">
Hover:
<img width="154" alt="Screenshot 2023-09-27 at 12 42 58 PM" src="https://github.com/golang/go/assets/6634754/87b01c7f-113c-4878-9b23-858cbdaad55e">
Click:
<img width="77" alt="Screenshot 2023-09-27 at 12 44 06 PM" src="https://github.com/golang/go/assets/6634754/195628ae-5cce-4ffe-9542-6b3ca57f3f7a">

In light mode, hovering over the file name does not have a visual effect.
Repository: TypeScript
Issue: Outline doesn't include JS namespace object
Labels: Suggestion,Awaiting More Feedback

Type: <b>Bug</b>

Please see the attached workspace.  When editing test2\test2b.js or test2\test2c.js, the outline does not show the proper tree.  Also, if you "Go to Definition" on the items referenced in the functions, you will get a "No definition found..." error.


VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12850HX (24 x 2419)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.67GB (4.57GB free)|
|Process Argv|C:\\Devel\\qb-latest\\QB_PLATFORM\\software\\web\\test --crash-reporter-id 9627556d-631e-4542-bfc5-c239f85d7509|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (5)</summary>

Extension|Author (truncated)|Version
---|---|---
gitlens|eam|14.3.0
shortcut-menu-bar|jer|3.0.4
hexeditor|ms-|1.9.12
intellicode-api-usage-examples|Vis|0.2.8
vscodeintellicode|Vis|1.2.30


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
962ge761:30841074
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30839828
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
pythonmhint1:30842940
dsvsc015:30845448

```

</details>

<!-- generated by issue reporter -->
[test.zip](https://github.com/microsoft/vscode/files/12739463/test.zip)
Repository: PowerToys
Issue: FencyZones: use it when resize a window
Labels: Needs-Triage

### Description of the new feature / enhancement

I use vertically and horizontally divided screens. I like to moving the window with win+arrow buttons. But would be nice to increase the regions with other fields to resize the window.
for example: 
- with win+shift+arrows combination, 
- or with mouse actions like dragging the edge while the grid is usable, 
- or with double click on window's edge increase window's that side to the next grid.

### Scenario when this would be used?

This is usefull for overdivided screens like my screen.
The attacked file is my dividing for many combination in one settings. 
The sensing distance are 200 pixels. It is enough for 1/4, 1/3, 1/2, 2/3 of screen width combinations
it would be nice to use this assimetric config with resize options.
![multi region select](https://github.com/microsoft/PowerToys/assets/46201574/b0ad5606-2529-4d63-8ea3-246964379802)


### Supporting information

_No response_
Repository: opencv
Issue: [security] Automated releases
Labels: feature,category: infrastructure

### Describe the feature and motivation

Automated releases can help keep your releases consistent, transparent for users and, save maintainance time. It also improves the security of the release by using a "trusted builder". A "trusted builder" provides a higher level of confidence, for example, that a `make` command always runs with the same flags.

### Additional context

To do that, one option is to create a GitHub workflow that runs when you create a new tag, then it builds, generates the necessary `.zip` and `.exe` files, generates the files SHA256, and creates the release on GitHub. Here's a quick draft on the idea:
```yml
# release.yml

on:
  push:
    tags:
      - '*'
...
  - name: build
    run: make build
  - name: generate sha256
    run: sha256sum output.zip
  - name: release
    uses: actions/create-release
    with:
      prerelease: false
      release_name: ${{ github.ref }}
      tag_name: ${{ github.ref }}
      body_path: ${{ body_with_sha_sums_and_link_to_changelog }}
  - name: upload release assets
    uses: actions/upload-release-asset
    with:
      asset_path: ./output.zip
```

About me, I'm Gabriela and I work on behalf of Google and the OpenSSF suggesting supply-chain security changes.
Repository: node
Issue: test_runner: document how to mock external libs
Labels: doc

### Affected URL(s)

https://nodejs.dev/en/api/v18/test/#mocking

### Description of the problem

I don't see any docs here on how to mock an external library imported from node modules. It would be useful to see that!
Repository: PowerToys
Issue: Layout switching & Auto switching layouts
Labels: Needs-Triage

### Description of the new feature / enhancement

Layout switching & Auto switching layouts

### Scenario when this would be used?

please add new feature to Switch the layout of the last entered word or selected text. for example, use Keyboard shortcut to change (اثممخص) to (hello) or ( lk o,fl) to (من خوبم).

Auto switching layouts will be good when I use browser and text editor. for example, I use English language in browser to translate and Persian language in text editor. It allows me not to monitor the current input language.

### Supporting information

_No response_
Repository: PowerToys
Issue: number converter
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

number converter

### Scenario when this would be used?

I need new feature to change numbers from English to Persian or arabic number in text editors like Notepad. for example, Consolas is my font in Notepad. I need to copy Persian numbers from browser to use them when typing in persian language.

English: 1234567890
Persian: ۱۲۳۴۵۶۷۸۹۰
Arabic: ۱۲۳٤٥٦۷۸۹۰
difference Persian and Arabic numbers: (۴,۶) Vs (٤,٦)

I tried "Context" for "Use native digits" in Language & region/ Region/ Customize Format settings but it was useless. change "Standard digits" was useless too because I have problem when type English.

### Supporting information

_No response_
Repository: PowerToys
Issue: copy/paste/delete popup on selecting text
Labels: Needs-Triage

### Description of the new feature / enhancement

copy/paste/delete popup on selecting text

### Scenario when this would be used?

show popup on selecting text to copy/paste/delete text will be good feature.

Thanks.

### Supporting information

_No response_
Repository: flutter
Issue: [Impeller] Unclosed filled rects are not optimized.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

Reading the code for a recent bug fix PR (https://github.com/flutter/engine/pull/46218) it looks like we only optimize rect paths if they are closed, but filled rects can be optimized whether or not they are specifically closed.

https://github.com/flutter/engine/blob/3929861d1278242a6f98dff08ad91ee2f42c9956/impeller/display_list/dl_dispatcher.cc#L828
Repository: PowerToys
Issue: Please add an option to center non-resizable windows instead of top-left justifying them
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

There should be an option to treat non-resizable windows different from regular windows. They should be centered instead of justified to the top left, which is not sensible for small popup dialogs or progress bar windows.

Ideally windows smaller than some minimum dimensions the user can define in the fancy zones settings should also be centered, and an option to center windows by application name similar to how you can exclude windows by application name in the settings already would also be very welcome..

### Scenario when this would be used?

![Screenshot 2023-09-27 224205](https://github.com/microsoft/PowerToys/assets/29549891/155d75a4-2eb1-42af-93c4-82fbe7da4cd3)

Here's an example from the Windows explorer, this is going to affect pretty much everyone using FancyZones. The file transfer progress window is small and non-resizable, yet it still gets top-left justified like a regular window. Maybe some people actually prefer it that way, but I believe there should at least be an option to center these types of windows in their zone instead.
Repository: godot
Issue: Can't rename scenes when they are open
Labels: bug,topic:editor,usability

### Godot version

4.1.1.stable

### System information

Arch Linux - Nvidia RTX 3050, Core i5 11400h

### Issue description

You can't rename a scene when it is open

### Steps to reproduce

New Project -> Create a scene -> open it -> try to rename it

### Minimal reproduction project

Blank project with a single scene
Repository: flutter
Issue: Document the add-to-app scenarios that must be avoided.
Labels: engine,d: wiki,P2,team-engine,triaged-engine

Add-to-app is great for incremental adoption of Flutter. But it can greatly diminish the developer experience and the performance expectations of Flutter applications. To the point where even the team would recommend against using Flutter.

Right now, there isn't great guidance on when add-to-app must be avoided. This issue tracks writing down guidance that details various add-to-app scenarios and the degradation in developer experience and application performance that can be expected in each scenario.
Repository: ant-design
Issue: Provide an option to prevent Mentions popover from opening
Labels: Inactive,improvement

### What problem does this feature solve?

We want users to be able to direct their conversations from person to person, with each request going to a specific person. If we allowed multiple mentions in the same block, the recipients wouldn't know who the request is directed to.

### What does the proposed API look like?

I see two possible ways of allowing this:

1. **Include `open` and `onOpenChange` properties.** This would provide an API similar to other components that show/hide features and give us the opportunity to override the visibility of the Mentions once one is found. We could then ignore the `onSelect` results if desired.
```tsx
const [open, setOpen] = useState(false);
<Mentions open={open} onOpenChange={setOpen} ... />
```
2. **Include a `disabled` property.** This would be a more all-in-one approach that would not call `onSelect` while the component is disabled.
```tsx
const [foundItem, setFoundItem] = useState<string | undefined>();
<Mentions
  onSelect={
    ({ key }) => {
      setFoundItem(key)
    }
  }
  disabled={!!foundItem}
  ...
/>
```

Either way, or perhaps a third option, would give us the ability to control when it appears.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->