sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: Saving a file on vim throws with 95% emitting fork-ts-checker-webpack-plugin
Labels: compatibility with other tools,has workaround,performance issue,typescript

**Describe the bug**
When using storybook  with angular project, and editing in vim, on save, Storybook throws :

```bash
95% emitting fork-ts-checker-webpack-plugin
```

**To Reproduce**
Steps to reproduce the behavior:

1. I created a new angular project with `ng new`
2. installed Storybook right after
3. launch storybook with `npm run storybook`
4. Open the project in vim (SpaceVim / Coc.nvim)
5. Open app.component.html
6. Modify nothing in it
7. save the file
8. console displays `95% emitting fork-ts-checker-webpack-plugin`
9. can only restart the Storybook cli

**Expected behavior**
File should be saved, storybook compiles, wait for any other saving.

**Screenshots**

Before saving :
<img width="1166" alt="Capture d’écran 2020-11-04 à 16 43 04" src="https://user-images.githubusercontent.com/24223583/98133048-68277280-1ebd-11eb-9565-1ac35d52e6bc.png">

After saving : 
<img width="1166" alt="Capture d’écran 2020-11-04 à 16 43 11" src="https://user-images.githubusercontent.com/24223583/98133072-6f4e8080-1ebd-11eb-9b9e-c60a190dc41e.png">

**System**
Environment Info:

  System:
    OS: macOS 11.0.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
  Browsers:
    Edge: 86.0.622.58
    Firefox: 82.0.2
    Safari: 14.0.1
  npmPackages:
    @storybook/addon-actions: ^6.0.28 => 6.0.28
    @storybook/addon-essentials: ^6.0.28 => 6.0.28
    @storybook/addon-links: ^6.0.28 => 6.0.28
    @storybook/angular: ^6.0.28 => 6.0.28
Repository: TypeScript
Issue: Don't include full paths in module names in error messages
Labels: Suggestion,Experience Enhancement

**TypeScript Version:**  4.0.5 (also tested with `typescript@next`)

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** namespace has no exported member error

**Description**

Currently certain error messages shows _full_ file paths. For example:

> Namespace '"y:/projects/opf/portal/OPF.Portal.Web/Content/Scripts/DinSide/App/Store/index"' has no exported member 'All'. ts(2694)

> Could not find a declaration file for module 'shortid'. 'y:/projects/opf/portal/OPF.Portal.Web/node_modules/shortid/index.js' implicitly has an 'any' type.
  Try `npm install @types/shortid` if it exists or add a new declaration (.d.ts) file containing `declare module 'shortid';` ts(7016)

