sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: App security test reports Insecure API for React Native iOS App - Binary Analysis (IPA)
Labels: Platform: iOS,Needs: Triage :mag:

Please provide all the information requested. Issues that do not follow this format are likely to stall.

## Description
•	Binary make use of malloc Function The binary can use the malloc function instead of calloc.
This is the result of a static analysis of the IPA file of an iOS-based application

## React Native version:
System:
    OS: macOS Mojave 10.14.5
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 273.91 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.8.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.10.2 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28, 29
      Build Tools: 28.0.3, 29.0.2, 29.0.3
      System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.4 AI-183.6156.11.34.5692245
    Xcode: 10.3/10G8 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_221 - /usr/bin/javac
    Python: 2.7.10 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0 
    react-native: 0.62.2 => 0.62.2 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

react-native-cli: 2.0.1
react-native: 0.62.2

## Expected Results
How could you change the variables found by those suggested by apple from react native? 

The issue has been raised by a client and is being considered as a High priority vulnerability.
Repository: TypeScript
Issue: Allow omission of generic type if its equal to the default type
Labels: Suggestion,Awaiting More Feedback

## Search Terms

generic, default, extends, equals, =

## Suggestion

Allow the syntax `extends = T` in generics definition in place of `extends T = T`.

**Currently**
```typescript
class Foo <T extends any = any> {}
```

**Suggestion***
```typescript
class Foo <T extends= any> {}
```

## Use Cases

The problem of having to write `<T extends any = any>` revealed itself when I had a bit more complex type looking like `keyof NetworkTransportProtocol` that looked then somehow like this:

```typescript
class Foo<T extends keyof system.NetworkTransportProtocol = keyof system.NetworkTransportProtocol> {}
```
which just was a lot of duplicated text.

```typescript
class Foo<T extends= keyof system.NetworkTransportProtocol> {}
```

by reducing the duplicate information the whole syntax becomes better to read.

While I did focus on the default-case for class-generics. I believe this could also help with other definitions:

