sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: [DevTools Bug] Cannot remove node "612" because no matching node was found in the Store.
Labels: Type: Bug,Status: Unconfirmed,Resolution: Needs More Information,Component: Developer Tools

### Website or app

proprietary

### Repro steps

Overall, testing and refactoring of a component containing a formik wrapped form which includes a fieldarray with yup schema.
Using VS Code to serve the  React js application.

Unable to share the repo / website as it is proprietary.

Task: Logged in to the app to see the form as the specific user role required to see the component, testing yup schema on formik elements touched property to do some custom error connections in the containing component with React Developer Tools open to the Components view with the console also open.  

I was verifying the elements described in the schema file were getting 'touched' and was refining a select in yup schema js file.

Switched one element's schema property from yup.object() to yup.int() triggers the error.  This is a syntax error.  Should be yup.number().  But switching the two causes it all to crash.

 "formik": "^2.2.6",
  "prop-types": "^15.7.2",
  "react": "^17.0.2",
  "react-router-dom": "4.3.1",
  "react-select": "^4.3.0",
  "yup": "^0.26.10"
  "yarn": "^1.13.0",

  "babel-eslint": "^10.1.0",


### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

4.23.0-e28a0db22

### Error message (automated)

Cannot remove node "612" because no matching node was found in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26349:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24415:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24581:14
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:54033:39)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot remove node  because no matching node was found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: go
Issue: cmd/go,x/tools/go/packages: doesn't propagate permission errors (missing from go list -e)
Labels: NeedsInvestigation,Tools

Preface: this is another instance of `go list -e` failing and reporting the error on stderr, and go/packages trying to process stderr intelligently.

Under certain conditions, go/packages will swallow permission errors and return no packages + no error. The bug boils down to the error processing in `golistState.invokeGo`. 

Simple reproducer: https://go.dev/play/p/L53GCKnfxg3
Repository: flutter
Issue: [pigeon] Add ability to delegate data class generation
Labels: c: new feature,package,team-ecosystem,p: pigeon,P3,triaged-ecosystem

We should add the ability to bypass data class generation in Pigeon and allow the data classes to be supplied to it.  This would allow it to interface with classes that are generated with protobufs.  Data classes defined elsewhere can just be declared with a "@DataClass" annotation that tells how to import and serialize the class.  The generated codec will just use those serialize methods.

Example api:
```dart
import 'package:pigeon/pigeon.dart';

@DataClass(
  objcImport: 'foo.pb.h',
  javaImport: 'com.example.Person',
  dartImport: 'foo.pb.dart',
  serializer: 'writeToBuffer',
  deserializer: 'readFromBuffer')
abstract class Person {}

@HostApi()
abstract class Api {
  Person search(String name);
  void store(Person person);
}
```

cc @ajmalk
Repository: rust
Issue: Tracking Issue for sort_floats
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(sort_floats)]`

This is a tracking issue for the `sort_floats` method on `[f32]` and `[f64]`, a convenience method to sort a slice of floats by calling `sort_unstable_by` using `total_cmp`.

### Public API

```rust
impl [f32] {
    pub fn sort_floats(&mut self);
}

