sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Find/Replace indicates the tooltip "enter" is for both "next item" and "replace".  Actual behavior depends on which textbox has focus.
Labels: editor-find,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.81.0-insider (user setup)
Commit: 5e0c49cc9ece55017822d18720990be105412760
Date: 2023-07-24T05:33:49.823Z
Electron: 22.3.17
ElectronBuildId: 22432899
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.19045

Steps to Reproduce:

1. In ctrl-h find/replace screen, hover over tooltip for "next match" (down arrow).  Tooltip says (enter).  
2. Do the same for "replace".  Tooltip also says (enter).

Actual behavior is that whichever text-box (find or replace) is focused is what will be submitted on "enter".  This behavior is probably muscle-memory for people and so shouldn't be changed, but the tooltips are a bit misleading.  Conventionally, keyboard tooltips indicate non-modal hotkeys, not ones that relate to current focus.  There *is* a hotkey for "Next Match" which is F3.

I ran into this trying to see "oh I want to skip X and replace Y in this long list of find/replace, surely there must be hotkeys for this" and saw that "enter" was the hotkey for "Next", with no indication that it's focus-based.  In hindsight I was dumb, but it occurs to me that this is a bit of a sharp edge in the Find/Replace UI.

My personal recommendation: change the "Next Match" tooltip to mention F3 and not Enter, and possibly remove the Enter altogether from the "Replace Next" tooltip unless there's a suitable non-focus-based hotkey for it.
Repository: stable-diffusion-webui
Issue: Command line argument for setting extension directory [Feature Request]: 
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 ?

if extension directory argument is used instead of data dir, it might fix errors with some extensions.

### Proposed workflow

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


### Additional information

_No response_
Repository: rust
Issue: Codegen emits ineffective vxorps/vaddps sequences
Labels: A-LLVM,I-slow,A-codegen,O-x86_64,C-bug,I-heavy,O-x86_32

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
pub fn vae_dec_linear(latent: &[f32; 4]) -> [f32; 3] {
    let weights: [[f32; 4]; 3] = [
        [49.5210, 29.0283, -23.9673, -39.4981],
        [41.1373, 42.4951, 24.7349, -50.8279],
        [40.2919, 18.9304, 30.0236, -81.9976],
    ];
  //  let bias = [99.9368, 99.8421, 99.5384];
    let bias = [0.0, 0.0, 0.0];
    affine_transform(&weights, &bias, &latent)
}

pub fn affine_transform<
    T: Copy + std::ops::Add<Output = T> + std::ops::Mul<Output = T>,
    const IN: usize,
    const OUT: usize,
>(
    weights: &[[T; IN]; OUT],
    bias: &[T; OUT],
    vec: &[T; IN],
) -> [T; OUT] {
    std::array::from_fn(|i| (0..OUT).fold(bias[i], |acc, j| acc + vec[i] * weights[i][j]))
}
```

I expected to see this happen: Literally nothing :)

Instead, this happened: 
```asm
example::vae_dec_linear:
        mov     rax, rdi
        vmovss  xmm0, dword ptr [rsi + 8]
        vmulss  xmm1, xmm0, dword ptr [rip + .LCPI0_0]

        vxorps  xmm2, xmm2, xmm2                 ;; here
        vaddss  xmm1, xmm1, xmm2

        vmulss  xmm2, xmm0, dword ptr [rip + .LCPI0_1]
        vmulss  xmm0, xmm0, dword ptr [rip + .LCPI0_2]
        vaddss  xmm1, xmm2, xmm1
        vaddss  xmm0, xmm0, xmm1
        vmovsd  xmm1, qword ptr [rsi]
        vmulps  xmm2, xmm1, xmmword ptr [rip + .LCPI0_3]

        vxorps  xmm3, xmm3, xmm3                 ;; and here
        vaddps  xmm2, xmm2, xmm3

        vmulps  xmm3, xmm1, xmmword ptr [rip + .LCPI0_4]
        vmulps  xmm1, xmm1, xmmword ptr [rip + .LCPI0_5]
        vaddps  xmm2, xmm3, xmm2
        vaddsubps       xmm1, xmm2, xmm1
        vmovlps qword ptr [rdi], xmm1
        vmovss  dword ptr [rdi + 8], xmm0
        ret
```

Note the two `xor`/`add` sequences adding zero to `xmm1` or `xmm2`, respectively, this is with `-Copt-level=3 -C target-cpu=native`

EDIT: Oh and nevermind that the code has a bug it should be 

```rust
    std::array::from_fn(|i| (0..IN).fold(bias[i], |acc, j| acc + vec[j] * weights[i][j]))
```
Changes the second sequence to

```asm
        vxorps  xmm5, xmm5, xmm5
        vmulps  xmm2, xmm2, xmmword ptr [rip + .LCPI0_5]
        vaddps  xmm0, xmm0, xmm5
        vaddps  xmm0, xmm0, xmm2
