sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: [Youtube] Got server error HTTP Error 403: Forbidden(latest master version)
Labels: broken-IE

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist
- [x] I'm reporting a broken site support issue
- [x] I've verified that I'm running youtube-dl version **2024.08.07(the latest master version)**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
- [x] I've searched the bugtracker for similar bug reports including closed ones
- [x] I've read bugs section in FAQ


## Verbose log
```
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2024.08.07.local
[debug] Python 3.8.5 (CPython x86_64 64bit) - macOS-10.16-x86_64-i386-64bit - OpenSSL 1.1.1h  22 Sep 2020
[debug] exe versions: ffmpeg 7.0.1-tessus, ffprobe 6.1.1, rtmpdump 2.4
[debug] Proxy map: {'http': 'http://127.0.0.1:58309', 'https': 'http://127.0.0.1:58309'}
Usage: youtube-dl [OPTIONS] URL [URL...]

youtube-dl: error: You must provide at least one URL.
Type youtube-dl --help to see a list of all options.

```

```
PASTE VERBOSE LOG HERE
```


## Description
- The download will run normally for a short time, and then a 403 error will appear

```shell
youtube-dl 'https://www.youtube.com/watch?v=lLSkbZ3-EOs'
```

```
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 2 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 3 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 4 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 5 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 6 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 7 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 8 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 9 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 41 (attempt 10 of 10)...
[download] Skipping fragment 41...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 42 (attempt 1 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 42 (attempt 2 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 42 (attempt 3 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 42 (attempt 4 of 10)...
```
Repository: TypeScript
Issue: Suggestion: use numeric literals for `BYTES_PER_ELEMENT`
Labels: Suggestion,Help Wanted,Domain: lib.d.ts,Experience Enhancement



### ⚙ Compilation target

ES5+

### ⚙ Library

lib.es5.d.ts, lib.es2022.bigint.d.ts

### Missing / Incorrect Definition

Suggesting to change the `BYTES_PER_ELEMENT` static and instance properties as follows:

```diff
interface Uint8Array {
    // ...
-   readonly BYTES_PER_ELEMENT: number;
+   readonly BYTES_PER_ELEMENT: 1;
    // ...
}
```
  
```diff
interface BigInt64ArrayConstructor {
    // ...
-   readonly BYTES_PER_ELEMENT: number;
+   readonly BYTES_PER_ELEMENT: 8;
    // ...
}
```

Etc.

### Sample Code

```ts
declare function fn(bytesPerElement: 1 | 2 | 4 | 8): void
// currently reports "Argument of type 'number' is not assignable to parameter of type '1 | 2 | 4 | 8'".
fn(Uint32Array.BYTES_PER_ELEMENT)
```


### Documentation Link

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray/BYTES_PER_ELEMENT#examples
Repository: stable-diffusion-webui
Issue: [Bug]: Connection refused behind proxy
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

I try to run the webui behind a reverse proxy. The website loads, but the websocket connection still points to `ws://127.0.0.1:7860`.  Thus I get error messages.

### Steps to reproduce the problem

I use the following command:
```bash
$ ./webui.sh --server-name foo
```

### What should have happened?

I expect that by passing the `--server-name` argument, that the websocket connection should use this too.

### What browsers do you use to access the UI ?

Mozilla Firefox

### Sysinfo

no need for a sysinfo.

### Console logs

```Shell
no logs needed.
```


### Additional information

A current workaround is to use an additional parameter `--no-gradio-queue` to disable the websocket connections.
Repository: flutter
Issue: [proposal] [test] test app generated from "old stable" running on "new stable"
Labels: c: proposal,team-release

### Use case

