sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: A code definition window like visual studio 
Labels: feature-request,editor-symbols

<!-- ⚠️⚠️ 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. -->
Hi
Can your team add a code definition window like visual studio already has.
![image](https://user-images.githubusercontent.com/56809930/201835090-9f7470d8-a4ca-4f16-974e-8cd61cdc4627.png)


I know there is already a peek window in vscode, but it is not enough, for :

1. it needs ctrl+click to call peek window
2. peek window can not be seen when user scroll screen up or down

what I am expecting is :

1. the definition window shows the symbol definition automatically when I put the cursor to the symbol (like visual studio)
3. the definition window is a independent window but not build-in control in the editor (like visual studio)
4. when I scroll down and up in the definition window, I can see the other part of codes in the file where the symbol defined.(like visual studio)
5. when I double-click anywhere in the definition window, a new editor opened to the 2nd editor group, to show the file where I clicked
6. when I click other symbol in the definition window, then window jumps to the new clicked symbol's defined location
Repository: stable-diffusion-webui
Issue: [Feature Request] Support running multiple independent upscalers on the same original image in Extras
Labels: enhancement

### Discussed in https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/4707

<div type='discussions-op-text'>

<sup>Originally posted by **PZAragon** November 14, 2022</sup>
This request is about being able to select many/all upscalers in Extras tab->Single Image and then batch-run each upscale one by one on the original image. 

This request is because the best upscaler is highly dependent on the image content, especially when upscaling to very large dimensions. This ends up being a try-and-error approach on each image. 

To clarify, the intention is not to run one upscaler on a previously upscaled image but for each upscaler to upscale the original image.
For example, having an image with 512x512 resolution, then setting 2x resize, and selecting "Lanczos", "BSRGAN", "Lollypop"  upscalers, would result in three images, each 1024x1024, and each one an upscale of the original 512x512 image using one of the selected upscalers. 
</div>
Repository: deno
Issue: Error: getaddrinfo ENOTFOUND localhost
Labels: needs investigation,node compat,node API

Tried simple deno 1.28.0 demo for Vite vanilla setup, not working.

```
$ deno --version
deno 1.28.0 (release, x86_64-apple-darwin)
v8 10.9.194.1
typescript 4.8.3
```

```
$ deno run -A npm:create-vite-extra
✔ Project name: … vite-project
✔ Select a template: › deno-vanilla

Scaffolding project in /Users/kieran/test/vite-project...

Done. Now run:

  cd vite-project
  deno task dev

$ cd vite-project
$ deno task dev
Task dev deno run -A --node-modules-dir npm:vite
error when starting dev server:
Error: getaddrinfo ENOTFOUND localhost
    at __node_internal_captureLargerStackTrace (https://deno.land/std@0.164.0/node/internal/errors.ts:113:11)
    at __node_internal_ (https://deno.land/std@0.164.0/node/internal/errors.ts:335:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (https://deno.land/std@0.164.0/node/internal/dns/promises.ts:67:17)
    at https://deno.land/std@0.164.0/node/internal_binding/cares_wrap.ts:111:9
```
Repository: PowerToys
Issue: Emoji Present
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Have the option in Power Toys to open an "ever present" emoji box.  When the Emoji box is open, it should show the Emojis with the matching words as typed from any text field on the screen.

### Scenario when this would be used?

When the Emoji Box is opened and when the user types a word, that matches an Emoji, it should show in the Emoji Box.  Then if the user wants to use that emoji, just by the click of the button over the Emoji (no key presses) and then shows next to the word - in the front or back.
Eg. User types Delivery , then it should show 🚚Delivery or Delivery🚚.
This would apply to any text field on a web page, a text editor etc.
There should also be a parameter for the Emoji position in a word.
Eg.  Set parameter third letter in the word.
Droplet, would then automatically do Dr💧plet.  
Eg. Set parameter second letter in the word
Or Delivery would change to D🚚livery.
--
The other parameter select the O's Emojis, this could be random selection making up words that have o letters.
L😍ve, G😄😄d, B🥱red etc.
--
Create Emojis Table for other words.  
Eg.
​Proof of P💸yment a📎📎ached.
** PLE🙏SE em📧il Invoice and a c©py of the Courier Waybill (if d🚚livery on your part), once proof of p💸yment is verified.

### Supporting information

_No response_
Repository: go
Issue: go/doc: example including `go-` prefixed packages not considered as playable
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

go 1.19

### Does this issue reproduce with the latest release?

Yes


### What operating system and processor architecture are you using (`go env`)?

_Playground env_

### What did you do?
See https://go.dev/play/p/SPW5ePcwU2Y

### What did you expect to see?
The three examples should be playable

### What did you see instead?
Example including `go-` prefixed packages not rendered as playable example, unless use of totally useless explicit alias
- First example for `mypkg` is playable
- Second example for `go-mypkg` is not playable
- But third example for `go-mypkg` using `mypkg` alias is playable

### Additional information
Issue might come from [there](https://github.com/golang/go/blob/362713183a8947394d2900563e711d05c9bbd67b/src/go/doc/example.go#L221), as import path contains `go-` prefix, it doesn't match the package name at runtime (where `go-` prefix is automatically removed), therefore related package is considered as unresolved, which leads to the whole example not considered playable.

One solution might be to trim `go-` prefix before [that line](https://github.com/golang/go/blob/362713183a8947394d2900563e711d05c9bbd67b/src/go/doc/example.go#L242)
Repository: pytorch
Issue: torch.distributed can't establish connection.
Labels: oncall: distributed

### 🐛 Describe the bug

I used three machines in the LAN to esbalish connection, it worked, however, when i can't esbalish connection with three machines in the WAN. I have closed the firewall and established connection by socket.

### Versions

```
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~18.04) 9.4.0
Clang version: Could not collect
CMake version: version 3.13.4
Libc version: glibc-2.9

Python version: 3.7.0 (default, Jun 28 2018, 13:15:42)  [GCC 7.2.0] (64-bit runtime)
Python platform: Linux-4.15.0-169-generic-x86_64-with-debian-buster-sid
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] numpy==1.15.1
[pip3] numpydoc==0.8.0
[conda] blas                      1.0                         mkl    defaults
[conda] mkl                       2019.0                      118    defaults
[conda] mkl-service               1.1.2            py37h90e4bf4_5    defaults
[conda] mkl_fft                   1.0.4            py37h4414c95_1    defaults
[conda] mkl_random                1.0.1            py37h4414c95_1    defaults
[conda] numpy                     1.15.1           py37h1d66e8a_0    defaults
[conda] numpy-base                1.15.1           py37h81de0dd_0    defaults
[conda] numpydoc                  0.8.0                    py37_0    defaults
```

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: flutter
Issue: [go_router] Support a history stack like in a web browser
Labels: package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

Suppose we have an app where we need to keep track of the history, and let the user go back and forth between pages he navigates to. (For example a note taking application where notes can be linked together).

In practice we would have a back/forward button somewhere in the application (behaving like the one in a web browser), and we would like to keep scroll positions / states of the pages in the history.

I wonder how to implement this with go_router.

I did the following:
- listen to navigation changes (store each path in a list)
- call GoRouter.go every time I want to go back/forth in the history

This leads to the following issues:
- page states are not preserved (scroll position)
- animation between pages are strange. (we can probably use an animation that is similar for entering / leaving the page and the problem is solved)

I considered using push / pop but it doesn't seem designed that way. (not sure what they are useful for besides dialogs that cannot be deep linked to).

I suspect this is somehow linked to https://github.com/flutter/flutter/issues/99112 for navigating the history properly and being able to store the state.

This is also probably connected to https://github.com/flutter/flutter/issues/80303 for state restoration. (which is the main issue)
Repository: flutter
Issue: Add lints test for all templates
Labels: a: tests,tool,a: first hour,c: proposal,P2,team-tool,triaged-tool

We have no test catching

* https://github.com/flutter/flutter/issues/115347

Rather than add a specific test for that, we should add a test that does it for all templates (and all lints/warnings/errors).
Repository: stable-diffusion-webui
Issue: [Feature Request]: Just request more memory when it runs on Windows
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

When memory is exhausted, Windows can increase pages file as memory.
But in the latest version of stable-diffusion-webui, when memory is exhausted, it mentions ‘RuntimeError: [enforce fail at ***] data. DefaultCPUAllocator: not enough memory: you tried to allocate *** bytes.’
I mean, stable-diffusion-webui can just request more memory, Windows will solve the rest problems.

### Proposed workflow

1. Run webui-user.bat
2. Just wait Windows increase virtual memory


### Additional information

I do not know how other system increase virtual memory, but on Windows, It's automatic.
So this Feature Request is only on Windows.
Repository: godot
Issue: VisualShader : Light Fragment - DIFFUSE_LIGHT 
Labels: enhancement,discussion,confirmed,topic:shaders,topic:3d

### Godot version

4.0 beta 04

### System information

Linux Ubuntu

### Issue description

Hello,
When generating the Shader  from a VisualScript, the **DIFFUSE_LIGHT** output of the LightShader is written as follows: 

DIFFUSE_LIGHT   **=** **** and NOT 
DIFFUSE_LIGHT **+=** **** 

![image](https://user-images.githubusercontent.com/10273261/201891568-87f120f5-5c56-449f-81ae-cafc7952a2c9.png)


Without this, the addition of several lights in the scene is not correctly calculated afterwards

 as explained in the documentation: 
[https://docs.godotengine.org/en/latest/tutorials/shaders/shader_reference/spatial_shader.html?highlight=DIFFUSE_LIGHT](url)

![image](https://user-images.githubusercontent.com/10273261/201888796-4f32c093-cb87-419f-b456-974381b02a7e.png)




### Steps to reproduce

- Create a VisualScript
- Go To Light Fragment
- Connect a node to Diffuse Output
- look at the generated Shader code

### Minimal reproduction project

_No response_
Repository: neovim
Issue: `Ctrl+L`(once) is needed to select long line (spanning multiple terminal lines) due to ctermfg/ctermbg being used for `highlight`
Labels: tui,has:workaround

### Neovim version (nvim -v)

NVIM v0.8.0

### Vim (not Nvim) behaves the same?

no, VIM - Vi IMproved 9.0

### Operating system/version

Gentoo ~amd64

### Terminal name/version

alacritty 0.12.0-dev (77855806), xfce4-terminal 1.0.4 (Xfce 4.16)

### $TERM environment variable

alacritty, xterm-256color

### Installation

system package manager: emerge

### How to reproduce the issue

0. (in bash): `$` `for i in {0..55}; do (echo;printf '#   %.0s' {1..100}); done  > /tmp/a.sh`
1. `$(which nvim) --clean -u /tmp/oneline /tmp/a.sh`
2. triple LMB(left mouse button) click on any line to select it (and auto copy it) and notice that it only selects one visible line, instead of the whole multiline which spans multiple visible lines.
3. press Ctrl+L once ie. refresh (though nothing visibly changes)
4. now try to triple LMB on any line and see that it does select the whole multiline! ie. [workaround](https://github.com/alacritty/alacritty/issues/5854#issuecomment-1314296614).

`/tmp/oneline` is:
```vimrc

" only needed for vim in alacritty:
set ttyfast

highlight Normal ctermfg=2

" to avoid holding shift for triple LMB:
set mouse=

" to can quit without frustration:
map :Q :q
map :WQ :wq
map :wQ :wq
map :Wq :wq
map :W :w
```

Without the line `highlight Normal ctermfg=2` the above step 2 acts like step 4, so there's no issue. However, you can change `ctermfg` to `ctermbg`, or `2` to `none` or even add so both `ctermfg` and `ctermbg` are present, and any combination of these variants, from what I can tell.

Misc:
If I do this instead `$` `for i in {0..55}; do (echo;printf '#   %.0s' {1..100}); done  | $(which nvim) --clean -u /tmp/oneline -- -` then it always works (always selects the entire multiline), so the problem only happens when the contents are from a file, but not when they're from stdin. Isn't it odd?


### Expected behavior

the whole line which spans multiple visible lines should be selected

![expected_screen-2022-11-15-11-08-03](https://user-images.githubusercontent.com/106607441/201892215-0acf09b6-c9cb-4c4e-bf8e-daeb409ad249.jpg)

it already works in vim(though in alacritty it needs `set ttyfast` because it's `nottyfast` [by default in it](https://github.com/vim/vim/issues/11549)):
![vim_good_screen-2022-11-15-11-08-38](https://user-images.githubusercontent.com/106607441/201892242-374d91e2-289d-4402-b377-590e92c8f9e7.jpg)


### Actual behavior

only one line of the actual multiline is selected.
![currentbad_screen-2022-11-15-11-08-15](https://user-images.githubusercontent.com/106607441/201892282-c3fc9551-898e-4303-a8a7-d1518bc9fb8c.jpg)
Repository: rust
Issue: Feed a span into the const eval queries in case of an error
Labels: A-diagnostics,T-compiler,A-const-eval

> Unfortunately we cannot do this on the query level, because then evaluating the same constant at different locations would re-evaluate the constant each time since an input changes.

We could do that by having an `Option<Span>` argument in the query key that we only set to `Some` if we are erroring. So basically invoke it once with `None`, causing no error to be emitted, but an error to be returned, if you get back an error, invoke again with `Some(span)` and now the query can error inside.

_Originally posted by @oli-obk in https://github.com/rust-lang/rust/issues/104317#issuecomment-1315057464_
Repository: PowerToys
Issue: FancyZones shortcut
Labels: Idea-Enhancement,FancyZones-Layouts,Needs-Triage

### Description of the new feature / enhancement

instead of having each layout tied to a single number, you can asign mutliple zones to a number. holding the activation keys and pressing the number either selects the last (or first if not used before) layout used that is tied to that number or begins to cycle through subsequent layouts tied to the same key.

### Scenario when this would be used?

when using multiple windows it can be tricky remembering which layout is tied to which number, but with this change you can put a single window layout on 1, two window layouts to 2, 3 windows to 3 and so on. the differences in layout for X layout can be selected by cycling through the numbers. this will not effect the normal behavior as it is still achievable even with this change.

### Supporting information

_No response_
Repository: go
Issue: archive/zip: make checksumReader implement io.WriterTo
Labels: Performance,NeedsInvestigation

We've stumbled upon a case where performance is left on the table in `io.CopyBuffer` when copying from an `archive/zip.checksumReader` to an `*os.File`:

```go
var dst *os.File // ...
var src *zip.checksumReader // ...
var buf [32 * 1024]byte
io.CopyBuffer(dst, src, buf[:])
```

In this case, profiles [1] show that `buf` is unused, and `io.CopyBuffer` ends up allocating in a child call. The allocations take up 8% of cycles in an exemplar of a fast compilation step (which uses an auxiliary Go binary featuring zip files) at our company.

We can work around this problem now that we've discovered it using the struct hack mentioned in https://github.com/golang/go/issues/16474, but this leaves performance on the table for others that copy from zip files to real files.

[1]:

![3xr6WSThD42tP6V](https://user-images.githubusercontent.com/189413/201907303-66643db0-70ef-4683-8345-8e60f40dee07.png)
Repository: pytorch
Issue: Add a `device` keyword argument to `torch.manual_seed`
Labels: triaged,module: random

### 🚀 The feature, motivation and pitch

I would argue that the default way to set seeds and to retrieve generators in PyTorch ML is to use `torch.manual_seed` which creates a generator underneath. 

So it's a common use case to do the following:

```python
import torch

generator = torch.manual_seed(0)
```

and then make use of the generator for downsteam pipelines. 

Now in many cases one would like the generator to be directly on GPU if all the computation happens on GPU and random tensors that are created along the way should then also directly be created on gpu:

```python
noise = torch.randn(shape, generator=generator, device="cuda")
```

In the above case, we would like `generator` to be on GPU, but it's currently a bit tedious to do this:

```python
generator = torch.Generator(device="cuda").manual_seed(0)
```

=> IMO a nicer API and easier to adapt API would be:

```python
generator = torch.manual_seed(0, device="cuda")
```

### Alternatives

```python
generator = torch.Generator(device="cuda").manual_seed(0)
```

### Additional context

With the rise of Diffusion Modes for generative tasks in ML making pipelines more deterministic becomes more and more important . E.g. we rely on the above functionality **a lot** in `difffusers`: https://github.com/huggingface/diffusers - a nicer API here would be great here.

cc @pbelevich
Repository: create-react-app
Issue: react-scripts 5.0.1 having vulnerable transitive libraries
Labels: needs triage,issue: bug report

We are using react-scripts 5.0.1 library, and facing some security vulnerabilities in its dependent packages.
1) nth-check v1.0.2 - vulnerable to Inefficient Regular Expression Complexity
2) loader-utils v2.0.2 - A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js 
3) minimatch v3.0.4 - A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.

These packages if upgraded to the below versions will fix the vulnerabilities:
nth-check v2.0.1
minimatch v3.0.5

Please upgrade react-scripts with transitive dependencies security patches.
Repository: PowerToys
Issue: Get space / tab data out when OCR is executed
Labels: Idea-Enhancement,Product-Text Extractor

### Description of the new feature / enhancement

it will enjoyable to get indent when copy paste code content

love from France <3

### Scenario when this would be used?

from YT for example

### Supporting information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: fourier-shaped noise IN-painting ? (mk2 inpainting)
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 ?

Initialize inpainting areas using fourier-shaper noise

### Proposed workflow

1. Go to img2img inpainting tab
2. choose an image to inpaint
3. choose a method for filling inpainting areas : 
- fill
- original
- latent noise
- latent nothing
- **fourier-shaped noise**


### Additional information

see also patch batch init [here](https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/4681)
Repository: material-ui
Issue: [Select] Misaligned dropdown
Labels: bug 🐛,component: Popover,component: select

### 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-select/#basic-select 
https://codesandbox.io/s/bug-missaligned-slect-dropdown-ubflw6?file=/demo.tsx (only changed minWidth to width)

Tested in Firefox and Edge (Chromium)

### Current behavior 😯

![grafik](https://user-images.githubusercontent.com/62615304/201939179-71c73255-67c4-4baa-b243-8e0f0b9359c1.png)
The dropdown position doesn't align with the select.

### Expected behavior 🤔

The dropdown should be aligned with the input. In the example it is a shift of 8px to the left

### Context 🔦

_No response_

### Your environment 🌎

_No response_
Repository: pytorch
Issue: Extend test_proxy_tensor tests to support ops test non floating point types
Labels: module: tests,triaged,module: ProxyTensor

### 🚀 The feature, motivation and pitch

Currently, proxy tensor tests are only run for `torch.float` dtype. This means two things:
1. Ops that don't support floating point types (e.g., `bitwise_{...}` ops, `view_as_real` etc) are completely untested
2. Op behavior is only tested for floating point types and not for other dtypes. This means that we might completely miss on some dtype specific correctness for other dtypes.

### Alternatives

_No response_

### Additional context

_No response_

cc @mruberry