```typescript
function foo <T extends=any>(bar: T) {}
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: pytorch
Issue: [FR] tensor ctors should support directly creating in shared memory
Labels: high priority,feature,triaged,module: tensor creation

## 🚀 Feature


Tensor ctors should support directly creating in shared memory. The current workaround is either the inefficient `.share_memory_()` after creation or private APIs like
https://github.com/pytorch/pytorch/blob/36c87f1243f582ae761ec6d69f5965bd91c32d3c/torch/utils/data/_utils/collate.py#L52-L54
Repository: pytorch
Issue: [FR] torch.load should support loading directly to pinned/shared memory
Labels: high priority,module: multiprocessing,feature,module: serialization,triaged

## 🚀 Feature

The current code can be modified to do so without large changes. Loading to these special memory pages can be very helpful, e.g., when the loaded tensors are to be shared among processes.

cc @mruberry
Repository: godot
Issue: Adding a reflection probe darkens scene
Labels: discussion,topic:rendering,topic:3d

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.2.3.Stable


**OS/device including version:**
Intel(R) Core(TM) i7-5820K, GTX 970, Windows 10 Pro


**Issue description:**
Adding a reflection probe darkens scene. The  area the reflection probe is in gets darkened incorrectly:
![image](https://user-images.githubusercontent.com/4955051/100550576-d53ae780-3272-11eb-9896-be72e70ff008.png)

The issue gets even more pronounced when using a coloured light.
![image](https://user-images.githubusercontent.com/4955051/100550634-395dab80-3273-11eb-86a1-58991f4a9277.png)
![image](https://user-images.githubusercontent.com/4955051/100550706-99545200-3273-11eb-9d88-dbb916318d87.png)


**Steps to reproduce:**
Open the attached project and observe the issue.


**Minimal reproduction project:**
[reflection_too_bright_test.zip](https://github.com/godotengine/godot/files/5612654/reflection_too_bright_test.zip)
Repository: neovim
Issue: Changing redrawstatus so that it doesn't clear the welcoming message
Labels: enhancement,ui,statusline

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: 0.5.0

I am trying to setup a clock that also shows seconds in lightline for my statusbar.
But if I make it so that redrawstatus is called every second so that the time is updated every second 
it causes the welcome message to disappear after one second has passed.
Repository: godot
Issue: Visual Script will generate error if the user sets a scene node in a variable by using VisualScriptSceneNode
Labels: bug,topic:editor,confirmed,topic:visualscript

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
Godot v3.2.4-beta3


**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->

- Windows 10 (64-bit) version (build) 2009 (10.0.19042).
- Intel® UHD Graphics 620 driver version 27.20.100.8935.
- GLES3


**Issue description:**
<!-- What happened, and what was expected. -->
I can't set a scene node in a variable (object data type) by using VisualScriptSceneNode. I have to set it in the __ready_ function with the _get_node()_ instead. Otherwise, the script will generate this error:

![Screenshot 2020-11-29 174128](https://user-images.githubusercontent.com/1403194/100553066-314d3e00-326a-11eb-9ed8-d977a4a6f675.jpg)

I don't know why this could cause an error. I already set the node in the editing variable window, as shown [here](https://photos.app.goo.gl/goxW5Ad14QZv44dq7).

I expect to be able to set the scene node as a default value in a variable of object data type, like when I am able to set a default int, float, Vector3, etc. value in a variable without having to set it in the __ready_ function.


**Steps to reproduce:**

1. Create a variable of the object data type.
2. Set its default value by using the VisualScriptSceneNode.
3. Pick a scene node.
4. Test the variable by setting the material_override. The script will generate an error.


**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[test.zip](https://github.com/godotengine/godot/files/5612857/test.zip)
Repository: create-react-app
Issue: CRA & Django integration
Labels: issue: proposal,needs triage

Hi
It would be great that there is a tutorial about using create-react-app with Django Rest api backend 
[Integrating with an API Backend](https://create-react-app.dev/docs/integrating-with-an-api-backend)
Repository: rust
Issue: Type checker fails to prove associated and normal types are same if has constraint on impl of generic struct
Labels: A-associated-items,C-bug

I tried this code: [playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=bfe131f8a2ac0cf1c27ed52edf58870c)

```rust
use std::marker::PhantomData;

trait Storable: Sized + Copy + Sync + Send + 'static{}

impl <T> Storable for T where T: Sized + Copy + Sync + Send + 'static{}

trait QueryProxyTrait{
    type Associated: Storable;
    fn get_item_pointers()->Self::Associated;
}

// This is struct with associated item
struct RefMutProxy<T: Storable>(PhantomData<T>);

impl<TR0: Storable> QueryProxyTrait for (RefMutProxy<TR0>,) {
    type Associated = i32;
    fn get_item_pointers()->Self::Associated{
        0i32
    }
}

// This is struct which impl fails to compile
struct Q<T: QueryProxyTrait>(PhantomData<T>);

impl<T> Q<(RefMutProxy<T>,)>
where T: Storable,
    // If line below is removed, it compiles
    (RefMutProxy<T>,): QueryProxyTrait
{
    fn get_data(){
        let v: <(RefMutProxy<T>,) as QueryProxyTrait>::Associated =
            <(RefMutProxy<T>,) as QueryProxyTrait>::get_item_pointers();
        // Here it fails to prove that v is i32
        let v: i32 = v;
    }
}
```

I expected to see this happen: Code compiles

Instead, this happened: compiler prints this error:
```
error[E0308]: mismatched types
  --> src/lib.rs:32:22
   |
32 |         let v: i32 = v;
   |                ---   ^ expected `i32`, found associated type
   |                |
   |                expected due to this
   |
   = note:         expected type `i32`
           found associated type `<(RefMutProxy<T>,) as QueryProxyTrait>::Associated`
   = help: consider constraining the associated type `<(RefMutProxy<T>,) as QueryProxyTrait>::Associated` to `i32`
   = note: for more information, visit https://doc.rust-lang.org/book/ch19-03-advanced-traits.html