Our project was started without `strict: true` (and few `@typescript-eslint` rules), so the code base includes several thousand errors. To be able to gradually fix them, we have started to use [`betterer`](https://github.com/phenomnomnominal/betterer/), which includes committing a snapshot of all the current errors. Snapshot is then used to report report when we fix errors, and fail our build if we add new errors. But because of certain Typescript errors using _full_ file paths, we're getting unnecessary diffs in this snapshot. 

Would it be possible to use file paths relative to the project/tsconfig.json root in the error messages instead?

So, with tsconfig.json in `y:/projects/opf/portal/OPF.Portal.Web/`, the error message would instead be:

> Namespace '"Content/Scripts/DinSide/App/Store/index"' has no exported member 'All'. ts(2694)

An alternative solution could be to change `betterer` instead, make it auto-replace file paths with relative paths, or something like that. But figured I could at least ask her, especially since it could maybe be an issue for other tools as well.

**Related Issues:** Couldn't find any
Repository: create-react-app
Issue: Bug: -webkit-calc doesn't work with var() when compiling css
Labels: stale,needs triage,issue: bug report

I've got different animation on android and iphone, that's most likely 
connected with top: and left: css props, so i have decided to add prefix
-webkit-calc (I am using calc() and var() for it). But npm run build crashes,
while npm run start works good -_-

React version: 16.13.1

Link to code example:
https://codesandbox.io/s/gifted-leftpad-j80id?file=/src/styles.css

PS: when i've tried to use -webkit-calc without var() npm run build worked
Repository: pytorch
Issue: FX quantization: we should preserve original model class name through the quantization passes
Labels: oncall: quantization,low priority,triaged

Currently, after a model goes through the FX quantization passes, the original class type and name is not saved.  Ideally, we could preserve it as an attribute so it can be used for debugging.  Something like

```
class ModelFoo(torch.nn.Module):
  ...

m = ModelFoo(...)
m_prepared = torch.quantization.prepare_fx(m, ...)
# m_prepared should save the information that it was created from an object of type ModelFoo
```

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @jgong5 @Xia-Weiwen @leslie-fang-intel @dzhulgakov @vkuzo
Repository: rust
Issue: Inefficient bit mask codegen in combination with comparison operators.
Labels: A-LLVM,I-slow,C-enhancement,T-compiler,C-optimization

Hi. All four test cases should compile to what is essentially a no operation. However the compiler does not omit the unnecessary case_1 and case_2 bit mask operations as it does with case_3 and case_4.

https://play.rust-lang.org/?version=stable&mode=release&edition=2018&gist=5bc8761dc8bebe2fbf7797f47c4a2a26

```rust
// Inefficiently compiled.
pub fn case_1(mut u: u32) -> u32 {
    if u <= 0x3F {
        // At this point u is 0..=0x3F and the mask operation does nothing
        u &= 0x7F; // also 0xFF, 0x01FF, ..., 0x7FFF_FFFF.
    }
    u
}

// Inefficiently compiled.
pub fn case_2(mut u: u32) -> u32 {
    if u <= 0x3E {
        // At this point u is 0..=0x3E and the mask operation does nothing
        u &= 0x3F; // also 0x7F, 0xFF, ..., 0x7FFF_FFFF.
    }
    u
}


// Ok
pub fn case_3(mut u: u32) -> u32 {
    if u <= 0x3F {
        // At this point u is 0..=0x3F and the mask operation does nothing
        u &= 0x3F;
    }
    u
}

// Ok
pub fn case_4(mut u: u32) -> u32 {
    if u <= 0x3F {
        // At this point u is 0..=0x3F and the mask operation does nothing
        u &= 0xFFFF_FFFF;
    }
    u
}
```

Generated assembly:

```assembly
playground::case_1:
	movl	%edi, %eax
	andl	$127, %eax
	cmpl	$64, %edi
	cmovael	%edi, %eax
	retq

playground::case_2:
	movl	%edi, %eax
	andl	$63, %eax
	cmpl	$63, %edi
	cmovael	%edi, %eax
	retq

playground::case_3:
	movl	%edi, %eax
	retq

playground::case_4:
	movl	%edi, %eax
	retq

```
Repository: vscode
Issue: Git - Expose git.publish as a command through Git API
Labels: help wanted,feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

The `git.publish` command would be very helpful to have in the API itself.  Right now, push is very limited in that everything needs to already be set up for the user before we can push, but publish has a really great UI experience to help the user with everything.
Repository: TypeScript
Issue: Allow non-identifiers to be used for JSXFragmentFactory
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

JSX factory expression identifier string JSXFragmentFactory

## Related Issues
https://github.com/Microsoft/TypeScript/issues/20469
https://github.com/microsoft/TypeScript/pull/38720

## Suggestion

Allow non-identifiers to be used as the JSXFragmentFactory. Currently, attempting to use a non-identifier like the empty string results in the following error:
```
  tsconfig.json(9,27): error TS18035: Invalid value for 'jsxFragmentFactory'. '''' is not a valid identifier or qualified-name.
```

My config:
```json
{
  "include": ["src", "types"],
  "compilerOptions": {
    "module": "esnext",
    "target": "esnext",
    "moduleResolution": "node",
    "jsx": "preserve",
    "jsxFactory": "createElement",
    "jsxFragmentFactory": "''",
    "lib": ["esnext", "dom"],
    "baseUrl": "./",
    /* paths - If you configure Snowpack import aliases, add them here. */
    "paths": {},
    /* noEmit - Snowpack builds (emits) files, not tsc. */
    "noEmit": true,
    /* Additional Options */
    "strict": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true,
    "allowSyntheticDefaultImports": true,
    "importsNotUsedAsValues": "error"
  }
}
```

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->
My JSX framework defines the `Fragment` tag as the empty string. Babel’s JSX support allows non-identifiers to be used as the JSXFragmentFactory so I wonder why we can’t do the same in TypeScript.

Using an identifier is a little more awkward.

## Examples

With the `jsxFactory` set to `createElement` and the `jsxFragmentFactory` set to the empty string, emitted code might look like the following.

```tsx
createElement(
  "",
  null,
  createElement("div", null),
  createElement("div", null),
);
```

## 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
* [ ] 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, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: Adding "-v" flag to drive-examples command hangs
Labels: p: tooling,package,team-ecosystem,P2,triaged-ecosystem

Steps to reproduce:
1. Apply this diff to https://github.com/flutter/plugin_tools/blob/master/lib/src/drive_examples_command.dart
```git
diff --git a/lib/src/drive_examples_command.dart b/lib/src/drive_examples_command.dart
index 59c6422..8b1fa36 100644
--- a/lib/src/drive_examples_command.dart
+++ b/lib/src/drive_examples_command.dart
@@ -120,7 +120,7 @@ Tried searching for the following:
             }
           }
 
-          final List<String> driveArgs = <String>['drive'];
+          final List<String> driveArgs = <String>['drive', '-v'];
 
           final String enableExperiment = argResults[kEnableExperiment];
           if (enableExperiment.isNotEmpty) {
```
2. Activate flutter_plugin_tools using local path:
`pub activate global -s path <path_to_plugin_tools_dir>`

3. In flutter/plugins directory, run `./script/incremental_build.sh drive-examples`, during running the drive test for the first plugin, the process hang at 
```
[ +100 ms] Running "flutter pub get" in example...
[   +4 ms] Using /Users/ychris/flutter/flutter/.pub-cache for the pub cache.
[   +1 ms] executing: [/Users/ychris/flutter/plugins/packages/android_alarm_manager/example/] /Users/ychris/flutter/flutter/bin/cache/dart-sdk/bin/pub --verbose get --no-precompile
[ +107 ms] MSG : Resolving dependencies...
```

After some investigation, it is caused by https://github.com/flutter/plugin_tools/blob/master/lib/src/drive_examples_command.dart#L150
If we replacing this method with https://github.com/flutter/plugin_tools/blob/master/lib/src/common.dart#L397, the hang is fixed.

Note that it is an issue with plugin_tools, running `flutter drive -v` directly on a project works. So it is **NOT** a flutter_tools issue.
Repository: TypeScript
Issue: Incorrect error on legitimate type overlap
Labels: Suggestion,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.0-dev-20201102

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

This condition will always return 'false' since the types 'X' and 'Y' have no overlap.

**Code**

```ts
function fn<T>(t: T) {
    return t === '' // error
}

fn('') // but here we pass it
```

https://www.typescriptlang.org/play?jsx=0#code/GYVwdgxgLglg9mABMMAeAKgPgBRQFyLoCUiA3gFCJWIBOAplCDUlIgLweIDkXiA9H0R0aNODXIBfcuRTYeJAYgDuYgNYBnIA

**Expected behavior:**

It works when we extend `unknown`. While this works on simple generics, it becomes inconvenient when the type parameter is nested deeper in a type structure.

```ts
function fn<T extends unknown>(t: T) {
    return t === '' // works
}

fn('') // works
```

https://www.typescriptlang.org/play?jsx=0#code/GYVwdgxgLglg9mABMMAeAKogpgDylsAEwGdFwBrMOAdzAD4AKKALkXQEpEBvAKEX8QAnLFBCCkURAF4ZiAORzEAeiWJqcQeWI8Avjx4oGCzirUatQA

**Actual behavior:**

> `This condition will always return 'false' since the types 'T' and 'string' have no overlap.`

**Related issues**
https://github.com/microsoft/TypeScript/issues/27910
Repository: react
Issue: Bug: can not pass some special custom attribute such as `size` 
Labels: Component: DOM,Status: Unconfirmed,Type: Discussion

As we know after react 16 we can use any custom attributes in dom elements 
but there is a bug which some special attributes (such as `size`) are not forwarding to dom element

![screenshot](https://user-images.githubusercontent.com/30382711/98168556-f91f3d80-1eff-11eb-8518-5647cd854e00.png)


React version: 16.13 & 17.0

## Steps To Reproduce

1. render a dom element with some custom attributes including `size`
2. inspect output and you will see your custom attributes but size

Link to code example:
https://codesandbox.io/s/setting-size-as-custom-attr-hdom2?file=/src/App.js

## The current behavior
`size` attribute will not show in output

## The expected behavior
`size` should be in output
Repository: flutter
Issue: Can't add Flutter module in Android with many sub apps
Labels: c: new feature,framework,engine,a: existing-apps,c: proposal,P3,team-engine,triaged-engine

So, I've create a Flutter module following the procedure here

https://flutter.dev/docs/development/add-to-app/android/project-setup

and if I create a new simple android project where the root is named 'app' I can add dependency to my flutter module and all is working good.

Problem is that it's not the current config I have in the main project
Mains project is composed of Many application that are all depending on one main library, and we also have other library for separation of concernt, like model layer, and data sources, so it look like this.

```
:app:app1                   // Application
:app:app2                  // Application
:app:app3                  // Application
:app:app4                  // Application
:UI_Presentation.      // Library
:Model                       // Library
:DataSource.            // Library
```

Most of the code is in UI_Presentation

Since I want to merge IOS and android team, I would like to be able to start writing common code in dart/flutter. Not there yet for IOS but, for Android, I would like the UI_Presentation to depend on the flutter module

Still can't find a way to make it work!

I've tried to put the 'flutter.hostAppProjectName' in each app gradle.properties. this look to work, but still can link the module in the settings.gradle, Tried to create a settings.gradle for each app, still no luck, don't even seem to be taken into account!

If I add 
```
setBinding(new Binding([gradle: this]))
evaluate(new File(
        settingsDir.parentFile,
        'flutter_module/.android/include_flutter.groovy'
))
```
it won't compile

I was expecting to be able to have something like this:

```
project gradle.properties:
flutter.hostAppProjectName=UI_Presentation 

settings.gradle:
setBinding(new Binding([gradle: this]))
evaluate(new File(
        settingsDir.parentFile,
        'flutter_module/.android/include_flutter.groovy'
))
```
Nothing work... From what I understand, you can't do that on an android library!

error :

```
Caused by: org.gradle.internal.event.ListenerNotificationException: Failed to notify project evaluation listener.

A problem occurred configuring project ':UI_Presentation'.
> Failed to notify project evaluation listener.
   > Could not get unknown property 'applicationVariants' for extension 'android' of type com.android.build.gradle.LibraryExtension.
```

Please help!
Repository: flutter
Issue: Felt snapshot is frequently invalid
Labels: engine,P3,team-engine,triaged-engine

Pretty much every day I have to delete `.dart_tool/felt.snapshot` because I get a "Signature mismatch" error when trying to run `felt`. We should improve felt's snapshot invalidation logic to make this happen less often.

/cc @nturgut
Repository: vscode
Issue: [json] UI for anyOf settings tooltips needs improvement
Labels: feature-request,json

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
Version: 1.50.1 (system setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

Note: I am aware of #92823, but this is a larger issue with settings tooltips for anyOf settings. I am about to go fix that specific case by writing extra description for that particular setting.

Steps to Reproduce:

1. Go into the user settings page and search for font ligatures; click on the item there
2. You get this, and think you can only turn it on/off: [caption: "Enable/Disable font ligatures" in a tooltip for `editor.fontLigatures` on a line with `"editor.fontLigatures": null`]
![image](https://user-images.githubusercontent.com/6652840/98171651-f0e5e480-1ea4-11eb-9c54-4919f1c79067.png)
3. Find out somehow that it allows strings and get this [also, assuming you think of mousing over it once you put the RHS in]? But what's a font-feature-settings [requires the user has domain knowledge of CSS]? [caption: "Explicit font-feature-settings" in a tooltip for `editor.fontLigatures` on a line with `"editor.fontLigatures": ""`]
![image](https://user-images.githubusercontent.com/6652840/98171692-fe9b6a00-1ea4-11eb-8aa9-e3d4b3bb8653.png)

Additionally, if you were to type in "editor.fontLigatures" and see the intellisense, it wouldn't help much: [caption: "Configures font ligatures or font features" in an intellisense box as a suggestion for "editor.font"]

![image](https://user-images.githubusercontent.com/6652840/98171869-45895f80-1ea5-11eb-82bc-aeb33738e487.png)

A PR is incoming to change all three of these strings to mitigate the UI issue for `editor.fontLigatures` specifically, but the UI should also be changed in these tooltips so it shows the description (last screenshot) above both the string and boolean setting types. I'm not proficient enough in TypeScript/VSCode internals to know where to start investigating the tooltip, so I'd appreciate if someone takes this on.

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
Yes
Repository: rust
Issue: Deduplicate code that finds the return type of a future
Labels: C-cleanup,T-compiler,A-async-await,AsyncAwait-Triaged

I've noticed a lot of code being added to different parts of the compiler that all does the same thing.. gives you the return type of an async fn. This issue is to keep track of all those places and eventually deduplicate them.
Repository: flutter
Issue: RenderParagraph does not scale WidgetSpan semantics node correctly when the textscalefactor > 1
Labels: framework,a: accessibility,P2,team-framework,triaged-framework

```dart
import 'package:flutter/gestures.dart';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Directionality(
      textDirection: TextDirection.ltr,
      child: Center(
        child: Container(
          color: Colors.green,
          child: RichText(
            text: TextSpan(
              children: [
                WidgetSpan(
                  child: Column(
                    children: <Widget>[
                      Semantics(container: true ,child: Text('line1'),),
                      Semantics(container: true ,child: Text('line2'),),
                      Semantics(container: true ,child: Text('line3'),),
                      Semantics(container: true ,child: Text('line4'),),
                    ],
                  )
                ),
              ],
            ),
            textScaleFactor: 4,
          ),
        ),
      ),
    );
  }
}
```

turn on talkback/voiceover, and then the rect does not match the children.