sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: [v7] `@storybook/vue3` setup is called twice when used with vue-router
Labels: bug,needs triage

### Describe the bug

When using the `setup` function provided by `@storybook/vue3` and creating a router using `vue-router` the callback is called twice, resulting in warnings in the console:

![image](https://user-images.githubusercontent.com/5918348/211833155-664314bf-15a9-4017-adf5-a88bc06ce469.png)


### To Reproduce

```shell
Reproduction repo: https://github.com/samturrell/storybook-7-vue-router-rerender

Run `yarn storybook`
Visit the `Test` story
Observe the browser console warnings
```


### System

```shell
Environment Info:

  System:
    OS: macOS 13.0
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
    Firefox: 100.0
    Safari: 16.1
  npmPackages:
    @storybook/addon-essentials: ^7.0.0-beta.24 => 7.0.0-beta.24
    @storybook/addon-interactions: ^7.0.0-beta.24 => 7.0.0-beta.24
    @storybook/addon-links: ^7.0.0-beta.24 => 7.0.0-beta.24
    @storybook/blocks: ^7.0.0-beta.24 => 7.0.0-beta.24
    @storybook/builder-vite: ^7.0.0-beta.24 => 7.0.0-beta.24
    @storybook/testing-library: ^0.0.13 => 0.0.13
    @storybook/vue3: ^7.0.0-beta.24 => 7.0.0-beta.24
    @storybook/vue3-vite: ^7.0.0-beta.24 => 7.0.0-beta.24
```


### Additional context

_No response_
Repository: storybook
Issue: [Feature Request]: [v7] Allow multiple calls to `@storybook/vue3` `setup` function
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

My `preview.js` is split into multiple files so that logic is contained in its own areas, for example i have `components.js`, `directives.js` and `router.js` that are responsible for setting up different things. In Vue 2 I could pull in Vue here and call `Vue.component()` etc directly, and in vue3 on previous storybook versions i could call `app.component();` etc.

With Storybook 7, the `app` is now available as a callback to `setup`, however this function can only be called once, and additional calls will overwrite the single stored callback.

### Describe the solution you'd like

The ability to call `setup` multiple times and have the callbacks batched.

### Describe alternatives you've considered

I have implemented this in userland using the following code:

```
// vue-app.js

import { setup as vueSetup } from '@storybook/vue3';

const setupFunctions = [];

/**
 * The `setup` callback from `@storybook/vue3` can only be
 * called once, so we'll batch the calls here and then
 * call them together using our own `setup` function.
 *
 * @param {Function} callback
 */
export const vueApp = (callback) => {
    setupFunctions.push(callback);
};

/**
 * Run all batched setup functions.
 */
export const setup = () => {
    vueSetup((app) => {
        setupFunctions
            .filter(({ ran }) => !ran)
            .forEach((callback) => {
                callback(app);
            });
    });
};
```

```
// preview.js

import { setup } from './vue-app';

setup();
```

However it would be nice if this was a native feature

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: opencv
Issue: OpenCV cannot import ONNX model: inputs.size() in function 'cv::dnn::dnn4_v20221220::Layer::getMemoryShapes'
Labels: bug,duplicate,category: dnn (onnx)

### System Information

OpenCV => Python opencv-python-rolling-4.7.0.68
Operating System / Platform Windows 10 64 bit
Python =>3.10.4

### Detailed description

I converted two FastSeg models from Pytorch to ONNX and simplified the models. OpenCV cannot load the either the original models. Failing with the following messages:

```
[ERROR:0@0.124] global onnx_importer.cpp:1054 cv::dnn::dnn4_v20221220::ONNXImporter::handleNode DNN/ONNX: ERROR during processing node with 1 inputs and 1 outputs: [Neg]:(onnx_node!Neg_65) from domain='ai.onnx'
Traceback (most recent call last):
  File "d:\Local\devel\Python\OpenCV\dnn_segmentation_fastseg\inference.py", line 143, in <module>
    model = cv2.dnn.readNet(model_path)
cv2.error: OpenCV(4.7.0-dev) D:\a\opencv-python\opencv-python\opencv\modules\dnn\src\onnx\onnx_importer.cpp:1073: error: (-2:Unspecified error) in function 'cv::dnn::dnn4_v20221220::ONNXImporter::handleNode'
> Node [Neg@ai.onnx]:(onnx_node!Neg_65) parse error: OpenCV(4.7.0-dev) D:\a\opencv-python\opencv-python\opencv\modules\dnn\src\layer.cpp:252: error: (-215:Assertion failed) inputs.size() in function 'cv::dnn::dnn4_v20221220::Layer::getMemoryShapes'
'``



### Steps to reproduce

Load model with the following code

``` Python
model = cv2.dnn.readNet(model_path)
```
Find the model here: https://drive.google.com/file/d/1MDkMfav6VEeOs_UD8TxyzUelci6nQtg8/view?usp=sharing


### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Prompt history
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 ?

I have tried out the History extension and being able to roll back prompts is really useful but you can't go forward and the history don't persist after the page reload.

What I really miss is to at least have a text file that saves all used prompts so you can go back and figuring out the exact prompt used.

### Proposed workflow

1. Use prompts
2. Turn off the computer
3. Turn on computer
4. Open prompt history
5. Reuse known good prompt

### Additional information

_No response_
Repository: vscode
Issue: Move the vertical ruler (the column limit) correctly when the inlay hints are used.
Labels: feature-request,editor-core

Type: <b>Feature Request</b>

So, when the inlay hints are activated for the language, for example, using an LSP, they make the line longer by inserting the inlay hints. However, the vertical ruler for the column limit for such lines needs to be moved to the right as it is supposed to be. I am saying it is supposed to be moved, as it should give a user a hint of where in the line the desired column is (for example, to easily be able to determine where the "max column length" in the code is reached visually).

VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:37:54.581Z)
OS version: Darwin arm64 21.6.0
Modes:
Sandboxed: No


<!-- generated by issue reporter -->
Repository: stable-diffusion-webui
Issue: [Feature Request]: improved metadata and history
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 ?

I ask for metadata to be stored in the images in a more machine+human readable format, like json, and to support the history of the image by allowing multiple generation parameters.

For example, an image starts with a txt2img prompt and its parameters saved as first object in the metadata. Then you apply img2img to it, and the new image adds the original image metadata as a sub-object of its metadata. Then you upscale it, and again you add the input image metadata as a sub-object of the upscale parameters object, which will now have three sets of parameters showing the full history of the image.

The input images metadata is added as a sub-object instead of just adding an item to a history array of parameters because in the future there could be a process that uses more than one input with its own parameters.

Processing over an existing image should also add the original image filename and maybe a hash to the metadata of the input (but not its path for privacy reasons, unless if it's relative to the webui installation).

It would also be nice if the format is discussed with other software packages and everyone agrees on using it.

### Proposed workflow

Any process should add to the metadata any prior metadata of its inputs (when available).

### Additional information

_No response_
Repository: godot
Issue: Godot 4 beta11: Camera2D not synchronized with player when it's process callback is set to Physics.
Labels: bug,discussion,topic:core,topic:2d

### Godot version

Godot 4 beta11

### System information

Windows10

### Issue description

Camera doesn't properly follow player when process mode is set to physics.


https://user-images.githubusercontent.com/43501741/211843323-e59392bc-70a6-4433-9d30-7fd22bb04a65.mp4



### Steps to reproduce

Create character with camera attached to it (Or with RemoteTransform2d). Change camera process callback to physics and move the character.

### Minimal reproduction project

[gdcamtest-mrp.zip](https://github.com/godotengine/godot/files/10393705/gdcamtest-mrp.zip)
Repository: angular
Issue: CLDR version is out of date
Labels: area: i18n

### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

According to this [line](https://github.com/angular/angular/blob/main/WORKSPACE#L178), CLDR v41 is currently used to generate the locales in the `@angular/common` package.

v42 of CLDR was released on 2022-10-19 [here](https://cldr.unicode.org/index/downloads/cldr-42) and includes some changes to currency formatting, including a new, preferred, `alphaNextToNumber` format.

Please see additional links [here](https://unicode-org.github.io/cldr/ldml/tr35-numbers.html) and [here](https://cldr.unicode.org/index/downloads/cldr-42)


### Proposed solution

Update CLDR to version 42, and implement changes to allow formatting based on `alphaNextToNumber` formats

### Alternatives considered

Use CLDR version 41, and keep formatting as is.
Repository: rust
Issue: Missed optimization with a consecutive sequence of match cases
Labels: A-LLVM,I-slow,A-codegen,T-compiler,C-bug

It appears there is a missed optimization with a consecutive sequence of match cases.

I tried this code (see also: https://rust.godbolt.org/z/raMTYK83d):

```rust
#[repr(u8)]
enum Foo {
    Zero, One, Two, Three, Four,
}

impl TryFrom<u8> for Foo {
    type Error = &'static str;

    fn try_from(val: u8) -> Result<Self, Self::Error> {
        match val {
            0 => Ok(Foo::Zero),
            1 => Ok(Foo::One),
            2 => Ok(Foo::Two),
            3 => Ok(Foo::Three),
            4 => Ok(Foo::Four),
            _ => Err("nope"),
        }
    }
}
```

I expected this to turn into a integer bounds check of `val` and a return of `val` when in range.

Instead, the compiler (even with `-O`) builds a jump table with each case in the jump table loading the discriminant value and returning it.

I also rewrote the `try_from` implementation such that the RHS of each non-error match arm is identical:
```
    0 => Ok(std::mem:transmute(val))
```
A jump table is constructed, and each case in the jump table is identical.

Finally, I rewrote the `try_from` implementation to group all valid cases into a single match arm:
```
    0 | 1 | 2 |3 | 4 => Ok(std::mem::transmute(val))
```
This last case produces the code that I'd expect: a bounds check and return of `val`.

### Meta
I observe this with rustc 1.66, beta and nightly (via godbolt).
Repository: angular
Issue: SwPush.subscription & SwPush.requestSubscription not emitting after hard reload
Labels: area: service-worker

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

service-worker

### Is this a regression?

No

### Description

I discovered this problem on Angular 13, but it also appeared on v14 and v15.

We've implemented Push Notifications with SwPush.
On initialization of a component, I want to subscribe to SwPush.subscription (the Observable) to get the current subscription (or null, if there is none).
Equally, I want to call SwPush.requestSubscription (the Promise) when I finally want to ask the user for permission.

Both of these methods are NOT emitting any value (or resolving, for the Promise) when I hard reload the application (STRG+F5). They don't throw any error, they just stay silent and never complete.

When I soft-reload the application (regular refreshing the page), only THEN these methods work and will emit corresponding values.

**Expected behaviour:**
Emit values when subscribing to the .subscription Observable or when using the requestSubscription() Promise, or throw an error if there is something wrong / if it fails.

**Current behaviour:**
Nothing is ever emitted, no errors are thrown, the user will be waiting forever.

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

_No response_

### Please provide the exception or error you saw

_No response_

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

```true
Angular CLI: 15.1.0
Node: 16.14.2
Package Manager: npm 8.5.5
OS: win32 x64

Angular: 15.1.0
... animations, cli, common, compiler, compiler-cli, core
... elements, forms, language-service, localize
... platform-browser, platform-browser-dynamic, router
... service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1501.0
@angular-devkit/build-angular   15.1.0
@angular-devkit/core            15.1.0
@angular-devkit/schematics      15.1.0
@angular/cdk                    14.2.7
@schematics/angular             9.1.15
rxjs                            6.6.7
typescript                      4.8.4
webpack                         4.46.0
```


### Anything else?

_No response_
Repository: go
Issue: spec: clarify wording describing result of recover
Labels: Documentation,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?
 
 https://go.dev/ref/spec

### What is your user agent?
 
chrome (not relevant)

 
### Screenshot
 
(not relevant) 
 
 
### What did you do?
 
Reporting a doc nit 
 
 
### What did you expect to see?
 
 (not relevant)
 
### What did you see instead?

Not sure where to find the source of the golang language spec to report this:

The words "the return value of D's call to recover will be the value passed to the call of panic" would be more clearly stated as:

"D's call to recover will return the value previously passed to the call of panic" possible adding " that initiated the unwinding"


The two wordings are equivalent, but the first wording may cause some readers dissonance while they figure out how the return value of D's call to recover could become the value passed to the call of panic.
Repository: pytorch
Issue: Add plots of LRSchedulers to doc to make it easier to read
Labels: module: docs,triaged,actionable,module: LrScheduler

We can do something similar to what we have for activation functions https://pytorch.org/docs/stable/generated/torch.nn.ReLU.html?highlight=relu#torch.nn.ReLU

A simple script similar to the one shared in https://github.com/pytorch/pytorch/issues/91765 can be used a the basis for generating these plots.

cc @svekars @carljparker
Repository: go
Issue: cmd/compile: os.Stdout.Write causes its argument to escape on Windows
Labels: Performance,OS-Windows,NeedsInvestigation,compiler/runtime

```
go version go1.19.5 linux/amd64
go version devel go1.20-76d39ae349 Tue Jan 10 20:34:22 2023 +0000 linux/amd64
```
```
package p

import "os"

func f() {
	os.Stdout.Write([]byte{'h', 'e', 'l', 'l', 'o'})
}
```

Linux:
```
$ GOOS=linux gotip build -gcflags=-m test.go

./test.go:5:6: can inline f
./test.go:6:24: []byte{...} does not escape             <<<<
```
Windows:
```
$ GOOS=windows gotip build -gcflags=-m test.go

./test.go:5:6: can inline f
./test.go:6:24: []byte{...} escapes to heap             <<<<
```

`Read` is also affected.

Reproducible on tip and 1.19.5. 

Related to #41474
Repository: vscode
Issue: Feature request: prettify symbols mode
Labels: feature-request,editor-rendering

<!-- ⚠️⚠️ 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. -->

Feature request: Emacs/Vim/Neovim has a cool feature called ["prettify symbols mode,"](http://emacsredux.com/blog/2014/08/25/a-peek-at-emacs-24-dot-4-prettify-symbols-mode/) demonstrated for [Haskell here](https://github.com/enomsg/vim-haskellConcealPlus). (called conceal in vim/nvim)

This is an intentional reopening of #2402 as it was closed despite public interest.

To put in simpler terms. It would be nice to have custom "ligatures" defined in the editor settings, by language, without making a custom font, and ideally capable of being context sensitive as is done in other major editors. It would be very nice if I could see what the symbols-prettifier aka "conceal" replaced when I hover over said symbol. 

This is an intentional reopening of #2402 as it was closed despite public interest. I believe there was a misestimation public interest in the backlog cleanup, in part because the description was a bit technical. The extension [Prettify Symbols Mode](https://marketplace.visualstudio.com/items?itemName=siegebell.prettify-symbols-mode&ssr=false#overview) **which does not work correctly, but people use it anyway** has 16k downloads and a 4 star rating. This feature is very useful for many programming languages which have verbosity for historical purposes and making a ligature for it is laborious or in many cases fully impossible. This pushes language designers to recommend other editors like emacs (prettify-symbols-mode), vim (conceal), or neovim (conceal) which support this feature natively without extensions. It would be very helpful if vscode supported this useful feature available in other major editors. There's many more arguments for this feature in the main feature request. I understand that ligatures are pretty good for most, but they are also quite limited, and you may have a font that does not support the one ligature you want. A good example of this is in Microsoft's F# where it would be very nice for readability to have "fun " translate to "λ" without breaking the editor. It feels _very_ weird recommending emacs/vim/nvim for a microsoft run language but there is no clear way forward.
Repository: stable-diffusion-webui
Issue: [Bug]: --disable-console-progressbars is ignored regarding console task progressbars
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

Using --disable-console-progressbars does not turn off console progressbars for individual tasks - it only turns off total progress progressbars, for which a Setting already exists

### Steps to reproduce the problem

1. Set --disable-console-progressbars
2. Run a task that would normally print a progress bar to console
3. Watch as the progress bar appears.

### What should have happened?

No progress bar should have appeared

### Commit where the problem happens

9cfd10cdefc7b2966b8e42fbb0e05735967cf87b

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

Linux

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

Mozilla Firefox

### Command Line Arguments

```Shell
--disable-console-progressbars --lowvram --use-cpu interrogate --xformers --opt-channelslast
```


### Additional information, context and logs

I believe the fault lies in sd_samplers.py, where it says "disable=False" near the end of both sample() and sample_img2img(), which means it's hard-coded for the progressbars to appear. Changing these to "disable=cmd_opts.disable_console_progressbars" makes it work as expected... however, since there's already a Setting for the total progress progressbar, perhaps it's worth moving this to a setting as well, rather than being a command line argument?
Repository: vscode
Issue: Provide a list of deduped and nicely named codicons for use in product
Labels: feature-request,ux,terminal-profiles

The terminal has a feature to change the tab/profile icon which opens this:

<img width="339" alt="image" src="https://user-images.githubusercontent.com/2193314/211871176-d86594d3-f44a-482f-a3ce-8b4b7979a89c.png">

It's very convenient to use but it would be nicer if it was instead:

```
➕ Add - add
💡 Lightbulb - lightbulb
etc.
```

The `- text` above would be the greyed out backing id.

_User_ profiles could also use this as @sandy081 has explored.
Repository: vscode
Issue: Explorer não atualiza
Labels: bug,file-explorer,WSL,confirmation-pending


Type: <b>Bug</b>

Quando eu crio um arquivo pelo terminal conectado no wsl2, esse arquivo não é exibido automáticamente, eu preciso fazer reflesh explorer para isso.

VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.15.79.1-microsoft-standard-WSL2

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-10500H CPU @ 2.50GHz (12 x 2496)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.78GB (0.99GB free)|
|Process Argv|--crash-reporter-id e0a76742-bc99-4828-a8cb-2079ccc1580e|
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|WSL: Ubuntu|
|OS|Linux x64 5.15.79.1-microsoft-standard-WSL2|
|CPUs|Intel(R) Core(TM) i5-10500H CPU @ 2.50GHz (12 x 2496)|
|Memory (System)|3.72GB (2.70GB free)|
|VM|0%|
</details><details><summary>Extensions (5)</summary>

Extension|Author (truncated)|Version
---|---|---
remote-wsl|ms-|0.72.0
material-icon-theme|PKi|4.23.1
42header|kub|0.42.9
codam-norminette-3|Mar|4.5.3
cpptools|ms-|1.13.9

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1:30587005
3biah626:30602489
3d0df643:30613357
89544117:30613380
fim-prod:30623723

```

</details>

<!-- generated by issue reporter -->
Repository: rust
Issue: Add unreachable hints for length getters?
Labels: C-enhancement,T-libs,C-optimization

As discussed in this [thread](https://internals.rust-lang.org/t/18126), Rust does not provide LLVM any information about possible lengths of slices, vectors, and other types. In some cases it prevents LLVM from applying optimizations since it has to account for invalid lengths.

I suggest updating length getters of slice-like types to something like this:
```rust
#[inline]
pub const fn len(&self) -> usize {
    let len = ...;
    let size = core::mem::size_of::<T>();
    // on most arches we can use `isize::MAX as usize`
    // instead of `usize::MAX`, but IIRC not everywhere
    if size != 0 && len > usize::MAX / size {
        unsafe { core::hint::unreachable_unchecked() }
    }
    len
}
```