sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Typescript supports less valid variable names characters than javascript
Labels: Bug,Help Wanted

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
unicode invalid character name

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- I specifically tried the zero width space non-joiner. In this particular case at least, the support was lost between versions 3.5.1 and 3.6.3, as shown by the playground.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?target=99&ts=3.6.3#code/PTAEBUAsFMCdtASwM6gIagF5wPagO6IAmALpKAHY4UC0AVjohXKAEbQn7TQWgBEADz7oKRfgE8+AOgBQAY2rISoAYBgCcaAC8oACwAmANxA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// There is a zero width non-joiner between "x" and "y".
// All versions starting from 3.6.3 think that I am defining a "x" and a "y" variable separately.
// Version 3.5.1 outputs the expected JS code, which is strictly equal to the TS code in this case.
const x‌y = 42;
```

### 🙁 Actual behavior

Not all variable names valid in JS are supported in TS. At least the zero width non-joiner character is not supported. I didn't go on the hunt for all the unsupported characters but clearly TS does not support the full set of supported JS characters anymore.

### 🙂 Expected behavior

All valid variable names in JS should also be valid variable names in TS. At least when tsconfig is configured to output in an ES version that supports it.

For the record, a wonderful tool exist to test if a variable name is valid in JS: https://mothereff.in/js-variables
Repository: rust
Issue: Non linear runtime increasment for `expand_crate` pass while compiling diesel with `128-column-tables`
Labels: I-slow,T-compiler,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.
-->

This is a followup issue to https://github.com/rust-lang/rustc-perf/pull/807, where I've suggested to add `diesel` with the `128-column-tables` enabled to the rustc-perf test-suite as this is taking quite a lot of time to compile. As part of that request we discovered that the `expand_crate` pass scales non-linear with the number of codelines expanded through a macro. (For diesel that would likely be [this macro call](https://github.com/diesel-rs/diesel/blob/493541ddcecfb110814681ae83289adb149ee253/diesel/src/type_impls/tuples.rs#L502) which expands the macro above for all tuples sizes between 1 and the maximal number specified (16, 32, 64 or 128) via [this macro](https://github.com/diesel-rs/diesel/blob/493541ddcecfb110814681ae83289adb149ee253/diesel/src/macros/tuples.rs)

@rustbot modify labels: +I-slow
Repository: rust
Issue: Nonlinearity in `check_mod_privacy` pass for a large number of impls
Labels: I-slow,A-visibility,T-compiler,C-bug

This is a followup issue to rust-lang/rustc-perf#807, where I've suggested to add diesel with the `128-column-tables` enabled to the rustc-perf test-suite as this is taking quite a lot of time to compile. As part of that request we discovered that the `check_mod_privacy` pass scales non-linear with the number of code lines. See the linked PR for the exact numbers. I suspect that this is somehow related to a large number of trait impls for tuples of various sizes.

@rustbot modify labels: +I-slow
Repository: excalidraw
Issue: Zooming is extremely slow and laggy on Safari 14
Labels: performance ⚡️,high priority

Hey,
recently I was switching to Safari and noticed that the Excalidraw zooming is super laggy. Are you aware of this? Is there anything we could do to improve it?
Repository: TypeScript
Issue: --format=checkstyle option for tsc --noEmit
Labels: Suggestion,Awaiting More Feedback

# Suggestion


## 🔍 Search Terms

Checkstyle

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

We have automated checking for typescript errors in our CI tooling (Jenkins), using the following command `./node_modules/.bin/tsc --project ./tsconfig.json --noEmit > build-logs/typescript-error.log`. Currently we save the output to a plaint text file, but we would like to be able to parse it in our CI. The standards most tooling follows is a format option which supports a checkstyle format, which can easily be parsed by most CI's.

See https://checkstyle.sourceforge.io/config.html#Configuration_XML_Structure for more information on how to format the xml.

It would be great to have a `--format=checkstyle` option we could add to our current command to get a formatted xml file with all errors.

## 📃 Motivating Example

Most of our current tooling already supports this, and this enables us to check code quality, fail builds, etc.
![Screenshot 2021-01-22 at 10 28 59](https://user-images.githubusercontent.com/1841343/105472886-bc601880-5c9c-11eb-8f4a-fc7a791a58b7.png)


## 💻 Use Cases

We currently have checks for stylelint, eslint, php codesniffer, phpstan, psalm and htmlhint. It would be great if we could also easily identify and report which typescript errors exist within our projects and possibly fail a build if we encounter them.
Repository: create-react-app
Issue: Babel-jest error when migrating to v4.0.1
Labels: stale,needs triage,issue: bug report

When I upgrade from `react-scripts` 3.4.1 to 4.0.1, I have an error when running `yarn start`

![1](https://user-images.githubusercontent.com/2200902/105474824-a45aba00-5cd9-11eb-98bd-d19c9cde531c.png)

Interestingly, when I run `npm ls babel-jest` I get this

![2](https://user-images.githubusercontent.com/2200902/105474852-ade42200-5cd9-11eb-8837-26e93b4e8c32.png)

The 26.6.0 version is not showing up when running that command so I wonder what dependency is using that
In yarn.lock file it shows 26.6.0

![3](https://user-images.githubusercontent.com/2200902/105474885-ba687a80-5cd9-11eb-8b2d-a00b855e69a0.png)

Tried `yarn list --pattern babel-jest` too

![4](https://user-images.githubusercontent.com/2200902/105474901-c0f6f200-5cd9-11eb-831c-a18ff304fcd3.png)
Repository: flutter
Issue: Number text field
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-text-input,triaged-text-input

## Use case

Currently, it's very hard to develop a number text field. And I'm not talking about just allowing digits (and plus, minus and period/comma) but also limiting the number of those characters so that we can input only one period, only one minus (or maybe two in case of a scientific notation) etc.

## Proposal

Either a new `NumberTextField` or similar or an official `NumberTextInputFormatter` that works just like the `input[type=number]` and guarantees that `double.parse` will work for the text field's value.

I tried to implement this myself, but maintaining correct cursor position and selection is really hard for me https://gist.github.com/Albert221/8f3e68f34eac0783f84c9f869b7857be
Repository: rust
Issue: "arithmetic_overflow" and "unconditional_panic" lints do not fire on `const fn` that is only const-used in bin crate
Labels: A-lints,P-medium,regression-from-stable-to-stable,C-bug,A-const-eval

I tried the following code:
```rust
const fn overflow() -> u32 {
    0 - 1
}

