sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: [NSFW] [New Website request] Add support for hanime 
Labels: site-support-request

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs


Hanime website link - https://hanime.tv/

- Hanime Single video: https://hanime.tv/videos/hentai/jashin-shoukan-inran-kyonyuu-oyako-ikenie-gishiki-2




## Description

Nhentai is a website where we can read doujinshis and hanime is the website where we can watch hentai.
Repository: material-ui
Issue: LinearProgress and Switch should not be flipped in right-to-left themes
Labels: new feature,component: LinearProgress,component: switch,component: progress

RTL does not work correctly in progress bar and switch btns with styleProvider

hi
i use styleProvider for making rtl based on docs and everything works correct but linear progress bar and switch component are completely wrong and they are fliped
here is sandBox:
https://codesandbox.io/s/material-demo-forked-08r6g?file=/index.js

i would like switch button off state goes to left and progress bar start from left side
Repository: deno
Issue: Implement serializable and transferrable web platform APIs
Labels: feat,web

Deno's implementation of structured serialize currently supports serializing the JS built-in `SharedArrayBuffer`, and transferring the JS built-in `ArrayBuffer` as well as the `MessagePort` web API. With #11823 it will also support serializing the wasm built-in `WebAssembly.Module`.

But Deno also implements some web APIs that per the spec should be serializable or transferable but aren't in Deno's implementation. In particular, `DOMException`, `File`, `Blob` and `CryptoKey` should be serializable; and `ReadableStream`, `WritableStream` and `TransformStream` should be transferable.

Implementing this would probably need adding some `Deno.core` API to define serialization and transfer steps, possibly in connection to the existing `Deno.core.createHostObject()`. This would also allow refactoring the implementation of `MessagePort`.
Repository: vscode
Issue: Actions are unclickable in Modal dialog when opened through a CodeLens (and all mouse event on the system disabled)
Labels: bug,help wanted,linux,confirmed,dialogs,extensions-development

<!-- ⚠️⚠️ 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: Fedora 34

Steps to Reproduce:

1. Clone https://github.com/apupier/reproducer-codelens-warningmessage it contains an extension with a CodeLens callign a command whcih is showing a warnign message in modal mode
2. Launch the extension
3. Create a file named my.hello.txt
4. open it
5. click on Codelens
6. the modal dialog has unclickable buttons

-->  all other windows have unclickable items too, even unrelated VS Code windows!

Workaround to get out of this state is to hit `escape`

https://user-images.githubusercontent.com/1105127/133226304-05536c75-3465-425f-b8e9-078424565c81.mp4
Repository: rust
Issue: Unnecessary stack usage
Labels: A-LLVM,I-slow,T-compiler

I have the following simple SIMD-powered function which tests whether points are inside one of bounding boxes:
```rust
pub unsafe fn foo(
    x: &[__m256i; N],
    y: &[__m256i; N],
    z: &[__m256i; N],
    bboxes: &[[__m256i; 6]],
) -> [__m256i; N] {
    let mut res = [_mm256_setzero_si256(); N];
    for bbox in bboxes {
        for i in 0..N {
            let tx = _mm256_and_si256(
                _mm256_cmpgt_epi32(x[i], bbox[0]),
                _mm256_cmpgt_epi32(bbox[1], x[i]),
            );
            let ty = _mm256_and_si256(
                _mm256_cmpgt_epi32(y[i], bbox[2]),
                _mm256_cmpgt_epi32(bbox[3], y[i]),
            );
            let t = _mm256_and_si256(tx, ty);
            let tz = _mm256_and_si256(
                _mm256_cmpgt_epi32(z[i], bbox[4]),
                _mm256_cmpgt_epi32(bbox[5], z[i]),
            );
            let t = _mm256_and_si256(t, tz);
            res[i] = _mm256_or_si256(res[i], t);
        }
    }
    res
}
```
By inspecting the [generated assembly](https://rust.godbolt.org/z/6fahjYKGP) we can see that for some reason it caches coordinates to stack and reads them from it each iteration instead of using the input pointers. The same behavior can be [observed](https://rust.godbolt.org/z/c5hGxsrvP) for a function which processes coordinate slices.  This caching looks quite redundant to me, especially considering that `noalias` is enabled (i.e. compiler should know that memory at which coordinates are stored can not change during function execution).

It looks like LLVM correctly moves coordinate loads from the inner loop using its infinite virtual registers. And it's exactly the behavior we want when there is enough physical registers. But when it's not true, it spills virtual register values to stack instead of relying on the original locations.

On Rust 1.51 code from the first link does not have this issue, but not from the second one.

UPD: See this [comment](https://github.com/rust-lang/rust/issues/88930#issuecomment-1734619004) for additional example affecting cryptographic code..
Repository: godot
Issue: [Godot 4 & 3]Hiding Tree and Inspector Docks, gets black when opening again
Labels: bug,topic:editor,needs testing

### Godot version

3.3.4 beta-4

v4.0.dev.20210916.official [104a6191f]

### System information

manjaro Gnome 21, AMD R7 200 series, Intel i3 3.0 GHZ,8GB RAM

### Issue description

![image](https://imgur.com/1ixom35.png)

As you can see in the image above, the right and left docks are black.

### Steps to reproduce

I'm not sure how to reproduce it!

I was testing the game, and when opened the editor back, the docks where hidden, then I clicked: `Editor->Editor Layout->Default` and this result in the image above!

### Minimal reproduction project

N/a
Repository: pytorch
Issue: RandomSampler / DistributedSampler does not seem really random
Labels: oncall: distributed,module: dataloader

## 🐛 Bug

Training a net with DataLoader(..., shuffle=True) produces weird sawtooth artifacts in both loss and accuracy (train & test), indicating that the end of an epoch kind of looks like the beginning of the next one. The dataset needs to be big enough to observe this bias.

https://discuss.pytorch.org/t/observing-strange-loss-jumps-between-epochs/64066/15

This looks bad as it clearly biases gradients and might mess with momentum-based optimizers

## To Reproduce

I can reproduce this on imagenet and can provide the code, but it just boils down to shuffle=True or RandomSampler withtout replacement. It does not happen with some other datasets AFAIK.

## Expected behavior

There shouldn't be any sawtooth shape like that.

## Environment

 - PyTorch Version : latest stable
 - OS (e.g., Linux): Ubuntu
 - How you installed PyTorch (`conda`, `pip`, source): pip
 - Python version: 3.8
 - CUDA/cuDNN version: CUDA 11.0 and 11.1
 - GPU models and configuration: RTX 2080 (4x and 2x)


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @gcramer23 @SsnL @VitalyFedyunin @ejguan @cbalioglu
Repository: vscode
Issue: merge-conflict: Add compare {current,incoming} to original
Labels: feature-request,merge-conflict

<!-- ⚠️⚠️ 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. -->

I use 3-way merge conflict checking, where I can see all of the current changes, the original code, and the incoming changes. My workflow for resolving conflicts is to compare the original code to the current and then, separately, to the incoming changes. I can then figure out which changes are easier to port (say, reflect the original-to-incoming changes in the current code), and then actually port the changes. A critical step here is to be able to compare the original version against the updated versions.

VSCode's merge-conflict support allows me to easily compare the current code against the incoming code, but that's not nearly as actionable as comparing against the original code. Is it possible to add a feature where, in a 3-way conflict, I can compare current and incoming against original?

Useful prior art: emacs's `smerge-mode` allows the `smerge-refine` command, which cycles through the 3 possible comparisons (original/current, original/incoming, current/incoming).
Repository: youtube-dl
Issue: Add option to embed sub as synced lyrics tag.
Labels: request

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones
Repository: flutter
Issue: TextFormField with textAlign: TextAlign.right  whitespace doesn't show unless text is entered.
Labels: a: text input,framework,f: material design,has reproducible steps,found in release: 2.5,found in release: 2.6,team-design,triaged-design

 I use TextFormField and property textAlign: TextAlign.right in my web application but I see prob when typing space, it don't show if don't have any text after it :(
 Please help!
Repository: TypeScript
Issue: Inlay hints should support spread arguments for tuple types
Labels: Suggestion,Needs Proposal

Issue Type: <b>Bug</b>

Inlay hints don't support ~~rest params~~ spread parameters. 
For example, I'm using [this method](https://github.com/yomotsu/camera-controls#setposition-positionx-positiony-positionz-enabletransition-) which has the following signature:

``` ts
controls.setPosition(x: number, y: number, z: number, enableTransition: boolean);
```

And I want to pass in a `Vector3Tuple` as the position, say `[0,0,0]`:

``` ts
type Vector3Tuple = [number, number, number];

const position: Vector3Tuple = [0,0,0];

controls.setPosition(...position, false);
```

This is what I see for the inlay hints:

![inlay rest](https://user-images.githubusercontent.com/5307958/133195439-d297413e-4705-4fea-9b84-b7d2b8c7a662.png)

In other words, `...position` is showing as a single argument when it should be three. 

If I expand the arguments, it does correctly show the hints:

![inlay explicit](https://user-images.githubusercontent.com/5307958/133195712-449eae12-4b00-43b8-b239-dcb678814fcf.png)

I'm not sure what the inlay hints should show for `...position`, however, the final parameter of `false` should correctly show `enableTransition`. 

VS Code version: Code 1.60.0 (e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff, 2021-09-01T10:41:52.311Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2


<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Show both narrowed type and declared type
Labels: Suggestion,Needs Proposal

# Suggestion

<!--
  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:
-->

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.

## ✅ 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:

* [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

<!-- 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?
-->

https://twitter.com/Rich_Harris/status/1437490023763415043

is roughly a confusion on narrowed vs storage type of a given field/binding

```mjs
// _: any
let _;

// _: any
_ = new Date();

// _: any, but completions from Date
// type doesn't match usability, only assignability
_.getFullYear();
```

## 💻 Use Cases

<!--
  What do you want to use this for?
  What shortcomings exist with current approaches?
  What workarounds are you using in the meantime?
-->

Current UI / typing only shows what can be assigned to a value storage location given a source text location.
Need UI to show what can be used from a value storage location given a source text location.

Much of the time these should be the same but showing something about the narrowing would apparently remove some confusions, for example (bikeshed):

```mjs
let _;
_ = new Date();

// _: any
_;

// becomes...

// _: any as Date
_;
```
Repository: pytorch
Issue: FX failed to normalize op `block_diag` and `broadcast_tensors`
Labels: triaged,module: fx

Got this error when creating opInfos for `block_diag` and `broadcast_tensors`. Added to skip list for now.
The issue could be that both `block_diag` and `broadcast_tensors` are variadic.
```
======================================================================
ERROR: test_normalize_operator_exhaustive_broadcast_tensors_cpu_float32 (__main__.TestNormalizeOperatorsCPU)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/local/pytorch/torch/testing/_internal/common_device_type.py", line 378, in instantiated_test
    raise rte
  File "/home/local/pytorch/torch/testing/_internal/common_device_type.py", line 373, in instantiated_test
    result = test(self, **param_kwargs)
  File "/home/local/pytorch/torch/testing/_internal/common_device_type.py", line 766, in test_wrapper
    return test(*args, **kwargs)
  File "/home/local/pytorch/torch/testing/_internal/common_device_type.py", line 913, in only_fn
    return fn(slf, *args, **kwargs)
  File "test/test_fx_experimental.py", line 1543, in test_normalize_operator_exhaustive
    raise RuntimeError(
RuntimeError: 
                    FX failed to normalize op - add the op to the op_skip list.
                    A common reason is if your OpInfo was implemented with a lambda
                    - otherwise, file an issue
```
Same error for `block_diag`

Test is also failing for `test_get_torch_func_signature_exhaustive`. Added to skip list for that as well for now.

cc @ezyang @SherlockNoMad
Repository: tauri
Issue: [MacOS / Linux] WebKit doesn’t set Secure cookies on localhost
Labels: type: bug,status: upstream,platform: Linux,platform: macOS

### **Describe the bug**
Thank you for the amazing work, progress and transparency with the community.

I’m going through a challenge with WebKit. I’ll try to be a brief as possible.

My app is based on Nuxt, using Nuxt Auth with HTTPOnly and Secure Cookie, Axios, and connects to the backend through Axios proxy and _withcredentials_.

I found out that my app was not login in on Safari/Tauri. After taking a look when it comes to setting Secure cookies locally, not all browsers behave in the same way. For example, **Safari doesn’t set Secure cookies on localhost**, but Firefox and Chrome do.

To test, I generated a local SSL Certificate and it works on Safari and Tauri Dev but not on Tauri Build.

`Set-Cookie: XSRF-TOKEN=eyJ0eXAiOiJK; expires=Fri, 08 Oct 2021 18:47:22 GMT; HttpOnly; Max-Age=2592000; Path=/; SameSite=Lax; Secure`

### **References**
https://web.dev/when-to-use-local-https/

#### **Update**
The same behavior is happening in the Linux environment.
Repository: flutter
Issue: TextField with lots of text can hang app
Labels: a: text input,framework,c: performance,perf: speed,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,team-framework,triaged-framework

For example, this app:

```dart
import 'package:flutter/material.dart';
import 'package:flutter/widgets.dart';

void main() {
  final TextEditingController controller = TextEditingController();
  runApp(
    MaterialApp(
      home: Material(
        child: Center(
          child: Column(
            children: [
              TextField(controller: controller),
              TextButton(
                onPressed: () {
                  controller.text = 'abcdef' * 100000;
                },
                child: Text('Fill'),
              ),
            ],
          ),
        ),
      ),
    ),
  );
}
```

on my MacBook pro causes the app to freeze after pressing fill. I discovered this when accidentally pasting a very large amount of text into a text field while testing something else. In that case, the text field probably also had some extra styling and input formatters, and the app completely hung (and hot restarting caused it to crash). This sample app does not crash on hot restart, but I suspect adding formatters or making the text even larger might cause it to.
Repository: react
Issue: [React 18] Optimized React Server Components's webpack bundling
Labels: Type: Discussion,React 18

In a chat between Facebook and Shopify about React Server Component, @sebmarkbage had mentioned the need to improve React Server Component's bundling strategy in webpack.

> The main thing is that by default you end up with way too many small chunks. You could use a telemetry based heuristic to inform bundling but without it, we think the best guidance is to analyze the server component's graph to group client components together by which server components use them.
We expect that the server will need to be built too, as a separate graph since best perf is gained when you prebuild the server anyway.
So it might be that the best API is building the server first and then using the data from that as input to building the client.

Looking at [RSC demo app](https://github.com/reactjs/server-components-demo), there are a total of 8 `*.client.js` files, and 5 of them ended up as separate bundles using the current [webpack plugin](https://github.com/facebook/react/blob/main/packages/react-server-dom-webpack/src/ReactFlightWebpackPlugin.js).

This issue’s main goal would be to investigate the current webpack plugin implementation and figure out any optimization that can be applied while keeping in mind React core team’s guidance of “building the server first and then using the data from that as input to building the client.” as an initial starting point.
Repository: pytorch
Issue: Traceback tensor mode
Labels: feature,triaged,better-engineering

Traceback tensor mode is like anomaly mode but what it does is associate every tensor with a traceback recording when the tensor was allocated, so you can easily debug where an unexpected tensor comes from even when you are not familiar with the codebase. It is trivially implementable after Richard's https://github.com/pytorch/pytorch/pull/64360

cc @zou3519 @albanD
Repository: react
Issue: Bug: Native Component Stacks don't respect function "displayName" in Firefox
Labels: Status: Unconfirmed,Type: Discussion

**Edit** See this comment for the key part of what's being reported/discussed on this issue: https://github.com/facebook/react/issues/22315#issuecomment-920061727

# Original bug report below

As of #18561 component stacks are generated from native stack frames. This is problematic with HOCs that inherit from the input component in order to change its behavior. The somewhat popular @risingstack/react-easy-state package is one example of such a component. While it does assign a `displayName`, the new Native Component Stacks appear to ignore this. Instead, components wrapped in `view()` (from react-easy-state) are always shown with the name of the wrapper class, i.e., `ReactiveComp` or `ReactiveClassComp`.

This is especially catastrophic in the case of react-easy-state, where one is supposed to wrap essentially *all components in the entire codebase* in the `view()` HOC. The result is that component stacks become unusable for debugging.

Is there perhaps a way to work around this (e.g. disable native component stacks, or some new way to explicitly provide a component name like `displayName`)?

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 17.0.1

## Steps To Reproduce

1. Apply a HOC that uses inheritance (i.e., inherits from the component instead of wrapping it in JSX) to a component.
2. The component will always be named `ReactiveComp` or `ReactiveClassComp` in component stack traces.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://codesandbox.io/s/rough-tdd-wqepe?file=/src/App.tsx

## The current behavior

```
Something went wrong.
Error: sorry

BadGuy@https://7ww9j.csb.app/src/App.tsx:21:9
ErrorBoundary@https://7ww9j.csb.app/src/App.tsx:33:5
div
App
```
```
Something went wrong.
Error: sorry

ReactiveComp@https://7ww9j.csb.app/node_modules/@risingstack/react-easy-state/dist/es.es6.js:62:53
ErrorBoundary@https://7ww9j.csb.app/src/App.tsx:33:5
div
App
```

Note how the component wrapped in `view()` is shown as `ReactiveComp` instead of either the function name or the explicitly assigned `displayName`.

## The expected behavior

The name of the `ReactiveComp` wrapper should never appear in component stacks.