sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking Issue for io_error_more
Labels: T-libs-api,C-tracking-issue,disposition-merge,finished-final-comment-period,A-error-handling,A-io

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(io_error_more)]`

This is a tracking issue for many `io::ErrorKind` variants being added in #79965.

The additions were motivated by a perusal of Unix standards, but corresponding mappings for Windows were included in that PR.

### Public API

`std::io::ErrorKind::Foo` for many `Foo`.  I will paste a list here when the MR is merged :-).

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #79965
- [ ] Final commenting period (FCP)
- [ ] Partial Stabilization - https://github.com/rust-lang/rust/pull/128316
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final commenting period
(FCP) is always needed before stabilization. This works as follows:

A library team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
commenting period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- What is our general policy about `ErrorKind` variants ?  It may not be necessary to resolve this wider question in order to stabilise this particular set of `ErrorKind`s.
Repository: go
Issue: x/playground: a test that terminates itself with a signal is spuriously reported as passing
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.17-45f251ad6 Thu Jun 17 21:58:54 2021 +0000 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="/usr/local/google/home/bcmills/.cache/go-build"
GOENV="/usr/local/google/home/bcmills/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/tmp/tmp.BvIzRvpmLB/.gopath/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/tmp/tmp.BvIzRvpmLB/.gopath"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/google/home/bcmills/sdk/gotip"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/google/home/bcmills/sdk/gotip/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.17-45f251ad6 Thu Jun 17 21:58:54 2021 +0000"
GCCGO="/usr/local/google/home/bcmills/bin/gccgo"
AR="ar"
CC="gcc"
CXX="c++"
CGO_ENABLED="1"
GOMOD="/tmp/tmp.BvIzRvpmLB/go.mod"
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-build2893288510=/tmp/go-build -gno-record-gcc-switches"

</pre></details>


### What did you do?

1. Wrote the program in https://play.golang.org/p/Natjl4SGrTr into a file `main_test.go` in a local package.
2. Ran `go test .`
3. Compared the result with the output reported on https://play.golang.org/p/Natjl4SGrTr.


### What did you expect to see?

I expected the Playground to produce roughly the same result as `go test .`, which reports the test as failing:
```
$ go test .
2021/06/18 13:32:15 Huh‽
FAIL    example.com/m   0.013s
FAIL
```


### What did you see instead?

The output from the Playground is:

<pre><span>=== RUN   TestLogPrintf
</span><span>2009/11/10 23:00:00 Huh‽
</span><span>
All tests passed.</span></pre>

CC @golang/release
Repository: pytorch
Issue: provide hashsum for downloads
Labels: module: binaries,triaged

## 🚀 Feature

Please provide hash sums for files provided at https://pytorch.org.

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

At the moment, there is no way to verify that downloaded files (e.g. `libtorch-cxx11-abi-shared-with-deps-*.zip`) are not corrupted. If these files are used in build scripts that verify their integrity, then a user has to manually download them, trust that they are not corrupted and compute a hash of the local file.

## Pitch

Hash sums are generally used to verify that files are identical. This helps to detect corrupted downloads. I believe it would be straightforward to compute and provide a hash sum on the download page.

## Alternatives

A (worse) alternative would be to provide the binary files via some version control system.


cc @ezyang @seemethere @malfet @walterddr
Repository: flutter
Issue: Let FlutterViewController in a UINavigationController be selectively back swipable
Labels: platform-ios,engine,a: existing-apps,customer: google,P2,team-ios,triaged-ios

When the FlutterViewController is added to a UINavigationController, the FlutterViewController itself will be entirely, natively back-swipable, overriding the back swipe gesture implemented inside Flutter when the Flutter navigator has multiple routes. 

This creates an incorrect behavior where in a stack like native 1 -> native 2 -> flutter 3 -> flutter 4 -> flutter 5, a back swipe from logical page 5 will go back to page 2 instead of page 4. We can entirely override `navigationController.interactivePopGestureRecognizer.delegate` to have `gestureRecognizerShouldBegin` return NO. But between pages 3 and 2, the native back swipe will no longer work. What a proper solution would be is to have Flutter report whether the navigator stack is empty, and have native selectively enable the native back swipe. This is the same problem as https://github.com/flutter/flutter/issues/67011 on Android.
Repository: pytorch
Issue: Add a NumPy-like `pad` function
Labels: triaged,module: numpy,function request,module: padding

## 🚀 Feature
Add a `torch.pad` function, based on [`numpy.pad`](https://numpy.org/doc/stable/reference/generated/numpy.pad.html)

## Motivation

NumPy compatability.

Plus, this will offer a solution to several issues with `torch.nn.functional.pad`:

* #52205 - reflection padding is only supported if padding width is less than the input's width
* #57911 - circular padding can only wrap once
* #46240 - we don't support symmetric reflection padding
* #28214 and #29863 - we only support a subset of input dimensionality

## Pitch

Most of the `numpy.pad` interface can probably be copied. However, we could potentially extend it to support anything extra that `torch.nn.functional.pad` offers that `numpy.pad` does not. We could also maybe make small improvements upon `numpy.pad`'s interface.

## Alternatives

There are a couple potentially confusing aspects of the `numpy.pad` interface that we could think about improving:
* The `constant_values` and `end_values` arguments can never be used at the same time (they are for different padding modes, 'constant' and 'linear_ramp'), and they logically specify the same exact thing: they indicate what the values at the edges of the padding are. If the padding mode is 'constant', the rest of the padding is filled up with the constant values, and if the padding mode is 'linear_ramp', the rest of the padding is filled with a linear ramp between the edge of padding and the edge of the input array. Since they basically mean the same thing, we could combine these into one argument.
* The term "end value" (for mode='linear_ramp') is potentially confusing. The word end, in my mind, implies one of two edges of something. For instance, there is one start and one end of a footrace. But in `numpy.pad`, "end" refers to both of the outermost edges of the padding for a given dimension. In the footrace example, both points where the race starts and stops would be "end"s, using this definition of the word. "edge value" could be better, but one of the padding modes is called "edge", so that could cause confusion, too. Perhaps "outer value" would be a good choice.

`numpy.pad` allows you to specify a function for the `mode` argument. I don't know of any PyTorch operations where a function can be given as an argument, so I'm guessing that we can't support this feature yet.

It could be useful to offer separate functions for each mode as well. Although maintaining all of them along with the combined `torch.pad` function could be a challenge.

## Additional context

I'm keeping notes about `numpy.pad` and `torch.nn.functional.pad` here, while I investigate the differences between the two: https://github.com/kurtamohler/notes/blob/main/numpy-pad-examples/numpy-pad-examples.ipynb


cc @mruberry @rgommers @heitorschueroff
Repository: pytorch
Issue: Optimize torch.einsum
Labels: module: performance,triaged,module: linear algebra

Currently, `torch.einsum` is computed by performing tensor contractions from left to right and calling `torch.bmm` for each contraction, unless there are no dimensions to be summed out in which case `torch.mul` is called instead. There are two main ways in which `torch.einsum` performance can be improved:

### 1. Optimize contraction path
Instead of performing contractions from left to right, we can compute an optimal (or near-optimal) contraction path. NumPy and TensorFlow do this by calling [opt_einsum](https://github.com/dgasmith/opt_einsum) library to get the path. The PR https://github.com/pytorch/pytorch/pull/60191 adds initial support for this by accepting a contraction path in the same format as given by `opt_einsum.contract_path(...)[0]`. However, we should consider either adding a dependency on `opt_einsum` or implementing our own algorithms for computing the optimal contraction path.

### 2. Optimize tensor contractions for non BLAS or discontiguous cases
Instead of always calling into `torch.bmm` for contracting two tensors which can cause expensive data movements for certain tensor contractions, we should do what NumPy does: if the contraction matches a BLAS operation and the dimensions are contiguous, call `torch.tensordot`, otherwise call a custom function to compute a sum_of_products over discontiguous dimensions. The issue https://github.com/pytorch/pytorch/issues/57121 illustrates a case where PyTorch is much slower than NumPy because the dimensions are discontiguous. A `sum_of_products` function could replace https://github.com/pytorch/pytorch/blob/d9e7df707bdc737a10b3af15f08143cc300ace39/aten/src/ATen/native/Linear.cpp#L47 which is also used by `torch.bilinear`'s forward and backward function.

cc @jianyuh @nikitaved @pearu @mruberry @heitorschueroff @walterddr @IvanYashchuk @xwang233 @Lezcano @VitalyFedyunin @ngimel

see also: https://github.com/pytorch/pytorch/issues/21760
Repository: flutter
Issue: Add `AppStartUp` UserTag to track timing of Flutter app start
Labels: tool,c: proposal,P2,team-tool,triaged-tool

Soon, DDS is going to support caching CPU profiles for a given user tag and provide an API for Flutter DevTools to request a cached profile. @bkonyi is working on this. We will use this functionality to support profiling app startup for Flutter apps. In order to use this functionality, we need a [UserTag](https://api.flutter.dev/flutter/dart-developer/UserTag-class.html) `AppStartUp` to be set at the beginning of app start, and unset at the end. This will mark the start and end times for app startup in the CPU profiler. 

I'm not sure where in the flutter ecosystem these UserTag changes will need to take place. If either of them need to happen in Native code in the engine, @bkonyi can make a small change to the C API to support this. @chinmaygarde @iskakaushik

Flutter Tools will then need to pass `AppStartUp`, or whatever the name of the user tag ends up being, as a flag value to DDS, so that DDS knows to cache profiles for that tag. @jonahwilliams
Repository: TypeScript
Issue: Destructuring exported array with `require` causes error
Labels: Bug,Help Wanted

# Bug Report

I'm progressively adding TypeScript to an existing JS codebase. In several of our files, there is an existing pattern of exporting arrays like so: `module.exports = [A, serializeA]`.
When requiring and destructuring this export like `const [A] = require('./a')`, I get an unexpected error `Module '"./a"' has no exported member 'A'. ts(2305)` which I believe to be a bug.

### 🔎 Search Terms

module has no exported member TS2305 

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `module.exports`

### ⏯ Playground Link

Not sure how to repro this in a Playground work Workbench since I believe it requires files and exports/requries.

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```js
// a.js
class A {}
module.exports = [A]

