sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Load Tensorflow 2 Object Detection model (saved_model.pb) with OpenCV (cv2.dnn.readNetFromTensorflow)
Labels: category: dnn

### System Information

OpenCV python version: 4.5.5
Operating System / Platform: Windows 10
Python version: 3.9.12

### Detailed description

**I've tried various methods I can find on the internet and none of them work. This problem has been known for 2-3 years. Are there any moves or plans to address this issue?**

### Steps to reproduce

- I trained SSD MobileNet V2 FPNLite 640x640 from TFOD 2 model zoo. Now I want to read it (saved_model.pb) from cv2.dnn.readNetFromTensorflow, but i get an error `Failed to parse GraphDef file: saved_model.pb in function 'cv::dnn::ReadTFNetParamsFromBinaryFileOrDie'`. 

- Also i tried convertind `saved_model.pb`  to 'inference_frozen_graph.pb' and get an error `error: (-215:Assertion failed) !empty() in function 'cv::dnn::dnn4_v20211220::Net::forward'`. 

- I also tried to change the model export script and get an error ` Input node with name MultiscaleGridAnchorGenerator/GridAnchorGenerator/Reshape_3 not found in function 'cv::dnn::Subgraph::getInputNodeId'`.

- I also tried to convert the model to ONNX format and get an error `error: (-2:Unspecified error) in function 'cv::dnn::dnn4_v20211220::ONNXImporter::handleNode Node [Squeeze@ai.onnx]:(StatefulPartitionedCall/Postprocessor/Decode/get_center_coordinates_and_sizes/unstack__1046:0) parse error: OpenCV(4.5.5) D:\bld\libopencv_1654292817370\work\modules\dnn\src\onnx\onnx_importer.cpp:2142: error: (-215:Assertion failed) node_proto.input_size() == 1 in function 'cv::dnn::dnn4_v20211220::ONNXImporter::parseSqueeze'` 

### 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: neovim
Issue: First byte of truncated double-width character is missing after syntax conceal with matchgroup
Labels: has:vim-patch,bug-vim,syntax,unicode  💩,conceal

### Neovim version (nvim -v)

v0.9.0-dev-530+gde90a8bfe5

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

No

### Operating system/version

Arch Linux

### Terminal name/version

kitty 0.26.5

### $TERM environment variable

xterm-kitty

### Installation

build from repo

### How to reproduce the issue

1. Run `nvim --clean`
2. Source the following file:
```vim
call setline(1, ['', repeat('a', &columns - 3) .. '<>个'])
setlocal conceallevel=2
syntax region foo matchgroup=NonText start="<" end=">" concealends
```

### Expected behavior

