sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: os: Process.Signal on the current PID should signal the current thread 
Labels: NeedsDecision

The Go standard library currently lacks an equivalent to the standard C `raise` function.

The closest portable analogue is something like:

```go
func raise(sig os.Signal) error {
  p, err := os.FindProcess(os.Getpid())
  if err != nil {
    return err
  }
  return p.Signal(sig)
}
```

Unfortunately, this pattern is somewhat error-prone: on many platforms (e.g. Linux), it can deliver the signal to any thread in the process group.  If the purpose of raising the signal is to produce a stack trace or trigger the invocation of a C fatal-signal handler (e.g. by raising `SIGQUIT` or `SIGABRT`), that can result in the handler executing on a thread unrelated to the failure.

It's tempting to request a new function call, `os.Raise`, for this purpose, but it seems like we could address this use-case automatically without an API change.  We could have `(*os.Process).Signal` check whether the `Process` in question is the Go program itself and raise the signal synchronously to the current thread (e.g. by using the `tgkill` syscall on Linux, or calling `pthread_kill` or `raise` in cgo-enabled builds).
Repository: go
Issue: x/build/cmd/coordinator: report pkg/bin changes, binary size changes
Labels: Builders,NeedsInvestigation,FeatureRequest

It would be helpful when reviewing changes, particularly toolchain changes, to be able to easily see which pkg/bin files have changed since the parent commit--an easy reviewer's toolstash -cmp.

It'd also be nice to have an automated report about the pkg/bin file size changes.

Could we cheaply/easily add this information to the trybot final report?

cc @bradfitz
Repository: TypeScript
Issue: Dom d.ts does not define event.target.parentNode
Labels: Bug,Help Wanted,Domain: lib.d.ts,VS Code Tracked

_From @linocatucci on February 28, 2017 19:25_

- VSCode Version: Code 1.9.1 (f9d0c687ff2ea7aabd85fb9a43129117c0ecf519, 2017-02-08T23:31:51.320Z)
- OS Version: Darwin x64 16.4.0
- Extensions:

|Extension|Author|Version|
|---|---|---|
|beautify|HookyQR|0.8.8|
|jslint|ajhyndman|1.2.1|
|jshint|dbaeumer|0.10.15|
|vscode-eslint|dbaeumer|1.2.6|
|githistory|donjayamanne|0.1.5|
|auto-close-tag|formulahendry|0.3.9|
|vscode-JS-CSS-HTML-formatter|lonefy|0.2.2|
|vscode-icons|robertohuertasm|7.3.0|
|open-in-browser|techer|0.0.3|

---
Hello,

with some code in VSCode the autocomplete and hints are not working.

For instance with the following codeL
`console.log(event.target.parentNode); `
Visual studio code does not show the options when I type in `event.target.ParentNode` or with `event.target.
`
Can somebody help me?

cheers,
Lino

Steps to Reproduce:

