sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Error in Creating a model for object Detection using cv2.dnn_DetectionModel. Please! solve it
Labels: incomplete

<!--
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.5
- Operating System / Platform => Windows 8 > 64 bit OS
- Compiler => :grey_question:

##### Detailed description

<!-- your description -->

##### 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
-->

##### Issue submission checklist

 - [ ] I report the issue, it's not a question
   <!--
   OpenCV team works with forum.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with questions without a real issue statement will be
   closed.
   -->
 - [x] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found any solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://forum.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [x] I updated to the latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only the latest release for each branch.
   The ticket is closed if the problem is not reproduced with the modern version.
   -->
 - [ ] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as an archive to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
![Error](https://user-images.githubusercontent.com/103021523/170428179-772e52fe-5b24-464d-ab8c-fe4c8ac5cd6b.jpg)
Repository: material-ui
Issue: [codemod] Top-Level-Imports codemod adds some named imports that aren't exported from the top level package
Labels: bug 🐛,package: codemod,ready to take

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

After running the `top-level-imports` codemod, I found that it attempts to import some things incorrectly. 
-  { TransitionProps } named import from '@mui/material' but it actually needs to be imported from '@mui/material/transitions';
- { common } from '@mui/material' should be '@mui/material/colors'

I'm not sure if these imports were intentionally left out of the main package exports, or if that was a mistake, but the codemod doesn't make the distinction. 


### Expected behavior 🤔

The `top-level-imports` codemod should not change imports to named imports for items that aren't exported from the top level package. 

### Steps to reproduce 🕹

Steps:

1. Create a file with: ```
    import { TransitionProps } from '@mui/material/transitions';
    import { common } from '@mui/material/colors';
```
2. Run `top-level-imports on that file. 
3. See it combine these into ```
    import { TransitionProps, common } from '@mui/material'
```
4. Run TSC and notice that typescript informs you that these modules are not exported from '@mui/material'


### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: macOS 12.0
  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: 102.0.5005.61
    Edge: Not Found
    Firefox: 98.0.2
    Safari: 15.0
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base: ^5.0.0-alpha.68 => 5.0.0-alpha.68 
    @mui/icons-material: ^5.5.1 => 5.5.1 
    @mui/lab: ^5.0.0-alpha.67 => 5.0.0-alpha.67 
    @mui/material: ^5.4.0 => 5.4.0 
    @mui/private-theming:  5.3.0 
    @mui/styled-engine:  5.3.0 
    @mui/styles: ^5.3.0 => 5.3.0 
    @mui/system: ^5.4.0 => 5.4.0 
    @mui/types:  7.1.0 
    @mui/utils:  5.3.0 
    @types/react: ^17.0.2 => 17.0.3 
    react: 17.0.1 => 17.0.1 
    react-dom: 17.0.1 => 17.0.1 
    styled-components: 5.2.3 => 5.2.3 
    typescript: ^4.3.2 => 4.5.5 
```
</details>
Repository: pytorch
Issue: `gradcheck` fails for `torch.distribution.transform` APIs in forward mode
Labels: module: distributions,module: autograd,triaged,module: forward ad

### 🐛 Describe the bug

`gradcheck` fails for `torch.distribution.transform` APIs in forward mode when `cache` is not 0.

Take `AbsTransform` as an example,
```python
import torch

def get_fn():
    cache_size = 1
    arg_class = torch.distributions.transforms.AbsTransform(cache_size=cache_size, )
    def fn(input):
        fn_res = arg_class(input)
        return fn_res
    return fn
fn = get_fn()

input = torch.rand([3], dtype=torch.float64, requires_grad=True)
torch.autograd.gradcheck(fn, (input,), check_forward_ad=True)
# torch.autograd.gradcheck.GradcheckError: Jacobian mismatch for output 0 with respect to input 0,
# numerical:tensor([[0., 0., 0.],
#        [0., 0., 0.],
#        [0., 0., 0.]], dtype=torch.float64)
# analytical:tensor([[1., 0., 0.],
#        [0., 1., 0.],
#        [0., 0., 1.]], dtype=torch.float64)
```

Other APIs like `SigmoidTransform, TanhTransform, SoftmaxTransform` also have this issue

### Versions

pytorch: 1.11.0

cc @fritzo @neerajprad @alicanb @nikitaved @ezyang @albanD @zou3519 @gqchen @pearu @soulitzer @Lezcano @Varal7
Repository: flutter
Issue: AutofillHints.oneTimeCode not works on flutter web on iOS
Labels: a: text input,c: new feature,framework,f: material design,platform-web,has reproducible steps,P3,browser: safari-ios,found in release: 3.0,found in release: 3.1,team-web,triaged-web

Hi, I want to suggest sms one time code to the user on iOS, flutter web, safari browser.
I tried many options but none of them solved the problem.
my code:
```
import 'package:flutter/material.dart';

void main() {
  runApp(const TestOneTimeCodeApp());
}

class TestOneTimeCodeApp extends StatelessWidget {
  const TestOneTimeCodeApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Padding(
          padding: const EdgeInsets.all(16.0),
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: const [
              TextField(
                autofillHints: [AutofillHints.oneTimeCode],
                decoration: InputDecoration(hintText: "text input with autofill hint=oneTimeCode"),
              ),//not works
              TextField(
                keyboardType: TextInputType.number,
                autofillHints: [AutofillHints.oneTimeCode],
                decoration: InputDecoration(hintText: "text input with autofill hint=oneTimeCode and keyboardType=number"),
              ),//not works
              TextField(
                keyboardType: TextInputType.phone,
                autofillHints: [AutofillHints.oneTimeCode],
                decoration: InputDecoration(hintText: "text input with autofill hint=oneTimeCode and keyboardType=phone"),
              ),//not works
            ],
          ),
        ),
      ),
    );
  }
}
```
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [Version 10.0.19042.1110], locale en-US)

It works on iOS native app, but not works on flutter web on iOS
the result:
![image](https://user-images.githubusercontent.com/47953151/170444219-b7da80d9-19b1-4cf7-b082-714e90efb69a.png)
Repository: rust
Issue: Audit accesses to the source_map
Labels: A-diagnostics,E-mentor,T-compiler,A-HIR,A-incr-comp,E-medium

The exact source code text in the `SourceMap` is not tracked for incremental compilation.  Accessing it and changing behaviour depending on this text is bound to cause issues with incremental compilation.  Accesses to the `source_map` should therefore be audited, to remove access to such untracked information.

As the main use for these is diagnostics (accessing the exact source code, adjusting a span...).  As a consequence, we don't expect ICEs or miscompilations.  The worse that could happen is weird diagnostics.

Are fine:
- accesses that happen *before* incremental compilation kicks in: parsing, macro expansion, AST passes, lowering, name resolution...
- accesses that are hashed in `impl HashStable for Span`: filename, line number, column number...
- accesses in rustdoc, clippy, rustfmt, as they don't use rustc's incremental compilation.

Steps:
1. create a query `source_map: () -> &'tcx SourceMap`, marked `eval_always` and `no_hash`;
2. for each access to `tcx.sess.source_map()` (there are many), determine if it looks at the source code text;
2.2 if it does, see below;
2.1. if it does not: leave it as it, wrap this access in a method on `TyCtxt` in `rustc_middle::ty::context` and document why this access is fine.

When an untracked access to the source code is found, there are three options, in order:
- try to replace the logic with one based on information available in the HIR;
- add the required information to the HIR and use it, it's meant for this sort of things;
- replace `tcx.sess.source_map()` by `tcx.source_map(())`, which will force the query system to recompute everything properly.

Note: there are many of such accesses.  A quick grep counted ~300.
We do not expect a single contributor to audit all of them at once.

Do not hesitate to contact @cjgillot on zulip if necessary.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: neovim
Issue: Cannot add highlight over search results
Labels: bug,marks,highlight

<details>
<summary>Version info</summary>

### Neovim version (nvim -v)

0.5.0 / 0.6.0 / 0.7.0

### Vim (not Nvim) behaves the same?

No

### Operating system/version

Fedora Linux 36 (Workstation Edition) x86_64

### Terminal name/version

kitty 0.25.0 (terminal) / neovim-qt (gui)

### $TERM environment variable

xterm-kitty (terminal) / unset (gui)

### Installation

appimage

</details>

### How to reproduce the issue

```sh
nvim --clean
```
```vim
:set hlsearch
:hi Search ctermfg=Yellow cterm=reverse ctermbg=NONE
:" ⬑ Only makes the highlight more obvious, does not impact in any other way
:au TextYankPost * silent! lua vim.highlight.on_yank{ timeout = 2000 }
```

Search for something and yank a line containing a match.

### Actual behavior

The match stays highlighted with the `Search` group while the rest of the line is highlighted with the `IncSeach` group.

I've tried to do a similar operation using only extmarks and even with the highest priority possible (65535), the search matches overrule any custom highlight.

<img src="https://user-images.githubusercontent.com/37866106/170480543-f74aeeb9-5ad3-4fd5-bd99-ff5ccd73a6f9.png" width="40%">

### Expected behavior

The match should be highlighted with the `IncSearch` highlight group, just like the surrounding text.

To fix this, I think that the search matches should have a well-defined priority, which is the case for `matchadd()`, where the `'hlsearch'` highlights have a zero-priority.
Repository: go
Issue: cmd/go: work use . does nothing in non module root
Labels: NeedsInvestigation,GoCommand

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.19-0ab71cc065 Thu May 26 04:57:33 2022 +0000 linux/amd64
</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=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/arccy/.cache/go-build"
GOENV="/home/arccy/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/arccy/.data/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/arccy/.data/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/arccy/sdk/gotip"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/arccy/sdk/gotip/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.19-0ab71cc065 Thu May 26 04:57:33 2022 +0000"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/arccy/tmp/testrepo-905/a/go.mod"
GOWORK="/home/arccy/tmp/testrepo-905/go.work"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4081894270=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

with the following directory tree:

```
.
├── a
│  ├── b
│  │  └── doc.go
│  └── go.mod
└── go.work
```

run `go work use .` in `a/b`

### What did you expect to see?

module defined at `a/go.mod` added to `go.work`

### What did you see instead?

nothing happened (see also #51965)

### notes

`go help work use` says `usage: go work use [-r] moddirs`,
but it would be more ergonomic to have `go` look upwards for the moddir,
essentially: `go work use $(dirname $(go env GOMOD))`

cc @bcmills @matloob
Repository: neovim
Issue: `grid_cursor_goto` sends invalid position in TERMINAL mode
Labels: bug,terminal,ui-extensibility

### Neovim version (nvim -v)

0.7.0

### Vim (not Nvim) behaves the same?

No

### Operating system/version

PopOs 21.10

### Terminal name/version

GUI

### $TERM environment variable

xterm-256color

### Installation

Build from source

### How to reproduce the issue

Open up `:terminal` in a GUI, and make the cursor go to the bottom of the screen while staying in terminal mode (e.g. not in normal mode). Once at the bottom of the screen/buffer, scroll up while staying in terminal mode and neovim will send bad `row` in `grid_line_cursor`. Correct cursor position is sent in the following ui event batch.

### Expected behavior

Neovim to send correct cursor position.

### Actual behavior

Neovim sends bad cursor position (bad `row`).

Related log file: [nvim.log](https://github.com/neovim/neovim/files/8778627/nvim.log). **Note** that the bad event is the _second last_, not last cursor goto event.
Repository: material-ui
Issue: [Button][Checkbox] Allow receiving focus when disabled
Labels: new feature,component: checkbox,component: button

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

`focusableWhenDisabled` prop for UnstyledButton has been recently implemented (#32090). The [docs claim](https://mui.com/base/react-button/#focus-on-disabled-buttons):

> Similarly to the native HTML <button> element, the ButtonUnstyled component can't receive focus when it's disabled. This may reduce its accessibility, as screen readers won't be able to announce the existence and state of the button.
>
> The focusableWhenDisabled prop lets you change this behavior. When this prop is set, the underlying button does not set the disabled prop. Instead, aria-disabled is used, which makes the button focusable.
>
> This should be used whenever the disabled button needs to be read by screen readers.

The same reasoning should be applicable to the MUI Button and Checkbox components


### Examples 🌈

See https://mui.com/base/react-button/#focus-on-disabled-buttons

### Motivation 🔦

Make `<Button disabled />` and `<Checkbox disabled>` accessible
Repository: flutter
Issue: Add a sample for repeat-tap tab to pop/scroll-up
Labels: platform-ios,d: api docs,d: examples,P3,team-ios,triaged-ios

A common pattern in iOS where re-tapping the same tab scrolls to the top of the page or pops all the routes on the nav stack.
Repository: PowerToys
Issue: [FEATURE request] Pick Dominant Colors
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Grab the color palette and the dominant color from an image or any currently running application.
Eventually for the latter case you could use a sort of "snipping tool" to focus on a specific area of ​​the screen.

### Scenario when this would be used?

Whether it's a 3D CGI project or a 2D digital painting, colors are essential to evoke certain emotions.
It often happens to be inspired by environments we have photographed. The idea is to facilitate the detection of those colors that we would like to transpose into our projects.

### Supporting information

_No response_
Repository: opencv
Issue: [FEATURE REQUEST] cv2.MORPH_ELLIPSE should give a rotationally symmetric kernel for square kernel sizes
Labels: bug,category: imgproc,pr: Discussion Required

`cv2.MORPH_ELLIPSE` is not rotationally symmetrical when the kernel is square. For me, and I'm assuming for others too, this is counter-intuitive.

```
>>> cv2.getStructuringElement(cv2.MORPH_ELLIPSE, [5, 5])
array([[0, 0, 1, 0, 0],
       [1, 1, 1, 1, 1],
       [1, 1, 1, 1, 1],
       [1, 1, 1, 1, 1],
       [0, 0, 1, 0, 0]], dtype=uint8)
```

I would expect the behaviour to look more like that of scikit-image. 

```
>>> skimage.morphology.disk(2)
array([[0, 0, 1, 0, 0],
       [0, 1, 1, 1, 0],
       [1, 1, 1, 1, 1],
       [0, 1, 1, 1, 0],
       [0, 0, 1, 0, 0]], dtype=uint8)
```
Repository: rust
Issue: Investigate eliminate `region_scope_tree`
Labels: I-slow,T-compiler

In https://github.com/rust-lang/rust/pull/95563 and https://github.com/rust-lang/rust/pull/97383, we found that computing the `region_scope_tree` is a non-trivial cost, especially in incremental builds. I was discussing with @dingxiangfei2009 and I am of the opinion that we can *probably* remove the `region_scope_tree` entirely now that we have moved over to the MIR borrow checker (i.e., NLL). We looked over the places that the `region_scope_tree` is used and it seems to be primarily dealing with "when do we run destructors". I think that we could probably just store the hir-id of statements and blocks and it's not important to model the full detail of the region-scope-tree. We didn't look closely into it though and it will require some detailed examination, so for now we are filing an issue to follow up on later.
Repository: go
Issue: cmd/compile,runtime: SIGILL on `linux-loong64-3a5000`
Labels: NeedsInvestigation,arch-loong64,compiler/runtime

```
#!watchflakes
post <- builder ~ `^linux-loong64` && `signal: illegal instruction \(core dumped\)`
```

```
signal: illegal instruction (core dumped)
FAIL	cmd/go/internal/modfetch	0.362s
```

`greplogs -l -e '(?ms)\Alinux-loong64-.*signal: illegal instruction \(core dumped\)'`
[2022-05-24T17:02:34-70668a4/linux-loong64-3a5000](https://build.golang.org/log/3b758d107ddd560a280541417d98cc71f65920d6)

(attn @golang/loong64)
Repository: youtube-dl
Issue: Please add support for website vtv.vn
Labels: site-support-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.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support 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 new site support request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://vtv.vn/video/chiec-xe-dap-khong-phanh-cua-cau-hoc-tro-ngheo-561319.htm
- Single video: https://vtv.vn/video/bao-ton-nhung-dong-vat-quy-hiem-561301.htm
- Single video: https://vtv.vn/video/ung-dung-bao-ve-phu-nu-561027.htm

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

This site is free to watch all videos.
Repository: vscode
Issue: Issue with encoding output in terminal
Labels: bug,debug

- VS Code Version: latest 1.67.2
- OS Version: Win 10

I run rust program by **F5**. When console=internalTerminal or externalTerminal - then I have issue with output encoding.
When console=internalConsole - all OK.

internalTerminal - cmd, powershell or cmder - all have  issue with output encoding (when run by F5), but work well when I start program manually or by "cargo run"
![ss_2022_05_26__16_49_28](https://user-images.githubusercontent.com/25248634/170528509-30b94a09-8b2f-4354-982c-25b45144a9d4.png)
[functions.zip](https://github.com/microsoft/vscode/files/8780417/functions.zip)