sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: tutorial_code/calib3d/camera_calibration crashes with cryptic errors
Labels: category: documentation,category: calib3d

##### System information (version)

- OpenCV => 3.2.0
- Operating System / Platform => Raspbian
- Compiler => GNU

##### Detailed description

- I am following this tutorial: https://docs.opencv.org/master/d4/d94/tutorial_camera_calibration.html
- The camera calibration sample crashes with cryptic errors that don't indicate what's wrong.
- The parameters, image list, and images I am using are checked in here: https://github.com/01binary/calibration
- All of the images have been taken with the same Raspberri Pi infrared camera by using raspistill command, so they are guaranteed to have the same width, height, and pixel format.
- I am using the asymmetric circle grid with 5 circles width and 4 circles height. I downloaded this image from OpenCV repository and printed it on 11x17 sheet of paper, so it's guaranteed to be a standard/known pattern.

##### Steps to reproduce

Clone OpenCV and OpenCV Contrib into home directory (~)
Make OpenCV

```
makedir -p build && cd build

cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D WITH_TBB=ON -D BUILD_NEW_PYTHON_SUPPORT=ON -D WITH_V4L=ON -D INSTALL_C_EXAMPLES=ON -D INSTALL_PYTHON_EXAMPLES=ON -D BUILD_EXAMPLES=ON -D WITH_QT=ON -D WITH_GTK=ON -D WITH_OPENGL=ON -DOPENCV_EXTRA_MODULES_PATH=../opencv_contrib-master/modules ../opencv-master
```

Build OpenCV

```
cmake --build .
```

Clone my repository with calibration config

```
cd ~/Desktop
git clone https://github.com/01binary/calibration.git
cd calibration
```

Run the sample

```
~/build/bin/example_tutorial_camera_calibration ./default.xml
```
Repository: terminal
Issue: Implement synchronized update control sequences
Labels: Product-Conhost,Area-VT,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

https://gitlab.com/gnachman/iterm2/-/wikis/synchronized-updates-spec

The goal of synchronized updates is to avoid showing a half-drawn screen, such as while paging through a document in an editor.

A new control sequence is proposed that indicates the beginning and end of a update. No new content should be rendered by the terminal emulator until the update ends, at which point any changes made during the update should be applied atomically.

The purpose of this sequence is to provide a hint to the terminal emulator about how to draw atomically. If it turns out to be too difficult to do under some particular input, the hint can be safely ignored

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->


```[tasklist]
### Tasks
```
Repository: electron
Issue: Document the known differences of Electron's Node.js fork
Labels: enhancement :sparkles:,documentation :notebook:,status/confirmed

Mentioned in #26560, here's a separate issue to track it.

### Preflight Checklist

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem Description

#26560 was about the `timeout` option of the `vm` module not working in the main process. It looks like some of the Node.js tests [are disabled](https://github.com/electron/electron/blob/e017d8714e75fdc861af612404ea67229e827665/script/node-disabled-tests.json). So I must assume there are some known differences between Electron and Node.js

Another thing I came across a few months ago is that Electron uses BoringSSL and not OpenSSL.

### Proposed Solution

When searching for "electron node.js differences" I only found this page https://www.electronjs.org/docs/development/electron-vs-nwjs

What I propose is a similar page titled "Differences between Node.js and Electron's Node.js fork". This page will

