sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: Python
Issue: Some algorithms are "how-to" examples
Labels: help wanted

In our [Contributing Guidelines](https://github.com/TheAlgorithms/Python/blob/master/CONTRIBUTING.md):

> Algorithms in this repo should not be how-to examples for existing Python packages. Instead, they should perform internal calculations or manipulations to convert input values into different output values. Those calculations or manipulations can use data types, classes, or functions of existing Python packages but each algorithm in this repo should add unique value.

And after some investigation like #6201, one can find some implementations that resemble online tutorials or are too trivial. In #6201, [`machine_learning/support_vector_machines.py`](https://github.com/TheAlgorithms/Python/blob/c86aa72cfa0467bd9a5711d7b5a77ed8243e49f1/machine_learning/support_vector_machines.py) is removed. It should be _migrated_ to a much detailed implementation of SVM instead of importing packages.


Migration list:
- [ ] [`machine_learning/support_vector_machines.py`](https://github.com/TheAlgorithms/Python/blob/c86aa72cfa0467bd9a5711d7b5a77ed8243e49f1/machine_learning/support_vector_machines.py)
Repository: pytorch
Issue: activation checkpointing with non_reentrant implementation memory leaks
Labels: high priority,triage review,oncall: distributed,triaged

### 🐛 Describe the bug

This is coming from an internal report where using `CheckpointWrapper` with the `CheckpointImpl.NO_REENTRANT` gradually leaks memory, leading to CUDA OOM. 

### Versions

main

cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: TypeScript
Issue: Add new setting to control JSX quote style
Labels: Bug,Help Wanted

<!-- ⚠️⚠️ 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.68.0
- OS Version: macOS 12.4

Steps to Reproduce:

1. Starting typing a new JSX string attribute (eg. `className`) then hit <kbd>Tab</kbd> to accept an auto-completion.
2. There will be quotes added (eg. `className='|'`) that are single quotes instead of double quotes. (This didn't used to happen in earlier versions of VSCode.)

This has been brought up in multiple issues: 

- https://github.com/microsoft/vscode/issues/139864 
- https://github.com/microsoft/vscode/issues/143164 
- https://github.com/microsoft/vscode/issues/149752

But each time closed because it seems like the desired behavior and cause of the issue isn't clear.

The issue is that the most common JSX coding style uses double quotes (`"`) **regardless** of whether the surrounding JavaScript/TypeScript code uses single or double quotes. So right now the auto-completion is inferring quote style from the surrounding non-JSX code and getting the quote style wrong.

There are three different quote-related settings:

<img width="572" alt="image" src="https://user-images.githubusercontent.com/311752/175209448-d4230483-7765-46f1-9fdb-7a59ffce3abc.png">

<img width="560" alt="image" src="https://user-images.githubusercontent.com/311752/175209467-4971ecde-5be1-4355-936e-565551107664.png">

<img width="554" alt="image" src="https://user-images.githubusercontent.com/311752/175209523-9e8b7384-62e5-4141-ac90-336ccf6526e1.png">

I believe it could be solved a number of ways: 

1. Use the HTML-specific setting for JSX code instead of the JS/TS-specific ones. 
2. Or, add a new JSX-specific quote setting.
3. Or, augment the `auto` behavior to check nearby JSX code instead of nearby JS/TS code. (Might not catch first instance.)

Thanks for reading!
Repository: godot
Issue: FileSystemDock doesn't have a signal for file/folder creation
Labels: enhancement,topic:editor,topic:plugin

### Godot version

3.4.stable

### System information

Windows 10

### Issue description

In `FileSystemDock` we have the following signals:

```
    file_removed ( String file )

    files_moved ( String old_file, String new_file )

    folder_moved ( String old_folder, String new_file )

    folder_removed ( String folder ) 
```

It make no sense that there aren't
```
    file_created( String file )

    folder_created( String folder )
```

(+ There is a typo it is not `files_moved` but `file_moved`, no s, as the signal gives only one file)

In the meantime, if someone knows a way to detect created files, I am interested.


### Steps to reproduce

Check the docs for [FileSystemDock](https://docs.godotengine.org/en/stable/classes/class_filesystemdock.html#filesystemdock).

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: Orthogonal Polynomials
Labels: feature,triaged,module: special

# Orthogonal Polynomials

A brief proposal for providing a complete suite of orthogonal polynomials as PyTorch operators. Enjoy!

One of a five-part series of special functions issues:

- Gamma and Related Functions (#78065)
- Bessel and Related Functions (#76324)
- Orthogonal Polynomials (#80152)
- Elliptic Functions and Integrals (#80157)
-

## API

### Chebyshev Polynomials

- [x] `chebyshev_polynomial_t(input: Tensor, n, *, out=None) → Tensor`

Chebyshev polynomial of the first kind $T_{n}\left(\text{input}\right)$.

- [x] `chebyshev_polynomial_u(input: Tensor, n, *, out=None) → Tensor`

Chebyshev polynomial of the first kind $U_{n}\left(\text{input}\right)$.

- [x] `chebyshev_polynomial_v(input: Tensor, n, *, out=None) → Tensor`

Chebyshev polynomial of the first kind $V_{n}\left(\text{input}\right)$.

- [x] `chebyshev_polynomial_w(input: Tensor, n, *, out=None) → Tensor`

Chebyshev polynomial of the first kind $W_{n}\left(\text{input}\right)$.

### Shifted Chebyshev Polynomials

- [x] `shifted_chebyshev_polynomial_t(input: Tensor, n, *, out=None) → Tensor`

Shifted Chebyshev polynomial of the first kind $T_{n}^{\ast}\left(\text{input}\right)$.

- [x] `shifted_chebyshev_polynomial_u(input: Tensor, n, *, out=None) → Tensor`

Shifted Chebyshev polynomial of the first kind $U_{n}^{\ast}\left(\text{input}\right)$.

- [x] `shifted_chebyshev_polynomial_v(input: Tensor, n, *, out=None) → Tensor`

Shifted Chebyshev polynomial of the first kind $V_{n}^{\ast}\left(\text{input}\right)$.

- [x] `shifted_chebyshev_polynomial_w(input: Tensor, n, *, out=None) → Tensor`

Shifted Chebyshev polynomial of the first kind $W_{n}^{\ast}\left(\text{input}\right)$.

### Hermite Polynomials

- [x] `hermite_polynomial_h(input: Tensor, n, *, out=None) → Tensor`

Physicist’s Hermite polynomial $H_{n}\left(\text{input}\right)$.

- [x] `hermite_polynomial_he(input: Tensor, n, *, out=None) → Tensor`

Probabilist’s Hermite polynomial $He_{n}\left(\text{input}\right)$.

### Charlier Polynomials

- [ ] `charlier_polynomial_c(input: Tensor, a, n, *, out=None) → Tensor`

### Gegenbauer Polynomials

- [ ] `gegenbauer_polynomial_c(input: Tensor, m, n, *, out=None) → Tensor`

Gegenbauer polynomial $C_{n}\left(\text{input}\right)$.

### Jacobi Polynomials

- [ ] `jacobi_polynomial_p(input: Tensor, a, b, n, *, out=None) → Tensor`

Jacobi polynomial $P_{n}\left(\text{input}\right)$.

### Laguerre Polynomials

- [ ] `generalized_laguerre_polynomial_l(input: Tensor, a, n, *, out=None) → Tensor`

- [x] `laguerre_polynomial_l(input: Tensor, n, *, out=None) → Tensor`

### Legendre Polynomials

- [x] `legendre_polynomial_p(input: Tensor, n, *, out=None) → Tensor`

Legendre polynomial $P_{n}\left(\text{input}\right)$.

### Shifted Legendre Polynomials

- [ ] `shifted_legendre_polynomial_p(input: Tensor, n, *, out=None) → Tensor`

Shifted Legendre polynomial $P_{n}^{\ast}\left(\text{input}\right)$.
Repository: pytorch
Issue: [primTorch] No _refs support for torch.Tensor.requires_grad.__get__
Labels: triaged,module: primTorch

Not sure what's going on here -- I would expect requires_grad should be a property access like ndim

cc @ezyang @mruberry @ngimel @eellison
Repository: material-ui
Issue: ReactSwipeableView is resulting in errors with react 18
Labels: docs,external dependency,component: tabs

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

SwipeableDrawer is resulting in the following console error in react 18:
```
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code.
```

There is a related issue [here](https://github.com/oliviertassinari/react-swipeable-views/issues/659), but it is getting no traction so far.

### Expected behavior 🤔

No error with react 18.

### Steps to reproduce 🕹

Steps:

1.
2.
3.
4.


### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: godot
Issue: Vulkan: ReflectionProbe not visible in subviewport
Labels: topic:rendering,needs testing,topic:3d

### Godot version

4.0 alpha10

### System information

linux

### Issue description

reflection probes do not affect objects in subviewport camera
even when visualinstance3D layers are checked

![screen](https://user-images.githubusercontent.com/95492794/175375795-c7a694dd-7336-4c56-8baa-5589e257394d.jpg)

subviewport always renders reflected light of environment settings

### Steps to reproduce

create a subviewport with second camera, set the cull mask of the 2nd camera to 2 (assign an object to layer2)
enable visualinstance3D layers to include layer 2 on the reflection probe.

>subviewport doesnt take the reflection probe into account, it renders the reflected light property of the assigned environment

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: AMP step() enforce synchronization
Labels: triaged,module: amp (automated mixed precision)

### 🐛 Describe the bug

# torch/cuda/amp/grad_scalar.py
def _maybe_opt_step(self, optimizer, optimizer_state, *args, **kwargs):
        retval = None
        if not sum(v.item() for v in optimizer_state["found_inf_per_device"].values()): **# v is on gpu**
            retval = optimizer.step(*args, **kwargs)
        return retval

### Versions

Collecting environment information...
PyTorch version: 1.11.0+cu115
Is debug build: False
CUDA used to build PyTorch: 11.5
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.31

Python version: 3.8.10 (default, Mar 15 2022, 12:22:08)  [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.4.0-105-generic-x86_64-with-glibc2.29
Is CUDA available: True
CUDA runtime version: 11.5.119
GPU models and configuration: GPU 0: NVIDIA A100 80GB PCIe
Nvidia driver version: 510.47.03
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.21.6
[pip3] torch==1.11.0+cu115
[pip3] torch-geometric==2.0.4
[pip3] torch-scatter==2.0.9
[pip3] torch-sparse==0.6.13
[conda] Could not collect

cc @mcarilli @ptrblck
Repository: pytorch
Issue: GEGLU activation
Labels: module: nn,triaged,enhancement,needs research

### 🚀 The feature, motivation and pitch

Seems to be the latest and greatest activation function for transformers.

See https://arxiv.org/abs/2002.05202v1

### Alternatives

One could copy-paste the implementation from https://github.com/pfnet-research/deep-table/blob/237c8be8a405349ce6ab78075234c60d9bfe60b7/deep_table/nn/layers/activation.py

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: flutter
Issue: Refactor or replace ExpansionPanel / ExpansionPanelList for more efficient scrolling
Labels: framework,c: performance,f: scrolling,customer: google,c: proposal,good first issue,P3,team-framework,triaged-framework

These widgets do not implement performant scrolling, in fact they do not actually scroll. In the API docs, the sample code places the ExpansionPanelList widget in a SingleChildScrollView which is not optimal. :(

https://api.flutter.dev/flutter/material/ExpansionPanelList-class.html

In discussing with another customer, I think the best way to approach this would be to refactor, or just replace these widgets. They are ripe for scrolling performance issues.

Ideally, ~the ExpansionPanelList would introduce its own Viewport, like a CustomScrollView, and~ each ExpansionPanel contained within would be a SliverAnimatedList to animate the items as it opened and closed. This would be much much more efficient.

Edit: Now that I think about it, updating ExpansionPanelList could probably be skipped if it is only adding a CustomScrollView. That wrapper does not sound necessary, unless there are other features it would provide. Curious though to see what other folks think and want from this. :)
Repository: pytorch
Issue: Torch.fx: add reporting of the name of a module not found during tracing
Labels: triaged,module: fx

### 🚀 The feature, motivation and pitch

During fx tracing of modules, the function `path_of_module` tries to get the qualified name of submodules.  If it is unable to find the module (as a member of the root modules `named_modules()` method), it returns a `NameError` that does not report which module caused this issue.  This PR adds reporting of the name of that module, making debugging easier.

### Alternatives

N/A, this is just making error messages more useful

### Additional context

One example that would raise this issue is the following torch model:
```
class ExampleModel(nn.Module):
    def __init__(self):
        super().__init__()
        self.conv1 = nn.Conv2d(3,64,(3,3))

    def forward(self, x):
        x = self.conv1(x)
        x = nn.ReLU()(x)
        return x
```
This model works training and inference, but fails fx tracing due to the initialization of the nn.ReLU() module in the forward pass.  In a toy example like above, tracing down this issue can be straightforward, but in a larger, production sized model, a lack of helpful error messages can make this a daunting task.

cc @ezyang @SherlockNoMad
Repository: rust
Issue: `for<'a> &'a T: 'a` and closures regressed
Labels: P-high,regression-from-stable-to-stable,C-bug,T-types

In https://github.com/rust-lang/rust/pull/98109, we fixed some bugs relating to NLL and `for` but apparently regressed a few examples. There are two tests in the test suite:

* [`collectivity-regression.rs`](https://github.com/rust-lang/rust/blob/e7ed8fe481fe103383f55a015a19f641450b76a3/src/test/ui/generic-associated-types/collectivity-regression.rs)
* [`snocat-regression.rs`](https://github.com/rust-lang/rust/blob/e7ed8fe481fe103383f55a015a19f641450b76a3/src/test/ui/nll/snocat-regression.rs)
Repository: vscode
Issue: Inconsistent use of beaks in tooltip and hovers
Labels: bug,ux

## Beaks
Activity bar
<img width="197" alt="CleanShot 2022-06-23 at 14 24 32@2x" src="https://user-images.githubusercontent.com/35271042/175404949-00b5c101-f7a2-4a0e-98e1-84f8adccd8a3.png">

Status bar
<img width="299" alt="CleanShot 2022-06-23 at 14 25 07@2x" src="https://user-images.githubusercontent.com/35271042/175405034-13879e03-61d1-4555-8d59-68cf6861ff45.png">

Command center
<img width="436" alt="CleanShot 2022-06-23 at 14 25 41@2x" src="https://user-images.githubusercontent.com/35271042/175405130-32a3b519-d188-485e-a77f-48ea3f35f7b0.png">

Extensions
<img width="736" alt="CleanShot 2022-06-23 at 14 26 24@2x" src="https://user-images.githubusercontent.com/35271042/175405222-8b50cd6b-620b-4b01-b5e2-a6d67a038b33.png">

<img width="160" alt="CleanShot 2022-06-23 at 14 29 00@2x" src="https://user-images.githubusercontent.com/35271042/175405576-74b4e8f2-34aa-4daa-a5b1-2b7ce0fd340b.png">

Peek views
<img width="946" alt="CleanShot 2022-06-23 at 14 35 20@2x" src="https://user-images.githubusercontent.com/35271042/175406428-4d7a842a-d22e-40ed-b832-597261ac3873.png">


## No Beaks

Editor hovers
<img width="535" alt="CleanShot 2022-06-23 at 14 30 57@2x" src="https://user-images.githubusercontent.com/35271042/175405838-71bf8768-1b66-4d46-8754-9ad0390a14ce.png">

Custom tree views
<img width="606" alt="CleanShot 2022-06-23 at 14 30 33@2x" src="https://user-images.githubusercontent.com/35271042/175405790-f3e19972-8c87-4d6c-8e94-c410adb2ee25.png">
Repository: godot
Issue: Exported typed variables in a tool script have wrong initial value if not initialized
Labels: bug,topic:gdscript,regression

### Godot version

ecf1877

### System information

Windows 10 x64

### Issue description

```GDScript
@tool
extends Node
@export var test: int
```
`test` will have value saved to scene even when it's not changed. It will save 0. The revert arrow appears, but clicking it does nothing.

### Steps to reproduce

1. Create `@tool` script
2. Export a typed variable, but don't initialize it
3. Try to revert it to default in the inspector

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: [NVFuser] Investigate modules with bad performance relative to eager
Labels: triaged,module: nvfuser,module: primTorch

### 🚀 The feature, motivation and pitch

In particular, `hf_DistilBert_forward_0` has ~30% regression compared to eager.

Status document (for those who have access): https://docs.google.com/document/d/1XU48ru9Cj4XFJJF6FTQ2X_QFuzyLroE1oomKGleYfP8/edit?usp=sharing

cc @ezyang @mruberry @ngimel @jjsjann123 @kevinstephano
Repository: pytorch
Issue: [NVFuser] Investigate models without any fusion groups found 
Labels: triaged,module: nvfuser

### 🚀 The feature, motivation and pitch

Many of the modules (29%) have no fusion groups found. It's possible that there's actually a bug in the partitioner, because this number seems high.

For those who have access: https://docs.google.com/document/d/1XU48ru9Cj4XFJJF6FTQ2X_QFuzyLroE1oomKGleYfP8/edit?usp=sharing

### Alternatives

_No response_

### Additional context

_No response_
Repository: go
Issue: reflect: verify/ensure that reflect supports the same string/[]byte/[]rune conversions as the spec/implementation
Labels: NeedsInvestigation,compiler/runtime

Follow-up on #23814.
See https://go-review.googlesource.com/c/go/+/412095/4/test/fixedbugs/issue23814.go for examples.
Repository: kubernetes
Issue: [Node Graceful Shutdown] kubelet sometimes doesn't finish kill pods before node shutdown within 30s and left the pods in running state still
Labels: kind/bug,priority/backlog,sig/node,priority/important-longterm,triage/accepted

### What happened?

In some cases, we saw that in a graceful shutdown enabled cluster, the kubelet started the shutdown for some pods, but end up not finishing it, and these pods have the same behavior without the graceful shutdown for preemption VM

```
2022-06-23 08:42:16.744 PDT
gke-dev-default-pool-XXX
I0623 15:42:16.744070    1748 nodeshutdown_manager_linux.go:316] "Shutdown manager killing pod with gracePeriod" pod="XX/client-64ccc5cc77-6jrfk" gracePeriod=15

>> Expected to have `Shutdown manager finishied killing pod` logs 

>> After the new node comes up, the pod skip the scheduling process and try to starts before the node is ready 
2022-06-23 08:44:33.989 PDT
gke-dev-default-pool-XXX
E0623 15:44:33.989839    1746 pod_workers.go:951] "Error syncing pod, skipping" err="network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized" pod="XX/client-64ccc5cc77-6jrfk" podUID=4ee81e47-0e79-42fb-a7f6-40cd8e1a47a9
```

### What did you expect to happen?

Pod set to terminated or failed status after node is shutdown 

### How can we reproduce it (as minimally and precisely as possible)?

it depends on the kubelet killing pod speed. probably could create lots of pods and have some postStop hook of these pods 

### Anything else we need to know?

_No response_

### Kubernetes version

v1.23+

### Cloud provider

GCP

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: go
Issue: encoding/pem:  Decode documentation misleading
Labels: Documentation,NeedsInvestigation

### What is the URL of the page with the issue?

https://pkg.go.dev/encoding/pem

### What is your user agent?

Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

### Screenshot

![Screenshot_from_2022-06-23_18-32-30](https://user-images.githubusercontent.com/722663/175442716-00f3d5a2-00ac-42fc-96ed-7583b07cf709.png)

### What did you do?

Used pem.Decode() as described.

### What did you expect to see?

To have it "Decode will find the next PEM formatted block (certificate, private key etc) in the input. It returns that block and the remainder of the input."

### What did you see instead?

It only found PEM formatted blocks when preceded by a newline, with no characters on the line before the "-----BEGIN" nor on the line after the end's "-----". It wasn't clear until I read the code that it was line by line with these restrictions. The docs made it sound like it looked for the PEM blocks using `bytes.Index(bytestream, "-----BEGIN")` and like (what I ended up using locally).

IMO the documentation is misleading here and should be fixed. 

Thanks!
Repository: next.js
Issue: Cannot navigate via next/link
Labels: bug,Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```
    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
    Binaries:
      Node: 16.13.2
      npm: 8.1.2
      Yarn: 1.22.19
      pnpm: 7.3.0
    Relevant packages:
      next: 12.1.6
      react: 18.2.0
      react-dom: 18.2.0
```

### What browser are you using? (if relevant)

Chrome 102.0.5005.115

### How are you deploying your application? (if relevant)

n/a

### Describe the Bug

Click on the link, unable to navigate to the specified page.

### Expected Behavior

Correctly navigate to the specified page

### Link to reproduction

https://github.com/liby/blog/tree/wip

### To Reproduce


https://user-images.githubusercontent.com/38807139/175450379-19bcb9bc-7952-4b05-8600-d60827676f85.mp4