sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: manager bundles is outputed with double slashes
Labels: bug,needs triage

### Describe the bug

Background: I am a library author, not an enduser.

I want the static assets in the format of `/assets/abc.png`. By default, it is `assets/abc.png`.

To achieve this, I set `config.output.publicPath = '/'` in `webpackFinal()`.

But this incurs another issue that the manager bundle has double slashes.
I believe it is a bug in the manager build (with `esbuild` config).

```
iframe.html:355     GET http://localhost:6006//runtime.iframe.bundle.js net::ERR_ABORTED 404 (Not Found)
iframe.html:357     GET http://localhost:6006//vendors.iframe.bundle.js 404 (Not Found)
iframe.html:359     GET http://localhost:6006//main.iframe.bundle.js net::ERR_ABORTED 404 (Not Found)
```

Probably related link: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#no-more-configuration-for-manager

Expected behavior: the manager build should correctly handle slash in the publicPath configuration from webpackFinal's output. Or. Allow manually configure the publicPath.

### To Reproduce

_No response_

### System

```shell
"@storybook/addon-essentials": "^7.0.7",
		"@storybook/addon-interactions": "^7.0.7",
		"@storybook/addon-links": "^7.0.7",
		"@storybook/cli": "^7.0.7",
		"@storybook/core-client": "^7.0.7",
		"@storybook/core-server": "^7.0.7",
		"@storybook/manager-api": "^7.0.7",
		"@storybook/react": "^7.0.7",
		"@storybook/react-webpack5": "^7.0.7",
		"@storybook/theming": "^7.0.7",
```
```


### Additional context

_No response_
Repository: flutter
Issue: Windows_build_tests_2_3 are running very close to the timeout
Labels: platform-windows,P2,c: flake,team-windows,triaged-windows

Step 17 has a timeout of 30 minutes, but it is starting to run over that time. The successful runs take 27-29 minutes which is cutting it close.

https://ci.chromium.org/p/flutter/builders/prod/Windows%20build_tests_2_3
Repository: rust
Issue: Moving structs with Copy fields into closures causes surprising behavior
Labels: A-lints,A-closures,T-compiler,C-bug

I noticed some counterintuitive behavior related to partial moves of Copy struct fields (ex: u64 fields) into closures.

## Minimal Reproducible Example

```rust
#[derive(Debug)]
struct Statistics {
    calls: u64,
    successes: u64,
}