impl [f64] {
    pub fn sort_floats(&mut self);
}
```

### Steps / History

- [x] Implementation: #93397
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Open questions

- Should we rename this to `sort`, which would require some additional steps (possibly negative impls for `Ord` on `f32` and `f64`) to avoid a name conflict?
Repository: yt-dlp
Issue: Format Selection Limit Output File Total Size
Labels: enhancement

### Checklist

- [X] I'm reporting a feature request
- [X] I've verified that I'm running yt-dlp version **2022.01.21**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Description

When using format selection with the default format (`-f bestvideo*+bestaudio/best`), I was trying to limit the size of the output file, using this syntax: `-f "bestvideo*[filesize<400M]+bestaudio[filesize<400M]/best[filesize<400M]"`, which works except this limits video and audio individually, but my constraint (for example, I need to upload said output file to somewhere, but can't upload files bigger than 400MB) is on the output file total size, and not on the files (audio+video) making it.

Can we have a format syntax to tell yt-dlp to limit the total output file size? if is it not exactly known (because combining will probably make it smaller by a bit), the approximate size is the sum of the audio and video anyway, and probably (I don't know for sure, if I'm wrong correct me please) this limit is an upper limit (meaning size(audio)+size(video) is always <= size(audio+video)), so even if it's not exact, that's still good as an approximate limit.

If this is currently possible, please let me know how can I do that right now.

Thanks!
Repository: godot
Issue: Yield completed not working for a function with a single yield
Labels: bug,topic:gdscript

### Godot version

v3.4.2.stable.official [45eaa2daf]

### System information

Windows 11

### Issue description

Yielding on a completition seems to be broken when the function has only one empty yield inside. Please have a look on a snipped below for a better understanding.
```
extends Node2D


func _ready():
	print("entered")
	yield(test(), "completed")
	print("passed") # never called


func test():
	yield()
```

**Current behaviour**: _passed_ isn't printed
**Expected behaviour**: _passed_ is printed

This issue doesn't affect Godot 4 though. The following node working as expected.
```
func _ready():
	print("entered")
	await test()
	print("passed") # called

func test():
	await empty()

func empty():
	pass
```

It would be great to have this fixed in 3.* since 4.0 is in alpha 😄 

### Steps to reproduce

Run a node with a code from description.

### Minimal reproduction project

[test.zip](https://github.com/godotengine/godot/files/7954384/test.zip)
Repository: pytorch
Issue: Multivariate normal defined by eigendecomposition 
Labels: module: distributions,triaged

### 🚀 The feature, motivation and pitch

I've been doing some work where I've had to construct covariance matrices from eigendecompositions e.g. I have a matrix that is _almost_ the covariance matrix I want, but it is has some bad eigenvalues (negative, too big etc). I regularise the spectrum by some process, and then I have the eigenvectors and eigenvalues of the final covariance matrix.

I appreciate this might be a bit niche, but to get this working in my case I had to make a custom distribution that is very similar to `torch.distributions.MutlivariateNormal` but can accept a covariance matrix specified by its eigendecomposition.

I already have this implemented locally, so happy to open a PR if it's the sort of thing that would be appreciated in the official library.

### Alternatives

I tried just computing the covariance matrix and passing that in, i.e.

```
covariance = eigenvectors @ torch.diag(eigenvalues) @ eigenvectors.T
mvn = torch.distributions.MultivariateNormal(loc=loc, covariance_matrix= covariance)
```

but this is prone to numerical issues in precisely the sort of case I am considering: when the spectrum may contain very small eigenvalues, the cholesky decomposition fails due to non-PSD errors. There may or may not be cunning numerical ways around this issue, but it seems safest to just work with eigendecomposition if one already has it.

### Additional context

_No response_

cc @fritzo @neerajprad @alicanb @nikitaved
Repository: rust
Issue: Intra-doc links do not support disambiguating methods overloaded with generics
Labels: T-rustdoc,C-enhancement,A-intra-doc-links

Hello all! I couldn't find any tickets that discuss this problem, so hopefully this isn't a duplicate report.

I'm experimenting with the [typestate pattern](http://cliffle.com/blog/rust-typestate/), where I'm using it in a builder to cascade a series of transformations. Here's a simple version:

```rust
pub trait State {}

pub struct Add;
impl State for Add {}

pub struct Mul;
impl State for Mul {}

pub struct Calculator<T: State = Add> { value: usize, _state: T }

impl Calculator {
    pub fn new() -> Calculator<Add> {
        Calculator { value: 0, _state: Add }
    }

    pub fn add_1(mut self) -> Self {
        self.value += 1;
        self
    }

    pub fn next(self) -> Calculator<Mul> {
        Calculator { value: self.value, _state: Mul }
    }

    /// See [Calculator<Mul>::done].
    pub fn done(self) -> usize {
        self.next().done()
    }
}

impl Calculator<Mul> {
    pub fn multiply_2(mut self) -> Self {
        self.value *= 2;
        self
    }

    /// I'm done.
    pub fn done(self) -> usize {
        self.value
    }
}
```

It seems though that rustdoc does not handle overloading the name particularly well. When running `cargo doc`, the documentation for the `Calculator<Add>::done()` just links to itself, rather than the doc on `Calculator<Mul>::done()`. I'm guessing it's just stripping out the type parameter and linking to the first entry.

I expected to see this happen:

I hoped that we could link to the doc comment on the overloaded method

Instead, this happened:

rustdoc linked to the first method's comment.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.58.0 (02072b482 2022-01-11)
binary: rustc
commit-hash: 02072b482a8b5357f7fb5e5637444ae30e423c40
commit-date: 2022-01-11
host: x86_64-apple-darwin
release: 1.58.0
LLVM version: 13.0.0
```
Repository: vscode
Issue: editor.actions.findWithArgs 'findInSelection' false doesn't work on an already opened Find Widget
Labels: bug,editor-find

<!-- ⚠️⚠️ 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

Start with these keybindings:

```jsonc
{
  "key": "ctrl+f",                        // any keybinding
  "command": "editor.actions.findWithArgs",
  "args": {
    "findInSelection": false,    // only works if Find Widget is not visible
    "isRegex": false,               // works whether the Find Widget is visible initially or not
    "searchString": "not in selection"       // just so it is obvious
  }
},

{
  "key": "ctrl+h",
  "command": "editor.actions.findWithArgs",
  "args": {
    "findInSelection": true,  // always works (if there is a selection)
    "isRegex": true              // always works 
    "searchString": "in selection"
  }
}
```
Now if the Find Widget is not showing, either of these commands will correctly set the `findInSelection` and the `isRegex` options.

But if the Find Widget is already showing, the `findInSelection` `false` will not work.  `findInSelection` `true` does work.

And even if the Find Widget is already showing, `isRegex` true or false works as expected.

So, if the Find Widget is already showing, `findInSelection` `true` works as expected, `findInSelection` `false` does not.

--------------

Version: 1.64.0-insider (user setup)
Commit: 3dda6ea7acb66ea8693032fe9631ccac629da770
Date: 2022-01-27T05:15:00.564Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000
Repository: godot
Issue: Code folding icon is blurry at high editor font sizes (CodeEdit regression)
Labels: discussion,topic:editor,confirmed,regression,topic:gui

### Godot version

4.0alpha1

### System information

Windows 10, GLES3,  NVIDIA Quadro P2000

### Issue description

