sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/go: do not download “modules” that contain no go.mod or *.go
Labels: Proposal,Proposal-Accepted,early-in-cycle,modules

At the moment, `go mod download` will happily try to extract and download any arbitrary repository as long as it can be resolved by some means (through a hard-coded hosting service such as `github.com`, or using a distinguished extension like `.git`), even if it does not contain anything even marginally related to building Go code.

I am not aware of any reasonable use-case for such a repository:

* It's not useful for storing test data, because we currently provide no mechanism for the tests to actually locate that data. (Modules are not guaranteed to be loaded from the module cache — for example, they might be subject to a `replace` directive — and since the test itself is run within the directory containing its source code, it has no way to locate the data or run `go list` within the module that invoked it.)

* It's not useful for C headers (for use with `cgo`), for the same reason.

* It _might be_ useful for fetching non-Go inputs to `go generate`: in theory, the generator could run `go mod download $MODULE` to locate the sources at the required version. But the output of `go generate` is intended to be checked in anyway, which makes the use of modules somewhat spurious: if an explicit version of the non-Go inputs appears in the module's requirements, then everyone using the generated package will have an extra module to fetch that is guaranteed to have no effect on the build, and in most cases the `go generate` program can just as easily `git clone` (or similar) the input data at a specific revision.

Furthermore, if someone _did_ find a way to make modules without Go source code useful (for the above use-cases or others), it's trivial to add a `go.mod` file to indicate that the repository really is _somehow_ intended for use with Go source code. (We need to support `go.mod`-only modules anyway, since they can arise naturally when splitting a large root module into smaller nested modules.)

----

On the other hand, module proxies tend to rely on the `go` command to decide what is or is not a valid module, and accepting arbitrary non-Go repositories potentially exposes such proxies to a significant amount of additional load.

----

Therefore, I propose that we change the `go` command to explicitly reject any “module” that both contains no `.go` source files **and** lacks a `go.mod` file.

CC @rsc @jayconrod @heschik @hyangah @katiehockman @thepudds @marwan-at-work @ianthehat
Repository: vscode
Issue: Add shift+ctrl option to editor.multiCursorModifier setting
Labels: feature-request,editor-multicursor

In Xcode multiple cursors is activated via shift+ctrl and clicking. Could that option (or just any recorded modifier combination) be added to the list of options for editor.multiCursorModifier?

https://stackoverflow.com/questions/50696995/multi-cursor-editing-in-xcode-10
Repository: pytorch
Issue: Latex Errors when Compiling documentation to latexpdf
Labels: module: docs,triaged,module: doc infra

## 📚 Documentation

<!-- A clear and concise description of what content in https://pytorch.org/docs is an issue. If this has to do with the general https://pytorch.org website, please file an issue at https://github.com/pytorch/pytorch.github.io/issues/new/choose instead. If this has to do with https://pytorch.org/tutorials, please file an issue at https://github.com/pytorch/tutorials/issues/new -->

I raise this issue because I encountered many warnings and errors compiling the documentation.
I checked out version 1.1.0, and followed the instruction of "Building the Documentation" by running pip install -r requirements, and then make latexpdf. I already have texlive, latexmk, and other necessary latex packages installed. My system is Ubuntu 19.04.

Errors include missing references, missing "$", extra alignment, etc. Given how verbose latex's error list is, I am not listing everything here. I can upload a log file of the errors if that is desired.

Is there any specific version of latex that is required? 

The reason I try to get a PDF is that PDF is so much better as a single file format when I don't get internet. PDF readers can handle very long PDF files smoothly, while my browser had a hard time to load a large single-file html is hard to handle by my browser. In this use case, PDF is overall a better solution.

On the other hand, I don't really know where the errors originated (the docs, Sphinx, or latex version). So, **maybe a better solution would be providing a downloadable PDF file of every release on the website**? I suppose that if the pytorch team already have a testing pipeline for documentation generation, it wouldn't be too much work to post the pdf file on the website. However, I don't really know if that fits into your pipeline.

Thank you very much!
Repository: pytorch
Issue: Unify Caffe2 and PyTorch OpenMP initialization
Labels: triaged,module: multithreading

At the moment we have two separate OpenMP initialization procedures, one in Caffe2 in `caffe2/core/init_omp.cc`, executed when `GlobalInit` is called. Another is in PyTorch in `at::init_num_threads()`

