sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/go: misleading 'use of internal package not allowed' in GOPATH mode when a subtree vendors its own package
Labels: NeedsFix

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.7 linux/amd64
</pre>

### Does this issue reproduce with the latest release?


### What operating system and processor architecture are you using (`go env`)?
RHEL 8 (Ootpa)
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/srinivas/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/srinivas/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=""
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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build192096706=/tmp/go-build -gno-record-gcc-switches"

Dep version
dep:
 version     : v0.5.4
 build date  :
 git hash    :
 go version  : go1.12.7
 go compiler : gc
 platform    : linux/amd64
 features    : ImportDuringSolve=false

</pre>
</details>

### What did you do?
<pre>
git clone https://github.com/wavefrontHQ/wavefront-kubernetes-collector.git
cd wavefrontHQ/wavefront-kubernetes-collector
dep ensure
make
</pre>

<!--
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?
I was expecting the build to be successful


### What did you see instead?
<pre>
go vet -composites=false ./...
cmd/test-driver/main.go:13:2: use of internal package github.com/wavefrontHQ/wavefront-kubernetes-collector/vendor/github.com/wavefronthq/wavefront-kubernetes-collector/internal/options not allowed
cmd/wavefront-collector/main.go:21:2: use of internal package github.com/wavefrontHQ/wavefront-kubernetes-collector/vendor/github.com/wavefronthq/wavefront-kubernetes-collector/internal/agent not allowed
cmd/wavefront-collector/main.go:22:2: use of internal package github.com/wavefrontHQ/wavefront-kubernetes-collector/vendor/github.com/wavefronthq/wavefront-kubernetes-collector/internal/configuration not allowed
</pre>
Repository: electron
Issue: BrowserWindow's size get's clamped to monitor's bounds
Labels: platform/windows,bug :beetle:,status/confirmed,5-0-x,component/BrowserWindow,7-1-x,10-x-y

### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:** 5.0.7
* **Operating System:** Windows 10

### Expected Behavior
In my new-window handler, I set the size of the window to something that exceeds the size of the monitor that the window is about to be opened on, and then set the position (via `options`) to move it to another monitor. I expect my position and size to be respected.

### Actual Behavior
Position is respected and the window moves to the correct place, but the window size is actually clamped to the size of the initial monitor that the window was about to be launched on.

### To Reproduce
Not exactly my case, but a similar behavior can be reproduced via:

```
const { app, BrowserWindow } = require('electron')

function createWindow() {
    const mainWindow = new BrowserWindow({x: 0, y: 0, width: 5000, height: 1350});
    console.log(mainWindow.getBounds());
}

app.on('ready', createWindow)
```

It logs `{ x: 0, y: 0, width: 2560, height: 1350}` which is the maximum size of the monitor on which it was launched.

The first time I launched it, I guess it was going to create it on the second monitor instead of the first, and so the width/height was set to the second monitor's bounds even though the window was moved to the first monitor (0,0).

Now this might due to the fact that Chrome clamps window bounds, so if you try launching a window via `window.open` with a width/height greater than the monitor, the window's size will be clamped to the monitor size.

So if there is a bug, the bug is that the BrowserWindow's size is the initial monitor's size, not the size of the monitor that we've repositioned the window to.
Repository: godot
Issue: Godot produces confusing error when a variable identifier shadows a keyword
Labels: enhancement,topic:gdscript

**Godot version:**
3.1.1

**Issue description:**
Godot doesn't allow scripts to create identifers which shadow keywords, this is good and makes sense. Godot serves an error which doesn't help the developer notice when they have misused a keyword however, which leads to confusion.

> Parser Error: Expected identifier for local variable name.

**Steps to reproduce:**
1. Attempt to use a reserved keyword as a variable name
2. The interpreter serves an error which doesn't appear on the surface related to the actual issue

> Parser Error: Expected identifier for local variable name.

**Minimal reproduction project:**
```
extends Node

func _ready():
    var floor = "test" # error
```
Repository: flutter
Issue: Embedder API should warn when software and GL renderer backing stores are mixed.
Labels: engine,e: embedder,P2,team-engine,triaged-engine

Currently, it is embedder responsibility to be consistent with the client rendering API of the backing stores being used with the custom compositor. However, mixing them will lead to significant performance issues (if it works at all in the case of a software root surface renderer config and a an OpenGL compositor backing store).

The embedder API must make sure the client rendering API of the compositor backing stores matches the root renderer config and return an error otherwise.
Repository: TypeScript
Issue: Investigate altering extension priorities for wildcard loading
Labels: Bug,Fix Available

