sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Tooltip controller to manipulate its visibility and such things
Labels: c: new feature,framework,f: material design,c: proposal,P3,workaround available,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

 I was working on a widget that should connect to the server to bring the Tooltip message to the client. after fetching the data I needed to show the tooltip manually because its triggerMode has been set to `.tap`.

### Proposal

I was thinking of a controller to pass into the Tooltip constructor.

Controller be like:
```dart
typedef TooltipVisibilityCallback = void Function({bool immediately});

class TooltipController extends ChangeNotifier {
  TooltipController();

  late TooltipVisibilityCallback _open;

  TooltipVisibilityCallback get open => _open;

  set open(TooltipVisibilityCallback value) {
    notifyListeners();
    _open = value;
  }
}
```

Usage:
```dart
_controller.open(immediately: true);

Tooltip(
    controller: _controller,
);
```

We have to set Controller's `open` callback on Tooltip's `initState`
```dart
    widget.controller?.open = _showTooltip;
```

If you think the idea of implementing it like I told, seems ok, then I can work on this feature and will make a PR for that.
Repository: godot
Issue: Godot 3.5.2 skeleton crashes on 64bit but not 32 bit
Labels: bug,needs testing,crash,topic:animation,topic:3d

### Godot version

3.5.2.stable

### System information

Window 10, family Intel, gles 2

### Issue description

I have a character model I made in blender that gets exported to dae/escn/gltf2/fbx. When I open it in 64 bit it crashes Godot, but on ,32 bit it opens with 1 fps. On web version it runs fine. The character has a rigitfy skeleton with a simple model.

### Steps to reproduce

Add a blender rigitfy skeleton only to Godot in 64bit in gles 2 or 32 bit

### Minimal reproduction project

No files
Repository: react-native
Issue: keyboard is closed immediately when removeClippedSubviews in ScrollView set to true
Labels: Issue: Author Provided Repro,Component: ScrollView,API: Keyboard

### Description

`removeClippedSubviews` set to `true` then the `Textinput` at the bottom (covered by the keyboard) when clicked, the keyboard will be closed immediately. I just tried it on **Android**

### React Native Version

0.71.7

### Output of `npx react-native info`

https://snack.expo.dev/@zhenguet/bugreport

### Steps to reproduce

Element "TextInput" inside "ScrollView", and when you click it at the bottom, the keyboard will automatically collapse.
'TextInput' at the top works properly

### Snack, code example, screenshot, or link to a repository

https://snack.expo.dev/@zhenguet/bugreport
Repository: kubernetes
Issue: Why do so many List requests to ApiServer in KCM have no ResourceVersion parameter
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

If the `ResourceVersion=0` parameter is added, the request will not penetrate to etcd directly. Therefore, is there any special reason that kcm needs to go to etcd to get real-time data?
Or we could actually add ResourceVersion=0 to the `metav1.ListOptions` ? 



```
 ~/go/src/xxx/xxxx/kubernetes/ [release-1.20-vke] ag '\.List\(context' pkg/controller |grep -iv lister
pkg/controller/nodeipam/ipam/cidr_allocator.go:128:             nodeList, err = kubeClient.CoreV1().Nodes().List(context.TODO(), metav1.ListOptions{
pkg/controller/namespace/deletion/namespaced_resources_deleter.go:354:  partialList, err := d.metadataClient.Resource(gvr).Namespace(namespace).List(context.TODO(), metav1.ListOptions{})
pkg/controller/namespace/deletion/namespaced_resources_deleter.go:588:  items, err := podsGetter.Pods(ns).List(context.TODO(), metav1.ListOptions{})
pkg/controller/cronjob/cronjob_controller.go:110:               return jm.kubeClient.BatchV1().Jobs(metav1.NamespaceAll).List(context.TODO(), opts)
pkg/controller/cronjob/injection.go:240:        return r.KubeClient.CoreV1().Pods(namespace).List(context.TODO(), opts)
pkg/controller/storageversiongc/gc_controller.go:160:   storageVersionList, err := c.kubeclientset.InternalV1alpha1().StorageVersions().List(context.TODO(), metav1.ListOptions{})
pkg/controller/deployment/util/deployment_util.go:549:          rsList, err := c.ReplicaSets(namespace).List(context.TODO(), options)
pkg/controller/replication/conversion.go:233:   rcList, err := c.ReplicationControllerInterface.List(context.TODO(), opts)
pkg/controller/volume/pvcprotection/pvc_protection_controller.go:280:   podsList, err := c.client.CoreV1().Pods(pvc.Namespace).List(context.TODO(), metav1.ListOptions{})
pkg/controller/testutil/test_utils.go:478:      nodes, _ := nodeHandler.List(context.TODO(), metav1.ListOptions{})
pkg/controller/podautoscaler/metrics/rest_metrics_client.go:68: metrics, err := c.client.PodMetricses(namespace).List(context.TODO(), metav1.ListOptions{LabelSelector: selector.String()})
pkg/controller/podautoscaler/metrics/legacy_metrics_client.go:121:      podList, err := h.podsGetter.Pods(namespace).List(context.TODO(), metav1.ListOptions{LabelSelector: selector.String()})
```

