sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: vim.ui_attach: detect if a message was sent because of a redraw (with `ext_messages`)
Labels: enhancement,ui,lua,ui-extensibility

### Feature already in Vim?

_No response_

### Feature description

Whenever a `redraw` happens anywhere, the non-cleared messages will be resent.

This is problematic, if the code that handles messages, also does a redraw. Redraws in my code only happen when any queued messages have not been rendered yet and we're in some sort of blocking call.

This would effectively cause some sort of loop.

To circumvent this, I currently [wrap any redraw function](https://github.com/folke/noice.nvim/blob/dee23c21c3ff52119d8452b77814e6be75dd23bb/lua/noice/hacks.lua#L55) and when we're inside a redraw cycle, we simply ignore incoming messages.

Not sure what the best way would be to solve this for `ext_messages`.
Repository: rust
Issue: When calling a function that is actually a method, mention it
Labels: A-diagnostics,P-low,T-compiler,A-suggestion-diagnostics,D-papercut,D-newcomer-roadblock

[Given code like `cos(3.3);`](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=b5d991ca985c644458bb7ee3dab58dd3) where `cos` is a method of `f64`, we currently look for free functions elsewhere in the dependency tree:

```
error[E0425]: cannot find function `cos` in this scope
 --> src/main.rs:2:13
  |
2 |     let _ = cos(3.3);
  |             ^^^ not found in this scope
  |
help: consider importing this function
  |
1 | use libm::cos;
  |
```

But we should also check for existence of methods under that name for its sole argument.


```
error[E0425]: cannot find function `cos` in this scope
 --> src/main.rs:2:13
  |
2 |     let _ = cos(3.3);
  |             ^^^ not found in this scope
  |
help: you might have meant to call method `f64::cos`
  |
2 |     let _ = 3.3.cos();
  |             ~~~~~~~~~

```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"compiler-errors"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: stable-diffusion-webui
Issue: Add toggle for saving image input while using img2img
Labels: enhancement

We can retrieve original prompts through pnginfo which works for txt2img but this solution is incomplete for img2img 

Pnginfo does not store the img2img's image input, I do not know if its possible to store another png in pnginfo, but the alternative could be simply having option in settings to output original .png file before SD's img2img after each batch

Example:
![originalinput](https://user-images.githubusercontent.com/76458234/193296029-fd4d4abe-d868-48d8-932e-11358d03992c.png)

Right the original input,
Left the img2img output
Repository: PowerToys
Issue: Automatic sorting of windows in FancyZones
Labels: Needs-Triage

### Description of the new feature / enhancement

Using one of key combination all windows will be sorted in current setting zones. This option could be helpful to sort unorganized windows that are in desktop. Could be also helpful to attach some zones to application so e.g Teams or Outlock window will connected to some zones. If outlock or teams application will be not in correct position then using key combination windows will bo moved to correct position and rest will be set to other free zones. Multi monitor support will be very helpful here. If we can have some different settings for different connection to windows and zones that also could be helpful.

### Scenario when this would be used?

When we have not sorted/unorganized windows in our desktop and we want to sort them. This pervert situation to use multi desktop feature in win 10 and just sort our windows application with some correct order

### Supporting information

_No response_
Repository: react
Issue: [DevTools Bug]: DevTools causes hook callback behavior inconstency
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://gist.github.com/nhusher/33981014bb69318ead012c11a73eff52

### Repro steps

Either clone the gist and run with static-server, or check out [this equivalent codesandbox link](https://5lu8ks.csb.app/) (Full sandbox IDE [here](https://codesandbox.io/s/new-snowflake-5lu8ks?file=/src/index.tsx))

1. Have React devtools installed 
2. Visit the URL indicated by static-server
3. Click both increment buttons, ensuring that they work
4. Open the developer tools
5. Navigate to the DevTools Component tree and highlight `<App />`
6. Click both the increment buttons
7. Observe that the normal in-React increment button works
8. Observe that the "increment (outside react)" button no longer works

Verification of the issue:

1. Open an incognito window
2. Visit the URL indicated by static-server
3. Click the two buttons and verify that both work
4. Open the developer tools (no React Devtools available)
5. Verify the two buttons continue to work

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: vscode
Issue: Add a specific panel for TODO-style comments
Labels: feature-request,languages-diagnostics

Other editors have a panel for TODO comments to keep them out of the normal Problems view. VS Code doesn't, so some languages (including Dart) are providing them as Diagnostics.

Some users use generic TODO extensions that search across text. These might not be as accurate as those provided by a language server because they don't understand the syntax (they're also duplicating work by reading every file searching for TODOs).

Because language extensions can't rely on users having TODO extensions, they might still produce diagnostics, giving the users duplicates (in their TODO extension and in Problems).

It seems like the best solution would be for VS Code to have some native concept for TODOs. This could be new, or it could simple be a new Diagnostic type, which can be filtered out of Problems and shown in another window (this reduces the need for new APIs, adding only a new diagnostic kind).

Having a seperate pane would also allow for seperate search/filters. For example in many repositories it's common to use `TODO(myname):` as a prefix. Being able to filter to `myname` in a TODO pane (to avoid seeing other users TODOs) without also hiding all the errors/warnings would be very useful.
Repository: stable-diffusion-webui
Issue: Add option to include the seed & seed H&W resize dimensions, when sending from text2img to img2img
Labels: enhancement

I find myself having to manually get the seed, tick the extras option and then select the size used to generate the initial image. It might be a good idea to have an option to automate these steps when moving an image from text2img into img2img.
Repository: deno
Issue: spawnWithCwdIsAsync is flaky
Labels: flaky

```
spawnWithCwdIsAsync => ./cli/tests/unit/spawn_test.ts:10:6
error: AssertionError: Values are not equal:


    [Diff] Actual / Expected


-   true
+   false

  throw new AssertionError(message);
        ^
    at assertEquals (file:///Users/runner/work/deno/deno/test_util/std/testing/asserts.ts:183:9)
    at spawnWithCwdIsAsync (file:///Users/runner/work/deno/deno/cli/tests/unit/spawn_test.ts:48:5)

 FAILURES 
```

https://github.com/denoland/deno/actions/runs/3156594201/jobs/5136467870
Repository: stable-diffusion-webui
Issue: Add optional password protection to settings tab
Labels: enhancement

**Is your feature request related to a problem? Please describe.**
I have been using this webui to host stable diffusion for others while also using it myself, but I don't want anyone to be able to edit the settings.

**Describe the solution you'd like**
Add a way to password protect only the settings tab rather than the entire ui.

**Describe alternatives you've considered**
So far I've been manually editing ui.py to remove the settings tab altogether, which also prevents me from accessing it.
Repository: vscode
Issue: Storing big edit session crashed window
Labels: bug,cloud-changes

Was verifying an edit session issue, and clicked "Store edit session" in a random window. Didn't notice that there were 6k+ changes in git (i'm not really using git in that workspace). The window didn't respond to clicks then I got the Stopped Responding dialog

<img width="296" alt="image" src="https://user-images.githubusercontent.com/323878/193337561-6f59ea7c-a2fd-4185-af37-6b83a4819954.png">
Repository: material-ui
Issue: When using tooltip with tailwind html size dont update to fit leaving white space after rotate on phone
Labels: external dependency

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [x] I have tested the latest version

### Steps to reproduce 🕹

Steps:

1. using [CRA](https://create-react-app.dev/)
2. install tailwindcss postcss autoprefixer
4. install @mui/material @emotion/styled @emotion/react
5. add tooltip to anywhere


### Current behavior 😯

html size is not update leaving white space at bottom and left side

### Expected behavior 🤔

html should resize back and fit screen

### Context 🔦

screenshot from google chrome on pc same result when testing on google chrome on phone

![image](https://user-images.githubusercontent.com/69170692/193341693-8770ec5e-c7d9-4885-9eba-78de2b137c6e.png)


### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Google Chrome

  System:
    OS: Windows 10 10.0.22000
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.15.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22000.120.0), Chromium (105.0.1343.53)
  npmPackages:
    @emotion/react: ^11.10.4 => 11.10.4 
    @emotion/styled: ^11.10.4 => 11.10.4 
    @mui/base:  5.0.0-alpha.99 
    @mui/core-downloads-tracker:  5.10.7 
    @mui/material: ^5.10.7 => 5.10.7 
    @mui/private-theming:  5.10.6 
    @mui/styled-engine:  5.10.7 
    @mui/system:  5.10.7 
    @mui/types:  7.2.0
    @mui/utils:  5.10.6
    @types/react: ^18.0.0 => 18.0.21
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.4.2 => 4.8.4
```
</details>
Repository: stable-diffusion-webui
Issue: Save generation parameters to a subdirectory?
Labels: enhancement

I love having the generation parameters saved, but it would make flipping through the images (with IrfanView, which I love) faster if the parameters could be in a subdirectory.
Repository: flutter
Issue: [flutter_tools] support build-time plugins
Labels: tool,c: proposal,P3,team-tool,triaged-tool

Flutter has a defined interface for creating runtime plugins, we should also design a plugin interface that can be executed at build-time.  These plugins would live on pub.dev and runtime plugins could have have dependencies on them.

We've talked about this in the past with respect to code generation.  This proposal provides more generic hooks for Dart compilation or native compilation (linking in particular).  And proposes they present themselves as packages in pub.dev.

## Example Build-time plugins
1) **Pigeon** - The code generator for Flutter interop.  Right now you have to use it externally to generate the code, this could be integrated as a build-time plugin.
1) **Rust language support for plugins** - This could install extra project templates and when executing build it can look for the presence of "rustc" and execute rust compilation, generating a library that can be linked in during the rest of the compilation.

## Requirements
1) Provide a location and scheme where generated / downloaded files can be cached
1) Able to generate Dart code into the cache
1) Adjust Dart package resolution so generated code can be imported
1) Ability to generate native libraries in the cache
1) Ability to adjust the linker flags in the project so linker can find those libraries
1) The plugin should be sandboxed to only operate on specific inputs and outputs.  The concern being that it could overcomplicate builds and the plugins could collide with one another.

## Bonus objectives
1) Plugins can add new templates to the command-line tool
1) Plugins can add new flags to the the command-line tool

## Non-goals
1) Supporting languages with runtimes (go, c#, etc.) - The concern being a proliferation of runtime costs that collide and bog down the system.
Repository: vscode
Issue: Add a way to copy the call hierarchy
Labels: feature-request,callhierarchy

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Add another right-click context menu item to be able to copy the call hierarchy in a simple indented ASCII tree form. This information is useful to process outside of VSCode like manually searching through it in light of https://github.com/microsoft/vscode/issues/135972

My exact use case at the moment is wanting to filter to only the error/exception classes and I can do that easily do that if I can get the text out of the panel.


## Current `callhierachy` UI

<img width="474" alt="VS Code references panel call hierachy view" src="https://user-images.githubusercontent.com/558581/193359828-4db871ba-f63c-42be-ba70-0921e0e11fda.png">
Repository: rust
Issue: Exponential compile times for chained RPITIT
Labels: I-compiletime,A-impl-trait,C-bug,requires-nightly,F-impl_trait_in_assoc_type

I tried this code:

```rust
#![feature(return_position_impl_trait_in_trait)]

trait Nest: FnOnce() -> () {
    fn nest(self) -> impl Nest;
}

impl<P: FnOnce() -> ()> Nest for P {
    fn nest(self) -> impl Nest {
        || self()
    }
}

fn inner(val: &'static str) -> impl Nest {
    move || {
        val;
    }
}

fn main() {
    inner("")
        .nest().nest().nest().nest().nest()
        .nest().nest().nest().nest().nest()
        .nest().nest().nest().nest().nest()
        .nest().nest().nest().nest().nest()
        .nest().nest().nest().nest().nest();
}
```

I expected this to compile reasonably quickly.

Instead the above example took about a minute and a half. With 20 `.nest()`s in sequence, it takes between two and three seconds. For each subsequent `.nest()`, it takes about twice the time.

When I replace `|| self()` with just `self`, it compiles almost instantly. The same happens when I remove the apparently inconsequential `val;` statement, or when I use an owned type instead of a `&'static str`.

### Meta

`rustc --version --verbose`:
```
rustc 1.66.0-nightly (3f83906b3 2022-09-24)
binary: rustc
commit-hash: 3f83906b30798bf61513fa340524cebf6676f9db
commit-date: 2022-09-24
host: x86_64-unknown-linux-gnu
release: 1.66.0-nightly
LLVM version: 15.0.0
```
Repository: stable-diffusion-webui
Issue: Create grids from uncorrected as well as corrected images when face reconstruction is enabled
Labels: enhancement

I have been creating grids of images to compare different artists against different art styles. For some styles, such as photographs, face correction is very useful, but for some illustration or stylised forms the uncorrected images are better. Having grids only show corrected images when those are generated means many pictures show the inappropriate option. 

I would like two image grids to be created when face correction is enabled and uncorrected images are saved. One grid with the face corrected images and one without.

Alternatively both options could be saved in the same grid side by side, but that would be less useful for my use case. Another option is to create a grid builder application which would let the user chose which image to use for each grid square, however I expect this would be a lot more work for both the developers and the users.
Repository: go
Issue: crypto/ecdh: document, that a key-derivation function is necessary
Labels: Documentation,NeedsInvestigation

I am excited for the new package `crypto/ecdh` that will be added to go 1.20.

In the [current documentation](https://github.com/golang/go/blob/aeedb5ab13a677367be8e526cc43aeecc3734c86/src/crypto/ecdh/ecdh.go#L17) it says, that `Curve.ECHD()` returns a shared secret. Later it says, that it [performs ECDH as specified in RFC 7748, Section 6.1.](https://github.com/golang/go/blob/aeedb5ab13a677367be8e526cc43aeecc3734c86/src/crypto/ecdh/ecdh.go#L25-L26)

In [RFC 7748 in Section 6.1](https://www.rfc-editor.org/rfc/rfc7748#section-6.1) there is the sentence: 
>  Alice and Bob can then use a key-derivation function that includes K, K_A, and K_B to derive a symmetric key.

The [current code of  X25519().ECHD ](https://github.com/golang/go/blob/aeedb5ab13a677367be8e526cc43aeecc3734c86/src/crypto/ecdh/x25519.go#L77-L84) does not do the key-derivation but returns the shared secret. This is the documented behavior.

I have two questions about this:

1. Is it really necessary to use a key-derivation function or could the shared secret be used directly as a symmetric key if the algorithms has the correct key-length?
2. If it is necessary to use a key-derivation function, then it might be important to add a warning in the documentation of the package, that the returned value should not be used as a key. It is quite easy to forget the key-derivation function. In this case you have code that works, but it not secure. For example:

```golang
key, err := X25519().ECDH(privateLocalKey, publicRemoteKey)
if err != nil {
  ...
}
block, err := aes.NewCipher(key)
```
Repository: go
Issue: proposal: runtime: add AppendNewCap to return new capacity if append is used with a given number of elements
Labels: Proposal

# Motivation

I wanted to implement circular queue that can grow (i.e. is not limited to any number of elements). Such an implementation seemed to be pretty straightforward - I have a slice of elements, I remember index of the first element in the queue and circle around.

The problem comes when I need the internal slice to grow. If that was a plain array, I'd just use `append` and let the language to take care of how much the slice should grow. Unfortunately in this case it's not possible because the appended element belongs to the end of the circular buffer, not to the end of the array.

I can implement the slice growing on myself with an arbitrary constant and I will still get to `O(1)` amortized time complexity. But I'd want to be able to leverage `append` and its capacity growth algorithm. The reasoning is that the numbers standard `append` uses for slice capacity grow are fine-tuned based on real language implementation as well as knowledge of many use-cases. There is quite a big chance that the growth factor chosen by language will result in much higher performance than any factor chosen by me.

# Proposed solution

Please expose a function that would return new size of a slice after `append` of `n` elements. The signature could look like following:
```
# TODO: Find better name.
func AppendNewCap(currCap int, newElemCnt int) int
``` 
Where `currCap` would be current capacity of a slice and `newElemCnt` would be number of elements appended to the slice. this function could be then called by [growslice](https://github.com/golang/go/blob/master/src/runtime/slice.go#L155) function.

Using this method, one would be able to manually allocate the new circular buffer with appropriate capacity and manually copy all existing elements to the new slice. In other words, one could reimplement `append` with additional logic. In the queue example above, the additional logic would be the circular queue reallocation - the first element in the circular buffer would be copied to index [0] of the newly allocated slice. Such an implementation would be then as fast as library `append` but it would allow much more flexibility to the programmer.
Repository: pytorch
Issue: Functorch memory_efficient_fusion gives wrong output batch size
Labels: module: docs,triaged,module: functorch

### 🐛 Describe the bug

Run the following script:

```python
import torch

from functorch.compile import memory_efficient_fusion

import timm

x = torch.randn(5, 3, 224, 224).cuda()
y = torch.randn(6, 3, 224, 224).cuda()

net = timm.create_model('resnet50').cuda()
net = memory_efficient_fusion(net)
net.eval()

with torch.jit.fuser('fuser2'):
    xout = net(x)
    yout = net(y)

print(xout.shape, yout.shape)
```

Got:
```
torch.Size([5, 1000]) torch.Size([5, 1000])
```

Expecting:
```
torch.Size([5, 1000]) torch.Size([6, 1000])
```

Note that `yout` has the wrong batch size. Commenting out the memory_efficient_fusion (using eager mode) gives the expected result.


### Versions

Was working fine on 9/28

torch_commit: https://github.com/pytorch/pytorch/commit/614d6f19e3d30cac0d77059e738d1f25d75eb408
torchdynamo_commit: https://github.com/pytorch/torchdynamo/commit/6ead5cae0d1234aa64db06fe230ef56e12ec76fe
torchvision_commit: https://github.com/pytorch/vision/commit/a35be97a6e6725c83032315a8f5e5f6911c9ef41

First saw error on 9/29

torch_commit: https://github.com/pytorch/pytorch/commit/3cfc61b84659cea435411a546eca6a891584247f
torchdynamo_commit: https://github.com/pytorch/torchdynamo/commit/6ead5cae0d1234aa64db06fe230ef56e12ec76fe
torchvision_commit: https://github.com/pytorch/vision/commit/a35be97a6e6725c83032315a8f5e5f6911c9ef41

cc @svekars @carljparker @zou3519 @Chillee @samdow @soumith @ngimel @ptrblck
Repository: godot
Issue: macOS: Editor window cannot be dragged by the title bar, or lags considerably when dragged
Labels: bug,platform:macos,topic:porting,confirmed,regression

### Godot version

4.0.beta2

### System information

macOS 12.6 on M1 Max

### Issue description

On macOS 12.6 (Apple silicon), sometimes the editor window isn't draggable, and when it can be dragged, the window lags considerably. It can be resized at the corners and edges no problem - this only affects clicking and dragging the editor by the title bar area and affects all areas of that part of the window equally. I don't know why the window can be dragged sometimes and why it can't other times. This issue is NOT present in 4.0.beta1.

The lagging you see in the video below is **not** caused by the screen recording - this the actual lag. No other windows are affected by this issue so I have to assume it's a Godot bug.

https://user-images.githubusercontent.com/52547466/193368558-492ac09c-7e26-48f8-92ce-34cf82b6e59f.mp4

### Steps to reproduce

Open the full editor on macOS 12.6 with Apple silicon and try to drag the window around by the title bar area.
Repository: stable-diffusion-webui
Issue: Implement Training-Free Structured Diffusion Guidance for Compositional Text-to-Image Synthesis
Labels: enhancement,extension-request

**Is your feature request related to a problem? Please describe.**
Don't think this is a duplicate of anything else and shouldn't be confused with #1325. This is related to the problems showcased in these images provided by the research paper that will be linked below. Anyone who uses SD on a frequent basis should know some of these issues far too well.
![image](https://user-images.githubusercontent.com/8052832/193371042-8b944814-5cad-43d5-b0e6-f86cc84b70a0.png)


**Describe the solution you'd like**
Implementation of the changes made to txt2img.py and attention.py to reduce these problems that show up in AI image generation. Obviously this shouldn't replace the default and should be an option offered as opt-in with plenty of warning that it will produce different results than what is currently produced.

**Appropriate links to the research page, paper, and zip file that contains their modified txt2img.py and attention.py**
https://openreview.net/forum?id=PUIqjT4rzq7
https://openreview.net/pdf?id=PUIqjT4rzq7
https://openreview.net/attachment?id=PUIqjT4rzq7&name=supplementary_material