sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: No TS2554 in JavaScript files even though the argument is definitely required.
Labels: Suggestion,Needs Proposal

# Bug Report

### 🔎 Search Terms

javascript TS2554 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `required`

### ⏯ Playground Link

- [JavaScript](https://www.typescriptlang.org/play?strictNullChecks=true&noUncheckedIndexedAccess=true&noUnusedLocals=true&noUnusedParameters=true&noFallthroughCasesInSwitch=true&useUnknownInCatchVariables=true&exactOptionalPropertyTypes=true&noImplicitOverride=true&noPropertyAccessFromIndexSignature=true&ts=4.8.0-beta&filetype=js#code/GYVwdgxgLglg9mABAJwKYEcQzQEwILIDmIAtqmFABQDeAUIg4sHHIgLyJTIioA0tAXwCUiOo0QQEAZzgAbVADpZcQpWZwhAbkG1aaTNlT4ipclS20gA)
- [TypeScript](https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABAJwKYEcQzQEwILIDmIAtqmFABQDeAUIg4sHHIgLyJTIioA0tAXwCUiOo0QQEAZzgAbVADpZcQpWZwhAbkG1aaTNlT4ipclS1A)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
function requiredArgument({
    foo = true,
}) {
    console.log(foo);
}

requiredArgument();
```

### 🙁 Actual behavior

No type error when calling `requiredArgument()`

### 🙂 Expected behavior

A type error saying `Expected 1 arguments, but got 0. TS2554`, since this is also the current behaviour in TypeScript files.
And when running the JavaScript code, you get a runtime error:
```
Uncaught TypeError: Cannot read properties of undefined (reading 'foo')
```

Related: #49869
Repository: godot
Issue: Android FileDialog unable to see .pck files
Labels: bug,platform:android,topic:gui

### Godot version

3.5.0

### System information

Android 12

### Issue description

FileDialogs are unable to see .pck files when running on Android. I am able to see other standard file types such as .png files, but the FileDialog will completely ignore .pck files.

Note: This works for Windows/Mac/Linux, no issue.

### Steps to reproduce

1. Create a Godot project that opens a FileDialog in the user's download directory
2. Put a .pck file in your download directory
3. It should not be visible in the FileDialog

### Minimal reproduction project

[Test.zip](https://github.com/godotengine/godot/files/9355898/Test.zip)
Repository: godot
Issue: [3.5] Initial AcceptDialog & ConfirmationDialog popup sizes are huge if FlowContainers are present as children.
Labels: bug,topic:gui

### Godot version

3.5.stable

### System information

Windows 10, GLES3, GTX 1070

### Issue description

Specifically in the case of the AcceptDialog and ConfirmationDialog, if either of them have FlowContainers as children, their first instance of popping up via the popup() methods will occur with `rect_size` skewed to an **extremely** large value. HFlowContainers cause the height to skew, whereas VFlowContainers affect the width. If both FlowContainers are children, the effect stacks. See example below (where the red rectangle represents the Rect2 passed to the popup() method):

https://user-images.githubusercontent.com/60264149/185023629-7863d07a-aa98-43ec-9daa-2577189234dd.mp4

There are a few specifics surrounding this bug:
1. For one, it will occur regardless of whether the FlowContainer is a direct or indirect child of the dialog, so long as its part of the dialogs sorting chain. To clarify, if the FlowContainer were to be the child of another container class (i.e. HBoxContainer), the bug would occur. But if it was the child of a base Control node which does no sorting to its children, the bug would not occur. 

2. The second specific is that the FlowContainer must have at least one child Control node. This leads me to believe there's some kind of clash happening between the dialogs sorting and the FlowContainers sorting.

3. The last specific is that the bug **only** occurs on the **first** popup() call. All subsequent ones behave normally with the dialog being of the specified size. You can see this happening in the example .gif. I tried adding and removing child nodes inbetween popups but neither action caused the issue to repeat.

So to summarize the above:
![ValidSetups](https://user-images.githubusercontent.com/60264149/185020856-6daa9fb2-be2f-4c8b-acda-8de1e5fd698e.png)

I tried replicating this behavior in all the other Popup derived nodes and none of them exhibited it. You'd expect the PopupPanel to since it sorts direct children in a similar manner to the Accept and Confirmation dialogs, but it does not. Also just to be clear, when I talk of the AcceptDialog & ConfirmationDialogs sorting, I'm referring to the way they automatically bound child Control nodes to their margins when resizing.

### Steps to reproduce

- Create an AcceptDialog or ConfirmationDialog.
- Add an HFlowContainer or VFlowContainer to the dialog.
- Add a Control node to the flow container.
- Attach a script to the dialog and declare a _ready() function with popup_centered() as the first & only line.
- Run the project and observe the dialog being stretched way beyond the edge of the screen bounds.

### Minimal reproduction project

[FlowContainerInDialogBug.zip](https://github.com/godotengine/godot/files/9355902/FlowContainerInDialogBug.zip)
Repository: three.js
Issue: GLTFLoader: HTTP Range Requests support
Labels: Suggestion

<!-- Ignoring this template may result in your feature request getting deleted -->

**Is your feature request related to a problem? Please describe.**

`GLTFLoader` first loads the entire bundle glb file and then starts the parse. It is inefficient for network usage if users want to first partially load the assets and then lazily load the others on demand (eg. glTF LOD extension).

**Describe the solution you'd like**

[Support HTTP Range Requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests) in `GLTFLoader`.

Changes probably needed:
* `FileLoader` supports HTTP Range Requests #24485
* First load only the glb header
* Load partial buffer for a buffer view with HTTP Range Requests

**Additional context**

With the changes, the number of requests can be many. How will the response time be? Longer because of many requests? Or shorter because of the parallelism?
Repository: puppeteer
Issue: [Feature]: Support DOMDebugger.getEventListeners on ElementHandle
Labels: feature,confirmed

### Bug description

### Steps to reproduce the problem:

1. await page.goto('https://www.baidu.com');
2. const elementHandle = await page.$('#hotsearch-refresh-btn');
3. response = await client.send('DOMDebugger.getEventListeners', { objectId: elementHandle.remoteObject().objectId });

### Complete Code to reproduce the problem
```
const puppeteer = require('puppeteer');

(async () => {

    const browser = await puppeteer.launch();
    const page = await browser.newPage();
    const client = await page.target().createCDPSession();

    await page.goto('https://www.baidu.com');
    const elementHandle = await page.$('#hotsearch-refresh-btn');

    console.log(elementHandle.remoteObject().objectId); // objectId has valaue

    response = await client.send('DOMDebugger.getEventListeners', { objectId: elementHandle.remoteObject().objectId });
    console.log(response);


    await browser.close();
})();
```

### Expect:
in step 3, response the returned normally

### Actually：
there was a error.
```
3008355417396813112.3.2
/Users/chenjili/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:286
                error: new Errors_js_1.ProtocolError(),
                       ^

ProtocolError: Protocol error (DOMDebugger.getEventListeners): Could not find object with given id
    at /Users/chenjili/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:286:24
    at new Promise (<anonymous>)
    at CDPSession.send (/Users/chenjili/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:282:16)
    at /Users/chenjili/practise/python/test.js:19:29
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  originalMessage: 'Could not find object with given id'
}

