sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: issue with upgrading '@storybook/*' via npx storybook@latest upgrade 
Labels: bug,cli

### Describe the bug

When running `npx storybook@latest upgrade`, the logs say the wrong parameter is being passed to the `timeout` argument, resulting in none of the versions in package.json being changed.

I am trying to upgrade from `v6.5.13` to `v7`

>  % npx storybook@latest upgrade
 • Checking for latest versions of '@storybook/*' packagesinfo ,Upgrading /Users/alex/projects/canvas/package.json
info ,TypeError [ERR_INVALID_ARG_TYPE]: The "timeout" argument must be of type number. Received type string ('60000')
info     at new NodeError (node:internal/errors:372:5)
info     at validateNumber (node:internal/validators:125:11)
info     at getTimerDuration (node:internal/timers:384:3)
info     at new ClientRequest (node:_http_client:179:20)
info     at request (node:https:353:10)
info     at /Users/alex/.npm/_npx/fb0d72a785aea960/node_modules/npm-registry-fetch/node_modules/minipass-fetch/lib/index.js:98:17
info     at new Promise (<anonymous>)
info     at fetch (/Users/alex/.npm/_npx/fb0d72a785aea960/node_modules/npm-registry-fetch/node_modules/minipass-fetch/lib/index.js:55:10)
info     at /Users/alex/.npm/_npx/fb0d72a785aea960/node_modules/npm-registry-fetch/node_modules/make-fetch-happen/lib/remote.js:51:23
info     at /Users/alex/.npm/_npx/fb0d72a785aea960/node_modules/promise-retry/index.js:29:24 {
info   code: 'ERR_INVALID_ARG_TYPE'
info }
info 
info ,Upgrading /Users/alex/projects/canvas/package.json
info 
info No dependencies.
info ,
 • Installing upgrades • Preparing to install dependencies. ✓

### To Reproduce

_No response_

### System

```shell
Environment Info:

  System:
    OS: macOS 13.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
    npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
  Browsers:
    Chrome: 114.0.5735.106
    Edge: 109.0.1518.52
    Firefox: 52.4.1
    Safari: 16.2
  npmPackages:
    @storybook/builder-webpack5: ^6.5.13 => 6.5.16 
    @storybook/manager-webpack5: ^6.5.13 => 6.5.16 
    @storybook/react: ^6.5.16 => 6.5.16
```


### Additional context

_No response_
Repository: go
Issue: cmd/doc: `go doc <Symbol>` shows "." as package import path
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.21-4dae3bbe0e Tue Jun 6 20:24:31 2023 +0000 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Ran `go doc <symbol>`

```
project/mod/modfile$ go doc AutoQuote
package modfile // import "."
...
```

See `// import "."`.
Compare it with the package doc mode output.

```
project/mod/modfile$ go doc
package modfile // import "golang.org/x/mod/modfile"
...
```


### What did you expect to see?

Current package's import path.

### What did you see instead?

Always `// import "."`.
Repository: kubernetes
Issue: Repeated server side apply creates additional revisions
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

A configmap using string data:

```
apiVersion: "v1"
kind: "Secret"
metadata:
  name: "example"
stringData:
  foo: "bar"
type: "Opaque"
```

Each time it is applied: "kubectl apply -f secret.yml --server-side"

Will create a new resourceVersion and an updated managedFields time, but otherwise no changes.

I observed similar behavior with Ingress resources as well.

### What did you expect to happen?

When there are no real modifications, no new revision should be created.

### How can we reproduce it (as minimally and precisely as possible)?

Run

```
kubectl apply --server-side -f - <<EOF
apiVersion: "v1"
kind: "Secret"
metadata:
  name: "example"
stringData:
  foo: "bar"
type: "Opaque"
EOF
```

twice and confirm the resourceVersion changes

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"09f825e2ac8ddedf8bbc6bc82ffc5520560788a0", GitTreeState:"clean", BuildDate:"2022-04-29T17:13:31Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
```



</details>


### Cloud provider

<details>
N/A - just minikube
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: go
Issue: x/tools/cmd/bundle: fails to rename references to embedded generic structs
Labels: NeedsInvestigation,Tools

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using?

<pre>
go version go1.20.5 linux/amd64
x/tools/bundle version: v0.9.3
</pre>
 
### What did you do?
 
I ran the command `bundle -o bundled.go ./lib` where `lib` is a folder containing a single file with <a href="https://go.dev/play/p/Ahi4eH8N8tm">this code (see link)</a>

### What did you expect to see?

I expected `bundle` to produce <a href="https://go.dev/play/p/64wl0Mop7b3">this code (see link)</a>.  Note in particular line 22:

```
	x := s.lib_Stack.Pop()