It is inevitable that changes to the framework will break builds created with a different release,  
When this behavior is observed in `beta` the fixes are pushed in `main`
which is totally fine since a choosing a non `stable` version obviously imply less "stability".
eg: [issue](https://github.com/flutter/flutter/issues/145410) identified in `beta`, [fix](https://github.com/flutter/engine/pull/53718) pushed to `main`, all good

I believe a developer upgrading the `stable` release should be warned not only about "breaking changes",
but also if an app created with the `previous stable` will break using the `new stable`.

At the moment this doesn't happen
eg: apparently the same issue above made it to [stable](https://github.com/flutter/flutter/issues/152844) and the fix is currently [cherrypicked](https://github.com/flutter/flutter/issues/152953)

### Proposal

I propose to add an automated integration test for all platforms with stable support
that:
1. build the starter app  with the previous stable
2. upgrade the flutter version
3. run the app 

if the issue is not fixable without developer's action
[detect a mismatch](https://github.com/flutter/flutter/issues/130034) "build version" and "run version" 
and trigger a warning for the known issue providing a workaround/fix
Repository: rust
Issue: E0210: clarify "at least one type"
Labels: T-compiler,A-coherence

### Code

```Rust
pub trait StreamParser {
    fn new(stream: Box<dyn BufRead>) -> Self;
    fn next_triple(&mut self) -> Result<Option<Arc<Triple>>, SourceError>;
}

pub struct NTriplesParser();

impl StreamParser for NTriplesParser { .. }; // left out for conciseness

pub struct StreamParserIter<P: StreamParser>(P);

impl<P> Iterator for StreamParserIter<P>
where
    P: StreamParser,
{
    type Item = Arc<Triple>;

    fn next(&mut self) -> Option<Self::Item> {
        // FIXME handle errors somehow
        self.0.next_triple().ok()?
    }
}

impl<P> IntoIterator for P
where
    P: StreamParser,
{
    type Item = Arc<Triple>;
    type IntoIter = StreamParserIter<P>;

    fn into_iter(self) -> Self::IntoIter {
        StreamParserIter(self)
    }
}
```


### Current output

```Shell
error[E0210]: type parameter `P` must be used as the type parameter for some local type (e.g., `MyStruct<P>`)
  --> core/src/sources/graphs/parsers.rs:32:6
   |
32 | impl<P> IntoIterator for P
   |      ^ type parameter `P` must be used as the type parameter for some local type
   |
   = note: implementing a foreign trait is only possible if at least one of the types for which it is implemented is local
   = note: only traits defined in the current crate can be implemented for a type parameter
```


### Desired output

```Shell
note: implementing a foreign trait is only possible if all of the types for which it is implemented are local
```


### Rationale and extra context

In the above example, clearly one type that satisfies `P: StreamParser` is local. The real essence here is that some other crate might have at least one type that implements `StreamParser`. So, in fact, all types hit by the generic trait bound must be local.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.80.0 (051478957 2024-07-21)
binary: rustc
commit-hash: 051478957371ee0084a7c0913941d2a8c4757bb9
commit-date: 2024-07-21
host: x86_64-unknown-linux-gnu
release: 1.80.0
LLVM version: 18.1.7
```


### Anything else?

_No response_
Repository: godot
Issue: Texture2Drd nested in ShaderMaterial keeps completely white once an empty RID was assigned to it
Labels: bug,topic:rendering,needs testing

### Tested versions

Godot v4.2.2

### System information

Godot v4.2.2.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; 31.0.15.3161) - AMD Ryzen 9 7900X 12-Core Processor (24 Threads)

### Issue description

For a Texture2Drd used as a shader uniform parameter (already settled in editor and saved in scene), the Texture2Drd keeps completed white once assigned an empty RID even if a valid RID is re-assigned to the Texture2Drd. 

And once the Texture2Drd turns to white, it never recovers to correct state even the scene is reloaded (not demonstrated in MRP). So it seems to be a Resource serialization bug? 

Replace the uniform parameter with a new Texture2Drd created by code can resolve it. 

### Steps to reproduce

1. Create a ShaderMaterial with a sampler2d uniform parameter. 
2. Bind a Texture2Drd to the uniform parameter in editor inspector. 
3. At runtime, assign an empty RID to this Texture2Drd.
4. Then whatever you re-assign to the Texture2Drd, this Texture2Drd keeps completely white even the full scene is reloaded. 

### Minimal reproduction project (MRP)

[test_texture2drd.zip](https://github.com/user-attachments/files/16539534/test_texture2drd.zip)

In the MRP, the upper two ColorRects should be in red, and lower two should be blue.
However, the red ones assigned an empty RID before the red texture is assigned, and they keep completed white in the rest time. 

![image](https://github.com/user-attachments/assets/4d65fcc6-c936-4361-b94f-1cd59aeecb4d)
Repository: deno
Issue: tracking: complete runtime documentation
Labels: docs

A lot of runtime APIs are missing [documentation](https://docs.deno.com/api). This can mostly be addressed by checking them with [`deno doc --lint`](https://docs.deno.com/runtime/manual/tools/documentation_generator/#linting) on the corresponding TypeScript declaration files:
- [ ] `ext/broadcast_channel/lib.deno_broadcast_channel.d.ts`
- [ ] `cli/tsc/dts/lib.deno_webgpu.d.ts`
- [ ] `cli/tsc/dts/lib.deno.unstable.d.ts`
- [ ] `ext/cache/lib.deno_cache.d.ts`
- [ ] `ext/console/lib.deno_console.d.ts`
- [ ] `ext/url/lib.deno_url.d.ts`
- [ ] `ext/web/lib.deno_web.d.ts`
- [ ] `ext/fetch/lib.deno_fetch.d.ts`
- [ ] `ext/websocket/lib.deno_websocket.d.ts`
- [ ] `ext/webstorage/lib.deno_webstorage.d.ts`
- [ ] `ext/canvas/lib.deno_canvas.d.ts`
- [ ] `ext/crypto/lib.deno_crypto.d.ts`
- [ ] `ext/net/lib.deno_net.d.ts`
- [ ] `cli/tsc/dts/lib.deno.ns.d.ts` (#24942)
- [ ] `cli/tsc/dts/lib.deno.shared_globals.d.ts`
- [ ] `cli/tsc/dts/lib.deno.window.d.ts`

A follow-up tracking issue could be created once this work is done to make documentation more extensive using the [JSDoc checker](https://github.com/denoland/deno/blob/main/tools/jsdoc_checker.js). E.g. assert that all class methods have at least one `@example` JSDoc tag. A similar approach was used to make the Standard Library's documentation great.
Repository: next.js
Issue: `robots.txt` generation from `robots.ts` fails with `output: "export"` config in Next 15 RC & Canary.108
Labels: bug,Metadata

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/robots-txt-bug-xx45yn

### To Reproduce

1. Build a static export with `next build`

### Current vs. Expected behavior

After building the site, I should see an equivalent `robots.txt` generated from my `robots.ts` file but the build failed with the  following error instead:
```sh
yarn build
yarn run v1.22.19
$ next build
  ▲ Next.js 15.0.0-canary.108

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types    
   Collecting page data  ..Error: export const dynamic = "force-static"/export const revalidate not configured on route "/robo
ts.txt" with "output: export". See more info here: https://nextjs.org/docs/advanced-features/static-html-export                   at new eP (/project/workspace/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:14:28341)
    at 4208 (/project/workspace/.next/server/app/robots.txt/route.js:1:954)
    at t (/project/workspace/.next/server/webpack-runtime.js:1:127)
    at r (/project/workspace/.next/server/app/robots.txt/route.js:16:652)
    at /project/workspace/.next/server/app/robots.txt/route.js:16:682
    at t.X (/project/workspace/.next/server/webpack-runtime.js:1:1191)
    at /project/workspace/.next/server/app/robots.txt/route.js:16:665
    at Object.<anonymous> (/project/workspace/.next/server/app/robots.txt/route.js:16:709)
    at Module._compile (node:internal/modules/cjs/loader:1369:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1427:10)

> Build error occurred
Error: Failed to collect page data for /robots.txt
    at /project/workspace/node_modules/next/dist/build/utils.js:1246:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  type: 'Error'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```

The error suggests to perhaps add `export const dynamic = "force-static"`  which doesn't fix the issue.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 8198
  Available CPU cores: 4
Binaries:
  Node: 20.12.0
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 15.0.0-canary.108 // Latest available version is detected (15.0.0-canary.108).
  eslint-config-next: 15.0.0-rc.0
  react: 19.0.0-rc-e948a5ac-20240807
  react-dom: 19.0.0-rc-e948a5ac-20240807
  typescript: 5.5.4
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

Metadata

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

I tested the reproduction against the `15.0.0-rc.0` and the latest installable canary version `15.0.0-canary.108`.
Repository: electron
Issue: [Bug]: WebContentsView does not apply bounds until visible
Labels: platform/windows,bug :beetle:,status/confirmed,has-repro-gist,component/WebContentsView,31-x-y,32-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

31.1.0

### What operating system(s) are you using?

Windows

### Operating System Version

10.0.19042

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

When creating a WebContentsView and setting the bounds, the html (dom) should reflect those bounds.

### Actual Behavior

Creating a WebContentsView and setting bounds will have no effect until it is shown.
This prevents preloading content that relies on the bounds

### Testcase Gist URL

https://gist.github.com/t57ser/b4711fff7527d72573af1f89989e9853

### Additional Information

In the devtools you can see the bounds of the body, it will apply the correct bounds once the WebContentsView becomes visible
Repository: deno
Issue: Implement crypto.hash
Labels: node compat,crypto

Stability 1 in Node

https://nodejs.org/api/crypto.html#cryptodiffiehellmanoptions
Repository: ant-design
Issue: tour修改挂载节点时不包含mask部分
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://react-6eqsg2-lemna7.stackblitz.io/](Stackblitz)

### Steps to reproduce

设置tour的挂载节点为shadow-dom

### What is expected?

mask部分内容包含在shadow-dom中

### What is actually happening?

控制台查看mask部分内容未包含在shadow-dom中

@afc163 @crazyair @li-jia-nan 


| Environment | Info |
| --- | --- |
| antd | 5.20.0 |
| React | react |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Add ability to snap windows to the predefined grid using keyboard and numpad shortcuts in FancyZones
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

The proposed feature would enable users to snap windows to predefined grid zones in FancyZones using keyboard shortcuts, including the numpad keys. This would function similarly to the now-defunct WinSplit Revolution app (last updated in 2013), which allowed for quick and efficient window management using keyboard shortcuts. Implementing this would enhance productivity by reducing the need for mouse interaction and allowing power users to quickly arrange windows using only the keyboard.

### Scenario when this would be used?

This feature would be particularly useful for power users who rely heavily on multitasking and need to quickly arrange multiple windows across their screens. It would also benefit users who prefer keyboard shortcuts over mouse actions for window management, providing a faster and more streamlined workflow. This is especially important in environments where efficiency and quick access to multiple applications are crucial, such as software development, data analysis, and creative workspaces.

### Supporting information

Implementing this feature would align FancyZones with the capabilities previously offered by the Windows Split app, which, although now defunct, was appreciated for its efficient window management through keyboard shortcuts. The addition of this feature would not only bring back functionality that some users miss but also enhance the overall utility of FancyZones for a broader user base. Including keyboard and numpad shortcuts for snapping windows to grid zones would modernize FancyZones and improve its appeal to both existing and potential new users.
Repository: deno
Issue: Provide an easier way to configure type checking for other runtimes
Labels: feat

Currently it's difficult to configure Deno type checking to make it work with browsers.

If you like to write code which works with browsers instead of Deno, you need to configure `deno.json` into something like the below:
```json
{
  "compilerOptions": {
    "lib": ["esnext", "dom", "dom.iterable"]
  }
}
```

This requires a lot of knowledge about `tsconfig.json`, and this situation seems against our zero-config/easier TypeScript principle.

I'd suggest we should have `runtime` field in `deno.json`, which accepts a list of `"deno" | "browser"` (for now), and that fields configures the type checking automatically for each given runtime.

```jsonc
{ "runtime": ["browser"] } //=> `compilerOptions.lib` becomes `["esnext", "dom", "dom.iterable"]`
```

For SSR situation:

```jsonc
{ "runtime": ["deno", "browser"] } //=> `compilerOptions.lib` becomes `["deno.ns", "esnext", "dom", "dom.iterable"]`
```
Repository: neovim
Issue: Go to tag after file name
Labels: enhancement,jumps-navigation

### Problem

nvim can go to file by `gf` comamnd, it should support the following grammar:

```
/path/to/file:100 : go to line.
/path/to/file#tag : go to tag
```

### Expected behavior

nvim can go to line or go to tag.
Repository: ollama
Issue: Update LLaVA to LLaVA OneVision
Labels: model request

LLaVA has a new version called OneVision which was released 2024/08/06

[HuggingFace](https://huggingface.co/collections/lmms-lab/llava-onevision-66a259c3526e15166d6bba37)
[GitHub](https://github.com/LLaVA-VL/LLaVA-NeXT/)
[Release Notes](https://llava-vl.github.io/blog/2024-08-05-llava-onevision/)

### key features:
- Supports various input resolutions up to 2304 * 2304 pixels.
- Single image input is represented by 729 * (9+1) tokens at most under anyres_max_9 mode.
- Supports multi-image and video inputs. Multi-image input is represented by 729 token for each image, and video input is represented by 196 token for each frame.
- Available in three sizes: 0.5B, 7B and 72B parameter versions, fit for different memory and inference latency requirements.
- better support for Set-of-mark prompting
- and more...
Repository: pytorch
Issue: Different random seeds can cause differences in arithmetic precision
Labels: module: numerical-stability,triaged

### 🐛 Describe the bug

Code Block1
```python
torch.manual_seed(1337)  #torch.manual_seed(42)
B,T,C = 4,8,2 # batch, time, channels
x = torch.randn(B,T,C)
#version1
xbow = torch.zeros((B,T,C))
for b in range(B):
    for t in range(T):
        xprev = x[b,:t+1] # (t,C)
        xbow[b,t] = torch.mean(xprev, 0)
```
Code Block 2
``` python
# version 2
wei = torch.tril(torch.ones(T, T)) 
wei = wei / wei.sum(1, keepdim=True)        
xbow2 = wei @ x # (B, T, T) @ (B, T, C) ----> (B,T,C)  
torch.allclose(xbow, xbow2)
``` 
The random seed 1337 and the random seed 42 cause a difference in the results of the above operations, and ultimately the output of the allclose function is completely different
![image](https://github.com/user-attachments/assets/5bbbe8de-a158-4df2-8a38-a43b6950e4b3)
![image](https://github.com/user-attachments/assets/d23f9ca5-3a42-49e5-b4d8-384b5bab4a97)
As shown in the figure

### Versions

the two code blocks run in the colab not in the colab pro