sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Feature Request]: Attend-and-excite support
Labels: enhancement,extension-request

### 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 ?

https://www.reddit.com/r/StableDiffusion/comments/10qhmzp/attendandexcite_attentionbased_semantic_guidance/ is a reddit post about this technique. It is a tweak to Stable Diffusion that makes it pay more attention to parts of a prompt if those parts are not properly represented in the image, making it more capable of creating images with multiple subjects or other tricky stuff.

I have seen no issue or PR on the matter yet, so I wanted to make sure people are aware it's a thing. Also, having an issue about the matter gives eager people something to subscribe to, so they'll know what's happening.

### Proposed workflow

This could probably be done with some new syntax to indicate the tokens that need to be present, and a checkbox to enable it. I don't know whether this would be doable as an extension.

### Additional information

_No response_
Repository: ant-design
Issue: [Bug] Using Menu as the nav bar, the Item click is invalid after being folded
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/menu-antd-5-1-6-k2q950)

### Steps to reproduce

open https://codesandbox.io/s/menu-antd-5-1-6-k2q950, click the last Menu Item, it will unfold the subItem, click the subItem invalid. 

Click `A(text part)` is ok, but `B(blank part)` no use. In other words it seems no event bubbling: 
There is a `<a>` in `<span>` and the `<span>` in `<li>`, click `<li>` is ok, but no use click `<span>`
When I just set the **antd version<5.0.0, it' ok.**