```

### What did you see instead?

`bundle` produced <a href="https://go.dev/play/p/2PrOOwf6WoS">this code (see link)</a> which does not compile:

```
./prog.go:22:9: s.Stack undefined (type *lib_StackTwo[T] has no field or method Stack)
```

The problem is that `bundle` failed to rename the field selector referring to the embedded generic struct `Stack` in line 22:

```
	x := s.Stack.Pop()
```

I have had similar problems running `bundle` on other programs featuring embedded generic structs.
Repository: rust
Issue: Collapsible sidebar items
Labels: T-rustdoc,A-rustdoc-ui

The sidebar can make it hard to find information if there are many enum variants or methods.

For example, a user interested in finding trait implementations for [`isocountry::CountryCode`](https://docs.rs/isocountry/latest/isocountry/enum.CountryCode.html) may look for this info in the sidebar. To do so, the user would have to tediously scroll through all of the variants and methods first.

*Current*
![current](https://github.com/rust-lang/docs.rs/assets/6740989/40b0b131-c118-45de-b915-545ef48aad28)

*Proposed*
![proposed](https://github.com/rust-lang/docs.rs/assets/6740989/fc4436f1-c37d-4131-8e3e-012440e73959)

*Proposed changelog:*
 - `.sidebar-title` heading moved from center to left, with left padding of 10px
 - `.sidebar-links > a` padding changed from 10px to 15px
 - collapsible link added to right side of `.sidebar-title`
 - collapsible link uses the styling of `.collapse-toggle` (colour of `#999`, typographic styling on the plus/minus character)
 - adjusted margins and vertical border (no double border) for adjacent collapsed items
 
\\\

The collapsing UX can also be improved for the main content section, but I will put that in a separate issue.

If you like this idea for the sidebar, I'd be happy to submit a PR.
Repository: excalidraw
Issue: I can't add any images, for some reason it just freeze then nothing are added.
Labels: More information needed / cannot reproduce,images