```

, not as easy to spot, the second vaddps also looks suspicious. 

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:

All I looked at in compiler explorer, including nightly


<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: storybook
Issue: [Bug]: Every Storybook update offers the MDX migration again
Labels: bug,needs triage

### Describe the bug

Every time I update Storybook (with `npx storybook@latest upgrade`), the MDX 1 to 2 migration is offered again. I have already run this many times. It doesn't actually do anything, and this command does not find any issues with my handful of `.mdx` files:

`npx @hipster/mdx2-issue-checker`

### To Reproduce

1. Have `.mdx` files in your project.
2. Run `npx storybook@latest upgrade`
3. If offered to migrate your MDX files, do so.
4. Run `npx storybook@latest upgrade` again when there's a new version.
5. The MDX 1 to 2 migration is offered again, even though you've already done it and there's nothing to migrate.

### System

```shell
Environment Info:

  System:
    OS: macOS 13.4.1
    CPU: (12) arm64 Apple M2 Max
  Binaries:
    Node: 18.16.1 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.5.1 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 16.5.2
  npmPackages:
    @storybook/addon-a11y: ^7.1.1 => 7.1.1 
    @storybook/addon-actions: ^7.1.1 => 7.1.1 
    @storybook/addon-essentials: ^7.1.1 => 7.1.1 
    @storybook/addon-interactions: ^7.1.1 => 7.1.1 
    @storybook/addon-jest: ^7.1.1 => 7.1.1 
    @storybook/addon-links: ^7.1.1 => 7.1.1 
    @storybook/jest: ^0.1.0 => 0.1.0 
    @storybook/node-logger: ^7.1.1 => 7.1.1 
    @storybook/preset-create-react-app: ^7.1.1 => 7.1.1 
    @storybook/preset-scss: ^1.0.3 => 1.0.3 
    @storybook/react: ^7.1.1 => 7.1.1 
    @storybook/react-webpack5: ^7.1.1 => 7.1.1 
    @storybook/testing-library: ^0.2.0 => 0.2.0
```


### Additional context

_No response_
Repository: ollama
Issue: Consider Using Standard Config Format
Labels: feature request,feedback wanted

Thank you for your work, this is great and will be very helpful for the OSS community. The custom configuration file named "Modelfile" works well in the context of this project. 

I would like to discuss the possibility of using a standardized config format such as JSON5, TOML, YAML, or another similar standard. Those are battle-tested, easy to read and maintain, and have extensive tooling support. Using custom config language makes it harder for people to adapt quickly and makes it hard to build tooling support on top of it. Thoughts?
Repository: TypeScript
Issue: Tsconfig option to disable .tsx extension lookup in module resolution
Labels: Suggestion,Awaiting More Feedback

# Suggestion

Running `tsc --traceResolution` in my project I found that Typescript was looking up .tsx files for every module resolution. That's very inconvenient, first because .tsx extension serves a very specific domain, second because by elliminating hundreds or maybe thousands of (think of a really big project) unecessary stat() syscalls the build time would probably speed up a bit, or maybe considerably.

## 🔍 Search Terms

- tsx
- module resolution

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: kubernetes
Issue: Update a pod's effective request after init containers complete execution
Labels: sig/node,kind/feature,needs-triage

### What would you like to be added?

Ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/

Today, The Pod's effective request for a resource is the higher of:
- the sum of all app containers requestfor a resource
- the effective init requestfor a resource

I want to update a pod's effective request after init containers complete execution. 

### Why is this needed?

This is useful when the init container has high request but app container has low request. After init containers complete execution, it will be more accurate to show only the requests of app containers, for scheduling.

@smarterclayton raised the concern for node reboot scenario: init containers can rerun on node reboot - so steady state is fine but might be unable to accept all the load otherwise. I agree this is a valid concern. On node reboot, the pod should show the requests of init containers (if effective init request is higher). The solution needs to understand the pod lifecycle regarding init containers.

This can be related to the node admission redesign. Cross-links:
- https://github.com/kubernetes/kubernetes/issues/116484
- https://github.com/kubernetes/kubernetes/issues/104824
Repository: storybook
Issue: [Bug]: 7.1 Table of Contents active heading highlight broken
Labels: bug,good first issue,help wanted,addon: docs,sev:S4

### Describe the bug

When there are subheadings (H3) with the same name under different headings (H2), the highlighting becomes broken, and only subheadings from the first H2 group get highlighted in the TOC as you scroll through the page.

### To Reproduce

1. Create a documentation page of a similar format:

```md
## Button

### Properties

Lorem ipsum

### Slots

Lorem ipsum

### Events

Lorem ipsum

## Input

### Properties

Lorem ipsum