```

### Meta
<!--
Bug occurs in beta and nightly too.
-->

`rustc --version --verbose`:
```
rustc 1.48.0 (7eac88abb 2020-11-16)
binary: rustc
commit-hash: 7eac88abb2e57e752f3302f02be5f3ce3d7adfb4
commit-date: 2020-11-16
host: x86_64-pc-windows-msvc
release: 1.48.0
LLVM version: 11.0
```

**P.S.**
If anyone faced same trouble, I solved it by removing this line in impl: `(RefMutProxy<T>,): QueryProxyTrait`

I found how to make this code compile (see comments in source) but I think rustc should either accept code above or print better error message.
Repository: opencv
Issue: G-API: revise generated documentation
Labels: bug,category: documentation,category: g-api / gapi

There is link on generated [gapi namespace](https://docs.opencv.org/master/d4/d1c/namespacecv_1_1gapi.html) documentation (content will be updated after fixes).

Issues:
- [x] broken layout after/in `BGR2Gray` entry
- [ ] navigation header doesn't look correct too (grouping issues):
    `G-API framework » G-API Graph Compilation ArgumentsG-API framework » G-API Data Types » | G-API Metadata Descriptors`
- [ ] perhaps we need to ignore in documentation entries with `std::enable_if< std::is_same< T, GCompileArgs >::value, GCompileArgs >::type` (or move it into nested group through [`@ingroup`](https://www.doxygen.nl/manual/grouping.html))
Repository: svelte
Issue: Crossfade transition events does not work as expected
Labels: bug,runtime

**Describe the bug**
Crossfade does not dispatch `outrostart`.

**To Reproduce**
https://svelte.dev/repl/444056d6706e4d16a604742a48e0d17c?version=3.30.0

**Expected behavior**
`introstart` should be dispatched when element is about to appear
`introend` should be dispatched when element is fully visible
`outrostart` should be dispatched when element is about to disappear
`outroend` should be dispatched when element is fully hidden

**Information about your Svelte project:**
- Svelte version 3.30.0
Repository: youtube-dl
Issue: Claro Argentina
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 2020.11.29. 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 **2020.11.29**
- [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 video: https://streaming.claro.com.ar/content/5fc155c3300ae10c3283e9df


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

This is a free live streaming service, and I would like to download the video in the example, if something can be done it would be awesome
Repository: deno
Issue: Analyse Test Results?
Labels: feat,cli,testing

**Description**

This is a question.

Are there plans on added support for being able to 'analyse' tests results? For example:

```typescript
const result = Deno.test("My test", () => {
  assertEquals(true, true)
  assertEquals(false, true)
})
console.log(result)
// {
//   failures: [
//     {
//      line: 3,
//      assertion: "assertEquals",
//      output: {
//        expected: false,
//        actual: true
//      }
//     }
//   ],
//   passes: ...
// }
```

**Use Case**

*Note: of course this is my own use case, but this feature may provide more utility, and i'm not saying just because it would be useful to me, i expect it to be implemented*

I have an idea for adding a GUI for a browser automation and testing tool (similar to Cypress.io), and i've been playing around with the idea of displaying test results for each test. I think the ability to analyse tests results would be sufficient in this scenario. The only current way i can think of doing this, is running the test inside a sub process, getting the stdout/stderr,  and filtering the result so I can end up with the `- "..."\n+ "..."` blocks
Repository: godot
Issue: Vertical collision with one way collision platform when colliding with another body to the side
Labels: bug,confirmed,topic:physics

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
3.2.3

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows 10

**Issue description:**
<!-- What happened, and what was expected. -->
There is a vertical collision as it goes up through a one way collision platform when it also collides with another body on top of the one way platform, leading to the kinematic body stopping completely instead of sliding up. In a platformer, this can lead to jumping through a one way platform, colliding with an NPC, and dropping immediately instead of sliding up the NPC collision box.

![bug](https://user-images.githubusercontent.com/1882199/100562723-84cf8400-328a-11eb-9541-e31c38be168a.gif)

What's expected is that the body stops horizontal movement but continues sliding up, shown when you disable the one way collision platform.

![onewaybodydisabled](https://user-images.githubusercontent.com/1882199/100562845-d2e48780-328a-11eb-88a7-2dc7169e73b9.gif)

**Steps to reproduce:**
Run the project.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[test_move_one_way_body_on_top.zip](https://github.com/godotengine/godot/files/5613499/test_move_one_way_body_on_top.zip)
Repository: rust
Issue: Forbid `#[rustc_const_stable]` without `#[stable]`
Labels: C-enhancement,A-stability,A-const-eval,T-libs

