sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: [RUMBLE] Make --write-comments work
Labels: site-enhancement,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a site-specific feature
- [X] I've verified that I'm running yt-dlp version **2023.03.04** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and 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)
- [X] 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

Norway

### Example URLs

ttps://rumble.com/v1cdyzf-fritz-springmeier-exposing-the-nwo-illuminati-agenda-on-fri.-night-livestre.html

### Provide a description that is worded well enough to be understood

              Not all data is extracted for all sites. Feel free to open a "site feature request"

_Originally posted by @pukkandan in https://github.com/yt-dlp/yt-dlp/issues/4285#issuecomment-1515656262_
            
Since the json file downloaded from Rumble when applying the `--write-comments` option doesn't in fact include the Comments section, I request that steps be taken to make sure this option works on Rumble videos!


### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [X] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
yt-dlp --write-comments https://rumble.com/v1cdyzf-fritz-springmeier-exposing-the-nwo-illuminati-agenda-on-fri.-night-livestre.html
[Rumble] Extracting URL: https://rumble.com/v1cdyzf-fritz-springmeier-exposing-the-nwo-illuminati-agenda-on-fri.-night-livestre.html
[Rumble] v1cdyzf-fritz-springmeier-exposing-the-nwo-illuminati-agenda-on-fri.-night-livestre.html: Downloading webpage
[RumbleEmbed] Extracting URL: https://rumble.com/embed/v19rt1x
[RumbleEmbed] v19rt1x: Downloading JSON metadata
[info] v19rt1x: Downloading 1 format(s): mp4-1081p
[info] Writing video metadata as JSON to: Fritz Springmeier - Exposing the NWO Illuminati Agenda on Fri. Night Livestream [v19rt1x].info.json
[download] Destination: Fritz Springmeier - Exposing the NWO Illuminati Agenda on Fri. Night Livestream [v19rt1x].mp4
[download]   0.5% of    4.73GiB at    7.30MiB/s ETA 10:59^C
ERROR: Interrupted by user
```
Repository: godot
Issue: Small Deploy with Network FS: can't connect to host, even though remote debug works
Labels: bug,platform:android,topic:network,topic:export

### Godot version

4.0.2 / 3.5.2

### System information

Windows 10 x64

### Issue description

When you use the Small Deploy option, the exported project does not load. It's stuck on splash screen and this is printed in the console over ADB:
```
04-20 16:23:45.840 17429 21078 E godot   : ERROR: Condition "!is_connected_to_host()" is true.
04-20 16:23:45.840 17429 21078 E godot   :    at: set_no_delay (core\io\stream_peer_tcp.cpp:227) - Condition "!is_connected_to_host()" is true.
04-20 16:23:45.840 17429 21078 E godot   : ERROR: Condition "!accesses.has(id)" is true.
04-20 16:23:45.840 17429 21078 E godot   :    at: _thread_func (core\io\file_access_network.cpp:113) - Condition "!accesses.has(id)" is true.
```
Using the Deploy with Remote Debug works correctly, only the Small Deploy can't connect for some reason.

### Steps to reproduce

1. Add Android export preset
2. Enable Small Deploy in Debug menu
3. Start the project with Remote Debug option

### Minimal reproduction project

N/A
Repository: pytorch
Issue: Parameterisation of MultivariateNormal distribution using Cholesky decomposition of precision matrix
Labels: module: distributions,feature,triaged

### 🚀 The feature, motivation and pitch

Currently, the `MultivariateNormal` distribution is parameterised based on the Cholesky factor of the covariance matrix, referred to in the code as `scale_tril` (I'm unsure where this naming comes from). While the distribution can be initialised with the full covariance or precision matrix instead, these are simply used to calculate `scale_tril` which is then used as the basis for all calculations, presumably for efficiency and numerical stability.

It is however possible to parameterise the distribution with Cholesky factor of the precision matrix. One possible implementation is laid out in [this report](https://arxiv.org/pdf/2003.05739.pdf) presented by a contributor to [FrEAI](https://github.com/vislearn/FrEIA), a PyTorch library for invertible NNs. The report argues a better numerical stability than traditional parameterisation, something which I have confirmed in my experiments (see “Additional context” section below).

I'm happy to work on this request myself. I have a working implementation of the `log_prob` and `sample` methods and am happy to work on expanding this to match the full `Distribution` interface and then integrating this into the existing implementation. One question would be whether this replaces the current functionality, or if this is activatable via a flag.

### Alternatives

A [PyTorch implementation of a GMM using this parameterisation](https://github.com/vislearn/FrEIA/blob/master/FrEIA/modules/gaussian_mixture.py) exists in [FrEAI](https://github.com/vislearn/FrEIA) but this is...
1. A full Gaussian mixture model, not a single multivariate distribution.
2. Built to be part of an invertible network, which makes the implementation difficult to use for non-invertible cases.

### Additional context

My use case is implementing a [Mixture Density Network](https://publications.aston.ac.uk/id/eprint/373/) to predict the parameters of a Gaussian Mixture Model for high-ish dimensional data (31 dimensions). I find the existing implementation of the `MultivariateNormal` distribution quickly runs into numerical stability issues and returns NaNs when calculating the log probabilities.

cc @fritzo @neerajprad @alicanb @nikitaved
Repository: next.js
Issue: Application error: a client-side exception has occurred
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
❯ npx --no-install next info

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.18.0
      pnpm: 6.11.0
    Relevant packages:
      next: 12.3.4
      eslint-config-next: N/A
      react: 17.0.2
      react-dom: 17.0.2
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://carrot.link

### To Reproduce

It seems the way to reproduce it is to have a window/tab open to our production site. And when a new version of the site has been deployed, when user navigates back to that tab, the page throws the "Application error: a client-side exception has occurred" error

![image](https://user-images.githubusercontent.com/49030/233413198-a1211e03-6a08-42b5-b225-2f916fb7fac4.png)


### Describe the Bug

What we have observed is that when a user has a tab open to our site for a while, and while they have the tab open (possibly in the background), and we deploy a new version of the site... when the user navigates to that tab, we see the error mentioned (screenshot below.) -- once the user refreshes the page, the error goes away

![image](https://user-images.githubusercontent.com/49030/233413609-33aede8c-1d24-4550-904c-e433ecbcb6cb.png)


### Expected Behavior

We expect the site to continue working as expected and not through the client-side error. it seems like old site assets no longer exist and are throwing 404's. maybe there is a way to cache site assets across deploys?

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: bitcoin
Issue: meta: Isolated fuzzing of net processing
Labels: Brainstorming,Tests

Efficient isolated fuzzing of our message processing code (net processing) would be very valuable. However, to make that deterministic, fast and fuzzer friendly it appears that extensive refactoring is required. There are three main blockers: module separation (net/net processing/validation split), determinism, performance.

I am gonna use this issue to track and motivate the work that needs to be done. It would be great if we can achieve the same outcome with less refactoring but I don't see how at the moment. Open to suggestions and feedback.

### Module separation

Once we have a clean separation between our net, net processing and validation modules, we can fuzz/test them in isolation to maximize the bug yield (🐛, 🪲, 🪳). By design, most fuzzing engines are not great at finding bugs when the scope of the targets is too large (e.g. fuzzing net, net processing and validation all at once).

* net / net processing split (https://github.com/bitcoin/bitcoin/pull/28252)
  * Move application layer data from net to net processing ([#19398](https://github.com/bitcoin/bitcoin/issues/19398))
    - [ ] https://github.com/bitcoin/bitcoin/pull/26621
  * Define a clean interface between net processing <-> net 
    - [ ] https://github.com/bitcoin/bitcoin/pull/25268
      - [x] https://github.com/bitcoin/bitcoin/pull/25500
      - [ ] https://github.com/bitcoin/bitcoin/pull/25572
    - [x] https://github.com/bitcoin/bitcoin/pull/27257
* net processing / validation split (lots of overlap with kernel)
  * Reduce `cs_main` usage in net processing
    - [ ] https://github.com/bitcoin/bitcoin/pull/26151
    - [x] https://github.com/bitcoin/bitcoin/pull/26140
    - [ ] Kill CNodeState
  * Define a clean interface between net processing <-> validation

### Determinism

Non-deterministic fuzz targets are less efficient at finding bugs and debugging non-reproducible bugs is annoying/costly.

* All required components should be newly setup for each target execution
  * Can be done currently using our testing setup suite but that's waaaay too slow for fuzzing.
* Avoid  `GetRand()` (mock it?)
* Avoid globals (are there any globals left in net processing?)

### Performance

Fuzzing is a search, the faster the search - the better.

* LevelDB (is in memory but still slow?)
  * Probably solved by mocking out validation?
* PeerManager construction is expensive because it requires multi megabyte allocations each time (mostly due to large bloom filters)
* Disk usage
  * Block storage
    - [x] https://github.com/bitcoin/bitcoin/pull/27125
    - [ ] Create a mock of BlockManager for in memory block storage?
  * BanMan (banlist is written to disk)

### Misc

* Decouple net processing from ArgsMan (args setup is slow)
  * Allows to fuzz the peerman options without depending on the global args man 
  - [x] https://github.com/bitcoin/bitcoin/pull/27499

---

Please let me know if you think there are PRs that aren't listed here but should be.
Repository: node
Issue: TextDecoder: ERR_ENCODING_INVALID_ENCODED_DATA on very long array buffer
Labels: util

### Version

v18.14.1

### Platform

Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

_No response_

### What steps will reproduce the bug?

When I try to decode a long utf-16le encoded buffer, ERR_ENCODING_INVALID_ENCODED_DATA is thrown instead of ERR_STRING_TOO_LONG.
```js
new TextDecoder("utf-16le").decode(new Uint16Array(2**27).fill(48))
// Uncaught TypeError: The encoded data was not valid for encoding utf-16le
//     at TextDecoder.decode (node:internal/encoding:448:14) {
//   code: 'ERR_ENCODING_INVALID_ENCODED_DATA'
// }
```
The default encoding version seems to work correctly, and throws an appropriate error
```js
new TextDecoder().decode(new Uint8Array(2**29).fill(48))
// Uncaught Error: Cannot create a string longer than 0x1fffffe8 characters
//     at TextDecoder.decode (node:internal/encoding:433:16) {
//   code: 'ERR_STRING_TOO_LONG'
// }
```
Another thing that I realized is that `TextDecoder()` seems to be capable of consuming an array buffer twice as long as `TextDecoder("utf-16le")` without throwing error, and produce a string that's 4 times as long.

### How often does it reproduce? Is there a required condition?

Confirmed this bug in both normal file execution and node.js repl

### What is the expected behavior? Why is that the expected behavior?

`new TextDecoder("utf-16le")` should be able to create a string up to 0x1fffffe8 characters.
It should throw ERR_STRING_TOO_LONG when this length is exceeded.

### What do you see instead?

ERR_ENCODING_INVALID_ENCODED_DATA is thrown when the input Uint16Array length is 2**27
```
Uncaught TypeError: The encoded data was not valid for encoding utf-16le
    at TextDecoder.decode (node:internal/encoding:448:14) {
  code: 'ERR_ENCODING_INVALID_ENCODED_DATA'
}
```

### Additional information

_No response_
Repository: material-ui
Issue: [Joy][Select] Cannot retrieve value from Select component using Typescript
Labels: docs,package: joy-ui,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. Created Select Component using Mui Joy
2. Added onChange event to retrieve current value
3. event.target.value is not available so retrieving value is not possible
![image](https://user-images.githubusercontent.com/16710568/233426088-96defdde-8e8f-4071-86e2-334e991e2f6e.png)



### Current behavior 😯

onChange event specifies on using these types of event: React.MouseEvent<Element, MouseEvent> | React.KeyboardEvent<Element> | React.FocusEvent<Element, Element> | null, value: {} | null. But none of those provide an option to get value from Select component

### Expected behavior 🤔

It should be possible to retrieve value from Select Component

### Context 🔦

I am trying to implement the Select component from MUI JOY using typescript and i added the onChange event capturer so i can get the value selected from the user but it is not possible

### Your environment 🌎

  System:
    OS: Linux 5.10 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
  Binaries:
    Node: 18.14.1 - ~/.nvm/versions/node/v18.14.1/bin/node
    Yarn: Not Found
    npm: 9.3.1 - ~/.nvm/versions/node/v18.14.1/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5 
    @emotion/styled: ^11.10.5 => 11.10.5 
    @mui/base:  5.0.0-alpha.117 
    @mui/core-downloads-tracker:  5.11.8 
    @mui/icons-material: ^5.11.0 => 5.11.0 
    @mui/joy: ^5.0.0-alpha.66 => 5.0.0-alpha.66 
    @mui/material:  5.11.8 
    @mui/private-theming:  5.11.7 
    @mui/styled-engine:  5.11.8 
    @mui/system:  5.11.8 
    @mui/types:  7.2.3 
    @mui/utils:  5.11.7 
    @types/react: ^18.0.27 => 18.0.27 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^4.9.5 => 4.9.5 

Used Microsoft Edge
Repository: next.js
Issue: When `middleware.ts` is specified, runtime is set to `edge` instead of `node`
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 19.8.1
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.16
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://github.com/ecumene/next-reproduce-edge-middleware

### To Reproduce

1. Setup a next app and `yarn build`
2. Notice the `.next` project is built for a node runtime (Compatible with SST in my case)
3. Create a `middleware.ts` file
4. Notice the `.next` project is built for an edge runtime (Incompatible with SST)

### Describe the Bug

An `edge-runtime-webpack.js` file is present in `.next` when it shouldn't be there.

### Expected Behavior

The project should be built for a node runtime.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

SST
Repository: godot
Issue: RigidBody2D doesnt get updated properly with MultiplayerSynchronizer
Labels: bug,documentation,topic:physics,topic:network,topic:2d,topic:multiplayer

### Godot version

4.0.2

### System information

Linux Mint 21.1, Vulkan, GTX 1660Ti

### Issue description

On the clientside the RigidBody2D constantly jumps back to the original position if you try to synchronize its velocities, position and rotation with a MultiplayerSynchronizer. There is no issue like that with RigidBody3D.

### Steps to reproduce

Set up a multiplayer scene as described in the blog post: https://godotengine.org/article/multiplayer-in-godot-4-0-scene-replication/ 
Then instead of the 3D scene recreate it in 2D and without players like that:
Add a RigidBody2D with collision on top of a StaticBody2D and make it bouncy(to have some movement). Then add a MultiplayerSynchronizer and synchronize linear_velocity, angular_velocity, position and rotation with it.
If you now host an join you can see the issue on the client window.

### Minimal reproduction project

[scene_replication.zip](https://github.com/godotengine/godot/files/11288435/scene_replication.zip)
Repository: pytorch
Issue: Torch hangs at import if tensorflow is imported first
Labels: module: binaries,triaged

### 🐛 Describe the bug

If I import tensorflow==2.12.0, and then try importing torch==2..0.0 , it hangs

Code to reproduce the error:
```
docker run --rm -it ubuntu:22.04
// once inside
apt-get update && apt-get install python3
apt-get install pip
pip install tensorflow==2.12.0 
pip install torch --extra-index-url https://download.pytorch.org/whl/cu118 
python3
import tensorflow
import torch
```
Note: the issue will persist even if you install torch-cpu, also on any Ubuntu:20.04 and above

### Versions

it says 404 not found, however, the version of torch is 2.0.0, same thing happens if it is torch-cpu

cc @seemethere @malfet @osalpekar @atalman
Repository: vscode
Issue: Git - git should use actual `--autostash` flag for pull
Labels: feature-request,git

<!-- ⚠️⚠️ 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.77.3
- OS Version: Windows

I have a project and I encountered a problem where syncing changes with git extension triggers the stashing of untracked files (even if I don't have anything to sync). This leads to the sudden disappearance and reappearance of a large number of files, causing a lot of notifications and potential performance issues. Also specifically in this project I also encountered an error which doesn't appear if I use `git pull --autostash`:

![image](https://user-images.githubusercontent.com/46503702/233423092-f94d28e4-2438-4d82-b583-bf00b7a6ec1e.png)

ref https://github.com/microsoft/vscode/issues/136650
Repository: next.js
Issue: next/image seemingly causing race condition with redux
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 19.9.0
      npm: 9.6.3
      Yarn: 1.22.19
      pnpm: 8.3.1
    Relevant packages:
      next: 13.3.1-canary.16
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

privaterepo.com

### To Reproduce

using <Image> in a component

### Describe the Bug

It seems that a race condition is being cause when using `<Image>`, we have an image on our login page, everything works fine when just using `<img>` but when using next/image we start seeing a bunch of errors. When we replace `<Image>` with `<img>` everything is fine again. 

![image](https://user-images.githubusercontent.com/3620183/233434440-b6546b49-fab4-4ad0-95dc-83eb6090fa52.png)


### Expected Behavior

Expected behavior is that this does not happen

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

this happens locally
Repository: pytorch
Issue: Ban GradScaler scale from being less than 1
Labels: triaged,module: amp (automated mixed precision)

### 🚀 The feature, motivation and pitch

We should standardize on a way to tell users when a reasonable/good scale for the AMP GradScaler cannot be found.

Context:

The grad scaler is awesome in that it "automatically" finetunes itself to settle on an ideal scale. However! There are instances where there is just no ideal scale for certain parameters, for example the one mentioned in issue #96755, where the scale becomes so so tiny that it causes infs and, consequently, nans. In this issue, we were nestled in the unlikely (but clearly not impossible) world where for a certain scale S, the scaled gradients were valid, but the unscaled (g/S) were invalid, leading to weird inconsistent behavior.

Generally, we want to be add invariants/guarantees to prevent weird inconsistent behavior and give users faster and clearer signal. Since the purpose of the scale is to scale UP the loss so that the grads do not underflow in fp16, we should set a hard boundary of scale must be greater than or equal to 1. Note that adding a check may induce a slight perf hit.

cc @mcarilli @ptrblck @leslie-fang-intel @jgong5 @ngimel @crcrpar @stas00 @albanD

### Alternatives

Do nothing, let users deal with nans from the perspective of BC + that there might be currently unimagined worlds where users want to handle nans themselves (?)

### Additional context

More context provided in https://github.com/pytorch/pytorch/issues/96755.