sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: impl CookieStore?
Labels: feature request,never-stale

### What is the problem this feature will solve?

Cookie parsing and serializing is tuff. Most often you need a cookie plugin for whatever reason and dose are downloaded milion of times / week on npm

Adding a memory based [CookieStore](https://wicg.github.io/cookie-store) that can be constructed using `new CookieStore()` in some form would be beneficial. I'm just imagining http, https, http2 and [fetch](https://github.com/whatwg/fetch/issues/1384) to have support for passing in own custom CookieStore parameter somewhere for it to be used somehow
Repository: TypeScript
Issue: Possible regression in error elaboration for optional properties
Labels: Bug

# Bug Report

It is my understanding that PR #47738 made changes to the elaborations of certain error messages. For me it had an adverse effect in a somewhat simple use case that includes optional parameters passed to an object.

I tried reproducing it in the TS playground, but version 4.6 is not yet available there and the latest nightly playground build doesn't seem to include this change yet.

Getting the following error in v4.6.2:
`Type 'boolean' is not assignable to type 'string'`

The error in v4.5.5 used to be:
`Type 'true' is not assignable to type 'string | undefined'`

I'll note that this happens whether `undefined` is allowed explicitly in the type definition, or defined only as an optional parameter.

### 🕗 Version & Regression Information

- This changed between versions 4.5.5 and 4.6

### ⏯ Playground Link
Here's a playground with the required setup, but as noted above, the playground doesn't seem to have the change that causes this issue yet.

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.7.0-dev.20220215#code/C4TwDgpgBAzsCGwIygXigbwLACgqwSQEYB+ALgICcBLAOwHMBuXAX2Z1wDMBXWgY2DUA9rSgAPABQgKcRMgCUmXPnyUIwbpVEh2LXLkkYCcohWCVu0FvPZA)

### 💻 Code

```ts
type states = {
  state1?: string | undefined;
};

function x(y: states) {}

x({ state1: true });
```

### 🙁 Actual behavior

Error message ignores optional definition, or explicit undefined definition, and returns an error that only mentions the allowed primitives.

### 🙂 Expected behavior

Error message should mention `undefined` as an allowed value.
Repository: electron
Issue: [Feature Request]: allow more control over recent documents in jump list / dock
Labels: enhancement :sparkles:,platform/windows

### 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.

### Problem Description

There is API to add and clear recent documents: `app.addRecentDocument` and `app.clearRecentDocuments`. Specifically on Windows, a user can remove documents from the jump list by right clicking and selecting the document for removal. There is no API in Electron to be informed when this happens. Related, there is no method to remove a single recent document either, so when the user performs an action inside the Electron application to remove such a document, it could not be applied to the OS.

### Proposed Solution

Introduce a new set of APIs to remove individual recent documents and to gather removed documents to handle them.

### Alternatives Considered

Via the jump list API it is possible to do almost everything of the above, with the exception that you don't get the native behaviour of the built in recent category, you have to build it on your own. If someone can explain the differences, then maybe it would be possible for us to switch to a custom category for this scenario, but I am unsure about the implications.

### Additional Information

We are using both recent documents API and jump list API in VSCode. Related issue: https://github.com/microsoft/vscode/issues/144237
Repository: PowerToys
Issue: FancyZones full-screen layout template
Labels: Idea-Enhancement,FancyZones-Layouts,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

There should be a built-in layout template with just a single full-screen zone.

### Scenario when this would be used?

My personal use case for this is to automatically open Teams meetings on a secondary monitor, and it's very easy to set up using the column layout with a single column and no space around. It just occurred to me that this layout is probably used often enough by users that it makes sense to have as a direct choice.

### Supporting information

Maybe there's also an opportunity for some kind of interop with the standard window snapping functionality that would be unique to this layout? For example detecting when the user maximizes a window on that screen and assigning that window to the zone, so that it will participate in layout changes later. Worth thinking about for someone that knows more about that under the hood, and probably a good idea to make separate issues for any ideas that come up.
Repository: vscode
Issue: [less] Build-in LESS syntax hint error, multiple '&'
Labels: bug,css-less-scss

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.64.2
- OS Version: Windows_NT x64 10.0.19042

Steps to Reproduce:

1. create a .less file (or change file type to less)
2. write the follow
```less
.link {
  && {}
}
 ```
3.cursor focus on '&&', and vscode show the tips(that's wrong

![869763d25b5a60ac979a5056833b507](https://user-images.githubusercontent.com/15227557/156364340-000faf73-8fb5-4a17-b29c-e6bce1d3dc0b.png)

4. follow the less official documentation - [Multiple `&`](https://lesscss.org/features/#parent-selectors-feature-multiple-)

![cad4ac5b8d0da95d73def5c9907fbce](https://user-images.githubusercontent.com/15227557/156365974-109d6283-2d77-433f-a4e2-bef4d1c88afc.png)

it should be **element with a class list that includes both "link" and "link"**, NOT **element with class "link" ~descendant~ children of  an element with class "link"**

```css
.link.link {} // expected
.link > .link {} // wrong
```
Repository: PowerToys
Issue: FancyZones screen-filling Focus layout template
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

The current Focus layout is a bit useless because the zones it makes are too small to be usable in practice, and it's a hassle to resize each of them.

There's a few options I can see for how to improve this, which could be done in increments, and all just suggestions and ideas:

- Cheap: Add layout template editor controls for zone size, and possibly for distance between each zone and distance to screen edge.
- Medium: Auto-size the zones so that the corners of the first and last zones are the same distance from the respective screen corner.
- Expensive: A fully dynamic layout that adds, removes and resizes windows as they are added to and removed from the layout in order to fill the screen.

### Scenario when this would be used?

It's essentially intended as a sort of taskbar quasi-replacement for multitasking on secondary monitors, or at least that's my use case for it. To achieve that I'd actually also want the direction to be configurable so that it stacks from the lower-left corner to the top-right corner, since that would expose the top-left corner of every window which typically has the app icon and title, but I can make a separate issue for that if this one gets approved.

I realize it's a bit niche, though, so I'll survive just fine with hand-crafted layouts too. 

### Supporting information

_No response_
Repository: vscode
Issue: Indicate if Task Exited for both dependency tasks
Labels: feature-request,tasks

![image](https://user-images.githubusercontent.com/2931520/156371876-ec89cddf-a946-40b2-b7a5-44a897845a35.png)

Both tasks exited, but the list to the right does not reflect this.

I would expect the checkmark and error icon to disappear.
Repository: material-ui
Issue: [Grid] Inconsistent layouts between Chrome and Safari
Labels: bug 🐛,component: Grid

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Hey, I was playing with Grid in an existing project and I noticed some inconsistent behaviour between Chrome and Safari when nesting Grid containers.

```
<Grid container direction="row">
	<Grid item>
		<Grid container direction="column">
			<Grid item>1</Grid>
			<Grid item>2</Grid>
		</Grid>
	</Grid>
	<Grid item>
		<Grid container direction="column">
			<Grid item>3</Grid>
			<Grid item>4</Grid>
		</Grid>
	</Grid>
</Grid>
```

The result of the above snippet is identical in both Chrome and Safari.
![image](https://user-images.githubusercontent.com/5859395/156372792-97ba40b5-b4fa-4ef0-b542-2ccbb7bf5136.png)

But if revert the directions of the containers from row to column and from column to row, the layout is not the same in Chrome and Safari anymore. There is a much bigger spacing in Safari between the rows in Safari.

```
<Grid container direction="column">
	<Grid item>
		<Grid container direction="row">
			<Grid item>1</Grid>
			<Grid item>2</Grid>
		</Grid>
	</Grid>
	<Grid item>
		<Grid container direction="row">
			<Grid item>3</Grid>
			<Grid item>4</Grid>
		</Grid>
	</Grid>
</Grid>
```

And here are the results:

### Chrome
<img width="70" alt="Screen Shot 2022-03-02 at 3 44 12 PM" src="https://user-images.githubusercontent.com/5859395/156373336-f786e59a-be73-4d0f-b021-3bbf517d9f9b.png">

### Safari
<img width="83" alt="Screen Shot 2022-03-02 at 3 44 33 PM" src="https://user-images.githubusercontent.com/5859395/156373370-0cf2de29-f1d4-4d94-9304-436826962334.png">

If I add a `nowrap` to the outermost container the result becomes the same on both Chrome and Safari. But none of the elements is overflowing so I don't think there should be need of that `nowrap` attribute

```
<Grid container direction="column" wrap="nowrap">
	<Grid item>
		<Grid container direction="row">
			<Grid item>1</Grid>
			<Grid item>2</Grid>
		</Grid>
	</Grid>
	<Grid item>
		<Grid container direction="row">
			<Grid item>3</Grid>
			<Grid item>4</Grid>
		</Grid>
	</Grid>
</Grid>
```

### Expected behavior 🤔

I would expect a consistent layout in both Chrome and Safari when nesting Grid container. The behaviour in Chrome looks more correct than in Safari

### Steps to reproduce 🕹

```
<Grid container direction="column">
	<Grid item>
		<Grid container direction="row">
			<Grid item>1</Grid>
			<Grid item>2</Grid>
		</Grid>
	</Grid>
	<Grid item>
		<Grid container direction="row">
			<Grid item>3</Grid>
			<Grid item>4</Grid>
		</Grid>
	</Grid>
</Grid>
```

### Context 🔦

_No response_

### Your environment 🌎

**@material-ui/core v4.12.3**
Repository: PowerToys
Issue: Start a specific app (a process) with a pre-set cpu prio
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Remember the cpu priority of a frequently used app (a process) - after a system restart.

### Scenario when this would be used?

Setting OBS to "higher" or "high" priority fixes random stuttering on the NDI-Stream - of the LAN cam.

### Supporting information

Proprietary solutions can do the job already... (https://www.start64.com/index.php/64-bit-software/64bit-process-management/4100-prio-process-priority-saver)
Repository: pytorch
Issue: Pure C binding/wrapper with libtorch for inference applications
Labels: feature,triaged

### 🚀 The feature, motivation and pitch

The motivation for pure C binding/wrapper with libtorch is easier FFI c-binding to languages such as Swift, which don't have C++ FFI. Swift iOS developers have to learn Objective C to use libtorch in their applications.

### Alternatives

This library claims that Pytorch may provide this natively in the future:

https://github.com/lighttransport/c-libtorch

### Additional context

_No response_
Repository: node
Issue: distutils package deprecation warning in configure.py
Labels: build,python

`D:\Git\nodejs\node\configure.py:17: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives`

@nodejs/python
Repository: TypeScript
Issue: Selectively opting in to `exactOptionalPropertyTypes`
Labels: Suggestion,Awaiting More Feedback

# Suggestion

I have one or two data types where misuses of `undefined` for optional members have caused multiple bugs. I'd love to be able to update my type definitions and TypeScript configuration to catch these mistakes. `exactOptionalPropertyTypes` does what I want; however, enabling it also raises hundreds of compilation errors throughout my project, in areas of the code where the use of `undefined` is just fine.

Is there, or could there be, a way to enable `exactOptionalPropertyTypes` for individual types? Maybe something like the following?

```ts
interface SampleType {
  a?: string | undefined;
  b?: string;
  c?: string!;
}

let value: SampleType = {};
value.a = undefined; // always legal
value.b = undefined; // legal if exactOptionalPropertyTypes is false
value.c = undefined; // never legal
```

## 🔍 Search Terms

exactOptionalPropertyTypes

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [X] This wouldn't change the runtime behavior of existing JavaScript code
* [X] This could be implemented without emitting different JS based on the types of the expressions
* [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [X] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: node
Issue: Readable.from() behaves in an unexpected way
Labels: stream

### Version

v16.6.1

### Platform

Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101 arm64

### Subsystem

stream

### What steps will reproduce the bug?

When we create a readable  from a buffer it works in an unexpected way:

Example:

```js
const readable = Readable.from(buffer)
```

`readable.readableLength`  should be equal `1`  instead it would be equal to `0`

Also:

```js
const readable = Readable.from([buffer])
```

`readable.readableLength` should be equal `1`  instead it would be equal to `0`

only when we do it this way. It works as expected:

```js
const readable = Readable.from([])
readable.push(buffer)
```

`readable.readableLength`  would be equal to `1`

Test case:

```js
import { Readable } from 'stream'

const buffer = Buffer.from('lalallala')

console.log({buffer})

const r1 = Readable.from([])
r1.push(buffer)

const r2 = Readable.from([buffer])

const r3 = Readable.from(buffer)

const log = {
  r1: r1.readableLength,
  r2: r2.readableLength,
  r3: r3.readableLength,
  equalResults: undefined
}

const r1Result = r1.read()
const r2Result = r2.read()
const r3Result = r3.read()

log.equalResults = r1Result === r2Result && r1Result === r3Result

console.log(log)

console.log({
  r1: r1.readableLength,
  r2: r2.readableLength,
  r3: r3.readableLength,
})
```

It will log the following: 

```js
{ buffer: <Buffer 6c 61 6c 61 6c 6c 61 6c 61> }
{ r1: 1, r2: 0, r3: 0, equalResults: true }
{ r1: 0, r2: 0, r3: 0 }
```



### How often does it reproduce? Is there a required condition?

always

### What is the expected behavior?

to output `readableLength = 1`  with:

```js
const readable = Readable.from(buffer)
```

```js
const readable = Readable.from([buffer])
```

```js
const readable = Readable.from([])
readable.push(buffer)
```



### What do you see instead?

it only r1 t outputs `readableLength = 1` with:

```js
const readable = Readable.from([])
readable.push(buffer)
```

### Additional information

_No response_
Repository: flutter
Issue: Consider splitting generated Dart plugin registrant by platform
Labels: c: new feature,tool,customer: penguin,P3,a: plugins,team-tool,triaged-tool

Currently for all platforms except web we are generating a single generated Dart plugin registrant file, with a bunch of `Platform` checks in it to decide what to register. This means that the Dart side of every platform's implementation is shipped to every platform (due to https://github.com/flutter/flutter/issues/14233). Ideally the tree shaking itself should be fixed, but absent that we may want to optimize this at the generated registrant level by having a different registration file for each platform.

The complexity here is that we currently don't have all the implementation we need at the compilation step to know what to target; we're currently using file existence, which is somewhat fragile, and wouldn't scale here. We'd need to figure out if we could plumb things all the way through to make sure we are using the correct file in each compilation invocation (even in complex scenarios like hot reload or hot restart when running simultaneously on multiple devices).

It may never be worth doing this, since the Dart side of plugins is probably not all that much code in the grand scheme of things, but filing for tracking to consolidate any discussion about this.

/cc @gaaclarke
Repository: TypeScript
Issue: Argument becomes implicit any when a void-returning overload follows a non-void-returning signature
Labels: Suggestion,Needs Proposal

# Bug Report

### 🔎 Search Terms

overload argument type signature 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about overloads (and #48077)

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/CYUwxgNghgTiAEYD2A7AzgF3gSwwLngG8AoeM+ACgxEwIoEp4BeAPngAUYkBbbNEADwA3JNmAt6BEWIDcpclRr5K2FAAcArsswxVAc0at404JOOjgcgL7FiuChVWaMhtiXI51WgHQYkAVTU1EBgAYSh+Bmt6OTsMCgiATxQwSlcieTIAeiz4b29iKxjiIA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
declare const it: {
    (test: () => Promise<void>): void;
    (test: (input: string) => void): void;
}

it((input) => {
    input.toUpperCase();
});

it(async () => {
    // ..
});
```

### 🙁 Actual behavior

```
Error: Parameter 'input' implicitly has an 'any' type.
```

### 🙂 Expected behavior

No type error. The `input` parameter is type `string` and should be resolved as such.

For more context, see https://github.com/DefinitelyTyped/DefinitelyTyped/pull/59075.
Repository: godot
Issue: GDExtension: stack smashing detected when accessing Texture2D/Image loaded by ResourceLoader
Labels: bug,confirmed,needs testing,topic:gdextension,crash

### Godot version

v4.0.alpha.custom_build [1c91d0979]

### System information

Ubuntu 22.04

### Issue description

Loading any Texture2D from a GDExtension class with ResourceLoader then trying to call Texture2D or Image functions causes aborts due to stack smashing protection:
```

#include <godot_cpp/classes/image.hpp>
#include <godot_cpp/classes/resource_loader.hpp>
#include <godot_cpp/classes/texture2d.hpp>

void GameSpace::_ready()
{
    Super::_ready();

    auto rl            = godot::ResourceLoader::get_singleton();
    auto resource_path = "res://icon.png";
    auto image_texture = godot::Ref<godot::Texture2D>(rl->load(resource_path));
    assert(image_texture.is_valid());

    auto image = godot::Ref<godot::Image>(image_texture->get_image());
    assert(image.is_valid());

    std::cout << image->get_width() << std::endl;          // <- *** stack smashing detected ***: terminated
    std::cout << image_texture->get_width() << std::endl;  // <- *** stack smashing detected ***: terminated
}

```

backtrace here:
[gdb.txt](https://github.com/godotengine/godot/files/8172283/gdb.txt)

godot4, godot-cpp and bindings and freshly updated and rebuilt.

I'm manually creating godot::Image and godot::ImageTexture elsewhere and those can be accessed just fine. 


### Steps to reproduce

- Add above code to any class of a GDExtension project.
- build debug/release_debug
- run app

Output:
*** stack smashing detected ***: terminated


### Minimal reproduction project

_No response_
Repository: pytorch
Issue: test_broadcast_coalesced_nccl fails on A100 GPUs
Labels: oncall: distributed,triaged,module: c10d

### 🐛 Describe the bug

This test fails consistently on A100s - results in this output: https://gist.github.com/rohan-varma/eb893076e5721099c20746f26d99b97f

To reproduce, build pytorch and run the following:

```
srun -p dev -t 10:00:00 --gpus-per-node 2 --cpus-per-task 8 python test/distributed/test_c10d_nccl.py CommTest.test_broadcast_coalesced_nccl
```

### Versions

main

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: flutter
Issue: Remove Usages of Android's Configuration.locale
Labels: platform-android,engine,P2,c: tech-debt,team-android,triaged-android

The [`Configuration.locale`](https://developer.android.com/reference/android/content/res/Configuration#locale) field was deprecated in API 24. The usages of it in the engine should be replaced with [`Configuration#getLocales()`](https://developer.android.com/reference/android/content/res/Configuration#getLocales()) and [`Configuration#setLocales(...)`](https://developer.android.com/reference/android/content/res/Configuration#setLocales(android.os.LocaleList)) for API 24+.

Part of [#98602](https://github.com/flutter/flutter/issues/98602).
Repository: PowerToys
Issue: Different fancy zones layouts when connected to different display configurations
Labels: Idea-Enhancement,Product-FancyZones

### Description of the new feature / enhancement

Would be great if one could define different fancy zones for different displays. 

### Scenario when this would be used?

E.g., when using a laptop and a display at home, and just the laptop display outsides, Kind of annoying to mannually change the fancy zones when switching displays.

### Supporting information

_No response_


crutkas notes:
A+B, A+C, A+B+C, layout, if set in that permutation, is set to the monitor layout.  so if A is connected to B, it could have layout 2, then when connected to C, it would have layout 4.