sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Ignored error in class constructor causes method usage errors to be ignored
Labels: Bug

**TypeScript Version:**  3.5.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
ts-ignore in class constructor
class method no error on parameter usage

**Code**

```ts
class Foo {
  bar: string
  constructor(bar: string) {
    this.bar = bar
  }

  baz(buzz: number) {
    return buzz + 1
  }
}

// @ts-ignore
const instance = new Foo()
instance.baz('buzz')
```

**Expected behavior:**
The invocation of `instance.baz('buzz')` should report that the parameter should be a `number` instead of a `string`.

**Actual behavior:**
There is no error on that line.
If I fix the ts-ignore on the line above, it then reports the error correctly.

**Playground Link:** 
http://www.typescriptlang.org/play/?ts=3.8.0-dev.20200116#code/MYGwhgzhAEBiD29oG8BQ1oCMwCcBc0EALjgJYB2A5utMPOcTgK7BHw4AU2+hJFlAShQ0MRABakIAOm7QAvFlw0AvqhrYAXlyYaNBckwC2mAKY4haDBhwmiTHOSw6N0ANTQAjCtSrUAej9oAAEiCABaUkpydhNUOgYiaApiMHJgE3lochMAdzhEDgFUZKJU9JkwLQByTGcqgSA

**Related Issues:** 
Could not find any through Google or here.
Repository: vue
Issue: Generate distinct paths for supporting .vue files in sourcemaps
Labels: discussion,improvement

### What problem does this feature solve?
Hello Vue 👋

I'm working on our [new JavaScript debugger](https://github.com/microsoft/vscode-js-debug) for VS Code, and ran into some problems when trying out Vue. The default vue-cli setup creates several supporting .vue scripts. For instance, open the Chrome devtools and ctrl p for "App.vue" in a new project. The top entry is the correct Vue file, the others aren't.