1. type in console.log(event.target.p -> parentNode is expected
2.type in event.ta -> target is expected.

_Copied from original issue: Microsoft/vscode#21570_
Repository: go
Issue: go/internal/srcimporter: src importer cannot handle re-import
Labels: NeedsInvestigation

The existing importers go out of their way to augment partially imported packages (types, etc.).

A source importer doesn't do that - it uses go/types to always create a new package. If only the source importer is used, then (recursively), any package that is imported somewhere is imported as a whole,  so all packages are complete upon import and there's never a need to augment a package.

If we want to provide a "mixed-mode" importer, where some packages are imported from installed packages, and some from source, depending on which is newer, the above is not so simple anymore: A package may be imported from an installed location, which in turn may contain partial package information about another package.

If that other package is imported from source, it must augment the partial package in the packages map rather than replace it.

This matters only for types since they are the only objects that may be used in the construction of other package-level objects - they must be unique.

One could expand the go/types API and provide a partially complete package that is then expanded. Or one could do a "full" import and then somehow merge the new with the old package (and update any types that need to be canonicalized - a tricky proposition).

Or one could disallow "mixed-mode" imports (currently they are not supported anyway).

Needs to be resolved before we can implement mixed-mode imports.
Repository: go
Issue: x/crypto/ssh: add support for alive interval
Labels: NeedsInvestigation,FeatureRequest

When the underlying TCP connection for a long-standing SSH connection abruptly dies, operations on an `ssh.Client` can hang forever. This is because the client remains [stuck in an `io.ReadFull` call](https://github.com/golang/crypto/blob/84bacda6ede319f5074d43b5d096b7ee7f3f5d77/ssh/cipher.go#L150) with no preceding or concurrent calls to `net.Conn.SetDeadline`. Without any deadline set, there is no guarantee that `Read` will ever return.

Even though the user has access the underlying `net.Conn` and can set the deadline themselves, they have no way of determining if the underlying connection is actually dead or just idle. Thus, the `ssh` package should support this functionality that allows sending of empty messages to intentionally invoke a response from the remote endpoint, in order to determine if it is still alive.

This is a feature request for the [equivalent options for OpenSSH](http://man.openbsd.org/ssh_config.5):
* `AliveInterval time.Duration`: Sets a timeout interval after which, if no data has been received, sends an alive message through the encrypted channel to invoke a response from the remote end. The default is 0, indicating that such messages will not be sent.
* `AliveCountMax int`: Sets the number of alive messages which may be sent without receiving a response from the remote end. If this threshold is reached while alive messages are being sent, the SSH session will be terminated.

If this is reasonable, I can implement this.
Repository: vscode
Issue: Add option to always show word based suggestions
Labels: feature-request,suggest

- VSCode Version: 1.9.1

Steps to Reproduce:

1. Go to an empty TypeScript file
2. Enter `fooBarBaz`
3. Enter a new line and then type `fooBa`

Expected result: word based quick suggestions should show.

Actual result: no quick suggestions. Ctrl+space shows a popup with content 'No suggestions'.

![image](https://cloud.githubusercontent.com/assets/921609/23452439/37f59c98-fe5c-11e6-8582-9591f4f2c498.png)

Try the same in a JavaScript file and it works.

I would like IntelliSense and word based suggestions for my TypeScript.
Repository: opencv
Issue: Uniform empty image handling
Labels: future,vote

**Vote**: Please use GitHub emoji/reaction for next two comments below to provide your opinion.

As suggested by @sovrasov in PR #8288 we definitely need to unify the way that empty images are handled inside the imgproc module.

- :one: OPTION 1: generate an assertion (exception) from the moment an empty input is given
- :two: OPTION 2: do not fail, just silently copy with empty data and make output also empty

The second option will require the user to do all the checking on data validity himself.

---

**Update 2020-03-01**: option 1 - 15, option 2 - 5
**Update 2020-04-30**: option 1 - 16, option 2 - 6
Repository: neovim
Issue: API/UI: externalize dialogs
Labels: enhancement,api,ui,channels-rpc,ui-extensibility

https://github.com/onivim/oni/issues/264#issuecomment-283428670

Add a new "dialog" event so that its UI can be externalized.
Repository: angular
Issue: ContentChildren doesn't get children created with NgTemplateOutlet
Labels: area: core,core: queries,type: use-case,P3

Original title: *ViewChildren doesn't get children created with NgTemplateOutlet*

**Please see comments below...**

**I'm submitting a ...**
```
[x] bug report
```

**Current behavior**
When you use ngTemplateOutlet to render a template passing by input property ViewChildren don't get or don't find in the redered elements.

**Expected behavior**
I think ViewChildren should get the elements rendered by ngTemplateOutlet.

**Minimal reproduction of the problem with instructions**
In this [plunkr](https://plnkr.co/edit/BHZHcVKuhoP8OzQHIxAR?p=info), on app.ts file, you can see a `Child` component and a `Parent` component, Parent component has an input property called `template1`, this accept a TemplateRef that is rendered using ngTemplateOutlet. `Parent` component has a `ViewChildren` collection to get the `Child` components and shows the length of this collection in the end of template.

Well, using this component this way:

```` html
    <ng-template #template1>
        <child></child>
        <child></child>
    </ng-template>
    <parent [template1]="template1"></parent>
````

The `Parent` component render the two `Child` components but the length of ViewChildren collection is 0. You can uncomment the line 16 of app.ts file to include a static `<child/>` component in the `Parent` template. Then the collection length is 1.

**What is the motivation / use case for changing the behavior?**
It's would be very useful to pass template to components, rows of grids, lines of lists, ...
In the other hand I have this [plunkr](https://plnkr.co/edit/wFvjrJjNYBLx5sYnJRhm?p=preview) in this case I am rendering `Child` components using a `ngFor`, ViewChildren works fine.
Since both, ngTemplateOutlet and ngForOf, using `viewContainerRef.createEmbeddedView` to render the templates ... why works with ngFor and not with ngTemplateOutlet?
I think that the only reason is that `Child` components come from different component context, but I would like to know it.

**Please tell us about your environment:**
Windows 10, VisualStudioCode, npm, lite-server

* **Angular version:** 4.0.0-rc2

* **Browser:** [all]
 
* **Language:** [TypeScript 2.2.1]
Repository: flutter
Issue: VM service should accept URIs instead of file paths for hot reload
Labels: team,tool,P3,team-tool,triaged-tool

Do be truly portable, the following calls should accept real platform-independent URIs (instead of platform-specific file paths) on the remote (VM) side:

* https://github.com/flutter/flutter/blob/17057bb44b7c10b2b4603cd09b266d9379f65ba2/packages/flutter_tools/lib/src/devfs.dart#L203
* https://github.com/flutter/flutter/blob/17057bb44b7c10b2b4603cd09b266d9379f65ba2/packages/flutter_tools/lib/src/devfs.dart#L273
* https://github.com/flutter/flutter/blob/17057bb44b7c10b2b4603cd09b266d9379f65ba2/packages/flutter_tools/lib/src/vmservice.dart#L850
* https://github.com/flutter/flutter/blob/17057bb44b7c10b2b4603cd09b266d9379f65ba2/packages/flutter_tools/lib/src/vmservice.dart#L853
* https://github.com/goderbauer/flutter/blob/b8a53749c1bd542e4c5588c332e01e2a8790f852/packages/flutter_tools/lib/src/vmservice.dart#L717
Repository: rust
Issue: consolidate recursion limit errors
Labels: C-cleanup,A-diagnostics,T-compiler

They should all have an error code and maybe a helper function to create the suggestion message.

cc @nikomatsakis #39655
Repository: TypeScript
Issue: Optional Generic Type Inference
Labels: Suggestion,In Discussion

#13487 added default generic types, but it's still not possible to infer a generic type:

```ts
type Return<T extends () => S, S = any> = S
```

Here `S` takes its default type `any`, but `T` could permit inference of a subset type of `any` for `S`:

```ts
const Hello = () => 'World'

type HelloReturn = Return<typeof Hello> // any
```

Here `HelloReturn` still has `any` type, and TypeScript could infer `S` as the literal type `'World'`, which is a subset of `any`.


## Use Case

Here's an example of a fully declarative workaround for #6606, using generic type inference:

```ts
type Return<T extends () => S, S = any> = S
```

```ts
const Hello = () => 'World'

type HelloReturn = Return<typeof Hello>  // 'World'
```


## Default Type

If return of `T` is not a subset of `S`, it should throw an error:

```ts
type ReturnString<T extends () => S, S = string> = S
```

```ts
const Hello = () => 'World'
type HelloReturn = ReturnString<typeof Hello>  // 'World'
```

```ts
const calculateMeaningOfLife = () => 42
type MeaningOfLife = ReturnString<typeof calculateMeaningOfLife> // ERROR: T should return a subset of String
```


## Multiple Possible Type Inferences

The current implementation always returns the superset (which is just the default generic type), solving this issue would require to return the subset (the most precise type of all the inferred possibilities).

If a type has multiple possible type inferences, TypeScript should check that all these types **are not disjoint**, and that they all are subsets of the Default Generic Type.

The inferred type is the most precise subset.
Repository: youtube-dl
Issue: Unable to download from http://oscar.go.com/video/...
Labels: geo-restricted

Example:
$ youtube-dl -v http://oscar.go.com/video/oscar-highlights-2017/seth-rogen-and-michael-j-fox-go-back-to-the-future
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'http://oscar.go.com/video/oscar-highlights-2017/seth-rogen-and-michael-j-fox-go-back-to-the-future']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.02.28
[debug] Python version 3.4.2 - Linux-3.16.0-4-amd64-x86_64-with-debian-8.7
[debug] exe versions: ffmpeg 3.2.4-1, ffprobe 3.2.4-1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] seth-rogen-and-michael-j-fox-go-back-to-the-future: Requesting header
WARNING: Falling back on generic information extractor.
[generic] seth-rogen-and-michael-j-fox-go-back-to-the-future: Downloading webpage
[generic] seth-rogen-and-michael-j-fox-go-back-to-the-future: Extracting information
ERROR: Unsupported URL: http://oscar.go.com/video/oscar-highlights-2017/seth-rogen-and-michael-j-fox-go-back-to-the-future
Traceback (most recent call last):
  File "/home/ant/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 761, in extract_info
    ie_result = ie.extract(url)
  File "/home/ant/bin/youtube-dl/youtube_dl/extractor/common.py", line 427, in extract
    ie_result = self._real_extract(url)
  File "/home/ant/bin/youtube-dl/youtube_dl/extractor/generic.py", line 2604, in _real_extract
    raise UnsupportedError(url)
youtube_dl.utils.UnsupportedError: Unsupported URL: http://oscar.go.com/video/oscar-highlights-2017/seth-rogen-and-michael-j-fox-go-back-to-the-future


Thank you in advance. :)
Repository: rust
Issue: Lifetime inference falls over with identical lifetimes across trait and implementing struct
Labels: A-lifetimes,A-inference,C-bug

I tried to write this code:
```
fn main() {
    let a = XImpl {};
    foo(&a);
}
fn foo(x: &X) {
    x.bar();
}
pub trait X<'a> {
    fn bar(&'a self);
}
pub struct XImpl {}
impl<'a> X<'a> for XImpl {
    fn bar(&'a self) {}
}
```

I think this should compile, but it fails with: [https://gist.github.com/buntpfotenkatze/073cc5d65bdbd0e87b202cfe6013d39c](https://gist.github.com/buntpfotenkatze/073cc5d65bdbd0e87b202cfe6013d39c)

Replacing `fn foo(x: &X)` with `fn foo<'a>(x: &'a X<'a>)` fixes it, but I think the compiler should be able to deduce that the two lifetimes of x are identical.

Edit:
[code updated to 2021 ed](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=335c08261b255849fe730f66be260416)

current error:
```
error: lifetime may not live long enough
 --> src/main.rs:6:5
  |
5 | fn foo(x: &dyn X) {
  |        -  - let's call the lifetime of this reference `'1`
  |        |
  |        has type `&dyn X<'2>`
6 |     x.bar();
  |     ^^^^^^^ argument requires that `'1` must outlive `'2`

error: could not compile `playground` (bin "playground") due to previous error
```
Repository: angular
Issue: State transition animations are canceled when the state changes, even though no transition is defined (e.g. with '*' transitions) or the state is identical.
Labels: type: bug/fix,area: animations,freq1: low,P4

**I'm submitting a ...**
```
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see 
```
**Current behavior**
State transition animations are canceled when the state changes to one with an identical style.

This could perhaps be as designed/intended behavior and should be a feature request?

**Expected behavior**
If the state has an identical style, the existing animation should continue.

**Minimal reproduction of the problem with instructions**
https://plnkr.co/edit/eP1lax?p=preview

**What is the motivation / use case for changing the behavior?**
This allows more complex state change animations driven from a single state variable. For example if an application has the following states:

initialized, loading, loaded, updating, failed

You can animate your component to appear after initialized, say the state changes to "loading":

      state('initialized', style({transform: 'scale(0)'})),
      state('loading, loaded, updating, failed', style({transform: 'scale(1)'})),
      transition('* => initialized', animate('2000ms')),
      transition('initialized=> *', animate('2000ms'))

but if you're server is quicker than the animation, and the loading is complete, your state changes to "loaded", and even though there should be no transition or new animation (due to the '*' notation) the current animation is canceled abruptly.

**Please tell us about your environment:**

* **Angular version:** 2.4.8 and 4.0.0-rc.1

* **Browser:** all (Assumption, only tested on chrome)
 
* **Language:** all (Assumption. Only tested with typescript)

* **Node (for AoT issues):**  n/a
Repository: TypeScript
Issue: Cannot Optionalize Class Getters
Labels: Suggestion,In Discussion

**TypeScript Version:**  2.2.1

**Code**

```ts
class Person {
  firstName: string;
  lastName: string;

  get fullName?() {
    return this.firstName + ' ' + this.lastName;
  }
}
```

**Expected behavior:**

Since `fullName` is optional the following should work:

```
const Me: Person = {
  firstName: 'Foo',
  lastName: 'Bar'
}
```

**Actual behavior:**

A syntax error occurs on this line `get fullName?() {`

I'm not sure if omitting the ability to optionalize getters was by design or not. If it was by design, I'd love to know the reasoning behind it.
Repository: TypeScript
Issue: Plugin Support for Custom Transformers
Labels: Docs

Since #13764 has landed, it's easy to write custom transformers. However, if I understand the API correctly, it is needed to duplicate the whole tsc command line just to add a single transformer. This leads to incompatibilities since these, on typescript depending, applications do not support the same features as the tsc command line tool. 

It, therefore, would be favored to have a plugin system that allows loading Custom Transformers from third party node modules as this is the case for the language service proxies #12231. These transformers then easily integrate into existing build tools / build workflows.

If someone experienced has inputs on how to implement the changes, I'm willing to create a PR as it would simplify my project tremendously.
Repository: vscode
Issue: Feature Request: Support for private marketplace/gallery
Labels: feature-request,upstream,marketplace,upstream-issue-linked

We have created several VSIX extension that have no use to anybody else except our company. We would like to host our own private extension gallery and have an ability to specify alternative extension gallery paths (like "Additional Extension Galleries" in Visual Studio 2015).

- VSCode Version: 1.10.1
- OS Version: Windows 10
Repository: go
Issue: cmd/compile: an FSM with ~40k states takes a lot of memory to build
Labels: ToolSpeed,compiler/runtime

### What version of Go are you using (`go version`)?

go version go1.8 linux/amd64

### What operating system and processor architecture are you using (`go env`)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/opennota/gocode"
GORACE=""
GOROOT="/home/opennota/go"
GOTOOLDIR="/home/opennota/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build723393668=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

### What did you do?

I tried to build `x.go` from here: https://github.com/opennota/x . It is a 3.3 MB / 230 kLOC file containing an autogenerated finite state machine with about 40k states.

### What did you expect to see?

The build is completed in a matter of seconds (there's no cgo, after all).

### What did you see instead?

The build takes a goodish while and slowly consumes all the available memory. Actually, despite having 8 GB of memory I wasn't able to build the package.

With Go 1.7.3 the memory usage is stable (not increasing), but again, the build is a way too slow.
Repository: vscode
Issue: Outline matching selections instead of highlight
Labels: feature-request,ux,editor-theming,editor-highlight

<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode -->

- VSCode Version: 1.10.1
- OS Version: macOS 10.12.2

Steps to Reproduce:

1. Highlight a selection with multiple instances. 
2. Look how hard it is to distinguish which instance is selected.

![screen shot 2017-03-03 at 7 33 55 am](https://cloud.githubusercontent.com/assets/10407384/23555115/e1ab96e6-ffe4-11e6-9d82-687e859a8f26.png)
![screen shot 2017-03-03 at 7 36 55 am](https://cloud.githubusercontent.com/assets/10407384/23555118/e38522ac-ffe4-11e6-968d-7913e65f2b49.png)

There are three fundamental issues that this request entails:

1. When you make a selection and there are multiple instances, it's extremely hard to distinguish which one is actually selected. This image shows VSCode's standard Monokai theme. This is not a "theme" issue, users should be able to use any theme that is available in the marketplace. 

2. When you make a selection, matching instances shouldn't be highlighted at all. Being highlighted indicates that they are also selected, which is not the case. So when I double click on a single word to select it, all the matching instances get highlighted too, creating the appearance that they are all selected.

3. The check that looks for matching instances should be _case sensitive_, so that when I select `contract`, a camel-case instance of `newContract` should not have that instance of contract highlighted.