sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: RFC: Move functorch into pytorch/pytorch
Labels: triaged

We (some folks from the functorch team, @samdow @Chillee) met with some of the PyTorch GitHub first and dev infra teams (@malfet, @osalpekar, @seemethere)  to discuss pytorch/pytorch and functorch co-development pains.

In that meeting, we identified the following solution, some stakeholders for out-of-tree (@suo) and pytorch core development (@gchanan), CI and developer velocity (@suo, @mruberry), and we are putting this issue up for discussion and to ask for sign-off from the stakeholders.

## Motivation 1: internal build failures

pytorch/pytorch and pytorch/functorch get synced internally at different cadences. Realistically this means that e.g. a deletion to a c++ function in pytorch/pytorch can cause the pytorch/functorch build to fail until it is fixed, leading to downstream failures.


## Motivation 2: co-development is difficult

functorch's CI breaks almost daily due to changes to pytorch/pytorch. There are a number of reasons for this:
- a pytorch/pytorch c++ function is deleted or signature is updated (see Motivation 1)
- a operator implementation is updated
- a developer is co-developing a feature between pytorch/pytorch and pytorch/functorch and is unable to atomically commit to both repos

## Proposal: move functorch into pytorch/pytorch

Our proposal is to "cut-and-paste" (with adjustments as necessary) functorch from pytorch/functorch into a top-level folder in pytorch/pytorch named functorch.

There are a couple of details here:
- **functorch development**: this happens inside pytorch/pytorch/functorch. There will probably be nothing left in the pytorch/functorch repo after the cut-and-paste.
- **Build and release**: functorch will still be packaged separately from pytorch/pytorch
- **CI**: pytorch/pytorch CI will run both pytorch/pytorch and functorch tests. *Developers are responsible for ensuring that both pass*

Why did we choose this? Our eventual plan is to upstream and integrate functorch into pytorch/pytorch. We believe functorch's {transforms, compilation} pieces should be a core part of pytorch/pytorch. Integration is a much larger project and we're looking for a quick stop-gap solution for  the co-development pains, so moving functorch into pytorch/pytorch is a first step towards integration.

## Impact on pytorch/pytorch developers

- **test-cost increase**. functorch build+test takes 1hr on CUDA. If we add new "functorch build+test" jobs to pytorch/pytorch CI, then we'll end up using more resources, but these can be run in parallel to pytorch/pytorch tests.
- **dev-x**. pytorch/pytorch developers are responsible for making sure all functorch build+tests pass. Realistically what this will look like is that if something fails and the developer needs help, then the should loop in someone from functorch and we will assist.

cc-ing some more folks: @vfdev-5, @kshitij12345, @ezyang, @bdhirsh
Repository: create-react-app
Issue: react-scripts start bug: Class extends value undefined is not a constructor or null
Labels: needs triage,issue: bug report

### Describe the bug

It seems like the build process changed and now throws an error where there previously wasn't one. In `react-scripts` version `4.0.3` everything works just fine, whereas in version `5.0.1` I get the error `Class extends value undefined is not a constructor or null`.

### Did you try recovering your dependencies?

Yes, I tried multiple setups and multiple repos. The error does not seem to be npm-version dependent. 
npm: 8.1.2

### Which terms did you search for in User Guide?

webpack, require, setup

### Environment

Environment Info:

  current version of create-react-app: 5.0.1
  running from C:\Users\main\AppData\Local\npm-cache\_npx\c67e74de0542c87c\node_modules\create-react-app

  System:
    OS: Windows 10 10.0.19044
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.13.1 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.1.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.53)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    react: 18.0.0 => 18.0.0
    react-dom: 18.0.0 => 18.0.0
    react-scripts: 5.0.1 => 4.0.3
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