Our rules for loading files from wildcard matches prioritize `.d.ts` files over `.json` files (and at the same priority as `.js` files). Now that we support declaration files for `.json` and `.js` files, this is undesirable, as when declarations are emitted in-place (ie, with `emitDeclarationsOnly`), subsequent compilations using wildcard lookups will load the generated declaration files over the original source `.js` (maybe) and `.json` (definitely) files. Fixing this would require rejiggering the extension priority machinery in `src\compiler\utilities.ts`, so that declaration files are truly the lowest priority extension to load. [This comment thread](https://github.com/microsoft/TypeScript/pull/32372#discussion_r328195950) has a bit more discussion on the topic. A cursory glance also leads me to believe that extension priorities for `extraFileExtensions` as passed into `getSupportedExtensions` are largely unhandled, so there's probably a fair chunk of work here to revisit this system.

In the meantime, if you encounter an issue likely caused by this discrepancy, the workaround is pretty simple: Use the `outDir` compiler option.
Repository: flutter
Issue: flutter_root/testing requires dart runtime to be linked in separately to build embedding test.
Labels: engine,e: embedder,P3,team-engine,triaged-engine

When we build embedding unit test executable we usually have to link
```
"$flutter_root/testing"
"//third_party/dart/runtime:libdart_jit"
```
together. Otherwise, build will fail.

We should refactor flutter_root/testing or create a new target that include both group so that we do not have to explicitly link both targets.
Repository: TypeScript
Issue: Rewrite `getAccessibleSymbolChain` for performance
Labels: Domain: Declaration Emit,Experience Enhancement,Domain: Performance

`getAccessibleSymbolChain` is one of the oldest parts of the compiler - remaining today mostly unchanged (barring support for new features) from when it was used in the old text-based declaration emitter. `getAccessibleSymbolChain` is used to, given a `[symbol, scope]` pair, find a series of symbols whose exports can be accessed to lookup the symbol. Today, this is by and large uncached, so the fail case, when a symbol is _not_ accessible, causes a traversal of every publicly reachable symbol in a program - this process is then repeated for every symbol that needs to be named, which means you end up spending a _very_ long time traversing symbol structures. On normal typescript code, the inefficiency is less outsized, as we only need to invoke this code when we generate inferred types in declaration emit, which is more rare in TS output than in JS output, however you can still find projects where its' influence is large (some of @AnyhowStep 's samples bad performance in declaration emit trace back to this).

As far as the direction of the fix goes - I have some ideas. Today, we enumerate all possibilities and just backtrack to see what works - instead, I imagine using a (cacheable) set-like structure to check if the symbol is even accessible from a given symbol, and then use a hierarchy of these sets to guide chain creation.
Repository: vscode
Issue: ctrl + click "go to definition" clashes with ctrl + click "follow link"
Labels: bug,editor-symbols