![Animation](https://github.com/excalidraw/excalidraw/assets/57834534/eed3e934-fb18-4c1f-840f-d4a0473e0f03)
Repository: PowerToys
Issue: Mouse Without Borders: Windows 11 emoji picker doesn't accept remote keyboard input
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.70.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1. Enable Mouse Without Borders on PCs A and B, with B having Windows 11 installed, and connect them.
2. From PC A, move mouse to PC B screen.
3. Access the Windows 11 emoji picker (`Win+.` or `Win+;`).
4. Try entering anything in the keyboard, including `Esc`.

### ✔️ Expected Behavior

Emoji picker doesn't accept any keyboard input.

Note that it does accept mouse input just fine (and in fact, is required just to exit the emoji picker).

### ❌ Actual Behavior

Emoji picker does accept keyboard input.

### Other Software

_No response_
Repository: next.js
Issue: HMR breaks in 13.4.3 and 13.4.4 (and in 13.4.8) when used with custom server 
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.0.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.4
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.2
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/vercel/next.js/tree/canary/examples/reproduction-template

### To Reproduce

Install 13.4.3/13.4.4
Use a custom server
Please have a look at WS in the network.

![Nextjs-13 4 3_HMR-Issue](https://github.com/vercel/next.js/assets/121205240/435a9bd0-3908-4f20-adc2-ed83d467feae)


(sorry for not providing the reproduction repo, as its just 4 lines of custom server)

### Describe the Bug

Using a custom dev server as I need https, 

```
const hostName = 'productname.dev';
const port = 443;
const dev = true;
const app = next({ dev, dir: path.join(__dirname, '../'), hostname: hostName, port });
```

This setup works fine and HMR works as expected on 13.4.2, but fails on 13.4.3/13.4.4 and the latest 13.4.5-canary.6.HTTPS

### Expected Behavior

HMR should work as normal and expected

### Which browser are you using? (if relevant)

Chrome

### How are you deploying your application? (if relevant)

Its a local only issue
Repository: PowerToys
Issue: MWB stuck at yellow (resolving?), is there a way to see error log?
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.70.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Try connecting two PSc using mouse without borders.

### ✔️ Expected Behavior

The devices should connect and the device border should become green to indicate a successful connection.

### ❌ Actual Behavior

The devices don't connect. The status indicator colour is yellow, which I believe is resolving. It remains stuck in this state forever. Is there a wat to see an error log to see what went wrong?

Here is what I have tried:

1. try running with administrator.
2. Try running without administrator.
3. Try running with service. 
4. Without service.
5. I had already added firewall exception before trying to connect.

I am on a university network. Would that be the cause of this issue?

### Other Software

_No response_
Repository: godot
Issue: Unable to Put Multiple NewLines After Applying FontFile to RichTextLabel
Labels: bug,topic:gui

### Godot version

v4.0.3.stable.official [5222a99f5]

### System information

Linux Mint 20.3 (una)

### Issue description

Having a FontFile loaded into the Theme Overrides for a Label or RichTextLabel causes the node in question to condense repeated newlines tags down to a single newline. In other words, "\n\n\n\n" becomes "\n". This only occurs when a FontFile is loaded, and does not depend upon whether an actual font is loaded, present, or referenced. I would expect that loading a FontFile would not affect the way that Labels of any kind apply and render newlines.

### Steps to reproduce

1. Open a Label or RichTextLabel. (If it is a RichTextLabel, check the node Inspector to make sure that the BBCode_Enabled box is checked.)
2. Insert text into the Text Box that includes several newlines in a row. Example Text:
```
This example text precedes three newlines.


This is example text both follows and precedes three newlines.


This is example text both follows three newlines.
```
3. Open the "Fonts" drop down, under the "Theme Overrides" drop down in the Control section of the Inspector.
4. Next to "Normal Font", click the down arrow and choose "New FontFile"
5. Go back to the Text Box, and modify the text slightly -- for example, by pressing 'enter' and then 'backspace'.
6. Uncheck the box next to "Normal Font", then repeat step 5.

### Minimal reproduction project

[FontIssue.zip](https://github.com/godotengine/godot/files/11671620/FontIssue.zip)
Repository: pytorch
Issue: error: ‘aligned_alloc’ was not declared in this scope        static_cast<char*>(aligned_alloc(FLATBUFFERS_MAX_ALIGNMENT, size)), free);
Labels: module: build,triaged

### 🐛 Describe the bug

[100%] Building CXX object caffe2/torch/CMakeFiles/torch_python.dir/csrc/init_flatbuffer_module.cpp.o
/data/meda_home/hongbin/pytorch/torch/csrc/init_flatbuffer_module.cpp: In function ‘std::shared_ptr<char> copyStr(const string&)’:
/data/meda_home/hongbin/pytorch/torch/csrc/init_flatbuffer_module.cpp:37:26: error: ‘aligned_alloc’ was not declared in this scope
       static_cast<char*>(aligned_alloc(FLATBUFFERS_MAX_ALIGNMENT, size)), free);
                          ^~~~~~~~~~~~~
gmake[2]: *** [caffe2/torch/CMakeFiles/torch_python.dir/build.make:1630: caffe2/torch/CMakeFiles/torch_python.dir/csrc/init_flatbuffer_module.cpp.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[1]: *** [CMakeFiles/Makefile2:4151: caffe2/torch/CMakeFiles/torch_python.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2


### Versions

(base) -bash-4.1$ python torch/utils/collect_env.py 
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: CentOS release 6.9 (Final) (x86_64)
GCC version: (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5)
Clang version: Could not collect
CMake version: version 3.21.3
Libc version: glibc-2.10

Python version: 3.7.4 (default, Aug 13 2019, 20:35:49)  [GCC 7.3.0] (64-bit runtime)
Python platform: Linux-2.6.32-696.el6.x86_64-x86_64-with-centos-6.9-Final
Is CUDA available: N/A
CUDA runtime version: 10.1.105
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.21.6
[pip3] torch==1.12.0a0+git664058f
[conda] numpy                     1.21.6                   pypi_0    pypi
[conda] torch                     1.12.0a0+git664058f          pypi_0    pypi

cc @malfet @seemethere
Repository: material-ui
Issue: Zoom has not been applied on radio buttons, stepper step icon buttons (on safari desktop browser)
Labels: bug 🐛,browser: Safari

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. open [stepper](https://mui.com/material-ui/react-stepper/) or [radio button](https://mui.com/material-ui/react-radio-button/) docs page on **safari desktop browser**



### Current behavior 😯

If we zoom in the radio button or stepper widgets, we can observe no change(or reduction) of sizes. It is working as expected on chrome browser, but not on safari(tested only on this for now)

when zoomed in, please observe the sizes of the buttons:
<img width="1268" alt="image" src="https://github.com/mui/material-ui/assets/76739349/486cc835-e7aa-4052-bd92-1f7f4562bc0f">

<img width="1382" alt="image" src="https://github.com/mui/material-ui/assets/76739349/2293e8ac-87dc-4275-b25e-281fabe748c8">


### Expected behavior 🤔

the radio button, stepper step number button(probability applied to similar items) sizes should change wrt to zoom in/out.

### Context 🔦

Safari desktop browser

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: flutter
Issue: [Feature Request] DatePickerThemeData to custom style of disabled dates
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I am using `showDatePicker()` to have my users use a calendar to select a date. 
I would like my `enabled` dates which meet the conditions of `selectableDayPredicate` to look different from `disabled` dates. so I looked at the source code of `calendar_date_picker.dart` and changed `_DayPickerState` like below

```dart
...
final Color? dayForegroundColor = resolve<Color?>(
            (DatePickerThemeData? theme) => isToday ? theme?.todayForegroundColor : theme?.dayForegroundColor, states);
final Color? dayBackgroundColor = resolve<Color?>(
            (DatePickerThemeData? theme) => isToday ? theme?.todayBackgroundColor : theme?.dayBackgroundColor, states);
final Color? disabledColor = resolve<Color?>(
            (DatePickerThemeData? theme) => isDisabled ? theme?.dayOverlayColor : theme?.dayOverlayColor, states);
...
Widget dayWidget = Container(
          decoration: decoration,
          child: Center(
            child: Text(
              localizations.formatDecimal(day),
              style: dayStyle?.apply(
                color: isDisabled ? disabledColor : dayForegroundColor,
              ),
            ),
          ),
        );

```

### Proposal

<img width="361" alt="Screenshot 2023-06-07 at 1 37 50 PM" src="https://github.com/flutter/flutter/assets/45306565/04a7d375-1374-405e-9863-40f20154776a">


the `CalendarDatePicker` now looks like the screenshot above, but I would like to have the disabled dates different `fontWeight` and `fontSize` from enabled dates. would you guys be willing to accept a PR if I were to add this feature?
Repository: storybook
Issue: Vue2/3: Fix conditional decorators
Labels: bug,vue,vue3

### Describe the bug

https://github.com/storybookjs/storybook/pull/22336 fixes conditionally rendering of decorators in React, but the tests expose incorrect behavior in both Vue2 and Vue3, which is discussed in the PR. Documenting that here for potential future follow-up.

### To Reproduce

See chromatic screenshots in https://github.com/storybookjs/storybook/pull/22336

### System

_No response_

### Additional context

_No response_
Repository: tauri
Issue: [bug] Initial content doesn't render inside app macOS
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

After executing `cargo create-tauri-app` and selecting rust/yew, the default content doesn't render inside the application window.

### Reproduction

1. `cargo install create-tauri-app`
2. `cargo create-tauri-app`
    - Select `Rust`
    - Select `yew`
3. `cd new-tauri-app`
4. `cargo tauri dev`

### Expected behavior

Application window opens and default template content is rendered.

### Platform and versions

```text
WARNING: no lock files found, defaulting to npm

[✔] Environment
    - OS: Mac OS 10.15.7 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.70.0 (90c541806 2023-05-31)
    ✔ Cargo: 1.70.0 (ec8a8a0ca 2023-04-25)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 16.14.0
    - yarn: 1.22.10
    - npm: 8.3.1

[-] Packages
    - tauri [RUST]: 1.3.0
    - tauri-build [RUST]: 1.3.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: not installed!
    - @tauri-apps/cli [NPM]: 1.3.1

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
```
```


### Stack trace

```text
`Unhandled Promise Rejection: Error: WebAssembly.Module doesn't parse at byte 273`
```


### Additional context

_No response_
Repository: deno
Issue: Support Gatsby
Labels: node compat,node native extension,triage required 👀

Tracking issue for supporting [Gatsby](https://www.gatsbyjs.com/)

with `deno task build`:
- `dyld[27742]: missing symbol called`
Repository: electron
Issue: [Bug]: Transparent BrowserWindows become opaque at small sizes on macOS
Labels: platform/macOS,bug :beetle:,status/confirmed,component/BrowserWindow,has-repro-gist,25-x-y,26-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

25.0.1 to 34.0.0

### What operating system are you using?

macOS

### Operating System Version

macOS Ventura 13.4 to macOS Sequoia 15.2

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

22.3.12

### Expected Behavior

After creating a BrowserWindow with the option `transparent:true` (and no other additional options), it should be possible to resize the window to any size, from 0x0 pixels or much larger without affecting the window's transparency.

### Actual Behavior

After creating a BrowserWindow with the option `transparent:true`, resizing the window to around 64 by 64 pixels or less draws a white window background. When the window is then resized larger, the white window background disappears, and the entire window becomes transparent again.

### Testcase Gist URL

https://gist.github.com/KevinHughes/28e0e2527dd6efaa84929f7740bc04dd

### Additional Information

This appears to have been introduced in Electron 23.0.0. When running the attached gist, resize the black window border from the bottom right or left corner until the size is around 64 by 64 pixels or less. The window should then be drawn with a white background.