sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/net/ipv4: missing a way to parse Linux packets on Darwin 
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

I captured TCP/IPv4 packets on Linux, saved them to files to be used in unit tests. Then I tried running unit tests on macOS and they failed. This was because of a hard-coded OS detection in ipv4.Header.Parse.

### What did you expect to see?

I would expect to have a way to specify packet OS when I want to parse the packet. This feature would make the code of the library cleaner and less platform dependent. Currently, even tests are not clean (by having switch/case)  and depend on the OS they are being run on.

### What did you see instead?

I'm not able to use ipv4.ParseHeader with pre-saved files on a different platform.
Repository: go
Issue: x/crypto/ssh: ParseRawPrivateKeyWithPassphrase doesn't support PKCS#8 encrypted keys
Labels: help wanted,NeedsInvestigation


### What version of Go are you using (`go version`)?

<pre>
go version go1.15.4 darwin/amd64

</pre>

### Does this issue reproduce with the latest release? Yes


### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOOS="darwin"

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/rob/Library/Caches/go-build"
GOENV="/Users/rob/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/rob/development/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/rob/development/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.15.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"

</pre></details>

### What did you do?
When decrypting a private key PEM block, using ssh package, there are two methods:  
ParseRawPrivateKeyWithPassphrase. 
ParseRawPrivateKey. 
  
ParseRawPrivateKey accepts PEM blocks with type "PRIVATE KEY" (with no other qualifier) and decrypts using x509.ParsePKCS8PrivateKey however ParseRawPrivateKeyWithPassphrase does not.  Both accept blocks with 
"RSA PRIVATE KEY", "EC PRIVATE KEY", "DSA PRIVATE KEY" and "OPENSSH PRIVATE KEY" but ParseRawPrivateKeyWithPassphrase seems to be missing the 'case' for "PRIVATE KEY" on its own.  
As methods perform the same task, just with the addition of decrypting, should they not be aligned in the keys they support?

https://play.golang.org/p/D_CtEEAqO7i


### What did you expect to see?
ParseRawPrivateKeyWithPassphrase parses pem block of type "Private Key" using x509.ParsePKCS8PrivateKey 


### What did you see instead?
Error: ssh: unsupported key type "PRIVATE KEY"


Looking at ssh/keys.go line: 1172 a switch block for the types appears to be missing the "PRIVATE KEY" case, reflected in the ParseRawPrivateKey switch block.  

Suggested fix is a simple insertion of:
`	case "PRIVATE KEY":
		return x509.ParsePKCS8PrivateKey(buf)
`
Repository: node
Issue: net.Socket enable emitClose
Labels: net,stream

`net.Socket` explicitly disables `emitClose`. Would be nice if it behaved like a regular stream.
Repository: go
Issue: text/template/parse: Pos is wrong in FieldNodes like .A.B.C
Labels: NeedsInvestigation


<pre>
$ go version
go version go1.15.6 darwin/amd64

</pre>

The template string
```
{{if .A.B.C.D}}{{printf .Z.Y.X.W}}
{{.Moo.N.P}}{{end}}
```
parses as
```

ListNode at 0:0, 2 children
. IfNode at 0:5
. . BranchNode at 0:5
. . Pipe. PipeNode at 0:5, 0 vars, 1 cmds
. . Pipe. . CommandNode at 0:5, 1 children
. . Pipe. . . FieldNode at 0:7, [A B C D]
. . List. ListNode at 0:15, 3 children
. . List. . ActionNode at 0:17
. . List. . . PipeNode at 0:17, 0 vars, 1 cmds
. . List. . . . CommandNode at 0:17, 2 children
. . List. . . . . IdentifierNode at 0:17
. . List. . . . . FieldNode at 0:26, [Z Y X W]
. . List. . TextNode at 1:1, len 1
. . List. . ActionNode at 1:2
. . List. . . PipeNode at 1:2, 0 vars, 1 cmds
. . List. . . . CommandNode at 1:2, 1 children
. . List. . . . . FieldNode at 1:6, [Moo N P]
. TextNode at 3:1, len 1
```
The offsets in the FieldNodes are after the first identifier. That is, in `{{.Moo.N.P}}` on line 1, the offset is 6, not 2. (And the same for the other FieldNodes.) If there is only one identifier in the FieldNode, then the offset is correct.
Repository: rust
Issue: Suboptimal diagnostic if const eval error site is in a different crate
Labels: A-diagnostics,T-compiler,A-const-eval