The `个` is shown correctly:
![vim](https://user-images.githubusercontent.com/35768171/208832374-da5d8cfb-f0f0-4072-b806-0303a05f6640.png)

### Actual behavior

The first byte of the `个` is missing:
![nvim](https://user-images.githubusercontent.com/35768171/208832513-de5e04b5-0d63-4813-8349-d406d74fdea4.png)
Repository: flutter
Issue: Date format abbreviated month not used in es_US locale
Labels: framework,a: internationalization,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-framework,triaged-framework

The abbreviated month is not being used in `es_US` locale when using the skeleton pattern.

Try this code:

```
import 'package:intl/date_symbol_data_local.dart';
import 'package:intl/intl.dart';

void main() {
  initializeDateFormatting();
  print(DateFormat('d MMM yyyy', 'es_US').format(DateTime.now()));
  print(DateFormat.yMMMd('es_US').format(DateTime.now()));
}
```

It prints:

```
21 dic. 2022
21 de diciembre de 2022
```

Note that instead using `es_ES` as the locale produces the expected result.
Repository: rust
Issue: Bounds on generics in trait definition are not propagated
Labels: A-trait-system,A-associated-items,C-bug,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
use core::ops::Add;

pub trait RefOpsBound<'a, F, T: 'a>: Add<T, Output = T> {}
// Bound the type, and also the `S` type.
pub trait OpsBounds<'a, F, S: RefOpsBound<'a, F, Self>>: 'static + Sized + Add<Self, Output = Self> {}

pub trait WithVar: Sized {
    // This should imply Var: Add<Var, Output = Var> and &'a Var: Add<Var, Output = Var>
    type Var: for<'a> OpsBounds<'a, Self, &'a Self::Var> + Sized;
}

fn thing<F: WithVar>(a: &F::Var, b: F::Var) {
    a + b;
}
```

I expected this to compile, but instead it errors out:
```
error[[E0369]](https://doc.rust-lang.org/stable/error-index.html#E0369): cannot add `<F as WithVar>::Var` to `&<F as WithVar>::Var`
  --> src/lib.rs:13:7
   |
13 |     a + b;
   |     - ^ - <F as WithVar>::Var
   |     |
   |     &<F as WithVar>::Var
   |
help: consider introducing a `where` clause, but there might be an alternative better way to express this requirement
   |
12 | fn thing<F: WithVar>(a: &F::Var, b: F::Var) where &<F as WithVar>::Var: Add<<F as WithVar>::Var> {
   |                                             ++++++++++++++++++++++++++++++++++++++++++++++++++++

For more information about this error, try `rustc --explain E0369`.
```
See this in action at this playground link: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=e17c4bf883f0692f6f02ac78a2560840

### Meta
This happens on the latest stable (1.66), as well as beta and nightly.
Repository: PowerToys
Issue: Add recursion to Resize Pictures features
Labels: Idea-Enhancement,Product-Image Resizer

### Description of the new feature / enhancement

By clicking on a folder, I would like to resize all the images contained in it and in all its subfolders.

### Scenario when this would be used?

This functionality would be very useful when you have large quantities of images organized in folders, to resize them in bulk for publication, or to create thumbnails, etc.

### Supporting information

_No response_
Repository: deno
Issue: Weird behavior when requesting network permissions before using fetch
Labels: permissions,needs investigation

Hello. I have a program that uses `Deno.permissions.request` to request `net` permissions before attempting to actually make the network requests. I have the network requests wrapped in a `try catch` so it silently fails if the user denied the first request. However, it's prompting the user to allow the permission a second time? I understand this isn't intended behavior? The message is even different between the two prompts, interchanging "net" and "network".

https://github.com/RuiNtD/ArtemisWaypointMigrator/blob/a3f38352518ea5de1d9534dabb951bd8e7dda52c/migrate.ts#L63-L79

![image](https://user-images.githubusercontent.com/1149870/208856178-5255ef9c-1b76-43d4-86f5-c57aebbe33b5.png)
![image](https://user-images.githubusercontent.com/1149870/208856193-4a497610-b103-46b0-8bd3-762cb2afbf9a.png)
Repository: flutter
Issue: Locally simulating web apps running on the same domain
Labels: c: new feature,tool,platform-web,P3,customer: dent,team-web,triaged-web

We have multiple web apps hosted on the same domain. We want to share data between these apps in indexed db (or local storage). When running these apps locally for debugging, we need to assign different ports (--web-port). But the browser then maintains separate local storages for these apps and no data is shared.

Can we simulate separate web apps under the same domain when starting locally?
Repository: rust
Issue: `cargo test` fails with fatal runtime error on `stable-aarch64-apple-darwin`
Labels: I-crash,A-LLVM,O-macos,T-compiler,S-waiting-on-author,C-bug

### Code

```Rust
#[test]
fn test() {
    assert!(false);
}
```

### Meta

`rustc --version --verbose`:
```
rustc 1.66.0 (69f9c33d7 2022-12-12)
binary: rustc
commit-hash: 69f9c33d71c871fc16ac445211281c6e7a340943
commit-date: 2022-12-12
host: aarch64-apple-darwin
release: 1.66.0
LLVM version: 15.0.2
```

### Error output

```
helloworld ❯ RUST_BACKTRACE=1 cargo test
    Finished test [unoptimized + debuginfo] target(s) in 0.00s
     Running unittests src/main.rs (target/debug/deps/helloworld-ed0dadb8f7ac71f4)

running 1 test
fatal runtime error: failed to initiate panic, error 5
error: test failed, to rerun pass `--bin helloworld`

Caused by:
  process didn't exit successfully: `/Users/klasseg/Workspace/rust/helloworld/target/debug/deps/helloworld-ed0dadb8f7ac71f4` (signal: 6, SIGABRT: process abort signal)
```

No backtrace is printed.


The error is solved temporarily if I clean and rerun using: 
```
cargo clean && env -i PATH="$HOME/.cargo/bin:/usr/bin:/bin" cargo test
```
Repository: rust
Issue: Add help for value moved multiple times in the same guard
Labels: A-diagnostics,T-compiler

Given the following code ([Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=c8e217552cdc94e049a6c441e226cdaf)):

```rust
struct NonCopy;

fn test(_x: NonCopy) -> bool { false }

fn main() {
    let x = NonCopy;

    match 0 {
        1 | -1 if test(x) => {}
        _ => {}
    }
}
```

The current output is:

```
error[E0382]: use of moved value: `x`
 --> src/main.rs:9:24
  |
6 |     let x = NonCopy;
  |         - move occurs because `x` has type `NonCopy`, which does not implement the `Copy` trait
...
9 |         1 | -1 if test(x) => {}
  |                        ^ value used here after move
  |
note: consider changing this parameter type in function `test` to borrow instead if owning the value isn't necessary
 --> src/main.rs:3:13
  |
3 | fn test(_x: NonCopy) -> bool { false }
  |    ----     ^^^^^^^ this parameter takes ownership of the value
  |    |
  |    in this function
```

This happens because the guard is executed multiple times for an or-pattern. Maybe this should be explained in the diagnostic, similar to the diagnostic emitted in loops ("value moved in previous iteration of loop")?

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: vscode
Issue: Allow extensions to set the body of the new comment editor
Labels: feature-request,api,api-proposal,comments

This would enable GitHub's "suggestion" feature in the GitHub Pull Request and issues extension:

1. When reviewing some's change, you want to leave a comment that contains a suggested change.
2. You hit the + to create a comment.
3. You write a message in the comment editor, then hit a button in the comment widget which appends a GitHub style suggestion block text to your in-progress comment.
Repository: flutter
Issue: [google_maps_flutter] Google Maps is not fully displayed when is wrapped in ClipRRect 
Labels: platform-android,a: platform-views,p: maps,package,has reproducible steps,P2,found in release: 3.3,platform-views: hc,found in release: 3.7,team-android,triaged-android

I am using google map package in my app
it has margin in right and bottom side
 google_maps_flutter: ^2.2.2
flutter 3.3.10
platform android 33
![Screenshot_1671624776](https://user-images.githubusercontent.com/62293873/208902669-3268fce6-719e-478d-af40-ff4ee9d1ab1e.png)

minimal code 

 just wrap google map widget into ClipRRect
Repository: storybook
Issue: addon-google-analytics: not compatible with Storybook 7 beta
Labels: help wanted,api: addons

### Describe the bug

I upgraded to Storybook 7 beta 12 using the automatic method (`npx storybook@next upgrade --prerelease`) + automigrations. This gave me the following package.json dependencies (amongst others):
```
"storybook": "^7.0.0-beta.12",
"@storybook/angular": "^7.0.0-beta.12",
"@storybook/addons": "^7.0.0-beta.12",
"@storybook/addon-google-analytics": "^6.3.0-next.1",
```
I then reset my workspace (I guess I probably deleted package-lock.json) and tried to do `npm i` again.
This is what I get:
```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: my-project
npm ERR! Found: @storybook/addons@7.0.0-beta.13
npm ERR! node_modules/@storybook/addons
npm ERR!   dev @storybook/addons@"^7.0.0-beta.12" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @storybook/addons@"^6.1.14" from @storybook/addon-google-analytics@6.3.0-next.1
npm ERR! node_modules/@storybook/addon-google-analytics
npm ERR!   dev @storybook/addon-google-analytics@"^6.3.0-next.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
```

So I understand that **addon-google-analytics does not yet support Storybook 7 beta**.

### System

```shell
System:
    OS: macOS 12.6
    CPU: (8) x64 Apple M1
  Binaries:
    Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
  npmPackages:
    @storybook/storybook-deployer: ^2.8.6 => 2.8.12
```
Repository: three.js
Issue: Derivatives should be computed before alpha test 
Labels: Suggestion

### Description

Hi, 

The computation of tangents for normal mapping relies on computing derivatives in xyz and uv space. Right now in MeshStandardMaterial `alphatest_fragment` comes before those computations. I found that on some devices derivatives on the pixels right next to discarded ones are not computed and set to 0, while on other devices alpha test does not impact the gradient computation. Below I used a custom shader that uses `perturbNormal2Arb` to exaggerate the issue.

![Screenshot from 2022-12-20 17-04-39](https://user-images.githubusercontent.com/6727524/208909035-267f9781-b012-46b0-9454-fbbf4ef51de4.png)

What solves it: I tried moving the computation of derivatives to before `alphatest_fragment`, it helps. 

![Screenshot from 2022-12-20 17-05-25](https://user-images.githubusercontent.com/6727524/208909056-917fa441-ebdf-405c-9a30-95362d96c892.png)

Important: It is a hardware/software dependent issue. It only reproduces on Linux with Nvidia drivers. I observe this on two PCs with different driver versions. My current setup is Ubuntu 22.04, Nvidia drivers 520.56.06. The behavior is same in Chrome and Firefox. 

What can be done: 

1) Move computation of derivatives needed in `perturbNormal2Arb` and other places to before `alphatest_fragment`.
2) Do nothing as it is not a common issue, just leave the issue opened for people who will encounter this problem. 

Let me know if you want to go for the 1st option, maybe I could come up with a PR. 

### Reproduction steps

Described above


### Code

-

### Live example
The bug is hardware dependent. 

### Version

r148

### Device

Desktop

### Browser

Chrome, Firefox

### OS

Linux
Repository: storybook
Issue: [Bug]: useArgs throws an error when used in a story in an mdx file
Labels: bug,needs triage

### Describe the bug

Trying to use `useArgs` inside an MDX file.

```
export const Template = (args) => {
  
    const [_, updateArgs] = useArgs();
    
    return (
        <Box>
            <Button onClick={()=>{updateArgs({isOpen: true})}}>
                Open Drawer
            </Button>
            
            <Drawer
                isOpen={args.isOpen}
                placement={args.right}
                onClose={args.onClose}
            >
              ...
            </Drawer>
        </Box>
    )
};


<Canvas>
    <Story 
        name="Drawer"
        args={{
            isOpen: false,
            placement: 'right',
            onClose: ()=>{},
        }}
    >{Template.bind({})}</Story>
</Canvas>

<ArgsTable story={"Drawer"}/>
```

UpdateArgs works and then throws an error of "Storybook preview hooks can only be called inside decorators and story functions".

### To Reproduce

_No response_

### System

```shell
tried to run npx sb@next info,  but this results in "unexpected token '||='
```


### Additional context

_No response_
Repository: pytorch
Issue: first class dims leak memeory
Labels: triaged,module: functorch

The new PyCode_Get* functions return new references. So decref are missing and we leak memory right now.
https://github.com/pytorch/pytorch/blob/15af4b1ceea3b689354ad664675b930486804c8e/functorch/csrc/dim/dim.cpp#L1447

cc @zdevito 

cc @zou3519 @Chillee @samdow @soumith
Repository: pytorch
Issue: Segmentation faults in DataLoader (in latest torch version).
Labels: needs reproduction,module: dataloader,triaged

### 🐛 Describe the bug

I'm experiencing segmentation faults in the dataloader.

# To Reproduce

This happens with `num_workers=16` or `12`, `8`, `4`, `3`. 

The Dataloader doesn't segfault when num_workers isn't set.

# Expected behavior

No segfaults

# Relevant snippet from code
```python
dataloader = torch.utils.data.DataLoader(train_data, shuffle=True,
                                         batch_size=batch_size,
                                         num_workers=16)
```

# Trace

```
ERROR: Unexpected segmentation fault encountered in worker.
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[20], line 38
     36 errG = criterion(output, labels)
     37 errG.backward()
---> 38 D_G_z2 = output.mean().item()
     39 optimizerG.step()
     41 # Save Losses for plotting later

File /lab/mlenv/lib/python3.10/site-packages/torch/utils/data/_utils/signal_handling.py:66, in _set_SIGCHLD_handler.<locals>.handler(signum, frame)
     63 def handler(signum, frame):
     64     # This following call uses `waitid` with WNOHANG from C side. Therefore,
     65     # Python can still get and update the process status successfully.
---> 66     _error_if_any_worker_fails()
     67     if previous_handler is not None:
     68         assert callable(previous_handler)

RuntimeError: DataLoader worker (pid 139803) is killed by signal: Segmentation fault. 
```

I've skimmed through earlier issues but those were closed and apparently fixed.

kind regards
Max

### Versions

PyTorch version: 1.13.1+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] (64-bit runtime)
Python platform: Linux-5.15.0-56-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4090
Nvidia driver version: 525.60.11
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.24.0
[pip3] torch==1.13.1
[pip3] torchvision==0.14.1
[conda] Could not collect


cc @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: stable-diffusion-webui
Issue: [Feature Request]: Redesign the structure of ui-config.json
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 ?

Currently, it is very nested, so I suggest to make it more readable by redesigning its structure. As an example:
```json
{
    "txt2img/Prompt/visible": true,
    "txt2img/Prompt/value": "",
    "txt2img/Negative prompt/visible": true,
    "txt2img/Negative prompt/value": "",
    "txt2img/Sampling Steps/visible": true,
    "txt2img/Sampling Steps/value": 20,
    "txt2img/Sampling Steps/minimum": 1,
    "txt2img/Sampling Steps/maximum": 150,
    "txt2img/Sampling Steps/step": 1,
    "txt2img/Sampling method/visible": true,
    "txt2img/Sampling method/value": "Euler a"
}
```
to this:
```json
{
    "txt2img": {
        "Prompt": {
            "visible": true,
            "value": ""
        },
        "Negative prompt": {
            "visible": true,
            "value": ""
        },
        "Sampling Steps": {
            "visible": true,
            "value": 20,
            "minimum": 1,
            "maximum": 150,
            "step": 1
        },
        "Sampling method": {
            "visible": true,
            "value": "Euler a"
        }
    }
}
```

### Proposed workflow

1. Do this

### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Can Scalable Diffusion usable on WebUI?
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 ?

![sample_grid_0](https://user-images.githubusercontent.com/116774664/208929656-3300ffd2-1661-4e05-8661-5df7c2b49613.png)
![sample_grid_1](https://user-images.githubusercontent.com/116774664/208930817-75f2b01e-19a6-4d3e-8b6a-511249caecac.png)

https://github.com/facebookresearch/DiT

It could be cherry-picking, but from what has been shown, it is outputting a very clear image unlike other AIs that has distorted silhouette. It looks pretty good.

### Proposed workflow

I just wanted to let you know if its existence was unknown. If possible, I'd like this to be available in the WebUI.

### Additional information

_No response_
Repository: rust
Issue: Tracking Issue for closures in const contexts
Labels: C-tracking-issue,A-const-eval

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for declaring const closures.
The feature gate for the issue is `#![feature(const_closures)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement the feature (#106004)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

* `for<'a> const static async move || {}` (keyword order?)

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->