sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: Angular valid template with all the strict flags on results in DOMException.
Labels: area: compiler,P3,compiler: parser

# 🐞 bug report

### Description
When compiling angular template there are no issues having `<app-test-component ([var1]="true">` but this results in `DOMException`. Angular is fine having any gibberish atributes, not only `([var1]`, it's just an example of a typo that is more likely to happen in real life scenario. IMO it should fail on compile. This happens even turning all strict flags on:
<pre><code>
  "angularCompilerOptions": {
    "fullTemplateTypeCheck": true,
    "strictTemplates": true,
    "strictInputTypes": true,
    "strictNullInputTypes": true,
    "strictAttributeTypes": true,
    "strictSafeNavigationTypes": true,
    "strictDomLocalRefTypes": true,
    "strictOutputEventTypes": true,
    "strictDomEventTypes": true,
    "strictContextGenerics": true,
    "strictLiteralTypes": true,
    "enableIvy": true
  }
</code></pre> 


## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-ivy-wgnb8w

Just open console and see the error.

## 🔥 Exception or Error
Console error in browser:
<pre><code>
ERROR DOMException: Failed to execute 'setAttribute' on 'Element': '([var2]' is not a valid attribute name.
    at EmulatedEncapsulationDomRenderer2.setAttribute (http://localhost:4200/vendor.js:44711:16)
    at setUpAttributes (http://localhost:4200/vendor.js:16006:30)
    at ɵɵelementStart (http://localhost:4200/vendor.js:25426:9)
    at Module.ɵɵelement (http://localhost:4200/vendor.js:25500:5)
    at AppComponent_Template (http://localhost:4200/main.js:67:64)
    at executeTemplate (http://localhost:4200/vendor.js:20205:9)
    at renderView (http://localhost:4200/vendor.js:20012:13)
    at renderComponent (http://localhost:4200/vendor.js:21274:5)
    at renderChildComponents (http://localhost:4200/vendor.js:19877:9)
    at renderView (http://localhost:4200/vendor.js:20037:13)
</code></pre>


## 🌍  Your Environment

**Angular Version:**
<pre><code>

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 11.0.2
Node: 12.13.1
OS: linux x64

Angular: 11.0.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.2
@angular-devkit/build-angular   0.1100.2
@angular-devkit/core            11.0.2
@angular-devkit/schematics      11.0.2
@schematics/angular             11.0.2
@schematics/update              0.1100.2
rxjs                            6.6.3
typescript                      4.0.5
</code></pre>
Repository: node
Issue: investigate flaky test-repl-history-navigation
Labels: repl,flaky-test

https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubi81_sharedlibs_openssl111fips_x64/23622/console

```console
00:11:05 not ok 1837 parallel/test-repl-history-navigation
00:11:05   ---
00:11:05   duration_ms: 3.266
00:11:05   severity: fail
00:11:05   exitcode: 1
00:11:05   stack: |-
00:11:05     node:assert:107
00:11:05       throw new AssertionError(obj);
00:11:05       ^
00:11:05     
00:11:05     AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
00:11:05     + actual - expected ... Lines skipped
00:11:05     
00:11:05       [
00:11:05         '> ',
00:11:05     ...
00:11:05         ' ',
00:11:05         ']',
00:11:05     -   '\n// [ [length]: 0 ]',
00:11:05         '[ [length]: 0 ]\n',
00:11:05         '> '
00:11:05       ]
00:11:05         at REPLServer.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-repl-history-navigation.js:584:16)
00:11:05         at Object.onceWrapper (node:events:482:28)
00:11:05         at REPLServer.emit (node:events:388:22)
00:11:05         at REPLServer.EventEmitter.emit (node:domain:470:12)
00:11:05         at REPLServer.Interface.close (node:readline:429:8)
00:11:05         at REPLServer.<anonymous> (node:repl:945:33)
00:11:05         at Object.onceWrapper (node:events:482:28)
00:11:05         at REPLServer.emit (node:events:376:20)
00:11:05         at REPLServer.EventEmitter.emit (node:domain:470:12)
00:11:05         at onwritten (node:internal/repl/history:143:14) {
00:11:05       generatedMessage: true,
00:11:05       code: 'ERR_ASSERTION',
00:11:05       actual: [
00:11:05         '> ',
00:11:05         '[',
00:11:05         ' ',
00:11:05         ']',
00:11:05         '\n// []',
00:11:05         '\n// []',
00:11:05         '\n// []',
00:11:05         '> util.inspect.replDefaults.showHidden',
00:11:05         '\n// false',
00:11:05         ' ',
00:11:05         '=',
00:11:05         ' ',
00:11:05         't',
00:11:05         'r',
00:11:05         'u',
00:11:05         'e',
00:11:05         'true\n',
00:11:05         '> ',
00:11:05         '[',
00:11:05         ' ',
00:11:05         ']',
00:11:05         '[ [length]: 0 ]\n',
00:11:05         '> '
00:11:05       ],
00:11:05       expected: [
00:11:05         '> ',
00:11:05         '[',
00:11:05         ' ',
00:11:05         ']',
00:11:05         '\n// []',
00:11:05         '\n// []',
00:11:05         '\n// []',
00:11:05         '> util.inspect.replDefaults.showHidden',
00:11:05         '\n// false',
00:11:05         ' ',
00:11:05         '=',
00:11:05         ' ',
00:11:05         't',
00:11:05         'r',
00:11:05         'u',
00:11:05         'e',
00:11:05         'true\n',
00:11:05         '> ',
00:11:05         '[',
00:11:05         ' ',
00:11:05         ']',
00:11:05         '\n// [ [length]: 0 ]',
00:11:05         '[ [length]: 0 ]\n',
00:11:05         '> '
00:11:05       ],
00:11:05       operator: 'deepStrictEqual'
00:11:05     }
00:11:05   ...
```
Repository: create-react-app
Issue: Too many cpu and ram usage on production build
Labels: needs triage

Hello. I have some problems with production build. react-scripts build use many ram, up to 9 GB.

Current environment:
- React. 17.0.1
- react-scripts 4.0.0
- Typescript 4.1.2

But this problem from react scripts 3.*.* , TS 4.0.* and react 16

I installed craco and add webpack bar. Build hangs on 90% and "additional chunk assets processing". In this time ram and cpu usage is increase.

Build result:
![screenshot](https://user-images.githubusercontent.com/8427994/99822428-41776600-2b64-11eb-8a14-c2578f579741.png)
Repository: react-native
Issue: Android) Switch track is not visible when it is disabled and the parent has a dark background
Labels: Issue: Author Provided Repro,Platform: Android,Component: Switch

## Description
Switch doesn't display the track if:
- It is an Android device
- Switch has `disabled={true}`
- Container background is `black`

## Expected Results
Switch should display the track with a gray color

## Snack, code example, screenshot, or link to a repository:
snack: https://snack.expo.io/@rubengt01/switch-with-dark-background
screenshot: 
![Screenshot_20201120-184049_Expo](https://user-images.githubusercontent.com/2068937/99831819-f78c8100-2b5f-11eb-897f-ee77f5bb43cf.jpg)

## `react-native info`

System:
    OS: macOS 11.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
    Memory: 168.31 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.18.4 - ~/.nvm/versions/node/v12.18.4/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.9.2 - ~/.nvm/versions/node/v12.18.4/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /Users/Ruben/.rvm/rubies/ruby-2.6.1/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.6911.18.40.6626763
    Xcode: 12.2/12B45b - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.2 - /usr/bin/javac
    Python: 2.7.16 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.3 => 0.63.3 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found
Repository: flutter
Issue: Refactor fml::RefPtr/WeakPtr to just be std::shared_ptr, std::weak_ptr
Labels: c: new feature,engine,P3,team-engine,triaged-engine

These classes do not really offer improvements over the `std` counterparts at this point, and we are no longer restricted by tonic living elsewhere.
Repository: rust
Issue: Consider providing an universal way to read (proc macro) dylib metadata.
Labels: A-codegen,A-metadata,T-compiler,A-proc-macros

In https://github.com/EmbarkStudios/rust-gpu/pull/268, I used `rustc_codegen_llvm`'s implementation of `get_dylib_metadata`, in order to support proc macros, and also found out that `rustc_codegen_cranelift` uses the `object` crate for its `get_dylib_metadata`.
(Both the LLVM and the `object`-based implementation extract the `.rustc` section of an `.so`, `.dll`, etc.)

AFAICT, the codegen backend shouldn't really matter, for proc macros specifically, as the proc macro is compiled for the same ("host") platform executing `rustc`, and for which we have `dlopen` (or equivalent) support.

So if we trust the `object` crate to work for at least proc macros, we can attempt to access the dylib metadata using it (i.e. just like `rustc_codegen_cranelift` does), before we ask the codegen backend for a fallback implementation (which could specifically handle non-proc-macro *target* `dylib` crates).

cc @bjorn3 @khyperia @nagisa
Repository: create-react-app
Issue: Can't store secret keys in .env & .env.local files 
Labels: stale,needs triage,issue: bug report
Repository: create-react-app
Issue: React script version 4.0.0 does not reloads the browser when new changes are made
Labels: needs triage,issue: bug report

### Describe the bug

I have been trying to create a new react app using `npx` and when I make changes to that new react app, the changes do not automatically get reflected in the browser. As far as I have seen, it works when use another version of react script like `3.4.4` but when I use the latest `4.0.0` it does not work. I have tried with both npm and yarn. 

### Did you try recovering your dependencies?
Yes, I did but the issue did not get resolved.

### Which terms did you search for in the User Guide?

I made a search for `react app did not reload after making changes in the codes.`

### Environment
```
Environment Info:

  current version of create-react-app: 4.0.0
  running from /home/mwibutsa/.npm/_npx/252967/lib/node_modules/create-react-app

  System:
    OS: Linux 5.8 Pop!_OS 20.04 LTS
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
  Binaries:
    Node: 14.15.1 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.9 - /usr/local/bin/npm
  Browsers:
    Chrome: 86.0.4240.111
    Firefox: 82.0
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.0 => 4.0.0 
  npmGlobalPackages:
    create-react-app: Not Found

```
### Steps to reproduce


(Write your steps here:)

1.npx create-react-app jsx
2. delete all the files in `src/` directory and recreate a new `index.js` file in the same directory
3. write these codes and start the app. 

4. make any new changes to the codes like changing the text 

### Expected behavior

- The browser tab containing the app should reload to reflect new changes


### Actual behavior

- The browser did not reload
Repository: pytorch
Issue: torch.float128 datatype
Labels: feature,triaged,module: numpy

## 🚀 Feature
It would be great to have a torch.float128 datatype for computations that require more precision. I understand that this datatype might not be supported by Cuda, but for many of the models that I run, there are many small calculations that in runs on cpu faster than gpu. 

## Motivation

In modeling optical problems, double precision can cause some issues. These problems usually have many small calculations that it runs faster on the cpu (also speed is not really an issue here). Having access to a float128 datatype can be extremely useful. 





cc @mruberry @rgommers @heitorschueroff
Repository: TypeScript
Issue: remove-unused-identifier codefix-all doesn't remove redundant `var`
Labels: Bug

```ts
function g(y: number) {
    var y: number
}
```

**Expected behavior:**

```ts
function g() {
}
```

**Actual behavior:**

```ts
function g() {
    var y: number
}
```

This is weird code so it's low priority to fix it.

Another example:

```ts
function g() {
    var z: number
    var z: number
    var z: number
}
```

**Expected**

```ts
function g() {
}
```

**Actual**

```ts
function g() {
    var z: number
    var z: number
    var z: number
}
```
Repository: TypeScript
Issue: Template literal types not giving autocomplete suggestions
Labels: Suggestion,Domain: Completion Lists,Experience Enhancement

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  4.1.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
Template literal type autocomplete suggestion lint
**Code**

```ts
        type autocomplete = `meeting`;
        type noAutocomplete = `meeting/${number}`;
        const val: noAutocomplete = 'meet';
```

**Expected behavior:**
Beginning to fill out a string on a template literal type will give a useful autocomplete suggestion, like filling it out with a string literal type.
**Actual behavior:**
In VSCode, there is no autocomplete suggestion and in the TypeScript Playground the suggestion is incorrect.

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
https://www.typescriptlang.org/play?ts=4.2.0-dev.20201120#code/C4TwDgpgBAhgrsA9gY0QWzAGwsaBeKAAzQhwEsA7Ac0IG4AoUSKCxAQQRXSx3yJOCUqAegAkAbwpw0AIwgAnAL516qCgGdgUAG4xMALlidUGbLigEA5CXLVLDNZp16ATIdYckJnuav2gA
**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: pytorch
Issue: [FR] bool tensor should support basic arithmetics
Labels: triaged,module: numpy,module: type promotion,module: boolean tensor

## 🚀 Feature

Numpy supports this (e.g., `100-x`) and I don't know why that we can't type promote bool torch tensors.


cc @izdeby @mruberry @rgommers @heitorschueroff @nairbv
Repository: scrcpy
Issue: Permission denied, ERROR: Could not execute "adb push"
Labels: adb,snap

Hi there, can anyone help me?

I have a conflict between two versions of adb:  local android-sdk (41) and version from scrcpy snap package (39). 

I tried to run scrcpy like that:

`ADB=~/.local/Android/Sdk/platform-tools/adb scrcpy`

But unfortunately, it doesn't work:

``
INFO: scrcpy 1.16 <https://github.com/Genymobile/scrcpy>
exec: Permission denied
ERROR: Failed to execute: [~/.local/Android/Sdk/platform-tools/adb], [push], [/usr/local/share/scrcpy/scrcpy-server], [/data/local/tmp/scrcpy-server.jar]
ERROR: Could not execute "adb push"
``

At the same time command `scrcpy` with adb 1.0.39 works properly.


OS: Ubuntu 20.10


`adb version` 
                                           
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Installed as ~/.local/Android/Sdk/platform-tools/adb

`scrcpy.adb version`

Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5~18.04
Installed as /snap/scrcpy/254/usr/lib/android-sdk/platform-tools/adb


Any suggestions on what to do?

I need to run 1.0.41 version of adb because my IDE uses it, and scrcpy crashes when I run IDE.
I would like to use them at the same time.
Repository: rust
Issue: [rustdoc, request] Please bundle local relative resources (favicon, logo, whatever)
Labels: T-rustdoc,C-feature-request

For some of my crates I have a favicon and logo within the repo but have to point to them via public links like this:

```rust
#![doc(html_logo_url = "https://github.com/jnqnfe/pulse-binding-rust/raw/master/logo.png",
       html_favicon_url = "https://github.com/jnqnfe/pulse-binding-rust/raw/master/favicon.ico")]
```

What I would love (and have long wanted) is if I could simply refer to the files with a relative path like this...:

```rust
#![doc(html_logo_url = "../../logo.png", html_favicon_url = "../../favicon.ico")]
```

...and `cargo doc` would then bundle them into the set of generated documentation files, such that when viewing the documentation offline locally, these resources are loaded from the `target/doc/` directory, and for the docs.rs copy, docs.rs would serve them along with the rest of the page components.

This would include the following advantages:
 - The favicon and logo would actually get loaded properly when viewing documentation offline. (It's very annoying that they don't, and loading them once at some point when you are online is not sufficient to subsequently ensure they are shown from cache in my experience).
 - Helps ensure in future that a change such as a move of the repo from github to gitlab, or move/rename of the files within the master copy of the public repo, does not break display of these items for older published versions of crates due to broken links.
 - Helps avoid in future trouble replacing favicon/logo images with new ones for new releases without replacing the older copies for older versions of the documentation, without making a mess of maintaining multiple versions of the file within the repo.
 - Helps alleviate any privacy concerns from loading such resources while online but reading local documentation.

Perhaps this could be applied to all such local relatively referenced image resources (others too?), not just favicon and logo, to cover situations where repos include images to embed in docs.
Repository: opencv
Issue: There may be some errors about `cv::HoughCircles`?
Labels: bug,category: imgproc

Consider that the size of cv::Mat `edges`  is different from the size of the accumulator. Since the size of accumulator is (edges.rows + 2, edges.cols + 2), the vote should be cast at 2d range [1, edges.rows] x [1, edges.cols]. 

Therefore, I think the following modifications should be made.


https://github.com/opencv/opencv/blob/0105f8fa38ec867a8e4bbc74c402afcd0e296194/modules/imgproc/src/hough.cpp#L1209
```
[-] adataLocal[y2*astep + x2]++;
[+] adataLocal[(y2+1)*astep + (x2+1)]++;
```

https://github.com/opencv/opencv/blob/0105f8fa38ec867a8e4bbc74c402afcd0e296194/modules/imgproc/src/hough.cpp#L1270
```
[-] centersLocal.push_back(base);
[+] centersLocal.push_back(base - acols - 1);
```
That's all.
Thanks for your considerations. : )
Repository: godot
Issue: Area2D's signals *_entered and *_exited do not fire predictably during movement dependent on speed and size.
Labels: bug,confirmed,topic:physics

**Godot version:**
v3.2.3.stable.official

**OS/device including version:**
Windows 10 Home 64-bit (10.0 Build 19041)

**Issue description:**
Area2D's signals body_entered, body_exitedm, area_entered and area_exited do not fire predictably dependent on the size and speed of the objects involved.

**Steps to reproduce:**
1. Create an Area2D segment that splits the viewing area.
2. Create two RigidBody2D objects with a small circle as a child CollisionShape2D.
3. Set their linear_velocity such that the two RigidBody2D objects move toward and pass through the segment.
4. Increase the speed of one of them sufficiently and the signal will not fire anymore.
5. Slowing down the object or increasing its size will cause the signal to fire again.

**Minimal reproduction project:**
[enter_exit_non_detection.zip](https://github.com/godotengine/godot/files/5577361/enter_exit_non_detection.zip)
Repository: godot
Issue: When raycasting in editor (Tool), collisions only register within bodies' original bounding box area (fixed in `master`)
Labels: bug,topic:editor,confirmed,topic:physics

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.2.3.Stable


**OS/device including version:**
Intel(R) Core(TM) i7-5820K, GTX 970, Windows 10 Pro


**Issue description:**
When raycasting in editor (Tool), collisions only register within bodies' original bounding box area. This happens both with static bodies and kinematic bodies. This might be on purpose, but if it is there should be some option (API Call?) to force the bounding boxes to update. at the moment you have to close the scene and open it again or do a workaround like disabling and re-enabling all the collision shapes.

![yNRoXvRdFx](https://user-images.githubusercontent.com/4955051/99876226-58ae6600-2bed-11eb-9342-c5612e6ee9a3.gif)

**Steps to reproduce:**
Open attached project and move the Static Body around.

**Minimal reproduction project:**
[raycasting_in_editor.zip](https://github.com/godotengine/godot/files/5577532/raycasting_in_editor.zip)
Repository: godot
Issue: range() function strange behaviour with arguments >= 2^24
Labels: bug,topic:core,confirmed

**Godot version:**
Godot Engine v3.2.3.stable.official

**OS/device including version:**
Windows 10 Home 64bit ver. 2004 (build 19041.630)
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59GHz 16GB
OpenGL ES 2.0 Renderer: GeForce GTX 1650/PCIe/SSE2
OpenGL ES 2.0 Batching: ON

**Issue description:**
from arguments >= 167772156 (2^24) the range fails

```
range(16777215, 16777217)
output:
16777215
```

```
range(16777217, 16777219)
output:
16777216
16777217
16777218
16777219
```

**Steps to reproduce:**
```
func _ready():
	var a = 16777215
	var b = a + 2
	for n in range(a, b):
		print(n)
```