// b.js
const [A] = require('./a') // Module '"./a"' has no exported member 'A'. ts(2305)
```

### 🙁 Actual behavior

The compiler shows an error

### 🙂 Expected behavior

The compiler shows no error and the exported array is correctly destructured and the type infered.

###
Repository: flutter
Issue: [TimePicker] Ability to change action buttons order
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,P3,team-design,triaged-design

![image](https://user-images.githubusercontent.com/9344207/122619345-eaedee00-d098-11eb-90d7-46659d6fb520.png)
I want the positive and negative buttons swap their position. In many cases, the positive button in rtl is on the right side.

I also want to remove the clock icon on the right bottom, so only one TimePickerEntryMode will be used by the user.

This is the desired result:
![image](https://user-images.githubusercontent.com/9344207/122620039-98153600-d09a-11eb-9706-34370c71607c.png)
Repository: TypeScript
Issue: Call signature returning a wide union type not seen as compatible with implementation 
Labels: Suggestion,In Discussion

# Bug Report

### 🔎 Search Terms

overload "not compatible" 2394 union return type

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about overloads and unions

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.3.2#code/GYVwdgxgLglg9mABMOcAUAPAXIqAnEAUwEocAGRAH0QEYBuRAekcULzzjwEIAoZxALRCBAPkQA-SXxYAVABYwAzojgA3NgBs4AQwAmiRTADmYbVBB5CiJYjBwoiCHAC2ABzMwARhqsB3GFBy1lDKMG4+zoRgUB4IBsam5pYAdGgATADMAJwALMQ8oJCwcSjo2MjaGookOGl0BeDQ8EilmDieqD7aYMSIAN48iIiWSUgYiAD8iBS19QC+PIuFTXGe2nhtuAQ101S0DA1FzYhrG+XAldWkiHWHK0inmx1wXT3kezR7af2Dw4SjiHGUxmN3miyAA)

### 💻 Code

```ts
function foo(x: true): 0 | 1; // error!
// ----> ~~~
// This overload signature is not compatible with its implementation signature.(2394)
function foo(x: false): 2;
function foo(x: boolean) {
  return x ? 0 : 2;
}
```

### 🙁 Actual behavior

The compiler complains that the first call signature which returns `0 | 1` is not compatible with the implementation signature which returns `0 | 2`.  

### 🙂 Expected behavior

The compiler "should" allow the `0 | 1` call signature return type because of the significant overlap with `0 | 2`. 

----

So, this is probably not actually a bug, but I'm having a hard time locating any canonical documentation or issues that mention this particular behavior.   It makes sense for the compiler to warn that a call signature is claiming to return something the implementation can never return, but in this particular instance (adapted from [this SO question](https://stackoverflow.com/questions/68042630/function-overload-compilation-error-this-overload-signature-is-not-compatible)) it seems unfortunate/misplaced: while the implementation cannot return a value of type `1`, it *can* return a value of type `0 | 1`.  Obviously there are workarounds, the easiest of which would be an explicit implementation return type annotation of the full union `0 | 1 | 2`:

```ts
function foo(x: true): 0 | 1;  // no error now
function foo(x: false): 2;
function foo(x: boolean): 0 | 1 | 2 {
  return x ? 0 : 2;
}
```

So... is this working as intended?  If so, could someone explain the intent?  Thanks!
Repository: rust
Issue: Rustdoc fails on modules with reserved file names
Labels: O-windows,T-rustdoc,C-bug

**Problem**
Adding a module named `con`, `nul`, or any other reserved name on Windows causes Rustdoc to fail.

**Steps**
1. Add an empty module named `con`.
2. Run `cargo doc`.

**Possible Solution(s)**
A fix similar to #83612 should get rid of this issue.

**Notes**

I'm on Windows 10. I haven't tested this, but I'm almost certain this bug should exist in all other versions of Windows, and in no other operating system.
Repository: go
Issue: cmd/cover: treats empty lambdas as being executed even when not executed
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.5 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

This problem came to my attention because I was surprised the coverage reported by `go test -coverprofile=cover` was significantly higher than that reported by the Codecov service. After carefully looking at a couple of files in the project which should have had identical coverage I came to the conclusion there appears to be an off by one bug, or something akin to it, in the go coverage calculations.

Create a directory with the following two files, run `go mod example.com/coverage` then `go test -coverprofile=cover ./...`.

File *x.go*:

```go
package coverage

