sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: NodeJS Crashed
Labels: net

### Version

v16.15.0

### Platform

Linux localhost 4.15.0-123-generic #126-Ubuntu SMP Wed Oct 21 09:40:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

_No response_

### What steps will reproduce the bug?

```
Error: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at new NodeError (node:internal/errors:372:5)
    at assert (node:internal/assert:14:11)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1151:3)
[ERROR] 12:00:06 Error: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
```

### How often does it reproduce? Is there a required condition?

everytime when nodejs is reconnecting

### What is the expected behavior?

its should work and not crash

### What do you see instead?

```
Error: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

    at new NodeError (node:internal/errors:372:5)
    at assert (node:internal/assert:14:11)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1151:3)
[ERROR] 12:00:06 Error: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
```

### Additional information

Code

```js
import { Socket } from "net";

const Client = new Socket();

Client.setTimeout(2500);
Client.setKeepAlive(true);

const ConnectOpts = {
    host:"127.0.0.1",
    port:9988
}

var ConnectIntervel = setInterval(() => {
    Client.connect(ConnectOpts);
},10000);

Client.on("connect", async () => {

    clearInterval(ConnectIntervel);

    console.log("Connected!")

    Client.write(JSON.stringify({
        "never":true,
        "gonna":true,
        "give":true,
        "you":true,
        "up":true
    }))

})

Client.on("data", async (BufferData) => {

})

Client.on('close', function(e) {

    Client.destroy();

    ConnectIntervel = setInterval(() => {
        Client.connect(ConnectOpts);
    },5000);

});

Client.on('error', (err) => {

    Client.destroy();

    ConnectIntervel = setInterval(() => {
        Client.connect(ConnectOpts);
    },5000);
    
})
```
Repository: flutter
Issue: Create `takeExceptionDetails` which is similar to `takeException` but allows the user to know details (e.g. stack trace)
Labels: a: tests,c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

<!-- 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

Currently, users can `takeException` to get the most recent exception. However, they can only see the `Exception`, but lose all details like stack trace, which is very useful when debugging as we all know. Therefore, this simple PR adds that information.

This is especially useful when implementing convenient_test, an open-source package to help write & debug tests easily. https://github.com/fzyzcjy/flutter_convenient_test . But as described above, it is surely also pretty useful for other users.

<!--
     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

see above

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     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: angular
Issue: service-worker: configure response status codes to treat as failed/offline with freshness strategy
Labels: feature,area: service-worker,feature: under consideration

### Which @angular/* package(s) are the source of the bug?

service-worker

### Is this a regression?

No

### Description


Expected behaviour: freshness strategy should return to user fetching requested data only if request was successful.
If request is unsuccessful (has 500, 504 and other codes) it should return cached result instead of bad result. And bad result should not be cached at all.

But in reality:

freshness strategy return for user bad results.

Interestingly, freshness strategy works as expected if web-server absolutely died (network error: connection refused). I mean, all configured in dataGroup requests begin to return from cache and web-application works despite dead backend. It is different with particular bad request (as I described above).

Performance strategy works as expected (it returns cached results firstly)

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 11.2.19
Node: 14.8.2
OS: darwin x64

Angular: 11.2.14
```


### Anything else?

https://angular.io/guide/service-worker-config#datagroups

https://stackoverflow.com/questions/69132411/angular-service-worker-return-cached-response-if-server-returns-error
Repository: pytorch
Issue: The codegen unconditionaly generate code even when it is not going to be used
Labels: triaged,module: codegen

The codegen today generate cpp and header for all the dispatch keys listed in https://github.com/pytorch/pytorch/blob/2083b16f68963e563c6fbf6bf1084e78a7f66139/torchgen/model.py#L144-L163

We should be able to skip all the cuda-related ones when doing a CPU-only build and skip the mkldnn ones when it is not available.
This would speed up codegen for such builds.

cc @ezyang @bhosmer @bdhirsh
Repository: go
Issue: x/website: `Internal Server Error` from `go-get` requests to golang.org
Labels: NeedsInvestigation,website

```
#!watchflakes
post <- log ~ `https://golang\.org/.*: 500 Internal Server Error`
```

```
            > ! go list -m golang.org/x/text
            [stderr]
            go: unrecognized import path "golang.org/x/text": reading https://golang.org/x/text?go-get=1: 500 Internal Server Error
            go: example.com@v0.0.0 requires
            	golang.org/x/text@v0.1.1-0.20170915032832-14c0d48ead0c+incompatible: unrecognized import path "golang.org/x/text": reading https://golang.org/x/text?go-get=1: 500 Internal Server Error
            [exit status 1]