fn main() {
    let mut statistics = Statistics {
        calls: 0,
        successes: 0,
    };
    
    let mut generator = move || {
        statistics.calls += 1;
    };
    
    generator();
    statistics.successes += 1;

    println!("{statistics:?}");
}
```

This code compiles and prints
```
Statistics { calls: 0, successes: 1 }
```

[Playground Link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=c4180fa1795ad2b77b0c0aa28aeaf37a)

## What I Expected

I would have expected a `borrow of partially moved value: 'statistics'` error at the `println!`, since the closure takes ownership of the `statistics.calls` field and then the field is later read by the print call.

The actual behavior, where the updates to `statistics.calls` have no observable effect, looks just like a silent copy of the whole struct. This surprised me. When I wrote the code, I expected either a compiler error or an output of `Statistics { calls: 1, successes: 1 }`.

## Investigation

I experimented a bit with the types of the fields within the struct, and I do get the compiler error I expect if `Statistics.calls` is a non-Copy type like `Vec`.

I didn't know about partial moves when I wrote the initial code. I expected the whole struct to move into the closure. It's still surprising to me that partial moves can create this type of "silent copy" behavior depending on the type of the struct's fields.

I did find a similar issue titled [Move closure copies :Copy variables silently](https://github.com/rust-lang/rust/issues/63220), but the code that I wrote is not covered by the "unused variable" warning added in response to that issue.

## Solution

I'm new to Rust so I'm not sure this is a bug, but it's still confusing behavior. Perhaps, like the other issue I linked, there is room for a lint or warning here. Something that warned me that the closure's modification of `statistics.calls` had no effect would be helpful, for example.
Repository: godot
Issue: Built-in Editor Docs scroll to wrong operator
Labels: bug,topic:editor

### Godot version

4.0.2

### System information

Ubuntu 22.04.1 LTS

### Issue description

When clicking on an operator in the class reference, Godot always scrolls to the last operator that uses its symbol and not the specific one I clicked.

### Steps to reproduce

Open Vector2's class reference, which has

```gdscript
Vector2 * Transform2D
Vector2 * Vector2
Vector2 * float
Vector2 * int
```

Clicking any of these will scroll down to `Vector2 * int`

### Minimal reproduction project

N/A
Repository: next.js
Issue: [NEXT-1196] Loading UI does not hydrate through hard navigation
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 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
Binaries:
  Node: 18.12.1
  npm: 9.6.5
  Yarn: 1.22.5
  pnpm: N/A
Relevant packages:
  next: 13.4.2-canary.3
  eslint-config-next: 13.4.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.0.4
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://github.com/kushuh/bug-nextjs-loading

### To Reproduce

```
npm run dev
```

 - Click on the "Go to feed" button.

 - See the loader displaying "Mounted" (expected behavior). Page will resolve 10s later with a "Home" button.

 - Reload the page. See the wrong text displayed.

### Describe the Bug

# What I did

I created a dummy application, with a `/feed` server page that takes 10s to load (forced). 

The loading UI component changes its state with a `useEffect` hook (only effective after client-side hydratation). The result of this update is not always properly displayed.

# The bug

The loading UI component is not hydrated properly on hard navigation (manual refresh or direct navigation). It, however, works as expected when using soft navigation (from `next/link` component).

Also a strange side-effect, with hard navigation, the loading spinner shows in the browser tab, which is not the case with soft navigation (not sure which one should be expected here). Tested on a recent version of Chrome.

### Expected Behavior

The loading UI should properly hydrate when using hard navigation.

### Which browser are you using? (if relevant)

Chrome canary 115.0.5753.0

### How are you deploying your application? (if relevant)

npm run dev

<sub>[NEXT-1196](https://linear.app/vercel/issue/NEXT-1196/loading-ui-does-not-hydrate-through-hard-navigation)</sub>
Repository: TypeScript
Issue: Type narrowing of singleton class
Labels: Suggestion,Awaiting More Feedback

# Suggestion

Able to type narrowing of a singleton class

## 🔍 Search Terms

unique symbol singleton class

## ✅ 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).


## ⭐ Suggestion

## 📃 Motivating Example

```ts
class Value {
  value: unknown
  declare static readonly true: unique (_BooleanValue & { value: true })
  declare static readonly false: unique (_BooleanValue & { value: false })
  declare static readonly null: unique _NullValue
}
class StringValue extends Value {
  value: string
  constructor(value: string) {
    super()
    this.value = value
  }
  toText() {}
}
class _BooleanValue extends Value {
  value: boolean
  constructor(value: boolean) {
    super()
    this.value = value
  }
}
class _NullValue extends Value {
  value: null = null
}
Object.assign(Value, { true: new _BooleanValue(true), false: new _BooleanValue(false), null: new _NullValue() })
type TrueValue = typeof Value['true']
type FalseValue = typeof Value['false']
type NullValue = typeof Value['null']

function test(value: StringValue | NullValue) {
  if (value === Value.null) {
    value // should be NullValue
  } else {
    value.toText() // should be StringValue
  }
}
```

## 💻 Use Cases

I'm working on the engine262 repo, it uses this pattern `value === Value.null` a lot.

Now only this works:

```ts
  declare static readonly true: unique symbol
  declare static readonly false: unique symbol
  declare static readonly null: unique symbol