![](https://memes.peet.io/img/Screen%20Shot%202020-01-17%20at%2011.47.46%20AM.png)

From the VS Code perspective, the user might ask us to set a breakpoint in a Vue file. We know which file the breakpoint is attached to on disk, and we need to figure out which loaded file that breakpoint gets mapped to. However, because all these paths are quite similar and all (in the context of a generic web app) possibly the file we want, we end up putting the breakpoint in the wrong file and breaking in the incorrect place. And often the supporting scripts evaluate before the 'real' script does, so we can't, for example, wait and pick the best match from the possible candidates.

### What does the proposed API look like?
The simplest solution would be to prefix the supporting files with some path like `__vue__`, or something along those lines. This would prevent the paths from incorrectly mapping to files that exist on disk.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: `#[used]` should work on functions
Labels: A-linkage,A-attributes,T-lang,C-feature-request,WG-embedded

Currently `#[used]` only works on static items. It would be more consistent and useful if it also worked on functions.

My motivation for this is to prevent some cases of user errors when using `cortex-m-rt`'s `#[exception]` and `#[interrupt]` attributes. As can be seen in [this test](https://github.com/rust-embedded/cortex-m-rt/blob/master/tests/compile-fail/default-handler-hidden.rs), it is possible to use those inside of private modules, which results in the function never ending up in the binary.

Note that `#[used]` cannot be made to work on functions that have generics in scope, since those can end up producing arbitrary monomorphizations depending on the parameters (and there's no single canonical thing that `#[used]` would make show up in the binary).
Repository: flutter
Issue: [a11y] matchesSemantics is missing fields on SemanticsNode, such as transform
Labels: a: tests,framework,a: accessibility,P3,team-framework,triaged-framework

Ideally, matchesSemantics has every field on SemanticsNode
Repository: flutter
Issue: Cannot detect taps on PlatformViews
Labels: framework,f: gestures,a: platform-views,P2,a: plugins,team-framework,triaged-framework

If you have a `GestureDetector` parent of a `PlatformView`, then the `onTap` of the `GestureDetector` is not called even when the `PlatformView` has no gesture detectors. I wrote a test case showing the issue:

```dart
    testWidgets('PlatformViewSurface works with GestureDetector parent', (WidgetTester tester) async {
      bool tapAcceptedByParent = false;
      await tester.pumpWidget(
        Align(
          alignment: Alignment.topLeft,
          child: Container(
            margin: const EdgeInsets.all(10.0),
            child: GestureDetector(
              onTap: () {
                tapAcceptedByParent = true;
              },
              child: SizedBox(
                width: 200.0,
                height: 100.0,
                child: PlatformViewSurface(
                  controller: controller,
                  gestureRecognizers: const <Factory<OneSequenceGestureRecognizer>>{},
                  hitTestBehavior: PlatformViewHitTestBehavior.opaque),
              ),
            ),
          ),
        ),
      );

      final TestGesture gesture = await tester.startGesture(const Offset(50.0, 50.0));
      await gesture.up();

      expect(tapAcceptedByParent, true);
      expect(
        controller.dispatchedPointerEvents,
        isEmpty,
      );
    });
```

The test case fails both `expect`s.

@amirh suggested changing the `GestureDetector`'s `behavior` to `HitTestBehavior.opaque` and the `PlatformViewSurface`'s `hitTestBehavior` to `PlatformViewHitTestBehavior.transparent`, which causes the test to pass, but I'm not 100% sure why.
Repository: pytorch
Issue: Migrate processGroup::async_work to use Future
Labels: oncall: distributed,triaged

Now we have generic Future in pyTorch codebase, see PR #29579. 

We can consider to migrate processGroup::async_work to use Future as well, so that we have generic handling for async work processing, and benefit from all the future improvement of the generic Future like timer and error handling and etc. 


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar
Repository: vscode
Issue: Readonly ranges/lines in the editors
Labels: feature-request,editor-core

In the Cosmos DB extension exploration, documents are opened as JSON files, which can be edited

![image](https://user-images.githubusercontent.com/2230985/72649220-eb2d0b80-3931-11ea-9c12-feabda6d8205.png)

They may have user defined properties, as well as several database-defined properties. Editing these is possible, and _may_ be desired for the `_etag`, but in general will have no effect, be ignored, or break things in odd ways. On the other hand, it's not appropriate to omit these entirely, as it can be useful to reference or copy.

It could be helpful to have readonly ranges within the editor to help users understand that changes made within these fields have no affect.

Readonly ranges also came up a few days ago in the context of @JacksonKearl's search editor a few days ago.
Repository: pytorch
Issue: Make _rpc_sync_torchscript and _rpc_async_torchscript work with autograd profiler
Labels: oncall: jit,triaged

This is to follow up PR #32197, we should make the torch script call work with auto grad profiler. 


cc @suo
Repository: godot
Issue: Selection doesn't work as well while freelooking in the viewport
Labels: bug,topic:editor,confirmed,usability,topic:3d

**Godot version:**

Godot 3.2 RC1

**OS/device including version:**

Windows 10 1903

**Issue description:**

Commit #34801 made me aware of the ability to select nodes while freelooking in the viewport. However, it seems that the ability to select things is significantly less accurate while freelook is active.

For example, in this test scene I included it's easy to select the small boxes from a fair distance away. However, while freelooking (i.e. while the right mouse button is held) their selection is only possible from close up.

Without freelook I select the box easily:
![Annotation-1](https://user-images.githubusercontent.com/6045198/72651353-b7a9ab80-3948-11ea-9904-403f3473295e.png)

While freelooking I can't select the box, only the larger mesh underneath:
![Annotation-2](https://user-images.githubusercontent.com/6045198/72651359-bbd5c900-3948-11ea-981e-aefea1165efe.png)


**Steps to reproduce:**

1. Open the "Selection Issues" project.
2. Attempt to select a few boxes from reasonably far away.
3. Now attempt to select the same boxes while freelooking (i.e. holding the right mouse button down) from the same camera position.

**Minimal reproduction project:**

[Selection Issues.zip](https://github.com/godotengine/godot/files/4079431/Selection.Issues.zip)
Repository: rust
Issue: LLVM error compiling core and builtin functions using 16-bit pointers in data layout
Labels: A-LLVM,T-compiler,C-bug

I'm trying to compile Rust code to run in 386 real mode, where pointers larger than 2^16 aren't meaningful, even though there are 32-bit registers to work with. It works if I use full 32-bit pointers, but this is quite wasteful, so I've written my target JSON file to specify 16-bit pointers with 16-bit alignment in the LLVM data layout, and set ``target-pointer-width`` to 16. However, I get errors from LLVM itself trying to compiler certain functions in ``core`` and ``builtins``.

```
LLVM ERROR: Cannot select: 0x7f962aae09c0: i16 = GlobalAddress<<{ [8 x i8], i8*, [2 x i8] }>* @anon.d1d52a4f9fbe2e9a9c47ed4caed11e39.2.llvm.4753579327427470583> 0
In function: _ZN4core3num7dec2flt3num21compare_with_half_ulp17h4eb4cc321c32da3aE
error: could not compile `core`.
warning: build failed, waiting for other jobs to finish...
LLVM ERROR: Cannot select: 0x7f75cd47f2d8: i16 = FrameIndex<-1>
In function: _ZN51_$LT$u64$u20$as$u20$compiler_builtins..int..Int$GT$12extract_sign17hef80dd72940759b7E
error: could not compile `compiler_builtins`.
```
Repository: TypeScript
Issue: No error from noUnusedLocals option on ambient local variable in module file
Labels: Bug

<!-- 🚨 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:**  3.7.x-dev.20200116

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
export { }

declare const Array: void;
```

**Expected behavior:**
error
**Actual behavior:**
pass
**Playground Link:** https://www.typescriptlang.org/play/index.html?noUnusedLocals=true&ts=3.8.0-dev.20200116&ssl=1&ssc=1&pln=3&pc=27#code/KYDwDg9gTgLgBAbzgXwFCoCbAMYBsCGUwc2EAdgM7wCCUU+AngFxwBuEAlhgNxA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: flutter
Issue: Make the _DatePickerDialog easier to driver with Flutter driver
Labels: a: tests,framework,f: material design,f: date/time picker,t: flutter driver,a: quality,c: proposal,P3,team-design,triaged-design

The Material date picker dialog is pretty hard, verging on impossible (to selected dates from previous/future years) to control via the Flutter Driver due to the lack of keys on some elements.

It would be great to have keys on the main elements so that they can be tapped by the driver.  The useful elements to have well known keys on are highlighted below:

![image](https://user-images.githubusercontent.com/3694497/72656515-c72fff80-39ef-11ea-9d2b-f77498c84264.png)

Having well known keys on these elements would make it easier to figure out the currently selected date and subsequently what driver actions to take to pick another date before or after the current date.

I'm happy to do a PR for this so let me know any thoughts or if I have missed something simple with driving this element with the driver.

As an example to selected a date around the current date I currently have to do this, which is pretty horrid and would be made a lot easier if I was able to use a key to get the currently selected date and year.  Then I would also be able to driver the widget to select a date far in the past or future by being able to tap the year button, select a year then month and day etc.

```
    final monthYearText = DateFormat.yMMMM(locale).format(dateToSelect);

      await runZoned(
        () async {
          await world.driver.scrollUntilVisible(
            find.byType('PageView'),
            find.text(monthYearText),
            dxScroll: 200,
            timeout: const Duration(seconds: 10),
          );
        },
        onError: (dynamic error, dynamic stack) async {
          await world.driver.scrollUntilVisible(
            find.byType('PageView'),
            find.text(monthYearText),
            dxScroll: -500,
            timeout: const Duration(seconds: 20),
          );
        },
      );

      await world.driver.tap(
        find.text(day.toString()),
        timeout: const Duration(seconds: 2),
      );

      await world.driver.tap(
        find.text('OK'),
        timeout: const Duration(seconds: 2),
      );
```

At the moment the above code just relies on blind luck to select a date (which has to be fairly close to the current date) which leads to unstable tests.


Note: running tests on the current stable branch.

Jon
Repository: flutter
Issue: [Web] Stuck at "Attempting to connect to browser instance"
Labels: tool,platform-web,P2,team-web,triaged-web

My web project compiles without error, but on launch, the browser opens with a blank page and Android Studio shows "Attempting to connect to browser instance" indefinitely.

Just ran Flutter upgrade now.

The console in the browser shows
```
Uncaught TypeError: Cannot read property 'core' of undefined
    at comparators.ddc.js:3
    at Object.execCb (require.js:1696)
    at Module.check (require.js:878)
    at Module.enable (require.js:1176)
    at Module.init (require.js:788)
    at callGetModule (require.js:1203)
    at Object.completeLoad (require.js:1590)
    at HTMLScriptElement.onScriptLoad (require.js:1717)
require.js:143 Uncaught TypeError: Cannot read property 'core' of undefined
    at utils.ddc.js:3
    at Object.execCb (require.js:1696)
    at Module.check (require.js:878)
    at Module.enable (require.js:1176)
    at Module.init (require.js:788)
    at callGetModule (require.js:1203)
    at Object.completeLoad (require.js:1590)
    at HTMLScriptElement.onScriptLoad (require.js:1717)
require.js:143 Uncaught TypeError: Cannot read property 'core' of undefined
    at typed_buffers.ddc.js:3
    at Object.execCb (require.js:1696)
    at Module.check (require.js:878)
    at Module.enable (require.js:1176)
    at Module.init (require.js:788)
    at callGetModule (require.js:1203)
    at Object.completeLoad (require.js:1590)
    at HTMLScriptElement.onScriptLoad (require.js:1717)
require.js:143 Uncaught TypeError: Cannot read property 'core' of undefined
    at hash.ddc.js:3
    at Object.execCb (require.js:1696)
    at Module.check (require.js:878)
    at Module.enable (require.js:1176)
    at Module.init (require.js:788)
    at callGetModule (require.js:1203)
    at Object.completeLoad (require.js:1590)
    at HTMLScriptElement.onScriptLoad (require.js:1717)
```
Repository: TypeScript
Issue: Allow `#`-private names in parameter property positions
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 -->
hard privacy  https://github.com/microsoft/TypeScript/issues/31670

## Suggestion

allow create `hard privacy` like we do `private` in `constructor(private foo: number)`

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

allow use `constructor(#foo: number) {}`  or `constructor(private #foo: number) {}` or `constructor(hard private #foo: number) {}`

for same as

```ts
#foo: number;
constructor(foo: number) {
		// This works.
		this.#foo = foo;
	}
```

---

```ts
class C {
	constructor(#foo: number) {}

	log() {
		console.dir(this.#foo);
		return this
	}
}

let o = new C(777).log();

// error
o.#foo;
```

same as

```ts
class C {
	#foo: number;

	constructor(foo: number) {
		// This works.
		this.#foo = foo;
	}

	log() {
		console.dir(this.#foo);
		return this
	}
}

let o = new C(777).log();

// error
o.#foo;
```

## 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.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: [webview_flutter] add onReceivedTitle
Labels: c: new feature,p: webview,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

need a way to get title in time,
android webview and ios wkwebview both provide the callback to listen the changes of title.
Repository: rust
Issue: --pretty=expanded fails after calling cbindgen in cdylib crate
Labels: A-pretty,T-compiler,requires-nightly

# Preface

This one is a bit of a doozy and I can't tell if it's a rustc issue or a cbindgen issue or both, so I'm going to cross-report them so both projects can be aware.

I don't have a minimal reproduction, but it is easily reproducible in my repo.

Repo: https://github.com/BVE-Reborn/bve-reborn
Working Commit: [`52b3ec6`](https://github.com/BVE-Reborn/bve-reborn/commit/52b3ec6c232198e7585909f20404b9ee5323bdab)
Failing Commit: [`7799c04`](https://github.com/BVE-Reborn/bve-reborn/commit/7799c04340edefcd52c51023e1271c0bb67d5ad1)

The only difference is the addition of the crate type of `cdylib`. (`rlib` is there, but it reproduces on my next commit which removed it)

# System Info

`Xubuntu 18.04`

Rust and Cargo locked to `nightly-2020-01-16`
rustc: `rustc 1.42.0-nightly (3291ae339 2020-01-15)`
cargo: `cargo 1.42.0-nightly (ad3dbe10e 2020-01-13)`

CBindgen latest, compiled on the same nightly toolchain:
`cbindgen 0.12.2`

# Repro

The rustc command is the exact command cbindgen runs to get macro expanded data.

This all takes place in the root of my repo.

```
cargo build
cargo rustc --lib --manifest-path bve-native/Cargo.toml  -p "bve-native:0.0.0-Placeholder" "--verbose" -- -Z unstable-options --pretty=expanded 
```

Both succeed as expected. However if you call cbindgen it fails, and the rustc no longer outputs anything at all.

```
# Succeeds
cargo build

# Fails citing an issue with compiling
# Occasionally must be run twice
cbindgen bve-native/ -c bve-native/cbindgen.toml -v

# Returns zero, but outputs nothing.
cargo rustc --lib --manifest-path bve-native/Cargo.toml  -p "bve-native:0.0.0-Placeholder" "--verbose" -- -Z unstable-options --pretty=expanded 
# You can call ^ as many times as you want, it will always fail
```

The problem goes away when you `cargo clean` and reappears by running cbindgen again.

# Comments

I have no idea what or who is causing this issue.

I feel like even if cbindgen is ultimately the "cause" of the bug, the expansion shouldn't be able to fail and not output anything without erroring (and returning `!= 0`) in some way.

# Notes:

Possibly relevant cbindgen code: https://github.com/eqrion/cbindgen/blob/master/src/bindgen/cargo/cargo_expand.rs#L129
cbindgen issue: https://github.com/eqrion/cbindgen/issues/457

Thanks!
Repository: create-react-app
Issue: Need to credit caniuse-lite in produced web app?
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

I'm not expert on software licenses, but from what I gathered, when deploying an javascript application bundle to production and serving it on a web server, this counts as distribution of statically linked software, where I need to follow the licenses of all javascript npm packages used by my project. So when I'm using create-react-app in my application, most dependencies are MIT or similar, which cause no issues. But there is an exception: [caniuse-lite](https://github.com/ben-eb/caniuse-lite) has CC-BY-4.0 license, which states the need to **give explicit credit to the author when distributing the software**. Does this mean that all projects using create-react-app need to provide such credits somewhere in the web application they are producing? Or am I misunderstanding something?

### Describe the solution you'd like

 If so, then I think we should state somewhere in the documentation of create-react-app that the users need to credit caniuse-lite or caniuse.

### Describe alternatives you've considered

I've already [contacted caniuse-lite](https://github.com/ben-eb/caniuse-lite/issues/40) but they say it's the license coming from the mother project caniuse.
Also caniuse are not willing to change this:
https://github.com/Fyrd/caniuse/issues/4062
Repository: go
Issue: x/crypto: add BLAKE3 support
Labels: NeedsDecision,FeatureRequest

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sh7dm/.cache/go-build"
GOENV="/home/sh7dm/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/sh7dm/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build981542473=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?
I found a new cryptographical hash function named BLAKE3:
https://github.com/BLAKE3-team/BLAKE3
It also has Go implementation:
https://github.com/lukechampine/blake3

### What did you expect to see?
BLAKE3 support in Go

### What did you see instead?
No BLAKE3 support in Go