[my example repo](https://github.com/MajorMeerkatThe3rd/react-viewer)
1. Go to the repository that I just created for this. 
2. Try `npm start` with the version `4.0.3` and version `5.0.1`. For `5.0.1` you will get the mentioned error in the console. 
3. For `4.0.3` everything works as expected.

### Expected behavior

no error

### Actual behavior

an error

### Reproducible demo

see Steps to reproduce
Repository: go
Issue: x/crypto/acme: not possible to remove contact information
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/mateusz/go/bin"
GOCACHE="/home/mateusz/.cache/go-build"
GOENV="/home/mateusz/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/mateusz/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/mateusz/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.18.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
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-build947326088=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?
```
c := &acme.Client{
	DirectoryURL: "https://acme-staging-v02.api.letsencrypt.org/directory",
	Key:          key,
}
c.UpdateReg(ctx, &acme.Account{
	Contact: nil,
})
```

### What did you expect to see?
Contact information removed


### What did you see instead?
Contact information didn't change
```
c := &acme.Client{
	DirectoryURL: "https://acme-staging-v02.api.letsencrypt.org/directory",
	Key:          key,
}
acct, _ := c.GetReg(ctx, "")
fmt.Println(acct.Contact) // ["mailto:email@gmail.com"]
```
Repository: flutter
Issue: Proposal: add selectionHeightStyle and selectionWidthStyle to TextSelectionThemeData
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Use case

In order to get consistent text selection behavior with regards to the heights and widths of the selection boxes, it seems like one has to override the [`selectionHeightStyle`](https://api.flutter.dev/flutter/material/TextField/selectionHeightStyle.html) and [`selectionWidthStyle`](https://api.flutter.dev/flutter/material/TextField/selectionWidthStyle.html) properties of `TextField` and `SelectableText` widgets manually for every such widget. `TextFormField` is actually missing these properties, which I guess is a bug.

## Proposal

I suggest to add these properties to the [`TextSelectionThemeData`](https://api.flutter.dev/flutter/material/TextSelectionThemeData-class.html) class (or a seperate `ThemeData` class if this one is unsuitable for some reason), and to have `TextField`, `SelectableText` and `TextFormField` inherit the values from such a theme.
Repository: godot
Issue: Boot Image inconsistent settings from android 12+
Labels: bug,platform:android,topic:porting

### Godot version

3.5

### System information

Android 12, GLES3, Samsung Galaxy S10+, Android SDK 31 (also tested on multiple virtual devices from android studio)

### Issue description

On every version before the image set in the project settings->Application->BootSplash is used (standard godot if no image is set)
But from Android 12 onward this setting is getting overwritten by the icon-images set in the export preset for android.

This should probably be consistently either one or the other option, but not both sometimes. Atleast if that is possible and not an issue with android itself ...

### Steps to reproduce

Make project, set icon/boot images and export to android 12+ or older to see the diffrences.

### Minimal reproduction project

_No response_
Repository: material-ui
Issue: Move `Container` gutter (padding) to theme
Labels: new feature,component: Container

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

I would like to see `Container` get its left and right padding—or "gutter width"—from a new value in the base theme.

This would offer two benefits:

- You could set a custom responsive page gutter width in your theme, and still use the `disableGutters` property on `Container`. This current incompatibility between `theme.components.MuiContainer.styleOverrides` and `Container.disableGutters` is a known issue (#30825).
- Other components could use the page gutter width too. For example, we have a carousel component that uses the page gutter to show previous/next navigation buttons; other components could also start to use the page gutter in creative ways.

### Examples 🌈

_No response_

### Motivation 🔦

_No response_
Repository: react
Issue: [DevTools Bug]: Overlapping flamecharts in Profiler
Labels: Type: Bug,Component: Developer Tools

### Website or app

https://github.com/reactjs/reactjs.org

### Repro steps

1. Check out https://github.com/reactjs/reactjs.org/commit/9cee632619065ade1e84c0470900e3634661d0d2
2. Open the beta website (https://github.com/reactjs/reactjs.org/tree/main/beta), `yarn dev`
3. Use Profiler -> "refresh and profile"

Some (but not all) commits appear a bit borked.

<img width="825" alt="Screenshot 2022-05-23 at 19 41 25" src="https://user-images.githubusercontent.com/810438/169885681-95c41ea1-b5fd-4b19-a850-f90bc725f9ce.png">


<img width="795" alt="Screenshot 2022-05-23 at 19 41 20" src="https://user-images.githubusercontent.com/810438/169885677-dcf922d9-70f6-40df-84bf-a940ac5c5c7e.png">
  

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: flutter
Issue: `CustomScrollView` applies overscroll effect on `SliverAppBar`
Labels: framework,f: material design,f: scrolling,d: api docs,d: examples,P2,team-design,triaged-design

Part of #104363.

When using the new variants SliverAppBar.medium and SliverAppBar.large in a CustomScrollView, scrolling in that CustomScrollView applies the overscroll effect on the SliverAppBar itself. This behavior should not be occuring.

**Expected result:**
- Scrolling through the CustomScrollView shows the overscroll effect only on the SliverList, not on the entire CustomScrollView.

**Actual result:**
- Scrolling through the CustomScrollView shows the overscroll effect on the SliverAppBar too, resulting in strange behavior.

https://user-images.githubusercontent.com/47219753/169891236-aeb82b09-fad6-427e-ad67-a0ff620d0708.mp4

<details>
<summary>Code sample:</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const TestApp());
}

class TestApp extends StatelessWidget {
  const TestApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.from(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.blue),
        useMaterial3: true,
      ),
      home: Scaffold(
        body: CustomScrollView(
          slivers: [
            SliverAppBar.large(
              title: const Text('Example App'),
            ),
            SliverList(
              delegate: SliverChildBuilderDelegate(
                (context, index) {
                  return ListTile(
                    title: Text('Item ${index.toString()}'),
                  );
                },
                childCount: 20,
              ),
            )
          ],
        ),
      ),
    );
  }
}
```
</details>

**However,** when the CustomScrollView scrollBehavior is set to CupertinoScrollBehavior, this issue does not occur.

https://user-images.githubusercontent.com/47219753/169891401-34de715b-caf7-4147-aec8-6483976f89b2.mp4

<details>
<summary>Code sample:</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const TestApp());
}

class TestApp extends StatelessWidget {
  const TestApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      theme: ThemeData.from(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.blue),
        useMaterial3: true,
      ),
      home: Scaffold(
        body: CustomScrollView(
          scrollBehavior: const CupertinoScrollBehavior(),
          slivers: [
            SliverAppBar.large(
              title: const Text('Example App'),
            ),
            SliverList(
              delegate: SliverChildBuilderDelegate(
                (context, index) {
                  return ListTile(
                    title: Text('Item ${index.toString()}'),
                  );
                },
                childCount: 20,
              ),
            )
          ],
        ),
      ),
    );
  }
}
```
</details>
Repository: vscode
Issue: Debug Cell option disappears 
Labels: bug,notebook-debugging