@AngusWR commented on [Wed Sep 25 2019](https://github.com/microsoft/vscode-python/issues/7591)


## Environment data

- VS Code version: Version: 1.38.1
- Extension version (available under the Extensions sidebar): Version: 2019.9.34911
- OS and version: Windows 10 Pro 1903 18362.356
- Python version (& distribution if applicable, e.g. Anaconda): 3.6.7

## Expected behaviour

ctrl + click on a string representation of a url opens the url in chrome

## Actual behaviour

ctrl + click on a string representation of a url opens the url in chrome and also goes to the definition for str in builtins.pyi


Holding ctrl and hovering the url:

![1](https://user-images.githubusercontent.com/46464807/65584584-73bf1f00-dfc4-11e9-8d43-c1e5aa92735f.jpg)



After clicking the url

![2](https://user-images.githubusercontent.com/46464807/65584596-76ba0f80-dfc4-11e9-899d-f50b3af833b7.jpg)


I haven't been able to find a way of changing the key binding for the "go to definition" feature. Any advice?

---

@karrtikr commented on [Thu Sep 26 2019](https://github.com/microsoft/vscode-python/issues/7591#issuecomment-535717671)

For changing keybindings, go to `File` -> `Preferences` -> `Keyboard shortcuts`. Search for `Go to definition`.
Anyways, this is controlled by VSCode, not the extension. So I am transferring the issue.
Repository: TypeScript
Issue: How to pass along .d.ts comment on function that returns a class extending React.Component
Labels: Bug,Domain: Quick Info

From: https://stackoverflow.com/questions/58088678/how-to-pass-along-d-ts-comment-on-function-that-returns-a-class-extending-react?noredirect=1#comment102571859_58088678

I've got a .d.ts file I'm writing for an npm module teselagen-react-components that is a set of functions/react components. Here is a subset of the definition file in question:  


```js
import * as React from "react";


/**
 *
 * I'm a comment
 */
declare class GenericSelect extends React.Component<GenericSelectProps, any> { }

export interface GenericSelectProps {
  layout: string;
}

declare function createGenericSelect() {
  return GenericSelect
}
```

In another module I have a file like so: 
```js
//./myOtherProject/someFile.js
import { createGenericSelect, GenericSelect } from "teselagen-react-components";
const GenSel = createGenericSelect()
return <GenSel />
return <GenericSelect />
```

The issue I'm seeing is that when I hover  `<GenericSelect />` I am able to see the comment: 
[![GenericSelect with comment][1]][1]


But when I hover the <GenSel/> component, I can't see it!
[![GenSel with no comment][2]][2]

If instead of this line:
```
/**
 *
 * I'm a comment
 */
declare class GenericSelect extends React.Component<GenericSelectProps, any> { }
```
I had 
```
/**
 *
 * I'm a comment
 */
declare function GenericSelect { }
```

Then I do see the comment!

[![GenSel() with comment][3]][3]

Why?

Thanks!


  [1]: https://i.stack.imgur.com/85DEX.png
  [2]: https://i.stack.imgur.com/K8X47.png
  [3]: https://i.stack.imgur.com/tOpg6.png
Repository: go
Issue: go/internal/gcimporter: single source of truth for decoder logic
Labels: NeedsInvestigation

It's somewhat tedious to have to maintain go/internal/gcimporter in both the standard repo and in x/tools. Can we find a better solution here?

E.g., we vendor a bunch of other x/ repos into the main build. Could we do that for x/tools/go/internal/gcimporter too?

I know go/internal/gcimporter is more aggressive about pruning backwards compatibility code than x/tools/go/internal/gcimporter, but I'd think we could still use the same code base and just either use different entry points into it, or build it in different ways.

/cc @griesemer @alandonovan
Repository: flutter
Issue: No scrollbar in (infinite) list widget.
Labels: c: new feature,framework,f: scrolling,platform-web,a: desktop,P2,team-framework,triaged-framework

While following and completing the instructions on [Write your first app](https://flutter.dev/docs/get-started/codelab#step-4-create-an-infinite-scrolling-listview), the resulting application does have an infinite scrolling list, but there is no (updating) scroll bar to show the "progress" of the list.

I would expect a scroll bar allowing to navigate from the first element to the "last element in memory", and updating as new content keeps loading.
Repository: pytorch
Issue: conv2d Memory usage is too large； pytorch 1.1.0
Labels: module: dependency bug,module: cudnn,module: memory usage,module: convolution,triaged

## 🐛 Bug

Some specific situations, such as batch_size = 32, in/out_channels = 128, h = 1, w = 128 and kernel_size = 7, Memory usage is too large.
if kernel_size = 5,  Memory usage is a few MB;
but if kernel_size = 7, Memory usage can reach 10GB!

## To Reproduce
you can run this code and test different situations。

```
import torch as t
import numpy as np
from torch import nn

def main():
    print(t.__version__)
    kernel_size = 7 # 5
    conv = nn.Conv2d(128, 128, kernel_size, 1, (kernel_size - 1) // 2, bias = False)
    conv.cuda()
    x = t.ones([32, 128, 1, 128], device = 'cuda')
    conv(x)
    a = input()

if __name__ == '__main__':
    main()
```

## Environment
pytorch version: 1.1.0
OS: Ubuntu
CUDA Version: 9.0
cudnn Version: 7.0.5
Repository: youtube-dl
Issue: youtube-dl auto-completion in not working in ubuntu 18.04
Labels: question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

In the past, I used youtube-dl and auto-completion feature was working fine. Now I am using ubuntu 18.04 and installed youtube-dl manually with curl. youtube-dl is working fine but it doen's complete any command. I even tried pip and distro installation but nothing is working for me, any help?
Repository: TypeScript
Issue: Language service doesn't output neither errors nor crashes
Labels: Needs Investigation

Language service doesn't output errors even when it crashes in these months. So developers can't report neither bugs nor crashes of language service. And this behavior hides type errors.

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.4.0-dev.20190926

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

1. Reproduce #33617.
1. VSCode must output crash logs of language service but actually doesn't output anywhere in the output panel.
1. Make a type error like #33616.
1. This type error must be reported on VSCode but actually not, because probably language service has crashed.
1. VSCode must output errors of language service but actually doesn't output anywhere in the output panel.

**Expected behavior:**

**Actual behavior:**

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: pytorch
Issue: Batched Dataloader
Labels: feature,module: dataloader,triaged

## 🚀 Feature
Add a mode to `Dataset` that enables fetching data in batches instead of item-by-item.

## Motivation
If model training takes relatively small individual examples as an input, like in the case of training on tabular data, the python interpreter overhead of fetching data becomes so large that hinders training performance. In other words, training becomes CPU-bound (even with multiprocessing enabled).

This came up in a real scenario of the StarSpace model from FAIR.

## Pitch

Add an optional `__getbatch__` method to the `Dataset` that's analogous to `__getitem__` but takes a collection of indices as an input. Make the `Dataloader` aware of `BatchedDataset`. Once the `Dataloader` recognizes that the `__getbatch__` is present, that method is used for fetching data, one batch at the time.

As a result, the user receives an ability to pass data in batch end-to-end and avoid the high cost (per byte read) of python interpreter.

I implemented a variant of batch loading for aforementioned StarSpace model and got the training down from 5.5 days to under 24 hours. The person who originally implemented it used standard PyTorch data loading abstractions and fall into the trap of low performance. 

This is a type of issue anybody working on e.g. tabular data will be running into. Unfortunately, there's no natural way out given current PyTorch abstractions.

## Alternatives

Implement this on top of existing abstractions by "smuggling" batches values wrapped as a single value and unwrapping them in a custom collate function. The code, that I provide below, is fairly subtle and a bit hacky (abusing current abstractions). The code is fully functional and used in production, though.

Edit: I found also this: https://github.com/pytorch/pytorch/pull/19228 which a different way of implementing what I need. The downside of IterableDataset is that it essentially throws through the window the nice decomposition into Dataset, Sampler and Dataloader. Suddenly, you're responsible for implementing all of the logic. Having said that, this is a big improvement over my rather hacky solution I posted below.

cc @SsnL
Repository: terminal
Issue: Add support for roaming settings.json or storing it elsewhere
Labels: Issue-Feature,Help Wanted,Area-Settings,Product-Terminal


<hr>

> **Note**: 📌 Pinned comment: **https://github.com/microsoft/terminal/issues/2933#issuecomment-536652883**

<hr>

# Description of the new feature/enhancement

I have three different computers that I use for work. I keep my PowerShell profile in a GitHub repository and dot source it in my local PowerShell profile. That way I will only need to do a `git pull` on my profile repository to get all changes propagated on each computer.

It would be great if I could do something similar with my Windows Terminal settings by simply stating in my local settings.json file that the "real" settings could be found somewhere else. 

(It could even be that the loaded profile acts like a base for the settings on the computer so things could be overridden, but that is a completely different issue that remains to be opened)

I'm aware that I might have overlooked something here, but would love to start a discussion about this since I suspect that I'm not the only one with this "problem".

# Proposed technical implementation details (optional)

```json
{
    "$schema": "https://aka.ms/terminal-profiles-schema",
    "globals": {
        "loadProfileFrom": "C:/Source/git/profiles/terminal_profile.json"
    }
```
Repository: terminal
Issue: Feature Request: Icon buttons to start relevant shell types
Labels: Issue-Feature,Area-UserInterface,Area-Extensibility,Product-Terminal

Feature request: Add icon buttons to the Windows Terminal title bar for the installed shell types (instead of the current drop down menu). Each button would start the relevant shell type.  The buttons could have tool tip/mouse over for the shell type label/description.

The feature would enable one click start of the desired shell type. Currently, other than the default shell type, there's one click for the drop down, one more for the desired shell type from the list.

Then consider deprecating:
- the + button (start default shell). 
- the drop down menu of the shell types
Repository: vue
Issue: Prevent Vue.use to be used without options parameter unless it's specified as optional (with `?`)
Labels: improvement,typescript

### What problem does this feature solve?
**Reproduction link**
Please see: https://tinyurl.com/y5mlgqqh

**Steps to reproduce**

1. write a plugin
2. overload Vue.use ( see the given link above for detail )

**What is expected?**
During compiling it fails, because the types are not matching.

**What is actually happening?**
It compiles without errors

### What does the proposed API look like?
A possible solution is to change the type in vue/types/vue VueConstructor to: 

` use(plugin: PluginObject<unknown> | PluginFunction<unknown>, ...options: unknown[]): VueConstructor<V>;`

See: https://tinyurl.com/y6anfs8b

<!-- generated by vue-issues. DO NOT REMOVE -->