sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: windows build start failed on main caused by MSVC update
Labels: windows,build

** TLDR **
MSVC don't care about this issue. nothing to do on our side

<del>
**TLDR:  Please upvote this MSVC issue to help us resolve this issue.**

**https://developercommunity.visualstudio.com/t/build-failed-on-Nodejs-introduced-in-17/10201632**
</del>


## Details

works good:

https://github.com/nodejs/node/runs/6376797643?check_suite_focus=true
Visual Studio: 17.1.32[42](https://github.com/nodejs/node/runs/6376797643?check_suite_focus=true#step:5:42)1.90 (Visual Studio Enterprise 2022)


failed:
https://github.com/nodejs/node/runs/6428804600?check_suite_focus=true

Visual Studio: 17.2.32505.173 (Visual Studio Enterprise 2022)

I don't know it's a new bug or MSVC introduced a braking change.


cc @nodejs/build @nodejs/actions 


also we have https://github.com/nodejs/node/issues/42560 pending on MSVC side to fix.
Repository: create-react-app
Issue: Updated version of webpack and Create-react-app
Labels: needs triage,issue: bug report


I recently stumbled on to this error while running npm start. its could be from updated version of webpack or create-react-app probably I don't really. Please take a look at the error i got below; 
 
`There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

  "babel-jest": "^26.6.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-jest was detected higher up in the tree:`
Repository: vscode
Issue: Bracket Pair Guides overlap non-indented text
Labels: feature-request,bracket-pair-guides

When using Bracket Pair Guides, generally there is plenty of room between the guide and the first character of each line, since typically this text will be indented with whitespace. But if there is no indentation, the guides are uncomfortably close to the text, and in some cases actually overlap it, hindering readability. It would be nice if the guides were offset to the left a bit to ensure there is at least a one-pixel column of background between the guide and text. Either that (or in conjunction) the following options would help, too:

- An option to hide column-0 guides altogether. Almost all cpp files I work with have a `namespace` bracket for the entire file, so that guide is less than helpful.
- An option to hide a guide if any of the block's lines are not indented relative to the brackets

<img alt="screenshot" src="https://user-images.githubusercontent.com/12552462/168413334-4f5f6c98-0ad8-4bc2-9d11-966ba5295c7b.png">

<img alt="zoomed" src="https://user-images.githubusercontent.com/12552462/168413337-6ef3bed4-c5ee-4bc7-a19e-13bd78cb5b80.png">


vscode info:
```
Version: 1.67.1
Commit: da15b6fd3ef856477bf6f4fb29ba1b7af717770d
Date: 2022-05-06T12:37:14.619Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin arm64 21.4.0
```

system info:
```
Model Identifier: MacBookPro18,1
System Version: macOS 12.3.1 (21E258)
Kernel Version: Darwin 21.4.0
```
Repository: pytorch
Issue: Standalone unittests for checkpoint_wrapper
Labels: oncall: distributed,module: bootcamp,triaged,better-engineering,module: fsdp

### 🚀 The feature, motivation and pitch

New features to checkpoint_wrapper are being added such as in https://github.com/pytorch/pytorch/pull/77224, but the file is missing standalone unittests and is instead mostly tested through FSDP (`test_fsdp_checkpoint` and `test_fsdp_state_dict`). To ensure more robust support, we should have standalone unittests independent of FSDP.

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: vscode
Issue: caret, tick, backtick and diaeresis can't be written. 
Labels: bug,linux,editor-input,editor-input-IME

<!-- ⚠️⚠️ 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.67.1
- OS Version: Ubuntu 20.04.4 LTS 

Steps to Reproduce:

1. Configure your keyboard with Spanish layout
2. launch vscode with gtk input method xim. `GTK_IM_MODULE="xim" code`
3. try to write any of the following characters `^`, `` ` ``, `´`, `á`,`é`,`í`,`ó`, `ú`, `ü`, etc...

The reason to use xim input method is due to (https://github.com/Microsoft/vscode/issues/48480#issuecomment-413793736). launching vscode with ibus or using a different keyboard layout makes those character tp work fine, but then some keyboard shorcut stop working. 

Also, it seems that this issue affects only vscode, since launching other gtk applications (such as gnome-calculator) with input method "xim" doesn't make those character to fail.
Repository: react
Issue: [Recomendation/Discussion]: Hook-based Context API
Labels: Type: Enhancement,Status: Unconfirmed

I would like to say that I'm impressed with how React hooks have revolutionized the React ecosystem, and the Context API. However, I see some major inconsistencies between how the context is read from, and how it is provided. Maybe we we could use a `useProvider(Context, ()=>expr, [deps, ...])` kind of hook (similar to the Vue `provide()` function)?
```js
const IsGuest = createContext(true)

const Status = () => {
  const isGuest = useContext(IsGuest)
  return <span class="status"> {isGuest} </span>
}

const App = () => {
  const [isLoggedIn, setIsLoggedIn] = useState(false)
  useProvider(isGuest, ()=>!isLoggedIn, [isLoggedIn])
  return <Status/>
}
```

Or maybe a more object-oriented approach?
```js
const IsGuest = createContext(true)

const Status = () => {
  const isGuest = IsGuest.useContext() // 👈
  return <span class="status"> {isGuest} </span>
}

const App = () => {
  const [isLoggedIn, setIsLoggedIn] = useState(false)
  IsGuest.useProvider(()=>!isLoggedIn, [isLoggedIn]) // 👈
  return <Status/>
}
```

I would like to hear what you all think about this. If you all think the former syntax was preferred, then the `createContext()` function could be removed entirely and replaced with the native `Symbol` constructor.
Repository: go
Issue: proxy.golang.org: Make 302 Redirect to Google Cloud Storage Explicit
Labels: Documentation,NeedsInvestigation,proxy.golang.org

Hello,

Sometimes the proxy will redirect to Google Cloud Storage for archive downloads.

As mentioned here: https://github.com/golang/go/issues/33928

This issue is no biggie. But having looked around the documentation I can not find any reference to the proxy working like this. Given that this is a technical tooling system and not a general consumer service I think the dependency on the external service should be made explicit somewhere.

Certain environments (including the Go Teams own development environments from linked issue) require domain allowlists and this information would help in those cases.

Looking around the internet at various sources of how the go proxy and module downloading works there is not general knowledge of the redirect part of the system.
Repository: neovim
Issue: API: nested extmarks tree with attached data
Labels: enhancement,api,needs:design,marks,highlight



### Feature description

I can see how the related machinery behind `nvim_buf_add_highlight` can be vastly generalised to something like this:
We attach arbitrary tree-like information to source-code ranges. This information can be, for example, a partially 
type-checked AST of the source-code language with zero semantic ambiguity.
The information gets carried over when the user relocates the relevant source code and partially invalidated when the user inserts a new character into the range or deletes a character from the range (this is already present in the current machinery). By choosing a tree-like structure whose sub-nodes get mapped to sub-ranges of the parent's range we can
pinpoint furthest sub-nodes that should be invalidated when the user performs a "discontinuous deformation" of the said range (inserting into it/deleting from it)

It opens up possibilities like visual-boilerplate-free disambiguation or *truly* incremental tooling: when the user modifies the source code we can instantaneously compute the impacted AST nodes in turn issuing a request to the backend that would compute the smallest set of re-checking/evaluation/etc. that it has to do.
Repository: TypeScript
Issue: In-line chained .then to map an array causes weird behavior with the Map constructor
Labels: Bug

# Bug Report

### 🔎 Search Terms
map, map constructor, promise, then, await

### 🕗 Version & Regression Information
- This changed between versions 4.5.5 and 4.6.2

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.6.2#code/JYOwLgpgTgZghgYwgAgCJzHZBvAUMg5YAEwC5kBnMKUAcwG5cBfXXOCgTxAWRgFduYYAHsQvEAAoAlOQAKUYQFtgFCAB50mANoBdAHw58hKBDB8oY3Yxa4EoqskVwADsgC8yEBADuyALIuEkYEcN5wwGDi0gB0YAAWEJISxBhwUu4GKZjRTs7JGchaxNEkADTIxDpSUrhSjLgA9A28wlDIYMLOALQANhAAbhA9XaHhYLgQAB7OrZHYTIxAA)

### 💻 Code

```ts
interface Data {
    id: string;
}

async function fn(): Promise<Data[]> {
    return [];
}

const map = new Map(
    await fn().then((data) => data.map(d => [d.id, d]))
);

// for top-level-await
export {};
```

### 🙁 Actual behavior
`map` has a type of `Map<unknown, unknown>`, incorrectly inferring `Map<string, Data>`.

Interestingly enough, if we were to do
```ts
const intermediate = await fn().then((data) => data.map((d): [string, Data] => [d.id, d]));
const map = new Map(intermediate);
```

the type is inferred correctly. It should also be noted that this issue also doesn't occur when we're not dealing with promises, for example:
```ts
function fn(): Data[] {
    return [];
}

const map = new Map(fn().map(d => [d.id, d]);
```

also works as intended

### 🙂 Expected behavior

`map`'s type is correctly inferred to `Map<string, Data>`
Repository: flutter
Issue: [Desktop-Windows]Chinese characters are incorrectly rendered in flutter 3
Labels: c: regression,engine,a: internationalization,platform-windows,a: typography,customer: crowd,a: desktop,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-windows,triaged-windows

Chinese font flutter 3.0.0 Desktop-Windows
![QQ截图20220514235906destop2](https://user-images.githubusercontent.com/7413008/168432499-ac1a22cd-8abb-44b6-a587-8972c2f1cd17.jpg)

Chinese font on flutter 2.10.5 Desktop-Windows
![QQ截图20220514235727desktop1](https://user-images.githubusercontent.com/7413008/168432594-5e3d1bac-562c-4ccd-a0a9-671e6989fd3f.jpg)

This is a desktop specific issue.(this is good on web)  flutter 3.0.0 web
![QQ截图20220514235811web1](https://user-images.githubusercontent.com/7413008/168432751-f7916f07-ac63-449a-8ef1-dcd0176589b3.jpg)
Repository: TypeScript
Issue: Type erroneously widened for property access after for loop when using comma operator
Labels: Bug

# Bug Report

This is somewhat a continuation of #41625. I found a case where the control flow breaks when using an if block to narrow a type, using a for loop inside that if block, and then accessing the object which should work due to the if-check, all while using a comma operator.

~This may seem like an edge case but we need this in our Svelte->TS transformation for intellisense when using stores (https://github.com/sveltejs/language-tools/issues/1475)~ Update: We no longer depend on using the comma operator, so this issue isn't high priority for us anymore.

### 🔎 Search Terms

comma operator for loop type narrowing

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about type narrowing

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.8.0-dev.20220514&ssl=10&ssc=1&pln=1&pc=1#code/DYUwLgBAZg9jEF4IAoCUiB8EDeBfA3AFCiQBGAhgE4BcOE5A-LdhKUxAM5iUCWAdgHMIuYYgh8ArsGD0O9PgE8ihHlBTJYMNABpWVVAwB0jQ6XTZCASA1wdeyqmOn8EAPSv6AY08gOcgO4wlADWHFawlCieMHxc9BAwagDaALrmVrhWNlqouhQOTqQu7l4+ftDkPMAcuhwAFjBSACYQgSGEmUA)

### 💻 Code

```ts
let foo = () => {};
let bar: { a?: { b?: string } } = null as any;

if ((foo(), bar)?.a?.b) {
	(foo(), bar).a.b; // access works
	for (const a of []) {
	}
	(foo(), bar).a.b; // access fails, should work
}
```

### 🙁 Actual behavior

Property access after for loop fails with a "could be undefined" type error.

### 🙂 Expected behavior

Control flow isn't affected by for loop.
Repository: TypeScript
Issue: `.length` property of function literals is not `readonly`
Labels: Bug,Help Wanted

# Bug Report

Function `.length` property is inconsistently `readonly` depending on whether `Function` constructor is used or not.

### 🔎 Search Terms

function length readonly

### 🕗 Version & Regression Information

v4.6.2 (haven't checked older versions)

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/MYewdgzgLgBAZjAvDMBTA7jAYgVzMKAS3AAoBKAKDgDoAbVMAcygAskYBGCi0SWOAEztySAHwwA3gF8qAug2ZtkXIA)

### 💻 Code

```ts
const f = new Function()
f.length = 1 // Error here: Cannot assign to 'length' because it is a read-only property.

const f2 = () => {}
f2.length = 1 // No error here
```

### 🙁 Actual behavior

The `length` property of the function created with `new Function()` is `readonly` while the `length` property of function literals is not.

### 🙂 Expected behavior

Both `length` properties should be `readonly`. Alternative both could be non-`readonly` but that seems worse since JS doesn't modify the length when assigning a value.
Repository: opencv
Issue: HoughLines: min_theta behavior
Labels: category: imgproc,needs investigation

The behavior of `min_theta` in the function `HoughLines` seems to be wrong, at least in the python opencv library that I refer to in this issue. The problem is that `min_theta` needs to be too low for my opinion, as otherwise lines won't get detected.

##### System information (version)

- OpenCV => 4.5.5
- Operating System / Platform => Arch Linux 64-bit
- Python => 3.10.4

##### Detailed description

Horizontal lines can only be detected if the `min_theta` is less or equal 0.0001. The expected behavior would be, that `min_theta` can get as large as pi / 2 minus a sufficient tolerance.

##### Steps to reproduce

```python3
import cv2 as cv
import math

img = cv.imread('houghlines_test.png', cv.IMREAD_GRAYSCALE)
lines = cv.HoughLines(img, 1, math.pi/180, 90, min_theta=0.0001, max_theta=1.58)
print(lines)
lines = cv.HoughLines(img, 1, math.pi/180, 90, min_theta=0.001, max_theta=1.58)
print(lines)
```

houghlines_test.png:
![houghlines_test](https://user-images.githubusercontent.com/890634/168444388-6b2e6d80-9bfa-43bf-8c6f-131516da857d.png)

Output:
```
[[[100.          1.5708964]]]
None
```

Expected output would be two times the first line.

##### Issue submission checklist

 - [X] I report the issue, it's not a question
 - [X] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found any solution
 - [X] I updated to the latest OpenCV version and the issue is still there
 - [X] There is reproducer code and related data files: videos, images, onnx, etc
Repository: rust
Issue: Better pattern argument naming in rustdoc
Labels: T-rustdoc

I noticed with function pattern arguments that rustdoc makes some interesting choices regarding argument names.

For instance:

```rust
fn func(Foo(bar): Foo) {}
```

gets rustdoc'd into

```rust
fn func(__arg0: Foo) {}
```

(see 
https://docs.rs/atuin-server/0.9.1/atuin_server/handlers/history/fn.calendar.html for a real life version)

It's hard to say what rustdoc should do in the general case, but there are some simple cases that could be improved.

For the single capture pattern, the argument could inherit the name. Eg, in the example above, it could be rendered as `bar: Foo`.

However, this single capture rule should maybe not apply if in a case like

```rust
fn func(Struct { bar, .. }: Struct) {}
```

Since `bar` might be a small subset of what the type is representing, and might be misleading (or implementation detail).

In the general case, the argument name could be a snake case version of the type name, if no conflicts. This is the best heuristic I can come up with for a sensible name
Repository: PowerToys
Issue: Request to add an option to the editor of FancyZones
Labels: Idea-Enhancement,FancyZones-Editor,Product-FancyZones

### Description of the new feature / enhancement

My bluetooth keyboard does not have the Delete key but the Back key, so I cannot delete the anchor without using the Keyboard Manager utility.

### Scenario when this would be used?

Any time.

### Supporting information

_No response_
Repository: vscode
Issue: Bracket colorization w/ semantic tokens
Labels: feature-request,bracket-pair-colorization

<!-- ⚠️⚠️ 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.67.1
- OS Version: n/a

Semantic token providers cannot influence the new bracket colorization. For instance, even if we tell VSCode a comment token is located on a given range, VSCode will still colorize the brackets:

<img width="598" alt="image" src="https://user-images.githubusercontent.com/1037931/168447845-3d78382b-3f3c-4370-8315-ed57b629a16d.png">

The only way to "silence" them is to specify comments, strings, etc within a tmLanguage file, which partially goes against the purpose of semantic tokens. Ideally VSCode should accept something (perhaps a token modifier) which would let us instruct it to disable bracket colorization within the token.
Repository: storybook
Issue: Add helper methods defineStory and defineMeta to enhance typescript support
Labels: feature request,csf

**Is your feature request related to a problem? Please describe**
The existing solution to get typing information is hard to write and gives suboptimal auto-completion support by the IDE. 

**Describe the solution you'd like**
Add the following identity methods
```ts
export function defineMeta(meta: Meta): Meta {
  return meta
}

export function defineStory(story: StoryObj): StoryObj {
  return story
}
```
With these methods, one could define
```ts
export default defineMeta({
  component: TInput,
  title: 't-input',
  args: {
    value: 'Input text',
  },
})

export const Default = defineStory({})
```
instead of 
```ts
export default {
  component: TInput,
  title: 't-input',
  args: {
    value: 'Input text',
  },
} as Meta

export const Default: StoryObj = {}
```


**Describe alternatives you've considered**
Continue using existing explicit type annotations.

**Are you able to assist to bring the feature to reality?**
yes, I can provide a PR introducing these methods.

**Additional context**
This is similar to Vue's `defineComponent` function whose reason for existence is also only to enhance typescript support, see https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#global-api-mapping for a description why it has been added.
See https://github.com/vuejs/core/blob/2a9e9a40963a852238adc4c61b86d0c48e7131fa/packages/runtime-core/src/apiDefineComponent.ts#L86-L89 for details.
Repository: godot
Issue: Black screen in godot
Labels: topic:editor,needs testing

### Godot version

3.2.3 stable, downloaded from custom build

### System information

Chromebook 32 bit (linux)

### Issue description

Been working on a project for a couple of weeks now and after leaving 1 single line of code errored, haven't been able to open any projects, I've seen issues related but resizing the tab does not work and I do not know if any other tabs such as #8302 will help because I am on a Chromebook with Linux installed.
Steps to reproduce:
First, the computer of choice has to crash, the second I don't know if this affects it but a wrong line of code put into place somewhere for me calling a pressed function for the script of a button, once rebooted the application will only work when running code but a black screen appears, whenever you try to edit, restarting the computer from there, will not work. Also, the application was downloaded of linux.

### Steps to reproduce

It did crash the editor with one error line, if I recall correctly the line was a node function to a button for a win title screen before I could change anything my Chromebook crashed and now here we are. In more specifics, I think it was a pressed call.

### Minimal reproduction project
https://docs.google.com/presentation/d/1whbQiX3pMjFsiO2oB6GqW3bGNIf_H5BXnY0qnOY7c-8/edit?usp=sharing
Repository: react
Issue: Bug:  When hydrate <Suspense>, it shows loading forever.
Labels: Type: Bug,Status: Unconfirmed,Component: Server Rendering

After calling `hydrateRoot`, the import() function was not called. It keeps showing loading.

React version: 18.1.0

Link to code example: https://codesandbox.io/embed/gracious-lederberg-nomtf0
(For mocking server side rendering, I write content in `public/index.html`)

## The current behavior
Always showing loading

## The expected behavior
The component should be rendered after finishing loading.