### Why is this needed?

we could actually add ResourceVersion=0 to the `metav1.ListOptions` ?
Repository: stable-diffusion-webui
Issue: [Feature Request]: add to load batch the abilty to auto download Python and GIT using winget on windows.
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

automate setup buy sourcing the first required programs thru Winget

### Proposed workflow

winget install --id Git.Git -e --source winget
winget install python --accept-package-agreements

### Additional information

https://learn.microsoft.com/en-us/windows/package-manager/
Repository: material-ui
Issue: [joy-ui] Automatic adjustment does not work when using it with Material UI
Labels: docs,package: material-ui,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/rough-browser-3d6rtd?file=/index.tsx

Steps:

1. Take the [example](https://codesandbox.io/s/f9jmje?file=/demo.tsx) of usage for Material Icons in [Using icon libraries](https://mui.com/joy-ui/guides/using-icon-libraries/).
2. Apply the changes described in [Using Joy UI and Material UI together](https://mui.com/joy-ui/guides/using-joy-ui-and-material-ui-together/).
3. The icons in the demo which used to auto-adjust in size in step 1, no longer auto-adjust, they are all the same size.


### Current behavior 😯

Icons appear all the same size in this example:
![Screenshot from 2023-05-15 00-10-25](https://github.com/mui/material-ui/assets/4794618/c766e578-e6cb-4b45-8942-a57f285baf65)


### Expected behavior 🤔

Icons auto-adjust their size:
![Screenshot from 2023-05-15 00-10-31](https://github.com/mui/material-ui/assets/4794618/4a9d104d-224b-4792-b952-2e0c0aac471f)


### Context 🔦

I am building a web application where I need to use components from both libraries Material UI and Joy UI, and I noticed that auto-adjustment in Joy UI doesn't work in this case, which is quite disruptive.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: Not Found
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 113.0.5672.92
    Firefox: 113.0.1
  npmPackages:
    @emotion/react:  11.10.5 
    @emotion/styled:  11.10.5 
    @mui/base:  5.0.0-beta.0 
    @mui/core-downloads-tracker:  5.13.0 
    @mui/icons-material: ^5.11.16 => 5.11.16 
    @mui/joy: ^5.0.0-alpha.79 => 5.0.0-alpha.79 
    @mui/lab: ^5.0.0-alpha.129 => 5.0.0-alpha.129 
    @mui/material: ^5.13.0 => 5.13.0 
    @mui/private-theming:  5.12.3 
    @mui/styled-engine:  5.12.3 
    @mui/system:  5.12.3 
    @mui/types:  7.2.4 
    @mui/utils:  5.12.3 
    @types/react: ^18.0.21 => 18.0.25 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^4.8.4 => 4.9.3 
```
</details>
Repository: stable-diffusion-webui
Issue: [Bug]: Segmentation fault
Labels: asking-for-help-with-local-system-issues,platform:amd

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

python launch.py 

Python 3.10.11 | packaged by conda-forge | (main, May 10 2023, 18:58:44) [GCC 11.3.0]
Version: v1.2.1
Commit hash: 89f9faa63388756314e8a1d96cf86bf5e0663045
Installing requirements
Launching Web UI with arguments: 
Segmentation fault

### Steps to reproduce the problem

1. Go to .... 
2. Press ....
3. ...


### What should have happened?

webui should proceed correctly after executing launch.py.

### Commit where the problem happens

89f9faa63388756314e8a1d96cf86bf5e0663045

### What platforms do you use to access the UI ?

_No response_

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
python launch.py
```


### List of extensions

No

### Console logs

```Shell
(webui) xxx@task-20230512150124-91891:/xxx/stable-diffusion-webui$ python launch.py 
Python 3.10.11 | packaged by conda-forge | (main, May 10 2023, 18:58:44) [GCC 11.3.0]
Version: v1.2.1
Commit hash: 89f9faa63388756314e8a1d96cf86bf5e0663045
Installing requirements
Launching Web UI with arguments: 
Segmentation fault
```


### Additional information

_No response_
Repository: next.js
Issue: app\[lang] breaks next/link with prefetch: false. Loading.tsx doesn't works with ISR
Labels: Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: 3.5.4
      pnpm: 7.24.3
    Relevant packages:
      next: 13.4.3-canary.0
      eslint-config-next: 13.2.5-canary.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Internationalization (i18n), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue

https://github.com/vercel/next.js/tree/canary/examples/app-dir-i18n-routing

### To Reproduce

1) use template from repro link, then create app\\[lang]\\publication\\[...slugs]\\page.tsx

Page.tsx
```
export const revalidate = 60;
export const dynamicParams = true;

export async function generateStaticParams() {
  return [];
}
export default async function Page() {
  return (
    <div>
      <h1>control</h1>
    </div>
  )
}
```

then in app\\[lang]\\page.tsx just use next/link with prefetch: false and href: "/en/publication/car/in/berlin".
after click on the link you will see window.reload (like php way).

2) create app\\[lang]\\publication\\[...slugs]\\loading.tsx
it doesn't works with ISR and prefetch: false

### Describe the Bug

Navigation breaks when wrapping app in [dynamicParam]

### Expected Behavior

nextjs navigation, but now like php

### Which browser are you using? (if relevant)

chrome

### How are you deploying your application? (if relevant)

localhost
Repository: rust
Issue: Collapsing two if-statements to a single if statement can result in a large performance decrease
Labels: I-slow

Apologies if this has already been reported.

---

Let's say I have some code that looks like this (this is a simplified version of some code a friend was writing):

```rust
pub fn fast(mut ret: u64) -> u64 {
    let mask = (1 << 38) - 1;

    for _ in 0..100_000 {
        let mut speed = 0.0;
        let mut z: f64 = speed;
        speed += 0.200000001;

        for _ in 2..14 {
            z += speed;

            if (z.to_bits() >> 8) & mask == 0 {
                if z % 0.0625 < 1e-13 {
                    println!("{}", z % 0.0625);
                    ret += 1;
                }
            }
        }
    }

    eprintln!("ret: {ret}");
    ret
}
```

I might be tempted to collapse the if-statement in the middle, since it shouldn't change anything - in fact, clippy will even recommend that I change it to this:

```rust
pub fn slow(mut ret: u64) -> u64 {
    let mask = (1 << 38) - 1;

    for _ in 0..100_000 {
        let mut speed = 0.0;
        let mut z: f64 = speed;
        speed += 0.200000001;

        for _ in 2..14 {
            z += speed;

            if (z.to_bits() >> 8) & mask == 0 && z % 0.0625 < 1e-13 {
                println!("{}", z % 0.0625);
                ret += 1;
            }
        }
    }

    eprintln!("ret: {ret}");
    ret
}
```

However, if I pit these two against each other using criterion, then when I run a bench (on 1.69.0):

```bash
➜ cargo bench 2> out.txt

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s


running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

slow                    time:   [7.5115 ms 7.5313 ms 7.5583 ms]
Found 4 outliers among 100 measurements (4.00%)
  2 (2.00%) high mild
  2 (2.00%) high severe

fast                    time:   [577.02 µs 578.91 µs 581.29 µs]
Found 5 outliers among 100 measurements (5.00%)
  1 (1.00%) high mild
  4 (4.00%) high severe
```

For some reason, collapsing the if branch leads to a massive performance regression! This is surprising as well since from my testing, where I set `z = 0`, the if branch should never run. Putting the two bits of code on Godbolt seems to also show that there's a bit of a difference in terms of assembly generation ([fast](https://godbolt.org/z/n969brv1b), [slow](https://godbolt.org/z/5M5fc3ae3)).

Furthermore, from some testing, commenting out either the `eprintln` or the `println` on both would result in them having similar performance.

~~I can set up a repo with my exact setup if that will be helpful.~~ Repo with code and benchmark: https://github.com/ClementTsang/collapse_if_slowdown
Repository: godot
Issue: Tileset physics layer doesn't show when using Polish editor translation
Labels: bug,enhancement,topic:editor

### Godot version

4.0.2

### System information

Windows 10

### Issue description

The issue occurs on Polish lang version, when you create in tileset new physic layer and then when you click on paint there is no physic layer shown afterwards,after long time i figured it out that on polish ver there is no default name for physic layer like in eng ver 


### Steps to reproduce

null

### Minimal reproduction project

null
Repository: material-ui
Issue: [tabs] Add min-width: '0' as default for TabPanel to help with CSS grid container
Labels: bug 🐛,component: tabs,package: lab,ready to take

### Summary 💡

Would like to have min-width: '0' as default for TabPanel so the GridDataPro layout doesn't overflow.

e.g. By using min-width: '0' with TabPanel, will fix the overflow issue with DataGridPro.

https://github.com/mui/material-ui/assets/91907117/81552937-e1e5-4b6a-8fff-ed9366782cc1


### Examples 🌈

Reproduction: https://codesandbox.io/s/data-grid-community-forked-tsywms?file=/package.json

### Motivation 🔦

**Note: Please reference these Github issues that explains the details:
 https://github.com/mui/mui-x/issues/8547#issuecomment-1544341740**
Repository: stable-diffusion-webui
Issue: [Bug]: CUDA out of memory
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Change GTX 1650 to RTX 2060 Super and got this error

### Steps to reproduce the problem

Try to generate image

### What should have happened?

It must work

### Commit where the problem happens

64fc936738d296f5eb2ff495006e298c2aeb51bf

### What platforms do you use to access the UI ?

Windows

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
--medvram --always-batch-cond-uncond
```


### List of extensions

a1111-sd-webui-locon
LDSR
Lora
ScuNET
SwinIR
prompt-bracket-checker

### Console logs

```Shell
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 3.33 GiB (GPU 0; 8.00 GiB total capacity; 1.67 GiB already allocated; 4.47 GiB free; 1.73 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
```


### Additional information

New updates on torch 2.0 didn't work consistently and i back to 64fc936738d296f5eb2ff495006e298c2aeb51bf
But after change GPU i got this error
Once after restarting the PC it worked, but the next day it didn’t
"Tried to allocate 3.33 GiB. 4.47 GiB free" What?
Repository: go
Issue: debug/pe: add Machine type with String method
Labels: OS-Windows,Proposal,Proposal-Accepted

When using the `debug/pe` package to look up information about binaries, I noticed that there's a subtle API difference compared to `debug/macho` and `debug/elf`.

For instance, in the `debug/elf` package, [`Machine` is defined](https://pkg.go.dev/debug/elf#Machine) as being able to call:

```go
f.Machine.String()
```

Whereas when using the `debug/pe` package, [`Machine` has no such definition in the `FileHeader`](https://pkg.go.dev/debug/pe#FileHeader).

It would be good to align the API of this package alongside how we do it in the other packages:

- Extract a type for `Machine`
- Add a `String()` method
- Add a `GoString()` method
Repository: storybook
Issue: [Bug]: `id` property on HTML element interpreted as Story id.
Labels: bug,needs triage

### Describe the bug

I have some `.mdx` files describing the HTML for a component. The first element has an `id`, and it is mistakenly interpreted to be referring to a story id.

### To Reproduce

https://stackblitz.com/edit/github-qwj9m6?file=src/stories/test.mdx

1. Create MDX file
2. Import Canvas, Meta from addon-docs
3. In Canvas, enter some HTML markup
4. Add an `id` to the first HTML element

There is no error produced initially, but when trying to load the page it will spin forever, failing to load.

Example:

```mdx
import { Canvas, Meta } from '@storybook/addon-docs';

<Meta title="Test Component" />

# Test Component

<Canvas>
  <div id="testComponent"></div>
</Canvas>
```

### System

```shell
Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @storybook/addon-essentials: ^7.1.0-alpha.15 => 7.1.0-alpha.17 
    @storybook/addon-interactions: ^7.1.0-alpha.15 => 7.1.0-alpha.17 
    @storybook/addon-links: ^7.1.0-alpha.15 => 7.1.0-alpha.17 
    @storybook/blocks: ^7.1.0-alpha.15 => 7.1.0-alpha.17 
    @storybook/react: ^7.1.0-alpha.15 => 7.1.0-alpha.17 
    @storybook/react-vite: ^7.1.0-alpha.15 => 7.1.0-alpha.17 
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

I tried to create a Stackblitz with HTML + Vite, but it failed on installing dependencies. Should I file that as a separate issue?
Repository: pytorch
Issue: DataParallel for nested modules
Labels: oncall: distributed

### 🐛 Describe the bug

My module is not on the same devices
`
class ImageEncoder(nn.Module):
    def __init__(self):
        super(ImageEncoder, self).__init__()
        resnet_model = torchvision.models.resnet18()
        self.model = torch.nn.Sequential(*(list(resnet_model.children())[:-1]))

    def forward(self, x):
        print('x', x.device)
        x = x.float()
        print('x.float', x.device)
        print('model', self.model[4][0].conv1.weight.device)
        output = self.model(x).squeeze(-1).squeeze(-1)
        print('output', output.device)
        return output

class VideoEncoder(nn.Module):
    def __init__(self):
        super(VideoEncoder, self).__init__()
        self.model =  ImageEncoder()

    def forward(self, x):
        x = self.model(x.flat(0,1))
        return x

class FinalModel(nn.Module):
    def __init__(self):
        supe(FinalModel, self).__init__()
        self.model = VideoEncoder()
    
    def forward(self, x):
        return self.model(x)


  def data_to_cuda(data):
      for d in data:
          if(type(data[d]) == dict):
              for p in data[d]:
                  data[d][p] = data[d][p].cuda()
          else:
              data[d] = data[d].cuda()
      return data

model = FinalModel()
model= nn.DataParallel(model, device_ids=[0,1])
model = model.cuda()

loss = torch.tensor(0.0).cuda()
losses = []

optimizer = Adam(model.parameters(), lr = 0.0001)

for data in train_data:
    data = data_to_cuda(data)
    predicted_labels = model(data)
    loss_i = compute_loss(data['labels'], predicted_labels)
    loss = loss + loss_i
      
    if(self.steps % backprop_every == 0):
        loss = loss / self.backprop_every
        loss.backward()

        optimizer.step()
        optimizer.zero_grad()
        loss = torch.tensor(0.0).cuda()

        losses.append(loss.item())  
    steps += 1
`

For this I am getting following result:

`
x cuda:0
x cuda:1
x.float cuda:1
model cuda:0
x.float cuda:0
model cuda:0
output cuda:0
return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:1 and cuda:0!

`

### Versions

pytorch                   1.10.1
gpu                         V100


cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: pytorch
Issue: problem of compilation for torch2.0
Labels: needs reproduction,module: build,triaged,module: third_party

### 🐛 Describe the bug

Hello, I want to compile torch2.0 with -D_GLIBCXX_USE_CXX11_ABI=1, However, I met some problems.
<img width="755" alt="捕获" src="https://github.com/pytorch/pytorch/assets/45058324/b9ffb0ed-e627-4a8d-a15f-1f9a9ab51bd1">
 How can I solve this? 

### Versions

cuda:11.7
driver version: 470.103.01
gcc: 10.2

cc @malfet @seemethere @ezyang @soumith @msaroufim @wconstab @ngimel @bdhirsh @anijain2305