sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]: Scale by 1x in 1.7.0 does nothing on "Extras tab" and "SD Upscale" script
Labels: bug

### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

In 1.7.0 version of Webui, if I select a scale factor of 1 when processing an image on the Extras tab or in the SD upscale script on Img2img tab, then the image is processed with no changes. I don't need to resize the image, I just want to use 1x Denoise model, 1x Colorize model or 1x Texturize model or other 1x GAN models with upscale factor of 1. In 1.5.2 webui version everything worked as expected.

### Steps to reproduce the problem

1. Go to Extras tab or use "SD upscale" script on Img2img tab with denoise strength = 0.
2. Set Upscale factor of 1
3. Select any upscaler and press "Generate"
4. The image will not be changed

### What should have happened?

The image must be denoised, colorised or textured without resizing, depending on the selected upscaler model

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

_No response_

### Sysinfo

    "Platform": "Linux-5.8.0-2-amd64-x86_64-with-glibc2.31",
    "Python": "3.11.4",
    "Version": "v1.7.0",
    "Commit": "cf2772fab0af5573da775e7437e6acdca424f26e",

        "torch_version": "2.1.0",
        "is_debug_build": "False",
        "cuda_compiled_version": "11.8",
        "gcc_version": "(Debian 10.2.1-6) 10.2.1 20210110",
        "clang_version": "11.0.1-2",
        "cmake_version": "version 3.26.3",
        "os": "Debian GNU/Linux 11 (bullseye) (x86_64)",
        "libc_version": "glibc-2.31",
        "python_version": "3.11.4 (main, Sep 14 2023, 15:29:16) [GCC 10.2.1 20210110] (64-bit runtime)",
        "python_platform": "Linux-5.8.0-2-amd64-x86_64-with-glibc2.31",
        "is_cuda_available": "True",
        "cuda_runtime_version": null,
        "cuda_module_loading": "LAZY",
        "nvidia_driver_version": "545.23.06",
        "nvidia_gpu_models": "GPU 0: NVIDIA GeForce RTX 2060",

        "pip_version": "pip3",
        "pip_packages": [
            "numpy==1.23.5",
            "open-clip-torch==2.20.0",
            "pytorch-lightning==1.9.4",
            "pytorch-triton==2.1.0+9e3e10c5ed",
            "torch==2.1.0.dev20230725+cu118",
            "torchdiffeq==0.2.3",
            "torchmetrics==1.0.1",
            "torchsde==0.2.6",
            "torchvision==0.16.0.dev20230725+cu118"



### Console logs

```Shell
SD upscaling will process a total of 1 images tiled as 1x1 per upscale in a total of 1 batches.
0it [00:00, ?it/s]
```


### Additional information

_No response_
Repository: puppeteer
Issue: [Bug] Wildcard handlers for event emitters are typed incorrectly.
Labels: bug,confirmed,P3

The wildcard handler for event emitters is typed completely incorrectly. It currently assumes first parameter is an intersection of all event infos, but the first parameter actually the type of the event followed by the intersection of all event infos.
Repository: vscode
Issue: Testing #203097: Calling `Fold cell` makes screen jump down
Labels: bug,notebook-folding

Testing #203097

In the gif below I am using the following notebook https://github.com/donnemartin/data-science-ipython-notebooks/blob/master/kaggle/titanic.ipynb. 

- Focus on the header `Explore the Data` in the notebook and make sure that section is unfolded
- Scroll down so that the sticky header `Explore the Data` is visible
- From the command palette, select the action `Notebook > Fold Cell`
- The section is folded, and the screen jumps in such a way that the header is no longer visible, whereas normally it would be visible if folding were triggered through the chevron

https://github.com/microsoft/vscode/assets/61460952/f595a76d-09eb-4b46-8026-7f3aadff3263
Repository: storybook
Issue: [Bug]: when using manager.ts sidebar filters, controls don't show up
Labels: bug,addon: controls,tags,sev:S3

### Describe the bug

We use storybook for screenshot tests, and so we have a few extra stories for screenshots only that we like to hide from the sidebar. We do this using `manager.ts` with the following config:

```ts
import { addons } from '@storybook/manager-api'

addons.setConfig({
  sidebar: {
    filters: {
      hidden: (item) => !item.tags?.includes('hidden'),
    },
  },
})
```

Then we can hide a story by giving it the `'hidden'` tag.

What I'm seeing though is that as soon as I hide a story, I can't see the controls anymore on that story's page. This seems like a bug, but please let me know if it's intended behavior.

### To Reproduce

_No response_

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.2.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.17.1/bin/yarn
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
    pnpm: 7.33.6 - ~/.nvm/versions/node/v18.17.1/bin/pnpm <----- active
  Browsers:
    Chrome: 120.0.6099.234
    Edge: 120.0.2210.144
    Safari: 17.2.1
  npmPackages:
    @storybook/addon-a11y: ^7.5.3 => 7.5.3 
    @storybook/addon-actions: ^7.5.3 => 7.6.4 
    @storybook/addon-essentials: ^7.5.3 => 7.5.3 
    @storybook/addon-interactions: ^7.5.3 => 7.5.3 
    @storybook/addon-links: ^7.5.3 => 7.5.3 
    @storybook/blocks: ^7.5.3 => 7.5.3 
    @storybook/components: ^7.5.3 => 7.5.3 
    @storybook/core-events: ^7.5.3 => 7.5.3 
    @storybook/manager-api: ^7.5.3 => 7.5.3 
    @storybook/preview-api: ^7.5.3 => 7.5.3 
    @storybook/react: ^7.5.3 => 7.5.3 
    @storybook/react-vite: ^7.5.3 => 7.5.3 
    @storybook/testing-library: ^0.2.2 => 0.2.2 
    @storybook/theming: ^7.5.3 => 7.5.3 
    storybook: ^7.5.3 => 7.5.3 
    storybook-addon-a11y: ^3.1.9 => 3.1.9 
    storybook-addon-pseudo-states: ^2.1.2 => 2.1.2
```


### Additional context

_No response_
Repository: go
Issue: x/build: include all first-class ports in TryBot coverage for x repos against previous Go releases
Labels: Builders,NeedsInvestigation,FeatureRequest

### Go version

a95136a88cb8a51ede3ec2cdca4cfa3962dcfacd

### Output of `go env` in your module/workspace:

```shell
N/A
```


### What did you do?

Observe #65223.

### What did you see happen?

Test failures for the `x/sys` repo on `release-branch.go1.20` on `windows` as of https://go.dev/cl/556895, which had a `LUCI-TryBot-Result +1` vote.

### What did you expect to see?

Since https://go.dev/cl/556895 had a passing TryBot run, it should not have introduced failures on any supported release branch on any [first class port](https://go.dev/wiki/PortingPolicy#first-class-ports).
Repository: vscode
Issue: Testing #203089: Alert `Notebook Cell Completed` overriden by alert `Save`
Labels: bug,accessibility

Testing #203089

- Turn on autosave 
- Run a cell in notebook, at the end there should be an alert `Notebook Cell Completed`
- The whole alert is not read aloud, as the alert is overridden by `Save`
- I was expecting to hear all of the first alert before hearing the second alert. Perhaps the alerts could be queued?

https://github.com/microsoft/vscode/assets/61460952/8b1054ab-1d2d-4e36-b30b-40519373f431
Repository: material-ui
Issue: [joy-ui][FormControl]Select with Checkbox inside an Option wrapped in FormControl causes warning and performance issues 
Labels: on hold,package: joy-ui,component: FormControl

### Steps to reproduce

Link to live example: (required)
https://codesandbox.io/p/sandbox/thirsty-wave-q9qp54

Steps:
1. Open Console 
2. Observe FormControl error


### Current behavior

Adding a `Checkbox` to the `Option` inside a `Select` wrapped with `FormControl` causes an error stating `A FormControl can contain only one control` with a larger list of items this causes performance issues

### Expected behavior

Performance is not impacted

### Context

In my use case the design suggests that inside an option should be checkbox that shows if the item is select or not, also the list of options is 100+ items.

Wrapping the checkbox in its own `FormContol` makes the error go away and boosts the performance but its still not ideal.
Seems there is an issue regarding multiple control components inside `FormControl` but I don't see a resolution for that. 
https://github.com/mui/material-ui/issues/37764

Maybe there is particular approach that should be taken in these cases? 

### 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>


**Search keywords**: Select Checkbox Option FormControl
Repository: PowerToys
Issue: XAML STYLER as a Git-Hook
Labels: Area-GitHub workflow

### Description of the new feature / enhancement

Let's add XAML Styler as a Git Hook. I'm getting annoyed every time the Styler blocks a pr and I have to update it myself. This would eliminate all of that.

### Scenario when this would be used?

On literally every commit :)

### Supporting information

https://github.com/Xavalon/XamlStyler/wiki/Git-Hook

> [!IMPORTANT]
> Need to set `xml:space="preserve"` in elements **first**, in order to prevent the following:
> In a paragraph of text, a \<Hyperlink> or a \<Bold> will be stripped of a preceding space. By contrast, a period following a \</Hyperlink> or a \</Bold> wil be placed on a new line. This will insert a [space] in the UI.
![image](https://github.com/microsoft/WinUI-Gallery/assets/65828559/003896ff-09d0-42cc-b111-66cfec169298)

- https://github.com/Xavalon/XamlStyler/wiki/Getting-Started#whitespace
- Q&A https://github.com/Xavalon/XamlStyler/issues/454
Repository: terminal
Issue: Support for broadcasting input to tabs, not just panes
Labels: Issue-Feature,Area-Input,Product-Terminal,Needs-Tag-Fix

# Description of the new feature/enhancement

I'd like a way to broadcast keyboard input to multiple tabs at once. 

This has been asked for across multiple requests and they all get marked as a duplicate of #2634 but that only covers doing broadcasts in panes.  This is a different request and I was unable to find an open issue for this.  There are many examples of requests that are marked as duplicates of that but are asking for support for tabs, not panes.

# Proposed technical implementation details (optional)

I don't have a preference for how this is done visually, just that I'm able to broadcast to multiple tabs via some mechanism.  This can be via a new input window or (like iTerm2 does it) just sending exactly what I send in one tab to other tabs.  Ideally there would be some options for choosing which tabs to which you're broadcasting.
Repository: angular
Issue: @if(A && B) {} should be the same as @if (A) { @if(B) {}} but is not
Labels: area: core,core: content projection,core: control flow

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

@if(A && B) {} should be the same as @if (A) { @if(B) {}} but is not

I wanted to work with angular material form-field. I tried to condition mat-errors.

I wrote a first @if to test if the field is touched or not and inside several @if to test the different error cases.

expected : as usual a beautiful mat-error design

Result : the mat-error is not displayed as expected. No design for him.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/73hcig-celf3j?file=src%2Fexample%2Fform-field-error-example.html

### 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: 17.0.0
Node: 18.18.0
Package Manager: yarn 1.22.19
OS: linux x64

Angular: 17.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1700.0
@angular-devkit/build-angular      17.0.0
@angular-devkit/core               17.0.0
@angular-devkit/schematics         17.0.0
@angular/cdk                       17.1.0
@angular/localize                  17.0.8
@angular/material                  17.1.0
@angular/material-moment-adapter   17.1.0
@schematics/angular                17.0.0
rxjs                               7.4.0
typescript                         5.2.2
zone.js                            0.14.0
```


### Anything else?

In the stackblitz repo you just have to click inside both input and you will see the difference
Repository: godot
Issue: Custom resource is reset to default values after a unrelated node is freed
Labels: bug,discussion,topic:core,topic:rendering

### Tested versions

v4.2.1.stable.arch_linux, v4.3.dev2.mono.official [352434668]

### System information

Godot v4.2.1.stable unknown - Arch Linux #1 SMP PREEMPT_DYNAMIC Fri, 05 Jan 2024 16:20:41 +0000 - X11 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1060 6GB (nvidia; 545.29.06) - AMD Ryzen 5 2600X Six-Core Processor (12 Threads)

### Issue description

After calling queue_free() on a node inside the tree, a custom resource in the MRP (which the freed node contains no reference to) is reset to its default values once the node is actually freed.

I'd expect the custom resource to persist its values after freeing the unrelated node.

### Steps to reproduce

1. Open the MRP, ignore errors/warnings because I've removed most unrelated scripts/assets. The MRP should still run fine.
2. Run the project, the run process stops with an error because an array is no longer present (all values were reset to the default)
3. Comment line 13 out in the node_2d.gd script in the res:// folder.
4. This should run fine and 2 characters will be visible on the screen.

### Minimal reproduction project (MRP)

[mrp_custom_resource.zip](https://github.com/godotengine/godot/files/14027017/mrp_custom_resource.zip)
Repository: flutter
Issue: Integration Testing docs are very basic and don't cover common real-world scenarios
Labels: a: tests,framework,d: api docs,c: proposal,f: integration_test,P2,team-framework,triaged-framework

I feel like Integration Testing documentation ([link 1](https://docs.flutter.dev/cookbook/testing/integration/introduction), [link 2](https://docs.flutter.dev/testing/integration-tests)) is not good enough. It doesn't mention how limited the integration_test package is:
- unable to interact with native UI (#36024, #36024)
- no sharding on CI (#101296)
- slow iteration time (#115751)

New Flutter developers thus may think that `integration_test` "the best" of testing and that everybody does that, while in reality it's rarely the case because of the problems above.

As far as I'm aware the Flutter team doesn't have plans nor throughput to improve the `integration_test` plugin, but maybe these docs could link to other popular testing frameworks made by the community, including:
- https://github.com/leancodepl/patrol
- https://github.com/appium/appium (with [appium-flutter-driver](https://github.com/appium/appium-flutter-driver))
- https://github.com/mobile-dev-inc/maestro

along with a short description (possible also including a list of objective advantages and disadvantages).
Repository: godot
Issue: Godot Script Editor/ LSP  The action_name completionitem of  `Input.is_action*` seemes return the wrong kind. 
Labels: bug,topic:gdscript,topic:editor

### Tested versions

4.2.1-stable

### System information

Win10, Core I7-9700,RTX2080

### Issue description

![image](https://github.com/godotengine/godot/assets/1620585/cf470d02-5635-4c64-ab5a-727266ba774e)

It probably should return the lsp::CompletionItemKind::Constant or lsp::CompletionItemKind::Text according to the LSP standard.


### Steps to reproduce

needn't.

### Minimal reproduction project (MRP)

needn't.
Repository: angular
Issue: SwUpdate emits superfluous `VERSION_READY` event with `navigationRequestStrategy` set to `"freshness"`
Labels: area: service-worker

### Which @angular/* package(s) are the source of the bug?

service-worker

### Is this a regression?

No

### Description

When settings `navigationRequestStrategy` to `"freshness"` in `ngsw-config.json`, a user opening the browser will always get the newest version, which is great.

However, when closing and reopening the tab `SwUpdate.versionUpdates` will emit a `VERSION_DETECTED` event alongside a `VERSION_READY` event, despite the user being on the latest version.

This behavior leads to showing unwanted update alerts to our users and as far as I know we don't have any way to differentiate these unwanted `VERSION_READY` events from other warranted ones.



### Please provide a link to a minimal reproduction of the bug

https://github.com/Babeetlebum/angular-sw-bug

### Please provide the exception or error you saw

```true
How to reproduce:

1. pull the repo
2. `yarn build --watch`
3. run a nginx webserver with `docker-compose up --build`
4. open the app at http://localhost:4201
5. it shows version `v1.0.0`
6. close the tab (important step)
7. increment the version in `app.component.ts` to `v1.0.1`
8. open the app at http://localhost:4201 again
9. the new version is pulled (`v1.0.1`) thanks to `navigationRequestStrategy: "freshness"` but `SwUpdate` still emits a `VERSION_READY` event, thus prompting users to update to the new version
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 17.1.0
Node: 20.11.0
Package Manager: yarn 1.22.19
OS: linux x64

Angular: 17.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
... service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1701.0
@angular-devkit/build-angular   17.1.0
@angular-devkit/core            17.1.0
@angular-devkit/schematics      17.1.0
@schematics/angular             17.1.0
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.3
```


### Anything else?

_No response_
Repository: vscode
Issue: SCM - Stash viewer shows a deletion after popping the stash
Labels: git,under-discussion

Testing #203040

- Create a stash that adds 'some new text'
- "View stash", select that stash
- In the terminal, "git stash pop"
- The editor updates so that the text that was previously green on the right is now red on the left. I don't know exactly what I expect, maybe for the editor to close since the stash no longer exists. But reversing the sides of the editor is confusing, not sure how to interpret that.

<img width="809" alt="image" src="https://github.com/microsoft/vscode/assets/323878/19e4a8c0-f7b1-41ac-b28b-52397656ebb2">
Repository: storybook
Issue: [Bug]: Cannot pass callback function as Input to Angular component using Storybook
Labels: bug,has workaround,angular,argtypes

### Describe the bug

I am attempting to pass a callback function as an `Input` to Angular component from a Story.
This argument is not being passed through, Inputs of non-function types are being passed without any issue though.
Tried with latest stable and alpha releases
(Angular 17.1)

My story:
```js
export const Primary: Story = {
  args: {
    primary: true,
    label: 'Button',
    myFn: () => console.log('running'),
  },
  render: (args) => {
    console.log('Bug here => ', args, args.myFn); // args: {"primary": true,"label": "Button"}, args.myFn: undefined
    return {
      props: {
        ...args,
      },
      template: `<storybook-button ${argsToTemplate(args)}></storybook-button>`,
    };
  },
};
```

### To Reproduce

https://github.com/vneogi199/storybook-input-callback-repro/blob/main/projects/my-lib/src/stories/button.stories.ts#L23-L38

### System

```bash
System:
    OS: macOS 14.2.1
    CPU: (8) arm64 Apple M1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.21 - /opt/homebrew/bin/yarn
    npm: 10.2.4 - /opt/homebrew/bin/npm <----- active
    pnpm: 8.14.1 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 120.0.6099.234
    Safari: 17.2.1
  npmPackages:
    @storybook/addon-docs: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/addon-essentials: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/addon-interactions: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/addon-links: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/angular: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/blocks: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/test: ^8.0.0-alpha.13 => 8.0.0-alpha.13 
    storybook: ^8.0.0-alpha.13 => 8.0.0-alpha.13
```


### Additional context

_No response_
Repository: Web-Dev-For-Beginners
Issue: Test
Labels: no-issue-activity

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
Repository: vscode
Issue: Git - Add link to help topic describing Git: View Stash Command when no Stashes exist
Labels: git,polish

Testing #203040

When invoking `Git: View Stash` when there are no stashes shows an information message that there are no stashes:

![image](https://github.com/microsoft/vscode/assets/1487073/e831de97-46d3-4889-9495-0d541cfe4e2e)

Suggestion here is to create a topic under the Source Code Control node in the docs that discusses what Stashes are, and then if someone clicks on this info message take them there (or have a `Learn More About Git Stash...` link).  Perhaps a middle ground (because the git docs are not that user friendly) is to simply link to the git docs for a [stash](https://git-scm.com/docs/git-stash).