sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [video_player] Android can't play an encrypted m3u8 link
Labels: platform-android,waiting for PR to land (fixed),p: video_player,package,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-android,triaged-android

Android can't play an encrypted m3u8 link, iOS and Web normal
Repository: pytorch
Issue: Zero-copy way to make flat tensor into a nested_tensor given a shape
Labels: triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

If it were possible to create a nested_tensor from a flat tensor with the correct layout, we could always work around elementwise functions which are not (yet) supported by nested_tensor e.g.

```
a_shape = [t.size() for t in a.unbind()]

tensor.nested.nested_tensor_from_values_as(elementwise_function(a.values()), a)

# OR

tensor.nested.nested_tensor_from_values(elementwise_function(a.values()), a_shape)
```

### Alternatives

Copying or trying to work with the flat tensor directly.

### Additional context

I am currently trying to use unsupported loss functions in their unreduced form

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @mikaylagawarecki
Repository: pytorch
Issue: binary_cross_entropy/bce_with_logits (+ other loss functions) for nested_tensor
Labels: module: loss,triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

For multi-task learning, it could be useful to have loss functions support nested_tensors. Some of the reductions might not be so useful for some loss functions as currently implemented since they seem to assume regularly sized inputs, but at least something could be implemented when reduce="none".

```
import torch
from torch.nn.functional import binary_cross_entropy

nt = torch.nested.nested_tensor([[1.0, 0.4, 0.2], [0.1]])
print(binary_cross_entropy(nt, nt, reduce="none"))
```

Current output

```
/home/frankier/edu/doc/bert_ordinal/nightlytorchplay/losstest.py:5: UserWarning: The PyTorch API of nested tensors is in prototype stage and will change in the near future. (Triggered internally at ../aten/src/ATen/NestedTensorImpl.cpp:177.)
  nt = torch.nested.nested_tensor([[1.0, 0.4, 0.2], [0.1]])
Traceback (most recent call last):
  File "/home/frankier/edu/doc/bert_ordinal/nightlytorchplay/losstest.py", line 7, in <module>
    print(binary_cross_entropy(nt, nt, reduction="none"))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/frankier/edu/doc/bert_ordinal/nightlytorchplay/venv/lib/python3.11/site-packages/torch/nn/functional.py", line 3087, in binary_cross_entropy
    if target.size() != input.size():
       ^^^^^^^^^^^^^
RuntimeError: Internal error: NestedTensorImpl doesn't support sizes. Please file an issue on https://github.com/pytorch/nestedtensor
```

### Alternatives

If this were possible https://github.com/pytorch/pytorch/issues/89124 it might provide a good/easy workaround.

### Additional context

_No response_

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @mikaylagawarecki
Repository: opencv
Issue: masked images in MatchTemplate()
Labels: bug

### System Information

// example for c++ user
OpenCV version: 4.6.0
Operating System / Platform: Ubuntu 20.04
Compiler & compiler version: GCC 9.4.0

// example for python user
OpenCV python version: 4.6.0.
Operating System / Platform: Ubuntu 20.04
Python version: 3.8.10

### Detailed description

When we use mask in function MatchTemplate() with two the same size images we always have result 1x1 because in your function result is formed as img.size - templ.size + 1.

I siggest doing like this
```
int count = countNonZero(mask);
std::vector<Point> locations;
findNonZero(mask, locations);
    
Size corrSize(img.cols - (locations.at(count-1).x - locations.at(0).x + 1) + 1, 
    						img.rows - (locations.at(count-1).y - locations.at(0).y + 1) + 1);
```

### Steps to reproduce

Also I suggest rewrite some code of function in ```TM_CCOEFF``` / ```TM_CCOEFF_NORMED``` modes. For example, 
```Mat templx_mask = mask.mul(mask.mul(templ - sum(mask.mul(templ)).div(mask_sum)));``` change to 
```Mat templx_mask = mask.mul(templ - sum(mask.mul(templ)).div(mask_sum));```
Delete ```crossCorr(img, mask, img_mask_corr, Point(0, 0), 0, 0);``` because 
```CCorr(I', T') = CCorr(I, T'*M) - sum(T'*M)*CCorr(I, M)/sum(M) = CCorr(I, T'*M)```.

Also I suggest not to do the same calculation in ```norm_templx``` and use ```norm(templx_mask, NORM_L2);```.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: vscode
Issue: Debugging: Support single-thread execution requests
Labels: feature-request,debug

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
DAP execution requests (continue, next, stepIn etc.) support two modes:
* The default mode, where execution requests resume all threads.
* A single-thread mode, where execution requests only resume a single thread.