pub const X: u32 = overflow();

fn main() {}
```
On stable, in release mode, the emits a lint (err-by-default) about the arithmetic overflow. On nightly, it does not.

This probably is related to https://github.com/rust-lang/rust/pull/78407. However, the part I do not understand is that I can only reproduce the problem with a binary crate, not with a library crate. Cc @oli-obk
Repository: ant-design
Issue: Ability to copy text from Select component (highlight with the mouse or Shift   End(home) buttons).
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.

### What problem does this feature solve?
Now there is no way to copy the text, partially or completely. After we have selected a value from the list, it is displayed on the form. Sometimes it is necessary to copy this value completely or part of it by selecting the desired fragment with the mouse, as we usually do with the Input component.
Now, if the value is selected, we will place the cursor in Select. Then we will not be able to select our value with the mouse or buttons. it will just become a dull color, but there is no way to highlight it.

If there is already a solution, I will be grateful for the hint. How to do it

### What does the proposed API look like?
Add a new property. Example (editableValue)
When setting which (true, false), we will be able to place the cursor in the Select field and will be able to select with the mouse or Shift   End(home) the piece of text we need for future copying to the buffer.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: SequentialSampler getting slower as time passing by
Labels: module: dataloader,triaged

## 🐛 Bug

I am training BERT model with a huge dataset (100M rows) and using SequentialSampler. The time spent for each step is increasing with time.
In the screenshot below you see the relationship between time in hours on x axis and global step in y axis. This relation should be linear as time passing by. 
I have noticed this issue with both Huggingface Transformer library and Simpletransformers. Replacing SequentialSampler with RandomSampler this issue disappear (but RandomSampler has other problems as in issue #50689 )

![image](https://user-images.githubusercontent.com/1651448/105484496-52973d00-5ca3-11eb-802c-422628f9e5a1.png)

## To Reproduce

Steps to reproduce the behavior:

1. Get a huge dataset, e.g. 100M rows
2. Start training
3. Track time over steps

## Expected behavior

I expect a linear relationship between time spent and number of steps processed, or in other words a constant training time per step during the entire training procedure. 

## Environment

PyTorch version: 1.7.1
Is debug build: False
CUDA used to build PyTorch: 10.1
ROCM used to build PyTorch: N/A

OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
Clang version: Could not collect
CMake version: Could not collect

Python version: 3.7 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: Tesla V100-PCIE-16GB
Nvidia driver version: 418.39
cuDNN version: /usr/local/cuda-10.0/targets/x86_64-linux/lib/libcudnn.so.7.6.5
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[conda] blas 1.0 mkl
[conda] cudatoolkit 10.1.243 h6bb024c_0
[conda] mkl 2020.2 256
[conda] mkl-service 2.3.0 py37he8ac12f_0
[conda] mkl_fft 1.2.0 py37h23d657b_0
[conda] mkl_random 1.1.1 py37h0573a6f_0
[conda] numpy 1.19.2 py37h54aff64_0
[conda] numpy-base 1.19.2 py37hfa32c7d_0
[conda] pytorch 1.7.1 py3.7_cuda10.1.243_cudnn7.6.3_0 pytorch
[conda] torchaudio 0.7.2 py37 pytorch
[conda] torchvision 0.8.2 py37_cu101 pytorch

cc @SsnL @VitalyFedyunin @ejguan
Repository: pytorch
Issue: Questions about amp
Labels: module: cuda,triaged,module: amp (automated mixed precision)

I want to use torch.cuda.amp.autocast to reduce the GPU memory，but I got a odd phenomenon.
The GPU memory will be decreased，only when I add the following code in forward() function of nn.Module class:
```
    # @autocast()
    def forward(self, x):
        with autocast():
            x1 = self.conv(x)
            out = self.outc(x1)
        return out  
