sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: net/http: improve proxy handling
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/vico/Library/Caches/go-build"
GOENV="/Users/vico/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/vico/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
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=/var/folders/32/7qmymd5950b3nhv4dd7qbqkw0000gn/T/go-build036564932=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?
I'm running requests (using **go-resty library**, based on default HTTP client). This problem is I need to use proxies, some of proxies are dead (public proxies) and so, they don't answer the request. 
I started learning Go not a long time ago, but when I was programming in C#, the proxy handling was good, I mean :
- Most of proxies respond well. Here in Go, the proxy definition is sketchy (in my opinion). There is also no official way to put proxy with authentication (not sure?).
- When a proxy is dead, it throws an error fast. Here in Go, it waits for the default page timeout, not a connect timeout or something.

### What did you expect to see?
Proxy integration that respond better or that skips wrong/dead proxies faster.

### What did you see instead?
Mainly performance losses, and when I use public proxies, Go seems not connecting to all proxies while some are really working.

(Original issue from go-resty: https://github.com/go-resty/resty/issues/320)
Repository: pytorch
Issue: torch::jit::script::Object::attr should throw AttributeError instead of RuntimeError
Labels: oncall: jit,triaged

## 🐛 Bug

Not doing so breaks the `hasattr` builtin, as per https://docs.python.org/3/library/functions.html#hasattr

## To Reproduce

```python
import torch

nt = torch.classes._TorchScriptTesting_PickleTester([3, 4])
print(hasattr(nt, "non_existent_attr"))
```

```
Traceback (most recent call last):
  File "test_script_throw.py", line 4, in <module>
    print(hasattr(nt, "non_existent_attr"))
RuntimeError: __torch__.torch.classes._TorchScriptTesting_PickleTester does not have a field with name 'non_existent_attr'
```
## Expected behavior

`hasattr` should not throw

cc @suo
Repository: angular
Issue: Enter and leave animations don't behave as expected with parent-child relationships
Labels: type: bug/fix,area: animations,freq3: high,P3

# 🐞 Bug report

### Affected Package
@angular/animation or @angular/core

### Is this a regression?
I've made a Stackblitz with Angular 9, 8  and 7. All versions have this problem.

### Description
There is a problem when you nest a component with an :enter and :leave animation inside a parent which is conditionally visible using *ngIf. When the parent is visible for the first time there is no issue. Once you trigger the parent to leave and enter again, the child will not be visible.
It looks like the leave animation of the child gets triggered when the parent leaves but the enter animation isn't fired once the parent enters again.

## 🔬 Minimal Reproduction
I've made a simple example in Stackblitz. You can even make it less complex by removing the animations on the collapsible panel.
[Stackblitz with Angular 17](https://stackblitz.com/edit/angular-17-animations-bug)
[Stackblitz with Angular 9](https://stackblitz.com/edit/angular-9-animations-bug)
[Stackblitz with Angular 8](https://stackblitz.com/edit/angular-8-animations-bug)
[Stackblitz with Angular 7](https://stackblitz.com/edit/angular-7-animations-bug)


## 🌍  Your Environment
Angular 9 but it's also reproducible in 8 and 7.
Stackblitz contains my package versions.
Repository: pytorch
Issue: ExceptionWrapper cannot handle exceptions with more than one argument
Labels: module: dataloader,module: error checking,triaged

## 🐛 Bug

_utils.py: ExceptionWrapper cannot handle exceptions with more than one argument

## To Reproduce

Steps to reproduce the behavior:

1. Create a DataLoader
2. Raise an error that takes multplie arguments in the constructor, eg. `urllib.error.HTTPError`

```
/torch/_utils.py", line 394, in reraise
    raise self.exc_type(msg)
TypeError: __init__() missing 4 required positional arguments: 'code', 'msg', 'hdrs', and 'fp'
```

## Expected behavior

ExceptionWrapper shouldn't throw in reraise. The exception should be wrapped in a generic Exception or initialized with all arguments (not sure if that's possible? Perhaps passing the exception object from the worker would be better)

## Environment

Please copy and paste the output from our
PyTorch Version (e.g., 1.0): 1.4.0
OS (e.g., Linux): CentOS 6.3
How you installed PyTorch (conda, pip, source): pip
Build command you used (if compiling from source):
Python version: 3.6.5
CUDA/cuDNN version: 10.0, 7.5
GPU models and configuration: P4


cc @SsnL
Repository: flutter
Issue: hide the samples related commands from `flutter create`
Labels: tool,P3,team-tool,triaged-tool

We should hide the sample related commands from `flutter create`. IDEs don't call these anymore - they instead identify samples in-line in the source code you have open, and show hyperlinks to open the hosted versions of these samples in the generated docs.

And, the samples aren't pedagogical getting started flutter apps, unlike the `flutter create` templates. Having both samples and templates in flutter create is esp. confusing for new users, as to which ones they should create to get started.

```
-s, --sample=<id>              Specifies the Flutter code sample to use as the main.dart for an application. Implies --template=app. The value
                               should be the sample ID of the desired sample from the API documentation website (http://docs.flutter.dev). An
                               example can be found at https://master-api.flutter.dev/flutter/widgets/SingleChildScrollView-class.html

    --list-samples=<path>      Specifies a JSON output file for a listing of Flutter code samples that can created with --sample.
```
Repository: opencv
Issue: DNN - Add support for XNNPACK Target for NN acceleration on ARM Devices
Labels: optimization,feature,category: dnn,platform: arm

I'd love to see XNNPACK as an inference engine for DNN, especially for running models on low-powered ARM devices. Thanks!

https://github.com/google/XNNPACK
Repository: material-ui
Issue: Popover - Cannot close Popover when using screen reader (Voiceover w/ Safari on Mac and iPad)
Labels: accessibility,component: Popover

- [X] The issue is present in the latest release.
- [X] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Current Behavior 😯

Currently you are unable to close a Popover when you are using a screen reader. I tested this on Safari on Mac and iPad with Voiceover. You end up getting into a focus trap where you cannot tab anymore once the Popover opens, so you cannot get back to the button that opened it to close it again.

## Expected Behavior 🤔

You should be able to tab away when a Popover is open so you can close it again.

## Steps to Reproduce 🕹

Steps:

1. Go the MUI site's Popover page https://v4-3-3.material-ui.com/components/popover/
2. Turn on your screen reader
3. Tab down to the Open Popover button in the first example, "Simple Popover"
4. Click the space bar or enter to press the button. Notice that the focus has not shifted to being onside the Popover and the content is read out.
5. Try to tab or back tab to get away from the Popover content and get to a different interactive element on the screen. You are unable to do so.

The only behavior I can do is press the up arrow key which will send the focus to text at the bottom of the screen and read it out, but you cannot get to interactive elements so there's no way to close the Popover.

## Context 🔦

This is blocking screen reader users from being able to close the Popover and creates a focus trap so they are not able to use any other interactive elements on a screen once a Popover has been opened.

## Your Environment 🌎


| Tech        | Version |
| ----------- | ------- |
| Material-UI | v4.3.3  |
| React       |         |
| Browser     |  Safari (best browser for using Voiceover)  |
| TypeScript  |         |
| etc.        |     iOS Sierra v10.12.6    |
Repository: rust
Issue: [rustdoc] Fuzzy search in rustdoc should be configurable
Labels: T-rustdoc,C-feature-request

I was in the std docs, and searched for "then" looking specifically for things that are "then" or "and_then". I ended up getting a LOT of results for "len"

I find that for things like grep, rg, search and replace, ctags, etc., when searching code, I want either exact matches, or exact machines (case insensitive).

Would it be possible to make this exact? or at least configurable?

Thanks!
Repository: go
Issue: x/build: investigate possibility of supporting Go tests that require use of Docker in trybots/builders
Labels: Builders,NeedsInvestigation,FeatureRequest

We would like the trybots to be able to run a docker container.

The discovery site needs a postgres database to run tests, and we've been starting it in our CI with `docker run`. 

An alternative would be to install postgres in the trybot image, but that's probably more difficult and definitely less general.
Repository: TypeScript
Issue: Path based Code navigation to /index.js seems broken
Labels: Suggestion,Experience Enhancement

- VSCode Version: 1.42.1
- OS Version: Mac OS

Steps to Reproduce:
Code navigation seems broken when you import by path and the file is actually in an index.js file.
There are a couple of scenarios relevant to developing in react-native

1. import from another package in a monorepo `import SomeComponent from 'common-lib/Router`, when the file is `packages/common-lib/src/Router/index.js`
2. import in the same package `import SomeComponent from 'modules/Router`, when the file is `src/modules/Router/index.js`
3. `import SomeComponent from 'modules/Router`, when the file is not actually index.js `src/modules/Router/index.ios.js` and `src/modules/Router/index.android.js`

In general, what works is loading a file name by name (not an index.js file)
What doesn't work is loading a file by path that is actually an index.js, index.native.js, index.ios.js, index.android.js etc file

My code structure is
```
root
    packages
           mobile
           server
                src
                       server
                       shared
           common-lib
```

There is some history here that is not ideal. But ok.

packages/server jsconfig.json
```
{
	"compilerOptions": {
		"target": "es2017",
		"allowSyntheticDefaultImports": false,
		"baseUrl": ".",
		"paths": {
			"common-lib/*": ["../common-lib/*"],
			"mobile/*": ["../mobile/*"],
			"modules/*": ["./src/shared/modules/*"],
			"components/*": ["./src/shared/components/*"],
			"router/*": ["./src/shared/router/*"],
			"server/*": ["./src/server*"],
			"App": ["./src/App"]
		}
	},
	"exclude": ["node_modules", "../../node_modules", "build"]
}

```
<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: TypeScript
Issue: Add extract to parameter refactoring for JS/TS in vscode
Labels: Suggestion,Awaiting More Feedback,Domain: Refactorings

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## 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

Add a refactoring to extract to parameter for JS/TS

e.g.

for

```

const fangler = () => {
  return {
    someProperty: [
      "a", "b"
    ]
  }
}

```

the extract to parameter refactoring would change to 

```

const fangler = (secondItem) => {
  return {
    someProperty: [
      "a", secondItem
    ]
  }
}

```

and populate each existing call site with the extracted value (in this example "b")

## Use Cases

It is a common refactoring when you discover that a previously fixed value should instead be provided by a caller

## Examples

e.g. in the case where I went looking for it code in a Lambda function that created a fixed header had to start providing a varying value depending on context and the easiest refactoring was to extract the currently fixed value as a parameter so that the callers that would vary it could do without breaking other callers

see https://twitter.com/mattbierner/status/1234920525543002113

## 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.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: go
Issue: text/template: JSEscape generates invalid JSON
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/shang/.cache/go-build"
GOENV="/home/shang/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY="*.epic.com"
GONOSUMDB="*.epic.com"
GOOS="linux"
GOPATH="/home/shang/go"
GOPRIVATE="*.epic.com"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build973203171=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Ran this code:
```
package main

import (
        "log"
        "os"
        "text/template"
)

func main() {
        const plate = `"{{ .Value | js}}"`

        type Vals struct {
                Value string
        }

        vals := &Vals{`=`}

        t := template.Must(template.New("plate").Parse(plate))

        err := t.Execute(os.Stdout, vals)
        if err != nil {
                log.Println("executing template:", err)
        }

}
```

### What did you expect to see?

Expected to see `"="`, which is the behavior in `go1.13.8`

### What did you see instead?

Insead see `"\x3D"`.
Repository: TypeScript
Issue: Inference from rest parameters has strange inconsistent results
Labels: Needs Investigation

```ts
declare function foo(...x: readonly any[]): any

type FooParams = Parameters<typeof foo>;

declare function bar(...x: readonly number[]): any

type BarParams = Parameters<typeof bar>
```

**Expected**:

* `FooParams` is `any[]` or `readonly any[]`
* `BarParams` is `number[]` or `readonly number[]`

**Actual**

* `FooParams` is `unknown[]`
* `BarParams` is `never`

[Playground link](http://www.typescriptlang.org/play/index.html#code/PTAEHUEsBcAsHsCu1QCcCmBDAJvAdgDYCeAsAFDnboDGBmGoAZontdJPk-PABQB0AgB4AuUJjxEA2gF0AlKPGkKZaEQAO6UADFuABXqYAtgGdQAXlD7UR9NHSpjAHlUb4jLvAB8AbnKUadAzMrOycAEb0-EKieIiGYfYy8mISfirqmgBC9FZGpha5hrb2Ti7obqARqJ5pIBAwsGhYuIRK-rT0msFsHHhojNxRfCJNOPjEKVJyCqnKZaAASjrwhfmWBkV2Ds4ZFagDXr7KVB1BLD2cqFVDIxhjraCx8YnTk2nzC9moq+br1pslHaudxXeg1MhAA)
Repository: flutter
Issue: Add platform screenshot capability to package:integration_test
Labels: a: tests,c: new feature,framework,customer: crowd,c: proposal,f: integration_test,P1,team-framework,triaged-framework

add screenshot capability to e2e web integration tests. 

These screenshots should be easy to trigger from the widget tests, but should be taken on the platform (by the browser's driver).
Repository: node
Issue: Docs only shows version subset in navigation
Labels: doc,meta

* **Browser version**: Chrome Version 80.0.3987.106
* **Operating system**: macOS 10.14

When viewing a given API reference on the website, there's an option to view another version:

<img width="688" alt="Screen Shot 2020-03-03 at 11 13 02 AM" src="https://user-images.githubusercontent.com/2036040/75810734-fac8ae00-5d3f-11ea-9e10-0de3e19b1826.png">

It allows for a user to pick another version to swap to and see relevant docs, but it's constrained by what existed at the time the _currently chosen doc_ was written. This means that e.g when a user picks v11.x, they won't be able to go back to v13.x:

<img width="732" alt="Screen Shot 2020-03-03 at 11 14 25 AM" src="https://user-images.githubusercontent.com/2036040/75810846-32375a80-5d40-11ea-97a0-23c7e06e0b30.png">

without first going back to v12.x.

I'd say this is an antipattern, and that we should unilaterally be storing the versions available in the most recently defined major line. If this seems like a good path forward, i'm happy to implement this myself!
Repository: flutter
Issue: Engine repo should be able to run tests that depends on the framework.
Labels: framework,engine,c: proposal,P3,team-engine,triaged-engine

This issue tracks the effort of making engine repo run flutter driver and e2e tests.

Flutter driver integration tests are not currently set up to be run in the engine.
When we fix engine code that is not directly testable in the engine, for example, platform view related code. We would need to create an integration test in the framework. The test won't run until the engine fix rolled into the framework. This creates a delay to find out whether the engine fix breaks tests.

Although not every integration test can be tested in engine, the ones that merely exists for engine behaviors should be run in the engine repo. Such tests include `flutter_driver_screenshot_test` as the time this issue is created.

Setting up flutter driver/e2e tests in engine can also help testing in engine easier. We currently use the [scenario app](https://github.com/flutter/engine/tree/master/testing/scenario_app) to run integration tests in engine. Although the `scenario app` can handle simple cases like screenshot and touch events, it is hard to wire up a test in the `scenario app` that handles complicated situations such as thread merging. The `scenario app` test case is much harder to write compares to flutter driver tests or e2e tests.

There is already a [ci script](https://github.com/flutter/engine/blob/master/.cirrus.yml#L19) in engine repo to fetch the framework for web team to run web related tests. We should be able to do something similar for mobiles and other platforms.
Repository: TypeScript
Issue: Release Automation Meta Issue
Labels: Infrastructure,Meta-Issue

We're trying to find ways to reduce the amount of manual work that a release requires. This currently includes

* [x] https://github.com/microsoft/TypeScript/issues/36863
* [ ] https://github.com/microsoft/TypeScript/issues/36864
* [ ] https://github.com/microsoft/TypeScript/issues/34818

More may be added to this list over time
Repository: pytorch
Issue: END_HANDLE_TH_ERRORS_PYBIND prevents pybind11 Exception translation
Labels: triaged,module: pybind

## 🐛 Bug

[pybind11 allows exception translation](https://pybind11.readthedocs.io/en/stable/advanced/exceptions.html#built-in-exception-translation) by [catching and translating C++ exceptions](https://github.com/pybind/pybind11/blob/1376eb0e518ff2b7b412c84a907dd1cd3f7f2dcd/include/pybind11/detail/internals.h#L215). This is similar to what we do within [END_HANDLE_TH_ERRORS_PYBIND](https://github.com/pytorch/pytorch/blob/4b3ae7e0af17cfaab832fd7954f5bfad07cee0ba/torch/csrc/Exceptions.h#L82) as well, in the sense that we also inspect the thrown type and handle it differently in some cases (e.g. py::builtin_exception). However, due to CATCH_ALL_ERRORS we prevent pybind from catching something like a std::out_of_range and instead bubble up a PyExc_RuntimeError. For the pybind11 user that's writing code out of tree and uses wrap_pybind_function as exception translation for at:: specific errors this means they have to  setup their own translation within the wrapped function to get the proper error.

## To Reproduce

To reproduce this behavior register a simple pybind11 function that throws out_of_range and see it turn into RuntimeError and not IndexError. I can provide a code snippet if needed.

## Expected behavior

I'd expect us to simply forward the exception and rely on pybind11 to do the proper translation for the listed functions, so we can simply forward them. I think this is ok, because END_HANDLE_TH_ERROR_PYBIND is explicitly written for pybind11.




## Environment

```
$ python torch/utils/collect_env.py
Collecting environment information...
PyTorch version: 1.5.0a0+45c4519
Is debug build: Yes
CUDA used to build PyTorch: Could not collect

OS: Ubuntu 18.04.3 LTS
GCC version: (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
CMake version: version 3.12.2

Python version: 3.7
Is CUDA available: No
CUDA runtime version: 9.2.88
GPU models and configuration:
GPU 0: Quadro GP100
GPU 1: Quadro GP100

Nvidia driver version: 418.116.00
cuDNN version: Could not collect

Versions of relevant libraries:
[pip3] gpytorch==0.2.1
[pip3] numpy==1.16.4
[pip3] torch==1.5.0a0+45c4519
[pip3] torchvision==0.6.0a0+0156d58
[conda] blas                      1.0                         mkl
[conda] gpytorch                  0.2.1                    pypi_0    pypi
[conda] magma-cuda100             2.5.0                         1    pytorch
[conda] mkl                       2019.4                      243
[conda] mkl-include               2019.4                      243
[conda] mkl-service               2.3.0            py37he904b0f_0
[conda] mkl_fft                   1.0.15           py37ha843d7b_0
[conda] mkl_random                1.1.0            py37hd6b4f25_0
[conda] torch                     1.5.0a0+45c4519           dev_0    <develop>
[conda] torchvision               0.6.0a0+0156d58           dev_0    <develop>
```

Compiled from source

## Additional context

This showed up in the context of porting [NestedTensor.to_tensor into C++](https://github.com/pytorch/nestedtensor/pull/74).