sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: On Triton inference server, the TorchScript .pt file, exported by 1.9.0, serves unsuccessfully
Labels: oncall: jit

## 🐛 Bug

I trained the model and export it to torchscript file by scripting (Torch == 1.9.0)
Then I want to serve it on Triton server, but I found:

```
E0728 06:06:45.028234 1 model_repository_manager.cc:899] failed to load 'my-model' version 1: Internal: load failed for libtorch model -> 'my-model: 
Unknown type name 'NoneType':
Serialized   File "code/__torch__/torch/nn/modules/dropout.py", line 5
  __buffers__ = []
  training : bool
  _is_full_backward_hook : NoneType
                           ~~~~~~~~ <--- HERE
  p : Final[float] = 0.10000000000000001
  inplace : Final[bool] = False
```
## To Reproduce

I find this field `_is_full_backward_hook` is added recently and its default value is None, which may be not supported by Triton.

**When I change the pytorch version to 1.6.0, this problem is solved and it can serve successfully.**

Thank you so much.

 - PyTorch Version (e.g., 1.0): 1.9.0
 - OS (e.g., Linux): Mac Os
 - How you installed PyTorch (`conda`, `pip`, source): pip
 - Python version: 3.6
 - CUDA/cuDNN version: No
 - GPU models and configuration: No
 - Any other relevant information: Triton


cc @gmagogsfm
Repository: godot
Issue: Debugger calls getters to update variable inspector
Labels: discussion,topic:editor

### Godot version

3.3.2

### System information

Windows 10

### Issue description

The actual debugger itself calls getters when they are defined for a variable, so as to update the debugger variable inspector. It should not do this, for this clearly can alter the state of the program from what it would be without the debugger, and introduce new issues solely from the debugger that are not the real issues in the first place.

### Steps to reproduce

Open the project and the only Node2D scene in there, and run the scene. Note that 'times_called' starts at 0, and never anywhere at all is 'variable' referenced, so the getter should never be called. Put a breakpoint on line 14 and step down one or two lines, and look at times_called in the inspector. Then, remove the breakpoint and run the scene. I get something like 48 printing for 'times_called' after using debugger to step a couple of lines, vs 0 when I run without the breakpoint.

### Minimal reproduction project