```
- I delete other code about amp.autocast and GradScaler in the train.py,and then the GPU memory still can be decreased from 9000+ to 6000.
- In addition,I can not control the GPU number,when I use "@autocast()". I have set one GPU,but all GPU were used.
Thanks for your help!
pytorch version:1.6.0+cu101
python version:3.65

cc @mcarilli @ptrblck @ngimel
Repository: rust
Issue: Wrong lifetime inference in closures
Labels: A-closures,T-compiler,A-inference,C-bug

I tried this code:

https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=b12eb2156476d65e668f66630a107a51

I expected to see this happen: both `check` calls will compile.

Instead, this happened: compiled only one call, another broken with error.

This is a bug with lambdas (not closures) as i can see. 

I think compiler infer '0 lifetime for argument and '1 lifetime for return value but return value must have '0 lifetime (like in function `t`)
Repository: pytorch
Issue: Exporting opnames fails when using custom classes
Labels: oncall: mobile

## 🐛 Bug

For using a custom PyTorch mobile build a list of operators is required. If the model uses custom classes however `torch.jit.export_opnames` fails, even though the model can be successfully run with PyTorch Mobile using the full build.


<!-- A clear and concise description of what the bug is. -->

## To Reproduce

Run the following script:

```python
import torch
from torch import nn


class DataContainer:
    def __init__(self, data: torch.Tensor):
        self.data = data


class SampleModule(nn.Module):
    def forward(self, x: torch.Tensor):
        dc = DataContainer(x)
        return dc.data


