sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Audit set of bundled MinGW import libraries
Labels: A-linkage,C-enhancement,T-compiler,O-windows-gnu,T-bootstrap

The set of import libraries that Rust bundles should strictly be what is needed to link against the libraries that come with the Rust distribution. Missing an import library causes link errors while including unnecessary import libraries bloats the distribution.

| Library | Necessary |
|--|--|
| libadvapi32.a | Yes |
| libbcrypt.a | No |
| libcomctl32.a | No |
| libcomdlg32.a | No |
| libcredui.a | Yes and missing! |
| libcrypt32.a | No |
| libdbghelp.a | Yes |
| libgdi32.a | Yes |
| libimagehlp.a | No |
| libiphlpapi.a | No |
| libkernel32.a | Yes |
| libmsimg32.a | Yes |
| libmsvcrt.a | Yes |
| libodbc32.a | No |
| libole32.a | No |
| liboleaut32.a | No |
| libopengl32.a | Yes |
| libpsapi.a | Yes |
| librpcrt4.a | No |
| libsecur32.a | Yes and missing! |
| libsetupapi.a | Yes |
| libshell32.a | Yes |
| libuser32.a | Yes |
| libuserenv.a | Yes |
| libuuid.a | No |
| libwinhttp.a | No |
| libwinmm.a | No |
| libwinspool.a | Yes |
| libws2_32.a | Yes |
| libwsock32.a | No |
Repository: flutter
Issue: Let flutter be installable via homebrew
Labels: c: new feature,tool,platform-mac,a: first hour,customer: crowd,P3,team-tool,triaged-tool

Latest update: https://github.com/flutter/flutter/issues/14050#issuecomment-1012647917

A description of the desired user experience: https://github.com/flutter/flutter/issues/14050#issuecomment-446712064

---- 
Didn't find any existing issues on this. Opening for tracking. 

Let flutter be `brew install flutter`able.
Repository: TypeScript
Issue: Destructing assignments with initializers do not affect control flow correctly in strictNullChecks
Labels: Bug

<!-- BUGS: Please use this template. -->
<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->
<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.7.0-dev.201xxxxx

**Code**

```ts
const { y = "A" } = { y: "B" };
y; // y's type here
```