### Slots

Lorem ipsum

### Events

Lorem ipsum

## Tooltip

### Properties

Lorem ipsum

### Slots

Lorem ipsum

### Events

Lorem ipsum
```

2. Add to a Storybook instance and enable TOC
3. Observe TOC links becoming active, only links from the first group "Button" will be highlighted as you scroll past "Input" and "Tooltip"

### System

```shell
System:
    OS: macOS 13.4.1
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
  Binaries:
    Node: 16.18.1 - ~/Library/Caches/fnm_multishells/66230_1690247671085/bin/node
    npm: 9.7.1 - ~/Library/Caches/fnm_multishells/66230_1690247671085/bin/npm
  Browsers:
    Chrome: 115.0.5790.102
    Edge: 114.0.1823.67
    Safari: 16.5.2
  npmPackages:
    @storybook/addon-a11y: ^7.1.0 => 7.1.0 
    @storybook/addon-essentials: ^7.1.0 => 7.1.0 
    @storybook/addon-links: ^7.1.0 => 7.1.0 
    @storybook/addons: ^7.1.0 => 7.1.0
    @storybook/theming: ^7.1.0 => 7.1.0 
    @storybook/web-components: ^7.1.0 => 7.1.0 
    @storybook/web-components-webpack5: ^7.1.0 => 7.1.0
```


### Additional context

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: Out of memory when generating 2nd image
Labels: asking-for-help-with-local-system-issues

### Is there an existing issue for this?

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

### What happened?

I generated an image, then I clicked to generate another image but an "out of memory" error happened. Some commits ago I was able to generate any amount of images

### Steps to reproduce the problem

1. Generate one image and wait
2. Click to generate another image


### What should have happened?

The second image should be generated without errors

### Version or Commit where the problem happens

14cf434bc36d0ef31f31d4c6cd2bd15d7857d5c8

### What Python version are you running on ?

Python 3.10.x

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

Windows

### What device are you running WebUI on?

Nvidia GPUs (GTX 16 below)

### Cross attention optimization

xformers

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

Google Chrome

### Command Line Arguments

```Shell
--xformers --medvram --no-half --no-half-vae
```


### List of extensions

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/38295327/1ef96a8b-49fc-4758-804c-3a893e88d504)


### Console logs

```Shell
https://pastebin.com/0ZwixjyV
```


### Additional information

As I was writing this issue it looked like it stoped to give errors, but suddenly they came back
Repository: tensorflow
Issue: tf.keras.callbacks.SidecarEvaluatorModelExport doc page looks broken.
Labels: type:docs-bug,awaiting review,type:bug,TF 2.13

### Issue type

Documentation Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

2.13.0

### Custom code

No

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

The raw html tag is displayed and the display is collapsed when you access this link. https://www.tensorflow.org/api_docs/python/tf/keras/callbacks/SidecarEvaluatorModelExport

### Standalone code to reproduce the issue

```shell
Please access from your browser.If it is not reproduced, I will share my detailed environment.
```


### Relevant log output

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: when the error with generating image,the memory will not release;and next time is the same.this problem lead to the memory allocate is more and more,finally out of memory
Labels: bug-report,sdxl

### Is there an existing issue for this?

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

### What happened?

the memory not released when generating image with error

### Steps to reproduce the problem

1.generate one image which will allocate large memory,there will have a error
2. and compare the memory before generating image and after
3. the memory is allocated and not released


### What should have happened?

the memory will released whatever error with the generated

### Version or Commit where the problem happens

general problem whether add the extensions or not

### What Python version are you running on ?

None

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

_No response_

### What device are you running WebUI on?

_No response_

### Cross attention optimization

xformers

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

Google Chrome

### Command Line Arguments

```Shell
python launch.py--no-gradio-queue --listen --enable-insecure-extension-access --port 7862 --xformers --api --disable-nan-check --no-half-vae
```


### List of extensions

controlnet,Additional Networks

### Console logs

```Shell
watch -n 0.2 nvidia-smi
i use this to watch the memory
```


### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: VQ diffusion
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 ?

https://github.com/microsoft/VQ-Diffusion
Be compatible. Over.

### Proposed workflow

1. Go to https://github.com/microsoft/VQ-Diffusion
2. Read Reamme.md
3. apply to code.


### Additional information

```python
import torch
from diffusers import VQDiffusionPipeline

pipeline = VQDiffusionPipeline.from_pretrained("microsoft/vq-diffusion-ithq", torch_dtype=torch.float16, revision="fp16")
pipeline = pipeline.to("cuda")

image = pipeline("teddy bear playing in the pool").images[0]

# save image
image.save("./teddy_bear.png")
```
Repository: stable-diffusion-webui
Issue: [Bug]: CLIP interrogate not working
Labels: asking-for-help-with-local-system-issues

### Is there an existing issue for this?

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

### What happened?

hi guys pls help me i get an error when i click on interrogate clip
*** Error interrogating
    Traceback (most recent call last):
      File "C:\Users\A\Desktop\A1111\modules\interrogate.py", line 193, in interrogate
        self.load()
      File "C:\Users\A\Desktop\A1111\modules\interrogate.py", line 121, in load
        self.blip_model = self.load_blip_model()
      File "C:\Users\A\Desktop\A1111\modules\interrogate.py", line 101, in load_blip_model
        blip_model = models.blip.blip_decoder(pretrained=files[0], image_size=blip_image_eval_size, vit='base', med_config=os.path.join(paths.paths["BLIP"], "configs", "med_config.json"))
    IndexError: list index out of range

### Steps to reproduce the problem

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

### What should have happened?

sdf

### Version or Commit where the problem happens

v1.2.3

### What Python version are you running on ?

Python 3.10.x

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

Windows

### What device are you running WebUI on?

Other GPUs

### Cross attention optimization

V1

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

_No response_

### Command Line Arguments

```Shell
sdf
```


### List of extensions

sdf

### Console logs

```Shell
sdf
```


### Additional information

esdf
Repository: next.js
Issue: not-found loses context from layout on the re-occurring render
Labels: bug,linear: next

### 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
  Version: Darwin Kernel Version 21.6.0: Thu Jun  8 23:57:12 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_X86_64
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 8.6.10
Relevant Packages:
  next: 13.4.13-canary.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.6
Next.js Config:
  output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/elegant-joji-mxx7fn

### To Reproduce

1. Visit the CodeSandbox above
2. Routing to **/abc** via a `<Link />` - works
3. Routing to **/abc** in the browser explodes 💥

### Describe the Bug

To use [next-intl](https://github.com/amannn/next-intl) you are supposed to use the `<Link />` provided by `next-intl/link`. This needs a context provided by [next-intl](https://github.com/amannn/next-intl). This is done in the root layout.tsx (app/[locale]/layout.tsx). This worked fine with version 13.4.9

I tracked it down that the layout.tsx does not render on re-occurring renders - if you load the page and look at the console you can see:
```
[...not-found]/page.tsx
layout.tsx
not-found.tsx

[...not-found]/page.tsx
not-found.tsx
Error: No intl context found. Have you configured the provider?
```
On the first render the layout.tsx gets loaded perfects, on the second render the layout is skipped and therefore the context is not provided. It could be introduced by this PR https://github.com/vercel/next.js/pull/52589

### Expected Behavior

The layout.tsx should be run on every render.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-1471](https://linear.app/vercel/issue/NEXT-1471/not-found-loses-context-from-layout-on-the-re-occurring-render)</sub>
Repository: material-ui
Issue: [docs] Revise "Styled library interoperability" doc
Labels: docs

Batch revisions to https://mui.com/material-ui/guides/interoperability/

- Update the title: it's very vague as to what the doc is about
- Update the blurb: _“While you can use the Emotion-based ... you can also use the one you already  know”_ sounds like it implies you can **replace** Emotion with all the things listed here (e.g. Tailwind CSS) which isn't true
- Improve the visibility of instructions to reverse Emotion's CSS injection order: I think this should be much closer to "Installation" or "Usage". Also wondering if it's possible to restructure the doc so we don't need to repeat the instructions multiple times
Repository: pytorch
Issue: torch.jit.frontend.NotSupported when compiling stable-diffusion
Labels: oncall: jit

### 🐛 Describe the bug

```
from diffusers import UNet2DConditionModel as model

unet = model.from_pretrained("CompViz/stable-diffusion-v1-4", subfolder="unet", torchscript=True)
# torchscript=True is from troch_tensorrt bert case

unet = torch.jit.script(unet)
```
then got torch.jit.frontend.NotSupportedError: keyword-arg expansion is not supported

I use torch.jit.script to adapt torch_tensorrt(as torchtrt).ts.compile. 

Using torch.jit.trace would face Aten dtype not support error, and using torchtrt.compile would face torchtrt.expanddim error

If this bug happens causing from the mismatch between torchtrt/torch.jit and diffusers.models, is there any way to compile diffusers' model without writing the unet instead of import, or writing the engine using nvidia/tensorRT python API without torchtrt to compile it? Thanks for any possible solution!

p.s. I have already remove all assert and branch using tensor result like `assert input_shape[0]==xxx manually` in diffusers.

### Versions

docker image: nvcr.io/nvidia/pytorch:22.11-py3
platform: DGX-A100 40GB(SXM)
python packages:
    pytorch 1.13.0a0+936e930
    torch_tensorrt 1.3.0a0
    diffusers 0.19.0.dev0
other CPU/memory/... env is unrelated, if need, i would list them here

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel