sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: Trigger Vue event with $event happen `method "toJSON" is not defined` by Addon Action
Labels: bug,vue,has workaround

**Describe the bug**
When adding the `$event` props for the event method of Vue component and trigger the event on Storybook button, 
the **Addon Action** and Vue will happen the error message below:
`[Vue warn]: Property or method "toJSON" is not defined on the instance but referenced during render`

![image bug](https://user-images.githubusercontent.com/15682657/118255666-1e0ff100-b4df-11eb-9ea5-c65fb489706c.png)

**To Reproduce**
1. I create an application with the command: `npx vue create vue-cli-storybook` with vue-router, vuex and eslint. (@vue/cli 4.5.13) 
2. I install the Storybook with the command: `npx sb init`
3. Then, I add the `$event` props on `onClick` method on the example file `./src/stories/Button.vue` like this:
```javascript
methods: {
  onClick($event) {
    this.$emit('onClick', $event);
  },
},
```
4. run storybook `npm run storybook` and open Addon Actions console to trigger the button event.

The example repository: https://github.com/VisionYi/vue-cli-storybook

**System**
- System:
   - OS: macOS 11.1
   - CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
- Binaries:
   - Node: 14.15.4 - /usr/local/bin/node
   - Yarn: 1.22.10 - /usr/local/bin/yarn
   - npm: 6.14.10 - /usr/local/bin/npm
- Browsers:
   - Chrome: 90.0.4430.212
   - Firefox: 85.0
   - Safari: 14.0.2
- npmPackages:
   - @storybook/addon-actions: ^6.2.9 => 6.2.9
   - @storybook/addon-essentials: ^6.2.9 => 6.2.9
   - @storybook/addon-links: ^6.2.9 => 6.2.9
   - @storybook/vue: ^6.2.9 => 6.2.9

**Additional context**
I think it is related to this issue [[Addon Action in v5]: Issue when serializing a Vue instance](https://github.com/storybookjs/storybook/issues/6153).

In my real project with **Storybook v6.1.x** that didn't happen like this error, but I upgrade the version to v6.2.9 just have this problem...

In addition, this problem causes severe delay to trigger the event.
Repository: youtube-dl
Issue: REQUEST: Create extractor guide for first time contributors
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.04.26. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.04.26**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

The documentation for youtube-dl, development-wise, is very sparse; I'd tried to write an extractor for a new website (issue #28839) and also reported a bug in Rotten Tomatoes (issue #28967) but due to both a lack of experience and a lack of guides/wiki/starting points, I am not able to make headway here.

The current docs are mostly limited to the basic guide on how to put the new ```InfoExtractor``` one writes into youtube-dl, but doesn't cover much ground on its capabilities/methods it provides, or how one goes about analyzing the websites and video streams in order to write said extractor.

After some searching, I found https://filippo.io/add-support-for-a-new-video-site-to-youtube-dl/, which was written by a contributor to youtube-dl, however, the more advanced version of this tutorial, which is also very important, is incomplete (https://filippo.io/scraping-a-video-out-of-a-more-stubborn-site/). These two posts are also several years out of date. 

Therefore the best solution is to write some good docs for future contributors to look at and follow. 

I would like to help designing/writing these docs as much as possible, and would like to work with an experienced developer on a guide on how to write an extractor, in the same vein as the two blog posts I've linked above. 
Similar docs could be made for other parts of youtube-dl as well, but this is the most urgent one as the extractors are the most heavily worked on part of this project

Thank you to all the developers who have contributed to youtube-dl. This is a really important project, and the work done here is incredible.
Repository: rust
Issue: LLVM backend does not generate debuginfo for const generics 
Labels: A-debuginfo,T-compiler,C-bug,A-const-generics

The code that creates the generic argument descriptions for functions and methods only handles type arguments bug not constants:
https://github.com/rust-lang/rust/blob/69b352ef7749825abde2d8f8e31c05f681e61a10/compiler/rustc_codegen_llvm/src/debuginfo/mod.rs#L425-L479

LLVM does support having value parameters here.
Repository: excalidraw
Issue: Reflect the zoom level and location in the url. 
Labels: enhancement,discussion

Would be nice if you could reflect the zoom level and location in the url.  So as you're zooming and moving around, the url updates. 

You can then send this specific url to someone to draw their attention to the exact area in the canvas you are talking about.
Repository: excalidraw
Issue: a setting where you can just use the mouse wheel, without cntl, to zoom in/out. 
Labels: enhancement,discussion

Would be nice to have a setting where you can just use the mouse wheel, without cntl, to zoom in/out. 

This UI is frequently used in the [AEC industry](https://www.google.com/search?q=aec+industry&rlz=1C1FKPE_enUS928US928&oq=AEC+indu&aqs=chrome.0.0i433j69i57j0l7j46i175i199.1669j0j7&sourceid=chrome&ie=UTF-8).
Repository: rust
Issue: Cannot build + install with `target = ["thumbv7m-none-eabi"]`
Labels: T-bootstrap,C-bug

Steps to reproduce:

1. Get gcc-arm-none-eabi-10-2020-q4-major-x86_64-linux.tar.bz2 from the [ARM developer](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads) website. Install and make available via `PATH`.
2. Get https://static.rust-lang.org/dist/rustc-nightly-src.tar.gz and extract.
3. Copy `config.toml.example` to `config.toml` and make the following changes:
   * Set `target = ["thumbv7m-none-eabi"]`.
   * Configure `prefix` and `sysconfigdir` to a path in your home directory.
4. Run `python3.9 x.py build`. This will be successful.
5. Run `python3.9 x.py install`.

Expected behavior:
Rust for target `thumbv7m-none-eabi` is built and installed.

Actual behavior:
The build/install fails with the following error message:
```
   Compiling rustc-std-workspace-core v1.99.0 (/home/osk/src/rust-thumb/rustc-nightly-src/library/rustc-std-workspace-core)
   Compiling alloc v0.0.0 (/home/osk/src/rust-thumb/rustc-nightly-src/library/alloc)
    Finished release [optimized] target(s) in 10.00s
Copying stage2 std from stage2 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / thumbv7m-none-eabi)
error: The argument '--package <SPEC>' was provided more than once, but cannot be used multiple times

USAGE:
    cargo rustdoc --features <FEATURES>... --jobs <N> --manifest-path <PATH> --package <SPEC> --release --target <TRIPLE>... -Z <FLAG>...

For more information try --help


command did not execute successfully: "/home/osk/src/rust-thumb/rustc-nightly-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "rustdoc" "--target" "thumbv7m-none-eabi" "-Zbinary-dep-depinfo" "-j" "12" "--release" "-p" "alloc" "--manifest-path" "/home/osk/src/rust-thumb/rustc-nightly-src/library/alloc/Cargo.toml" "--features" "compiler-builtins-mem compiler-builtins-c" "-p" "core" "--" "--markdown-css" "rust.css" "--markdown-no-toc" "-Z" "unstable-options" "--resource-suffix" "1.54.0" "--index-page" "/home/osk/src/rust-thumb/rustc-nightly-src/src/doc/index.md"
expected success, got: exit code: 1


failed to run: /home/osk/src/rust-thumb/rustc-nightly-src/build/bootstrap/debug/bootstrap install
Build completed unsuccessfully in 0:08:12
```
Repository: go
Issue: runtime: SIGBUS / SIGSEGV during asmcgocall
Labels: NeedsInvestigation

One while running `cmd/go`:

[2021-05-14T14:37:54-d137b74/solaris-amd64-oraclerel](https://build.golang.org/log/66c5a8bd5b07248bfb8704dc43c69808938dbaed)

```
##### 
fatal error: unexpected signal during runtime execution
[signal SIGBUS: bus error code=0x3 addr=0x7fff929fefd8 pc=0x46eadd]

runtime stack:
runtime.throw({0xa53921, 0x2a})
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/panic.go:1198 +0x74 fp=0x7fff929fef80 sp=0x7fff929fef50 pc=0x43a2d4
runtime.sigpanic()
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/signal_unix.go:719 +0x4a5 fp=0x7fff929fefe0 sp=0x7fff929fef80 pc=0x451be5
runtime.asmcgocall(0x0, 0x0)
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/asm_amd64.s:795 +0xbd fp=0x7fff929fefe8 sp=0x7fff929fefe0 pc=0x46eadd
```

Another while running `cmd/vet`:

[2021-04-14T19:38:22-b161b57/solaris-amd64-oraclerel](https://build.golang.org/log/c80bf7a1d7f69161fc593135e10ce153461b735e)

```
# vendor/golang.org/x/net/nettest
fatal error: unexpected signal during runtime execution
[signal SIGBUS: bus error code=0x3 addr=0x7fff945feff8 pc=0x468fd2]

runtime stack:
runtime.throw(0x728723, 0x2a)
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/panic.go:1191 +0x74
runtime.sigpanic()
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/signal_unix.go:719 +0x4a5
runtime.asmcgocall(0x0, 0x0)
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/asm_amd64.s:796 +0xb2
```

To me that smells like a runtime or compiler bug, and since these are the only two in the logs it looks like a Go 1.17 regression.

CC @prattmic @cherrymui @randall77
Repository: next.js
Issue: 404 in catch all route not being handled properly by custom rewrite
Labels: Navigation

### What version of Next.js are you using?

^10.2.1-canary.6

### What version of Node.js are you using?

v14.16.0

### What browser are you using?

Chrome

### What operating system are you using?

WSL with Ubuntu 20

### How are you deploying your application?

Vercel

### Describe the Bug

the 404 of a catch all route is handled by the custom rewrite but it switches to a blank page (in localhost) with network errors trying to fetch next files.

### Expected Behavior

If a catch all route returns a 404 and a custom rewrite matches that path, it should be able to handle it.

In the demo the destination of the rewrite is another catch all route in a nested folder.

### To Reproduce

Repo: https://github.com/lfades/next-routing-test-a

Demo: https://next-routing-test-a.vercel.app/

https://next-routing-test-a.vercel.app/a <- Handled properly by the root catch all route
https://next-routing-test-a.vercel.app/1 <- is a 404 in the root catch all route, but not handled properly by the rewrite
Repository: PowerToys
Issue: Rereview project dependencies in solution
Labels: Area-Quality,Area-Build,Issue-Task

### Provide a description of the new feature / enhancement

Recently i've tried to a normal build / F5 run a project via runner or the hosting app and just didn't run what was expected due to not doing a full rebuild.

We should valid someone can do a solid F5 and just run these.  This goes for tests as well.

- Runner
   - -> Modules
      - ->  Dependencies (example a plugin)
Repository: opencv
Issue: OOM error while running dnn_superres models on GPU with 8GB memory
Labels: category: gpu/cuda (contrib),category: dnn

I've built OpenCV from the source to run its super-resolution module on my NVIDIA GPU. I've used it in a code like this:
```
# Read the desired model
path = "EDSR_x4.pb"
sr.readModel(path)

# Set CUDA backend and target to enable GPU inference
sr.setPreferableBackend(cv2.dnn.DNN_BACKEND_CUDA)
sr.setPreferableTarget(cv2.dnn.DNN_TARGET_CUDA)
```
But I keep getting this error:

`error("OpenCV(4.5.2) /space/opencv/modules/dnn/src/cuda4dnn/csl/memory.hpp:54: error: (-217:Gpu API call) out of memory in function 'ManagedPtr'\n")`

My GPU memory is 8GB(More info is below), and the image that I'm trying the "EDSR_x4.pb" model on, is 200KB, but the error shows my GPU memory isn't sufficient to run the model with the given input size!
As @YashasSamaga has suggested, we need some API to control heuristics: fastest algo or minimum memory or some middleground. 
Do you have any idea how to work around this issue?

**System information (version)**
- OpenCV => 4.5.2
- Operating System / Platform => Ubuntu 20.04
- GPU => GeForce RTX 2080 SUPER
- GPU memory => 8GB 
- CUDA version => 11.2
- cuDNN version => 8.1.0
Repository: flutter
Issue: The "back" button in the Crane app does not work with screen readers
Labels: engine,a: accessibility,platform-web,P2,team-web,triaged-web

Describe your issue and include the command you're running, flutter_web version, browser version

Steps to reproduce:
1. Launch VoiceOver screen reader on Mac OS (Command + POWER button three times or ask Siri).
2. Using Chrome or Safari go to gallery.flutter.dev, tab to the "Crane" link and press the ENTER key to go inside the app.
3. Tab around between the widgets on the page, then shift+tab to the BACK button and observe.

Expected results:
1. The shift+tab should be able to reach and focus on the BACK button.
2. The screen reader should announce the element in focus.

Observed results:
None of the above happens.
Repository: flutter
Issue: Consider improving the keyboard navigation for the tab list in the Crane app
Labels: framework,engine,a: accessibility,platform-web,P2,team-web,triaged-web

Presently, the user has to press the TAB key to navigate between the tabs in the Crane app (Fly, Sleep and Eat). Additionally, when any of the tabs is selected, the selection state is not reported to the screen reader and other assistive technology.

Steps to reproduce:
1. Launch VoiceOver screen reader on Mac OS (Command+POWER button three times or ask Siri).
2. Using Chrome or Safari navigate to gallery.flutter.dev, then tab around and choose the "Crane" link, press the ENTER key to go inside the app.
3. Navigate to the list of tabs using the TAB key, then press the ENTER key to select one of the tabs. Observe the behavior and spoken feedback.

Expected results:
According to [ARIA best practices](https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel)
1. The state of the currently-selected tab should be reflected so that screen reader users can perceive the it.
2. Left and right arrow keys should navigate between the tabs.

Observed results:
None of the above happens.
Repository: opencv
Issue: Filesystem support on OpenBSD
Labels: category: build/install

<!--
If you have a question rather than reporting a bug please go to https://forum.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->

- OpenCV => 4.5.2
- Operating System / Platform => OpenBSD
- Compiler => clang (not relevant)

##### Detailed description

<!-- your description -->
The filesystem Impl code is inactive, because there is no set of definitions for OpenBSD.

##### Steps to reproduce

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->

noticed while porting gmic and trying to use camera.

I have a 
[patch.txt](https://github.com/opencv/opencv/files/6480601/patch.txt)
patch to fix this, it's really as stupid as adding __OpenBSD__ where __FreeBSD__ is mentioned, and gmic camera now works.
Repository: bitcoin
Issue: Duplicate coinbase transaction space reservation in CreateNewBlock
Labels: Bug

In `BlockAssembler::CreateNewBlock`, we initiate `nBlockWeight` to 4000 WU, reserving space for
coinbase transaction.

Latter on, while iterating on transactions for block inclusion in `addPackagesTxs`, we verify that candidate package doesn't overflow the max block weight. This check is done in `TestPackage` against `nBlockMaxWeight`. However, default value is DEFAULT_BLOCK_MAX_WEIGHT which is equal to MAX_BLOCK_WEIGHT - 4000 (L20 in `src/policy/policy.cpp`). So block weight assembled is starting at 4000 WU and can't overflow 3996000 WU.

Do we have duplicated coinbase transaction space reservation ? I can see this a safety margin to avoid creating invalid blocks if you create inflated coinbase transaction, at the price of few weight units leftover.

If so, maybe we should leave it as it is but document this behavior, I was surprised hitting this while scratching unrelated tests.

See [comment](https://github.com/bitcoin/bitcoin/pull/11100#discussion_r135124178) in #11100
Repository: material-ui
Issue: Doc should ask devs to prioritize reusable CSS patterns over one-off customization approaches
Labels: docs,discussion,package: styled-engine

Has the team considered adding info warnings to pages like [1] so that developers don't overreach into one-off customization techniques when they should be writing re-usable CSS?

[1] https://material-ui.com/customization/components/#customizing-components
Repository: go
Issue: x/build/devapp/owners: remove stale and unhelpful entries
Labels: Builders,NeedsFix

The list of owners at https://dev.golang.org/owners is updated periodically via people sending CLs that add/remove entries. Given a good amount of time has passed and people's priorities and time availability has changed, there are some entries that likely no longer benefit from being on the list (and getting CCed on issues and CLs) but haven't done the work of removing themselves.

We should do a pass over the owners table and remove such owners, so that the entries that are left are known to be more up-to-date. If someone prefers to stay as an owner despite being less active, we shouldn't remove them.

So the task here is to find candidate entries for removal, let them know their entry might be removed unless they prefer to stay, and then remove them.

CC @golang/release.
Repository: go
Issue: cmd/link: support calls to SDYNIMPORT symbols on mips64
Labels: NeedsFix,arch-mips,compiler/runtime

The mips64 port currently fails to handle calls to `SDYNIMPORT` symbols, even when external linking is in use, since it emits `R_MIPS_26` relocations, resulting in "relocation truncated to fit" warnings. An equivalent call from assembly when compiled with LLVM results in the following:

```
   0:   df990000        ld      t9,0(gp)
   4:   0320f809        jalr    t9
   8:   00000000        nop
```

Furthermore, two relocations are produced for the external symbol - a `R_MIPS_CALL16` relocation for the `ld` instruction and a `R_MIPS_JALR` relocation for the `jalr` instruction.

There are a couple of additional things to note here - firstly, PIC code requires that register 25 (`t9`) contains the address of the called function, which is why this register is used here. Secondly, when the external linker performs the R_MIPS_CALL16 relocation is is done with an expected `gp` register value, which is loaded by the dynamic linker. Unfortunately, Go currently uses this register and clobbers the value placed in it by the dynamic linker, breaking the relocation.

This means there are effectively two things to solve:

1. Currently a `CALL` translates to a single `JAL` instruction with an `R_CALLMIPS` (aka `R_MIPS_26`) relocation - given that the assembler does not know if this is an internal function or an `SDYNIMPORT` symbol, the easiest option is to likely produce trampolines for the `SDYNIMPORT` calls, modelling the above assembly and generating the two matching relocations.

2. In order for these relocations to work we likely have to avoid clobbering the `gp` register - one option may be to change Go's `REGSB` register (as was done for `tp` on `riscv64`). The other is to save the value of the `gp` register at start up and restore the `gp` value before calling an `SDYNIMPORT`, switching it back to Go's value after the call returns.

I've got a proof of concept working with external linking, trampoline generation and `gp` register save/restore on `openbsd/mips64` (I'll make this available soon) - in the mean time, I'm interested in feedback and/or other suggestions on these issues/approach, before I proceed further.
Repository: ant-design
Issue: Select element lacking dark theme
Labels: 💄 Design,help wanted,Inactive,good first issue

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[https://ant.design/components/select/?theme=dark](https://ant.design/components/select/?theme=dark)

### Steps to reproduce
The menu element has a dark theme, see here:
https://ant.design/components/menu/?theme=dark

But the select element, which is very similar to menu when expanded, doesn't, causing inconsistency.

### What is expected?
Select, which looks like menu, provides dark-compatible theme.

### What is actually happening?
Only light theme is available for select elements.

| Environment | Info |
|---|---|
| antd | 4.15.5 |
| React | 17.0.2 |
| System | Windows 10 |
| Browser | Chrome 89 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->