module = SampleModule()
scripted_module = torch.jit.script(module)
ops = torch.jit.export_opnames(scripted_module)
```

This will result in the following error:
```
RuntimeError: CREATE_OBJECT is not supported in mobile module.
Workaround: instead of using arbitrary class type (class Foo()),
define a pytorch class (class Foo(torch.nn.Module)).
```
<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

If a model runs on PyTorch Mobile, `torch.jit.export_opnames` should also not raise an exception.

<!-- A clear and concise description of what you expected to happen. -->

## Environment

 - PyTorch Version (e.g., 1.0): 1.8.0.dev20210122 (also earlier nightlies)
 - OS (e.g., Linux): macOS Catalina
 - How you installed PyTorch (`conda`, `pip`, source): pip (nightly build)
 - Python version: 3.8.5
 - CUDA/cuDNN version: None
 - GPU models and configuration: None


cc @gmagogsfm
Repository: TypeScript
Issue: Code Completion missing for a generic type which references itself since v3.8.3
Labels: Bug,Domain: Completion Lists

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

code completion, generic type, reference itself

### 🕗 Version & Regression Information

- This changed between versions 3.7.5. and 3.8.3.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=3.7.5#code/MYewdgzgLgBADgQwE4ILYRgXhgbwFAwwIBcMAjADQEwBGpA5AEz1WHClRICuApqzABNSYLgBtRVAL4BuPHigBPODxgBhcADMAlgHMAPAAVkaANI8FEAHxZcMRcoYQtYHaJ70YkmAB9b9ngyIWkj00vAIwaRGKKhmFp6yeBpcYMBQWuCCIADKIKg8UAAWzvrU0WgQ-KowPAAeUDxgAhgASjygSAJ61IQAorXAolwCPHoA1uYgGjDl6BQwAJJgGjxIAPKoWlBQCDRucRB6qpaW-ITqy7rjk9OzVtSneJYAFPiEiDGV1KCXOlKkb3CnyixnQsjYml0pFUskkAEoAUCKiDPvMftodNDPLhqEgClwkGBbB8KmjIToEnhJHIAPQ0mA6EAIUSkAAG6N0rJgEEKIDEAhgYB4PAFRRUEDQKgm8QQGFZJPQrPmNC4sHAogUMC003AKimdkKPFQeDpWowYBAsAgymA2q0Iq1RLFMAAREEkC6YMBZTw8AIcnkCsUXK9qAqvhDfgCekREf5HCU3B5JGdaHGlAEYPR3SxwpEs8Bk6nTew-BmEy4k55UzG6UIyw4s05K+5q9QU1S4Yl-ItlqsNlsdnseAc9AAVazYJYrdabba7fbmccAbWl+rHAF1LN2M72ZwP58O4uPJzAxzV6o1mjjCPGsznwXmkKRnDOYAeh4uFLDqAB+RYQNknAlHoH4LiO5iWNQwg8AAbqsO7KABQFICBE42OedQNE0GDQKhLgwP+54wfBSCJHIFHyLuY48NANjTv2c6fhBFh6ICJANpm9DNq4rYyNQdCcYEEQhGE7oMIWlKEPWOB2OWTaJnxsLbngQA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// see linked playground for the full example
function doSomething<
  Params,
  C extends Record<
    Exclude<keyof Params, InferOmittableKeys<C>>,
    Config<keyof Params>
  >,
>({
  params,
  config,
}: {
  params: Params;
  config: C;
}): { params: Params, config: C } {
  return { params, config };
}

doSomething({
  params, // { a: 1, b: '2', c: true, d: null }
  config: {
    a: { type: 'single' },
    b: { type: 'pair', pair: 'c' },
    // GOAL: CODE COMPLETION FOR `d`, BUT NOT `c`
  },
});
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->

With 3.8.3:
![image](https://user-images.githubusercontent.com/1152805/105494205-bb3de400-5cba-11eb-8034-f464e7fec432.png)

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

With 3.7.5:
![image](https://user-images.githubusercontent.com/1152805/105494166-af522200-5cba-11eb-9058-e106143742c4.png)

---

Both versions have the correct error however: `Property 'd' is missing in type '{ a: { type: string; }; b: { type: string; pair: string; }; }' but required in type 'Record<"a" | "b" | "d", Config<"a" | "b" | "c" | "d">>'.`
Repository: pytorch
Issue: libpytorch macos build: static library eigen_blas_LIBRARY-NOTFOUND not found
Labels: module: build,triaged

## 🐛 Bug

When building a static libpytorch on macos, cmake configuration for `find_package` reports the following warning:

```
[cmake] CMake Warning at libtorch_from_source/pytorch-build/TorchConfig.cmake:22 (message):
[cmake]   static library eigen_blas_LIBRARY-NOTFOUND not found.
[cmake] Call Stack (most recent call first):
[cmake]   libtorch_from_source/pytorch-build/TorchConfig.cmake:113 (append_torchlib_if_found)
[cmake]   src/CMakeLists.txt:4 (find_package)
```

## To Reproduce

Steps to reproduce the behavior:

1. Build libpytorch with `-DBUILD_SHARED_LIBS=OFF`
2. In your cmake-built app, use `find_package(Torch 1.8.0 EXACT REQUIRED)`.
3. Observe the warning from above.
4. Link the library to your executable and see linker errors when building.

I build libpytorch with the following command (from the source directory):

```
mkdir pytorch-build && cd pytorch-build && cmake -DBUILD_SHARED_LIBS=OFF -DUSE_CUDA=OFF -DCMAKE_BUILD_TYPE:STRING=MinSizeRel -DPYTHON_EXECUTABLE:PATH=`which python3` -DCMAKE_INSTALL_PREFIX:PATH=../pytorch-build ../pytorch && cmake --build . --target install
```

And this is the CMakeLists.txt that contains the find_package:

```
set(Torch_DIR ${CMAKE_SOURCE_DIR}/libtorch_from_source/pytorch-build)
set(ENV{TORCH_INSTALL_PREFIX} ${CMAKE_SOURCE_DIR}/libtorch_from_source/pytorch-build)
find_package(Torch 1.8.0 EXACT REQUIRED)

add_executable(myexec main.cpp)
target_link_libraries(myexec  PRIVATE "${TORCH_LIBRARIES}")
target_include_directories(myexec PRIVATE "${TORCH_INCLUDE_DIRS}")
```

## Expected behavior

For the warning to not appear and the linking process to succeed.

## Environment

 - PyTorch Version: 1.8.0 (current master)
 - OS (e.g., Linux): MacOS Catalina 10.15.7
 - How you installed PyTorch (`conda`, `pip`, source): source from github master branch.
 - Build command you used (if compiling from source):
```
mkdir pytorch-build && cd pytorch-build && cmake -DBUILD_SHARED_LIBS=OFF -DUSE_CUDA=OFF -DCMAKE_BUILD_TYPE:STRING=MinSizeRel -DPYTHON_EXECUTABLE:PATH=`which python3` -DCMAKE_INSTALL_PREFIX:PATH=../pytorch-build ../pytorch && cmake --build . --target install
```
 - Python version: Python 3.7.6
 - CUDA/cuDNN version: None
 - GPU models and configuration: whatever gpu is in Macbook Pro

cc @malfet @seemethere @walterddr
Repository: terminal
Issue: Allow "hyperlink" matching for arbitrary patterns and adding custom handlers 
Labels: Issue-Feature,Area-TerminalControl,Area-Settings,Product-Terminal

# Description of the new feature/enhancement

A lot of developer tools print errors in:
```
dir/dir/filename:lineNumber:columnNumber
```

format. For example:

![image](https://user-images.githubusercontent.com/172594/105504686-f7277800-5cbf-11eb-9733-7388c9c02b87.png)

Terminal should make these clickable.

# Proposed technical implementation details (optional)

Leverage any relevant bits about how http links work in the current version of Terminal.
Repository: deno
Issue: Error from eval when adding -p flag
Labels: bug,repl

The command 

    deno eval 'let i=3;1+i'

works as expected returning no error code and if we print the last statement it returns 4 as expected:

    deno eval 'let i=3;1+i;console.log(1+i)'

However, if you add the `-p` flag to automaticly print the output it returns an error

    deno eval -p 'let i=3;1+i'
    > error: Expected ,, got i at file:///.../$deno$eval.ts:1:16

I was expecting it to print out `4` as that is the result of the last statement.
Repository: go
Issue: x/pkgsite: warn if a module regularly breaks semver
Labels: NeedsInvestigation,FeatureRequest,modules,pkgsite

On the right side of the module page there are checkmarks like "stable version" and "redistributable license". I think we should also add a checkmark along the lines of "follows semver". That is, that minor or bugfix versions don't repeatedly make clearly backwards-incompatible changes, like removing entire functions or packages.

Here's an example of such an obvious breakage: https://pkg.go.dev/google.golang.org/grpc/naming

That page does show a `This package is not in the latest version of its module` warning, but one would usually not find such a warning until *after* experiencing breakage when updating the module and finding build failures due to the now-missing package.

In other words, if I'm looking at what modules to add as dependencies and I looked at https://pkg.go.dev/google.golang.org/grpc, I'd think twice before adding that module if I saw an alert saying one of the following:

* Last breaking change on *date* (or the version)
* *N* v1 releases contain breaking changes (or *N%* of stable v1 releases)
* *N* packages have had breaking changes since v1.0.0 (or *N%* of total packages)

Please realise that I'm only using grpc as an example since it's the one I've struggled with the most recently. The feature would equally apply to any other v1+ module which uses stable semver tags, but which actively breaks the semver compatibility rules.

cc @bcmills @heschik @julieqiu @leitzler