sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: net, net/http: Deadline and Timeout Fail to Close Hung Connections. 
Labels: NeedsInvestigation

<!--
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 1.16 
AND 
go 1.17
</pre>

### Does this issue reproduce with the latest release?
Yes, this has been tested on 1.17


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/justin/.cache/go-build"
GOENV="/home/justin/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/justin/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/justin/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/justin/deadlinetest/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-build833553530=/tmp/go-build -gno-record-gcc-switches"

</pre>
</details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

#### Context:
I am part of a research project called "Project-Lernaean". We are working on mapping and surveying the internet for both developers and security researchers. We have been using [Colly](https://github.com/gocolly/colly) quite successfully in our scans but recently have run into a [fairly obscure issue](https://github.com/gocolly/colly/issues/644). In a variety of cases, we run into IPs that deadlock something during a page request.  

#### Test Cases:
Two test repositories have been created to show the bug in action. One uses Colly and the other is pure `net/http` and `net`. 
https://github.com/dherbst/deadlinetest (Thanks to the work of https://github.com/dherbst)
https://github.com/Project-Lernaean/CollyTimeoutError

In both cases, `Deadline` and `Timeout` setting within `http.Transport` fail to terminate these connections and hang indefinitely. 

#### Transport Settings:
```
transport := &http.Transport{
	IdleConnTimeout:       5 * time.Second,
	MaxIdleConns:          100,
	ExpectContinueTimeout: 10 * time.Second,
	DialContext: (&net.Dialer{
		Timeout:  1 * time.Second,
		Deadline: time.Now().Add(20 * time.Second),
	}).DialContext,
}
```

### What did you expect to see?

I would expect that `Deadline` would be the absolute max time a connection can take before it is forcefully terminated. 

### What did you see instead?

The connection never fails and remains "open" indefinitely.
Repository: kubernetes
Issue: CVE-2020-8561: Webhook redirect in kube-apiserver
Labels: kind/bug,area/security,sig/api-machinery,lifecycle/frozen,triage/accepted

A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.

This issue has been rated **Medium** (https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N) (4.1), and assigned **CVE-2020-8561**

### Am I vulnerable?

You may be vulnerable if `--profiling` is enabled on the kube-apiserver and actors who control a validating or mutating webhook can access the kube-apiserver process logs.

#### Affected Versions

This issue affects all known versions of kube-apiserver. 

### How do I mitigate this vulnerability?

This issue can be mitigated by not allowing kube-apiserver access to sensitive resources or networks, or to reduce the “-v” flag value to less than 10 and set the “--profiling” flag value to “false” (default value is “true”). Setting the profiling flag to “false” prevents users from dynamically modifying the kube-apiserver log level, and the flag value Webhook requests may still be redirected to private networks with a log level less than 10, but the response body will not be logged.

### Fixed Versions
There is no fix for this issue at this time.

### Detection

Examining kube-apiserver log responses is the only known method of detection for this issue.

If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io

#### Acknowledgements

This vulnerability was reported by QiQi Xu


/triage accepted
/lifecycle frozen
/area security
/kind bug
/committee security-response
Repository: vscode
Issue: Editor hint in new file can't be reached by tabbing
Labels: bug,accessibility,good first issue,workbench-untitled-editors

Version: 1.60.0-insider
Commit: e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff
Date: 2021-09-01T10:39:32.559Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 18.7.0

Steps to Reproduce:

Open VS Code and create a new untitled file. Tab over to try to click on the "Select a language" action and the hint disappears. Can we make this action keyboard focus-able?

cc @isidorn
Repository: PowerToys
Issue: Move to top of screen maximize.
Labels: Idea-Enhancement,Product-FancyZones

### Description of the new feature / enhancement

I'd like the option of having Fancy Zones handle the Windows Snap feature "drag to top to maximize".

I think a checkbox in the Fancy Zones settings would be sufficient. Holding shift (or not depending on the configuration) should probably disable the behavior in the same way it disables snapping regularly.

### Scenario when this would be used?

Right now I disable the "DockMoving" and "SnapSizing" features of Windows Snap, but I leave the feature that allows me to drag already maximized windows on. This is fine for the most part, since Fancy Zones does all my non-maximized window arranging and Windows key movement (I also use AutoHotkey to map Win+PgUp to maximize and Win+PgDn to minimize), but since I can't just turn of DockMoving on a per side basis I've lost the ability to drag a window and maximize it by dropping it at the top of the screen.

This would be a great addition for those of us who want to completely shift from Windows Snap to Fancy Zones.

### Supporting information

Registry path for WindowsSnap configurations:

__Computer\HKEY_CURRENT_USER\Control Panel\Desktop\DockMoving__ - Snaps windows to some section or maximizes them when dragged to the edge of the screen.

__Computer\HKEY_CURRENT_USER\Control Panel\Desktop\SnapSizing__ - Snaps windows to fill screen height when top border is resized to the top of the screen.

__Computer\HKEY_CURRENT_USER\Control Panel\Desktop\DragFromMaximize__ - Allows maximized windows to be restored and moved by dragging their title bars.
Repository: pytorch
Issue: Create a boxed/templated ADInplaceOrView kernel
Labels: module: autograd,triaged

As documented in https://github.com/pytorch/pytorch/issues/62032, an autograd "not implemented" kernel would provide a function/macro to register an autograd kernel that forwards but raises an error on backward. 

However, as of now, users will still need to manually write their own ADInplaceOrView kernel to make their custom view op have an official view relationship and custom in-place ops that actually increase the version counter. This feature will provide a way to automate that for users as well.

As a bonus, we can potentially reduce compilation time, binary size, and the amount of codegen code we'd need to maintain if the boxed kernel is sufficiently fast.

We proceed in two steps, as documented in the original issue:
> -  Just like the autograd not implemented fallback, the InplaceOrView kernel could either be boxed or unboxed. Ideally this InplaceOrView kernel will be boxed because in the templated (unboxed) case users would need to pass in a schema string. We should benchmark prototypes of both, and confirm that boxed is not significantly slower than a templated version.
>  -  If we decide to proceed with the boxed kernel we can also consider replacing the codegened InplaceOrView kernels with a boxed kernel. This has the benefit of reducing compilation time and binary size. Just like for autograd fallback, we should benchmark both codegened and boxed kernel to make sure there isn't a major regression.





cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: flutter
Issue: WidgetTester.dragUntilVisible() docs to say "use negative offset to swipe up"
Labels: a: tests,framework,d: api docs,c: proposal,P2,team-framework,triaged-framework

## Use case

I need to use `WidgetTester.dragUntilVisible()` (inherited from [`WidgetController.dragUntilVisible`](https://api.flutter.dev/flutter/flutter_test/WidgetController/dragUntilVisible.html)).  The method takes a `moveStep` parameter of type  [`Offset`](https://api.flutter.dev/flutter/dart-ui/Offset-class.html).  I need to know what numerical `dx` and `dy` values to pass to the `Offset` constructor.

I discovered the information by trial-and-error.  That took some time because of https://github.com/flutter/flutter/issues/88756, https://github.com/flutter/flutter/issues/88763 , https://github.com/flutter/flutter/issues/88759, and https://github.com/flutter/flutter/issues/88762.  `dragUntilVisible()` uses a negative offset to scroll down, while [`scrollUntilVisible()`](https://api.flutter.dev/flutter/flutter_test/WidgetController/scrollUntilVisible.html) uses a positive one.

## Proposal

Update the docs to say:
> `moveStep` is the movement of the virtual finger on the virtual screen.  To swipe up (scroll down), use negative `dy` and `dx=0`.  To swipe right, use positive `dx` and `dy=0`.
Repository: go
Issue: cmd/go: -keepfuzzing needs renaming, does not exist
Labels: NeedsFix,fuzz

Generally, we try to keep the flag names big-endian, so that related flags all have a common prefix, like bench, benchtime, benchmem; memprofile, memprofilerate; even fuzz, fuzzcachedir, fuzzminimizetime, fuzztime, fuzzworker. 

The exception in the go help testflag output is keepfuzzing, which doesn't begin with fuzz. It probably should. Maybe fuzzmore?

Also the flag seems not to be implemented. 

	% gotip test -v -fuzz=Fuzz -keepfuzzing
	flag provided but not defined: -keepfuzzing
	Usage of /tmp/go-build1779596492/b001/pkg.test:
		...


/cc @jayconrod @katiehockman
Repository: pytorch
Issue: Memory leak in multi-thread inference
Labels: high priority,module: performance,module: memory usage,triaged,module: multithreading

## Symptom

The memory usage of a process significantly increases when using more threads. It's likely PyTorch or some 3rd-party dependencies created expensive (much more than the ~8MB stack size) thread-local states. See #61920 for more discussion.  I tried build without MKLDNN, doesn't help. This issue seems has existed for a long time (https://discuss.pytorch.org/t/heap-size-increase-constantly-when-inference-with-new-thread/57621). 

## Repro

The following code creates 20 threads and run inference through the same ResNet50 model instance using the same input tensor. The process memory consumption keeps increasing when more threads are used. 

```python
import os
import threading
import psutil

import torch

from torchvision import models

batch_size = 120
image_w = 128
image_h = 128

def model_forward(model, input):
    return model(input)

if __name__=="__main__":
    model = models.resnet50()
    inputs = torch.randn(batch_size, 3, image_w, image_h)
    process = psutil.Process(os.getpid())
    for i in range(20):
        thread = threading.Thread(target=model_forward, args=(model, inputs))
        thread.start()
        thread.join()
        print(f"Round {i}: memory {process.memory_info().rss // 1000000} MB")
```

```
Round 0: memory 1491 MB
Round 1: memory 3261 MB
Round 2: memory 4242 MB
Round 3: memory 5342 MB
Round 4: memory 5423 MB
Round 5: memory 6220 MB
Round 6: memory 6635 MB
Round 7: memory 6915 MB
Round 8: memory 8206 MB
Round 9: memory 7646 MB
Round 10: memory 8966 MB
Round 11: memory 9125 MB
Round 12: memory 9690 MB
Round 13: memory 8881 MB
Round 14: memory 10648 MB
Round 15: memory 11228 MB
Round 16: memory 11716 MB
Round 17: memory 11000 MB
Round 18: memory 12270 MB
Round 19: memory 10994 MB
```

The same ResNet50 inference code with a single thread does not hit this issue. 

```python
import os
import threading
import psutil

import torch

from torchvision import models

def model_forward(model, input):
    return model(input)

if __name__=="__main__":
    model = models.resnet50()
    inputs = torch.randn(batch_size, 3, image_w, image_h)
    process = psutil.Process(os.getpid())
    for i in range(20):
        model_forward(model, inputs)
        print(f"Round {i}: memory {process.memory_info().rss // 1000000} MB")
```

```
Round 0: memory 1423 MB
Round 1: memory 1416 MB
Round 2: memory 1424 MB
Round 3: memory 2089 MB
Round 4: memory 2112 MB
Round 5: memory 2725 MB
Round 6: memory 2746 MB
Round 7: memory 2075 MB
Round 8: memory 2080 MB
Round 9: memory 1403 MB
Round 10: memory 2089 MB
Round 11: memory 2715 MB
Round 12: memory 3282 MB
Round 13: memory 3267 MB
Round 14: memory 3138 MB
Round 15: memory 1404 MB
Round 16: memory 2026 MB
Round 17: memory 1405 MB
Round 18: memory 1403 MB
Round 19: memory 1408 MB
```



cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @anjali411 @VitalyFedyunin @ngimel @heitorschueroff
Repository: godot
Issue: Non-matching texture filtering mode for cursor preview in new tilemap editor
Labels: bug,topic:editor,confirmed,topic:2d

### Godot version

4.0.dev.custom_build [a160a95ea]

### System information

W10, Vulkan, NVIDIA GeForce GTX 1080

### Issue description

When drawing on tilemaps using the new tilemap feature, the transparent preview of the tile under the drawing cursor always uses linear filtering.

It looks like this when the TileMap's filter mode is set to Nearest:

![image](https://user-images.githubusercontent.com/141511/131770801-8e267ed4-c960-4dec-b9f0-608986bc2f2e.png)

It should probably match whichever filter mode the TileMap is assigned to use, rather than assuming Linear.

### Steps to reproduce

1. Create a tileset with a tile.
2. Create a tilemap node, set its filtering mode to Nearest, and use the tileset to paint that tile.
3. Compare the tile preview to the painted tiles.

### Minimal reproduction project

_No response_
Repository: create-react-app
Issue: Local typescript module import
Labels: needs triage

I made a local module with typescript and tried to use it in another project by creating an npm link.

But I got an error saying it couldn't compile. 

message...
`Module parse failed: The keyword 'interface' is reserved (10:0`


I wonder if this is a part supported by the create react app environment or not.


Since I often have to modify my modules, I made a typescript-based module in the local environment and imported the module through the Npm link.
But **I didn't compile the module.** I didn't do it because I thought it would take a long time to compile. I imported **index.tsx in src instead of dist folder**.
Repository: storybook
Issue: storybook cannot import `.js` paths in `.tsx?` files.
Labels: bug,help wanted,has workaround,builder-webpack5

**Describe the bug**
I'm creating a UI Library that is distributed as a ES Module.

in typescript, to create an ES Module compliant package you must import/export all paths as `.js` as outlined here: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c

storybook does not currently infer these paths and will fail to find the .ts files during development.

in order to provide a great developer experience, storybook should support this functionality.

**To Reproduce**

https://github.com/lifeiscontent/storybook-repro

**System**

```
Environment Info:

  System:
    OS: Linux 5.11 Zorin OS 16
    CPU: (4) x64 Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz
  Binaries:
    Node: 14.17.4 - ~/.asdf/installs/nodejs/14.17.4/bin/node
    Yarn: 3.0.1 - ~/.asdf/installs/nodejs/14.17.4/.npm/bin/yarn
    npm: 6.14.14 - ~/.asdf/installs/nodejs/14.17.4/bin/npm
  Browsers:
    Chrome: 93.0.4577.63
    Firefox: 91.0.2
  npmPackages:
    @storybook/addon-actions: ^6.4.0-alpha.33 => 6.4.0-alpha.33 
    @storybook/addon-docs: ^6.4.0-alpha.33 => 6.4.0-alpha.33 
    @storybook/addon-essentials: ^6.4.0-alpha.33 => 6.4.0-alpha.33 
    @storybook/addon-links: ^6.4.0-alpha.33 => 6.4.0-alpha.33 
    @storybook/react: ^6.4.0-alpha.33 => 6.4.0-alpha.33 
```

**Additional context**

thanks for your help ❤️
Repository: create-react-app
Issue: How to customize assets  output folder when build?
Labels: stale,needs triage

The default assets ouput folder is `{BUILD_PATH}/static/...`,  Can i customize it like `{BUILD_PATH}/my_custom_path/static/...`?
But the  `homepage` field in `package.json` is just use for modify file path in index.html.
Repository: rust
Issue: Multidimensional array compilation takes too much time
Labels: A-LLVM,I-compiletime,T-compiler,A-array

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.

http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/

-->

### Code

Compile it with `--release` please.

```Rust
fn main() {
    let s = [[[[Option::<usize>::None; 10]; 10]; 10]; 10];
    println!("{:?}", s);
}
```


### 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.54.0 (a178d0322 2021-07-26)
binary: rustc
commit-hash: a178d0322ce20e33eac124758e837cbd80a6f633
commit-date: 2021-07-26
host: x86_64-apple-darwin
release: 1.54.0
LLVM version: 12.0.1
```

### Error output

It takes **3 mins** to compile.

```
   Compiling untitled v0.1.0 (/Users/Tnze/CLionProjects/untitled)
    Finished release [optimized] target(s) in 3m 15s
```
Repository: rust
Issue: Tracking Issue for `int_roundings`
Labels: T-libs-api,C-tracking-issue,disposition-merge,finished-final-comment-period

Feature gate: `#![feature(int_roundings)]`

This is a tracking issue for the `div_floor`, `div_ceil`, `next_multiple_of`, and `checked_multiple_of` methods on all integer types.

### Public API

```rust
impl {integer} {
    #[unstable]
    pub const fn div_floor(self, rhs: Self) -> Self;
}

impl {signed integer} {
    #[unstable]
    pub const fn div_ceil(self, rhs: Self) -> Self;

    #[unstable]
    pub const fn next_multiple_of(self, rhs: Self) -> Self;

    #[unstable]
    pub const fn checked_next_multiple_of(self, rhs: Self) -> Option<Self>;
}

impl {unsigned integer} {
    #[stable(since = "1.73.0")]
    pub const fn div_ceil(self, rhs: Self) -> Self;

    #[stable(since = "1.73.0")]
    pub const fn next_multiple_of(self, rhs: Self) -> Self;

    #[stable(since = "1.73.0")]
    pub const fn checked_next_multiple_of(self, rhs: Self) -> Option<Self>;
}
```

### Steps / History

- https://github.com/rust-lang/rust/pull/88582
- https://github.com/rust-lang/rust/issues/88971
- https://github.com/rust-lang/rust/pull/89184
- https://github.com/rust-lang/rust/pull/90329
- https://github.com/rust-lang/rust/pull/91141
- https://github.com/rust-lang/rust/pull/95359
- https://github.com/rust-lang/rust/pull/94455

### Unresolved Questions

- None yet.
Repository: flutter
Issue:  [Desktop] Support custom cursor 
Labels: c: new feature,framework,c: proposal,a: desktop,a: mouse,P3,team-framework,triaged-framework

According to https://github.com/flutter/flutter/issues/58260, in pre flutter version, we can custom cursor shape by self image.
But, now it is not work.
Now we can achieve this by only modifying a few core methods.
```dart
var listnode = document.getElementsByTagName('flt-glass-pane') 
// cast node to Element, then
node.style.setProperty('cursor', 'url(\'https://www.ernegonzal.com/wp-content/uploads/2020/02/hand-2.png\'), auto');
```
This is  according [mouse_cursor.dart](https://github.com/flutter/engine/blob/master/lib/web_ui/lib/src/engine/mouse_cursor.dart)
``` dart
 static const Map<String, String> _kindToCssValueMap = <String, String>{
    'alias': 'alias',
    'allScroll': 'all-scroll',
     // ...
  };
  static String _mapKindToCssValue(String? kind) {
    return _kindToCssValueMap[kind] ?? 'default';
  }

  void activateSystemCursor(String? kind) {
    DomRenderer.setElementStyle(
      domRenderer.glassPaneElement!,
      'cursor',
      _mapKindToCssValue(kind),
    );
  }
```
which is called by fellow example code
```dart
MouseRegion(
  cursor: SystemMouseCursors.click,
  child: Container(),
),
```

So, can provide `SystemMouseCursors.custom` and trans image url to support custom cursor shape ?
Repository: node
Issue: doc: "Buffers and character encodings" issue regarding base64/base64url 
Labels: buffer,doc

# 📗 API Reference Docs Problem


<!-- The output of “node --version”. -->

- **Version**: v16.8.0 (possibly other versions as well)

<!-- The output of “uname -a” (UNIX) or version
and 32-bit or 64-bit (Windows). -->

- **Platform**: Linux 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux (but I think this is irrelevant for this issue

<!-- The name of affected core module. -->

- **Subsystem**: Buffer / encodings

## Location

_Section of the site where the content exists_

Affected URL(s):

- https://nodejs.org/docs/latest-v16.x/api/buffer.html

## Description

_Concise explanation of the problem_

<!-- If applicable, include any screenshots that
may help solve the problem. -->

The documentation for 'base64' and 'base64url' both reference  RFC 4648, Section 5, but base64 and base64url are two distinct encodings, and the contents of Section 5 states "This encoding may be referred to as "base64url".  This encoding should not be regarded as the same as the "base64" encoding and should not be referred to as only "base64".  Unless clarified otherwise, "base64" refers to the base 64 in the previous section."

Because of this, it is unclear whether `buf.toString('base64')` returns base64 or base64url. If it indeed returns base64url, then it is unclear why 'base64url' exists as another encoding option.

---

<!-- Use “[x]” to check the box below if you are
interested in contributing. -->

- [ ] I would like to work on this issue and
      submit a pull request.