```

`greplogs -l -e 'https://golang\.org/x/[^?]*\?go-get=1.* 5\d\d ' --since=2021-01-01`
[2022-05-10T20:13:31-2ecf747/linux-amd64-longtest](https://build.golang.org/log/6bd2bdf22c77b1184f930d6b2df62c7daac69f15)
[2022-05-10T16:17:51-30a2750/linux-386-longtest](https://build.golang.org/log/82881b5637db2680bd3e1ceda9ff75aed37ac374)
[2022-05-10T15:33:47-f7209f9/linux-386-longtest](https://build.golang.org/log/b63f36fe6ac64e58d993a0c5fdad2e84f4601482)
[2022-05-04T20:20:28-fbb47e8/linux-amd64-longtest](https://build.golang.org/log/83712c4f167ce7828a1a604c3a424e7f014270fd)
[2022-04-11T02:55:52-a6f6932/linux-386-longtest](https://build.golang.org/log/33b2466a7da925ec7a642e0673198222e47667f5)
[2022-02-15T21:18:59-08ed488/linux-386-longtest](https://build.golang.org/log/8fd9d1746de1983a40f97df7259a1768a1d5ea54)
[2022-01-11T15:23:23-28f2869/linux-386-longtest](https://build.golang.org/log/996bc5eb293c26f60f2a9902586dd33372ea8949)
[2022-01-06T21:38:57-c5540e5/linux-amd64-longtest](https://build.golang.org/log/7eaa284d513324d2483d9322f90c193bc0e99e51)
[2021-11-22T23:09:35-9678f79/linux-386-longtest](https://build.golang.org/log/632883450dee2c0cb08817ac8ccf9b6376baddbc)
[2021-11-09T16:55:47-34abc12/linux-386-longtest](https://build.golang.org/log/71de0bda100d22c70c6e522d2d3af0848be727e2)
[2021-10-15T16:57:36-a80e53e/linux-386-longtest](https://build.golang.org/log/1770424a0231da50b86bb49755a7efe3ca9b2ae7)
[2021-10-08T21:38:44-74abcab/linux-386-longtest](https://build.golang.org/log/07b3d2c894b5b391d2c112361784ede08237afde)
[2021-10-04T19:51:37-579ff8b/linux-amd64-longtest](https://build.golang.org/log/234b176482f8a9c06d6dc0b3c7cc21fbd3f7601a)
[2021-09-24T00:30:36-c90ead9/linux-386-longtest](https://build.golang.org/log/618f196ce8282e3c6832cace97274699e4762241)
[2021-09-02T13:52:06-a35c5c9/linux-386-longtest](https://build.golang.org/log/9e6b4e34f4684498ccf89018400d05df12079c0c)
[2021-08-28T18:48:37-f4cd001/linux-386-longtest](https://build.golang.org/log/ee4e52390b29b940aceece86b0290d6aef2fc17d)
[2021-04-21T13:38:59-4d56576/linux-386-longtest](https://build.golang.org/log/51b3e86f5dd9efe3dd032b0a5d0edae8209ee3d7)
Repository: godot
Issue: Memory leak from misconfigured Skeleton
Labels: bug,topic:rendering,crash

### Godot version

4.0 Alpha 8 #917fd65748957304c987414c63d54ef4f6972394

### System information

Windows 7 64 Bit, AMD Phenom X3 8450 (x86_64 (?)), 8GB Dual-Channel DDR2 @ 333MHz, 2047MB NVIDIA GeForce GTX 960 (PNY), GPU Driver version 452.06, Vulkan

### Issue description

After importing a Godot 3.4 project into Godot 4 Alpha 7, I noticed that the Engine kept crashing if the Engine window is minimized for a longer duration, updating it to Alpha 8 didn't fixed it, after some good help from a Discord member Squish, it got narrowed down to my NPCs that im using, their model/skeleton seems to be corrupted or simply misconfigured, before I redo them I thought I leave one here incase its a problem that has to be fixed.

Once it had enough leaked and then crashed I will get a error message:
<img width="290" alt="crash" src="https://user-images.githubusercontent.com/105369276/167868872-74031283-f06d-40b2-841c-fd282f4ef66f.png">


### Steps to reproduce

- extract and import the reproduction project into Godot 4.0 Alpha 8 ( commit 917fd65748957304c987414c63d54ef4f6972394 )
- open up "HumanEnemy.tscn" (if its not open already)
- open up a Task Manager and look for "Godot_v4.0-alpha8_win64.exe"
- minimize your Engine window and wait about 1 minute. (dont start the "game")
- you should see the memory the engine uses increase, it gets faster the more "HumanEnemies" you have.

### Minimal reproduction project

[test.zip](https://github.com/godotengine/godot/files/8670684/test.zip)
Repository: material-ui
Issue: Sliders not functioning correctly on iphone 13 mini.
Labels: bug 🐛,component: slider,ready to take

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When I use any kind of slider on the iphone 13 mini (iOS 15.4.1) the sliders do not work properly.

80% of the time when you drag a slider it works. But about 20% of the time the slider jumps back to where you slid it from, potentially 2-5 increments closer to where you were trying to drag to. This can be quite frustrating when trying to make precise adjustments and it keeps jumping back.

It does not seem to be affected by how quickly I drag or finger placement etc.

### Expected behavior 🤔

Sliders to function as normal, like on other devices.

### Steps to reproduce 🕹

Steps:

1. Use the iPhone 13 mini
2. Drag any slider multiple times
3. Sometimes it won't register the drag properly.


### Context 🔦

The context is that I'm trying to drag the slider to input a specific value.

### Your environment 🌎

This applies to all environments. I've loaded the mui slider documentation on my iphone and had the same results.
This bug affects both safari and chrome.
Repository: pytorch
Issue: CrossEntropyLoss computes SoftMax always across the second dimension
Labels: module: nn,module: loss,triaged,actionable

### 🚀 The feature, motivation and pitch

When working with recurrent neural networks, such as `torch.nn.RNN`,  the shape of the output (the logits) of that network is `NxLxD` where `N` is the batch size, `L` is the sequence length and `D` is the feature dimension. When using one-hot encodings for our targets in the same dimensions, e.g., for text processing, we want to use categorical cross entropy-loss on top of softmax activation (i.e. `torch.nn.CrossEntropyLoss`). 

According to the documentation, `torch.nn.CrossEntropyLoss` performs sodtmax **always** on the second dimension of the given logits. In our case, however, we need to compute softmax across the **third** dimension. Currently, it is required to `permute(0,2,1)` both the logits and the targets to artificially turn the third dimension second.

The requested feature would be a `dim` parameter in the constructor of the `torch.nn.CrossEntropyLoss` that enables to select the dimension over which softmax is computed. Similarly, for `torch.nn.functional.cross_entropy`, a `dim` parameter would be required.

### Alternatives

I guess, a quick-and-dirty implementation would simply apply the `permute` internally before passing the data to the C implementation.

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: vscode
Issue: margin of context between right and left are different in notebook
Labels: ux,polish,notebook-layout

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

版本: 1.68.0-insider (system setup)
提交: 8c882677f947ef7ec748e7f031c7b5470aaf9be1
日期: 2022-05-11T05:17:12.474Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Windows_NT x64 10.0.22616
Steps to Reproduce:

![image](https://user-images.githubusercontent.com/1876302/167884528-7bcf5654-995d-4c35-83c2-c8781f3139b8.png)
Repository: TypeScript
Issue: Rename symbol is not working in template literal type
Labels: Suggestion,Awaiting More Feedback

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.67.1
- OS Version: macOs 11.6 (20G165)

❌ Doesn't work like this:

```ts
type Prefix = 'NICE';
type Suffix = 'WORK'