It seems VS Code always uses the default mode (even when using the inline buttons on each thread in the Call Stack window). For debug adapters that support single-thread execution requests, it would be great if there was some way to perform them from VS Code. Some ideas for how this could work:

* A button in the debug toolbar that globally toggles between the modes. All continue/next/stepIn etc. actions taken by the user would use the currently selected mode.
* Separate UI for single-thread execution control. For example, the debug toolbar could perform actions on all threads, whereas the inline buttons shown when hovering over a thread in the Call Stack window could perform actions only on that thread. To me at least, it's a bit confusing that pressing the inline 'Continue' button on a thread also resumes all other threads.
Repository: rust
Issue: Consider relaxing the `Sized` requirement in `impl Error for Box<T>`
Labels: T-libs-api

As for today the following blanket implementation exists:
https://github.com/rust-lang/rust/blob/e702534763599db252f2ca308739ec340d0933de/library/alloc/src/boxed.rs#L2443-L2458

The problem with this is that `T` is required to be `Sized`, so, for example, `Box<dyn Error>` doesn't implement `Error`. It looks like a straightforward and intuitive assumption that `Box<dyn Error>` should implement `Error` trait, but it doesn't.

Going even further, there is an inconsistency between the blanket impls for `Arc` as well, because there exists an analogous impl for `Arc` that has relaxed `Sized?` requirement:

https://github.com/rust-lang/rust/blob/e702534763599db252f2ca308739ec340d0933de/library/alloc/src/sync.rs#L2769-L2788

## Use Case

The use case where I stumbled with this problem is where I wanted to put `Box<dyn Error>` as a `source` error in `thiserror` error enum, but I couldn't because that type doesn't implement Error trait. 

## Workarounds

The workaround for this problem is to use `Arc<T>` instead of `Box<T>` when an Error impl is required for `Sized?` type.
Repository: excalidraw
Issue: Redesign Context menu 🔥
Labels: enhancement

The context menu is becoming bigger and overloaded with more and more options so we need to revamp it. 

Let's discuss the ideas here on how we can improve it
Repository: stable-diffusion-webui
Issue: [Feature Request]: Training Tab Changes (embeddings / hypernetworks )
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Since dreambooth doesn't work for me at the moment, i've been playing a lot of with embeddings and hypernetworks. And in the training tab, there's something wrong : 
- if i want to train an embedding (after creating it), i select the correct embedding and the parameters for it, click train embedding and it works fine, it trains the new embedding
- if i want to train a hypernetwork, i select it, set the parameters and click on train hypernetwork and it doesn't work. to get it to work i also had to select an emebedding (not sure why).

### Proposed workflow

either separate the training tab into 2 separate tabs (embeddings / hypernetworks)

or let it as it is and remove the requirement of having an embedding selected if you only need to train a hypernetwork


### Additional information

_No response_
Repository: material-ui
Issue: [Pagination] on table pagination row info is not in correct order on RTL
Labels: component: pagination

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://mui.com/material-ui/react-pagination/#table-pagination

Steps:

