sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Upgrade OpenEXR version
Labels: category: 3rdparty

##### System information (version)
- OpenCV => 3.4.7+

##### Detailed description
OpenEXR library has a memory leak in IlmThreadPool.cpp in version 2.3.0, please upgrade OpenEXR
https://www.cvedetails.com/cve/CVE-2018-18443/
https://github.com/AcademySoftwareFoundation/openexr/issues/350
https://github.com/AcademySoftwareFoundation/openexr/pull/412/files

OpenCV has this issue incorporated since this commit when OpenEXR was upgrade to 2.3.0: https://github.com/opencv/opencv/commit/878af7ada86efc3eb7bcc5eb011549a834455b90#diff-a47057f8b610809c98f4e3a6f8f1679bb9a64dc1ec6fc95ad4f5a3976112507d

##### Steps to reproduce
See https://github.com/AcademySoftwareFoundation/openexr/issues/350

##### Issue submission checklist

 - [x] 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 question without 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 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 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 latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [x] 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 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 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/
   -->
Repository: PowerToys
Issue: [Settings] Add restart button to restart warnings
Labels: Idea-Enhancement,Product-Settings,Area-User Interface,Priority-2,Cost-Small

_With the new settings ux (#12470) we have switched to a new settings ux and updated the styling._

---

### Description of the new feature / enhancement

I suggest to add a restart button to the restart warning in the settings ux for faster access to the restart function. (This makes only sense on pages other than the general page.)

**Addition**
If possible it would be great if settings will open on the same page where the button was clicked.

**Mock up**
![image](https://user-images.githubusercontent.com/61519853/130640998-fbf74b46-36c3-43f0-851a-f444aa337551.png)

### Scenario when this would be used?

When a user needs to restart the settings as admin from a other page than the general page without the need of switching the page.

### Supporting information

_No response_
Repository: PowerToys
Issue: [Settings] Aborting "Restart as admin" closes settings
Labels: Product-Settings,Priority-3

### Microsoft PowerToys version

0.43.0

### Running as admin

- [ ] Yes

### Area(s) with issue?

Settings

### Steps to reproduce

1. Clicking restart as admin button
2. Choosing "No" on UAC
3. Clicking "Ok" on error message box

### ✔️ Expected Behavior

After the error message box the settings window reopens in non-admin mode.

### ❌ Actual Behavior

After the error message box nothing happens.

### Other Software

_No response_
Repository: godot
Issue: instance created via instance() method nulls the material when 'local to scene' is set
Labels: bug,topic:rendering,needs testing

### Godot version

3.3 stable

### System information

Linux Mint

### Issue description

In case this is 'as designed' (but I really do hope not as it breaks everything ;-) ), I'll wait to post sample project and video.

I have a simple node, with a material set:

![image](https://user-images.githubusercontent.com/12863685/130659408-f8f31893-e234-4485-a34e-db242b1f2757.png)

The resource is local so that multiple instances don't affect the shader properties being set per instance.

When I instance this node via the editor (i.e. put it into the scene) everything is fine.

However, when I instance via

```
var human=preload("res://entities/screen_based/Human.tscn")

var myhuman=human.instance()
```

Then material is null at runtime.

If I untick 'local to resource' then the material is set ok at runtime. 

### Steps to reproduce

video/code can be produced if this is not expected behaviour.

### Minimal reproduction project

_No response_
Repository: go
Issue: x/website:  Error of "Developing a RESTful API with Go and Gin" chapter
Labels: Documentation,NeedsFix,website

<!--
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.16.6 windows/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
set GOHOSTARCH=amd64
set GOHOSTOS=windows
</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.
-->
I wrote a RESTful API for adding albums according to the documentation([Tutorial: Developing a RESTful API with Go and Gin](https://golang.org/doc/tutorial/web-service-gin)), but when i called it according to the curl command in the case, an error occurred.

```shell
$ curl http://localhost:8080/albums \
    --include \
    --header "Content-Type: application/json" \
    --request "POST" \
    --data '{"id": "4","title": "The Modern Sound of Betty Carter","artist": "Betty Carter","price": 49.99}'
```
Finall I found out that I need to escape the double quotes in the data send using curl, otherwise the problem will occur.
The following case can be send successfully.

```shell
curl http://localhost:8080/albums --include --header "Content-Type: application/json" --request "POST" --data '{\"id\": \"4\",\"title\": \"The Modern Sound of Betty Carter\",\"artist\": \"Betty Carter\",\"price\": 49.99}'
```


### What did you expect to see?
```shell
curl http://localhost:8080/albums --include --header "Content-Type: application/json" --request "POST" --data '{\"id\": \"4\",\"title\": \"The Modern Sound of Betty Carter\",\"artist\": \"Betty Carter\",\"price\": 49.99}'
```


### What did you see instead?
```shell
$ curl http://localhost:8080/albums \
    --include \
    --header "Content-Type: application/json" \
    --request "POST" \
    --data '{"id": "4","title": "The Modern Sound of Betty Carter","artist": "Betty Carter","price": 49.
Repository: pytorch
Issue: torch median / nanmedian w/ nans speed
Labels: module: performance,triaged,module: NaNs and Infs,module: sorting and selection,module: reductions

Hello, I am trying to calculate the median for a NxM array (N ~ 100 and M ~ 25,000). The normal median function is fast enough, but I need to mask out some values for each row. I use nanmedian; however, I see it is a magnitude slower (.5 ms vs .05 ms).

I am running the following code 
```
# x is NxM
x[x == 0] = float("nan")
# x_medians is N
x_medians = torch.nanmedian(x, dim=1)
```
If I comment out, `x[x == 0] = float("nan")`, I can recover the faster performance but of course that's the wrong answer.

Is there a way to achieve what I want while keeping performance. I am on pytorch 1.8.1 btw. 

cc @VitalyFedyunin @ngimel @heitorschueroff
Repository: electron
Issue: [Feature Request]: setPermissionRequestHandler should pass the requesting frame in the details
Labels: enhancement :sparkles:

### 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](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

[session.setPermissionRequestHandler](https://www.electronjs.org/docs/api/session#sessetpermissionrequesthandlerhandler) provides a `webContents` and `isMainFrame`, but there is no way to know which specific frame the permission request came from.

### Proposed Solution

Provide a reference to the specific frame which originated the request, as a `WebFrameMain` in the `details` structure.

### Alternatives Considered

I think if we were designing this API today we'd pass a `WebFrameMain` as the first arg instead of a `WebContents`, but for back compat let's add the frame to the details.

### Additional Information

NA
Repository: material-ui
Issue: [Tabs] Tabs doesn't work with Tab as a custom component
Labels: new feature,component: tabs

- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Current Behavior 😯
Tabs doesn't switch between Tab if it's a custom component that returns Tab

## Expected Behavior 🤔
The same behavior as with Tab

## Steps to Reproduce 🕹
You can see this behavior [here](https://codesandbox.io/s/material-demo-forked-vo6zv)

Steps:

1. Create component that returns Tab
2. Use it in Tabs instead of Tab
Repository: react
Issue: [Feature Request][eslint-plugin-react-hooks] no-ref-checks, display error when using useRef's return value as condition
Labels: Type: Enhancement,Status: Unconfirmed,Component: ESLint Rules

https://github.com/reactjs/rfcs/issues/198
https://github.com/yannickcr/eslint-plugin-react/issues/3042

Not sure whether this belongs in `eslint-plugin-react-hooks` or `eslint-plugin-react`, but a contributor at the latter suggested this to be a more appropriate place. I've opened an issue instead of an RFC to discuss whether this is the appropriate place. https://github.com/yannickcr/eslint-plugin-react/issues/3042#issuecomment-899689312

I started migrating a codebase from class-based to function-based and came across some silliness. I had completely missed converting some of the ref checks:

```diff
- const thing = this.thing;
+ const thing = useRef(props.thing);

// I missed this
- if (!thing) {
+ if (!thing.current) {
```

TypeScript considers `!useRef(props.thing)` to be perfectly valid since it may be testing for non-existence of the value even if it is not boolean. However, due to the rules of hooks, this value will never be undefined -- any checks for it are unnecessary and could either be an innocuous useless check or indicate a serious bug / typo. Thus, I'm thinking it might make sense to make sure a useRef's return value is never used as a boolean or condition at the react linter level. Not sure if it's possible with ESLint, but if so it could be a very useful rule which would catch a lot of bugs.
Repository: transformers
Issue: Tapas tokenization Different from Tensorflow Code
Labels: Good First Issue

## Environment info
<!-- You can run the command `transformers-cli env` and copy-and-paste its output below.
     Don't forget to fill out the missing fields in that output! -->

- `transformers` version: 4.9.1
### Who can help
@LysandreJik @sgugger @NielsRogge

## Information

Model I am using (Bert, XLNet ...): Tapas

When I am trying to replicate the TAPAS table retrieval results using Huggingface Tapas implementation, I find that [Tapas tokenization in Huggingface](https://github.com/huggingface/transformers/blob/master/src/transformers/models/tapas/tokenization_tapas.py#L1314) is different from the original [Tensorflow code ](https://github.com/google-research/tapas/blob/master/tapas/utils/tf_example_utils.py#L391). The original code first checks whether the table cell is "n/a", "?" or empty. If so, it would return "[EMPTY]" token. The Huggingface code has implemented [the same tokenization](https://github.com/huggingface/transformers/blob/master/src/transformers/models/tapas/tokenization_tapas.py#L370) with the tensorflow code, but it is not used to tokenize the tables. It could be easily fixed by changing all the calls of function `self.tokenize` to `self._tokenize` in the `_tokenize_table` function. After fixing this, I could use the released table retrieval model to replicate their results on NQ dataset with Huggingface Tapas.
Repository: transformers
Issue: [model loading] framework-agnostic dtype parameter
Labels: WIP

This is a split off from one of the discussions at https://github.com/huggingface/transformers/pull/13209:

1. It all started with trying to load torch models under either the desired dtype or the the dtype of the pretrained model - and thus avoid 2x memory usage needs e.g. if the model needs to be just fp16. So we added `torch_dtype` to `from_pretrained` and `from_config`.
2. Then we started storing `torch_dtype` in the config file for future possibly automatic loading model in the optimal "regime".
3. This resulted in a discrepancy where the same symbol sometimes means `torch.dtype` at other times a string like "float32" as we can't store `torch.dtype` in json.
4. then in https://github.com/huggingface/transformers/pull/13209#discussion_r693292542 we started discussing how `dtype` is really the same across pt/tf/flux and perhaps we should just use `dtype` in the config and variables and have it consistently to be a string ("float32") and convert it to the right dtype object of the desired framework at the point of use, e.g. `getattr(torch, "float32")`

A possible solution is to deprecate `torch_dtype` and replace it with `dtype` string both in config and in the function argument.

Possible conflicts with the naming:

1. we already have the `dtype` attribute in modeling_utils, which returns `torch.dtype` based on the first param's dtype.

   https://github.com/huggingface/transformers/blob/master/src/transformers/modeling_utils.py#L205

   The context is different, but still this is something to consider to avoid ambiguity.

I may have missed some other areas. So please share if something else needs to be added.

Additional notes:
- wrt flux: https://github.com/huggingface/transformers/pull/13209#discussion_r694511759
>  #13098 - the idea of the PR is exactly to disentangle parameter dtype from matmul/computation dtype. In Flax, it's common practice that the dtype parameter defines the matmul/computation dtype, see: https://flax.readthedocs.io/en/latest/_autosummary/flax.linen.Dense.html#flax.linen.Dense.dtype instead of the parameter dtype and not the parameter dtype.
> So for Flax, I don't really think it would make sense to use a config.dtype to define weights dtype as it would be quite confusing with Flax's computation dtype parameter.


@LysandreJik, @sgugger, @patrickvonplaten
Repository: material-ui
Issue: [Slider] Dragging slider with onChangeCommitted prop changes other value 
Labels: bug 🐛,component: slider

<!-- Provide a general summary of the issue in the Title above -->
Continuing  #27800, 

<!--
  Thank you very much for contributing to Material-UI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->

- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Current Behavior 😯
Dragging slider with onChangeCommitted prop changes other value when mouseup happens near the other thumb.
<!-- Describe what happens instead of the expected behavior. -->

## Expected Behavior 🤔
It should only change the value of the thumb which is being dragged.

<!-- Describe what should happen. -->

## Steps to Reproduce 🕹

![pic1](https://user-images.githubusercontent.com/14920241/130699337-ab708c82-7f79-4743-be75-746886b3c22b.gif)

https://codesandbox.io/s/material-demo-forked-vxsmr?file=/demo.js
<!--
  Provide a link to a live example (you can use codesandbox.io) and an unambiguous set of steps to reproduce this bug.
  Include code to reproduce, if relevant (which it most likely is).

  You should use the official codesandbox template as a starting point: https://material-ui.com/r/issue-template-next

  If you have an issue concerning TypeScript please start from this TypeScript playground: https://material-ui.com/r/ts-issue-template

  Issues without some form of live example have a longer response time.
-->

## Context 🔦
<!--
  What are you trying to accomplish? How has this issue affected you?
  Providing context helps us come up with a solution that is most useful in the real world.
-->
Trying to drag and change first value near to second value but when doing mouseup second value moves up and It gets difficult to select the value.
If the 2nd value is 80 and I want to change 1st value 20 to 60, 2nd value moves up, Which is not required.
Repository: pytorch
Issue: Scalar construction in C++: PY`torch.tensor(7)` !~= C++`at::tensor(7)`
Labels: module: cpp,triaged,module: tensor creation

## 🐛 Bug

The documented way to construct a scalar in python `torch` is `torch.tensor(X)` for scalar values of X; which produces a Rank-0 (sizes == []) Tensor with one 0-dim value `X`.

a10 doesn't really ... have documentation; it seems to largely leverage familiarity with the python semantics.

The equivalent interface in a10 is `at::tensor(X)` for scalar values of X; which produces ... a Rank-1 (sizes = [1]) Tensor with one 1-dim value `{X}`.

The closest I can seem to come to `torch.tensor(7)` in C++ is `at::tensor(7).select(0, 0)`

This seems ... wrong?

cc @yf225 @glaringlee @gchanan @mruberry
Repository: flutter
Issue: FileSystemException errno = 5 while building app at FlutterBuildSystem.trackSharedBuildDirectory
Labels: tool,P2,team-tool,triaged-tool

on beta/2.5.0-5.2.pre

with command: `--quiet assemble --no-version-check --depfile C:\Users\app\build\app\intermediates\flutter\debug/flutter_build.d --output C:\Users\app\build\app\intermediates\flutter\debug -dTargetFile=C:\Users\app\lib\main.dart -dTargetPlatform=android -dBuildMode=debug -dTrackWidgetCreation=true debug_android_application`

```
Thread 0 main threadFileSystemException: FileSystemException: Cannot delete file, path = 'C:\Username\dev\appname\build\app\intermediates\flutter\debug\flutter_assets\assets/buttondown.png' (OS Error: Acesso negado.
, errno = 5)
at _File.throwIfError(file_impl.dart:635)
at _File._deleteSync(file_impl.dart:298)
at FileSystemEntity.deleteSync(file_system_entity.dart:408)
at ForwardingFileSystemEntity.deleteSync(forwarding_file_system_entity.dart:70)
at ForwardingFileSystemEntity.deleteSync(forwarding_file_system_entity.dart:70)
at ErrorHandlingFileSystem.deleteIfExists(error_handling_io.dart:82)
at FlutterBuildSystem.trackSharedBuildDirectory(build_system.dart:739)
at FlutterBuildSystem.build(build_system.dart:627)
at <asynchronous gap>(async)
at AssembleCommand.runCommand(assemble.dart:314)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1125)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:209)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:288)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:236)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:62)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:150)
at <asynchronous gap>(async)
at main(executable.dart:92)
at <asynchronous gap>(async)
```
Repository: TypeScript
Issue: `atob()` is incorrectly marked as deprecated.
Labels: Bug,Blocked

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.60.0
- OS Version: Windows 7

![image](https://user-images.githubusercontent.com/8168391/130551535-de2684ca-d35f-40be-998b-b995d3d4c90b.png)

Steps to Reproduce:

1. Reference the `atob()` function in a JavaScript or TypeScript file.
2. The reference to the function is marked as deprecated, even if only the unintended one of its two overloads is.