const myName: `${Prefix}${Suffix}` = 'NICEWORK';
```

1. Select `'NICE'` text, use 'rename symbol' action
2. `myName` won't change

But if the template literal doesn't combined any other symbols, it works fine✅:

```ts
type Prefix = 'NICE';

const myName: `${Prefix}` = 'NICE';
```

1. Select `'NICE'` text, use 'rename symbol' action
2. `myName` will change.
Repository: rust
Issue: Tracking issue for the implementation of RFC 2011: Generic assert
Labels: T-compiler,C-tracking-issue,T-libs,F-generic_assert

Edit(fmease): The overarching tracking issue: #44838 (feature `generic_assert`).

Just a better-than-a-TODO internal issue to track the remaining things of https://github.com/rust-lang/rust/pull/96496.

* [ ] Constant environments.
* [ ] Cap size to avoid large copies (https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=85575be37ce9ebaa2286ba1a7ed4930a).
* [ ] ~~Capture `matches!` arguments.~~ (Postponed, see #110382)
* [x] Prevent copies when methods don't require ownership. For example, `PartialEq`.
* [ ] ~~Capture block statements~~
* [ ] ~~Pretty printing synchronization~~

@rustbot claim
Repository: vscode
Issue: Allow parameter hints and completion documentation to appear in a docked panel instead of floating over the code
Labels: feature-request,suggest,editor-parameter-hints

Parameter hints and the documentation popup in code completion can be useful, but sometimes they completely obscure the code being typed:

<img width="1306" alt="Screenshot 2022-05-11 at 16 52 13" src="https://user-images.githubusercontent.com/1078012/167893635-4dc9cb96-c147-415f-9660-f4dcad248a35.png">

It would be nice if these could be shown in an alternative location (such as a dockable panel that can be put in a sidebar or along the bottom) to avoid covering so much of the code.

I'm aware both can quickly be toggled with their respective shortcuts (and that I can control whether they open automatically), but those aren't perfect solutions - sometimes you're trying to compare the parameters you've written to the signature to understand what's wrong, and having to flick them on and off is less convenient than being able to see both on the screen at the same time.
Repository: flutter
Issue: flutter command line tool error
Labels: tool,a: internationalization,platform-windows,t: flutter doctor,P2,team-tool,triaged-tool


![image](https://user-images.githubusercontent.com/68740152/167894155-5cb9d009-3b53-4f1e-9360-0fdfdf8cd4e8.png)

When I type flutter doctor -v, instead of got check mark I always got this symbol â€¢, how can I fix this?
Repository: opencv
Issue: Build fails after WITH_OPENGL is added (3.4.17)
Labels: category: build/install,platform: win32

Rebuilding **OpenCV 3.4.17** that already had _WITH_OPENCL_ and _WITH_CUDA_ after enabling _WITH_OPENGL_ fails.

- OpenCV => 3.4.17
- Operating System / Platform =>Windows 10 x64
- Compiler =>  Visual Studio 2019

##### Detailed description

The Debug build fails on:

1. _opencv_python3_ project's configuration is NOT pointing to python39_d.lib anymore but to python39.lib even though cmake configuration provides the path to python39_d.lib.  Before adding _WITH_OPENGL_ this was correct. Easy workaround is the correct this manually in the VS project property page (and is a non-issue for non-debug builds).

2. _opencv_world3417_ build fails with unresolved external symbol **clGetGLContextInfoKHR**; showstopper. no workaround.

##### Steps to reproduce
![image](https://user-images.githubusercontent.com/16941640/167903285-f9f45013-1858-4b01-84ea-1ac599669e4d.png)
![image](https://user-images.githubusercontent.com/16941640/167903070-54f99242-2767-4e1e-9895-a8090bd690a1.png)
Configure and Generate using these "WITH"s and build debug version via Visual Studio 2019.

##### Issue submission checklist

 -  [X] I report the issue, it's not a question
   <!--
   OpenCV team works with forum.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with questions without a real issue statement will be
   closed.
   -->
 - [X] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found any solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://forum.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [X] I updated to the latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only the latest release for each branch.
   The ticket is closed if the problem is not reproduced with the modern version.
   -->
 - [ ] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as an archive to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->