sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: ContentChildren query lags in change detection when wrapped by template
Labels: area: core,state: confirmed,core: queries,core: change detection,core: content projection,P3

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->


# 🐞 bug report

### Affected Package
<!-- Can you pin-point one or more @angular/* packages as the source of the bug? -->
<!-- ✍️edit: --> The issue is caused by package @angular/core probably


### Is this a regression?

<!-- Did this behavior use to work in the previous version? -->
<!-- ✍️--> No, the issue was present at least since version 7


### Description

When your component has `ng-template` in its content for later instantiation and inside that template there's a list of items — you can query those children with `ContentChildren` once you instantiate the template. However change detection in them lags a cycle.


## 🔬 Minimal Reproduction
<!--
Please create and share minimal reproduction of the issue starting with this template: https://stackblitz.com/fork/angular-ivy
-->
<!-- ✍️--> 
https://stackblitz.com/edit/angular-content-children-query-bug

<!--
If StackBlitz is not suitable for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue.
A good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem.
Share the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.

Issues that don't have enough info and can't be reproduced will be closed.

You can read more about issue submission guidelines here: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue
-->

## 🌍  Your Environment

**Angular Version:**
<pre><code>10</code></pre>

**Anything else relevant?**
In the reproduction Stackblitz, type a short string into input. 
This string is then broken into chars and spread into a list of DIVs with a 2 seconds delay.
You can even see that "content checked" is printed to console when the list updates.
However the `QueryList` of children is not refreshed.
Also note that I had to wrap `setInterval` into `runOutsideAngular`. 
Otherwise it would create a tick that refreshes the query, even though both components are `OnPush`.
Repository: flutter
Issue: devfs_test: Add test that shows we do the right thing when an upload fails 10 times
Labels: a: tests,team,tool,P3,team-tool,triaged-tool

There is no case showing what happens when the retry count is depleted.

Relevant files: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/general.shard/devfs_test.dart
Repository: ant-design
Issue: Form's getFieldError not updated inside pure FormItem with dependencies
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-puz3e?file=/index.js)

### Steps to reproduce
1. Start typing in the first "foo" field

### What is expected?
As the "foo" field is updated and validated, I expect the following two FormItem (one via `shouldUpdate={true}` and one via `dependencies={["foo"]}`) to be able to extract that field errors via `getFieldError`.

I expect a pure FormItem with dependencies={["foo"]}  to get re-rendered when "foo" has errors.

### What is actually happening?
Calling `getFieldError("foo")` inside the "shouldUpdate FormItem" renderProps correctly returns the most updated errors for the field.
Calling `getFieldError("foo")` inside the "dependencies FormItem" renderProps does not return the updated errors.  

| Environment | Info |
|---|---|
| antd | 4.7.1 |
| React | 16.13.1 |
| System | macOS 10.14.5 |
| Browser | Chrome 85.0.4183.121 |

---
I've added some renderCounts to each FormItem so we can see that both of them are being called although the "dependencies" one isn't being triggered by the validations.
The use case is being able to build an independent FormItem which renders its own errors in a custom form and don't use "shouldUpdate=true" because we don't want to call that when other FormItems are modified.

This started happening in 4.5.0 by https://github.com/ant-design/ant-design/pull/25408


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: opencv
Issue: numpy_array.reshape(1,-1,2) is often needed in Python
Labels: category: python bindings

##### System information (version)

- OpenCV => 4.x
- Operating System / Platform => any
- Compiler => Python 2.x/3.x

##### Detailed description

When OpenCV functions that processes point a sequence/point cloud is called from Python, it fails to process it because of unsupported shape of array. And so it needs reshape to pass through. If the output of point cloud processing functions is also a point cloud, it also needs to be reshaped in a similar way.

##### Steps to reproduce

```.py
pts = np.array([[10,5],[20,30],[70,20],[50,10]], np.int32)
pts = pts.reshape((-1,1,2))
cv2.polylines(img,[pts],True,(0,255,255))

...
pts = ...
rpts = pts.reshape((1,-1,2))
xfm_pts = cv2.perspectiveTransform(rpts,H).reshape((-1,2))
```

##### References

https://stackoverflow.com/questions/51723910/at-what-situation-points-need-to-be-reshaped-like-reshape-1-1-2-in-python-open/51724120

reported by @garybradski
Repository: flutter
Issue: Add a commit-finder tool
Labels: c: new feature,team,tool,P3,team-tool,triaged-tool

When debugging, we frequently need to answer commit-tracking questions such as:
* given a Dart SDK (or Skia) commit, at which commit did it roll to the engine, at which commit did it make it into the framework? 
* given a commit range in the framework, which engine commits are included? Which Dart commits? Which Skia commits?

We have an internal dashboard that answers the first question, but nothing usable by non-Googler contributors.
Repository: storybook
Issue: Controls are not generated automatically if the component is not SFC (that is not a .vue file).
Labels: question / support,documentation,vue,addon: controls

**Describe the bug**
Controls are generated automatically when a .vue file is used in the story. When an .js file is used (e.g. when a component is just an .js file with render function), no controls are generated.

**To Reproduce**
Steps to reproduce the behavior:

1. `git clone https://github.com/schoonc/test-storybook-addon-controls-vue-non-sfc`
2. `npm i`
3. `npm run storybook`
4. We can see that the controls have been generated.
5. Comment `import MyButton from './MyButton.vue';` and uncomment `import MyButton from './MyButton.js';` in the `stories/MyButton.stories.js`
6. We can see that the controls disappeared.

**Expected behavior**
Controls should be generated if .js files are used.

**Screenshots**
`import MyButton from './MyButton.vue`:
![image](https://user-images.githubusercontent.com/4659633/94178371-ae8fb780-fea3-11ea-8b20-ef50c627687e.png)

`import MyButton from './MyButton.js'`:
![image](https://user-images.githubusercontent.com/4659633/94178414-bcddd380-fea3-11ea-862a-eb8e99f50434.png)


**Code snippets**
dependencies in the package.json:
```
"@storybook/addon-essentials": "6.0.21",
"@storybook/vue": "6.0.21",
"chromatic": "^5.2.0",
"vue": "2.6.12",
"vue-loader": "15.9.3",
"vue-template-compiler": "2.6.12"
```

.storybook/main.js:
```
module.exports = {
  "stories": [
    "../stories/**/*.stories.js"
  ],
  "addons": [
    "@storybook/addon-essentials"
  ]
}
```

stories/MyButton.stories.js:
```
import MyButton from './MyButton.js';
// import MyButton from './MyButton.vue'; // 

