sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Stitcher problem
Labels: question (invalid tracker),category: stitching

##### System information (version)
- OpenCV => 3.4.7

##### Detailed description

<!-- your description -->
And when I do Stitcher,

```.cpp
Stitcher::Status Status = Stitcher -> Stitch (IMGS, PANO); 
```
Is able to achieve the splicing function I need.

But when I try to call estimateTransform first and then composePanorama, I get an error : **imgs.size() ! = imgs_.The size()**. 

I looked at the source code and it seems that the matchImages function in the estimateTransform will "Leave only images we are sure are from the same panorama", which causes imgs_ to be reassigned, But the composePanorama function still calls indices_, 

```.cpp
Stitcher::Status s = stitcher->estimateTransform(imgs2);
stitcher->composePanorama(imgs2, pano);
```
Because imgs_ is reassigned inside the class, the size will change. so  CV_Assert(imgs.size() == imgs_.size()) will happen

According to the following code and the input image, the result will be reported as an error, but comment out   CV_Assert(imgs.size() == imgs_.size())  in the composePanorama(), and the result can be output normally
```.cpp
        imgs.push_back(cv::imread("/home/yangod/cvhandle/source7/a.jpg"));
	imgs.push_back(cv::imread("/home/yangod/cvhandle/source7/b.jpg"));
	imgs.push_back(cv::imread("/home/yangod/cvhandle/source7/c.jpg"));
	imgs.push_back(cv::imread("/home/yangod/cvhandle/source7/d.jpg"));

	Mat pano;
	Ptr<Stitcher> stitcher = Stitcher::create(mode);
	Stitcher::Status status = stitcher->stitch(imgs, pano);
	
	if (status != Stitcher::OK)
	{
		cout << "Can't stitch images, error code = " << int(status) << endl;
		return 1;
	}
	stitcher->composePanorama(imgs2, pano); //可以加入新的图片集imgs(保证与之前的大小数量一致)
```