Currently, it is possible for a function in std to be marked stably `const` without the function being stable. In #79548, it was noted that rustdoc assumes that stably const implies stable, and that seems to be a reasonable requirement. There should be an error added to ensure the consistency of const stability.
Repository: youtube-dl
Issue: Yet another parallelism request: call external downloader once with all URLs
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 2020.11.29. 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 **2020.11.29**
- [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.
-->

Using aria2c with multiple connections allows me to actually use all of my bandwidth...except when it doesn't. For example, if I try to download a YouTube video whose audio and video are separate files, youtube-dl will first call aria2c with the video, which will download super fast, and then when that's finished, youtube-dl will call aria2c again with the audio, which will download at 2.5Mbps because the file is too small to be split.

So my request is this: when using youtube-dl with an external downloader, in such a way that will result in multiple files being downloaded (whether it's because multiple URLs were passed to youtube-dl, or a playlist URL was passed, or you're downloading one video in multiple "formats," or some combination of the above), youtube-dl should first determine all the URLs to be downloaded and then call the external downloader *once,* passing it all of those URLs. This will properly facilitate what is presumably the main reason external downloaders are supported in the first place: letting them handle parallelism. They can't properly do that if you only give them one URL at a time!
Repository: flutter
Issue: [proposal] Switch widget is missing a padding property
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: rust
Issue: Coverage is not generated when using rust-lld as linker
Labels: A-linkage,T-compiler,C-bug,A-code-coverage

First:
```
cargo init --lib
```
No changes to the generated crate are necessary. Then:
```sh
rm -Rf target/x86_64-unknown-linux-musl && \
CARGO_INCREMENTAL=0 RUSTFLAGS="-Zinstrument-coverage -Clink-self-contained=yes -Clinker=rust-lld" cargo +nightly test --target=x86_64-unknown-linux-musl && \
find . -name "*.profraw"
```
and
```sh
rm -Rf target/x86_64-unknown-linux-musl && \
CARGO_INCREMENTAL=0 RUSTFLAGS="-Zprofile -Clinker=rust-lld" cargo +nightly test --target=x86_64-unknown-linux-musl && \
find . -name "*.gcda"
```

I expected to see this happen:

The profiling data is generated; i.e. each `find` command outputs at least one result.

Instead, this happened:

No profiling data is generated.

This seems very similar to Issue #71233: "Coverage is not generated when using lld as linker" and it may be a regression.

Note that the specific combination of `RUSTFLAGS` that I'm trying to use is `RUSTFLAGS="-Zinstrument-coverage -Clink-self-contained=yes -Clinker=rust-lld"` so that I can use the new self-contained linking support for musl targets when profiling; see https://github.com/rust-lang/rust/blob/master/RELEASES.md#compiler. I think this combination of flags will become commonplace soon.

````
$ rustc +nightly --version --verbose
rustc 1.50.0-nightly (349b3b324 2020-11-29)
binary: rustc
commit-hash: 349b3b324dade7ca638091db93ba08bbc443c63d
commit-date: 2020-11-29
host: x86_64-unknown-linux-gnu
release: 1.50.0-nightly
```