1. Establish that Electron even uses a fork and not vanilla Node.js (this is not obvious to everyone)
2. List known issues with the fork linking to the GitHub issue (e.g. #26560)
3. Known differences that are deliberate with a short explanation, e.g. the use of BoringSSL.

### Additional Information

From the top of my head I've encounter at least these three:

1. vm timeout (#26560)
2. BoringSSL (#20204)
3. Different ctrl+c handling than Node.js (#5273)

I'll keep adding more as they come up:

- https://github.com/electron/electron/issues/35801
- https://github.com/electron/electron/issues/34808 (wontfix)
- https://github.com/electron/electron/issues/21457
Repository: pytorch
Issue: torch.save writes file even when pickle fails
Labels: module: serialization,triaged

## 🐛 Bug

It should not write file if serialization fails

## To Reproduce

![image](https://user-images.githubusercontent.com/5674597/99633411-d9623c00-2a0c-11eb-9b07-efe30baf9bde.png)



cc @mruberry
Repository: go
Issue: io/fs: add clearer documentation for "unrooted" paths
Labels: Documentation,NeedsInvestigation

`io/fs` requires "unrooted" paths, but it is currently only documented in passing under `io/fs.ValidPath`.

This may be surprising to many developers starting to use `io/fs`. Eg, walking "/" on `os.DirFS` or `embed.FS` filesystems will fail. Walking "." is less obvious since this is traditionally associated with the current working directory which doesn't exist for virtual filesystems.

Cc @rsc
Repository: go
Issue: cmd/go: describe replacements in dependency modules in case of a build failure
Labels: NeedsDecision,FeatureRequest,modules

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version

go version go1.14.6 darwin/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="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/spground/Library/Caches/go-build"
GOENV="/Users/spground/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOOS="darwin"
GOPATH="/Users/spground/go"
GOPROXY="http://goproxy.cn,direct"
GOROOT="/usr/local/go"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/n1/tx8c68cs7dz04f741k98qn8r0000gp/T/go-build130682422=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

As discussion in #39358,  `replace` and `exclude` directive will be ignored in modules except main module. However, we only get some simple error build info like `build error in test.go:123:456`  when running go command such as `go test` or `go build` if  we forgot to add `replace` or `exclude` directive in `go.mod` file of main module. These simple error build info is not enough to  guide me to add what statement in `go.mod` file of main module.  Meanwhile,  these simple build error message does not hint to me that the problem is about `replace directive`  missing, which will get worse if i am not familiar with some dependent modules.
 
### What did you expect to see?

Do more work to find which dependency introducing problems. 

### What did you see instead?

go command such as `go test`, `go build` will show more detail message related in `replace directive` topic in situation  that `replace directive` missing in main module.
Repository: next.js
Issue: Es2018 Unicode Property Escapes Not working
Labels: good first issue,bug,Webpack

<!-- NOTE: This template is not optional. If you remove it or leave out sections there is a high likelihood it will be moved to the GitHub Discussions "Help" section -->

# Bug report

## Describe the bug

Reproduction: [codesandbox.io/s/muddy-cookies-9jr6z?file=/pages/index.js](https://codesandbox.io/s/muddy-cookies-9jr6z?file=/pages/index.js)

After upgrading to V 10.0.2 the ES2018 `Unicode Property Escapes` feature is not working anymore. The same works perfectly till V 10.0.1 Not sure if it is due to the impact of https://github.com/vercel/next.js/pull/18759

## Expected behavior

Since the upgrade is not a major one, expecting the feature to work with out any issues.

## System information

- OS: macOS,
- Browser NA
- Version of Next.js: [e.g. 10.0.2]
- Version of Node.js: [e.g. 12.18.2]
Repository: pytorch
Issue: RuntimeError: "threshold_cpu" not implemented for 'Half'
Labels: module: cpu,triaged,enhancement,module: half

## 🐛 Bug
I was trying to implement a half-precision network in PyTorch. Unfortunately, I have encountered the following error:
> RuntimeError: "threshold_cpu" not implemented for 'Half'

## To Reproduce

Steps to reproduce the behavior:
```python
import torch
import torch.nn as nn
import torch.nn.functional as F
from sklearn.datasets import load_boston

X, y = load_boston(return_X_y=True)
X, y = torch.tensor(X), torch.tensor(y)


class Net(nn.Module):

    def __init__(self):
        super(Net, self).__init__()
        self.fc1 = nn.Linear(X.shape[1], 64)
        self.fc2 = nn.Linear(64, 64)
        self.fc3 = nn.Linear(64, 1)

    def forward(self, x):
        x = F.relu(self.fc1(x))
        x = F.relu(self.fc2(x))
        x = self.fc3(x)
        return x


print(Net().half().forward(X[0].half()))
```

## Environment

- PyTorch version: 1.8.0a0+781e0ed
- Is debug build: False
- CUDA used to build PyTorch: None
- ROCM used to build PyTorch: N/A
- OS: CentOS Linux 8 (Core) (aarch64)
- GCC version: (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
- Clang version: Could not collect
- CMake version: version 3.18.2
- Python version: 3.8 (64-bit runtime)
- Is CUDA available: False
- CUDA runtime version: No CUDA
- GPU models and configuration: No CUDA
- Nvidia driver version: No CUDA
- cuDNN version: No CUDA
- HIP runtime version: N/A
- MIOpen runtime version: N/A


cc @VitalyFedyunin
Repository: godot
Issue: Joypad joystick input sensitivity regression (3.2.4 beta 2)
Labels: topic:input

**Godot version:**
3.2.4 beta 2


**OS/device including version:**
Windows 10 64bit


**Issue description:**
I may have a slightly drifting analog stick on my joypad, but in 3.2.3 I am getting none or hardly any random joystick inputs, whereas in 3.2.4 beta I am getting loads (causing interference with other input events.)


**Steps to reproduce:**
The minimal reproduction project spits out any unhandled events, I am getting none in 3.2.3, but here is what is happening in 3.2.4 beta 2 (ignore the meta/shift presses, that was me capturing the image):
![image](https://user-images.githubusercontent.com/1631516/99643918-26e4b480-2ab2-11eb-95d8-c964bc68891e.png)


**Minimal reproduction project:**
[InputEcho.zip](https://github.com/godotengine/godot/files/5565592/InputEcho.zip)
Repository: TypeScript
Issue: Convert named tuple into object literal type.
Labels: Suggestion,Awaiting More Feedback,Domain: Refactorings

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms
refactor
<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

Provide a refactor that convert named tuple into object literal type.

<!-- A summary of what you'd like to see added or changed -->

## Use Cases
Now we have named tuple. 
It's common to write a tuple to pass multiple value.
As time goes on, you may add many other fields into tuple.
You cannot take a subsequence in the middle or the end of the tuple.
If we could convert that into an object, That would be useful.

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

```ts
type Tuple = [number, number]

function aggregate(items: number[]): Tuple {
  // ...
  return [min, max]
}

const [ min, max ] = aggregate(items)

```

Growth to

```ts
type Tuple = [number, number, number, number, number, number]

function aggregate(items: number[]): Tuple {
  // ...
  return [min, max, avg, mid, first, last]
}

const [ min, max, avg, mid, first, last ] = aggregate(items)

```

If we want first and last only

```ts

const [ , , , , first, last ] = aggregate(items) // too many '.'

const result = aggregate(items);
const first = result[4] // magic number
const last = result[5]  // magic number
```

If we have the refactor

```ts
// add names into tuple
type Tuple = [min: number, max: number, avg: number, mid: number, first: number, last: number]

// apply refactor
type Tuple = {min: number, max: number, avg: number, mid: number, first: number, last: number}

function aggregate(items: number[]): Tuple {
  // ...
  return {min, max, avg, mid, first, last}
}

const { first, last } = aggregate(items)

```



## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [ ] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: pytorch
Issue: torch.eye(d) is slow and hogs cpu for d >= 182
Labels: module: performance,good first issue,module: cpu,triaged,module: multithreading

## 🐛 Bug

I stumbled upon excessive CPU usage for my training code running on GPU. After some investigations I found the culprit.
It basically was
```
x = torch.eye(256).to('cuda') 
```

## To Reproduce

### This is quick and loads single CPU core.
```
%%timeit
    torch.eye(181)
6.43 µs ± 218 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)
```
### This is 3 times slower and hogs 30 cores.
```
%%timeit
    torch.eye(182)
21.2 µs ± 84.8 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
```
## Environment

I tested on server with 72 Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz cores (hyper-threading is on)

```
% python3 collect_env.py

Collecting environment information...
PyTorch version: 1.6.0
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.3 LTS (x86_64)
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Clang version: Could not collect
CMake version: version 3.10.2

Python version: 3.6 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti
GPU 4: GeForce RTX 2080 Ti
GPU 5: GeForce RTX 2080 Ti
GPU 6: GeForce RTX 2080 Ti
GPU 7: GeForce RTX 2080 Ti

Nvidia driver version: 440.100
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.18.2
[pip3] pytorch-wavelets==1.2.2
[pip3] torch==1.6.0
[pip3] torchvision==0.4.2
[conda] Could not collect
```


cc @VitalyFedyunin @ngimel
Repository: create-react-app
Issue: while creating react app 
Labels: stale

ERR! Unexpected end of JSON input while parsing near '...:{'shasum':'ef16c2018'
ERR! A complete log of  this can be found in 👍 
ERR!  C:\Users\Vaishnavi Karil\AppData\Roaming\npm-cache\_logs\2020-11-19T-11_51_03_447Z-debug.log
Repository: godot
Issue: Steam controller not detected 
Labels: bug,topic:input

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
v3.2.3 stable offical

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Void linux

**Issue description:**
<!-- What happened, and what was expected. -->
Steam controller not detected with or without https://github.com/kozec/sc-controller.  
If i use sc-controller and emulate kb and mouse that works but if i try to emulate example xbox-controller
it ignores any input, i think that is because godot does not even detect it as joypad at all for some reason :(...
Input.get_connected_joypads() gives an empty array.
It was expected to work :)


**Steps to reproduce:**
Connect steam controller  and run any project

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
Any project + steamcontroller
Repository: flutter
Issue: [proposal] Z-index in Stack widget
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

Hello, yesterday I have reported spurious lack of functionality in flutter and without it I cannot complete game migration. I have tried all proposed ways proposed on stackoverflow, Flutter cummunity silent about solution also
I have found another similar feature request here  https://github.com/flutter/flutter/issues/70836 just its usecase is simple
So I am asking to reopen issue:

https://github.com/flutter/flutter/issues/70758#issuecomment-729675908

And implement it adding zindex to positioned and animated Position widgets or creating new widget ZIndex

It will simplify layouting dranatically as well as games cretion

Thank you
Repository: create-react-app
Issue: CVE-2020-7774 Security finding
Labels: stale,needs triage,issue: bug report

A security find was found in the y18n library. Fixed in version 5.0.5. Can you update the library?

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7774
Repository: PowerToys
Issue: [Run] Refactor Plugins UpdateIconPath
Labels: Help Wanted,Product-PowerToys Run,Issue-Refactoring

"Abstracted out as I think most plugins have to do this.  This way we're consistent."

_Originally posted by @crutkas in https://github.com/microsoft/PowerToys/pull/8062#discussion_r525622227_

https://github.com/microsoft/PowerToys/blob/9144123f32a6b938ddd256bc459e1acf93d5c906/src/modules/launcher/Plugins/Microsoft.Plugin.Folder/Main.cs#L89-L92

https://github.com/microsoft/PowerToys/blob/9144123f32a6b938ddd256bc459e1acf93d5c906/src/modules/launcher/Plugins/Microsoft.Plugin.Shell/Main.cs#L280-L290

https://github.com/microsoft/PowerToys/blob/9144123f32a6b938ddd256bc459e1acf93d5c906/src/modules/launcher/Plugins/Microsoft.Plugin.Uri/Main.cs#L159-L169
Repository: create-react-app
Issue: proxy server config error::: Must use import to load ES Module
Labels: stale,needs triage,issue: bug report

## Description 

Crashing when running npm start with setupProxy.js
I configured proxy server manually, created setupProxy.js in my `src` folder. The problem is that I'm using new ES6 modules in node.js and when I'm running `npm start` I get this error:

Must use import to load ES Module: C:\Users\d\projects\v\src\setupProxy.js
require() of ES modules is not supported.
require() of C:\Users\d\projects\v\src\setupProxy.js from C:\Users\d\projects
\v\node_modules\react-scripts\config\webpackDevServer.config.js is an ES module file as it is a .js file
whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as
ES modules.
Instead rename setupProxy.js to end in .cjs, change the requiring code to use import(), or remove "type": "module
" from C:\Users\d\projects\v\package.json.


Proxy config:

import { createRequire } from 'module';

const require = createRequire(import.meta.url);

const proxy = require('http-proxy-middleware');

const target = process.env.PROXY_TARGET;

if (!target) {
  throw new Error('Please specify the proxy target in your environment variables.');
}

export default (app) => {
  app.use(
    '/api/v1',
    proxy({
      target,
      changeOrigin: true,
      secure: false,
    }),
  );
};


### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

* create-react-app proxy config
* create-react-app Must use import to load ES Module
* webpack Must use import to load ES Module

### Environment

System:
    OS: Windows 10 10.0.17763
    CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
  Binaries:
    Node: 14.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 83.0.4103.61
    Edge: Spartan (44.17763.831.0)
    Internet Explorer: 11.0.17763.771
  npmPackages:
    react: ~16.13.1 => 16.13.1
    react-dom: ~16.13.1 => 16.13.1
    react-scripts: 4.0.0 => 4.0.0
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

1. install node.js 14+
2. set "type": "module" in your package.json
3. config a proxy server using setupProxy.js file
4. run npm start

### Expected behavior

Should run dev server with proxy

### Actual behavior

crashing with error
Repository: frp
Issue: Dashboard的Proxies清單中，未列出XTCP類型的Proxy
Labels: todo

<!-- From Chinese to English by machine translation, welcome to revise and polish. -->

<!-- ⚠️⚠️ Incomplete reports will be marked as invalid, and closed, with few exceptions ⚠️⚠️ -->
<!-- in addition, please use search well so that the same solution can be found in the feedback, we will close it directly -->
<!-- for convenience of differentiation, use FRPS or FRPC to refer to the FRP server or client -->

**What version of frp are you using** 
- frpc v0.34.2
  - amd64 Windows 10 2004 Build 19041.630
- frps v0.34.2
  - amd64 Ubuntu 20.04
- (都是使用Release的Binary)

**Description of errors**
在Dashboard裡面Proxy只有顯示TCP、UDP、HTTP、HTTPS和STCP，並沒有XTCP。
想請問這是預期的結果嗎?
因為XTCP的Proxy數量在Overview頁面的右下角的圓餅圖，確實有顯示出正確的數量。
但是左側的Proxies清單裡面，並不包含XTCP的分頁。

**Supplementary information**
![image](https://user-images.githubusercontent.com/12500621/99690753-72538e80-2ac3-11eb-9fac-06fcf47fedff.png)