We currently produce fun diagnostics like

```
error: any use of this value will cause an error
  --> $SRC_DIR/core/src/intrinsics.rs:LL:COL
   |
LL |     unsafe { copy_nonoverlapping(src, dst, count) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |              |
   |              memory access failed: pointer must be in-bounds at offset 8, but is outside bounds of alloc6 which has size 4
   |              inside `copy_nonoverlapping::<u32>` at $SRC_DIR/core/src/intrinsics.rs:LL:COL
   |              inside `std::ptr::read::<u32>` at $SRC_DIR/core/src/ptr/mod.rs:LL:COL
   |              inside `ptr::mut_ptr::<impl *mut u32>::read` at $SRC_DIR/core/src/ptr/mut_ptr.rs:LL:COL
   |              inside `_MUT_READ` at $DIR/out_of_bounds_read.rs:15:37
   | 
  ::: $DIR/out_of_bounds_read.rs:15:5
   |
LL |     const _MUT_READ: u32 = unsafe { (PAST_END_PTR as *mut u32).read() };
   |     --------------------------------------------------------------------
```

Which I have multiple problems with (all of which are my fault :stuck_out_tongue:)

1. the main message only makes sense when you realize this is a lint
2. the diagnostic points to another crate's internals as the main span
3. the local crate's span is pointing at the entire item, instead of the useful span that we have (last element in the stack trace)

I think we should adjust the diagnostic to report on the site in the currently compiling crate while still mentioning the backtrace in full, so something like 

```
error: memory access failed: pointer must be in-bounds at offset 8, but is outside bounds of alloc6 which has size 
  --> $SRC_DIR/core/src/intrinsics.rs:LL:COL
   |
LL |     const _MUT_READ: u32 = unsafe { (PAST_END_PTR as *mut u32).read() };
   |                                                               ^^^^^^^ in function call here
   |     
LL |     unsafe { copy_nonoverlapping(src, dst, count) }
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ failure in external crate here
   |              inside `copy_nonoverlapping::<u32>` at $SRC_DIR/core/src/intrinsics.rs:LL:COL
   |              inside `std::ptr::read::<u32>` at $SRC_DIR/core/src/ptr/mod.rs:LL:COL
   |              inside `ptr::mut_ptr::<impl *mut u32>::read` at $SRC_DIR/core/src/ptr/mut_ptr.rs:LL:COL
   |              inside `_MUT_READ` at $DIR/out_of_bounds_read.rs:15:37
```

cc @rust-lang/wg-diagnostics @rust-lang/wg-const-eval
Repository: godot
Issue: Segfault in non-debug exports when using queue_free() on a referenced node
Labels: bug,topic:core,crash

**Godot version:**
3.2.3 official

**OS/device including version:**
Ubuntu Linux 20.04, but have tested this also applies to Windows exports

**Issue description:**

Apologies if I've missed something really obvious in the docs about this, but there appears to be an inconsistency in the way freed nodes are handled in GDScript.

The following works without a hitch in a debug build:

```gdscript
var i := 0
onready var child_node := $Child as Node2D

func _physics_process(_delta):
	if child_node:
		child_node.visible = true
	i += 1
	if i == 2:
		child_node.queue_free()
```

But on a release (or non-debug) build, it segfaults.

`is_instance_valid` seems to be how to deal with this properly, but I just find the above confusing, and it's lead me to have to do a huge refactoring operation just before a release.