## Environment data

-   VS Code version: XXX
-   Jupyter Extension version (available under the Extensions sidebar): v2022.4.1021342353
-   Python Extension version (available under the Extensions sidebar): v2022.6.2
-   OS (Windows | Mac | Linux distro) and version: Windows 
-   Python and/or Anaconda version: Python 3.8.8
-   Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
-   Jupyter server running: Local | Remote | N/A: Local and Remote

## Expected behavior

A small drop down arrow next to the run cell, which shows a debug cell option:
![image](https://user-images.githubusercontent.com/54779308/169826876-cadd85c9-56d6-45f8-95ab-5f560626955c.png)

## Actual behavior

The drop down arrow disappears after a single debug run, and using the `ctrl + shift + alt + enter` to key combo to debug the cell is also unresponsive. Sometimes it comes back in a few minutes of waiting and sometimes I have to restart VS Code. 

![image](https://user-images.githubusercontent.com/54779308/169826720-012aac61-d924-4e5e-ae68-daf92693e420.png)

## Steps to reproduce:
1. Start a notebook
2. Debug a cell 
3. The down arrow disappears. 

## Logs

<details>

<summary>Output for <code>Jupyter</code> in the <code>Output</code> panel (<code>View</code>→<code>Output</code>, change the drop-down the upper-right of the <code>Output</code> panel to <code>Jupyter</code>)
</summary>

<p>

```
XXX
```

</p>
</details>
Repository: pytorch
Issue: Segfault in bincount
Labels: triaged,module: edge cases

### 🐛 Describe the bug

Function `torch.bincount` contains segmentation fault.

### Example to reproduce

```
import torch

self = torch.full([3], 2550, dtype=torch.int64, requires_grad=False)
weights = torch.full([3, 1, 3, 0, 0, 0, 1, 1], -4620, dtype=torch.int64, requires_grad=False)
minlength = 9711
torch.bincount(self, weights, minlength)
```

### Result

Segmentation fault

### Expected Behavior

Throwing a Python Exception

### Notes

This bug was discovered using [Atheris](https://github.com/google/atheris).


### Versions

Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: Debian GNU/Linux 11 (bullseye) (x86_64)
GCC version: (Debian 10.2.1-6) 10.2.1 20210110
Clang version: 11.0.1-2
CMake version: version 3.18.4
Libc version: glibc-2.31
Python version: 3.9.7 (default, Sep 16 2021, 13:09:58)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.10.0-11-amd64-x86_64-with-glibc2.31
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch==1.11.0
[pip3] torchaudio==0.11.0
[pip3] torchvision==0.12.0
[conda] blas                      1.0                         mkl
[conda] cpuonly                   2.0                           0    pytorch
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640
[conda] mkl-service               2.4.0            py39h7f8727e_0
[conda] mkl_fft                   1.3.1            py39hd3c417c_0
[conda] mkl_random                1.2.2            py39h51133e4_0
[conda] numpy                     1.21.2           py39h20f2e39_0
[conda] numpy-base                1.21.2           py39h79a1101_0
[conda] pytorch                   1.11.0              py3.9_cpu_0    pytorch
[conda] pytorch-mutex             1.0                         cpu    pytorch
[conda] torchaudio                0.11.0                 py39_cpu    pytorch
[conda] torchvision               0.12.0                 py39_cpu    pytorch
Repository: pytorch
Issue: Segfault in grid_sampler_3d
Labels: triaged,module: edge cases

### 🐛 Describe the bug


Function `torch.grid_sampler_3d` contains segmentation fault.

### Example to reproduce

```
import torch

input = torch.full([4, 2, 0, 0, 4, 0, 0, 3], -1480, dtype=torch.float64, requires_grad=False)
grid = torch.full([1, 6, 3, 5, 3, 4, 0, 6], -2024, dtype=torch.float64, requires_grad=False)
interpolation_mode = -3278
padding_mode = -1469
align_corners = True
torch.grid_sampler_3d(input, grid, interpolation_mode, padding_mode, align_corners)
```

### Result

Segmentation fault

### Expected Behavior

Throwing a Python Exception

### Notes

This bug was discovered using [Atheris](https://github.com/google/atheris).

### Versions

Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: Debian GNU/Linux 11 (bullseye) (x86_64)
GCC version: (Debian 10.2.1-6) 10.2.1 20210110
Clang version: 11.0.1-2
CMake version: version 3.18.4
Libc version: glibc-2.31
Python version: 3.9.7 (default, Sep 16 2021, 13:09:58)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.10.0-11-amd64-x86_64-with-glibc2.31
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch==1.11.0
[pip3] torchaudio==0.11.0
[pip3] torchvision==0.12.0
[conda] blas                      1.0                         mkl
[conda] cpuonly                   2.0                           0    pytorch
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640
[conda] mkl-service               2.4.0            py39h7f8727e_0
[conda] mkl_fft                   1.3.1            py39hd3c417c_0
[conda] mkl_random                1.2.2            py39h51133e4_0
[conda] numpy                     1.21.2           py39h20f2e39_0
[conda] numpy-base                1.21.2           py39h79a1101_0
[conda] pytorch                   1.11.0              py3.9_cpu_0    pytorch
[conda] pytorch-mutex             1.0                         cpu    pytorch
[conda] torchaudio                0.11.0                 py39_cpu    pytorch
[conda] torchvision               0.12.0                 py39_cpu    pytorch
Repository: pytorch
Issue: Segfault in max_unpool3d
Labels: triaged,module: edge cases

### 🐛 Describe the bug


Function `torch.max_unpool3d` contains segmentation fault.

### Example to reproduce

```
import torch

tensor_0 = torch.full([], -10000, dtype=torch.int64, requires_grad=False)
tensor_1 = torch.full([7, 7, 7, 4, 4, 4, 7, 7], -8695, dtype=torch.float16, requires_grad=False)
intarrayref_2 = []
intarrayref_3 = 7052
intarrayref_4 = -9995
torch._C._nn.max_unpool3d(tensor_0, tensor_1, intarrayref_2, intarrayref_3, intarrayref_4)
```

### Result

Segmentation fault

### Expected Behavior

Throwing a Python Exception

### Notes

This bug was discovered using [Atheris](https://github.com/google/atheris).

### Versions

Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: Debian GNU/Linux 11 (bullseye) (x86_64)
GCC version: (Debian 10.2.1-6) 10.2.1 20210110
Clang version: 11.0.1-2
CMake version: version 3.18.4
Libc version: glibc-2.31
Python version: 3.9.7 (default, Sep 16 2021, 13:09:58)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.10.0-11-amd64-x86_64-with-glibc2.31
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch==1.11.0
[pip3] torchaudio==0.11.0
[pip3] torchvision==0.12.0
[conda] blas                      1.0                         mkl
[conda] cpuonly                   2.0                           0    pytorch
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640
[conda] mkl-service               2.4.0            py39h7f8727e_0
[conda] mkl_fft                   1.3.1            py39hd3c417c_0
[conda] mkl_random                1.2.2            py39h51133e4_0
[conda] numpy                     1.21.2           py39h20f2e39_0
[conda] numpy-base                1.21.2           py39h79a1101_0
[conda] pytorch                   1.11.0              py3.9_cpu_0    pytorch
[conda] pytorch-mutex             1.0                         cpu    pytorch
[conda] torchaudio                0.11.0                 py39_cpu    pytorch
[conda] torchvision               0.12.0                 py39_cpu    pytorch