```

But I cannot attach any properties on `Value.{true,false,null}`
Repository: stable-diffusion-webui
Issue: [Feature Request]: Img2Img Batch use metadata from source image.
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 ?

In Img2Img batch mode, use metadata from the source image of the batch, (like prompt, or seed) as part of the batch rendering for that image.

### Proposed workflow

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


### Additional information

_No response_
Repository: godot
Issue: _forward_3d_gui_input does not work when camera preview is enabled
Labels: bug,topic:editor,topic:plugin,topic:3d

### Godot version

4.0.2

### System information

Windows 10

### Issue description

The `forward_3d_gui_input` of an `EditorPlugin` is not called, when the viewport is currently previewing a camera.
The behavior can be seen in the following image, this is also the attached min repro project.

![CameraPreviewBug](https://user-images.githubusercontent.com/53947784/236988963-13f23b9d-8298-4572-9cb0-4c17241126b9.gif)

This might be related to the Subviewport in the editor still referencing the other editor viewport camera. 

I.e., if you get the first editor viewport via 
```gdscript
var main_screen = get_editor_interface().get_editor_main_screen()
var vp_container = main_screen.get_child(1).get_child(1).get_child(0).get_child(0).get_child(0)
var vp1 : SubViewport = vp_container.get_child(0).get_child(0).get_child(0)	
```
then `vp1.get_camera_3d()` returns `@@9832:<Camera3D#771751971705>`, both if camera preview is enabled or disabled. I would expect it to return the Camera3D in the scene, when preview is enabled. Any workarounds here to get the scene camera if and only if preview is enabled?

### Steps to reproduce

Open reproduction project, make sure that plugin is enabled.

### To reproduce the `_forward_3d_gui_input` issue:
- Hover over viewport
- Observe that the code inside `_forward_3d_gui_input` is called (output produced)
- Then select the Camera3D and enable the preview in the editor viewport 
- Hover over viewport
- Observe that the code inside `_forward_3d_gui_input` is not called (no output)

### To check the referenced Camera3D:
- Press Enter, observe output
- Then select the Camera3D and enable the preview in the editor viewport 
- Press Enter, observe that output is the same

### Minimal reproduction project