![image](https://user-images.githubusercontent.com/41513919/216906117-6ce8c0d5-30c4-463b-8bac-999a37871173.png)

### What is expected?

Click the fold item jump to href

### What is actually happening?

No response click `<span>`

| Environment | Info |
| --- | --- |
| antd | 5.1.6 |
| React | 18.2.0 |
| System | Win10 |
| Browser | Chrome 108.0.5359.125 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Why can't I type in a value for Fancy Zones zone attributes?
Labels: Needs-Triage

### Description of the new feature / enhancement

The sliders are insanely inaccurate. The "space around zones" slider doesn't move in 1 pixel increments, it jumps in random numbers. -10, -6, 2. Trying to select an exact amount with the sliders is almost or actually impossible. Whenever you have a slider, there should be the option for an exact integer to be entered.

### Scenario when this would be used?

Every scenario. This is a basic design principal. Sliders are annoying and not accurate. If you are going to have sliders, have them actually be accurate.

### Supporting information

_No response_
Repository: kubernetes
Issue: Deployment with Recreate Strategy status incorrect when rolling out
Labels: kind/bug,sig/apps,lifecycle/stale,needs-triage

### What happened?

When I update a `Deployment` with `Recreate` Strategy. Its conditions remains `Complete` (when `status.observedGeneration` ==  `spec.generation`) until the older ReplicaSet finished scaled to 0.



### What did you expect to happen?

According to the doc https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#progressing-deployment, Kubernetes marks a `Deployment` as `Progressing`, when `The Deployment is scaling down its older ReplicaSet(s)`

I.E. the `Reason` field of the `Progressing` condition should not be `NewReplicaSetAvailable`

### How can we reproduce it (as minimally and precisely as possible)?

Create a simple deployment with Recreate Strategy:
```
apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
  namespace: test
spec:
  selector:
    matchLabels:
      app: myapp
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: myapp
        dummy: dummy
    spec:
      containers:
      - name: myapp
        image: nginx:1.15.8
```

Open another console to watch on the deployment:
```
kubectl -n test get deploy -o yaml -w
```

Then update the podtemplate of the deployment
```
kubectl -n test patch deploy myapp -p '{"spec": {"template": {"metadata": {"labels": {"dummy": "dummy2"}}}}}'
```


Check the output of the watch

### Anything else we need to know?

The watch output of the deployment:
[watch.log](https://github.com/kubernetes/kubernetes/files/10660721/watch.log)


And about the solution, maybe we should add a new reason like `OldReplicaSetScalingDown`

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:36:36Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.8-eks-ffeb93d", GitCommit:"abb98ec0631dfe573ec5eae40dc48fd8f2017424", GitTreeState:"clean", BuildDate:"2022-11-29T18:45:03Z", GoVersion:"go1.18.8", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>
AWS EKS
</details>


### 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: flutter
Issue: Deprecate `ColorScheme.fromSwatch`
Labels: framework,f: material design,team-design,triaged-design

This constructor carries over numerous M2 defaults, leads to issues like an inconsistent experience. We should replace with `ColorScheme.fromSeed`.

## Related issues
https://github.com/flutter/flutter/issues/91772
https://github.com/flutter/flutter/issues/112811
https://github.com/flutter/flutter/issues/86341
https://github.com/flutter/flutter/issues/90637
https://github.com/flutter/flutter/issues/127992
Repository: tauri
Issue: [bug] Iframe is not able to receive invoke callbacks
Labels: type: bug,status: needs triage

### Describe the bug

I am mounting an iframe ("child") within a Tauri app. I control both the parent and child and they both are rendered via tauri's vite build. Both the parent and the child have access to `window.__TAURI__` and related methods.

The problem is that I'm not able to `invoke` handlers from the iframe. Using `invoke` from the ifram produces the following warning in the developer console:

```
[TAURI] Couldn't find callback id 90962087 in window. This happens when the app is reloaded while Rust is running an asynchronous operation.
```

It seems that iframe `invoke` successfully registers callbacks and calls the rust handlers, which are successfully run. However, when rust tries to return the response, the callback is caught by the parent window instead of the iframe. The parent does not have the callbacks registered, hence the warning.

Is there some way to get Tauri to work with this setup? One way to go about this would be to prefix the callback handlers by frame or window?


### Reproduction

Repro:

1. Clone repo at https://github.com/gamgi/repro-tauri and enter its root.
2. Install prerequisites `npm install`
3. Start the tauri app `cargo tauri dev`
4. In parent greet box, type name and press greet (it works)
5. In child greet box, type name and press greet (it does not work)
6. Open console, see error `[TAURI] Couldn't find callback id 90962087 in window. This happens when the app is reloaded while Rust is running an asynchronous operation.`

---

Additional verifications:

7. The iframe does have tauri IPC defined, this can be verified by `document.querySelector("#root > div > iframe").contentWindow.__TAURI__`.
8. The iframe is able to call tauri, which can be verified by the "Rust backend called with ..." log from rust

### Expected behavior

I expect the child window to be able to invoke tauri handlers from the iframe and to get a response.

### Platform and versions

Environment
  › OS: Mac OS 10.15.7 X64
  › Node.js: 18.12.1
  › npm: 8.19.2
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.25.1
  › rustc: 1.66.1
  › cargo: 1.66.1
  › Rust toolchain: 1.66.1-x86_64-apple-darwin 

Packages
  › @tauri-apps/cli [NPM]: 1.2.3
  › @tauri-apps/api [NPM]: 1.2.0
  › tauri [RUST]: 1.2.4,
  › tauri-build [RUST]: 1.2.1,
  › tao [RUST]: 0.15.8,
  › wry [RUST]: 0.23.4,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:1420/
  › framework: React
  › bundler: Vite

App directory structure
  ├─ node_modules
  ├─ public
  ├─ src-tauri
  ├─ .git
  ├─ .vscode
  └─ src

### Stack trace

```shell
`[TAURI] Couldn't find callback id 90962087 in window. This happens when the app is reloaded while Rust is running an asynchronous operation.`
```


### Additional context

_No response_
Repository: PowerToys
Issue: Allow to toggle zone configuration overlay (Fancy Zones)
Labels: Needs-Triage

### Description of the new feature / enhancement

I'm using a keyboard shortcut to switch between different zone layouts. The layout changes immediately but after a few seconds (0.5 - ~2) the overlay opens that shows the new zone configuration. Unfortunately that layout is on top of everything and I can't continue to work until the overlay disappears.

I suggest to
* have a toggle to enable/disable the overlay displaying of the zone configuration when the configuration changes
* be able to set the timeout for the zone overlay to disappear (so it can be adjusted to be a lot shorter e.g.)

### Scenario when this would be used?

As already stated in the description this would help when the zone configuration is changed via a hotkey (or other means) and you don't want your work to be interrupted by the zone configuration overlay.

### Supporting information

_No response_
Repository: next.js
Issue: Bundle size of pages/_app seems to be added to api routes and edge functions.
Labels: bug

### 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: arm64
      Version: Darwin Kernel Version 21.4.0: Mon Feb 21 20:35:58 PST 2022; root:xnu-8020.101.4~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.13.0
      npm: 8.19.3
      Yarn: 3.2.2
      pnpm: N/A
    Relevant packages:
      next: 13.1.6
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://github.com/zeitgeistpm/ui/pull/546/commits/9e29c79525e65ceb570c6b61deb6a450da93e88b

### To Reproduce

- Checkout linked repo at branch `#521-og-image-generation`
- run `yarn install`
- run `yarn build`

Inspect output:
```
Route (pages)                         Size        First Load JS
┌ ● / (ISR: 600 Seconds) (562 ms)     995 B       2.7 MB
......
├ ℇ /api/og/generate                  0 B         2.7 MB <--- this cant be right?
```

**_Optionaly:_**
_Try to deploy it to vercel on a plan that has a limit of 2mb edge function size and assert that it fails to build due to:_
```
Error: The Edge Function "api/og/generate" size is 2.5 MB and your plan size limit is 2 MB. Learn More: https://vercel.link/edge-function-size
```

### Describe the Bug

When building the application, the size of the built `_app.ts` seems to be taken into consideration when estimating build size of edge functions in `pages/api` thus preventing it from deploying on vercel since the size exceeds the `2mb` limit of our current plan.

This relates to the route `pages/api/og/generate.tsx`

**Bundle analyzer:**
The analyzed output of the mentioned api route done by `@next/bundle-analyzer` is only at `396.08 KB` and my asumption is that this is a standlone executable that runs in the edge function so the _app.ts size shouldnt affect it?

![Screenshot 2023-02-06 at 10 22 59](https://user-images.githubusercontent.com/411755/216934566-e17d6027-07ab-4c33-9944-1b37906eccd6.png)


### Expected Behavior

Its expected that `_app.ts | js` bundle size shouldnt affect api routes with `edge` or `nodejs` runtimes.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Vercel
Repository: tensorflow
Issue: Remove dependency on six
Labels: stat:awaiting tensorflower,type:build/install,awaiting PR merge,TF 2.11

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Build/Install

### Have you reproduced the bug with TF nightly?

Yes

### Source

source

### Tensorflow Version

2.13.0

### Custom Code

Yes

### OS Platform and Distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

Tensorflow [relies on six](https://github.com/tensorflow/tensorflow/blob/c746206c1a377fe8f5571511a778993701d10ecc/tensorflow/tools/pip_package/setup.py#L109) as direct dependency. Since Tensorflow [requires Python >= 3.8](https://github.com/tensorflow/tensorflow/blob/c746206c1a377fe8f5571511a778993701d10ecc/tensorflow/tools/pip_package/setup.py#L357) and `six` is a Python 2 and 3 compatibility library, I'm sure it should be possible to remove this unneeded dependency and rely on Python 3 stdlib


### Standalone code to reproduce the issue

Irrelevant


### Relevant log output

_No response_</details>
Repository: material-ui
Issue: [material-ui] Autocomplete right click triggers open
Labels: bug 🐛,package: material-ui,component: autocomplete

### 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://mui.com/material-ui/react-autocomplete/

Steps:

1. Scroll to first `Autocomplete` example 
2. right click item


### Current behavior 😯

Right clicking the component renders the "opened" state of the list.

### Expected behavior 🤔

Right click doesn't trigger an "onclick" event which opens the list.

### Context 🔦

Right clicking is a native browser and OS system, which we shouldn't typically be listening to, especially on a search component.

### 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: vscode
Issue: user installed fonts not loaded after a reboot
Labels: bug,font-rendering,confirmation-pending,workbench-fonts

VS Code Version:
```
Version: 1.75.0 (user setup)
Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
Date: 2023-02-01T15:23:45.584Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
```

OS Version:
```
     Edition  Windows 11 Pro
     Version  22H2
    OS build  22621.1194
  Experience  Windows Feature Experience Pack 1000.22638.1000.0
```

Steps to Reproduce:

1. Download JetBrains Mono: https://www.jetbrains.com/lp/mono
2. Install `JetBrainsMono-Regular.ttf`
3. Install `JetBrainsMonoNL-Regular.ttf`
4. Set `"editor.fontFamily": "'JetBrains Mono'"` in settings
5. Set `"editor.fontFamily": "'JetBrains Mono NL'"` in settings

Observe that NL works and the plain one doesn't.
Repository: PowerToys
Issue: Fix windows system display settings with regards to arrangement of multiple monitors with different dpi.
Labels: Needs-Triage

### Description of the new feature / enhancement

Fix multi-display alignment (mouse-jumps) for configurations with different dpi screens. 
Currently in display settings, screen sizes seem to be derived from number of pixels, ignoring pixel density / real screen size. 
Without the correct dimensions, you cannot arrange the displays properly, and this leads to jumping mouse. 
Please, either detect screen sizes correctly, or let the user set the size for each connected display. 

### Scenario when this would be used?

Scenario is a multi-display arrangement with 2 or more screens having different pixel density. 
This is typically the case when using a notebook with internal screen and an external monitor. 

### Supporting information

_No response_
Repository: godot
Issue: Loading a scene that preloads another scene that has a shader with a uniform, causes a cryptic error
Labels: bug,topic:rendering,needs testing

### Godot version

3.5.stable

### System information

Windows 7, GLES2

### Issue description

this only happens in GLES2 not 3 and requires a specific order to occur, even though this feels like an edge case I managed to ran into it at a project of mine.

the error looks like this:
![temp](https://user-images.githubusercontent.com/69814029/216965111-923d642c-cf0d-46df-8b2e-c2d39c23c1d6.PNG)

and is triggered when one scene loads (not preload) another scene that preloads (not load) a third scene, where this third scene has a shader with a uniform variable (has to be a uniform)

### Steps to reproduce

see minimal project

### Minimal reproduction project

[Uniform issues.zip](https://github.com/godotengine/godot/files/10662730/Uniform.issues.zip)

if you wish to investigate further here is the original project where I has this issue (_ready function):

https://github.com/DissonantVoid/Godot-Sort-Visualizer/blob/master/scenes/objects/components/popups/popup_main_interface_visualizers.gd
Repository: electron
Issue: [Bug]: performance.measureUserAgentSpecificMemory causes exception
Labels: bug :beetle:,status/confirmed,has-repro-repo,22-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

22.2.0

### What operating system are you using?

Windows

### Operating System Version

Windows 10 Pro, Version 22H2, OS build 19045.2546

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

It should perform the performance.measureUserAgentSpecificMemory function without error, if crossOriginIsolated is true.


### Actual Behavior

It causes exception:
DOMException: Failed to execute 'measureUserAgentSpecificMemory' on 'Performance': performance.measureUserAgentSpecificMemory is not available.


### Testcase Gist URL

https://github.com/masa-nuc/ua-specific-memory-test

### Additional Information

_No response_
Repository: vscode
Issue: Support OpenRC in tunnel service instsall
Labels: feature-request,remote-tunnel

<!-- ⚠️⚠️ 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?: N/A

<!-- 🪓 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: `code-cli 1.75.0 (commit e2816fe719a4026ffa1ee0189dc89bdfdbafb164)`
- OS Version:

```
> cat /etc/alpine-release
3.17.0
```

Steps to Reproduce:

1. `scp` a copy of an already downloaded `linux arm64` `Code CLI` package from another host onto the target Alpine host system (see #173550)
2. Extract copied `tar.gz` (`tar xzvf code.tar.gz`)
3. `./code tunnel service install`

This produces:

```
> code tunnel service install
*
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
*
[2023-02-06 08:11:56] error error creating dbus session: I/O error: No such file or directory (os error 2)
```

I see the solution as using an appropriate `openrc` configuration file to properly run the `code tunnel` as an `openrc` service.

Even with a proper service manager though, it looked like the service that would be created utilized `systemctl`/`systemd` :-1: So that would need to be stripped out as well.
Repository: terminal
Issue: AppHost::_updateTheme is called 8x during launch
Labels: Area-Performance,Product-Terminal,Issue-Task,Priority-3

### Windows Terminal version

42e8de3

### Actual Behavior

This primarily happens due to `TerminalPage::_updateThemeColors` being called just as often. Once during `TerminalPage::Create`, but then again during `TerminalPage::WindowActivated` and `TerminalPage::_UpdatedSelectedTab` and then multiple times because the "BackgroundBrush" property changed, even though the actual color stayed constant during the entire time.
We should add one more more early returns in our event handlers, as far up the call chain as possible.