Node.js v18.7.0
```




### Puppeteer version

puppeteer@16.1.0

### Node.js version

v18.7.0

### npm version

8.15.0

### What operating system are you seeing the problem on?

macOS

### Relevant log output

```shell
3008355417396813112.3.2
/Users/chenjili/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:286
                error: new Errors_js_1.ProtocolError(),
                       ^

ProtocolError: Protocol error (DOMDebugger.getEventListeners): Could not find object with given id
    at /Users/chenjili/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:286:24
    at new Promise (<anonymous>)
    at CDPSession.send (/Users/chenjili/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:282:16)
    at /Users/chenjili/practise/python/test.js:19:29
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  originalMessage: 'Could not find object with given id'
}

Node.js v18.7.0
```
Repository: TypeScript
Issue: async code generator does not correctly handle labelled blocks
Labels: Bug,Help Wanted

# Bug Report

When using the "ES5" target, `async`/`await` code generation does not correctly handle breaking from labelled blocks.

### 🔎 Search Terms

break block label async

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about everything

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?target=1&ts=4.8.0-beta&filetype=ts#code/CYUwxgNghgTiAEYD2A7AzgF3gBRkgtgJZogBc8UKAngNwBQdUaVKY8AZgK6saGodIkACgCU8AN5140+BnwAHcpJkqBMeEIggsAD3gBeeAAYa8PQB54AFlM6A1HZFTVLwuw1QA7lEJZcBYhAAOjg0JAgANxAhDBhOEBEnF2SZACM4KABrWQV6FOR0cOCIJABzIQAiAEkFJDQ0QlStCpE85IwACzxPYzbpAF9naQKwrSCS8oqAZU4wMBB6lvpBunZBURogA)

### 💻 Code

Compiler options: `--lib ES2015,dom --target ES5`

```ts
async function foo() {
    tmp: {
        for (let x = 0; x < 4; x++)
            if (await Promise.resolve(true))
                break tmp;
        console.log("Impossible");
        throw 0;
    }
    console.log("Success");
}

