sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: React 18: useEffect different behaviour compare to v17 in specific cases
Labels: Type: Discussion,React 18

<!--
  Ask a question or share feedback about the React 18 release here.
-->
Hi!
In [this](https://github.com/tannerlinsley/react-query/issues/2628) issue to react-query repo we found some strange useEffect behaviour.

Here's examples:
[react 17](https://codesandbox.io/s/react-or-react-query-bug-version-2-forked-fnebv?file=/src/example.js)
[react 18 with old root api](https://codesandbox.io/s/react-bug-version-3-x8fs6?file=/src/example.js)

Just click "rerender" button and see that there's no effect firing.

But in react 18 with the new root API it works fine:
[codesandbox](https://codesandbox.io/s/react-bug-version-3-forked-8mxy2?file=/src/example.js)

I tried to explain it like that:
> So, in our case we have `dummy` and `forceRerender` state variables.
After calling `rerender` function, `dummy` updates with the same value, and React bails out without rendering the children or firing effects. I suppose that somewhere here the effect should've been scheduled, but it didn't because of that react behaviour.
BUT, the render function was actually called and useEffect received updated `value` in deps (you can see this by checking how many times console.log was called in render).
And then on the next tick `forceRerender` causes another update, but this time it doesn't schedule the effect because it has the same deps (`value`) that were captured in the previous render function call.

So, is this right explanation for what is going on there?
And I guess, the main question, why does this example work fine when the new root api is used?
Does it mean that with the new root api (and with concurrent mode) useEffect compare deps only with those from the last previous render that was committed to the DOM?

Thanks!
Repository: ant-design
Issue: Input disable的时候应该只禁用输入事件的 onChange 吧，iconRender 的切换不应该一起禁用。
Labels: 💡 Feature Request,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/mi-ma-kuang-antd-4-18-2-forked-0e0qf?file=/index.js)

### Steps to reproduce
disable Input，切换 iconRender

### What is expected?
iconRender 的切换不应该被 Input disable 禁用

### What is actually happening?
iconRender 的切换被 Input disable 禁用

| Environment | Info |
|---|---|
| antd | undefined |
| React | 16.14.0 |
| System | macos |
| Browser | chrome |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: An issue with MenuButton and OS.execute causes the window to become unclosable
Labels: bug,platform:windows,topic:porting,topic:gui

### Godot version

3.4.2

### System information

Windows 8.1, but I've been told the issue is present on Windows 10 as well

### Issue description

The game window can no longer be selected (closed/maximized/minimized/resized/moved) after clicking MenuButton, then OS.execute() a program, then clicking within game.

### Steps to reproduce

Step 1. Click on a MenuButton that runs this line of code:
```
OS.execute("C:/Windows/system32/notepad.exe", [], false)
```
Step 2. Minimize or close the notepad which pops up, then click somewhere within the game (click on the grey background)

Step 3. Try to click on minimize/maximize/close in the corner of the window. They are unclickable and will not highlight. Alt+F4 doesn't work either.

If you use a normal Button instead of a MenuButton then this issue does not occur. Launching ``OS.execute`` with a key press instead also works correctly.

### Minimal reproduction project

[cannotCloseWindowBug.zip](https://github.com/godotengine/godot/files/7843622/cannotCloseWindowBug.zip)
Repository: pytorch
Issue: The implement of `containsTensorType(const TypePtr& t)` in jit pass `PropagateInputShapes` ignore some situation?
Labels: oncall: jit

### 🐛 Describe the bug

The implement of [`containsTensorType(const TypePtr& t)`](https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/passes/shape_analysis.cpp#L140) in [TORCH_API void PropagateInputShapes(const std::shared_ptr<Graph>& graph)](https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/passes/shape_analysis.cpp#L2133) will missing the situation of that `t->isSubtypeOf(*TensorType::get())`?

```c++
  bool containsTensorType(const TypePtr& t) {
    auto n_contained = t->containedTypes().size();
    if (n_contained == 1) {
      return t->containedTypes().at(0)->isSubtypeOf(*TensorType::get());
    } else if (n_contained > 1) {
      return std::any_of(
          t->containedTypes().begin(),
          t->containedTypes().end(),
          containsTensorType);
    }
    return false;
  }

  ...

  // If there's no Tensor in outputs, e.g float / float,
  // we don't need to propagate shape.
  bool DoesntRefineOutputs(Node* node) {
    auto outputs = node->outputs();
    for (auto& out : outputs) {
      if (containsTensorType(out->type())) {
        return false;
      }
    }
    return true;
  }
```

As #17756 code review：[Changes to shape_analysis look fine, one small suggestion](https://github.com/pytorch/pytorch/pull/17756#pullrequestreview-215287319). Though `virtual at::ArrayRef<TypePtr> containedTypes()` will support  (optionals, futures)，`containsTensorType` misses the situation `t->isSubtypeOf(TensorType::get())`。

@zdevito @ailzhang

### Versions
tag: 1.10.1+cu102 (git_version 302ee7b)

### Workaround

```python3
import torch
from torch import nn
from torch.nn import functional as F

class Foo(nn.Module):
    def __init__(self):
        super(Foo, self).__init__()
        self.mean = torch.zeros((3, 448, 448))
        self.std = torch.ones((3, 448, 448))

    def forward(self, x):
        x = x - self.mean
        x = x / self.std

        padding_size = [0, 0, 0, 0]
        x = F.pad(x, padding_size, value=0.0)
        return x

jit_mod = torch.jit.trace(Foo(), torch.zeros((3, 448, 448))).eval()

freeze_mod = torch.jit.freeze(jit_mod)
lowered_graph, _ = torch._C._jit_pass_lower_graph(freeze_mod.graph, freeze_mod._c)
print("before pass: ", lowered_graph)

torch._C._jit_pass_complete_shape_analysis(lowered_graph, (torch.zeros((3, 448, 448)), ), False)
print("after pass: ", lowered_graph)
```

The above `Graph` with `_jit_pass_complete_shape_analysis` will return unexpectedly at [shape_analysis.cpp:735](https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/passes/shape_analysis.cpp#L735)：

```c++
    if (DoesntRefineOutputs(node)) {
      return;
    }
```
Repository: pytorch
Issue: clang format hash mismatched for linux64
Labels: module: ci,module: lint,triaged

### 🐛 Describe the bug

clang format hash outdated, making clang-format skipped in CI runs:

Sample CI run output:
```
 find . -type f -path ./c10/* -or -path ./torch/csrc/jit/*+  -or -pathxargs ./test/cpp/jit/* -or -path ./test/cpp/tensorexpr/*
 tools/linter/git-clang-format --verbose 4f6c999f67526290201b548235bea9ad04ee3070 --
Downloading clang-format to /home/runner/work/pytorch/pytorch/.clang-format-bin

The downloaded binary is not what was expected!
Downloaded hash: 'e1c8b97b919541a99e0a355df5c3f9e8abebc64259dbee6f8c68e1ef90582856' vs expected 21ca53c291a88b53dac85751b7a0203ca610ac94b7adaff3c092cf30df4168f2
The binary has been deleted just to be safe
```

The expected hash is stored here:
[https://github.com/pytorch/pytorch/blob/master/tools/clang_format_hash/linux64/clang-format-linux64#L1](https://github.com/pytorch/pytorch/blob/master/tools/clang_format_hash/linux64/clang-format-linux64#L1
)
while the download path stored here:
[https://github.com/pytorch/pytorch/blob/master/tools/linter/clang_format_utils.py#L7](https://github.com/pytorch/pytorch/blob/master/tools/linter/clang_format_utils.py#L7)

Manual check shows the oss path is actually a different binary.
```
curl https://oss-clang-format.s3.us-east-2.amazonaws.com/linux64/clang-format-linux64 --output clang-format && sha256sum -b clang-format 
```
gave 

```
e1c8b97b919541a99e0a355df5c3f9e8abebc64259dbee6f8c68e1ef90582856 *clang-format

```


### Versions

Collecting environment information...
PyTorch version: 1.11.0a0+git4f6c999
Is debug build: True
CUDA used to build PyTorch: 11.5
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.3 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: version 3.21.3
Libc version: glibc-2.31

cc @malfet @seemethere @pytorch/pytorch-dev-infra
Repository: godot
Issue: Image captured from viewport results in garbled png when saved
Labels: enhancement,topic:core,topic:rendering,documentation

### Godot version

3.4.2

### System information

Debian Linux 11 "Bullseye", ATI RX580, GLES3

### Issue description

I'm using a viewport containing some GUI controls for creating a texture for a mesh. This works great so far, but when I try to save the viewport's texture as PNG image, I seem to get some random noise rather than the texture image.

Here's a screenshot of the minimal reproduction project, showing the GUI viewport's texture applied to the mesh's albedo:

![image](https://user-images.githubusercontent.com/6480173/148906313-b6f6260e-856e-4fa4-99df-ab93986970ad.png)

And here's what the exported PNG looked like in three consecutive launches:

![image](https://user-images.githubusercontent.com/6480173/148906400-ccd85c1f-266e-4c49-be55-865cb3d034d2.png)
![image](https://user-images.githubusercontent.com/6480173/148906648-0c42dbcc-e43e-4f26-8686-857f0a8d0fbe.png)
![image](https://user-images.githubusercontent.com/6480173/148906686-1ef28eba-d4f8-486a-991a-c481f1958f34.png)

I would, of course, expect the saved PNGs look exactly like what's visible on the mesh.

### Steps to reproduce

Just launch the provided minimal reproduction project and have a look in your Godot user folder.

### Minimal reproduction project

[viewport-capture-test.zip](https://github.com/godotengine/godot/files/7844847/viewport-capture-test.zip)
Repository: go
Issue: x/tools/gopls: feature request: adding postfix snippets for errors
Labels: FeatureRequest,gopls,Tools,gopls/completion

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### gopls version

golang.org/x/tools/gopls v0.7.4

Would it be possible to add postfix snippets that are specific for the error type.

I was thinking something like:
```go
err.if!

// Which would expand to:

if err != nil {
    |
}
```
I guess this one could be uses for any type, not just an error, though maybe the snippet name should be better (`ifNot!`?)

and a more complex one that returns and takes into account the other return types:
```go
func MyFunc() (*Ptr, int, error) {
    ...

    err.ret!

    // Which would expand to:
    if err != nil {
         return nil, 0, fmt.Errorf("|: %w", err)  
    }
}
```
Repository: godot
Issue: The script is deleted but the assign icon remains
Labels: bug,topic:editor

### Godot version

v3.4.2.stable.official [45eaa2daf]

### System information

w10 64

### Issue description

When the script is removed, the icon remains assigned to the node.
![gif](https://user-images.githubusercontent.com/19652075/148924608-2958b556-9198-4317-b1a7-7fd16b6f977d.gif)

Also remains in this zone
![Captura2](https://user-images.githubusercontent.com/19652075/148925837-a2e65124-e449-4bf9-a693-f0cf851b99ee.PNG)


### Steps to reproduce

Create a new script and assigno to a node
Delete the script

### Minimal reproduction project

...
Repository: yt-dlp
Issue: PlutoTV live channels support
Labels: site-request,geo-blocked

### Checklist

- [X] I'm reporting a site feature request
- [X] I've verified that I'm running yt-dlp version **2021.12.27**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [ ] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

Italy

### Example URLs

https://pluto.tv/it/live-tv/pluto-tv-film-it
https://pluto.tv/it/live-tv/pluto-tv-film-azione-it

### Description

While VOD is supported, live channels are not supported yet.

### Verbose log

```shell
[debug] Command-line config: ['-Uv', 'https://pluto.tv/it/live-tv/il-banco-dei-pugni-it']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2021.12.27 [6223f67] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.18363-SP0
[debug] exe versions: ffmpeg 4.4.1-essentials_build-www.gyan.dev (setts), ffprobe 4.4.1-essentials_build-www.gyan.dev
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2021.12.27, Current version: 2021.12.27
yt-dlp is up to date (2021.12.27)
[debug] [generic] Extracting URL: https://pluto.tv/it/live-tv/il-banco-dei-pugni-it
[generic] il-banco-dei-pugni-it: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] il-banco-dei-pugni-it: Downloading webpage
[generic] il-banco-dei-pugni-it: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://pluto.tv/it/live-tv/il-banco-dei-pugni-it
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1353, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1423, in __extract_info
  File "yt_dlp\extractor\common.py", line 599, in extract
  File "yt_dlp\extractor\generic.py", line 3829, in _real_extract
yt_dlp.utils.UnsupportedError: Unsupported URL: https://pluto.tv/it/live-tv/il-banco-dei-pugni-it
```
Repository: TypeScript
Issue: Allows report some suggestion diagnostics as errors
Labels: Suggestion,Awaiting More Feedback

# Suggestion

Allows report some suggestion diagnostics as errors.

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

diagnostics, errors

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
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, new syntax sugar for JS, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

We have some suggestions for now. But sometimes we want to make sure they are not be used (like deprecated).
There's some lint to do that. But It's a little slow outside of TypeScript compiler to do this. (We have to check every expression, find symbol, foreach declarations, check comments). For example: https://github.com/microsoft/TypeScript/pull/40607#issuecomment-1007880299

Is that possible to specify some suggestion diagnostics as an error? Might be a list in compiler options in tsconfig?

It's not only an editor feature, because for example what If we want to block the entire compile progress in CI.

<!-- A summary of what you'd like to see added or changed -->

## 📃 Motivating Example

<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->

```ts
/*
* @deprecated
*/
const a = 1

a.toFixed(); // error
```
Repository: TypeScript
Issue: Explicit type annotation required in TS 4.5
Labels: Needs Investigation

# Bug Report

I am sorry to report a bug in this way without a minimized repro but I wasn't able to minimise it, I'd be happy to do more in debugging it but I'd need some pointers.

### 🔎 Search Terms

explicit type annotation, 4.5 issues

### 🕗 Version & Regression Information

This was introduced in `4.5`, it's not yet fixed in `next` and is working fine up to `4.4`

### 💻 Code

https://github.com/Effect-TS/monocle/commit/401ff6be2646a3d2498960ac608e03daad534fa1#diff-05996f2c5b1dbbe79e34a0167eb2ee5017f540f68dd1f94e16cc9760ff3aabacR171

### 🙁 Actual behavior

![Screenshot 2022-01-11 104517](https://user-images.githubusercontent.com/24249610/148928568-6c7d2c3a-b57c-45db-b089-6b9b0907dbbd.png)

### 🙂 Expected behavior

to compile fine, there are no two types named `F`, when explicitly annotated like in the commit above the compiler can check the type correctly.

![Screenshot 2022-01-11 104634](https://user-images.githubusercontent.com/24249610/148928745-6642ab9f-6435-4645-bdf0-c9ed4dbb0089.png)
Repository: rust
Issue: LLVM Error with "+soft-float": "Do not know how to split the result of this operator"
Labels: A-LLVM,I-ICE,T-compiler,C-bug,A-target-feature

I can't compile the [`fontdue`-crate](https://github.com/mooman219/fontdue/issues/98) because it fails with: `LLVM ERROR: Do not know how to split this operator's operand!`

I compile it with: `cargo rustc -- -C target-feature=+soft-float,-sse,-sse2,-x87 --emit=llvm-ir`

This happens **with different compiler versions**, independent of **stable or nightly** versions. I tested to build the dependencies of `fontdue` without problems, therefore I think Rustc/LLVM runs into a bug because of the code from `fontdue`.

### LLVM IR
The two LLVM IR files I found after the build can be found [on Google Drive](https://drive.google.com/drive/folders/1XgAa_X4HW22Ah_rOAP0DOludk-hqb9Tn?usp=sharing).
Repository: flutter
Issue: FFI plugin for prebuilt binaries (documentation/sample/plugin)
Labels: team

Lets create a tracking issue to get this done.

From https://github.com/flutter/flutter/issues/96225#issuecomment-1009862695
> Building the binaries for all platforms is no problem but. More documentation would be > very helpful. Especially how to:
> - put shared libraries in the correct place to be found at runtime

ToDo: put in documentation

> - add multiple binaries for the same OS (ios_arm64, ios_arm64_sim etc.)

I haven't figured out how to bundle prebuilt binaries with the same hardware for 2 different OSes. (With different hardware architectures we can use fat binaries, but that doesn't work. So we likely need to define a Framework.)

> - make sure the binaries don't get stripped

That should only be a problem when using static linking, try dynamic libraries instead.
Repository: opencv
Issue: Slower grayscale png image loading than GDI+/Bitmap
Labels: question (invalid tracker),incomplete

##### System information (version)
- OpenCV => 4.5.3 (via OpenCvSharp4.Windows 4.5.3.20210817)
- Operating System / Platform => Windows 10 64 Bit
- Compiler => Visual Studio 2022

##### Detailed description
Comparing `OpenCVSharp` to `System.Drawing`/GDI+/Skia for loading a simple grayscale 8-bit png image I discovered this is ~2.7x slower with OpenCV.
```
|       Method |        FileName |      Mean |    Error |    StdDev | Ratio |
|------------- |---------------- |----------:|---------:|----------:|------:|
|      GDIPlus | Gray304x384.png | 123.93 us | 2.440 us |  2.810 us |  1.00 |
|          WPF | Gray304x384.png | 149.84 us | 0.501 us |  0.391 us |  1.20 |
|    SkiaSharp | Gray304x384.png | 101.01 us | 0.159 us |  0.141 us |  0.81 |
| OpenCVSharp4 | Gray304x384.png | 337.63 us | 1.537 us |  1.284 us |  2.70 |
```
I wonder why that is and what could be done about it?

##### Steps to reproduce
```csharp
 var ImageBytes = File.ReadAllBytes("ImageFileName.png");
 using var mat = Mat.FromImageData(ImageBytes, ImreadModes.Grayscale);
```
using attached image below.

![Gray304x384](https://user-images.githubusercontent.com/10798831/148958387-0fd95d04-4f67-4a34-aaf2-a2b8178b7ab3.png)

PS: This is using Skia 1.60.3 before Index8 was removed.
PPS: With basic profiling I have confirmed bottleneck is in the native OpenCV code, so OpenCVSharp is not the issue as such.
Repository: PowerToys
Issue: Request: Add Constrain window option.
Labels: Product-Window Manager,Product-Always On Top,Needs-Triage

### Description of the new feature / enhancement

Prevent any edge of a window from leaving the screen.
(Low priority) With additional option to constrain to one monitor or to span across multiple monitors providing that they are operating at the same orientation, resolution and pixel density.

### Scenario when this would be used?

Any time when I have a window which does not conform to any Fancy Zone, 
Could combine as an option within Always on Top.

### Supporting information

_No response_