**Steps to reproduce:**

Attach the above script to a scene with a child Node2D called `Child`

**Minimal reproduction project:**
[queue-free-segfault.zip](https://github.com/godotengine/godot/files/5743471/queue-free-segfault.zip)
Repository: TypeScript
Issue: Mixing Iterable destruction with plain args when calling function
Labels: Bug

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 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 verions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This changed between versions 3.3.3333 and 3.5.1

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/FAehAIDsHtwUwE4OggzgGnAd2ZA5sJHFuAMpwAuAFAHR1EnkUA8qFCAlvgHxUDaAXQCUmAOQBmACyihhYmUq168pq3Zc8vPqICMAJlHCxUmcFAREyBJmgBrOY0W6Dx6bKA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts

// no errors, wrong
new Set(...new Set<string>([]), '34')
new Set(...new Set<string>(['12']), '34')

// error, ok
new Set('12', '34')
```

### 🙁 Actual behavior

Code accepted as valid

### 🙂 Expected behavior

Error thrown
Repository: rust
Issue: Don't require -Cpanic=abort when doing profile guided optimization on windows-msvc
Labels: A-LLVM,T-compiler,O-windows-msvc,C-bug

Currently, when doing profile guided optimization on *-pc-windows-msvc targets, you need to use -Cpanic=abort, but the LLVM bug that caused this (https://bugs.llvm.org/show_bug.cgi?id=41279) is fixed, so this isn't necessary any more and should be removed.
Repository: pytorch
Issue: Tensorboard Error
Labels: needs reproduction,triaged

INTERNAL ASSERT FAILED at ..\torch\csrc\jit\ir\alias_analysis.cpp:318, please report a bug to PyTorch. We don't have an op for aten::randint but it isn't a special case.  Argument types: int, int[], None, int, int, Device, bool,
Error occurs, No graph saved
Repository: godot
Issue: Geometry::is_point_in_triangle returns false on triangle borders
Labels: enhancement,discussion,topic:core

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
Tested in 3.2.3, however it can safely be assumed that issue exists in both 3.2 and master given that the implementations, while in different files (geometry.h in 3.2 and geometry_2d.h in master), are functionally identical.

**Issue description:**
`Geometry::is_point_in_triangle` is a function exposed through `Geometry.point_is_in_triangle`. It's a basic triangle intersection test, however the test fails when the tested point lies on the edge or corners of the triangle. While it could be argued that "in" and "on" are distinct cases, the function is used internally in a few places (including pathfinding, which is how I discovered the issue in the first place), and in those cases the author seems to assume that the test _does_ include points on the triangle's boundaries. In addition, `Geometry::is_point_in_circle` is a much simpler function which _does_ return true for points on the extents, so presumably it's intended to be a straight intersection test.

**Steps to reproduce:**
The following GDScript demonstrates the problem and should run when attached to a node. All test fail except the last one:
```
extends Node

func _ready():
    # Points
    var a = Vector2(1.0, 0.0)
    var b = Vector2(0.0, 1.0)
    var c = Vector2(0.0, 0.0)
    
    # Corners
    print(Geometry.point_is_inside_triangle(a, a, b, c))
    print(Geometry.point_is_inside_triangle(b, a, b, c))
    print(Geometry.point_is_inside_triangle(c, a, b, c))
    
    # Edges
    print(Geometry.point_is_inside_triangle((a + b) / 2.0, a, b, c))
    print(Geometry.point_is_inside_triangle((b + c) / 2.0, a, b, c))
    print(Geometry.point_is_inside_triangle((c + a) / 2.0, a, b, c))
    
    # Center
    print(Geometry.point_is_inside_triangle((a + b + c) / 3.0, a, b, c))
```

**Further Investigation:**
I believe the initial implementation came from the comments of #16495 [(here specifically)](https://github.com/godotengine/godot/pull/16495#issuecomment-364148848) and advises replacing occurrences of `>` within the implementation with `>=` in order to include the boundaries in the test. My own attempts at implementing the function seemed to confirm this, but my testing process was not rigorous.
Repository: pytorch
Issue: Accessibility of Website for Low Vision Users
Labels: feature,triaged,module: doc infra

## 🚀 Feature
Accessibility

I would love for the website to think about our low vision users, as well as users that use screen readers to help them navigate a website and have an improved user experience.

## Motivation

The website has a lot of issues when it comes to color contrast, screen reader accessibility, font sizes, link names and attributes, etc.

## Pitch

What I would want to happen is for us to be more conscious of our community of users, and their accessibility needs for a website.

## Alternatives

The alternative is to do nothing to support our users that need a bit more help navigating websites.

## Additional context

I'm coming from the perspective of user experience, 508 compliance and web accessibility as described on the following websites: https://www.w3.org/WAI/ , and https://accessibility.digital.gov/ux/getting-started/ .


cc @ezyang @zou3519 @jlin27
Repository: pytorch
Issue: Accessibility Coding Needed
Labels: feature,triaged,module: doc infra

## Accessibility

The website has a lot of issues when it comes to color contrast, screen reader accessibility, font sizes, link names and attributes, etc.

## To Reproduce

Steps to reproduce the behavior:

1. Viewing the website as a low vision user.
2. Using a screen reader to read the website.


`<a href="#" class="">
          
            Docs
          
        </a>`

## Expected behavior

This is not the full code, but the color of this navigation item has a low contrast as seen by the screenshot below:
<img width="482" alt="Screen Shot 2020-12-27 at 1 57 50 AM" src="https://user-images.githubusercontent.com/618307/103165557-6dcb7580-47e7-11eb-8bdb-11d995d63948.png">


## Environment

This is what is seen on the page: small text (Docs) with low contrast. 
<img width="223" alt="Screen Shot 2020-12-27 at 2 02 07 AM" src="https://user-images.githubusercontent.com/618307/103165573-b125e400-47e7-11eb-8e31-b523268dfad6.png">


You can get the script and run it with:
ANDI or WEBAIM


This is the first of many accessibility issues I will be reporting and I wanted to open the discussion to see if it's possible to create a separate section from "Bugs" specifically to tackle web accessibility on PyTorch.

cc @ezyang @zou3519 @jlin27
Repository: TypeScript
Issue: The type of bitwise operations on 'any' operands should be 'number | bigint'
Labels: Suggestion,Awaiting More Feedback,Has Repro

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

* bigint
* bitwise

### 🕗 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 verions 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 bigint.

### ⏯ Playground Link

[Workbench Repro](https://www.typescriptlang.org/dev/bug-workbench/?target=7#code/PTACBcEMCcHMFNwC4AEBRAygJgAy4FD4DGA9gHYDO4KAbgIwoC8KdZKkF7ZAngNzHkqtLExRY2HFGXg140fqUrUaAZlH0UAH2G8UIWmooALEgFcANgBMUAI3gpw3AA7xrACjKmAtnehbbAJawAWTgAJQANLam1AGcnj5yQA)

### 💻 Code

```ts
//@target: ES2020
const v1 = 1n as any;
const v2 = 2n as never;
const v3 = v1 | v2; // v3 should be typed (number | bigint), but is number
```

### 🙁 Actual behavior

The result of the bitwise operations `&`, `|`, `^` and `~` is assumed to be a `number` when all the operands have unspecified type, like `any` or `never`.

### 🙂 Expected behavior

The result of bitwise operations with unspecified type operands should be `number | bigint`.
Repository: godot
Issue: Moving scenes in the FileSystem dock that are nested inside other scenes breaks the other scenes
Labels: bug,topic:editor

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
3.2.3.stable.mono.official

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Win10

**Issue description:**
<!-- What happened, and what was expected. -->
See this video:
https://user-images.githubusercontent.com/8841352/103167731-f66d0480-482d-11eb-9e75-3b6caaf1a324.mp4

When moving scene files that have instances in another scene ('Maps' here), that scene and every other one that uses this scene in turn cannot be opened anymore.
It looks like the references are just not updated correctly after moving.

**Steps to reproduce:**
In my case, it's 3 scenes that are instanced in another scene. Just moving those 3 around in the FileSystem Dock is enough to break it.
Repository: flutter
Issue: Jump to today on date picker
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,P3,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
I'm running `showDatePicker`.

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
It would be awesome to have a "Jump to Today" or similar button. So if I go to other month pages, I could get back in a single click.

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: create-react-app
Issue: react-scripts start is serving old data
Labels: needs triage,issue: bug report

### Describe the bug

When using `react scripts start` to serve Dev data, the served JSX is old/cached when it breaks.
For example, when I accidentally added `;` by accident to the end of some code, it broke, and it gave me the popup to say so. But when I then fixed it, that broken code is still being shown to me in the error, even after I both reload the page and even do a forced reload. I have saved the file multiple times and even opened the file itself in a separate program to make sure that it is indeed "fixed", and it is. But webpack seems to think that nope, it is broken still.

### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

Old code, serving old code, build not updating

### Environment

System:
    OS: Windows 10 10.0.20279
    CPU: (12) x64 AMD Ryzen 5 1600 Six-Core Processor
  Binaries:
    Node: 12.14.1 - E:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.10 - E:\OneDrive\GitHub\talespire\site\node_modules\.bin\npm.CMD
  Browsers:
    Chrome: 87.0.4280.88
    Edge: Spartan (44.20279.1.0)
    Internet Explorer: 11.0.20279.1
  npmPackages:
    react: ^16.14.0 => 16.14.0
    react-dom: ^16.14.0 => 16.14.0
    react-scripts: ^4.0.1 => 4.0.1
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

1. Create a CRA App
2. start the server to serve it to the client to work on
3. add a error
4. fix the error
5. see no change

### Expected behavior

The code to change in the browser & console when I changed the file itself

### Actual behavior

It didn't change.
Both console and the website give me this error 
![image](https://user-images.githubusercontent.com/24227350/103168941-819aca00-482f-11eb-81ef-c829e7e236d7.png) , but the code it references is this https://starb.in/BjDNGR.js
This is even the case after, reloading the page, clearing cache, restarting the server, uninstalling it (4.0.1) and reinstalling ^3.4 and back again. Even removing that whole function, saving, and adding it back in doesn't fix.
Breaking it will show the new error, but when that is fixed, it will show the old one and old code again.
I got it to work once an hour ago and no idea how I did that.
Repository: excalidraw
Issue: Paste for chart not working in mobile Safari
Labels: bug,safari,mobile,charts

The “Paste” option is not visible in the context menu. Cc @lipis
Repository: pytorch
Issue: The same tensor requires more memory on RTX3090
Labels: high priority,module: cuda,module: memory usage,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

## To Reproduce

Steps to reproduce the behavior:

1. I run the following code, and observe memory usage by `nvidia-smi`
```
import torch

a = torch.randn(64,16,200,200)
a = a.to('cuda:0')
```
2. On GTX2090Ti, this tensor use 1035MiB, while on RTX3090 it requires 1644MiB.
3. Is there something worng with that?

## Environment

### RTX3090
 - PyTorch Version (e.g., 1.0): 1.7.1+cu110
 - OS (e.g., Linux): Ubuntu20.04
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Python version: 3.8.5
 - CUDA/cuDNN version: 11.1
 - GPU models and configuration: RTX3090
 
### GTX2080Ti
 - PyTorch Version (e.g., 1.0): 1.6.0+cu101
 - OS (e.g., Linux): Ubuntu18.04
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Python version: 3.8.5
 - CUDA/cuDNN version: 10.1
 - GPU models and configuration: GTX2080Ti


cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @ngimel