sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: net: DNS load balancing during bursts of traffic
Labels: NeedsInvestigation,FeatureRequest

Right now inflight DNS lookups are [grouped together](https://github.com/golang/go/blob/master/src/net/lookup.go#L267). 

Since DNS resolution picks the [first available IP](https://github.com/golang/go/blob/master/src/net/dial.go#L417), this has the side effect of resolving the same IP when there are bursts in traffic. 

This was surprising to me since I expected load to be distributed amongst the resolved hosts, especially during these bursts (assuming equal RFC 6724 weighting).

Load distribution via DNS seems like a common use case/expectation - it would be nice to be able to enable randomized DNS resolution. Being able to disable DNS query grouping or customize the way the group key is generated would also work.
Repository: kubernetes
Issue: Finalizing objects not reflected in CLI
Labels: kind/feature,sig/cli,lifecycle/frozen

Assume I have an object, e.g. a Service, which has a finalizer.  When I delete that object, it correctly waits for the finalizer to be removed.  In that intervening period, I can not see any indication that the object is being deleted.  It does not show up in `kubectl describe`.  It is not an event.  If it gets stuck, I have NO indication that it is being deleted or if I know that, why it is not complete.

**What would you like to be added**:

Some consistent way to see that things are "currently being deleted, waiting for finalizers X, Y, Z"
Repository: TypeScript
Issue: noUnusedLocals throws errors for "never" type.
Labels: Suggestion,Awaiting More Feedback

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
nounusedlocals never 
nounusedlocals
never
never variable is not used error

**Code**


```ts
//NOTE: nounusedlocals is set to true in tsconfig.
enum Color {
  A,
  B,
}
function f(color: Color) {
  switch(color) {
    case Color.A:
      console.log("White");
      break;
    case Color.B:
      console.log("Black");
      break;
    default:
      const _:never = color;
  }
}
```

**Expected behavior:**
Compiles fine, prints nothing

**Actual behavior:**
Given variable _ is unused. _ is of type never which means it is expected to be never used. It is being declared as a compile time safety to ensure that we have cases over all the Color enum values.
Repository: TypeScript
Issue: TS with .js files and JSDoc: type is found, displayed and used - despite "TS2304: Cannot find name XYZ"
Labels: Domain: JSDoc,Needs Investigation,checkJs

TS 3.4.5, Webstorm 2019.1.1, node v11.14.0, Linux

Project: .ts files in src/, transpiled using Babel to lib/, *but files under test/ are .js files*

tsconfig.json has `allowJs` and `checkJs` set to `true` in order to check the .js files under test/  &mdash; which (CommonJS) `require(...)` transpiled .js files from lib/ (there also are .d.ts and .d.ts.map files for all files).

Every single TS type declared in src/ has an accompanying JSDoc `@typedef` (don't know if that is important or if TS does not even use it since there is the original TS type too).

The problem I see is a weird one, because what Typescript says and what it actually does is completely opposite!

In the IDE I see every single type declared in src/ files as read, and on mouseover I get `TS2304 Cannot find name "XYZ".`:

![Unbenannt-1](https://user-images.githubusercontent.com/25476357/56831914-bab8b500-686a-11e9-880a-e2a98985984d.png)

**However**, and this is the weird part (1 of 2): **It all works!**

Showing the type (in WebStorm, CTRL plus mouse-hover over a symbol, shows the correct information. Even on those red types, I get the type name and the file name of where it is declared. Variables show the correct autocompletion suggestions and type information, jumping to the type definition (the TS one) works too.

The other weird part (2 of 2) is that when I follow the suggestions to change e.g.

     * @param {SHA256Hash} hash

to

     * @param {import('../lib/core-types.js').SHA256Hash} hash

the symbols are no longer red &mdash; but now nothing works. No more type information or anything. (*Tried different import paths, also directly to the src/ files and without extension, for example.*)

This is the reason why I file this as a bug. It actually works, so it is not a feature request.

So all it needs is for TS to stop showing the "cannot find name" errors, I don't need a change in behavior, since it *does* find the names just fine.

<br>

PS: I realize this is probably deeper, the plugin does not specifically remove the comments, I think it is the `path.remove()` command from the underlying AST. That doesn't make it any better or even right though. [Others had similar issues in the past.](https://github.com/Microsoft/TypeScript/issues/17606)
Repository: kubernetes
Issue: API proxy strips URL query params when proxying websocket connections
Labels: sig/api-machinery

Tested on Kubernetes 1.14 (minikube 1.0). To reproduce:

1. deploy pod with a websocket server running:

    ```bash
    kubectl run wsserver --generator=run-pod/v1 --rm -i --tty --image ubuntu:disco -- bash -c \
      "apt-get update && apt-get install -y wget && \
      wget https://github.com/vi/websocat/releases/download/v1.4.0/websocat_1.4.0_ssl1.1_amd64.deb && \
      dpkg -i webso*.deb && \
      websocat -vv -s 0.0.0.0:8000"
    ```

2. in host shell outside minikube run the following websocat command to connect to the websocket server in your wsserver pod:

    ```bash
    websocat --binary --ws-c-uri=wss://192.168.99.100:8443/api/v1/namespaces/default/pods/wsserver:8000/proxy/test?foo=what - ws-c:cmd:'socat - ssl:192.168.99.100:8443,verify=0,cafile=$HOME/.minikube/ca.crt,cert=$HOME/.minikube/client.crt,key=$HOME/.minikube/client.key'
    ```
3. check the output of the server-side websocat and notice that **the query params are missing**: `[DEBUG websocat::ws_server_peer] Incoming { version: Http11, subject: (Get, AbsolutePath("/test")), headers: ...`
4. exec into your pod with the websocket server, and issue a local websocket connect.

    ```bash
    kubectl exec wsserver websocat ws://localhost:8000/test?foo=what
    ```

5. check output of the service-side websocat, now **the query params are present as to be expected**: `[DEBUG websocat::ws_server_peer] Incoming { version: Http11, subject: (Get, AbsolutePath("/test?foo=what")), headers: ...`

(note: updated instructions to be much simpler now)
Repository: flutter
Issue: BackdropFilter doesn't work as child of Opacity or other Filter widgets (was iOS dialogs fade in without blur)
Labels: framework,engine,a: animation,dependency: skia,a: fidelity,f: cupertino,has reproducible steps,P2,team-design,triaged-design,found in release: 3.19,found in release: 3.22

I'm on Android, using the Gallery, Cupertino / Alerts demo. When I tap a button, the dialogs fade in, but they don't blur the background until the animation is over, at which point the blur effect pops in.

Testing with v1.5.4.

cc @xster
Repository: flutter
Issue: Support embedding native views in macOS shell
Labels: c: new feature,engine,platform-mac,a: desktop,P2,team-macos,triaged-macos

We'll need support for embedding `NSView`s in Flutter views (e.g., for embedding a web view, as on mobile).
Repository: flutter
Issue: Implement PlatformView support on Windows
Labels: c: new feature,engine,platform-windows,customer: crowd,a: platform-views,a: desktop,P2,team-windows,triaged-windows

We'll need support for embedding native views in Flutter views (e.g., for embedding a web view, as on mobile).

~Obviously this depends on having a view-based Windows shell first (#30726).~
Repository: three.js
Issue: Geometries are not de-serialized in all cases
Labels: Suggestion

##### Description of the problem

Currently, there are geometries in THREE JS src that are not de-serializable.

- `EdgesGeometry`
- ~~`ParametricGeometry`~~
- ~~`TextGeometry`~~
- ~~`InstancedBufferGeometry`~~
- `WireframeGeometry`

There are 2 main reasons for this issue. 
- `ObjectLoader` doesn't handle these types. Every geometry has a `type` property which is the name of the geometry. `ObjectLoader` uses this to determine how to de-serialize the JSON. 
- Geometries are serialized differently if they contain a `parameters` property.

Based on @Mugen87's [comment](https://github.com/mrdoob/three.js/issues/16026#issuecomment-475947408), it sounds like increasing the complexity of `ObjectLoader` is undesirable. However, these geometries are currently serialized in a way where they can't be de-serialized.


My suggestion would be one of the following:

1. Make these geometries serialize as normal `BufferGeometry` and send a warning saying such. 
```javascript 
EdgesBufferGeometry.prototype.toJSON = function () {

	console.warn("EdgesBufferGeometry is not serializable. It will be serialized as BufferGeometry.");
	var parameters = this.parameters;
	this.parameters = undefined;
	var data = BufferGeometry.prototype.toJSON.call( this );
	this.parameters = parameters;

	return data;

};
```


2. Make these geometries not serializable and send a error saying such.
#### Example
```javascript
EdgesBufferGeometry.prototype.toJSON = function () {

	console.error("EdgesBufferGeometry is not serializable. Convert this geometry to BufferGeometry and call .toJSON() on that");

};
````


3. Make `ObjectLoader` handle these geometries

Related #16026, #16087, #14357

##### Three.js version

- [x] Dev
- [x] r104
- [ ] ...

##### Browser

- [x] All of them
- [ ] Chrome
- [ ] Firefox
- [ ] Internet Explorer

##### OS

- [x] All of them
- [ ] Windows
- [ ] macOS
- [ ] Linux
- [ ] Android
- [ ] iOS
Repository: vscode
Issue: [themes] Support for hue, saturation, lightness (HSL) color codes for theming
Labels: feature-request,themes

Support for hue, saturation, lightness (HSL) color codes for theme colors would allow for easier iteration in theme design by providing a more human readable format for color codes.

I find it much easier to modify color values using HSL than it is with hex codes because the values being modified more closely model how humans think about color rather than how the computer renders color.

Example:
```jsonc
{
  "colors": {
    "editor.background": "hsla(301, 46%, 9%, 1)", // #220c21,
  }
}
```
Repository: go
Issue: cmd/go: build: add -buildmode=nolink flag
Labels: Proposal,NeedsInvestigation,FeatureRequest,GoCommand

My understanding of the "go build" process is it does something like this:

- Figure out all of the dependencies of the package.
- For each dependency, determine whether it has changed since the last time it was built, by checking the `.a` file or equivalent in `$GOPATH/pkg`.
- Compile them, in parallel if possible
- Generate the new artifact (a `.a` file or similar) we checked in #2 that is now out of date.
- Link them all into a single binary.

I use `vim` to edit Go files. The most popular plugin, `vim-go`, recommends checking compilation by running `:GoBuild`. I do this frequently to ensure I have syntax correct, imports correct, a working Go program.

`:GoBuild` changes directory to the directory containing the file you are editing, then runs 

```
go build -tags '' . errors
```

It builds the "errors" package because vim-go desperately does _not_ want to build any final artifacts, and attempting to build multiple packages turns off the binary building behavior.

However, I notice that this never takes advantage of build caching. That is, if I run `:GoBuild` and then run `:GoBuild` again immediately without making changes, it takes 4 seconds on the package I am compiling. If I run `go build .` to compile an artifact, it is much faster, about 600ms on the second run.

Is there a way to make "go build" take advantage of whatever intermediate build steps exist - the `.a` files from above, or their equivalents - even if it does not produce a final binary?

Alternatively, can you work with the `vim-go` maintainers to recommend a different tool for checking a package (and/or test package) contains valid Go syntax and identifiers?
Repository: rust
Issue: .tar.gz dist files require running `install.sh` before they can be used
Labels: T-bootstrap,T-infra

If I download Rust using:

~~~
x86_64-pc-windows-gnu.tar.gz
~~~

from here:

https://forge.rust-lang.org/other-installation-methods#standalone-installers

it seems the compiler cant actually compile anything:

~~~
$ cat aaaaa.rs
fn main() {
   println!("bbbbb ccccc");
}

$ rustc aaaaa.rs
error[E0463]: can't find crate for `std`
~~~
Repository: TypeScript
Issue: KeyboardEvent interface implements key as string
Labels: Suggestion,Needs Proposal,Domain: lib.d.ts

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.3.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Actual Output**
![image](https://user-images.githubusercontent.com/26967284/56852502-302c9000-6914-11e9-9e12-4f3fbeaf7aa3.png)
The `key` property is defined as a string

**Expected Output**
The `key` property should be a enum of keys.
Repository: opencv
Issue: Core.NATIVE_LIBRARY_NAME and Jni so files name should be identicals
Labels: bug,category: build/install,category: java bindings

<!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

Please:

* Read the documentation to test with the latest developer build.
* Check if other person has already created the same issue to avoid duplicates. You can comment on it if there already is an issue.
* Try to be as detailed as possible in your report.
* Report only one problem per created issue.


This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
- OpenCV => 4.1.0 
- Operating System / Platform => Android
- Compiler => Android Studio


##### Detailed description

<!-- your description -->
Core.NATIVE_LIBRARY_NAME and Jni so file name should be identicals

##### Steps to reproduce
1. compile opencv-sdk with jni libs (libopencv_java4.so files)
2. `static { System.loadLibrary(Core.NATIVE_LIBRARY_NAME); }` at begin of class
3. Run opencv program.
Exception occur:
long exception description and then: `couldn't find "libopencv_java410.so`

Core.NATIVE_LIBRARY_NAME == "libopencv_java410"
jni.files = "libopencv_java4.so"

If I change to  `static { System.loadLibrary("libopencv_java4"); }`   
Everything is working. 
Add build.gradle I create for compile the sdk.
[build.gradle.txt](https://github.com/opencv/opencv/files/3124106/build.gradle.txt)
Repository: go
Issue: errors: examples need improvement
Labels: Documentation,NeedsFix

There is a total of 4 examples in the package. Two are for `New`, one doesn't use the package at all, and one incorrectly uses `As` by dropping the error on the floor if it's not a `os.PathError`.

```
	_, err := os.Open("non-existing")
	if err != nil {
		var pathError *os.PathError
		if errors.As(err, &pathError) {
			fmt.Println("Failed at path:", pathError.Path)
		}
	}
```
Repository: pytorch
Issue: Performance issue master (a25b79531)
Labels: module: performance,module: cpu,triaged,module: multithreading

## 🐛 Bug
To run the mnist example from https://github.com/pytorch/examples is taking more than twice long the usual

## To Reproduce

I have built the pytorch package from the repo ( BUILD_TORCH=ON python setup.py bdist_wheel).

I also have modified the num_workers option of the mnist example script from 1  to 8.

A lot of time is spent on iomp functions (see figure):
![perf_flamegraph_hotspot_mnist_master](https://user-images.githubusercontent.com/36332518/56854438-ea1ffe00-690c-11e9-8cea-3f29b30397b6.jpg)

Setting the environment variable OMP_NUM_THREADS=1  reduces the time to the usual ones on this machine.

## Expected behavior

To run at the usual speed without needing tho change the OMP_NUM_THREADS environment variable.

## Environment
PyTorch version: 1.1.0a0+a25b795
Is debug build: No
CUDA used to build PyTorch: 10.1.105

OS: Fedora release 29 (Twenty Nine)
GCC version: (GCC) 8.3.1 20190223 (Red Hat 8.3.1-2)
CMake version: version 3.14.2

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 10.1.105
GPU models and configuration: GPU 0: GeForce GTX 1080
Nvidia driver version: 418.56
cuDNN version: /usr/local/cuda-10.1/targets/x86_64-linux/lib/libcudnn.so.7.5.0

Versions of relevant libraries:
[pip3] numpy==1.16.2
[pip3] numpydoc==0.8.0
[pip3] torch==1.1.0a0+a25b795
[pip3] torch-nightly==1.1.0.dev20190423
[pip3] torchtext==0.3.1
[pip3] torchvision==0.2.3a0+0c36735
[pip3] torchvision-nightly==0.2.3
[conda] blas                      1.0                         mkl  
[conda] mkl                       2019.3                      199  
[conda] mkl-service               1.1.2            py37he904b0f_5  
[conda] mkl_fft                   1.0.10           py37ha843d7b_0  
[conda] mkl_random                1.0.2            py37hd81dba3_0  
[conda] torch-nightly             1.1.0.dev20190423          pypi_0    pypi
[conda] torchtext                 0.3.1                    pypi_0    pypi
[conda] torchvision-nightly       0.2.3                    pypi_0    pypi

## Additional context
The issue #18398 still occurring. I have copied the relevant libraries to a folder in the LD_LIBRARY_PATH.
Repository: puppeteer
Issue: waitForSelector with visible:true not returning the first visible element, causes timeout.
Labels: feature,confirmed

<!--
STEP 1: Are you in the right place?

- For general technical questions or "how to" guidance, please search StackOverflow for questions tagged "puppeteer" or create a new post.

https://stackoverflow.com/questions/tagged/puppeteer

- For issues or feature requests related to the DevTools Protocol (https://chromedevtools.github.io/devtools-protocol/), file an issue there:

https://github.com/ChromeDevTools/devtools-protocol/issues/new.

- Problem in Headless Chrome? File an issue against Chromium's issue tracker:

https://bugs.chromium.org/p/chromium/issues/entry?components=Internals%3EHeadless&blocking=705916

For issues, feature requests, or setup troubles with Puppeteer, file an issue right here!
-->

### Steps to reproduce

**Tell us about your environment:**
* Puppeteer version: 0.14.0
* Platform / OS version: MacOS (Dockerized in node:10)
* URLs (if applicable): https://j4q389wzv3.codesandbox.io/
* Node.js version: v10.15.3

**What steps will reproduce the problem?**
Open Website OR use this file:
```
<html>
  <head>
    <meta charset="UTF-8" />
  </head>

  <body>
    <input style="display: none" type="number" class="my-input-class" />
    <input type="number" class="my-input-class" />
  </body>
</html>
```

_Please include code that reproduces the issue._
```
const browser = await puppeteer.launch();

const page = await browser.newPage();
await page.goto('https://j4q389wzv3.codesandbox.io/');

try {
  const visibleInput = await page.waitForSelector('.my-input-class', {visible: true, timeout: 1000 })
  console.log('Found visible Element')
} catch (e) {
  console.log('Could NOT find a visible element ', e.message)
}

const inputs = await page.$$('.my-input-class')
console.log(`Found ${inputs.length} inputs`)

await browser.close()
```

**What is the expected result?**
There are 2 elements matching the CSS Selector on the page.  the first one is hidden, the second one is visible.  The `page.waitForSelector` with `{visible: true}` should have found and returned the visible element on the page.

**What happens instead?**
It Times Out since there was another HIDDEN element matching the CSS selector higher up in the DOM structure, causing it to wait until timeout even though a visible element exists on the page.
Repository: vscode
Issue: Source Control: "Accept All Incoming" for "deleted by them" should delete the file from working copy and stage the change
Labels: feature-request,merge-conflict

When:
![image](https://user-images.githubusercontent.com/611746/56856209-41c56600-691b-11e9-8e15-646bdd3c2820.png)

Actual:

- warning message: No merge conflicts found in this file

![image](https://user-images.githubusercontent.com/611746/56856211-4f7aeb80-691b-11e9-9711-d8506c000d03.png)

Expected:

- delete file from working copy
- stage the change (`git add`)

VS Code 1.33.1
Repository: go
Issue: crypto/rsa: doc: reword "coprime to" in doc comments
Labels: ExpertNeeded,Documentation,NeedsDecision

I found this paragraph in the `crypto/rsa` docs:

https://github.com/golang/go/blob/master/src/crypto/rsa/rsa.go#L187-L191
```
	// Check that de ≡ 1 mod p-1, for each prime.
	// This implies that e is coprime to each p-1 as e has a multiplicative
	// inverse. Therefore e is coprime to lcm(p-1,q-1,r-1,...) =
	// exponent(ℤ/nℤ). It also implies that a^de ≡ a mod p as a^(p-1) ≡ 1
	// mod p. Thus a^de ≡ a mod n for all a coprime to n, as required.
```

It is a mistake to say `x` is _coprime to_ `y`, because _co_ and _to_ convey the same thing. A number `x`, `y` can be coprime, but we say `x` is _prime to_ `y`. 

This is explicitly stated by Stewart in _Galios Theory_ 3rd Edition (ISBN 1-58488-393-6), in Definition 3.14 on the topic of coprimes.
Repository: vscode
Issue: [folding] Support flags on folding.markers RegExps
Labels: feature-request,editor-folding

A `language-configuration.json` file can supply a pair of regular expressions `start` and `end` [(doc)](https://code.visualstudio.com/api/language-extensions/language-configuration-guide#folding). At the moment there's no way to specify regexp flags, for example to make the matches case-insensitive.

Previous enhancements tackled a similar issue for `wordPattern` and `indentationRules` by allowing their regexps to be objects with `pattern` and `flags` properties.

Please enhance languageConfigurationExtensionPoint.ts [(code pointer)](https://github.com/Microsoft/vscode/blob/a47406b9c8aeed71e2b26ee41e0f275ead87da04/src/vs/workbench/contrib/codeEditor/browser/languageConfigurationExtensionPoint.ts#L313) to support `pattern` and `flags` on `start` and `end`. See also https://github.com/Microsoft/vscode/issues/27591#issuecomment-305175307

It'd also be good to augment [the doc](https://code.visualstudio.com/api/language-extensions/language-configuration-guide) , which currently doesn't mention the pattern+flags syntax.