1. change the direction of the page to RTL
2. it should have been `100 of 30-21`
![image](https://user-images.githubusercontent.com/34584266/202188386-2ab29f50-913f-4216-9ff5-4db1b5bc7011.png)


### Current behavior 😯

![image](https://user-images.githubusercontent.com/34584266/202188665-acc97e60-8557-4c18-b0bd-56adc92d1c10.png)


### Expected behavior 🤔

`100 of 30-21`

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: deno
Issue: fsFile writer slow 
Labels: perf,needs investigation

Calling `fsFile.writable.getWriter().write(new Uint8Array(128))` x 10M times takes 20s~30s to finish.

While Node.js `writeStream().write(new Uint8Array(128))` only costs 1s.

Deno version: v1.28.0
Node verison: v18.12.0

See this repo: https://github.com/OpenGG/deno-node-fs-write
Repository: pytorch
Issue: [FSDP] Investigate Unit Testing when Gradient Computation Differs on CPU/GPU
Labels: oncall: distributed,triaged,module: fsdp

Consider the following unit test (relying on some imports from `common_fsdp.py`):
```
def test_cpu_gpu_parity(self):
    cpu_model = TransformerWithSharedParams.init(
        self.process_group,
        FSDPInitMode.NO_FSDP,
        CUDAInitMode.CUDA_NEVER,
        deterministic=True,
    )
    gpu_model = copy.deepcopy(cpu_model).cuda()
    cpu_inp = cpu_model.get_input(torch.device("cpu"))
    gpu_inp = gpu_model.get_input(torch.device("cuda"))
    for t1, t2 in zip(cpu_inp, gpu_inp):
        assert torch.equal(t1, t2.cpu())  # same input except device
    for p1, p2 in zip(cpu_model.parameters(), gpu_model.parameters()):
        assert torch.equal(p1, p2.cpu())  # same parameters except device
    cpu_out = cpu_model(*cpu_inp)
    cpu_out.sum().backward()
    gpu_out = gpu_model(*gpu_inp)
    gpu_out.sum().backward()
    for p1, p2 in zip(cpu_model.parameters(), gpu_model.parameters()):
        assert torch.equal(p1, p2.cpu())
        assert torch.equal(p1.grad, p2.grad.cpu()), f"{torch.linalg.vector_norm(p1.grad - p2.grad.cpu())}"
```
This fails on the last line:
```
assert torch.equal(p1.grad, p2.grad.cpu()), f"{torch.linalg.vector_norm(p1.grad - p2.grad.cpu())}"
AssertionError: 2.398389005975332e-05
```
This slight difference in the computed gradients makes downstream testing infeasible (e.g. testing `clip_grad_norm_()`). This is relevant when testing DDP and FSDP parity when only FSDP is offloading parameters to CPU (since DDP does not support that natively).

We need to find a workaround for this for the unit testing coverage.

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501
Repository: godot
Issue: Right to left makes the container layout buttons counterintuitive 
Labels: topic:editor,usability,topic:gui

### Godot version

v4.0.beta4.official [e6751549c]

### System information

linux

### Issue description

When making a right to left user interface, these buttons,
![image](https://user-images.githubusercontent.com/80917990/202203533-72f77572-a7e5-4e17-8b1d-c7cb6468dec2.png)
![image](https://user-images.githubusercontent.com/80917990/202204414-83ebdb74-d21b-40c0-b823-d3bead628b87.png)

are reversed - pressing the left-align button for example will put the control on the right side and vice versa
(this is a really small issue so I understand if you decide to just leave it as is)

### Steps to reproduce

set a node to RTL (layout -> layout direction -> right to left) and try to use these buttons

### Minimal reproduction project

_No response_
Repository: rust
Issue: coercion `?0: Sized` check, rewrite to not rely on fulfill internals
Labels: C-cleanup,T-types,WG-trait-system-refactor

The behavior of `fn coerce_unsized` for some inference variable `?0` changes depending on whether there's a pending `?0: Sized` obligation in the fulfillment context:

https://github.com/rust-lang/rust/blob/63c748ee23ab7b6706655146f5b7c7f579811803/compiler/rustc_hir_typeck/src/coercion.rs#L672-L682

This pending obligation can be a nested obligation, e.g. we may have only added a `Vec<?0>: Debug` obligation to the fulfillment context. But proving that adds a nested `?0: Sized` obligation from the impl candidate to the `FulfillmentContext`, which then influences coercion.

As our new solver should try to fully prove obligations instead of selecting a candidate and adding nested obligations to the root, this has to change.

cc @rust-lang/initiative-trait-system-refactor
Repository: rustdesk
Issue: Rustdesk shows workstation offline when its screen is off
Labels: bug,help wanted

### Discussed in https://github.com/rustdesk/rustdesk/discussions/2159

<div type='discussions-op-text'>

<sup>Originally posted by **PabloGrok** November 16, 2022</sup>
<!-- Hey there, thank you for creating an issue! -->

**Describe the bug you encountered:**
Most of our workstations in the studio turn their screens off after 10 min. That's standard and recommended Windows behavior. At that point, Rustdesk can no longer connect to that workstation showing it offline.

...

**What did you expect to happen instead?**
Since the workstations is not offline, just its screen is off, Rustdesk shouldn't declare that workstation offline and just connect to it.
...


**How did you install `RustDesk`?**

<!-- GitHub release, build from source, Windows portable version, etc. -->
Downloaded and executed this file: https://github.com/rustdesk/rustdesk/releases/download/1.1.9/rustdesk-1.1.9-x64.exe

---

**RustDesk version and environment**
<!--
In order to reproduce your issue, please add some information about the environment
in which you're running RustDesk.
-->
1.1.9. Windows 10 fully updated, both on the remote and local computers.
</div>
Repository: TypeScript
Issue: Support `satisfies` operator on functions
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

satisfies function

## ✅ Viability Checklist

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

Support the `satisfies` operator to appear after a function

```ts
function foo () { } satisfies Bar
```

This was requested/mentioned in #47920 several times but never followed up on

## 📃 Motivating Example

`satisfies` is super handy to use, and you can already use it for arrow functions. Not having support for it on functions feels unintuitive and forces a certain coding style where people have to use arrow functions when they rather want to use functions.

## 💻 Use Cases

Typing a function while preserving its return type.
Repository: PowerToys
Issue: [Keyboard Manager] Extending Remap a Shortcut
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

Extend the support of shortcut remaps up to 4 keystrokes, from the current of 3 keys

### Scenario when this would be used?

In FancyZones, the shortcut to change layout is Win+Ctrl+Alt+[number]

### Supporting information

_No response_
Repository: TypeScript
Issue: Compiler API: Hygiene Identifier
Labels: Suggestion,Awaiting More Feedback

# Problem

When writing a transformer, it's hard to analyze where the variable is declared from.

For example,

```ts
var a
{ let a
  a // <- here
}
```

When the transformer hits the Identifier `a`, there is no way to know where it is (lexically) declared from. This is extremely hard to track that relationship, you need to do the track top-down (note: `.parent` is not unsafe during transformation).

# Suggestion

Add a new property `hygiene: number` on the `Identifier` to track it.

It has the following invariant:

- A `(name, hygiene)` pair determines a unique definition of an identifier.
- The invariant above only holds within a `SourceFile` (no cross-file knowledge)

# Example

In the following example, I will use `(name, hygiene)` to represent `identifier.escapedText` and `identifier.hygiene`

> Undefined (in the lexical scope) variable has ID=0

```ts
window // (window, 0)
undefined // (undefined, 0)
```

> Variable referencing

```ts
let a // (a, 1)
a // (a, 1)

b // (b, 1), use before declaration
var b // (b, 1)
```

> Variable shadowing

```ts
const { a, b, c } = expr
// (a, 1); (b, 1); (c, 1);
a // (a, 1)

{
    const { a, b, c } = expr2
    // (a, 2); (b, 2); (c, 2);
    a // (a, 2)
}
```

# Benefit

It can significantly simplify some transformer that requires that information.
Repository: vscode
Issue: [Accessibility] Add an option to allow Alt+F5 to jump to the next --word-diff instead of the whole line
Labels: feature-request,accessibility,diff-editor

CC @isidorn and @meganrogge

Although Alt+F5 and F7 provide accessible diff navigation for screen reader users, it is still challenging to identify exact changes when focused on the whole line.

Could you please consider adding a setting option to allow Alt+F5 to land in `--word-diff` instead of the whole line so that screen reader users can more easily identify modified locations?

## System Info

Version: 1.74.0-insider (system setup)
Commit: edccbd1307ef8055f26778c5a86f9eef885bc6ff
Date: 2022-11-16T05:24:12.776Z
Electron: 19.1.3
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes
Repository: svelte
Issue: Props fail to update if component visibility is changed during transition
Labels: transition/animation

### Describe the bug

Props are not updated correctly when the visibility state of a component changes during a transition. 

### Reproduction

[REPL](https://svelte.dev/repl/c6802d3a0b4c4fe2abe0c089f1182784?version=3.53.1)

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Pro
    Memory: 916.34 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.8.0 - ~/.nvm/versions/node/v18.8.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.8.0/bin/yarn
    npm: 8.18.0 - ~/.nvm/versions/node/v18.8.0/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Firefox: 106.0.3
    Safari: 16.0
  npmPackages:
    svelte: ^3.50.0 => 3.50.1
```


### Severity

annoyance
Repository: flutter
Issue: Add option to test deployed flutter web builds
Labels: c: new feature,tool,platform-web,c: proposal,f: integration_test,P3,team-web,triaged-web

I am part of a team using flutter for web in a very test focused organisation. It is a requirement that end2end tests are run against a deployed build. As it is right now Flutter integration tests do not allow us to fulfil that requirement. Flutter integration tests are run against a locally hosted build and there is no option to point the driver to a deployed build.

I appreciate the work needed to support this end2end testing for flutter web is in no way trivial but it seems to me that this is the right way to leverage the awesome capabilities of the flutter integration test framework in the web setting.

### Alternatives
Right now the only option to test deployed flutter web applications is to use other test frameworks such as Selenium, Karate, Cypress and rely on the semantic layer for interactivity. This approach poses some issues. Mainly that interacting with the semantic layer is very limited compared to what can be done with Flutter widget tests. But also that we have to learn and rely on a new language and that the alternative test framework must be able to traverse and parse the shadow dom of the deployed web build.

### Proposal
My proposal is that running Flutter integration tests should be decoupled from the locally hosted build and instead offer the option to point the test driver to a hosted build elsewhere. This could be a deployed debug or profiling build - but of course the preferred option would be to test against a real release build.
Repository: PowerToys
Issue: FancyZones: When you drag a window to move it, the window should collapse into an icon or something so you can more easily see zones
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

Right now when you drag a window, it can be hard to see the zones behind it. Yes, I know you can enable transparency but sometimes that is not enough.

It would be cool if, when you start dragging a window, the windwo collapses into an icon or something so you can more easily see the zones.

### Scenario when this would be used?

When moving a window into a zone.

### Supporting information

N/A