sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: Rtve.es Play
Labels: site-request,patch-available

The list of the supported sites say that Rtve Alacarta has supported. This site has replaced with Rtve Play and extractor doesn't work with new site. Please could you add support for Rtve Play? This is example to video https://www.rtve.es/play/videos/comando-actualidad/
Repository: pytorch
Issue: test_nccl_barrier_timeout_new_group_non_member fails intermittently
Labels: high priority,triage review,oncall: distributed,module: tests

Snippet from https://github.com/pytorch/pytorch/runs/3931996186:

```
======================================================================
ERROR [100.035s]: test_nccl_barrier_timeout_new_group_non_member (__main__.CommTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 424, in wrapper
    self._join_processes(fn)
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 643, in _join_processes
    self._check_return_codes(elapsed_time)
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 695, in _check_return_codes
    i, elapsed_time
RuntimeError: Process 1 terminated or timed out after 100.02551603317261 seconds
```

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @mruberry
Repository: TypeScript
Issue: `noPropertyAccessFromIndexSignature` does not affect object literals
Labels: Suggestion,Awaiting More Feedback

# Bug Report

### 🔎 Search Terms

noPropertyAccessFromIndexSignature

### 🕗 Version & Regression Information

4.2+

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?noPropertyAccessFromIndexSignature=true#code/FAGwpgLgBBYM4QFxQN4G0CWA7AJmAHoggE7YDmAukRKVmQL5QC8qwU7UA9J1AO5h8AhlmgQAFhjgwA9lABGAgMaCArmTHQ5ATyhZpABWLSADmGIQtAQUWL4cAGJGAtgElcBAMoYyWQRBXEYAA08irQGOFwWADkEAB0bByCcorI0RLRQYnseABmaWJgICDSmcD0ANzAwIrSWHDS4HElZAAUsAhxyYoAlFW19Y1gzdJtHfF5fTV1DU0t7fAQaNHd0RRTA7PD8+PLeWt9QA

### 💻 Code

```ts
let test: {[index:string]:string} = {
    // we want this to be caught by noPropertyAccessFromIndexSignature, but it isn't.
    abc: 'hi',
    def: 'hello',
};

console.log(test.abc); // reported
console.log(test.def); // reported
console.log(test['abc']); // OK
console.log(test['def']);  // OK
```

### 🙁 Actual behavior

Unquoted string keys are allowed when assigned to types with index signatures.

### 🙂 Expected behavior