There're some differences in default settings (e.g. single-thread setting in Caffe2 and default settings in PyTorch) as well as potential conflict if two initialization procedures are called in one process.
Repository: terminal
Issue: [Setting] New tab button should open another of the currently selected tab
Labels: Issue-Feature,Help Wanted,Area-UserInterface,Product-Terminal

* Your Windows build number:  10.0.18890.1000

* What you're doing and what's happening: When you press the add tab button it always opens cmd.

* What's wrong / what should be happening instead: It should open another of the currently viewed tab.
Repository: terminal
Issue: Feature request: Add fluent design reveal highlight to tabs and buttons
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

Add reveal highlight to the tabs and buttons similar to how classic ms edge has.
Repository: flutter
Issue: Different mainAxisMargins for different scrollbar orientations and edges
Labels: framework,a: fidelity,f: cupertino,P2,team-design,triaged-design

`ScrollbarPainter` now assumes `mainAxisMargin` is always the same for different scrolling directions / towards different edges
On iOS, mainAxisMargin should be different for vertical and horizontal scrollbars. And for vertical scrollbars the top margin and the bottom margin are different.

### Screenshot from iPhone XR simulator:
![Simulator Screen Shot - iPhone XR - 2019-04-30 at 15 00 14](https://user-images.githubusercontent.com/31859944/57262089-7faf4200-701f-11e9-914a-83f1b047e260.png)
![Simulator Screen Shot - iPhone XR - 2019-04-30 at 15 12 06](https://user-images.githubusercontent.com/31859944/57262090-7faf4200-701f-11e9-9bd1-d0d5b7a64619.png)
![Simulator Screen Shot - iPhone XR - 2019-04-30 at 17 53 40](https://user-images.githubusercontent.com/31859944/57262091-7faf4200-701f-11e9-9c8d-3a0744307240.png)
Repository: PowerToys
Issue: Full window manager including specific layouts for docking and undocking laptops
Labels: Idea-Enhancement,Idea-New PowerToy,Product-Window Manager,Product-FancyZones

This was mentioned in the README so I'm creating the issue as it sounds like a neat idea to me

I'm assuming this would allow for more flexible window arrangements than the current quadrant snapping, etc.
Repository: PowerToys
Issue: Window auto-alignment/snap/magnet to other windows and screen edges
Labels: Idea-Enhancement,Product-Window Manager,Product-FancyZones

When window is moved or resized, the edge should auto-align/snap when it gets within X pixels of an existing window or screen edge.

Edit: To clarify, I'm talking about snapping capability like the old "AllSnap" program.  This has nothing to do with layouts or window management.
Repository: vue
Issue: ability to keep `enter-to` class after show transition completes
Labels: feature request,transition

### What problem does this feature solve?
In some CSS libraries, i.e. Bootstrap, many components have opacity set to `0` by default, and only have opacity set to `1` when a class is applied.  i.e. Bootstrap's `fade + show` classes:

```css
.fade:not(.show) { opacity: 0; }
```

The current `<transition>` behaviour does not support retaining the `enter-to-class` (as it is immediately removed once the transition completes).

Currently one has to use javascript hooks and VM data to add/remove the `show` class, which makes it impossible to make re-usable transition components, as simply adding a class via javascript to the `el` reference (via `el.classList.add/remove('show')`) doesn't guarantee persistence if the content in the default slot manipulates it's own classes, meaning the transition component _must_ be integrated into the custom component, not as a re-usable utility wrapper component).

### What does the proposed API look like?
It would be nice to either be able to retain the `enter-to-class` class after the transition completes, or create a new prop that provides this behaviour for a particular class name i.e. `enter-to-retain-class`. The class would be removed on leave.

The other option would be to create a new prop `active-class="classname"` which is added one frame after insertion, and removed when the leave transition is to start (basically rolling the `enter-to-class` and `leave-class` into one prop, but retain the class until leave is initiated)

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: flutter
Issue: [maps] Get latitude and longitude when polyline is tapped
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case
It would be nice if we can get latitude and longitude when a polyline is tapped. 

## Proposal
Currently the `onTap` for a polyline looks like 
`onTap() {}`, can you guys make it like
`onTap(LatLng) {}`?

Now `GoogleMap` widget does have `onTap(LatLng)` but to be able to receive click events on my polyline, I have to use `consumeTapEvents: true` and this way `GoogleMap` `onTap(...)` doesn't work.
Repository: create-react-app
Issue: `yarn tsc && react-scripts build` v3 takes 1 hour to complete
Labels: issue: needs investigation

### Is this a bug report?
Yes, 
The production build of a TypeScript project requires almost an hour to complete.

I have tried many different version combinations all with the same result; either my system crashes or I get a very slow build process.

yarn start takes about 5 min and my production build takes almost 1 hour; it's quite consistent.

Currently on the following versions.
**"@types/styled-components": "4.1.10",
"react-scripts": "3.0.0",
"typescript": "3.3.4000",**

### Did you try recovering your dependencies?

I have deleted these files numerous times and tried a few of the typescript-dev versions as well as the styled-component types.

I am using Yarn 
Version 1.15.2

### Which terms did you search for in User Guide?

script react-scripts tsc build slow
typescript cra creating optimized production build takes an hour

### Environment

Issues are consistent in both environments.

1. Windows 16GB RAM, WSL (Ubuntu Install)
2. IBM Cloud Docker Instance

npx: installed 91 in 18.872s

Environment Info:

  System:
    OS: Linux 4.4 Ubuntu 18.04.1 LTS (Bionic Beaver)
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
  Binaries:
    Node: 11.11.0 - ~/.nvm/versions/node/v11.11.0/bin/node
    Yarn: 1.15.2 - /usr/bin/yarn
    npm: 6.7.0 - ~/.nvm/versions/node/v11.11.0/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    react: Not Found
    react-dom: Not Found
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to Reproduce

This is a very large project with hundreds of components.

    "start": react-scripts start", (5-6 min)
    "build": "tsc && react-scripts build" (~53min),

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
-->

I upgraded my existing installation to the newest version of React which supports Hooks and integrated TypeScript which caused the development server to slow down on first launch; with the console displaying the following. 

Files successfully emitted, waiting for typecheck results...

When I commit and merge the code, a deployment build is spun up in a Docker instance which takes almost an hour to complete.


### Expected Behavior

I would expect the production build to take no more than 10 min.
The development server should also launch a bit quicker.
Repository: terminal
Issue: Workspace-specific settings and profiles
Labels: Issue-Feature,Area-Settings,Product-Terminal

Is workspace-specific settings on the roadmap for the Windows Terminal? I was chatting with @jongalloway about it and it would really help streamline teams to be able to check in certain settings or profiles with a solution. VS Code has a great model for Workspace settings and User Settings, I would love to see it here as well. (bonus points for auto-switching settings when `cd`'ing into a workspace directory).

[UserVoice recommendation](https://wpdev.uservoice.com/forums/266908-command-prompt-console-windows-subsystem-for-l/suggestions/37567330-workspace-specific-settings-and-profiles)
Repository: TypeScript
Issue: support match for type infer
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 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

As a suggestion, there is any plans to support `match` keyword in type inference to simplify the type destruction and `T extends P` test and make code more expressive.
Support `match` in type inference.

<!-- A summary of what you'd like to see added or changed -->

## Use Cases

```ts
type Infer<T> = match T {
  { prop: infer P } => P
  [infer P] => P
  _ => never // default
}
```

The above is equal to:

```ts
type Infer<T> = T extends { prop: infer P }
  ? P
  : T extends [infer P]
    ? P
    : never
```

```

## 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
* [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.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: terminal
Issue: Feature request: Recording
Labels: Issue-Feature,Area-Output,Area-Extensibility,Product-Terminal

It would be cool to have a built-in tool to record a terminal session; this would make it easy to create demos and tutorials with no demo ghosts.
Basic feature could be a animated gif
The more advanced could be a playback where you get a live terminal that plays back the recorded session and leaves it open for continued use.
Repository: PowerToys
Issue: Tabbing Features
Labels: Idea-New PowerToy,Product-Window Manager

With the release of the new command line system for W10 I think this kind of feature is a no brainier. Here is another solution for reference: [TidyTabs](https://www.nurgo-software.com/products/tidytabs)
Repository: PowerToys
Issue: Disable Sticky Corners in aero snap
Labels: Idea-New PowerToy,Product-Tweak UI Design

When moving the mouse from one monitor to the other it gets stuck because of the "sticky corners".

So for example, if you want to close a window in the right monitor but your mouse is on the left monitor, you end inadvertently closing the window of the left monitor as the mouse gets stuck in the close button.

The problem is described in detail here https://superuser.com/questions/947817/how-to-disable-sticky-corners-in-windows-10

A workaround https://github.com/patricknelson/win10-sticky-mouse
Repository: PowerToys
Issue: Scripting API for Window Manager
Labels: Idea-Enhancement,Product-Window Manager

Just through out an idea. If you guys create a customizable window manager, I'd welcome a way to interact with it via some scripting language or the commandline.

In Linux, [i3](https://i3wm.org/) comes with a commandline utility `i3-msg` which allows you to reorganize windows via scripts.
Repository: ant-design
Issue: Collapse中使用form的validateFieldsAndScroll
Labels: 💡 Feature Request,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?
因为Collapse展开需要时间，调用validateFieldsAndScroll会滚动不到具体位置，需要加定时器。

### What does the proposed API look like?
希望添加Collapse展开后回调函数。


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: Correct typing when using the index signature of an Enum
Labels: Suggestion,In Discussion

## Search Terms

enum index signature

## Suggestion

Imagine a non const enum (which can be accessed using properties and it's index signature).

``` typescript
enum example { ONE = 1, TWO = 2, THREE = 3 }

const a = example.ONE;
console.log(a); // Prints 1

const aName = example[a]; // Type of aName is string and should be "ONE" | "TWO" | "THREE". Or even "ONE" since a is const
console.log(aName); // Prints "ONE";
```

The implicit type of aName is _string_ and should be "ONE" | "TWO" | "THREE" since those are the only possible values. Or even "ONE" since a is a constant.

## Use Cases

More control over the values of a variable.

## Examples

See above

## 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
* [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.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: neovim
Issue: missing redraws when rpcrequest() is used in statusline expression
Labels: bug,api,channels-rpc,display

This is with recent nvim HEAD, and also manifested with a version some month back. I did not investigate if there are older versions which behave correctly here. The RPC plugin in question is [here](https://github.com/KillTheMule/nvimpam/tree/impro) (take care to take the `impro` branch), so it's not minimal in any way. I might get around to produce something more minimal in python or so.

If you cloned the repo, then in the master directory first you need to compile the plugin (`cargo build`, needs a rust installation), and then you can produce the error from running `nvim -u init.vim files/example.pc` as follows:

1. Start the plugin with `:NvimPamAttach`
1. move to line 50, which reads

```
 NODE  /       22      20.20000076            50.5             30.
```

3. Run `3f2`, and then `i<Space><Esc>` to insert a space. 
  * What happens: The space is inserted, no highlighting applied.
  * What should happen: Space inserted, highlighting applied
4. Run `x` to remove the Space inserted in 1.)
  * What happens: Space is removed, the highlighting from 1.) is applied
  * What should happen: Space is removed, a different highlighting should be applied

 Note that the status line involes a function that runs a request to the plugin, namely `CellHint`,
which interweaves with all other communication of course. This seems to cause trouble.

When I keep doing edits, it very much looks like the highlighting applied is always lagging 1 action behind. A filtered neovim log is at https://gist.github.com/KillTheMule/12378fae90419f539be2d44b48bc0547 which only includes steps 3.) and 4.). These can be seen from line 37 (the update event from inserting a space) to line 51, where the plugin answers the "CellHint" request from neovim (which is a consequence of the statusline being updated). Just to be clear, the log looks perfectly fine to me, it's just that the highlights are not applied at the right time, but "one action later".

@justinmk already looked at it in gitter, and I could provide the following additional answers:
* When using `<C-l>` inbetween, the correct highlighting will be applied
* Using `:redraw` inbetween does not change anything
* Setting `lazyredraw` does not change anything

He also suggested  `as a workaround setting a  "dummy" highlight e.g. nvim_add_buf_hl(..., 'Normal', 1,1) i.e. highilight line 1, column 1 with "Normal" highlight every time you add a real highlight` which I will try tonight (or so...)
Repository: pytorch
Issue: SyncBatchNorm should support 2D input (B, C)
Labels: oncall: distributed,module: nn,triaged,enhancement

## 🐛 Bug

In the implementation of SyncBatchNorm, I just found that there is a `_check_input_dim` to make sure the input dimension > 2. But actually it should support the input with shape (B, C), just like the BatchNorm1d. 

So is there any other reasons for the condition `input.dim() <=2`? If no, could you relax the input check to be `input.dim() < 2` of [SyncBatchNorm here](https://pytorch.org/docs/stable/_modules/torch/nn/modules/batchnorm.html#SyncBatchNorm) ?