![a](https://user-images.githubusercontent.com/44219258/187455434-d06b066f-fd3d-4d0a-a4de-c03a47c66556.jpg)
![b](https://user-images.githubusercontent.com/44219258/187455679-6448a104-d3cc-4577-95c4-05b2372be86f.jpg)
![c](https://user-images.githubusercontent.com/44219258/187455695-a4fdcca0-547f-497f-892e-834f74f01842.jpg)
![d](https://user-images.githubusercontent.com/44219258/187456311-045251dd-4c5f-4a24-a697-954a49001288.jpg)
Repository: PowerToys
Issue: Word count function
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Hope to add keyboard shortcuts to count the word count of the selected text.

### Scenario when this would be used?

When writing

### Supporting information

_No response_
Repository: storybook
Issue: buildStoriesJson feature produces error when "stories" is set to async function
Labels: bug,needs triage

In "main.js" I am using an [async function](https://storybook.js.org/docs/react/configure/overview#with-a-custom-implementation) to set which story files to load. This works correctly until I add the `buildStoriesJson` and I get an error.

<img width="727" alt="Screen Shot 2022-08-30 at 10 48 57 AM" src="https://user-images.githubusercontent.com/23062081/187485449-a8e7aebe-7258-48ed-b9c5-4f9197c439e3.png">

This is my "main.js" file:
```
module.exports = {
  stories: async (list) => [...list, ...findStories()],
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/preset-scss',
    '@storybook/addon-a11y',
  ],
  features: {
    buildStoriesJson: true
  },
};
```

Using `@storybook/react@6.5.10`
Repository: go
Issue: x/build/cmd/fetchlogs: add a -since flag
Labels: Builders,NeedsFix

When searching for test faillures, my workflow is as follows:

```
> fetchlogs -repo tools -n <some large number, usually 3000>
```

Followed by

```
> greplogs -md -l -e 'FAIL: TestName' -since=<date>
```

The problem is, if my `-n` value is too small I may silently miss test failures in my `-since` range. Also, without doing a bit of digging it's not easy to see how far back `fetchlogs` results go.

A nice solution to this problem would be to add a `-since` flag to `fetchlogs`, telling it to keep searching dashboards until it finds a build where both the repo revision date and go revision date are too old.

CC @bcmills
Repository: TypeScript
Issue: JSX attributes should use double quote by default
Labels: Suggestion,Help Wanted,Experience Enhancement

Like prettier default behavior: Although you set using single quotes in javascript, but jsx attributes still using double quotes.

[prettier playgound](https://prettier.io/playground/#N4Igxg9gdgLgprEAuc0DOMAEBDTBeTAcgEYAmAZkIB0oaAzAVyjBgEtpMBhCAWwAcAFAEpMwGlRgAnODAaSomADwATVgDdMYADbY0aAHLYecPFVSxsrKHElmAfIoD0qtXZoBfEABoQEPm3RkUGxJSQgAdwAFEIQ0ZBBsLXDsAE84nwAjSWwwAGsZAGUjOAAZKzhkOkS0OEzsvMK+HKsAc2QpBlqQOB4MuGVlfpLsKBaGbBa4ADEISR5sGDZR+OwGGAhvEAALGB4tAHUt1ng0JrA4Atjj9WOU+LA9TasayRhI7Jb5yuqugCs0AAeBVaWjgAEUGBB4N8tDUfE1JC94hlsH0tJs+JIrDB9qxlDAtsgABwABnhYRq+2yfHimLgLzUFR8AEdIfB3n44ihdABaaz9fqbaSs1jSd4TL5IKqwro1HisdqSTo+NAg8FsipSn4+GCo3H4wlIUg67KsLStbg8SXdNAAVk2DBqABVUVzpXCQGpOgBJKCDWAFMBY-wAQT9BRgKVBMJq7ncQA)

I think the reason is jsx isn't toatally javascript, it's also mark language. When deal with jsx attributes, we should using mark language quotes style.

In fact, react users may using the single quote or double quotes for javascript. But every users must use double quotes for jsx attributes.

Like https://github.com/microsoft/vscode/issues/143164#issuecomment-1042328896  comment, we may need a new setting for this.

```
Version: 1.71.0-insider (Universal)
Commit: 16faaf4eb07424d5d7dba7d12bffd64309c283f7
Date: 2022-08-29T15:28:34.899Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0
Sandboxed: Yes
```

@mjbvz @nifte @rzhao271 


https://user-images.githubusercontent.com/41773861/187392236-3e748945-9eb3-4ea9-84c4-eba094ac2159.mov
Repository: rust
Issue: match-then-remake `Result` doesn't optimize away for some payload widths
Labels: E-easy,A-LLVM,I-slow,E-needs-test,T-compiler

As [the new codegen test](https://github.com/rust-lang/rust/pull/100693/files#diff-68a12d31335d7f061169500381ebaf9634034cf419332c16512355df8c8cfddeR16) confirms, matching and rebuilding a `Result<i32, u32>` optimizes away now (on x64).

However, it seemingly *doesn't* optimize away if the ok and error types are *64* bits:
```rust
pub fn result_nop_match_64(x: Result<i64, u64>) -> Result<i64, u64> {
    match x {
        Ok(x) => Ok(x),
        Err(x) => Err(x),
    }
}
```
https://rust.godbolt.org/z/fMn6aqWG8
```nasm
result_nop_match_64:
        mov     rax, rdi
        cmp     qword ptr [rsi], 0
        je      .LBB0_1
        mov     rcx, qword ptr [rsi + 8]
        mov     qword ptr [rax + 8], rcx
        mov     ecx, 1
        mov     qword ptr [rax], rcx
        ret
.LBB0_1:
        mov     rcx, qword ptr [rsi + 8]
        mov     qword ptr [rax + 8], rcx
        xor     ecx, ecx
        mov     qword ptr [rax], rcx
        ret
```

---

Interestingly, it *does* optimize away when there's another enum in the middle, like happens in the `?` desugaring.  From that same godbolt,
```rust
pub fn result_nop_traits_64(x: Result<i64, u64>) -> Result<i64, u64> {
    try {
        x?
    }
}
```
gives
```nasm
result_nop_traits_64:
        mov     rax, rdi
        movups  xmm0, xmmword ptr [rsi]
        movups  xmmword ptr [rdi], xmm0
        ret
```



<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: Fix convert path for fixed qparam ops (sigmoid and softmax)
Labels: oncall: quantization,low priority,triaged

### 🐛 Describe the bug

sigmoid is an op that works for both fp32 and quantized input: https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/native_functions.yaml#L4519

but we have a quantized sigomid module: https://github.com/pytorch/pytorch/blob/master/torch/ao/nn/quantized/modules/activation.py#L129-L148 this is confusing and we should remove it

## How to fix?
remove the quantized modules for all the modules in this list: https://github.com/pytorch/pytorch/blob/master/torch/ao/quantization/quantization_mappings.py#L163-L166


### Versions

master

cc @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: material-ui
Issue: [colorManipulator] Inconsistent output values with the `darken` function
Labels: bug 🐛,package: system

### Current behavior 😯

When using MUI's internal `darken` function ([material-ui/packages/mui-system/src/colorManipulator.js](https://github.com/mui/material-ui/blob/198f67996ca7983dd4530ee87af998f65a211899/packages/mui-system/src/colorManipulator.js)) we see very different color outputs depending on the format of the input color value. For example:

```js
/* All these values are the same color and written in different formats */
let hex = "#7B61FF";
let rgb = "rgb(123, 97, 255)";
let hsl = "hsl(250, 100%, 69%)";

let coefficient = 0.1; // Can be any value

darken(hex, coefficient) // returns rgb(110, 87, 229)
darken(rgb, coefficient) // returns rgb(110, 87, 229)
darken(hsl, coefficient) // returns hsl(250, 100%, 62.1%) which is very different than the first two
```

Preview (Left column is inputs, right column is outputs):
<img width="413" alt="image" src="https://user-images.githubusercontent.com/298336/187518764-bcefafbe-3969-4cd1-b3b5-a3a58fd8669f.png">

This is due to the way that the darken function manipulates colors. If it detects an hsl color, it will lower the lightness by the coefficient. However, if it is RGB (or is cast to RGB) the function will adjust each separate color component by the coefficient. The latter is a more naïve approach to darkening since the result is usually desaturated. 

### Expected behavior 🤔

Color adjustments should output a consistent color value regardless of input format. TinyColor's [darken function](https://github.com/bgrins/TinyColor/blob/2322a1a70a0cd075b98829d67dbd90228abebab4/tinycolor.js#L607-L613) is a good example; it always casts an input value to HSL and then makes the adjustment, outputting the same results for every color format. 

### Steps to reproduce 🕹

Live example: https://codesandbox.io/s/magical-dubinsky-zrehcj?file=/src/index.js

### Context 🔦

This is causing issues with keeping our design files in sync with our Figma mockups because not all color values are in the same base color format. 

### Your environment 🌎

_No response_
Repository: flutter
Issue: API verification of `ui.dart` not taking enums into account when validating against web
Labels: team,engine,platform-web,P2,team-web,triaged-web

As an example see: `DartPerformanceMode` enum added in https://github.com/flutter/engine/pull/35614, did not have matching members for web.
Repository: three.js
Issue: OrbitControls doesn't detect pointerup when off the DOM element
Labels: Needs Investigation

**Describe the bug**
The OrbitControls continue to manipulate the camera if a click+drag is released outside of the OrbitControls' DOM element.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to any three.js scene using OrbitControls, such as https://threejs.org/examples/#webgl_animation_keyframes
2. Click and drag starting in the scene and release the click with the cursor out of the scene.
3. Return the cursor to the scene without clicking and observe that the camera is still being controlled by the cursor movements.

**Expected behavior**
I would expect the camera to no longer be rotated by the cursor after releasing the click.

**Platform:**

 - Device: Desktop
 - OS: MacOS (likely impacts others too)
 - Browser: Chrome (likely impacts others too)
 - Three.js version: r143 (impacts other versions too)
Repository: godot
Issue: Renaming a node will show it's old name for a split second
Labels: bug,topic:editor

### Godot version

4.0 Alpha15

### System information

Win

### Issue description


https://user-images.githubusercontent.com/47016402/187533407-9983827b-4fa9-4b16-8ac3-23f3197cca1e.mp4



### Steps to reproduce

1. Add a node, 
2. select it and rename it
3. hit enter
4. watch it weirdly switch back to it's old name for a split second

### Minimal reproduction project

does not require a MRP
Repository: godot
Issue: Sprite get_rect() does not return the correct Rect2 position
Labels: discussion,topic:core

### Godot version

3.5 stable, 4.0 Alpha 15

### System information

Win

### Issue description

In both Godot 3.5 stable and Godot 4 Alpha 15 (and earlier) if you try to get the Rect2 of a Sprite using `get_rect()`, the resulting Rect2() will have the correct size, but not the correct position.

Instead, the Rect2 position will be the Sprites `offset` - halve of it's size (if `centered` property is enabled). If centered property is not enabled, the returned Rect2 position will be exactly the Sprite offset. Which by default is Vector2(0,0).

I would expect the Rect2 position to be the Sprite `position`+`offset`-`centered(halve the size)`.

### Steps to reproduce

1. Add a Sprite and give it a texture
2. position it somewhere in the scene
3. execute `print( $Sprite.get_rect() )`

### Minimal reproduction project

You are faster testing this without having to install a minimal project.
Repository: go
Issue: x/build/cmd/rundockerbuildlet: unable to start rundockerbuildlet on ppc64
Labels: Builders,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
I have not tested.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
debian@go-be-debian-1:~$ go env
GO111MODULE=""
GOARCH="ppc64"
GOBIN=""
GOCACHE="/home/debian/.cache/go-build"
GOENV="/home/debian/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="ppc64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/debian/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/debian/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.19"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.19/pkg/tool/linux_ppc64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOPPC64="power8"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="0"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2889172257=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?
I built the latest version of rundockerbuildlet on my amd64 dev machine.
<pre>
GOARCH=ppc64 GOOS=linux /usr/bin/go build -o rundockerbuildlet.ppc64 golang.org/x/build/cmd/rundockerbuildlet
</pre>
I created a systemd unit file to run rundockerbuildlet similar to other PPC64 builders, and the utility fails to start with the following error:
<pre>
Aug 30 20:30:39 go-be-debian-1 systemd[1]: Started Run Buildlets in Docker.
░░ Subject: A start job for unit rundockerbuildlet.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit rundockerbuildlet.service has finished successfully.
░░ 
░░ The job identifier is 4777.
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]: 2022/08/30 20:30:40 unable to retrieve EC2 user data: EC2MetadataError: failed to make EC2Metadata request
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]:         status code: 404, request id:
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]: caused by: 404 Not Found
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]: The resource could not be found.
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]:    
</pre>

### What did you expect to see?

This builder is not running on AWS. I wouldn't expect to see AWS related chatter causing a failure to start.

### What did you see instead?

The usual startup and status information for this utility.
Repository: neovim
Issue: Is there any options can set `popup-menu` 's scroll off value?
Labels: enhancement,completion

### Feature already in Vim?

Seems not

### Feature description

Sometimes when we navigate through the the pop-up menu but accidentally miss the result we want in subconscious

Maybe setting the scroll off in the pop-up menu would be a good idea :D

Are there any options that to set `popup-menu` 's scroll off?
Repository: flutter
Issue: Make `.ci.yaml` not hidden
Labels: team,team-infra,P3,triaged-infra

## Seen
CI tasks are defined in `//.ci.yaml`.  That means many search tools will ignore it without explicitly telling it not to.  For example, "ag **--hidden** channels_integration_test_ios".

## Expected
The CI file is an important part of adding new tests and it shouldn't be hidden.  Maybe it could be put somewhere like `//dev/ci/ci.yaml`
Repository: flutter
Issue: [Proposal] Make most shapes lerp
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

Right now, half the shapes can lerp into another, but not from another. You can lerp from `RoundedRectangleBorder` to `CircleBorder`, but not from `CircleBorder` to `RoundedRectangleBorder`. Check here:

<img width="967" alt="image" src="https://user-images.githubusercontent.com/351125/187567065-c130c01e-2d75-4320-b565-b29157acdd03.png">

Something like this would solve all our issues:
![image](https://user-images.githubusercontent.com/351125/187567257-e882ce24-9685-46c5-acf9-3346ea062c51.png)

1. Do we want this?
2. Is this implementation fine?
Repository: pytorch
Issue: [Profiler] Generic Tensor summary
Labels: module: bootcamp,oncall: profiler

### 🚀 The feature, motivation and pitch

The PyTorch profiler has several flags which enable optional functionality. One such flag is `record_shapes`, which is needed to assess kernel performance. However the scope of what is captured has gradually grown to include not only shape and dtype, but also [address, device, layout, and strides](https://github.com/pytorch/pytorch/blob/master/torch/csrc/profiler/collection.h#L51-L68). At the same time we have found applications for inspecting Tensors in other profiling contexts in the Python tracer for [`nn.Module` profiling](https://github.com/pytorch/pytorch/blob/master/torch/csrc/autograd/profiler_python.cpp#L305-L308), and soon optimizer profiling as well.

As PyTorch evolves various sharp edges have emerged: NestedTensors do not have a concept of strides, not all Tensors have storage, etc. We are also developing tooling in Python and the disparity between representations requires us to fall back to the lowest common denominator for analysis.

A more elegant and maintainable approach would be to have a single summary class which takes an `at::Tensor` and extracts a broadly useful summary which could then be conveniently bound into Python. This would harden the collection path by minimizing the boundary between profiler and TensorImpl/StorageImpl and provide a featureful analysis experience out of the box.

### Alternatives

_No response_

### Additional context

_No response_

cc @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb
Repository: pytorch
Issue: [Profiler] Snapshot CudaCachingAllocator on profile begin
Labels: module: bootcamp,oncall: profiler

### 🚀 The feature, motivation and pitch

One of the largest technical hurdles to memory profiling is deducing information about Tensors which were created before profiling began. PyTorch uses a custom [GPU allocator](https://github.com/pytorch/pytorch/blob/master/c10/cuda/CUDACachingAllocator.h) for fine grained control over GPU memory. One feature of this allocator is that it can expose a [detailed snapshot](https://github.com/pytorch/pytorch/blob/master/c10/cuda/CUDACachingAllocator.h#L151) of its current state. Moreover, [lightweight, always on source attribution](https://github.com/pytorch/pytorch/pull/82146) was recently added to CUDACachingAllocator. This information would go a long way towards disambiguating memory use for profiled regions and would provide a more complete picture of overall usage, and we should collect it in profiler.

### Alternatives

_No response_

### Additional context

_No response_

cc @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb
Repository: flutter
Issue: [Image_picker] Flutter web Popup menu start position is wrong on iOS
Labels: platform-web,p: image_picker,package,has reproducible steps,P2,browser: safari-ios,found in release: 3.1,found in release: 3.3,team-web,triaged-web

Export Flutter to web,
Test on iOS devices,
The image picker menu position will not be on the Button
use package `image_picker: ^0.8.5+3`

<details>
<summary>
The case of Flutter Web
</summary>

![](https://i.imgur.com/Mh6CzBu.jpg)
</details>

<details>
<summary>
General web page
</summary>

![](https://i.imgur.com//5Smo1mP.jpg)

</details>



<details>
<summary>
Code sample
</summary>



```dart
class _MyHomePageState extends State<MyHomePage> {
  WebViewController? _controller;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: _bodyContent(),
    );
  }

  _bodyContent() {
    return TextButton(
        style: TextButton.styleFrom(
          primary: Colors.blue,
        ),
        onPressed: () async {
          var getImage = await ImagePicker()
              .pickImage(source: ImageSource.gallery, maxWidth: 1600);
        },
        child: Text('Click'));
  }
}
```

</details>

<details>
  <summary>flutter doctor</summary>

```
[✓] Flutter (Channel stable, 3.0.0, on macOS 12.3.1 21E258 darwin-arm (Rosetta), locale zh-Hant-TW)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.69.0)
Scanning for devices is taking a long time...[✓] Connected device (8 available)
[✓] HTTP Host Availability

```

</details>


<!--
      Consider also attaching screenshots and/or videos to better
      illustrate the issue.

      You can upload them directly on GitHub.
      Beware that video file size is limited to 10MB.
-->
Repository: deno
Issue: Feature Request: loading ffi shared libs from Uint8Array directly
Labels: suggestion,FFI

The idea here is pretty simple, in addition to `Deno.dlopen` accepting a `string` or `URL`, lets also let it accept a `Uint8Array`. The reason for this is so we can start embedding shared libraries in javascript files, so that they can be downloaded at import time. This idea is already widely used with wasm binaries, so in my opinion it isnt a large stretch for ffi libraries either

[edit]
Further background on this idea is that currently we do not have a great way to package ffi shared libs alongside the rest of a deno library. Node solves this with node-gyp, and I believe precompiled binaries in some cases. In this case, we can just piggy-back off of existing javascript module imports.