Some mechanism for restricting the definitions of object literals so that only named properties are allowed to be provided without quotes (  `{['somekey']: value}` or `{'somekey':value}`.    This would both prevent logic errors and improve compatibility with Closure Compiler's ADVANCED optimizations.
Repository: TypeScript
Issue: Renaming only one of an export w/separate value/type decls renames imports of both
Labels: Bug,Help Wanted,Effort: Difficult,Domain: Refactorings

# Bug Report

### 🔎 Search Terms

rename refactor import export value type

### 🕗 Version & Regression Information

- This is the behavior in every version I tried.

### 💻 Code

```ts
// file1.ts
export interface IFoo /*a*/ { }
export const IFoo /*b*/ = Symbol();

// file2.ts
import { IFoo /*c*/ } from "./file1";

type T = IFoo /*d*/;
const x = IFoo /*e*/;
```

### 🙁 Actual behavior

- Case 1: Rename the `IFoo` interface to `IBar` at (a):
  - (a) is renamed to `IBar`
  - (c) is renamed to `IBar`
  - (d) is renamed to `IBar`
  - (b) and (e) are not renamed, (e) is now an error
- Case 2: Rename the `IFoo` constant to `IBar` at (b):
  - (b) is renamed to `IBar`
  - (c) is renamed to `IBar`
  - (e) is renamed to `IBar`
  - (a) and (d) are not renamed, (d) is now an error.

In either case, renaming the remaining `IFoo` does not fix the broken reference, as there is no longer a relationship between the non-renamed declaration and its respective imports.

### 🙂 Expected behavior

- Case 1: Rename the `IFoo` interface to `IBar` at (a):
  - (a) is renamed
  - (c) is not renamed, but a new import for `IBar` is added
  - (d) is renamed
  - (b) and (e) are not renamed, (e) continues to work
- Case 2: Rename the `IFoo` constant to `IBar` at (b):
  - (b) is renamed
  - (c) is not renamed, but a new import for `IBar` is added
  - (e) is renamed
  - (a) and (d) are not renamed, (d) continues to work

In either case, renaming the remaining `IFoo` should result in duplicate `IFoo` imports being reduced to a single import.
Repository: flutter
Issue: Regression in time to first frame on Mac_ios_flutter_gallery_ios__start_up
Labels: engine,P2,perf: startup,team-engine,triaged-engine

https://flutter-flutter-perf.skia.org/e/?begin=1633048137&end=1634677682&keys=X5f6a5ffdd81655de5243538567fe837f&requestType=0&xbaroffset=26246

On the Engine roll here:

https://github.com/flutter/flutter/pull/92082

Wondering about the change here:

https://github.com/flutter/engine/pull/29145

but this probably needs a bisect /cc @dnfield
Repository: godot
Issue: Simple panning doesn't wrap cursor
Labels: bug,topic:editor,usability,topic:2d

### Godot version

a4fbb67

### System information

W10

### Issue description

When you enable "Simple Panning" option in Editor Settings, the cursor wrapping doesn't work. It works correctly with normal Spacebar panning.
![6TlBD1wRic](https://user-images.githubusercontent.com/2223172/138000972-b50b519e-410d-40c8-8668-5ce87386d862.gif)



### Steps to reproduce

1. Enable "Simple Panning" in Editor Settings
2. Hold Space and try to move around

### Minimal reproduction project

_No response_
Repository: flutter
Issue: Retry presubmit checks that fail due to a bot dying
Labels: team-infra,P2,triaged-infra

For example: https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20build_tests_2_4/11125/overview

/cc @keyonghan
Repository: pytorch
Issue: Modify Dr. CI so it could detect runner disconnection failures
Labels: module: ci,triaged

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: torch.chunk return type may not be documented correctly
Labels: module: docs,triaged

## 📚 Documentation

Minor but https://pytorch.org/docs/master/generated/torch.chunk.html?highlight=chunk#torch.chunk says it returns a list, but in fact it is a tuple. 

```
>>> z = torch.ones(10).chunk(2)
>>> type(z)
<class 'tuple'>
>>> torch.__version__
'1.10.0.dev20210816'
```

cc @brianjo @mruberry
Repository: deno
Issue: How to declare types when importing within a JSDoc type?
Labels: cli,suggestion

### Discussed in https://github.com/denoland/deno/discussions/12404

<div type='discussions-op-text'>

<sup>Originally posted by **jaydenseric** October 12, 2021</sup>
There is a way to declare types when importing:

> ```js
> // @deno-types="./coolLib.d.ts"
> import * as coolLib from "./coolLib.js";
> ```
> — https://deno.land/manual@v1.14.3/typescript/types#providing-types-when-importing

But how do you do the same when importing within a JSDoc type?

For example in `x.js`:

```js
/** @param {import("foo").Foo} foo A foo. */
function x(foo) {
  // …
}
```

In the above situation, if `Foo` is a type that comes from a `.d.ts` file and isn't actually a named export in the ESM module, trying to import the `x.js` module in a TypeScript module with type checking enabled will cause a TS error: `TS2694 [ERROR]: Namespace '__' has no exported member 'Foo'.`.</div>
Repository: pytorch
Issue: readme not update
Labels: module: docs,triaged

## 📚 Documentation
[https://github.com/pytorch/pytorch/tree/master/aten/src](url) dir has changed, but the readme not changed: THNN THCS...
<!-- A clear and concise description of what content in https://pytorch.org/docs is an issue. If this has to do with the general https://pytorch.org website, please file an issue at https://github.com/pytorch/pytorch.github.io/issues/new/choose instead. If this has to do with https://pytorch.org/tutorials, please file an issue at https://github.com/pytorch/tutorials/issues/new -->


cc @brianjo @mruberry
Repository: rust
Issue: `impl FusedIterator for Cycle<I>` is incorrect 
Labels: C-bug,A-iterators

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code [on playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=91a3caafed82c5dd018c63c78cd3a4b0):

```rust
// Cycle implementation
/*
    fn next(&mut self) -> Option<<I as Iterator>::Item> {
        match self.iter.next() {
            None => {
                self.iter = self.orig.clone();
                self.iter.next()
            }
            y => y,
        }
    }
*/
use std::iter::FusedIterator;
use std::rc::Rc;
use std::cell::Cell;

pub struct ErraticIterator(Rc<Cell<usize>>, Option<()>);

impl Clone for ErraticIterator {
    fn clone(&self) -> ErraticIterator {
        self.0.set(self.0.get() + 1);
        
        Self(self.0.clone(), Some(()))
    }
}

impl Iterator for ErraticIterator {
    type Item = ();
    
    // Cycle behavior:
    //
    // Some(())
    // None -> .clone() -> None
    // Some(())
    // None -> .clone() -> None
    // ..
    fn next(&mut self) -> Option<()> {
        if self.0.get() % 2 == 0 {
            self.1.take()
        } else {
            None
        }
    }
}

pub fn fused_iter(it: &mut impl FusedIterator<Item = ()>) {
    it.for_each(|()| {});
    
    assert!(it.next().is_none());
}

fn main() {
    let it = ErraticIterator(Rc::new(Cell::new(0)), Some(()));
    fused_iter(&mut it.cycle())
}
```

I expected to see this happen: `Cycle<ErraticIterator>` should not be fuse thus compilation should fail.

Instead, this happened: Cycle implements FusedIterator, so the assertion fails that should always pass for actually fused iterators.
Repository: rust
Issue: LLVM ERROR: Do not know how to split the result of this operator!
Labels: A-LLVM,T-compiler,C-bug,A-LTO

There is a family of errors related to splitting that happen when building Firefox for android. I haven't managed to get a usefully reduced testcase. The gist of it is that it involves `-Clinker-plugin-lto` and linking being done outside cargo, between C/C++ and rust code with the i686-linux-android or x86_64-linux-android targets. The former fails with `LLVM ERROR: Do not know how to split the result of this operator!`, and the latter with `LLVM ERROR: Cannot select: 0x7fa32221e808: v16i8 = X86ISD::PSHUFB 0x7fa323d69d40, 0x7fa2ca5946d8, /rustc/d9aa28767287670df6cf823b94629122e04442c0/library/core/src/../../stdarch/crates/core_arch/src/x86/ssse3.rs:80:15 (...)`, and seems to be related to the lack of `target-features` in the LLVM-IR emitted by rust (that is, building my own rustc with [this condition](https://github.com/rust-lang/rust/blob/a17193dbb931ea0c8b66d82f640385bce8b4929/compiler/rustc_codegen_llvm/src/attributes.rs#L359) changed to `true` fixes the issue).

It seems to me rustc should always emit target-features, especially when using -Clinker-plugin-lto, where the LLVM that will read the LLVM bytecode doesn't necessarily have the same target definitions that rustc has.

This is how this can be reproduced:
- `hg clone https://hg.mozilla.org/mozilla-unified` or `git clone https://github.com/mozilla/gecko-dev`
- `cd mozilla-unified` or `cd gecko-dev`
- `mkdir ~/.mozbuild`
- `./mach --no-interactive bootstrap --application-choice mobile_android` (this might fail to install openjdk-8-jdk-headless depending on your distro, you might need to find and install it yourself, and try again)
- Restart your shell and return in the `mozilla-unified` or `gecko-dev` directory.
- Edit `mozconfig` to uncomment `ac_add_options --target=i686` and add `ac_add_options MOZ_LTO=cross`
- Run `rustup target add i686-linux-android`
- `./mach build`
Repository: flutter
Issue: [Proposal] Add CameraX Vendor Extensions support
Labels: c: new feature,platform-android,p: camera,package,c: proposal,P3,team-android,triaged-android

Ability to access on Android CameraX Vendor Extensions supported by given hardware.

https://developer.android.com/training/camerax/vendor-extensions
- Auto: automatically adjust the final image based on the surrounding scenery.
- Bokeh: make foreground people sharper when photos are taken in portrait mode.
- Face Retouch: skin-toning and other facial effects when taking still images.
- HDR(High Dynamic Range): taking photos with different AE settings.
- Night: take great still images under low-light situations, typically at night time.



labels:
p: camera
android
Repository: opencv
Issue: DNN(Int8): error messages from Quantized tests
Labels: bug,category: dnn

[Nightly build](http://pullrequest.opencv.org/buildbot/builders/master-lin64/builds/11688):

```
[ RUN      ] Test_ONNX_layers.Quantized_MatMul_Variable_Weights/0, where GetParam() = OCV/OCL
[ERROR:0] global modules/dnn/src/onnx/onnx_importer.cpp (744) handleNode DNN/ONNX: ERROR during processing node with 8 inputs and 1 outputs: [QLinearMatMul]:(2_quantized)
[       OK ] Test_ONNX_layers.Quantized_MatMul_Variable_Weights/0 (1 ms)
[ RUN      ] Test_ONNX_layers.Quantized_MatMul_Variable_Weights/1, where GetParam() = OCV/OCL_FP16
[ERROR:0] global modules/dnn/src/onnx/onnx_importer.cpp (744) handleNode DNN/ONNX: ERROR during processing node with 8 inputs and 1 outputs: [QLinearMatMul]:(2_quantized)
[       OK ] Test_ONNX_layers.Quantized_MatMul_Variable_Weights/1 (0 ms)
[ RUN      ] Test_ONNX_layers.Quantized_MatMul_Variable_Weights/2, where GetParam() = OCV/CPU
[ERROR:0] global dnn/src/onnx/onnx_importer.cpp (744) handleNode DNN/ONNX: ERROR during processing node with 8 inputs and 1 outputs: [QLinearMatMul]:(2_quantized)
[       OK ] Test_ONNX_layers.Quantized_MatMul_Variable_Weights/2 (0 ms)
```

Test cases don't fail.

relates #20228 #20535

/cc @vpisarev @SamFC10
Repository: rust
Issue: Coalesce inherent implementations with the same parameters
Labels: T-rustdoc,A-rustdoc-ui

Some types have multiple inherent impls that don't differ in terms of type parameters, but are just ways of organizing the code. For instance, [NonZeroU16 and friends](https://doc.rust-lang.org/beta/std/num/struct.NonZeroU16.html):

![image](https://user-images.githubusercontent.com/220205/138042264-741d64d8-5eb5-4060-85f3-5be7c61ca348.png)

Vec has some impls that are different from each other, but also `impl<T, A: Allocator> Vec<T, A>` shows up two separate times:

![image](https://user-images.githubusercontent.com/220205/138042318-8fa9f743-823e-4702-ba17-a7c549bb4db0.png)

We should coalesce these into a single `impl` block for each set of distinct parameters.

This came up while working on #85492: When I added sub-headings in the sidebar for multiple impls, I realized many more types than I thought had multiple impls.
Repository: rust
Issue: Tracking Issue for split_array
Labels: T-libs-api,C-tracking-issue,A-array

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(split_array)]`

This is a tracking issue for splitting slices and arrays into constant-length arrays.

### Public API

```rust
impl<T, const N: usize> [T; N] {
    pub fn split_array_ref<const M: usize>(&self) -> (&[T; M], &[T]);
    pub fn split_array_mut<const M: usize>(&mut self) -> (&mut [T; M], &mut [T]);

    pub fn rsplit_array_ref<const M: usize>(&self) -> (&[T], &[T; M]);
    pub fn rsplit_array_mut<const M: usize>(&mut self) -> (&mut [T], &mut [T; M]);
}

impl<T> [T] {
    pub fn split_array_ref<const N: usize>(&self) -> (&[T; N], &[T]);
    pub fn split_array_mut<const N: usize>(&mut self) -> (&mut [T; N], &mut [T]);

    pub fn rsplit_array_ref<const N: usize>(&self) -> (&[T], &[T; N]);
    pub fn rsplit_array_mut<const N: usize>(&mut self) -> (&mut [T], &mut [T; N]);
}
```

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

* [ ] Naming, see https://github.com/rust-lang/rust/pull/83233#pullrequestreview-780315524
* [ ] Array functions should return `[T; N - M]`, like so:
```rust
impl<T, const N: usize> [T; N] {
    pub fn split_array<const M: usize>(self) -> ([T; M], [T; N - M]);
    pub fn split_array_ref<const M: usize>(&self) -> (&[T; M], &[T; N - M]);
    pub fn split_array_mut<const M: usize>(&mut self) -> (&mut [T; M], &mut [T; N - M]);
}
```
However, const generics is not powerful enough for this today. See https://github.com/rust-lang/rust/pull/83233#issuecomment-947542204 and https://github.com/rust-lang/rust/pull/83233#discussion_r732722222. The array functions need to be here so the slice functions can be stabilized without forward compatibility concerns.
Repository: flutter
Issue: [Proposal] allow camera access to all hardware lenses
Labels: c: new feature,platform-android,p: camera,package,c: proposal,P3,team-android,triaged-android

## Use case
Most devices currently have 2+ cameras in the back.
Multi Camera implemented for Android 9+
https://developer.android.com/training/camera2/multi-camera

Developers should be able to get info about available cameras or at least set need for:

- wide lens photo
- telephoto
- standard lens
- ...

## Proposal
Ona Android 9+ and iOS 10+ have access to all cameras with information about their hardware such as 

- fov - field of view,
- hardware zoom,
- max resolution,
- facing backwards or to the user;

Sources:
- https://developer.android.com/training/camera2/multi-camera
- https://developer.android.com/training/camera2/camera-enumeration
- https://developer.apple.com/documentation/avfoundation/avcapturedevice/devicetype/3377621-builtintriplecamera
- https://developer.apple.com/documentation/avfoundation/avcapturedevice/devicetype/2361449-builtinwideanglecamera


labels:
p: camera
android, ios
Repository: kubernetes
Issue: Readiness probes should keep running (or pod marked as not ready) during graceful node termination
Labels: kind/bug,priority/backlog,sig/node,priority/important-longterm,triage/accepted

### What happened?

In this PR all probes were disabled during the graceful node termination https://github.com/kubernetes/kubernetes/pull/105215.

This may pose a problem when pods will keep being marked as ready fir the duration of a node termination. Ideally we need to keep readiness probes running

### What did you expect to happen?

Ideally we need to keep readiness probes running

### How can we reproduce it (as minimally and precisely as possible)?

Configure the pod with the readiness probe and observe during the node termination

### Kubernetes version

master branch - 1.23

/sig node
Repository: ant-design
Issue: Table - "Tree data" mode - Long string breaks view of first column
Labels: Inactive

- [x] 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/tree-data-antd-4-17-0-alpha-7-forked-fbqh3)

### Steps to reproduce
1. Create Table component with Tree data mode
1. Set data with long strings in main field to props (This field must be first column in table)
1. Try to open tree nodes

### What is expected?
The content of the first column is indented according to its level in the tree.

### What is actually happening?
The content of the first column is not indented according to its level in the tree.
Part of content (2nd, 3rd strings) starts from left border of table cell.

| Environment | Info |
|---|---|
| antd | 4.16.13 |
| React | 16.14.0 |
| System | Windows 10 |
| Browser | Google Chrome 94 |

---
Reproduced in latest versions. (4.17.0-alpha too)

It depends of width of screen / parent / column.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->