sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: How to use webpack V5+ in yarn start
Labels: issue: proposal,needs triage

### How to use webpack V5 in yarn start
![image](https://user-images.githubusercontent.com/36875951/146172821-893c56dd-a3ab-4da5-962d-9eb538432d83.png)
Repository: vscode
Issue: Notebook File/Cell Sace and Recover Problem
Labels: under-discussion,notebook-undo-redo


Issue Type: <b>Feature Request</b>

Hello, I am using jupyter notebook in VScode, I found it diffcult to reason about what I can recover in the cell or the file; I suppose the controlling logic is confusing; If you guys can make it clearer, it will be a great thing to use notebook in VScode! Thanks a lot

VS Code version: Code 1.63.1 (fe719cd3e5825bf14e14182fddeb88ee8daf044f, 2021-12-14T02:13:54.292Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No


<!-- generated by issue reporter -->
Repository: vscode
Issue: Git - Synchronizing changes stays in loop in VSCODE
Labels: bug,git

Hello,

I got issue with my visual studio code. I want to note that was working couple month ago, but now is not working.

I'm doing change in the file, staging changes and doing commit. But when I click Sync Changes it stays in loop nothing is happening.

When I'm doing git pull or git push from terminal it's working. Only issue in VSCODE.
Repository: rust
Issue: Confusing compiler error for function taking closure returning reference
Labels: A-diagnostics,A-lifetimes,A-closures,T-compiler,D-confusing,D-terse

Compiling the following code:

```Rust
use std::collections::HashMap;

fn unclear_compiler_error(f: &dyn Fn(&i32) -> Option<&i32>) -> i32 {
    242
}

fn main() {
    let map: HashMap<i32, i32> = HashMap::new();

    let f = |p: &i32| match map.get(&p) {
        Some(v) => Some(v),
        _ => None,
    };
    unclear_compiler_error(&f);
}
```

Gives the following output:
```
error[E0308]: mismatched types
  --> src/compiler/main.rs:14:28
   |
14 |     unclear_compiler_error(&f);
   |                            ^^ one type is more general than the other
   |
   = note: expected enum `Option<&i32>`
              found enum `Option<&i32>`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `thing` due to previous error
```

But I think the actual issue is with lifetimes, changing to `Option<i32>` makes it compile.
Repository: flutter
Issue: Add documentation describing how to use the Flutter engine HTTP blocking mechanism.
Labels: d: api docs,c: proposal,P2,team-engine,triaged-engine

Dart uses sockets in order to make its HTTPS requests, which means any enforced HTTPS policies forced by the OS will be ineffective and won't work.

An app can have multiple sources that trigger an HTTP request, many of those we can't control as they can be in a third party library.

Currently we can force HTTPS only connections passing this zone configuration:

```dart
zoneValues: {#flutter.io.allow_http: false},
```

But this isn't documented anywhere and it's deep inside the engine, so this can be changed at any time, so it's not a strong and guaranteed solution.

I this this configuration should be documented and also we should have a higher level mechanism for configuring it.
Repository: go
Issue: net: *TCPConn deadlines missed by more than 25% on NetBSD and OpenBSD
Labels: ExpertNeeded,OS-NetBSD,OS-OpenBSD,NeedsInvestigation

In [CL 366176](https://go.dev/cl/366176) (for #36108), I increased the timeout slop in `net.TestWriteTimeoutFluctuation` and `net.TestReadTimeoutFluctuation` to 33% even for tests with very generous (multiple-second) timeouts. At that scale, that margin of slop should be trivial for even a heavily-loaded builder to hit.

Unfortunately, the NetBSD and OpenBSD builders still do not reliably hit it, even on an `n1` instance that does not appear to be affected by #49209.

Given the other issues we've had with NetBSD and OpenBSD, I suspect a kernel bug. I plan to further raise the slop for those two platforms, narrow it everywhere else, and call it at that without investigating further. However, I suggest that folks who care about these kernels (@bsiegert, @coypoop, @4a6f656c?) may want to look into whether the underlying system calls may be adding unnecessary slop in their timeout handling.

`greplogs --dashboard -md -l -e 'FAIL: TestWriteTimeoutFluctuation' --since=2021-11-23`

[2021-12-13T16:09:22-d198a36/openbsd-amd64-70-n2d](https://build.golang.org/log/c34f8685d020b98377dd4988cd38f0c5bd72267e)
[2021-11-29T19:45:58-f598e29/netbsd-amd64-9_0-n1](https://build.golang.org/log/1a6eb1c220f0fbb0b26b26b4a2ff215e189d942f)
[2021-11-29T16:08:23-a59ab29/openbsd-amd64-68](https://build.golang.org/log/a90772f56ebc1c147542ed28eeee5c81971adf83)
[2021-11-25T00:07:28-f7e34e7/openbsd-amd64-70-n1](https://build.golang.org/log/4031d6c8c90dca526ecede231396f8c7b7ac9ae5)
[2021-11-25T00:07:11-c58243a/openbsd-amd64-70-n1](https://build.golang.org/log/0fdd1387d4c279ef12e85238d0a95274f0410eca)
Repository: vscode
Issue: Notebooks inserts/edits code cell
Labels: debt,smoke-test-failure,notebook

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=147018&view=logs&j=3792f238-f35e-5f82-0dbc-272432d9a0fb&t=07088cf7-fede-5f74-0d50-155edd53af7d&l=73

```
1) VSCode Smoke Tests (Electron)
       Notebooks
         inserts/edits code cell:
     Error: Timeout: get element '.quick-input-widget' after 20 seconds.
      at poll (/Users/runner/work/1/s/test/automation/out/code.js:65:19)
      at async Code.waitForElement (/Users/runner/work/1/s/test/automation/out/code.js:188:16)
      at async QuickInput.waitForQuickInputClosed (/Users/runner/work/1/s/test/automation/out/quickinput.js:28:9)
      at async QuickInput.selectQuickInputElement (/Users/runner/work/1/s/test/automation/out/quickinput.js:37:13)
      at async QuickAccess.runCommand (/Users/runner/work/1/s/test/automation/out/quickaccess.js:84:9)
      at async Notebook.openNotebook (/Users/runner/work/1/s/test/automation/out/notebook.js:15:9)
      at async Context.<anonymous> (out/areas/notebook/notebook.test.js:26:13)

```
Repository: ant-design
Issue: InputField does not increment properly when min is defined as 0.1 (or other decimal)
Labels: Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-d14vj)

### Steps to reproduce
Press the increment arrow in the field

### What is expected?
The value in the input field to increase by 1

### What is actually happening?
The value in the input field increases by 0.1 (or whatever the 'min' is defined as). Pressing the button again increments by 1 as expected

| Environment | Info |
|---|---|
| antd | 4.17.3 |
| React | 17.0.2 |
| System | Windows |
| Browser | Chrome |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: Add "at exit" infrastructure to the CLI
Labels: feat,cli

I think we should add "at exit" infrastructure to our Rust code; we got a bunch of issues that would greatly benefit from it. Otherwise we'd need to add hacks for each of the issues.
Two examples on the top of my head:
- https://github.com/denoland/deno/issues/13007
- https://github.com/denoland/deno/issues/8713
Repository: kubernetes
Issue: Allow wildcards in field selectors
Labels: sig/api-machinery,kind/feature,triage/accepted

Is there a possibility to add wildcards for these queries? For example, trying to run 'kubectl get pods --field-selector metadata.name=common-* -o name -n ns | xargs kubectl delete'. Would help clearing out multiple pods.
Repository: PowerToys
Issue: Warn if "Touch Keyboard and Handwriting Panel Service" is off
Labels: Product-Settings,Area-User Interface,Area-App Compat

From a different issue, when this is disabled, you can't type in a ton of WinUI text boxes.

We should have a warning about this when we detect it, link to help, and a button to reenable

> Same issue v0.51.1 [PowerToysReport_2021-12-15-19-33-42.zip](https://github.com/microsoft/PowerToys/files/7721158/PowerToysReport_2021-12-15-19-33-42.zip)

I solved this issue by re-enabling "Touch Keyboard and Handwriting Panel Service"  and rebooting as suggested in [here](https://github.com/microsoft/terminal/issues/7855) for Terminal.

Maybe relevant for others too.

_Originally posted by @4DEATH in https://github.com/microsoft/PowerToys/issues/14514#issuecomment-994970830_
Repository: rust
Issue: Tracking issue for pref_align_of intrinsic
Labels: T-lang,T-libs-api,C-tracking-issue,A-intrinsics,S-tracking-design-concerns,S-tracking-needs-summary

This intrinsic returns the "preferred" alignment of a type, which can be different from the *minimal* alignment exposed via `mem::align_of`. It is not currently exposed through any wrapper method, but can still be accessed by unstable code using the `intrinsics` or `core_intrinsics` features.

See https://github.com/rust-lang/rust/pull/90877 for why it cannot be removed; the short summary is some code is actually using it. So let's have a place to centralize discussion about the intrinsics. (This is not a regular tracking issue because there is no associated feature gate, but close enough I think.)

It would be good to figure out what the "preferred alignment" actually is used for, e.g. there doesn't seem to be consensus on the question whether it is ever relevant for ABI or UB, or whether it is merely a hint used by the compiler to align some globals more than it has to.
Repository: godot
Issue: Collision not detected when animating monitorable
Labels: bug,topic:physics,regression,topic:animation

### Godot version

3.3.4, 3.4-beta1..3.4.1-rc3

### System information

Windows 10, GLES 3, GTX 2060

### Issue description

Enabling monitorable on an area2d doesn't immediately make it detectable if it is already overlapping with another Area2D. This worked in 3.3.4 if you also set the position(even if it was the same position it already had). On 3.4+ it doesn't work either way.

### Steps to reproduce

- Open the project and run the scene:
  - There are two overlapping Area2d named "Left" and "Right", and an animator. "Left" has `area_entered` connected to a callback
  - Test A: The animator will play an animation turning `Right:monitorable` on and off three times
  - After the animation finished "Passed" will be printed if "Left" emitted `area_entered` and `area_exited` three times each.
  - Test B: The animator will play a second animation setting `Right:position` to the same position it already had and then turning `Right:monitorable` on and off three times
   - After the animation finished "Passed" will be printed if "Left" emitted `area_entered` and `area_exited` three times each
 
 Expected: 
 - When `Right:monitorable` changes from false to true it should trigger `area_entered` on "Left"
 - When `Right:monitorable` changes from true to false it should trigger `area_exited` on "Left"
 Actual:
 - On 3.3.4 Test A fails and Test B works as expected
 - On 3.4+ both tests fail
 
![image](https://user-images.githubusercontent.com/526829/146472386-69bf5075-16fb-46a5-8347-d0ee7b34b8d1.png)

*Note:* a workaround is, instead of toggling `monitoring`, toggling the `disabled` property in the CollisionShape node, which works in all cases for both versions. 
It could be argued that my expectation is wrong, that since the areas never changed from overlapping to non-overlapping and vice-versa, no area_enter/area_exit signals should be emitted, but in that case the behavior would still be inconsistent. I also think that most users will expect that if an area becomes detectable it should be detected in all cases, even if already overlapping.

### Minimal reproduction project

[MonitorableBug2.zip](https://github.com/godotengine/godot/files/7731303/MonitorableBug2.zip)
Repository: vscode
Issue: [Test UI] Support Update
Labels: feature-request,testing

@connor4312 

## Issue Description
With a tool like Pester, there are "BeforeAll" and "AfterAll" statements that run before a test suite. I suppose these are known as fixtures in some other tools.

If one of these fails when running a test, I want to report the status at the suite level (e.g. "Describe") in the tree. However, if someone click run on the individual test, the RunRequest doesn't allow updating the parent suite because it's not in the test list.

If I try to create a new testrunrequest that includes the parents, I end up with a duplicate run and it still doesn't report correctly (I can't peek the error). Example:
```ts
		const include = request.include ?? getTestItems(this.testController.items)

		// add the parent test suites of the included tests so that their status can be updated. This is needed for BeforeAll/AfterAll test updates
		const includeWithParents = include.flatMap(getParents).concat(include)

		const RequestWithParents = new TestRunRequest(
			includeWithParents,
			request.exclude,
			request.profile
		)

		const run = this.testController.createTestRun(RequestWithParents)
```
![image](https://user-images.githubusercontent.com/15258962/146239257-496dd3e0-e2b5-4f53-8393-b14f343356d0.png)

## Implementation
I recommend either adding a switch to `createRunProfile` to include the parents of invoked tests in the runRequest, or make it so that you can createTestRun with a new TestRunRequest.
Repository: rust
Issue: Strange behavior when specializing over a generic trait parameter
Labels: T-compiler,A-specialization,C-bug,requires-nightly,F-specialization

Consider the following code:

```rust
#![feature(min_specialization, never_type)]

pub struct Foo;

pub trait Bar<T>
{
    fn myfunc(&self, _: T);
}

impl<T> Bar<T> for Foo
{
    default fn myfunc(&self, _: T) { println!("default"); }
}

impl Bar<bool> for Foo
{
    fn myfunc(&self, _: bool) { println!("bool"); }
}

// uncommenting the following impl will fix the compiler error
// impl Bar<!> for Foo
// {
//     fn myfunc(&self, _: !) {}
// }

fn main() {
    Foo.myfunc(true);
    Foo.myfunc(42);
}
```

The compiler errors with 

```
error[E0308]: mismatched types
  --> src/main.rs:28:16
   |
28 |     Foo.myfunc(42);
   |                ^^ expected `bool`, found integer

For more information about this error, try `rustc --explain E0308`.
```

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=5b161930612fbcee70a522948c6a1fb6

I would have expected that `Foo.myfunc(42)` falls back to the default implementation. The weird thing is, if I uncomment the second special implementation for any other type (e.g. `!`) the code all of a sudden compiles and works as expected.

So I have A = `(T, Foo)`, B = `(bool, Foo)` and C = `(!, Foo)`, where B and C do not overlap and are both subsets of A. Why do I need the specialization C to get the specialization B to work, when C is completely independent of B?

_Originally posted by @joergbrech in https://github.com/rust-lang/rust/issues/31844#issuecomment-994983430 and https://users.rust-lang.org/t/specialization-over-generic-trait-parameter/68838_
Repository: pytorch
Issue: Docs for torch.nn.MSELoss are confusing
Labels: module: docs,module: nn,module: loss,triaged,Stale

### 📚 The doc issue

The documentation for the `reduce` parameter [says the default is `True` ](https://github.com/pytorch/pytorch/blob/master/torch/nn/modules/loss.py#L503 )but the function signature [says it's `None`](https://github.com/pytorch/pytorch/blob/c6bcfb152da93fc29e04c6dd32bfe5a311140711/torch/nn/modules/loss.py#L525). The documentation likely needs to be updated

### Suggest a potential alternative/fix

The default value for the reduce parameter should be changed to `None` in the documentation.

cc @brianjo @mruberry @albanD @jbschlosser @walterddr @kshitij12345
Repository: rust
Issue: Unable to link rust static lib to C code on 1.57.0
Labels: A-linkage,O-windows,C-bug

<!--
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.
-->

I am working on [ccextractor](https://github.com/CCExtractor/ccextractor/), and recently the tests failed on rustc 1.57.0, with the error:-
```
"D:\a\ccextractor\ccextractor\windows\ccextractor.sln" (default target) (1) ->
"D:\a\ccextractor\ccextractor\windows\ccextractor.vcxproj" (default target) (2) ->
(Link target) -> 
  ccx_rust.lib(std-f87c887dcbebcf7e.std.06878a67-cgu.0.rcgu.o) : error LNK2019: unresolved external symbol __imp_BCryptGenRandom referenced in function _ZN3std6thread5local4fast12Key$LT$T$GT$14try_initialize17h6f0eaa92973cfc73E [D:\a\ccextractor\ccextractor\windows\ccextractor.vcxproj]
  D:\a\ccextractor\ccextractor\windows\x64\Release\ccextractorwin.exe : fatal error LNK1120: 1 unresolved externals [D:\a\ccextractor\ccextractor\windows\ccextractor.vcxproj]
```
Error relates to an undefined symbol `__imp_BCryptGenRandom` referenced in `std:: thread::localfastkey::try_initialize`
 Switching to rustc 1.56.0 or below does not cause any errors

[Here ](https://github.com/CCExtractor/ccextractor/runs/4422483428?check_suite_focus=true)are the logs for 1.57.0 test run, and [here ](https://github.com/CCExtractor/ccextractor/runs/4537075744?check_suite_focus=true)for 1.56.0 test run.

Looking into the static libraries, only the lib built with 1.57.0 has the symbol specified in the error
```
C:\ccextractor>dumpbin /symbols ccx_rust_1-56.lib | FIND "BCrypt"

C:\ccextractor>dumpbin /symbols ccx_rust_1-57.lib | FIND "BCrypt"
3283 00000000 UNDEF  notype       External     | __imp_BCryptGenRandom
```
Repository: flutter
Issue: [flutter_conductor] conductor start can fail if there are non-tagged commits at tip of release branch
Labels: P1,team-release

Such as:

```
Attempt to cherrypick trunkRevision: 6ab00756a8e30f71f0dc30b1f12333479e7f2757
state: PENDING
 succeeded
Exception: 2.8.0-1-g2ef5ad67fe cannot be parsed
```

The commit in question is https://github.com/flutter/flutter/commit/2ef5ad67fefb883d830b02fc59f5bac5443fc782, which is not tagged, because it was an infra-only commit, which is reasonable. Although this can be worked around with `conductor start --force`, the tool is overly-aggressively failing, and this constraint should be relaxed, and allow for non-tagged commits at the tip of a branch.
Repository: flutter
Issue: Support a variable number of workers in fml::ConcurrentMessageLoop.
Labels: c: new feature,engine,P3,team-engine,triaged-engine

Today, this is capped to available device concurrency. But, if there are use-cases that require a potentially unbounded number of threads to be created, this support can be added. This issue can be used to list those use-cases to evaluate if this task must be attemted.
Repository: flutter
Issue: Fix warnings in the Android embedding
Labels: team,platform-android,engine,P2,team-android,triaged-android

This clutter is making it harder to see new warnings added in a PR, and thus defeating the purpose of having a linter.

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8827824836836510401/+/u/android_lint/dart_bin_main.dart/stdout?format=raw
Repository: flutter
Issue: Issues should not be displayed as an xcode result issue.
Labels: platform-ios,tool,P3,team-ios,triaged-ios

**This issue is intended to track a list of errors or warnings that are intentionally not logged on console during an xcode build. Please do not close.**

When xcode build fails, we parse the result bundle and display the issues in the bundle. (Original discussion [here](https://github.com/flutter/flutter/issues/22536#issuecomment-700292646))
There are certain issues we ignore to make the output cleaner. This github issue tracks all the ignored issues:

- [x] All warnings. (There are many warnings not relevant to flutter devs, they still show in -v mode)
- [x] `Command PhaseScriptExecution failed with a nonzero exit code`. (Happens every time when there's a dart compilation issue)
Repository: go
Issue: x/build/cmd/gerritbot: uses too much GitHub quota
Labels: Builders,NeedsInvestigation

gerritbot makes GitHub API requests for each open PR. There are enough open PRs across all the Go repositories that each gerritbot restart consumes most (maybe all?) of our 5000 requests per hour.

In response, today I closed all the PRs that were opened more than a year ago. This has had the effect of annoying a number of people and probably is not a tenable plan long-term. It seems we'll have to figure out a way to avoid looking at unmodified PRs that works across restarts.
Repository: storybook
Issue: Can't use storyStoreV7 with Flow
Labels: bug,core

**Describe the bug**

It seems like `storyStoreV7` depends on this `babelParse` utility that has a hardcoded configuration:

https://github.com/storybookjs/storybook/blob/cf4b3c77bad29c941b91620bcf84aeb79cbb33c9/lib/csf-tools/src/babelParse.ts#L6-L12

Because of this, Flow-specific syntax cannot be supported without getting a parser error from babel. I've confirmed that if I replace `typescript` with `flow` in the above code, I no longer get the parser error.

**To Reproduce**

Run storybook with any story files using flow-specific syntax.

**System**

```
Environment Info:

  System:
    OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
  Binaries:
    Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
    Yarn: 1.22.15 - ~/dev/elastic/scramble-com/node_modules/.bin/yarn
    npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
  Browsers:
    Chrome: 68.0.3440.75
    Firefox: 95.0
  npmPackages:
    @storybook/addon-actions: 6.4.9 => 6.4.9 
    @storybook/addon-essentials: 6.4.9 => 6.4.9 
    @storybook/addon-knobs: 6.3.1 => 6.3.1 
    @storybook/addon-options: ^5.3.21 => 5.3.21 
    @storybook/addons: 6.4.9 => 6.4.9 
    @storybook/builder-webpack5: 6.4.9 => 6.4.9 
    @storybook/manager-webpack5: 6.4.9 => 6.4.9 
    @storybook/react: 6.4.9 => 6.4.9 
    @storybook/theming: 6.4.9 => 6.4.9 
```

**Additional context**
N/A
Repository: terminal
Issue: Stop global installation workaround for PGO Nuget package
Labels: Area-Build,Product-Meta,Issue-Task

Following up from #11819, we need to remove the workaround when the PGO Nuget package updates to fix the path resolution. (See https://github.com/microsoft/terminal/pull/11819#discussion_r761558613) I'm waiting on @dkbennett to fix up the package. He's working on it.