[EditorPreviewViewport.zip](https://github.com/godotengine/godot/files/11427082/EditorPreviewViewport.zip)
Repository: neovim
Issue: weird visual mode
Labels: bug-vim,needs:vim-patch

### Problem

hi folks, i just ran into a weird visual mode (i dont have a clear idea about it, sorry for the terrible issue title), in which every keypress will be appended to the buffer; while in a 'regular' visual mode, keypress will trigger rhs.

### Steps to reproduce

1. `$ nvim --clean +'inoremap <c-x> <cmd>so test.lua<cr>'`
2. `i`
3. `<c-x>`
4. `j` #weird thing happends here

<details>

<summary>test.lua</summary>

```
local api = vim.api

local function keycode(raw) return api.nvim_replace_termcodes(raw, true, true, true) end

local function ensure_mode(mode)
  local held = api.nvim_get_mode().mode
  if mode ~= held then error(string.format("expecting in %s mode, actually %s", mode, held)) end
end

local win_id = api.nvim_get_current_win()
api.nvim_buf_set_lines(api.nvim_win_get_buf(win_id), 0, 1, false, { "abcdef" })

ensure_mode("i")
api.nvim_feedkeys(keycode("<esc>"), "nx", false)
-- vim.cmd.stopinsert() -- makes the following assertion failed
ensure_mode("n")
api.nvim_win_set_cursor(win_id, { 1, 0 })
api.nvim_feedkeys("v", "nx", false)
-- vim.cmd('normal! v') -- makes no difference
ensure_mode("v")
api.nvim_win_set_cursor(win_id, { 1, 4 })
```

</details>

### Expected behavior

in the 4 step, `j` should behave like `vmap j`

### Neovim version (nvim -v)

0.9.0

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

archlinux

### Terminal name/version

st 0.9

### $TERM environment variable

st-256color

### Installation

system package manager
Repository: go
Issue: x/tools/gopls: completion incorrectly offers embedded field shadowed by outer field
Labels: NeedsInvestigation,gopls,Tools,gopls/completion

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.2 linux/arm64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.9.0
$ go list -m golang.org/x/tools/gopls
golang.org/x/tools/gopls v0.0.0-20230508221120-0809ec2e45f6
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE="on"
GOARCH="arm64"
GOBIN=""
GOCACHE="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/myitcv/gostuff/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_arm64"
GOVCS=""
GOVERSION="go1.20.2"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2292349384=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

With the following input file:

```
package main

import (
	"fmt"
	"log"
)

type outer struct {
	// outer logger
	logger *log.Logger

	inner
}

type inner struct {
	// inner logger
	logger *log.Logger
}

func main() {
	var v outer
	fmt.Println(v.lo_)
}
```

The cursor at the position `_`.

Attempt a completion.


### What did you expect to see?

The single candidate `outer.logger`.

### What did you see instead?

Two candidates:

```
outer.logger
inner.logger
```

The completion text for both is the plain `logger`. So this can't be correct, as the `outer.logger` shadows the embedded `inner.logger`.
Repository: TypeScript
Issue: Add JSON schema to the `typescript` package for `tsconfig.json` and `jsconfig.json`
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

- JSON schema
- SchemaStore
- `tsconfig.json`
- `jsconfig.json`

## ✅ Viability Checklist

N/A


## 📃 Why

I noticed that [Rome](https://rome.tools/) doesn't use a traditional hosted JSON schema and instead they publish their JSON schema in their package so that it can then be referenced with a local path:

```json
{
  "$schema": "./node_modules/rome/configuration_schema.json",
}
```

I see three advantages to this approach...

1. The JSON schema will match the installed version of the package.
2. The JSON schema will work without internet access, provided that node_modules has been installed.
3. Any changes to the JSON schema in the development can be used straight away in examples, etc.

## ⭐ Suggestion

Maintain the JSON schema in this repository, instead of the the [`SchemaStore`](https://github.com/SchemaStore/schemastore) repository. It will be kept in sync with new TypeScript releases. Finally, publish the JSON schemas in the `typescript` package.

You can still leave the hosted JSON schema as an option, which will always resolve to the JSON schemas for the latest version of TypeScript. This will still be needed for editor autocomplete, whereby the schema is not specified in the JSON, but detected from the name of the file.
Repository: pytorch
Issue: PyTorch installs the file mkldnn.cmake that looks for the package MKLDNN that doesn't exist
Labels: module: build,triaged,module: mkldnn

### 🐛 Describe the bug

/usr/local/lib/python3.9/site-packages/torch/share/cmake/Caffe2/public/mkldnn.cmake looks for ```MKLDNN```.
There is a GitHub project https://github.com/Intel-tensorflow/mkl-dnn that was last updated in 2019. Its website though redirects to oneDNN.

As a result, the DGL project (https://github.com/dmlc/dgl) fails to build:
```
CMake Error at /usr/local/lib/python3.9/site-packages/torch/share/cmake/Caffe2/public/mkldnn.cmake:7 (find_package):
  By not providing "FindMKLDNN.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "MKLDNN", but
  CMake did not find one.

  Could not find a package configuration file provided by "MKLDNN" with any
  of the following names:

    MKLDNNConfig.cmake
    mkldnn-config.cmake

  Add the installation prefix of "MKLDNN" to CMAKE_PREFIX_PATH or set
  "MKLDNN_DIR" to a directory containing one of the above files.  If "MKLDNN"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/local/lib/python3.9/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:106 (include)
  /usr/local/lib/python3.9/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:68 (find_package)
  CMakeLists.txt:29 (find_package)
```


### Versions

PyTorch-2.0.0
FreeBSD 13.2

cc @malfet @seemethere @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @jgong5 @mingfeima @sanchitintel @ashokei @jingxu10 @min-jean-cho @yanbing-j @Guobing-Chen @Xia-Weiwen
Repository: opencv
Issue: Installing OpenCV by Ropencvlite and output bugs
Labels: category: build/install,community help requested

### System Information

OpenCV version: 4.7.0
Operating System / Platform: Win11
Compiler & compiler version: GNU 12.2.0
R version: 4.3.0
Rtools:4.3 (5550-5548)
processor: AMD64
VS:Visual Studio 2022
Cmake:3.26.3

#Other defult version:
Python version: 3.7.12

### Detailed description

#Description
When installing Opencv by using package "Ropencvlite" it shows some errors occured in Cmake compiler function which cannot fixed by coding and changing the environment variables and stucked there for weeks,the exsisted solutions suggest not only in re-installed the old version of R/Rtools/Cmake, but also changing operating system into ubuntu,still won't make it work efficients.However it can do,when installing opencv by python.
#error log                               
C:\rtools43\x86_64-w64-mingw32.static.posix\bin/ld.exe: internal error: aborting at ../../binutils-2.40/ld/ldlang.c:527 in compare_section
C:\rtools43\x86_64-w64-mingw32.static.posix\bin/ld.exe: please report this bug
collect2.exe: error: ld returned 1 exit status
make[2]: *** [modules/videoio/CMakeFiles/opencv_videoio.dir/build.make:307: bin/libopencv_videoio470.dll] Error 1
make[1]: *** [CMakeFiles/Makefile2:2918: modules/videoio/CMakeFiles/opencv_videoio.dir/all] Error 2
make: *** [Makefile:166: all] Error 2
make: Leaving directory '/c/Users/yuqia/AppData/Local/Temp/RtmpsrRv74/opencv-4.7.0/build64'


### Steps to reproduce

install.packages("ROpenCVLite", INSTALL_opts = "--no-multiarch")

[ROpenCVLite-master.zip](https://github.com/opencv/opencv/files/11428728/ROpenCVLite-master.zip)


### 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: rust
Issue: E0623 diagnostic degraded by presence of method parameter
Labels: A-diagnostics,A-lifetimes,T-compiler

### Code

```Rust
use std::marker::PhantomData;

impl Trait for () {
    type In<'a> = PhantomData<&'a ()>;

    type Out<'a: 'b, 'b> = PhantomData<&'a ()>
    where
        Self: 'b;

    fn m<'a, 'b>(&'b self, _: Self::In<'a>) -> Self::Out<'a, 'b> {
        todo!()
    }
}

pub trait Trait {
    type In<'build>;

    type Out<'a: 'b, 'b>
    where
        Self: 'b;

    fn m<'a, 'b>(&'b self, _: Self::In<'a>) -> Self::Out<'a, 'b>;
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0623]: lifetime mismatch
  --> src/lib.rs:10:48
   |
10 |     fn m<'a, 'b>(&'b self, _: Self::In<'a>) -> Self::Out<'a, 'b> {
   |                               ------------     ^^^^^^^^^^^^^^^^^
   |                               |                |
   |                               |                ...but data is returned here
   |                               this parameter and the return type are declared with different lifetimes...

For more information about this error, try `rustc --explain E0623`.
error: could not compile `playground` due to previous error
```


### Desired output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0478]: lifetime bound not satisfied
  --> src/lib.rs:10:31
   |
10 |     fn m<'a, 'b>(&'b self, _: Self::In<'a>) -> Self::Out<'a, 'b> {
   |                                                ^^^^^^^^^^^^^^^^^
   |
note: lifetime parameter instantiated with the lifetime `'a` as defined here
  --> src/lib.rs:10:10
   |
10 |     fn m<'a, 'b>(&'b self, _: Self::In<'a>) -> Self::Out<'a, 'b> {
   |          ^^
note: but lifetime parameter must outlive the lifetime `'b` as defined here
  --> src/lib.rs:10:14
   |
10 |     fn m<'a, 'b>(&'b self, _: Self::In<'a>) -> Self::Out<'a, 'b> {
   |              ^^

For more information about this error, try `rustc --explain E0478`.
error: could not compile `playground` (lib) due to previous error
```


### Rationale and extra context

Here's [a playground][BAD] demonstrating the poor diagnostic. When the method parameter is removed, the desired output [is emitted][GOOD].

It would be even better if the diagnostic pointed at the lifetime bound in line 6 in both cases. However, the primary concern should be that adding a (seemingly unrelated) method parameter can lead to a poorer diagnostic.

[BAD]: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=2c311c66a510bac86271ce40708df6bc
[GOOD]: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=a64544d05cfbcafa0e4751f7e354936c


### Other cases

_No response_

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->