type covered struct {
        f func()
}

var c covered

func BadCoverage() {
        c.f = func() {}
}

func GoodCoverage1() {
        c.f = func() { c = covered{} }
}

func GoodCoverage2() {
        c.f = func() {}
        c.f()
}
```

File *x_test.go*:

```go
package coverage

import "testing"

func TestCoverage(t *testing.T) {
        BadCoverage()
        GoodCoverage1()
        GoodCoverage2()
}
```

### What did you expect to see?

Correct coverage of 66.7%.

### What did you see instead?

Incorrect coverage of 80% due to treating the lambda in the `BadCoverage` function as if it had been executed. Changing the body of the lambda to do anything at all "fixes" the coverage. Interestingly, the HTML produced by `go tool cover -html=cover` highlights the right-paren in red in the `BadCoverage` case. Which suggests a disconnect between the code highlighting and coverage calculation. Also, the incorrect value of 80% is also wrong, it seems to me, since it is treating the code as if 5/6 of the lines were executed which is 83.3%. It looks like it is treating the incorrect case as if 4/5 of the lines were executed. Which is another clue how the coverage data is being misinterpreted.

For the record, the *cover* data is (compare lines 3 and 5):

```
mode: set
example.com/t/x.go:9.20,10.15 1 1
example.com/t/x.go:10.16,10.17 0 0
example.com/t/x.go:13.22,14.15 1 1
example.com/t/x.go:14.15,14.32 1 0
example.com/t/x.go:17.22,18.15 1 1
example.com/t/x.go:19.2,19.7 1 1
example.com/t/x.go:18.16,18.17 0 1
```
Repository: flutter
Issue: LiveImage cache leaks an image if a frame is not scheduled after the last listener goes away.
Labels: c: regression,framework,a: images,perf: memory,P3,team-framework,triaged-framework

Introduced here: https://github.com/flutter/flutter/pull/69219/files#diff-208380935f5b42b6e5476d5f1ea45c6ee0fe51ff23e318b2e1f4bdf50637a3e7R927

I'm pretty sure we need to dispose the image there (or perhaps invert the condition and just conditionally call _emitFrame).

Need to make sure that it still works if someone starts listening again later.

/cc @ds84182
Repository: deno
Issue: prompt function got "\x00" when input is not ascii (windows terminal)
Labels: bug,windows,runtime

![image](https://user-images.githubusercontent.com/13158903/122637068-3e0a8400-d11f-11eb-98b9-16eac66f9855.png)
PS: it works for other command line application
Repository: vscode
Issue: [css] Color picker for css variables
Labels: help wanted,feature-request,css-less-scss

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Currently vs code color picker doesn't display color picker on hover for a color picker where css variable is used. E.g.

```css
color: hsl(0, 0%, 0%)
``` 
^Works

But,

```css
--hue-color: 250
color: hsl(var(--hue-color), 0%, 0%)
```
^Doesn't work.

Is there a way to make it work? If the feature is not implemented is there any challenge to do so. I am currently looking at the code how this can be implemented but if some can direct me where to start would be great.
Repository: youtube-dl
Issue: crazycash.tv support
Labels: site-support-request

Hi,

I am using the latest version of youtube-dl and I try to download from crazycash.tv.
I receive Unsupported URL.

- [X] I'm reporting a new site support request
- [X] I've verified that I'm running youtube-dl version **2021.06.06**
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've checked that none of provided URLs violate any copyrights
- [X] I've searched the bugtracker for similar site support requests including closed ones

Urls are similar to:
https://crazycash.tv/view-stream/XXXXXX
where XXXXXX is a number.

Do you plan to add this site in the future?
Thank you very much