![blurry](https://user-images.githubusercontent.com/80684394/151466431-dbfe802c-f105-4e3d-b3b0-f54aebb9197e.png)
The code-folding icon is a bit blurry compared to 3.x versions. Code font size is 18 in both screenshots, the upper one is 3.4.2 and 4.0alpha1 is below. It gets even worse the bigger number you set the code font size(image below). It doesn't happen in 3.4.2 stable. 

![worse](https://user-images.githubusercontent.com/80684394/151468373-b75fc156-ff25-4056-b106-638885ac6e58.png)

I guess it's because Godot 4.0alpha1 uses a bigger sprite on it? I'm unsure if it should be called a bug, but I'm not comfortable with this, and I believe there are some people who think the same way. I'd like it to be fixed, or to have an option to get around rather than just disabling Code Folding.

### Steps to reproduce

You can reproduce the issue by just downloading 3.4.2 and 4.0alpha1 with no settings modified. To be precise, I edited 3.4.2's Text Editor Highlighting in the screenshot, but I don't think it affects the problem in any way

### Minimal reproduction project

_No response_

*Bugsquad edit (keywords for easier searching): collapse*
Repository: angular
Issue: Warn on negated async pipes
Labels: feature,area: compiler,feature: under consideration,compiler: extended diagnostics

### Which @angular/* package(s) are relevant/releated to the feature request?

`@angular/compiler-cli`

### Description

Negating an async pipe in an `*ngIf` thrashes the layout because the pipe emits `null` immediately before checking the condition. This can lead cause unnecessary rendering work and trigger component events which cause XHR's or other work to be done that shouldn't be needed.

```html
<div *ngIf="!(myConditional | async)">
  <!-- ... -->
</div>
```

http://codelyzer.com/rules/template-no-negated-async/

### Proposed solution

We should consider an [extended diagnostic](https://angular.io/extended-diagnostics) to detect and warn the user of this anti-pattern to head-off their confusing and suggest a better alternative.

I'm not entirely sure what that alternative should be, but I imagine there's an easily transformable way of doing this?

### Alternatives considered

N/A
Repository: angular
Issue: Verify all text nodes have an i18n attribute
Labels: feature,area: compiler,feature: under consideration,compiler: extended diagnostics

### Which @angular/* package(s) are relevant/releated to the feature request?

`@angular/compiler-cli`

### Description

In internationalized applications, each piece of text in an Angular template requires the `i18n` attribute. This can contain a description, and there are other `i18n-` attributes which provide localized versions of user-visible text (such as `i18n-title`). The attributes are easy to forget, especially edge cases like `i18n-title`. There should be some kind of conformance check which verifies that all text in an application is marked for internationalization.

### Proposed solution

We could have an extended diagnostic which requires that every message in the compilation is marked for `i18n` and warns / errors for messages missing the relevant attribute. It could also warn on attributes like `title` and suggest `i18n-title` as an alternative.

Since not every app is internationalized, this check probably needs to be off by default, but having a one line config change like:

```diff
  {
    "angularCompilerOptions": {
      "extendedDiagnostics": {
        "checks": {
+         "i18nMessages": "error"
        }
      }
    }
  }
```

Would be a really easy way to make sure no messages fall through the cracks.

We may want some kind of `i18n-ignore` attribute to allow some messages to be skipped. I've seen this happen for debug UI which doesn't typically need to be translated.

### Alternatives considered

There might be a community based solution which is able to do this, but I don't recall any offhand.
Repository: angular
Issue: Validate a11y attributes
Labels: feature,area: compiler,Accessibility,feature: under consideration

### Which @angular/* package(s) are relevant/releated to the feature request?

compiler-cli

### Description

We should have the Angular compiler validate the types for a11y features of the DOM, such as `role` or `aria-*` attributes to make sure they are always set to valid values. This could allow the compiler to error or warn on bad a11y values and help users identify mistakes in their code which can lead to a more accessible experience.

### Proposed solution

This could potentially be done as an extended diagnostic, or possibly through a `*.d.ts` typecheck or other direct compiler integration. I'm not sure which would be more appropriate here.

### Alternatives considered

N/A
Repository: angular
Issue: Warn on `==` / `!=` in templates
Labels: feature,area: compiler,feature: under consideration,compiler: extended diagnostics

### Which @angular/* package(s) are relevant/releated to the feature request?

compiler-cli

### Description

In Angular templates, `==`, `!=`, `===`, and `!==` all map to their JavaScript equivalents. However the JS community has generally standardized on `===` and `!==` as the go to comparison operators, with many tools banning `==` and `!=` outright from codebases. This is because `==` and `!=` have unintuitive type conversion semantics which can be hard to reason about and lead to bugs. We should consider emitting a warning/error for these operators in Angular templates to catch these mistakes immediately and save the developer an hour of debugging.

### Proposed solution

An extended diagnostic could easily identify this case and emit a warning. Users would also be free to configure the diagnostic as a hard error if they desired and truly purge `==` and `!=` from their codebase.

### Alternatives considered

You could expect me to remember not to do this, but that ain't happenin'.
Repository: godot
Issue: Document Spatial gizmos under Viewport with Own World not appearing in the 3D editor
Labels: topic:rendering,topic:editor,documentation,topic:3d

### Godot version

v3.5.beta1.official [b9b23d222]

### System information

Windows 10, Nvidia GTX 750 Ti

### Issue description

I'm not sure if this is intentional by design but im pretty sure its been here for a long time since 3.x. I also couldn't find any similar issues to this one.
When trying to preview a spatial node under a Viewport that has a parent of ViewportContainer, any spatial nodes won't render at all expect their default gizmos.

![CyIqRfD1Hx](https://user-images.githubusercontent.com/16618467/151487048-5ca70fa2-81dc-49a5-8e5b-21bba942b098.png)
The Camera gizmo doesn't render at all.

You can easily workaround this issue by setting up a separate scene with the root node of a Spatial.

### Steps to reproduce

1. Setup a scene like the one in the above image and then click on the root Spatial node of the Viewport.
2. 3D scene looks blank except for the default gizmos.

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Clipboard API parity
Labels: debt,editor-clipboard

Here is a list of clipboard api issues we are currently facing on Web.

* Workaround user permission
  * **Write**
    * Clipboard requests from extensions running in Web worker in Safari not classified by Safari as "in response to a user gesture" and will reject. We turn every `click`/`keydown` to clipboard request and any clipboard write is then classified  as response to a user gesture.
    * Otherwise, use `navigator.clipboard.writeText`
    * Lastly `document.execCommand('copy')`
  * **Read**: `navigator.clipboard.readText`. To avoid prompt for user permission, we don't allow keybinding customizations. 
* Electron API parity #140976, #139761
  * readText/writeText
  * readHTML/writeHTML
  * readRTL/writeRTL
  * readImage/writeImage
  * availableFormats
  * readBuffer/writeBuffer
* Firefox https://github.com/microsoft/vscode/issues/84084#issuecomment-550772159
  * `readText`: only available in Browser extensions
  * `writeText`: available without permission in secure contexts and browser extensions, but only from user-initiated event callbacks
  * `read/write(data: ClipboardItem[])`: available when users have browser preference dom.events.asyncClipboard.dataTransfer set to true
* Copy large text fails #123030.
Repository: pytorch
Issue: from_blob / make_tensor support MemoryFormat
Labels: triaged,module: memory format

### 🚀 The feature, motivation and pitch

Currently, making a tensor from external memory always assumes contiguous NCHW memory, regardless of the memory format set in options.
This means that the incoming memory must be rearranged from an existing memory format (eg. channels last) to channels first and potentially rearranged again to whatever the model input takes.
This design prevents optimisation.

### Alternatives

None that I know of.

### Additional context

_No response_

cc @VitalyFedyunin @jamesr66a
Repository: excalidraw
Issue: Can't change Shapes by number shortcuts
Labels: enhancement

Hello, I'm using Excalidraw well. 😊

However, after changing to the M1 Pro Mac Book recently, I have been experiencing a problem where the keyboard number shortcut didn't work.

Is there a solution related to this?
Repository: godot
Issue: Color picker pick color incorrect output with `Stretch Mode 2d, expand` and `window not with default size`
Labels: bug,topic:gui

### Godot version

3.4.2 stable mono (actually I think it is always like this)

### System information

Winodws 10 / Windows 11, RX580 2048SP GLES3; Linux Mint, RX580SP GLES3, GLES2; 

### Issue description

Console output (partial):

```
ERROR: Index p_x = 1622 is out of bounds (width = 1550).
   at: get_pixel (core/image.cpp:2560)
ERROR: Index p_x = 1729 is out of bounds (width = 1550).
   at: get_pixel (core/image.cpp:2560)
```

### Steps to reproduce

1. Set project stretch mode to 2d, expand
2. Add a color picker
3. Run it
4. Resize the window (increase width, decrease height)
5. Use the picker button to pick screen color

### Minimal reproduction project

[Test.zip](https://github.com/godotengine/godot/files/7957675/Test.zip)