**Expected behavior:**
y is `"B"` - `"B"` is not a type with `undefined` in its domain, so the initializer will _never_ be run. (And should be marked as unreachable code, and definitely not incorporated into the variable's type)

**Actual behavior:**
y is `"A" | "B"` - this is fine outside of `strictNullChecks`, but is lacking within it.
Repository: flutter
Issue: Service protocol extensions for screenshotting need to be able to handle multiple Flutter views.
Labels: customer: fuchsia,tool,engine,a: desktop,P3,team-macos,triaged-macos

The service protocol extensions "_flutter.screenshot" and "_flutter.screenshotSkp" return a single item. This involves choosing a random view when mutliple Flutter views are present. These calls must be modified to return an array of resources.
Repository: TypeScript
Issue: Provide lib for modern DOM
Labels: Suggestion,Help Wanted,Domain: lib.d.ts,Experience Enhancement

This is basically a re-opening of #2910, which @mhegazy asked me to do.

Nowadays TS has the `lib` compiler option that allow users to selectively choose which core definitions to include or not based on their target.

It would be nice to add a new option similar to `dom` and `dom.iterable` for users targetting a modern DOM runtime. Not sure how to name this since W3C has moved from releases to a "living standard" model.

For example, the living standard includes interfaces `ChildNode` with methods `after`, `before`, `remove` and `replaceWith`; `ParentNode` with methods `prepend` and `append`.

Those methods have been in Firefox and Chrome for a long while, they're in preview in Edge (17035+).

They are very convenient and there's no reason a dev that targets modern browsers shouldn't be able to do `"lib": "dom.living"` and use them.

Unfortunately I am not sure if there's a list somewhere of all those new features... except going through the whole standard :(
Repository: TypeScript
Issue: Suggestion for readonly interface
Labels: Suggestion,Awaiting More Feedback

Avoid duplicating "readonly" for each property by applying it to the interface definition itself.
This is to reduce boilerplate code defining immutable objects.

Having interface where ALL properties are read only:
```ts
interface State {
    readonly prop1: string;
    readonly prop2: string;
    ...
    readonly prop22: string;
}
```
equals to:
```ts
readonly interface State {
    prop1: string;
    prop2: string;
    ...
    prop22: string;
}
```
Repository: react-native
Issue: Inverted FlatList displays activity indicator at the bottom
Labels: Good first issue,Help Wanted :octocat:,Type: Enhancement,Component: FlatList,Bug

### Is this a bug report?
yes

### Have you read the [Contributing Guidelines](https://facebook.github.io/react-native/docs/contributing.html)?
yes

### Environment
  Environment: all newer environments
  Packages: any packages
  Target Platform: any platform
  Version: 0.53.0 and all other versions of RN that support FlatList with the ```inverted``` attribute

### Steps to Reproduce
1. ```return <FlatList {...props} inverted data={[...]} refreshing={this.state.isLoading} onRefresh={this.someListUpdatingFunction} />```
(just add the 'inverted' attribute to any RN ```<FlatList/>``` to reproduce, then try pulling **down** to refresh, then try pulling **up** to refresh)

### Expected Behavior
onRefresh should allow users to refresh using the **most common** way that users have been trained to refresh data over the years, which is to "pull **down** to refresh" and see an ActivityIndicator spinning **above** the FlatList, **never** below it... this should be the default **even when** inverted={true}

### Actual Behavior
user has to pull UP to refresh (with Activity Indicator at the bottom) ... literal vs intuitive: when taken "literally", i can agree that this is expected behavior since it is after all "inverted" ... however, when taken "intuitively", it's not so expected, **especially** for users... I don't think app users have ever been trained to pull up to refresh data, except for maybe in the "OfferUp" chat app!

### Most Applicable Use Case
- a chat app, where users pull down to load more chat history that's appended above, similar to how it's done in iOS Messages app
- UIs like terminals, event logs, chat, etc... where it's common to insert new content from the bottom and load old content when the user scrolls to the top or pulls down to refresh

### Demo
https://snack.expo.io/S1UOyWgSM
(to reproduce, just add the 'inverted' attribute to any RN ```<FlatList/>``` component using v0.53.0 or any version of RN that supports FlatList)
Repository: pytorch
Issue: Protect user from No module named _C import error
Labels: module: error checking,triaged,module: pybind

After installing pytorch, I tried to test that it worked by firing up python and import torch.
I get the error
 ImportError: No module named _C

I was sitting in the root of the pytorch git tree.  Moving out of the tree solves the problem, but it's mysterious until you find someone else on the web who had it.

Please consider adding a check that the user isn't sitting in the tree during import to save newbies from this issue?

Thanks!
Repository: pytorch
Issue: Better header hygiene in ATen
Labels: module: internals,triaged

Steps to reproduce:
1. Edit `native_functions.yaml` to add a single new function
2. Rebuild

Expected result: Quick rebuild
Actual result: Everything in the universe rebuilds

This is because a good portion of our C++ functions include `ATen/ATen.h`, which includes the autogenerated (very long) header file, which gets modified when you edit `native_functions.yaml`.

I suggest we separate the headers which depend on methods from functions. Methods have to be defined in the class so life is hard, but functions are not, so they can be split up and only functions you actually need can be included. This requires a bit more import discipline, but you now get to avoid long rebuilds.

(Or maybe you think the cure is worse than the disease.)

cc @ezyang @bhosmer @smessmer @ljk53
Repository: vscode
Issue: [folding] "Select all Occurrences" bug
Labels: bug,editor-folding

- VSCode Version: 1.19.2
- OS Version: Win 10

Steps to Reproduce:
- Open a new document and paste the following content

```
abc
  abc
  def
  ghi

abc
  abc
  def
  ghi
```
 
- Place the cursor in the first line and execute Fold (`Ctrl + Shift + [`)
- Select "abc" in the 3rd line
- Select all occurrences (`Ctrl + Shift + L`)
- type A to replace all selections with "A"
- Unfold All (`Ctrl + K` `Ctrl + J`)
- There are 3 A's in the document. Expected: 4.
Repository: svelte
Issue: Whole-app optimisation
Labels: feature request,popular,compiler

I keep bringing this up as a thing-we-should-do but it's probably time we had an issue for it with specific ideas about *what* it means and *how* to get there.

I'll kick things off with a few ideas of things we could do:

### Static properties

```html
<!-- App.html -->
<Greeting name='world'/>

<!-- Greeting.html -->
<h1>Hello {{name}}!</h1>
```

Right now, this involves creating three separate text nodes inside the `<h1>` (which we *could* collapse into one — Scott Bedard had some good ideas in Gitter), and adding update code that waits for `state.name` to change. We could replace all that with

```js
h1.textContent = 'Hello world!';
```

### Static computed properties

As a corollary to the above, if you know the values of the inputs to a computed property, and know that the computed property function is pure, you can precompute the value.

### Collapsing entire components

A 'component' is really two things — the main fragment, and the interface. In a lot of cases, such as the `<Greeting>` component above, we don't actually *need* the interface — we can statically determine that there are no lifecycle hooks or events, and no way that the user could get a reference to the component.

### Optimising styles

Component-level unused style removal is cool, but if we had all your styles we could start to do [Styletron](http://styletron.js.org/)-style optimisations.

---

Will add to this list as other things occur to me; please suggest others!
Repository: vscode
Issue: Git - Detect git repositories under ignored paths
Labels: bug,help wanted,git

This is a feature request.

I work in several projects, mostly Docker-related, where I need to edit code inside git repositories that are ignored inside the main one.

Example file tree:

```
main-repo/
  .git/
  .gitignore # <-- Here we ignore the `external_sources` folder
  src/
    [files]
  external_sources/
    extra1/
      .git/
      [files]
    extra2/
      .git/
      [files]
```

The reasoning behind this is an aggregated Docker project that includes sources from many unrelated places. Developing means mounting local code, changing it, and pushing code to all repos (the main one and the ones under `external_sources`, where we mainly need to open PRs for that), but deploying to production means building a different Docker image where we download and merge external code instead of copying it from localhost.

Boilerplate apart, the feature request is to be able to find those subrepositories, even if they are untracked from the main one, and let the user use the full SCM interface (diffs, SCM section...) on them.

Right now, the diffs do not show because you are editing ignored code, and the SCM does not show these folders for the same reason.

I gues that now that multi-root workspaces are in, this shouldn't be so hard to achieve...

Thanks!
Repository: godot
Issue: Allow specifying C# class name instead of source file path as node's script
Labels: enhancement,discussion,topic:dotnet

**Godot version:**
`master` / 30d7943311cdf4efbc6794a52df0e298f5e6d975

**OS/device including version:**
_Manjaro Linux 17.1-rc2_

**Issue description:**
Currently, C# is treated in the same manner as GDScript, in that it is assumed the code would be reused in its source code form. However, it is not ideal for C# which is a compiled language and often used to create binary assemblies that can be reused in other programs.

With Godot, it is not possible to attach a C# class to a node directly (by specifying its fully qualified class name), but must be done by providing a path to the source file where the class is declared.

This is problematic, since C# allows declaring a class that has a different name from its source file, or even declaring multiple classes in a single source file.

More importantly, it makes creating a library or a framework that can be used in Godot very difficult, since it is impossible to reuse such a module in its binary form, as it is generally done by a normal C# project (by using NuGet, and etc.).

This limitation also prevents one from writing editor plugins, as described in #15237.

Ideally, users should be able to reference a C# type by its fully qualified name (including the namespace) and attach it to a node, as long as the assembly that contains the class is referenced by the main C# project which is associated with the current Godot project.
Repository: go
Issue: cmd/go: default GOBIN to GOPATH[0]/bin when outside of GOPATH?
Labels: NeedsFix,GoCommand

### What version of Go are you using (`go version`)?
1.9.2

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
Linux, amd64

### What did you do?

```
$ docker run -it --rm --name test golang:1 bash
$ go get github.com/nats-io/go-nats-streaming
$ go install /go/src/github.com/nats-io/go-nats-streaming/examples/stan-pub.go
```

### What did you expect to see?
`/go/bin/stan-pub` binary installed, consistent with the requirements when `go install <package>` is used, just GOPATH is set and that should be enough, GOBIN should not be required.

### What did you see instead?
Error message:
`go install: no install location for .go files listed on command line (GOBIN not set)`
Repository: youtube-dl
Issue: support for http://new-play.tudou.com
Labels: request

- [x] I've **verified** and **I assure** that I'm running youtube-dl **2018.01.07**
- [x] At least skimmed through the [README](https://github.com/rg3/youtube-dl/blob/master/README.md), **most notably** the [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones

### What is the purpose of your *issue*?
- [x] Bug report (encountered problems with youtube-dl)

### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: http://new-play.tudou.com/v/385712786.html?spm=a2hzp.8253869.0.0
- Playlist: http://id.tudou.com/i/UMTcwNTIxNjA2OA==/videos?order=2

---

### Description of your *issue*, suggested solution and other information
Tudou uses a new URL for their videos, "new-play.tudou.com". Could support be added for this?
Repository: vscode
Issue: Can we get a few more pixels for clicking the cursor at the beginning of a line?
Labels: bug,editor-rendering

Hello!

I'm routinely frustrated when trying to click on the beginning of a line of text to place the cursor or start a selection - I aim for it but it is very narrow (first half of the first character) and I miss and either hit the code-folding vertical or I get text-column two instead.   Can that be made a little wider please?

![image](https://user-images.githubusercontent.com/17498172/34908005-b51c6f4a-f856-11e7-88a4-ca4360f28edf.png)

Thanks!

*Addition by @hediet*: See #127025 for how the cursor is misleading.
Repository: godot
Issue: Building the summator module from docs as shared module results in error
Labels: bug,platform:windows,topic:buildsystem,documentation

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if non-official. -->
Master Branch from today (1/13/2018) 

**OS/device including version:**
<!-- Specify GPU model and drivers if graphics-related. -->
Win 10 | MSVC 2017 x64

**Issue description:**
<!-- What happened, and what was expected. -->
So after succeeding in building the summator module as a static library (by following the docs) I tried to do the same thing but make the library shared instead.
This appears to work at first but it generates a library with a name that is repeated twice **'summator.windows.tools.64.windows.tools.64.lib'** instead of **'summator.windows.tools.64.lib'.**

I've had this error before and I thought it was just from me or it will be fixed soon. But it is still persistent.

This is the full error .

`scons platform=windows summator_shared=yes
scons: Reading SConscript files ...
Detected MSVC compiler: amd64
Compiled program architecture will be a 64 bit executable (forcing bits=64).
Checking for C header file mntent.h... (cached) no
scons: done reading SConscript files.
scons: Building targets ...
[ 97%] [91mLinking Program        [95m==> [93mbin\godot.windows.tools.64.exe[0m
LINK : fatal error LNK1181: cannot open input file 'summator.windows.tools.64.windows.tools.64.lib'
scons: *** [bin\godot.windows.tools.64.exe] Error 1181
scons: building terminated because of errors.`


**Steps to reproduce:**
Following the docs http://docs.godotengine.org/en/latest/development/cpp/custom_modules_in_cpp.html#creating-a-new-module using an MSVC 2017 compiler will reproduce this.

**Minimal reproduction project:**
<!-- Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->
Repository: create-react-app
Issue: Look into simplifying post-ejected projects
Labels: tag: enhancement

Webpack has been landing some improvements and adding sane defaults—perhaps we can revisit some of the configuration and try to remove it? Alternatively, we could try hiding more code into `react-dev-utils`.
Repository: pytorch
Issue: [Feature proposal] Add MC-derived optimizers
Labels: feature,module: optimizer,triaged,needs research

Recent papers have proposed SGD variants based on stochastic gradient MCMC algorithms that can complete with SOTA optimizers like Adam. Would anyone be interested in an implementation of Santa ([Chen et al. 2016](http://people.ee.duke.edu/~lcarin/Santa_aistats16.pdf)) and relativistic stochastic gradient descent ([Lu, Perrone et al. 2017](http://proceedings.mlr.press/v54/lu17b/lu17b.pdf))?

cc @vincentqb
Repository: create-react-app
Issue: Follow up about Jest issues
Labels: tag: underlying tools

Before cutting 2.0 final I'd like to have a good understanding of these:

- [ ] https://github.com/facebook/jest/issues/3251#issuecomment-337032314 (potential regression in Jest 21+)
- [ ] https://github.com/facebook/jest/issues/5311 (just a weird warning)
Repository: create-react-app
Issue: Automatically install dependencies on yarn start?
Labels: issue: proposal

Developers less familiar with modern JavaScript likely have trouble understanding why an error message like this comes up after running `yarn start`:

![image](https://user-images.githubusercontent.com/709451/34923695-006f3462-f953-11e7-8884-31d51df72b41.png)

Would `create-react-app` benefit from adding a check on `yarn start` that ensures the latest dependencies are already installed?
Repository: rust
Issue: Implement method suggestions for associated functions
Labels: C-enhancement,A-diagnostics,A-associated-items,T-compiler,A-suggestion-diagnostics,D-papercut

This doesn't suggest `bar` but IMO should ([see it live](https://play.rust-lang.org/?gist=107b9a29435251c232c81653d97290c3&version=stable)):

```rust
struct A { }

impl A {
    fn foo() -> Self {
      /*Self::*/bar()
    }
    
    fn bar() -> Self { A { } }
}

fn main() {
    let v = A::foo();
}
```

produces

```shell
error[E0425]: cannot find function `bar` in this scope
 --> src/main.rs:5:17
  |
5 |       /*Self::*/bar()
  |                 ^^^ not found in this scope

error: aborting due to previous error
error: Could not compile `playground`.
```

I'd like a `help/note` saying: "Maybe you meant to call `Self::bar()?" in this case, but if for example `bar` has a typo, I'd like to see more suggestions, like here:

```rust
impl A {
    fn foo() -> Self {
      /*Self::*/bar()
    }
    
    fn bar0() -> Self { A { } }
    fn bar1() -> u32 { 0 }  // mismatching-types
    fn bar2() -> Self { A { } }
}
```

It should suggest whether I meant `Self::bar0` or `Self::bar2` (`Self::bar1` produces a different type). If I remove `bar0` and `bar2`, I'd expect to see a suggestion for `Self::bar1` though.
Repository: rust
Issue: rustc should suggest using `move` for closures where a variable is `Copy` and does not live long enough
Labels: C-enhancement,A-diagnostics,T-compiler

I was trying to get [this code snippet](https://play.rust-lang.org/?gist=34a9759c0547866af2d02a57658f5a63&version=stable) to work earlier:

```rust
[1, 2, 4, 7].iter()
    .flat_map(|num| {
        (0 .. 5).map(|x| (x, num))
    })
    .for_each(|(x, num)| println!("{} {}", x, num));
```

Where `rustc` gives the following error:

```
error[E0597]: `num` does not live long enough
 --> src/main.rs:4:34
  |
4 |             (0 .. 5).map(|x| (x, num))
  |                          ---     ^^^ does not live long enough
  |                          |
  |                          capture occurs here
5 |         })
  |         - borrowed value only lives until here
6 |         .for_each(|(x, num)| println!("{} {}", x, num));
  |                                                       - borrowed value needs to live until here
```

I found out that the solution was to add a `move` to the inner closure, but as I did not know much about the keyword this was not especially obvious.

```rust
(0 .. 5).map(move |x| (x, num))
```

I think it would be very helpful if a note could be added to situations like this to provide an easy solution:
```
help: try adding `move` to the closure like this: `(0 .. 5).map(move |x| (x, num))`
help: This means that the value is moved into the closure instead of being referenced.
```
Repository: rust
Issue: macro_rules: "no syntax variables matched as repeating at this depth" fires before "unknown macro variable"
Labels: C-enhancement,A-diagnostics,A-macros,T-compiler

Consider the following code:

```rust
macro_rules! a {
    (begin $ard: ident end) => {
        [$arg]
    }
}

macro_rules! b {
    (begin $($ard: ident),* end) => {
        [$($arg),*]
    }
}

fn main() {
    let (m, n) = (1, 2);
    let x = a![begin m end];
    let y = b![begin n end];
}
```

This produces the following pair of error messages:

```
error: unknown macro variable `arg`
  --> src/main.rs:3:10
   |
3  |         [$arg]
   |          ^^^^
...
15 |     let x = a![begin m end];
   |             --------------- in this macro invocation

error: attempted to repeat an expression containing no syntax variables matched as repeating at this depth
 --> src/main.rs:9:11
  |
9 |         [$($arg),*]
  |           ^^^^^^

error: Could not compile `playground`.
```

While the second error message is *correct* in principle, it is also misleading. When I get a message like that, my focus is on counting how deeply nested the variable is. I usually don't consider "wait is the syntax variable *misspelled*?" when I see that error message.

I think we could and should first check if a macro variable occurs at *any* depth (and report the first error if not) before we report anything about whether a match is found at the *current* depth (and report the second error if not).