foo();
```

### 🙁 Actual behavior

"Impossible" is logged, because the `break` statement seems to short-circuit the inner loop

### 🙂 Expected behavior

"Success" is logged, because the `break` statement should short-circuit the outer block

Interestingly, it does seem to handle breaking from outer loops (eg adding a superfluous loop, `tmp: for (let nvm = 0; nvm < 1; nvm++) ...`), but not plain blocks.
Repository: youtube-dl
Issue: pornhub gif (actually short webm video) download from (https://www.pornhub.com/gif/)
Labels: broken-IE

<!--

######################################################################
  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.12.17. 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 site 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 site feature request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've searched the bugtracker for similar site feature requests including closed ones


## Description

<!--
Provide an explanation of your site feature request 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.
-->

youtube-dl treat the `/gif/***` path URL as playlist and tries to download the "playlist" but nothing is downloaded.
Repository: flutter
Issue: [in_app_purchase] Restore Purchase IOS , applicationUsername return null
Labels: platform-ios,d: api docs,p: in_app_purchase,package,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-ios,triaged-ios

Hi
i am having a problem when restoring payments from ios, **applicationUsername** returns null,while restoring from android is working fine
![Screen Shot 2022-08-17 at 14 27 59](https://user-images.githubusercontent.com/89825540/185060261-d3d99089-3790-4f24-8802-f865cb894f40.png)
Repository: godot
Issue: [Godot 3.5 issue - Solved] Android: Exported aab on Google play show splash screen then crash
Labels: platform:android,needs testing,topic:export

### Godot version

3.5.0.stable.mono

### System information

Windows 11,GLES2,GeForce 310M

### Issue description

-Project works perfectly on many android devices and different versions( as apk - release- custom build)
*After uploading project to google play store(as aab - release - custom build), users see splash screen then project crash
*Android vital(in google play console) tells information about exception coming from libgodot_android.so
-The project unpublished from google play, we try to build using godot 3.4.5 and check again
-The issue will update soon
*We report this issue as bug becuase we found some of developers face same problem

### Steps to reproduce

Can't reproduce issue, we think it's comming from exporting templates

### Minimal reproduction project

_No response_
Repository: angular
Issue: Make possible to disable Disabling the AbstractControl  to make forms easier to use in common scenarios
Labels: area: forms,P3,forms: strictly typed

### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

Motivation:
- currently, type of Value in FormGroup - nomatter what - is Partial<T>
- in half of the scenarios, developer is never ever disabling the controls 

Usecase:
```
formGroup: FormGroup<{ a: FormControl, b: FormControl }> 
method(arg: {a: any, b: any}){}
// Error - a anb b is optional - formGroup.getRawValue() has to be used
this.method(formGroup.value);
```

Workaround:
 - formGroup.getRawValue() has to be used


UseCase2:
```
@Output() valueChanges = this.formGroup.valueChanges;
onValueChanges(arg: {a: any, b: any}){}
// error 
(valueChanges)=onValueChanges($event)
```
Workaround:
`@Output() valueChanges = this.formGroup.valueChanges.pipe(map(()=> this.formGroup.getRawValue()));`



### Proposed solution

Allow developer to specify, AbstractControl cannot be disabled.

new FormGroup({
a: new FormControl(.., { cannotBeDisabled: true })   
b: new FormControl(..)   
})


type:
Partial<{ b: any }> & { a: any }   

### Alternatives considered

- provide  rawValueChanges observable.
Repository: pytorch
Issue: Silent promotion of bool to int in the dispatcher
Labels: triaged,module: type promotion,module: pybind,module: library

### 🐛 Describe the bug

I try to register a function that according to its signature should only accept int or a list of ints, but there's a silent bool promotion to integers:
```py
import torch

test = torch.library.Library("test", "DEF")
test_impl = torch.library.Library("test", "IMPL", "CompositeExplicitAutograd")

schema = "test(int[2] arg) -> Tensor"

test.define(schema)
test_impl.impl("test", lambda arg=None: torch.tensor(arg))

try:
    res = torch.ops.test.test(arg=True)
    print(res)
    print("Unexpected success!")
except RuntimeError as e:
    print(e)

# This doesn't work as expected:
try:
    res = torch.ops.test.test(arg=2.0)
    print(res)
except RuntimeError as e:
    print(e)
```

### Versions

Latest master.

cc: @ezyang, @albanD, @bdhirsh  

cc @nairbv @mruberry @anjali411
Repository: transformers
Issue: Refactor Pytorch `model.generate` method to work on TPU
Labels: WIP

### Feature request

Refactor PT version of the method `model.generate` for text generating models to make it compatible with XLA and speed up inference on TPU.

### Motivation

Right now, `model.generate` on PT is extremely slow on TPU compared to CPU and GPU. This is probably due to the fact that some operations done in the PT version of `model.generate` are not XLA compatible, and thus the generation process falls back on CPU. This makes inference on TPU infeasible. A major refactoring work has already been done on its TF counterpart, so it would be nice to have the PT version working as well.

A more in-depth discussion with @gante took place in #12322 and on this [huggingface discussion](https://huggingface.co/spaces/joaogante/tf_xla_generate_benchmarks/discussions/1).

### Your contribution

If there is some interest from the HF team, I can definitely assist during the work.
Repository: kubernetes
Issue: kube-apiserver: some HTTP requests might hang indefinitely
Labels: kind/bug,priority/backlog,sig/api-machinery,triage/accepted

### What happened?

Since `kube-apiserver` doesn't specify a `WriteTimeout` on the server level it solely relies on the timeout filter to terminate HTTP requests.

The timeout filter wraps the `http.ResponseWriter` into a time-aware construct and passes it to an HTTP handler. Once the specified timeout has elapsed the HTTP handler loses control and an appropriate response is sent back to a client.

The issue arises when a response written via the `http.ResponseWriter.Write` method cannot be sent to the client. In that scenario, the timeout handler won't be able to terminate the connection because it cannot acquire a lock and the HTTP request will hang forever.

The `Write` method does not always send immediately data to the client. Most of the time anything sent via the `Write` method is actually stored in a memory buffer and sent to the client at a later time. It only sends data immediately when the buffer is sufficiently large.

Now, with the introduction of `HTTP2/ping` feature, stale connections are detected and terminated. But what if the connection isn't stale but the client is still slow to download data? Exactly in those cases, the `kube-apiserver` won't be able to terminate hanging HTTP requests.

### What did you expect to happen?

the `kube-apiserver` should always terminate timed-out HTTP requests.

### How can we reproduce it (as minimally and precisely as possible)?

1. update the `OpenAPI` spec so that it exceeds the HTTP buffer.
2. send an HTTP request for that spec but don't actually download it. (not closing the `ResponseBody` does the trick). For example:
```
req, _ := http.NewRequest("GET", `/openapi/v2`, nil)
resp, _ := rt.RoundTrip(req)
// don't close the rsp body, usually you would: resp.Body.Close()
// sleep for 1 hour
```

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```
n/a
</details>


### Cloud provider

<details>
n/a
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: TypeScript
Issue: The static private field should not be accessed from `new.target` and `typeof T`.
Labels: Suggestion,Needs Proposal

# Bug Report

The static private field should not be accessed from `new.target` and `typeof T`.

### 🔎 Search Terms

static private field new target

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- I believe it never worked since private field is introduced.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/MYGwhgzhAEAq0G8CwAoa7oQC5iwS2GgGIAzPAUxABMAuaMAOwE9UNpgB7B7AJwFdgWDjwAUASkSs2GBuQDuAOhw8A5uSwLSFalOnQA9Pr0YAfmfO7ph4mUpVoVDuRgMOWaOQAeebNC7RZRWU1DWgAQRAsAAsOPhUouGgoyGhon2hbagAaaDwsGGAovGp2cChoOWKQALcksAA3clyNSzZWjBB1diLqOiwmAAdyDhJEgF5SyBgvLHIGKhh4BABfdvRObncBjig8ACNOgGEe+wnApTBVdTXu4qpNTKoc7d2D8mO7h+0qG+tTczMxiB0ABZl+Ri0dgcThctS8Pnc-gABv0hiM4EiFOFIjE4gl4MkYGkYI8cnkCidJuVKiBqq53MlGs0FKhLKsUOzAnBxAYjPwGPgALZNcg8HjCACEQA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
class T {
    static #field: any
    constructor() {
        new.target.#field
        //         ~~~~~~
        // #field does not exist on new.target. Although T has this field, its child class will not have it.
        
        let child: typeof T = class extends T {}
        const possibleChild = new.target
        child.#field, possibleChild.#field
        //    ~~~~~~                ~~~~~~
        // #field does not exist on `typeof T`. Although T has this field, its child class will not have it.

    }
}
new T() // runtime error!
```

### 🙁 Actual behavior

No error reported

### 🙂 Expected behavior

Should report error (commented in code)
Repository: create-react-app
Issue: CRA older version that support node 12 and webpack4
Labels: needs triage

Hi all, how can I use CRA that support node 12 and Webpack 4, we need this as our main  project uses this type of CRA, and we can not update it for many reasons, thank you vey much.
Repository: rust
Issue: "Methods from Deref<Target = [T]>" doesn't render const
Labels: T-rustdoc,C-bug,F-const_trait_impl,A-rustdoc-ui

The documentation for [`[T]::is_empty` on `Vec`s documentation page](https://doc.rust-lang.org/nightly/std/vec/struct.Vec.html#method.is_empty-1) don't show that it's a `const fn`, while the documentation for [the same method on `[T]`s documentation page](https://doc.rust-lang.org/nightly/std/primitive.slice.html#method.is_empty) correctly show that it is a `const fn` since 1.39.0.

@rustbot labels: +T-rustdoc +A-rustdoc-ui