[debugger bug.zip](https://github.com/godotengine/godot/files/6891190/debugger.bug.zip)
Repository: flutter
Issue: Add KML layer management
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

Package google_maps_flutter (now at v2.0.6) does not implement the visualization of a kml layer on the map.

I found this guide (https://brunozaranza.medium.com/google-maps-flutter-com-kml-e750c8c5b793) to a possible solution (but only for android) that uses:

- com.google.maps.android:android-maps-utils:2.0.1, as android dependencies in build.gradle file
- mapController.channel, in the flutter app, to invoke the custom method ("map#addKML")

I can fork google_maps_flutter project and reproduce the implementation suggested by the above guide. Than I will submit a pull request.
Repository: angular
Issue: FormGroup validator is not triggered after FormControl async validator completes
Labels: area: forms,forms: validators,P3

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I have a form with several fields and one of the field has async validator. There is aslo a form validator that is supposed to do cross field validation. The issue is that the form validator is not triggered when the field async validator finishes. In fact the form validator is triggered probably at the same time as the field validator.
This issue occurs in Angular 11 and 12

### Please provide a link to a minimal reproduction of the bug

https://angular-ivy-x6tfzc.stackblitz.io

### Please provide the exception or error you saw

```true
If you run the example then you can see in the console debug logging of the application.
When you type into email field you can see that form validator is triggered, then email async validator finishes but the form validator is not triggered
```


### Please provide the environment you discovered this bug in

```true
"@angular/animations": "^12.1.3",
"@angular/common": "^12.1.3",
"@angular/compiler": "^12.1.3",
"@angular/core": "^12.1.3",
"@angular/forms": "^12.1.3",
"@angular/platform-browser": "^12.1.3",
"@angular/platform-browser-dynamic": "^12.1.3",
"@angular/router": "^12.1.3",
"rxjs": "^7.2.0",
"tslib": "^2.3.0",
"zone.js": "^0.11.4"
```


### Anything else?

_No response_
Repository: material-ui
Issue: Breadcrumb bar is highlighting the first element and underlining the second element on iOS devices. (platform: Material-UI website) 
Labels: bug 🐛,component: breadcrumbs


Breadcrumb bar doing this behaviour on the mobile devices (iOS)

It is also happening in the latest version of the material-ui and also on the material-ui website. 

just visit https://material-ui.com/components/breadcrumbs/ with an iOS device and go to the Collapsed breadcrumbs.

You can produce this problem. 

an image is attached to depict the result.

![File (1)](https://user-images.githubusercontent.com/64686892/127310788-fee1c4c1-5150-4904-9dbe-971fb75840bb.jpg)

Expected behaviour should be that it should open all the elements without highlighting the first element and underlining the one of the elment randomly.
Repository: godot
Issue: Undo/Redo Keymap changes not working in script editor
Labels: bug,topic:editor

### Godot version

3.3.2.stable

### System information

Windows 10, GLES3

### Issue description

As i use a QWERTZ keyboard, i wanted to remap undo/redo to ctrl+y and ctrl+x. This worked fine for the scene editor, but does not work in the script editor. The editor settings save my keymap, but it gets simply ignored in the script editor, and still uses ctrl+Z

### Steps to reproduce

1. Remap "undo" to Ctrl+Y
2. Try to undo anything in the script editor

### Minimal reproduction project

_No response_
Repository: go
Issue: x/tools/internal/imports: Grouping when using -local flag groups into more groups than expected
Labels: NeedsInvestigation,Tools

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 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/will/Library/Caches/go-build"
GOENV="/Users/will/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/will/go/pkg/mod"
GONOPROXY="github.com/bugsnag"
GONOSUMDB="github.com/bugsnag"
GOOS="darwin"
GOPATH="/Users/will/go"
GOPRIVATE="github.com/bugsnag"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.16.6/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.16.6/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.16.6"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

</pre></details>

### What did you do?

Started with imports, grouped like this:

```
 import (
	"fmt"
	
	"github.com/pkg/errors"
        "go.mongodb.org/mongo-driver/bson"
	
	"github.com/mymodule/somepkg"
) 
```

Added a new module import, which my IDE added to the middle group, so it looked like this

```
import (
	"fmt"
	
	"github.com/pkg/errors"
        "go.mongodb.org/mongo-driver/bson"
	"github.com/mymodule/anotherpkg"
	
	"github.com/mymodule/somepkg"
)
```



Then ran `goimports -w -local github.com/mymodule main.go`

### What did you expect to see?
```
import (
	"fmt"
	
	"github.com/pkg/errors"
        "go.mongodb.org/mongo-driver/bson"
	
	"github.com/mymodule/anotherpkg"
	"github.com/mymodule/somepkg"
)
```


### What did you see instead?
```
import (
	"fmt"
	
	"github.com/pkg/errors"
        "go.mongodb.org/mongo-driver/bson"
	
	"github.com/mymodule/anotherpkg"
	
	"github.com/mymodule/somepkg"
)
```
Repository: rust
Issue: Specialized trait impls appear unannotated in the docs
Labels: T-rustdoc,C-bug,A-rustdoc-ui

Looking at the docs for `ToString` it shows that there's an [implementation for `char`](https://doc.rust-lang.org/nightly/std/string/trait.ToString.html#impl-ToString)

```rust
impl ToString for char
```

but, this overlaps the blanket impl + char's `Display` impl:

```rust
impl<T> ToString for T where T: Display + ?Sized
impl Display for char
```

Showing this specialization-based implementation in the docs with no indication of why the overlap is allowed is confusing.

Since specialization is supposed to be generally invisible to the user, maybe we shouldn't be showing specialized impls at all.
Repository: rust
Issue: enabling const-generics interferes with object safety
Labels: C-bug,A-const-generics,F-generic_const_exprs

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

*Summary*: Enabling the `const_generics` feature makes an object safe trait with const generics unsafe.

The following code compiles successfully as expected (note the angle brackets around 42):

```rust
trait TraitWithConstGeneric<const GENERIC: u64> {}
trait ObjectSafeTrait: TraitWithConstGeneric<{42}> {}

// Check that `ObjectSafeTrait` is in fact object safe
type __ = dyn ObjectSafeTrait;
```

However, when I enable the `const_generics` feature, compilation fails (note the angle brackets around 42):

```rust
#![feature(const_generics)]

trait TraitWithConstGeneric<const GENERIC: u64> {}
trait ObjectSafeTrait: TraitWithConstGeneric<{42}> {}

// Check that `ObjectSafeTrait` is in fact object safe
type __ = dyn ObjectSafeTrait;
```

with the error that "`ObjectSafeTrait` cannot be made into an object".

<details><summary>Full Error Message</summary>
<p>

```
error[E0038]: the trait `ObjectSafeTrait` cannot be made into an object
 --> src/lib.rs:7:11
  |
7 | type __ = dyn ObjectSafeTrait;
  |           ^^^^^^^^^^^^^^^^^^^ `ObjectSafeTrait` cannot be made into an object
  |
note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>
 --> src/lib.rs:4:24
  |
4 | trait ObjectSafeTrait: TraitWithConstGeneric<{42}> {}
  |       ---------------  ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...because it uses `Self` as a type parameter
  |       |
  |       this trait cannot be made into an object...

For more information about this error, try `rustc --explain E0038`.
```

</p>
</details>

You can also reproduce the behaviour on the playground:
https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=e083b7b2d1cb62e355201987e6076775
The same error can also be reproduced on stable 1.53.0, though rustc then also complains about the feature, of course.

It is also worth noting that when the angle brackets around 42 are removed, i.e. `TraitWithConstGeneric<42>`, the code compiles both with and without the `const_generics` feature.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.56.0-nightly (2faabf579 2021-07-27)
binary: rustc
commit-hash: 2faabf579323f5252329264cc53ba9ff803429a3
commit-date: 2021-07-27
host: x86_64-unknown-linux-gnu
release: 1.56.0-nightly
LLVM version: 12.0.1
```
Repository: pytorch
Issue: broken pipe error 
Labels: needs reproduction,module: crash,module: cuda,triaged

## 🐛 Bug

when I run the 2 gpu at the same time in docker environment(nvidia-docker)
it gives the broken pipe error 
what is the problem? and how to solve it?

## Environment 
pytorch : 1.7.0+cu110
cuda : 11.2
gpu 1,2 : titan 3090

cc @ngimel
Repository: youtube-dl
Issue: downloaded videos from facebook groups
Labels: request

<!--

######################################################################
  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:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

When I try to download a video from a facebook group I get an "_Unsupported URL_" error. Example:

```
$ youtube-dl https://www.facebook.com/groups/AustinDrones/posts/4493415057345664/
[generic] 4493415057345664: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 4493415057345664: Downloading webpage
[generic] 4493415057345664: Extracting information
ERROR: Unsupported URL: https://www.facebook.com/groups/AustinDrones/posts/4493415057345664/
```
Superficially, #26975 seems like a similar issue but the error is distinctly different. #12055 look similar, as well, but again, different error and that ticket i super old anyway
Repository: pytorch
Issue: How to Fix “AssertionError: CUDA unavailable, invalid device 0 requested”
Labels: module: binaries,triaged

## 🐛 Bug

I'm trying to use my GPU to run the YOLOR model, and I keep getting the error that CUDA is unavailable, not sure how to fix.

I keep getting the error:
```
Traceback (most recent call last):
  File "D:\yolor\detect.py", line 198, in <module>
    detect()
  File "D:\yolor\detect.py", line 41, in detect
    device = select_device(opt.device)
  File "D:\yolor\utils\torch_utils.py", line 47, in select_device
    assert torch.cuda.is_available(), 'CUDA unavailable, invalid device %s requested' % device  # check availablity
AssertionError: CUDA unavailable, invalid device 0 requested
```

When I check CUDA availability with:
```
py
>>import torch
>>print(torch.cuda.is_available())
```

I get `False`, which explains the problem. I tried running the command:

`py -m pip install torch1.9.0+cu111 torchvision0.10.0+cu111 torchaudio==0.9.0 -f https://download.pytorch.org/whl/torch_stable.html`

I get the error:` ERROR: Invalid requirement: 'torch1.9.0+cu111'`

Running `nvcc --version`, I get:
```
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Mon_May__3_19:41:42_Pacific_Daylight_Time_2021
Cuda compilation tools, release 11.3, V11.3.109
Build cuda_11.3.r11.3/compiler.29920130_0
```

Thus, I'm not really sure what the issue is, or how to fix it.

## Expected behavior

I expect the program to be able to run, and CUDA to be available.

## Environment

 - **PyTorch Version (e.g., 1.0):** 1.9.0
 - **OS (e.g., Linux):** Windows
 - **How you installed PyTorch (`conda`, `pip`, source):** pip
 - **Python version:**  Python 3.9.4
 - **CUDA/cuDNN version:** Cuda compilation tools, release 11.3, V11.3.109
 - **GPU models and configuration:** 2070 Super


EDIT:
I noticed that I forgot the `==` sign. I ran `py -m pip install --user torch==1.9.0+cu111 torchvision==0.10.0+cu111 torchaudio===0.9.0 -f https://download.pytorch.org/whl/torch_stable.html`, and even after doing so, 
```
py
>>import torch
>>print(torch.cuda.is_available())
```
still gets `False`.

Additionally, `torch.version.cuda` gives `None`. Please help!

cc @ngimel @ezyang @seemethere @malfet @walterddr
Repository: TypeScript
Issue: Diagnostic messages typo in RU locale
Labels: Bug,i18n

There is an error in words `…предложения clutch указана…`. Should be `…предложения catch указана…`
https://github.com/microsoft/TypeScript/blob/main/lib/ru/diagnosticMessages.generated.json#L358
Repository: rust
Issue: Tracking Issue for RFC2509: concat_bytes!()
Labels: T-libs-api,C-tracking-issue

<!--
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(concat_bytes)]`

This is a tracking issue for https://github.com/rust-lang/rfcs/pull/2509

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
#[macro_export]
macro_rules! concat_bytes { .. }
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] RFC: https://github.com/rust-lang/rfcs/pull/2509
- [x] Implementation: #87599
- [ ] Final comment period (FCP)
- [ ] 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 comment period
(FCP) is always needed before stabilization. This works as follows:

A library API 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
comment 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.
-->

- Should additional literal types be supported? Byte string literals are basically the same thing as byte slice references, so it might make sense to support those as well (support `&[0, 1, 2]` in addition to `[0, 1, 2]`).
- What to do with string and character literals? They could either be supported with their underlying UTF-8 representation being concatenated, or rejected.
Repository: go
Issue: net/http: request returns non-idiomatic error messages that may leak sensitive info
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.6 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
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOVERSION="go1.16.6"
</pre></details>

### What did you do?

Got a context deadline timeout from an HTTP PATCH request.

### What did you expect to see?

An idiomatic error return.

### What did you see instead?

```
Error processing request: Patch "http://www.example.com/sensitiveurl": context deadline exceeded
```

i.e. returned error has "patch" capitalized.

Error also includes the entire URL, even for a POST/PUT/PATCH which may involve a sensitive URL.

### Comments

The HTTP verb formatting is from `net/http/client.go` in `urlErrorOp`. I'd suggest that it should either make the verb all caps (like in the actual protocol and the `http.MethodFoo` constants), or leave it lower case.

I'd argue that it's the responsibility of the code calling `request.Do` to log the entire URL if appropriate. Having to perform a text search-and-replace on error strings to sanitize them before reporting them is undesirable.

### Sample code

```go
package main

import (
	"context"
	"log"
	"net/http"
)

func main() {
	ctx, cancel := context.WithTimeout(context.Background(), 1)
	defer cancel()
	req, err := http.NewRequestWithContext(ctx, "PATCH", "http://www.example.com/sensitiveurl", nil)
	if err != nil {
		panic(err)
	}
	resp, err := http.DefaultClient.Do(req)
	if err != nil {
		log.Printf("Error processing request: %v", err)
	}
	defer resp.Body.Close()
}
```
Repository: TypeScript
Issue: Bug: Intellisense shows misleading error when parameter is expected to be a union of an object and a string
Labels: Suggestion,Help Wanted,Effort: Moderate,Domain: Error Messages,Experience Enhancement,Rescheduled

# Bug Report

### 🔎 Search Terms

Intellisense, incorrect function parameter

### 🕗 Version & Regression Information

Tried with v4.3.5

### ⏯ Playground Link

[Playground](https://www.typescriptlang.org/play?#code/CYUwxgNghgTiAEYD2A7AzgF3mkLgC4AoeeAChADdcN94BveDATwAcRaAiAQQ4Bp4AZkiS1MMAJYoA5vAC+8AD71GrdvA4AhDnMXqtASngBeAHzwKSccEKFQkWAmTosOPAHkUEJm4BGAK3AaYjJKaloGZjZOHn4hEWwMCWkdJQjVTi05Q1NzS2sbV2BSNKj1HizCQo8vXwCwDGKVUu5tWX0gA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
declare const send:
  (event: { type: "A", foo: string } | { type: "B" } | "B") => void

declare const sendOnlyObject:
  (event: { type: "A", foo: string } | { type: "B" }) => void


send({ type: "A" })
// Type '"A"' is not assignable to type '"B"'.(2322)

sendOnlyObject({ type: "A" })
// Argument of type '{ type: "A"; }' is not assignable to parameter of type '{ type: "A"; foo: string; } | { type: "B"; }'.
//   Property 'foo' is missing in type '{ type: "A"; }' but required in type '{ type: "A"; foo: string; }'.(2345)
```

### 🙁 Actual behavior

The error for `send({ type: "A" })` is `Type '"A"' is not assignable to type '"B"'`

### 🙂 Expected behavior

The error should be something like the one for `sendOnlyObject` or at least not misleading that the property `type` has to be `"B"` that's what is getting suggested here.