export default {
  title: 'MyButton',
  component: MyButton
};

export const Default = (args, { argTypes }) => ({
  props: Object.keys(argTypes),
  components: { MyButton },
  template: '<my-button />'
})
```

stories/MyButton.js:
```
export default {
  props: {
    someProp: Boolean
  },
  render(h) {
    return h('div')
  }
};
```

stories/MyButton.vue:
```
<template>
  <div></div>
</template>

<script>
export default {
  props: {
    someProp: Boolean
  }
};
</script>
```

**System:**
```
Environment Info:

  System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  Binaries:
    Node: 12.18.4 - /usr/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.6 - /usr/bin/npm
  Browsers:
    Chrome: 84.0.4147.125
    Firefox: 80.0.1
```


**Additional context**
vue-docgen-api generates the same scheme for both the .js and the .vue file:

generator.js:
```
var vueDocs = require('vue-docgen-api')
// vueDocs.parse('./MyButton.vue').then(ci => {
vueDocs.parse('./MyButton.js').then(ci => {
  console.log(ci)
})
```

output:
```
{
  exportName: 'default',
  displayName: 'MyButton',
  description: '',
  tags: {},
  props: [ { name: 'someProp', type: [Object] } ],
  events: undefined,
  methods: undefined,
  slots: undefined
}
```
Repository: create-react-app
Issue: My Project Stop Loading
Labels: stale,needs triage

![Anotação 2020-09-24 150442](https://user-images.githubusercontent.com/71350840/94182397-50e57600-fe77-11ea-914a-acc5cb1f8075.png)
 
When I create a new react app my prompt end like this image and stop loading. The last message I have was 'Done in 437.30s'. I've try to create 5 different times. 

Anybody has the same issue?
Repository: create-react-app
Issue: Unable to delete project created with "npx create-react-app"
Labels: stale,needs triage

On windows 10 if I try to run ```rm -r <dir>``` name ```<dir>``` being the name of the react app created via npx, the command fails with permission denied error.

I don't know if its a bug or not, thus asking as question.

Node: 14.12.0
npx: 9.6.0
Repository: pytorch
Issue: Adaptive usage of memory during training inference
Labels: feature,module: nn,module: cuda,triaged,needs research

## 🚀 Feature

Better management of GPU and RAM memory to train CNN models with larger image size.

## Motivation

Find a way to train the model (CNN) with better frame size (720 * 720) on GPUs like the Nvidia K80 by splitting the inference process.

## Pitch

- Save a part, or some parameters of the models on the RAM in order to allow more data to be passed to CNNs.
- Or infer on a batch by cutting it into several small sets so as not to have memory allocation errors.



cc @ngimel @albanD @mruberry
Repository: node
Issue: doc: crypto.sign and crypto.verify string/buffer keys must be pem
Labels: crypto,doc

# 📗 API Reference Docs Problem

<!--

Thank you for wanting to make nodejs.org better!

This template is for issues with the Node.js API
reference documentation.

For problems with nodejs.org beyond the API
reference documentation, please open an issue
using the issue tracker for our site repository.

  https://github.com/nodejs/nodejs.org

For more general support, please open an issue
using the issue tracker for our help repository.

  https://github.com/nodejs/help

---

For the issue title, please enter a one-line
summary after “doc: ” (preferably 50 characters
or less and no more than 72).

The “✍️” are placeholders signifying requests for
input. Replace them with your responses.

If you are unsure of something, do your best.

-->

<!-- The output of “node --version”. -->

- **Version**: v12.16.2

<!-- The output of “uname -a” (UNIX) or version
and 32-bit or 64-bit (Windows). -->

- **Platform**: Darwin Jacobs-MacBook-Pro.local 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64

<!-- The name of affected core module. -->

- **Subsystem**: crypto

## Location

_Section of the site where the content exists_

Affected URL(s):

- https://nodejs.org/api/crypto.html#crypto_crypto_sign_algorithm_data_key
- https://nodejs.org/api/crypto.html#crypto_crypto_verify_algorithm_data_key_signature
- possibly (probably?) others

## Description

_Concise explanation of the problem_

According to the documentation for `crypto.sign` and `crypto.verify`, the `key` argument may be a string, buffer, object, or `KeyObject`. It does not mention that if the key is a string or buffer, it must be `pem` format. Passing a key with `der` format will result in an error `error:0909006C:PEM routines:get_name:no start line`

The source code is quite clear that keys are assumed to be pem. https://github.com/nodejs/node/blob/d6fe46f749bf39f8cb0a9b29f13f34672122c4eb/lib/internal/crypto/keys.js#L277-L280

<!-- If applicable, include any screenshots that
may help solve the problem. -->


---

<!-- Use “[x]” to check the box below if you are
interested in contributing. -->

- [x] I would like to work on this issue and
      submit a pull request.
Repository: flutter
Issue: Add DropdownMenuTheme to make it more customizable and fix background color and border radius issues
Labels: framework,f: material design,c: proposal,team-design,triaged-design

## Use case

If Flutter currently there are two implementations for very similar things. On one hand we have the `PopupMenuButton` and on the other hand we have the `DropdownButton`.

Both have very different stylings and looks even though they should look the same following the [spec](https://material.io/components/menus).

So currently the `PopupMenuButton` implementation is much better then the `DropdownButton` implementation.


Theming:
- `PopupMenuButton` can be globally themed by `PopupMenuTheme`
- `DropdownButton` can not be globally themed

Background color:
- `PopupMenuButton`s background color is rather bright in dark mode, which is correct, as it has an elevation. 
- `DropdownButton`s background color is black

Shape:
- `DropdownButton` has a default shape with rounded corners as it is specified in the specs.
- `DropdownButton` has no shape. The corners are sharp.

## Proposal
Add a new Theme called `DropdownMenuTheme` and make `DropdownButton` follow it.
Also add shape to `DropdownButton` and make the background color `colorscheme.surface` by default and apply the elevation overlay to it in dark mode.
Repository: pytorch
Issue: Blocked version of Cholesky backward
Labels: module: autograd,triaged,module: linear algebra

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Update the `cholesky_backward` function to use the blocked algorithm from https://arxiv.org/abs/1602.07527 (function `chol_blocked_rev` in the paper).

## Motivation

For large matrices, the proposed algorithm is faster than the currently implemented symbolic approach.



cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @vincentqb @vishwakftw @jianyuh
Repository: PowerToys
Issue: Refactoring of the Settings Codebase
Labels: Product-Settings,Priority-2,Issue-Refactoring

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

### Refactoring work that needs to be wrt settings:

1. Move IPC from the shell page to settingsUtils.
2. Have the viewmodels utilize the settings utils to communicate with runner rather than through having a delegate passed to each of them.
3. We should be able to make the code such that settings doesn't have to save the file directly, it can rather communicate this information to the runner and the runner can save the information.
4. only FZ, Shortcutguide, and powerPreview use settings repository. It should be expanded to the rest so that ideally SaveSettings is made private.
5. If we can somehow have runner tell the settings that it has received the information and has successfully stored it, then we can notify the user if something goes wrong there instead of having settings and runner running completely independently.
Repository: flutter
Issue: Add "insertAll" method to AnimatedList 
Labels: framework,a: animation,f: material design,c: proposal,team-design,triaged-design

When i'm using the AnimatedList widget, there are many times where i need to insert more than one time at a time.
Just like a normal list provides an `insertAll` method, the AnimatedList widget should also have an `insertAll` method that inserts multiple items.
Repository: create-react-app
Issue: Create a @tsconfig/* like tsconfig to extend from
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

When you use TypeScript, CRA generates a large complex 20 line tsconfig.json with a lot of implementation details. Details which CRA normally tries to hide (like how the eslint config is just `{ extends: 'react-app' }` and the babel configuration is entirely hidden).

The TypeScript Handbook recommends using one of a collection of TSConfig Bases which are published under `@tsconfig/*`, to reduce complexity of a project's tsconfig file.

As an additional issue the way that CRA manages the tsconfig by resetting some properties but allowing you to edit other tsconfig properties makes it very unclear to the user what properties are editable and what properties CRA requires be left alone.

### Describe the solution you'd like

CRA should publish a tsconfig base in a package which can then be extended in the tsconfig.json that CRA manages. Then instead of forcing certain values in tsconfig.json CRA can unset any property it doesn't allow the user to edit and set an `extends` to the CRA managed tsconfig file instead.

I can see two potential locations for this tsconfig.json.

1. One possibility is to host this tsconfig base in `react-scripts`. This way the tsconfig is guaranteed to be in line with the current version of CRA and will not lag behind if installed separately. And any customized react-scripts package can override the config.
2. Since CRA publishes a `eslint-config-react-app` for the eslint config. The equivalent to this would be to negotiate the publishing of a `@tsconfig/react-app` package. This wouldn't be strange or without precedent, `@tsconfig/react-native` already exists and the official TypeScript handbook indicates they are "hoping the community can add more for different environments".
Repository: rust
Issue: Exponential compilation time for recursive data structures implementing traits with associated types.
Labels: A-trait-system,I-compiletime,A-associated-items,T-compiler,C-bug,I-hang,fixed-by-next-solver

I stumbled upon a case when recursive data structures implementing traits with associated types cause exponential compilation time and memory consumption.

Example is a bit complicated, but quite fragile. I couldn't simplify it further.
Looks like associated type is a required prerequisite for exponential behavior.

I did some basic profiling and it seems that slowdown is caused by exponential growth of obligation forest.

### Code

Following code hangs the compiler:

```Rust
use std::marker::PhantomData;

// Trait with associated type.
trait Trait<T> {
    type AssocType;
    fn foo(&self, a: T) -> T;
}

// End of recursion.
impl<T> Trait<T> for () {
    type AssocType = i32;
    fn foo(&self, a: T) -> T { a }
}

// Recursive struct. Nested type implements trait.
struct NestingStruct<T, SubStruct: Trait<T>>(
    SubStruct,
    PhantomData<T>,
);

impl<T, SubStruct> Trait<T> for NestingStruct<T, SubStruct> where
    SubStruct: Trait<T, AssocType=i32>,
{
    type AssocType = i32;
    fn foo(&self, a: T) -> T { self.0.foo(a) }
}

fn main() {
    let t = ();

    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    // No noticeable slowdown here.

    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    // Ten iterations take less than a second.

    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    // Fifteen iterations take several seconds on my machine.

    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    // Twenty iterations take several minutes.

    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    let t = NestingStruct(t, PhantomData);
    // Each consequent iteration doubles compilation time.
    // I believe it would take several hours to compile next block.

    println!("Hello {}", t.foo(1));
}
```


### Meta

Bug exists in both stable and nightly.

`rustc +nightly --verbose --version`:
```
rustc 1.48.0-nightly (e599b53e6 2020-09-24)
binary: rustc
commit-hash: e599b53e67ddd197a09a3d8720eed872df481aa0
commit-date: 2020-09-24
host: x86_64-pc-windows-msvc
release: 1.48.0-nightly
LLVM version: 11.0
```
Repository: flutter
Issue: WebGPU in Flutter
Labels: c: new feature,engine,customer: crowd,c: proposal,P3,team-engine,triaged-engine

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
Right now integrating low level rendering capabilities in flutter can be kind of tricky as you need to utilize the various platform specific APIs and loose the awesome ability of flutter to port to another platform by simplify specifying another device for `flutter run`.
WebGPU is a cross platform consistent modern API for graphics programming that requires a reasonable level of explicitness and has or is in the process of getting backend support on all major platforms.

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
Create a dart API for graphics programming that closely resembles the WebGPU API (similar to wgpu-es for rust).

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->