sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Private Members with Default Value on Class Extension Compiles with Member declarations before Super call if function is called before super
Labels: Bug

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.3.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
* "Private member compile"
* "Private Properties before super"
* "compile class extension"
* "constructor order at compile time"
* "functions before super call"
**Code**

```ts
function example ( number: number ) {
    return number;
} 
class ExtString extends String {
    private x: number;
    private y: number = 10;
    z: number;
    constructor(...args){
        example(args[0]);
        super(...args);
        this.z = 19;
    }
}
```

**Expected behavior:**
I would expect that when the above code compiles, that the private members get initialized with values after the super call like below: 

```
function example(number) {
    return number;
}
class ExtString extends String {
    constructor(...args) {
        example(args[0]);
        super(...args);
        this.y = 10;
        this.z = 19;
    }
}
```

**Actual behavior:**
the private members which have values gets assigned to before the super call. This behaviour only happens when I call a function before a super call, even if said function does not alter `this` in the code (like below). 

```
function example(number) {
    return number;
}
class ExtString extends String {
    constructor(...args) {
        this.y = 10;
        example(args[0]);
        super(...args);
        this.z = 19;
    }
}
```
This results in a compile time error. 

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
I found a similar bug that is referenced here [#8277](https://github.com/Microsoft/TypeScript/issues/8277)
Repository: ant-design
Issue: Select组件tag模式下，可以用鼠标或者方向键 选中已输入的tag，并且复制
Labels: Inactive

- [ ] 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?
很多情况想复制Select tag模式下的tag。但是目前无法选中。

最根本的诉求是可以复制选中的tag或者全选tag，就像input标签中的文字一样，然后在复制。
可以指定 分隔符="," 来合并成成一段文本放到剪切板

### What does the proposed API look like?
添加props
// textSelectable用于判定是否可以选中 
textSelectable:boolean = false,
// textJoinToken用于表示选中的字已何种形式连接并复制在剪切板
textJoinToken:string = ","


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: scrcpy
Issue: Remote Control API
Labels: feature request

We're currently using scrcpy to perform a series of QA tests. We use it to stream the screen content in one direction and user inputs in the other direction. While this works well, the tasks are quite repetive and so we started writing some automations for this.

Something like: If (screen shows x) then click(x, y).

To do so we have written an external software that copies the screen content from scrcpy and eventually send events like mouse clicks to it. While this works more or less sufficient for our needs, it still lacks some features. For example, we must keep the scrcpy window shown (i.e. not minimized) and the user must keep the mouse still while the automation is in progress. Also, we haven't found a way to input multi touch gestures.

It would be very handy if the scrcpy comes as library (or with a library) or exports that would allow a programmatic extraction of data and supplying input data to it.

Any thoughts about it? It shouldn't be that complicated and I'm willing to help, but at the moment I have no idea how much work this will be in the end or whether this is already possible in some way.
Repository: go
Issue: cmd/go: clarify the impact of the -tags flag on test/build caching
Labels: Documentation,help wanted,NeedsFix

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +4b3f04c
</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
GOARCH="amd64"
GOBIN=""
GOCACHE="~/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="~"
GOPROXY=""
GORACE=""
GOROOT="~/go"
GOTMPDIR=""
GOTOOLDIR="~/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
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-build224479533=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?
Read the documentation for build/test caching from `go help test`. Then

```
$ go test -tags noasm gonum.org/v1/gonum/mat
ok  	gonum.org/v1/gonum/mat	44.695s
$ go test -tags noasm gonum.org/v1/gonum/mat
ok  	gonum.org/v1/gonum/mat	(cached)
```

From this it's clear that `-tags` is not counted in test flags (and this is reasonably given the wording).

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

### What did you expect to see?
No caching.


### What did you see instead?
Happily, caching.


While the wording is consistent with the apparent intended meaning, it could be made clearer that build flags do not impact on caching for tests (if this is true - I could find no mention of caching in `go help build` or `go help install` or mention of which flags prevent caching (other than `-a` in  `go help cache`)).
Repository: go
Issue: cmd/compile: eliminate memory allocation for non-int n in slice extension idiom
Labels: Performance,NeedsFix,compiler/runtime

The slice extension idiom from #21266 doesn't work in go tip for non-int `n` in `append(a, make([]T, n)...)`:

```go
func BenchmarkExtendInt(b *testing.B) {
        var buf []byte
        b.ReportAllocs()
        n := int(12345)
        for i := 0; i < b.N; i++ {
                buf = append(buf[:0], make([]byte, n)...)
        }
}

func BenchmarkExtendUint64(b *testing.B) {
        var buf []byte
        b.ReportAllocs()
        n := uint64(12345)
        for i := 0; i < b.N; i++ {
                buf = append(buf[:0], make([]byte, n)...)
        }
}
```

Benchmark results:
```
BenchmarkExtendInt-4      	10000000	       145 ns/op	       0 B/op	       0 allocs/op
BenchmarkExtendUint64-4   	 1000000	      1576 ns/op	   13568 B/op	       1 allocs/op
```

As you can see, if `n` has a type other than `int`, go doesn't remove the allocation.
Repository: TypeScript
Issue: symbolToName does handle exports of namespaces
Labels: Bug,Domain: Declaration Emit

**TypeScript Version:**  3.2.2

**Search Terms:** symbolToName, exports, declaration, `.d.ts`

TypeScript cannot emit the name for a symbol that's declared in an inner namespace but re-exported in the outer namespace. That is, emitting the type name of a symbol does not take an alias created by an `export {x as y}` statement into account.

This comes up when trying to use the `chrome.debugger` declaration file. Because `debugger` is a reserved keyword, the `.d.ts` is defined using a fake, unexported inner namespace called `_debugger`, and re-exports it using `export {_debugger as debugger};`. TypeScript then cannot produce `.d.ts` files when trying to generate the name for a symbol.

**Code**

```ts
// decl.d.ts
declare module chrome {
  namespace _debugger {
    export class Foo {}
  }
  export function getFoo(): debugger.Foo;
  export {_debugger as debugger};
}

// user.ts
export const x = chrome.getFoo();
```

Run `tsc --declaration`.

**Expected behavior:**

```
// user.d.ts
export declare const x: chrome.debugger.Foo;
```

**Actual behavior:**

```
test.ts:1:14 - error TS4025: Exported variable 'x' has or is using private name '_debugger.Foo'.

1 export const x = chrome.getFoo();
               ~
```

**Playground Link:** n/a

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: flutter
Issue: Feature Request: publish flutter package as a native framework to cocoapods
Labels: c: new feature,platform-ios,tool,a: existing-apps,t: xcode,P3,team-ios,triaged-ios

Support a native command to publish a package to cocoapods so native apps can also use it hassle-free.

Fastlane could be a huge help to publish it easily and upgrade versions etc.

A native app should be able to consume my package with just adding a simple pod into his Podfile.
`pod "MyPod"`
Repository: node
Issue: Create node/doc/guides/writing-docs.md
Labels: help wanted,doc,discuss

Currently we don't seem to have a guide for writing docs – or at least not one that I can find.

In the [`node/doc/guides`](https://github.com/nodejs/node/tree/master/doc/guides) directory, there seems to be examples for [writing and running benchmarks](https://github.com/nodejs/node/blob/master/doc/guides/writing-and-running-benchmarks.md) and [writing tests](https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md), but not one for writing docs.

I'd be happy to help take this on if someone could provide a list of bullets that would need to be addressed as steps to write docs within the file.
Repository: kubernetes
Issue: Handle recovery from resize failure
Labels: kind/bug,sig/storage,lifecycle/frozen

Currently when resize fails of a volume it keeps retrying indefinitely. This leads to two problems:

1. Unnecessary API usage for an action that is not going to succeed (for example when you are out of quota on cloud provider or out of bricks on glusterfs).

2. Sometimes user may want to retry volume expansion with lower value. For example - my current PVC is of 12GB and I tried to expand it to 40GB. But that failed. Now I want to retry volume expansion with 20GB except I can’t.


/sig storage

cc @bswartz @saad-ali
Repository: TypeScript
Issue: Add "find assignment references"
Labels: Suggestion,Domain: TSServer,Domain: Symbol Navigation,Rescheduled

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

find usage reference as LVALUE langauge services assignment read write

## Suggestion

Add a language feature that will find a variable/property "x" when assigned a value in the code (or otherwise is used as an LVALUE).

## Use Cases

Allows a user to find where a variable/property is **_set_** as opposed to **_defined_** or _**read**_.

## Examples

When searching in VSCode, and my cursor is on "name" in

`x = myPerson.name`

a "**find LVAUE references**" call _**would**_ return... 

`myPerson.name = "Jim";`
or
`this.name = "Ann";`
or
`myOtherPerson.name = "Arlo";`

but _**not**_ 

`class person { name: string; }`
or
`print(myPerson.name);`
or
`x = myPerson.name`
Repository: go
Issue: cmd/compile: misleading panic on deferred func
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +75f4aa86ba Thu Sep 27 22:02:08 2018 +0000 linux/amd64
</pre>


### What did you do?

https://play.golang.org/p/3aP7yqgWXdf


### What did you expect to see?

The panic stack trace should point to where a nil pointer was dereferenced.

### What did you see instead?

The panic stack trace pointed at an innocent line.


This is pretty similar to #14646 and #16011. The panic points at a line that is clearly quite capable of yielding that panic, so it led me on a wild goose chase. It took using gdb (gasp!) to figure out that the defer was involved. Consider this an argument for revisiting the "working as intended" judgment on #16011; it was a bug in my code, but the stack trace was very confusing.

If there was a way to indicate that the deferred function was being executed I would have spotted the issue earlier. The regular stack trace does not indicate that. gdb, however, shows `runtime.jmpdefer` as the immediate stack frame, which is how I figured it out.
Repository: terminal
Issue: Exiting from Full Screen mode incorrectly restores window size
Labels: Product-Conhost,Help Wanted,Area-Interaction,Issue-Bug,Priority-3,good first issue

Version 10.0.17763.253

Start cmd.exe
Enter command `mode 80, 25`
Go to window menu - Properties - Layout
Check that Window Size is 80 x 25 indeed
Close Properties
Press Alt+Enter twice to enter and exit full screen
Go to window menu - Properties - Layout
Check Window Size again. This time it's not 80 x 25, but 78 x 24.

This happens because exiting full screen restores the original **outer** window size (with the title, borders etc., say, 802 x 532px), however:
- Entering full screen increases the buffer size (which is fine)
- Exiting full screen doesn't change the buffer size (which is also fine)
- The console window now has to display scrollbars (also fine), but since it's outer size is the same it has to display them at the expense of console viewport area.

This causes an issue in an app that automatically syncs buffer size with window size - after every switch to full screen and back window size gets smaller, the app reduces the buffer size accordingly, eventually going down to nothing.
Also, even if an app doesn't do anything like that, reducing the viewport size can make some (potentially important) information invisible.

Please consider preserving the console viewport size and increasing the outer window size to make room for scrollbars.
Repository: go
Issue: cmd/go: trim go.sum without adding module requirements
Labels: NeedsDecision,FeatureRequest,modules

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?
go version go1.11.4 linux/amd64 

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64" 
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/user/go" 
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo" 
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/d/14-Workspace/go/github.com/F21/somerepo/go.mod"
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-build348706889=/tmp/go-build -gno-record-gcc-switches"
```
### What did you do?
1. Create go.mod: `go mod init github.com/F21/somerepo`.
2. Populate `go.mod` and `go.sum` by running `go test ./...`.
3. One of the dependencies `github.com/uber/jaeger-client-go` conflicts with another dependency, so I bumped it to master: `go get github.com/uber/jaeger-client-go@master`.
4. There are now 2 entries for `github.com/uber/jaeger-client-go` in my go.sum:
```
github.com/uber/jaeger-client-go v2.15.0+incompatible h1:NP3qsSqNxh8VYr956ur1N/1C1PjvOJnJykCzcD5QHbk=
github.com/uber/jaeger-client-go v2.15.0+incompatible/go.mod h1:WVhlPFC8FDjOFMMWRy2pZqQJSXxYSwNYOkTr/Z6d3Kk=
github.com/uber/jaeger-client-go v2.15.1-0.20190116124224-6733ee486c78+incompatible h1:b2A4zBpOpzqZoSlqlJ3OOe0yjd577TnQIHG1/KN7U8E=
github.com/uber/jaeger-client-go v2.15.1-0.20190116124224-6733ee486c78+incompatible/go.mod h1:WVhlPFC8FDjOFMMWRy2pZqQJSXxYSwNYOkTr/Z6d3Kk=
```
The `github.com/uber/jaeger-client-go v2.15.0+incompatible` entries are unnecessary as the project is now pinned to `github.com/uber/jaeger-client-go v2.15.1-0.20190116124224-6733ee486c78+incompatible (current master)`.

In https://github.com/golang/go/issues/26381, the ability to trim `go.sum` was added to `go mod tidy`. However, `go mod tidy` is something I avoid as it pulls in all test dependencies for all my dependencies and their dependencies for all platforms. Unfortunately, `go mod tidy` has burnt me quite a few times and causes a lot more problems than it solves.
See: 
- https://groups.google.com/forum/#!topic/golang-nuts/5otdvVra0xg
- https://github.com/golang/go/issues/27920

### What did you expect to see?
I'd like to be able to trim unneeded entries from go.sum without having to run `go mod tidy` as its current behavior causes a lot more problems than it solves.

### What did you see instead?
N/A.
Repository: TypeScript
Issue: [feature request] not sure how to word this: "infer generic arg type/constraint in wrapping type"
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## 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 -->

## Suggestion

Sometimes we want to wrap an existing type, where the existing type has generic type args that have constraints using `extends`.

## Use Cases

For example, this is material-ui's `WithStyles` type:

_____________

and I can wrap it like this to make one of it's properties optional:

```ts
// omit a set of keys from a type
type Omit<T, K extends keyof T> = Pick<T, Exclude<keyof T, K>>

// like Partial, but choose which keys are optional instead of making all of them optional
type Optionalize<T, K extends keyof T> = Omit<T, K> & Partial<Pick<T, K>>

// my wrapper type:
export type WithStyles_OptionalClasses<
  Style extends string | StyleRules | StyleRulesCallback = string,
  IncludeTheme extends boolean | undefined = false
> = Optionalize<WithStyles<Style, IncludeTheme>, 'classes'>
```

## Examples

But it'd be nice if we could just pass along the args, not having to re-define them. Maybe it would look like the following, and achieve the same thing:

```ts
export type WithStyles_OptionalClasses<Style, IncludeTheme> =
  Optionalize<WithStyles<Style, IncludeTheme>, 'classes'>
```

and it would take advantage of the fact that `WithStyles` already has the constraint, so if we pass something into `WithStyles_OptionalClasses` that doesn't meet the constraint defined by `WithStyles`, then it could throw an error just like when using `WithStyles` by itself.

## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code **not sure**
* [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
* [x] 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). **not sure**
Repository: rust
Issue: --emit=dep-info or some flag should include rlibs & externally linked files that will be used
Labels: T-compiler,C-feature-request

Currently, `--emit=dep-info` only shows source files that are included in the current crate. There should be another mode (or the behavior should be extended) to include all files that will be used by the equivalent non-`dep-info` invocation of `rustc`. This includes `rlibs` of all crates used by the build, both explicitly in `--extern` and brought in through lib search paths, as well as external object files etc. that may be linked in. This is necessary in order to add Rust support to remote compilers and compiler caches, which depend on the exact hashes of all files used in the build.

Note that AFAICT sccache currently works around this by relying on some behaviors of `cargo` and depending on all the libraries contained in link paths. (@luser / @alexcrichton please correct me if I'm wrong here). I'd like to instead ensure that we can ship the exact set of files needed for compilation, both of libraries, and for the final link step.

i'm sure what I've written above is probably partially incorrect and misrepresentative somehow, but hopefully others will correct my errors and we can work towards a solution together :)

cc @juliehockett @petrhosek
Repository: TypeScript
Issue: Generic type inference failure in a union.
Labels: Bug,Domain: Type Inference

<!-- 🚨 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 `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.3.0-dev.20190117

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** generic type inference, union types

**Code**

```ts
function f1<A1, B1>(cb: (a: A1, b: B1) => void) {
  f2(cb);  // I expect no errors
}

function f2<A2, B2>(cb: ((x: number, a: A2, b: B2) => void)|
                    ((a: A2, b: B2) => void)) {}  // If I swap the two types it compiles
```

**Expected behavior:**
No errors.

**Actual behavior:**
```
TS2345: Argument of type '(a: A1, b: B1) => void' is not assignable to parameter of type '((x: number, a: B1, b: B1) => void) | ((a: B1, b: B1) => void)'.
  Type '(a: A1, b: B1) => void' is not assignable to type '(x: number, a: B1, b: B1) => void'.
    Types of parameters 'a' and 'x' are incompatible.
      Type 'number' is not assignable to type 'A1'.
```

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
http://www.typescriptlang.org/play/#src=function%20f1%3CA1%2C%20B1%3E(cb%3A%20(a%3A%20A1%2C%20b%3A%20B1)%20%3D%3E%20void)%20%7B%0D%0A%20%20f2(cb)%3B%0D%0A%7D%0D%0A%0D%0Afunction%20f2%3CA2%2C%20B2%3E(cb%3A%20((x%3A%20number%2C%20a%3A%20A2%2C%20b%3A%20B2)%20%3D%3E%20void)%7C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20((a%3A%20A2%2C%20b%3A%20B2)%20%3D%3E%20void))%20%7B%7D

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
I looked around and didn't anything obviously related.
Repository: vscode
Issue: [css] support IE10 repeat syntax
Labels: feature-request,css-less-scss

<!-- 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. -->
- VSCode Version: 1.23.1
- OS Version: Windows 8

Steps to Reproduce:

1. View the following code in IE; https://s.codepen.io/fizzbuzz791/debug/EGBxdq/XBkGRZQpnRNA
2. Confirm that it's valid syntax and displays a grid with 3 columns
3. Open a CSS file in VS Code, copy the CSS from codepen and view the following error;
 
![image](https://user-images.githubusercontent.com/2747764/51363652-f594a980-1b13-11e9-9fec-90ca52d26e3b.png)


<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes