sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Allow dub language selection for Funimation
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.04.01. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.04.01**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

Funimation offers multiple dubs, usually English and Japanese. 

By default English is selected and downloaded but I only want the Japanese dub (or both if that's possible).

AFAICT there is no option in youtube-dl to select the dub language it should download.

You can force a certain language on the website using `?lang=japanese` and such URLs work in youtube-dl for singular episodes but appending it to playlists doesn't work as youtube-dl interprets `?lang=japanese` as an episode path and that obviously doesn't exist.
Repository: terminal
Issue: Research how often the existing "duplicateTab" and duplicate pane actions are used
Labels: Issue-Bug,Area-Settings,Product-Terminal,Priority-3,Gathering-Data

The name suggests that it should duplicate the whole pane tree.

Should we remove it until it does? It's just confusing otherwise.

[DH: I bet we get a lot of calls about it not duplicating the panes.]

_originated in 4/2 bug bash_
Repository: create-react-app
Issue: Memory leak if setState set to previous state
Labels: needs triage,issue: bug report

### Describe the bug

If setState is set to the previous state, a memory leak is produced. 
Very strangely I could not reproduce this in a [sandbox](https://stackblitz.com/edit/react-memory-leak), only a create-react-app application hence why I am raising it here.

### Did you try recovering your dependencies?
Reproduced with a fresh create-react-app. 

### Environment

```
Environment Info:
  current version of create-react-app: 4.0.3
  running from C:\Users\hamis\AppData\Roaming\npm-cache\_npx\17828\node_modules\create-react-app

  System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
  Binaries:
    Node: 12.18.2 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 89.0.4389.114
    Edge: Spartan (44.19041.423.0), Chromium (89.0.774.68)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    react-scripts: latest => 4.0.3
  npmGlobalPackages:
    create-react-app: Not Found

```
### Steps to reproduce
The following code snippet produces the memory leak. When the memoryLeak flag is true, it will just set state to the previous state. Turning this flag off alternates the state and results in no memory leak.
```
import { useState, useEffect } from 'react';
const memoryLeak = true;
export default function App() {
  const [someState, setSomeState] = useState(false);
  useEffect(() => {
    const interval = setInterval(() => setSomeState(state => memoryLeak ? state : !state), 100);
    return () => clearInterval(interval);
  }, []);
  return <div>Test Memory Leak</div>;
}
```

Example project reproduction:
1. `git clone https://github.com/Haemoglobin/react-memory-leak.git`
2. `npm install`
3. `npm run build` (to prove it's not a development build issue)
3. npx http-server build
4. Navigate to http://localhost:8080
5. Open dev tools, navigate to Memory tab, start new "Allocation instrumentation on timeline" session

### Expected behavior
React should not do anything if state is set to the previous value. 
All objects reclaimed by the garbage collector. 
![image](https://user-images.githubusercontent.com/204224/113739814-1008cc80-96f8-11eb-9674-902b6e219a40.png)

(the above screenshot was taken by flipping the toggle in the example project which sets the state to a different value, rather than the same value) 

### Actual behavior
1. Observe lots of blue bars in the profiler indicating objects that are not being reclaimed by the garbage collector, click "Collect Garbage" button, stop profile session.
2. Select a section of blue bars and note the retained react objects with a very deep distance to the GC root
![leak](https://user-images.githubusercontent.com/204224/113742897-ff0d8a80-96fa-11eb-9208-6e5261746cc2.png)

### Reproducible demo
https://github.com/Haemoglobin/react-memory-leak
Repository: three.js
Issue: Export USDZ often inflates file size
Labels: Needs Investigation

A significant number of downloaded usdz files are greatly inflated in size compared to their .glb source. The attached model is a 1578 KB .glb, but the exported .usdz is 22,192 KB -- a 14-fold increase in size.
[GlassTable.zip](https://github.com/mrdoob/three.js/files/6266556/GlassTable.zip)

Steps to reproduce the behavior:
1. Add .glb to scene at https://threejs.org/editor/
2. File > Export USDZ
3. Compare file sizes

I would expect the .usdz to be fairly close in size to the .glb.  Other tools such as Vectary and Gestaltor convert the same file to a a usdz of comparable size (i.e. Vectary version is 1106 KB). 

 - Device: [Desktop]
 - OS: [Windows]
 - Browser: [Chrome]
 - Three.js version: [dev, r127]
Repository: pytorch
Issue: [FX][testing] Test tracing into all the standard `nn.Module` instances
Labels: triaged,module: fx

We currently have a study on the traceability of standard torch.nn Module instances and torch.nn.functional instances: https://docs.google.com/document/d/1n_H0Lut88G0byd_RQPDzoaRk4BM6NzYLEkrBB0ZGdyc/edit?usp=sharing

We should add the Module traceability tests to our test suite (probably `test/test_fx.py`) and ensure that they are run in CI. This will allow us to track traceability of `Modules` and flag when a `Module` becomes untraceable and fix it. As mentioned in the note, some of these Modules may not be currently traceable, and we can add those to an exception list

cc @ezyang @SherlockNoMad
Repository: pytorch
Issue: [FX][testing] Test tracing into all the standard `torch.nn.functional` instances
Labels: triaged,module: fx

We currently have a study on the traceability of standard torch.nn Module instances and torch.nn.functional instances: https://docs.google.com/document/d/1n_H0Lut88G0byd_RQPDzoaRk4BM6NzYLEkrBB0ZGdyc/edit?usp=sharing

We should add the `nn.functional` traceability tests to our test suite (probably test/test_fx.py) and ensure that they are run in CI. This will allow us to track traceability of functionals and flag when a functional becomes untraceable and fix it. As mentioned in the note, many of these functionals may not be currently traceable, and we can add those to an exception list

cc @ezyang @SherlockNoMad
Repository: pytorch
Issue: [FX][testing] Run symbolic tracing tests over torch benchmark in CI
Labels: triaged,module: fx

We currently have a set of benchmark models in this repo: https://github.com/pytorch/benchmark

It would be nice to be able to test symbolic tracing of these models in our tests (e.g. `test/test_fx.py`) and in CI (should be covered if we put tests in `test_fx.py`). I think what we'd need to figure out is: can PyTorch depend on `pytorch/benchmark` in CI? Then we need to look at the API of torch benchmark and see how we can pull as many of those models into the test cases and symbolically trace them. Then, we can triage any issues seen when trying to symbolically trace the models

cc @ezyang @SherlockNoMad
Repository: go
Issue: x/tools/gopls: vendor go/parser
Labels: gopls,Tools,gopls/parsing

Gopls depends on go/parser error recovery, and has various targeted workarounds where go/parser error recovery is not sufficient (`fixSrc`, `fixAST`). It also has tests that assert on behavior in the presence of invalid syntax.

As we work on improving the built-in error recovery in go/parser, these workarounds and tests present a difficult target to hit across Go versions. The easiest solution for this is probably to vendor go/parser so that we have consistent parser behavior for all supported go versions.

Another consideration is that some of the changes to parser error recovery we want to make for gopls might not be suitable for upstreaming to go/parser. For example, it might make sense for gopls to attempt multiple error recovery modes and choose the result with the fewest errors / most parsed syntax. Something like that would be very hard to support in go/parser, where simplicity and efficiency are critical, and which (mostly) targets valid source.  Conceivably we could have some methodology for maintaining a patch on top of go/parser, and/or adding extensibility points to go/parser.

This would not be without its downside: as we have seen with e.g. x/tools/go/internal/gcimporter, there is a non-trivial amount of work and risk associated with maintaining a copy. Nevertheless, on balance I think it's worth doing.

CC @stamblerre @heschi
Repository: pytorch
Issue: [FX][testing] Test symbolic tracing of detectron2
Labels: triaged,module: fx

[detectron2](https://github.com/facebookresearch/detectron2) is an object detection system written in PyTorch. We should investigate if this set of models is symbolically traceable and add tests in `test/test_fx.py` to ensure these things stay traceable in the future. A prerequisite to this is the tests depending on detectron2. I don't know if that's possible or not.

cc @ezyang @SherlockNoMad
Repository: pytorch
Issue: [FX][testing] Add symbolic tracing tests for torchtext
Labels: triaged,module: fx

[torchtext](https://github.com/pytorch/text) is a domain library for text processing networks. We should add tests in `test/test_fx.py` to test whether the models provided in this package are symbolically traceable. A prerequisite to this is the tests depending on torchtext. I don't know if that's possible or not.

cc @ezyang
Repository: pytorch
Issue: [FX][testing] Add symbolic tracing tests for torchaudio
Labels: triaged,module: fx

[torchaudio](https://github.com/pytorch/audio) is a domain library for text processing networks. We should add tests in test/test_fx.py to test whether the models provided in this package are symbolically traceable. A prerequisite to this is the tests depending on torchaudio. I don't know if that's possible or not.


cc @ezyang
Repository: flutter
Issue: Have Flutter Tools expose an API on the VM Service indicating whether a running device is an emulator
Labels: c: new feature,platform-android,tool,P3,team-android,triaged-android

There is an issue where Samsung devices can look like emulators. Good news is that real emulators show zero for graphics memory (as reported by ADB) and we can use that fact to detect real emulators.
This would help for tooling that we should never show on emulators such as warnings about slow frames or graphics memory debugging tooling.
Fyi @jonahwilliams
Repository: youtube-dl
Issue: please support Voice of han audio download
Labels: site-support-request


<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.04.01. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.04.01**
- [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

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single audio: https://audio.voh.com.tw/TW/Playback/ugC_Playback.aspx?PID=70

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

WRITE DESCRIPTION HERE
Repository: rust
Issue: Allow non-ascii-idents in extern blocks
Labels: C-enhancement,F-non_ascii_idents

[RFC 2457](https://github.com/rust-lang/rfcs/pull/2457) disallows non-ascii idents in extern blocks and `no_mangle`.

We added an error for extern blocks in https://github.com/rust-lang/rust/issues/83923 (`no_mangle` already errors).

We should figure out if we can allow these -- we'd need to make sure the name mangling schemes consistently handle non-ASCII. I believe at the moment MSVC gets grumpy about this.
Repository: youtube-dl
Issue: please support RTI radio taiwan international audio
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.04.01. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.04.01**
- [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

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single audio: https://www.rti.org.tw/radio/programMessagePlayer/programId/10/id/122890

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

WRITE DESCRIPTION HERE
Repository: godot
Issue: Tween property stacking can lead to memory leak
Labels: bug,topic:animation

**Godot version:**
3.2 branch (commit 94a0fc47f7)

**Issue description:**

When calling successive `interpolate_property`/`follow_property` on the same (object, property), previous existing `InterpolateData` persists. I know that maybe this is intended, but at least warn the user when a new property interpolation is being overridden? I was calling `stop()` before calling `interpolate_property()` for the same property and it took some time to identify that I was memory-leaking internal `InterpolateData`s, because they weren't being processed (so never removed)...

On a custom build, calling `remove(object,property)` inside every `interpolate_property(object, property)` solves this issue, but maybe there is a better solution? Maybe only a note on documentation?

**Steps to reproduce:**
```gdscript


func _process(delta):
	stop_all()
        var sprite_node = get_parent()
	var random_target_pos = get_viewport().size * Vector2( randf() , randf() )
	interpolate_property( sprite_node  ,"position", sprite_node.position, random_target_pos,1)
	start()
```

**Minimal reproduction project:**
[tween_memory_leak.zip](https://github.com/godotengine/godot/files/6267415/tween_memory_leak.zip)
Repository: go
Issue: cmd/link: would like a way to emit DT_RPATH tags (instead of DT_RUNPATH)
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

Anything (since the linker's -r flag was added in 2010 anyway)

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

Ubuntu 20.04, but really: any ELF system.

### What did you do?

I maintain the Go snap, which is a "classic snap": classic snaps run in the same mount namespace as everything else but load dynamic libraries from a "core" snap, which is mounted at a path like /snap/core18/current. To do this, they need to have a DT_RPATH like /snap/core18/current/lib/x86_64-linux-gnu. The linker's -r option causes a DT_RUNPATH tag to be used, which doesn't work for the reasons explained in https://www.qt.io/blog/2011/10/28/rpath-and-runpath. (It almost works, but when glibc tries to load a NSS component, it loads it from the host not the core snap and that can break).

It would be a trivial change to the linker to add an option "-rpath-instead-of-runpath" or whatever, but would that be acceptable?
Repository: scrcpy
Issue: Start maximized
Labels: feature request

Do it is possible to start scrcpy maximized in Windows, without to have to click che window button?

the help have a tiny error:

>     --window-height value
>         Set the initial window width.
>         Default is 0 (automatic).
Repository: flutter
Issue: [web] App crashing when browser doesn't support MediaQueryList listener
Labels: platform-web,customer: web10,P2,team-web,triaged-web

Cobalt browser doesn't implement listener. Engine should do feature check before calling.
Same for Navigator.platform.
Repository: next.js
Issue: productionBrowserSourceMaps doesn't work with profiler
Labels: bug

### What version of Next.js are you using?

`latest` in package.json at time of submission - 10.1.3

### What version of Node.js are you using?

14.16.0

### What browser are you using?

chrome

### What operating system are you using?

macOS

### How are you deploying your application?

next build --profile; next start (local in prod mode)

### Describe the Bug

Starting with `npx create-next-app --example with-typescript with-typescript-app`, I added: 

```
module.exports = {
  productionBrowserSourceMaps: true,
}
```
to next.config.js, and I altered `npm run build` to run:
```
    "build": "next build --profile",
```

Then when I did a build and a start, the React Profiler doesn't show the proper names of the components:
<img width="470" alt="image" src="https://user-images.githubusercontent.com/31303/113789310-bacabc00-96f3-11eb-8eb4-d6253a58f375.png">

### Expected Behavior

In prod mode with --profile and productionSourceMaps, I expect profiler to show proper names of components:

<img width="473" alt="image" src="https://user-images.githubusercontent.com/31303/113789386-d6ce5d80-96f3-11eb-9945-20b96ef8c265.png">

### To Reproduce

See above, I used `with-typescript` and altered two files.
Repository: create-react-app
Issue: Support for inline source maps
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

I have a React application that is hosted on a server application using Windows authentication. This unfortunately means that VS Code is (currently) not able to debug this React application since it is not able to retrieve the source maps files (see [this issue](https://github.com/microsoft/vscode-chrome-debug-core/issues/5)).

A common workaround is to use inline source maps (for development) but unfortunately, `react-scripts` does not support this.

### Describe the solution you’d like

I would like to see an option to configure CRA to generate inline source maps instead of separate source map files. I would be fine if this was limited to development time only, replacing the `cheap-module-source-map` configuration there:

https://github.com/facebook/create-react-app/blob/2d1829eaf6ff1308da00720fa9984620dd0fb296/packages/react-scripts/config/webpack.config.js#L177-L181

Since there is already a built-in option to disable source maps altogether using the [`GENERATE_SOURCEMAP` environment variable](https://github.com/facebook/create-react-app/blob/2d1829eaf6ff1308da00720fa9984620dd0fb296/packages/react-scripts/config/webpack.config.js#L45), I think it would be feasible to allow affecting _how_ the source maps would be generated through an additional environment variable.

### Describe alternatives you’ve considered

There is already an [open issue](https://github.com/microsoft/vscode-js-debug/issues/425) on the VS Code side for this, but even if they were able to fix this soon, I don’t actually expect that they will be able to solve this for Windows authentication as well. So right now, I’m left with a hacky workaround to disable the authentication completely, or to debug this in the browser (where source maps are loaded successfully).

Of course, I could also eject the webpack configuration but I would prefer not to do that to keep the build complexity as low as possible for the app.


If it helps, I would be willing to contribute such an option if the proposal receives the necessary support.