sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Exported PackedScene Field - Rightclick->Edit for assigned resource not working
Labels: bug,topic:editor,usability

<!-- 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.stable.mono.official

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Win10

**Issue description:**
<!-- What happened, and what was expected. -->
Rightclick on packedscenes assigned as resources opens a menu with actions where 'Edit' doesn't do anything.
![grafik](https://user-images.githubusercontent.com/8841352/99983552-49294b80-2dac-11eb-9c15-0a4b19dd7b99.png)

The expected outcome would be seeing the scene opened for editing.
This may technically only apply to asset based scenes, not sure about the internals of that, but there it would match the expected outcome (and provide the menu entry with actual functionality).

**Steps to reproduce:**
Rightlick on a packedscene assigned to an exposed field of type PackedScene and chose -Edit.
Repository: TypeScript
Issue: Allow protected/private index signatures
Labels: Suggestion,Needs Proposal,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

TS1071 private protected index number string signature

## Suggestion

I can't dope out why it's not supported

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

```ts
class List {
    private [index :number] :Task
    public * [Symbol.iterator] () :Generator<Task> {}
}
```

## 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: rust
Issue: cycle errors for unevaluated constants in the param env
Labels: T-compiler,C-bug,A-const-generics,F-generic_const_exprs,I-cycle

```rust
// check-pass
#![feature(generic_const_exprs)]
#![allow(incomplete_features)]

struct Foo<T>(T);

fn test() where [u8; {
    let _: Foo<[u8; 3 + 4]>;
    3
}]: Sized {}
```
ends up failing with
```
error[E0391]: cycle detected when simplifying constant for the type system `test::{constant#0}`
  --> src/lib.rs:7:22
   |
7  |   fn test() where [u8; {
   |  ______________________^
8  | |     let _: Foo<[u8; 3 + 4]>;
9  | |     3
10 | | }]: Sized {
   | |_^
   |
note: ...which requires const-evaluating + checking `test::{constant#0}`...
  --> src/lib.rs:7:22
   |
7  |   fn test() where [u8; {
   |  ______________________^
8  | |     let _: Foo<[u8; 3 + 4]>;
9  | |     3
10 | | }]: Sized {
   | |_^
note: ...which requires type-checking `test::{constant#0}`...
  --> src/lib.rs:7:22
   |
7  |   fn test() where [u8; {
   |  ______________________^
8  | |     let _: Foo<[u8; 3 + 4]>;
9  | |     3
10 | | }]: Sized {
   | |_^
   = note: ...which requires evaluating trait selection obligation `[u8; _]: std::marker::Sized`...
   = note: ...which again requires simplifying constant for the type system `test::{constant#0}`, completing the cycle
note: cycle used when checking that `test` is well-formed
  --> src/lib.rs:10:5
   |
10 | }]: Sized {
   |     ^^^^^
```
The cycle happens while typechecking the outer array length. This happens because `Foo<[u8; 3 + 4]>` requires `[u8; 3 + 4]` to be sized. While trying to fulfill this we see the `[u8; ...]: Sized` bound in the param_env and try to unify these two. This causes us to evaluate both constants which once again relies on typechecking them.

*This test succeeds with `min_const_generics` and currently fails with `const_generics`.
Repository: flutter
Issue: App Clip uncompressed size is larger than 10MB
Labels: platform-ios,a: size,P2,team-ios,triaged-ios

Submitting a minimal app currently exceeds the 10mb uncompressed size limit with a

ITMS-90865: Thinned app clip size is too large

on `1.24.0-8.0.pre.344`.

Compressed, thinned IPA is 4.6mb, but the current uncompressed breakdown is:

Total: 11,289,773 bytes
```
[ 320]  AppClip.app
├── [ 90K]  AppClip
├── [ 34K]  Assets.car
├── [ 128]  Base.lproj
│   ├── [ 160]  LaunchScreen.storyboardc
│   │   ├── [2.2K]  01J-lp-oVM-view-Ze5-6b-2t3.nib
│   │   ├── [ 258]  Info.plist
│   │   └── [ 896]  UIViewController-01J-lp-oVM.nib
│   └── [ 160]  Main.storyboardc
│       ├── [1.8K]  BYZ-38-t0r-view-8bC-Xf-vdC.nib
│       ├── [ 258]  Info.plist
│       └── [ 923]  UIViewController-BYZ-38-t0r.nib
├── [ 128]  Frameworks
│   ├── [ 192]  App.framework
│   │   ├── [1.7M]  App
│   │   ├── [ 794]  Info.plist
│   │   ├── [  96]  _CodeSignature
│   │   │   └── [2.7K]  CodeResources
│   │   └── [ 160]  flutter_assets
│   │       ├── [   2]  AssetManifest.json
│   │       ├── [   2]  FontManifest.json
│   │       └── [725K]  NOTICES
│   └── [ 192]  Flutter.framework
│       ├── [7.4M]  Flutter
│       ├── [ 956]  Info.plist
│       ├── [  96]  _CodeSignature
│       │   └── [2.0K]  CodeResources
│       └── [781K]  icudtl.dat
├── [4.2K]  Info.plist
├── [   8]  PkgInfo
├── [  96]  _CodeSignature
│   └── [6.7K]  CodeResources
└── [104K]  embedded.mobileprovision
```

The App.framework/App breakdown is:

![Screen Shot 2020-11-23 at 11 15 52 AM](https://user-images.githubusercontent.com/156888/100005074-419e7e00-2d7d-11eb-82a8-e0a7a2a0fc7b.png)

The flutter package breakdown is:
![Screen Shot 2020-11-23 at 11 17 10 AM](https://user-images.githubusercontent.com/156888/100005207-71e61c80-2d7d-11eb-9af8-68456f42c01b.png)

The Flutter.framework/Flutter breakdown (on an equivalent Android libflutter.so, since we don't have a tool to break down iOS dylibs yet https://github.com/dart-lang/sdk/issues/44278):

![Screen Shot 2020-11-23 at 11 23 09 AM](https://user-images.githubusercontent.com/156888/100005800-63e4cb80-2d7e-11eb-84b9-43f8e7e9a143.png)

### Possible explorations

- [ ] `[90k]` Dig more into what the AppClip binary is.
- [x] `[1.6m]` Build App.framework/App with split-debug-info.
- [x] `[781k]` The NOTICES file is huge. Since the uncompressed size is being measured here, there might be de-duplication potential. https://github.com/flutter/flutter/issues/71102
- [ ] `[1m]` The 70kb ld-temp.o and the 950kb unattributed code in the Flutter.framework/Flutter / libflutter.so is suspicious.
Repository: flutter
Issue: Wrap flutter/settings channel in embedder.h API(s)
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

Basic functionality should be available to embedders via stable APIs, rather than needing to use method channels that don't have the same stability guarantees. We should wrap the information provided via the flutter/settings channel (preferred time format, OS theme, others if added) with one or more embedder.h APIs.

/cc @chinmaygarde
Repository: youtube-dl
Issue: Site support - Domestika
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.24. 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.24**
- [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.
-->

- Link: https://www.domestika.org/

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Hi, greetings from Zamora, Spain, i love your project, my friend. I have a request for you. I think is a good idea to add support to the web of Domestika, is a good place to learn new things, and i think is a good idea to download the videos after you pay for that online classes, please and thanks friend.
Repository: flutter
Issue: Wrap flutter/platform channel in embedder.h API(s)
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

Basic functionality should be available to embedders via stable APIs, rather than needing to use method channels that don't have the same stability guarantees. We should wrap the information provided via the flutter/platform channel (e.g., clipboard) with one or more embedder.h APIs.

For clipboard, we should either make sure it's easily extenisble to new data types, or wait until we have rich clipboard support implemented so we know the API will handle it.
Repository: flutter
Issue: Wrap flutter/mousecursor channel in embedder.h API(s)
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

Basic functionality should be available to embedders via stable APIs, rather than needing to use method channels that don't have the same stability guarantees. Setting mouse cursors should be handled via an embedder.h callback registration (likely via the configuration struct where many other callbacks are set up).

We'll need it to be extensible to custom cursor images in the future.
Repository: flutter
Issue: Wrap flutter/textinput channel in embedder.h API(s)
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

Basic functionality should be available to embedders via stable APIs, rather than needing to use method channels that don't have the same stability guarantees. We should wrap text input with embedder.h APIs.

This should probably be done after we revisit the way state is managed and coordinated between the framework and the embedder as to what the source of truth for the edit state is.
Repository: flutter
Issue: ☂ Eliminate the need for embedder.h clients to use system channels
Labels: engine,e: embedder,a: desktop,P3,team-engine,triaged-engine

Basic functionality should be available to embedders via stable APIs, rather than needing to use method channels that don't have the same stability guarantees. Currently, that's not the case. We should work to make the desktop embeddings channel-free, and then in the future whenever we add an important channel (as we did recently with mouse cursors) we should wrap it as a precondition for adopting it in the desktop embeddings, to hold the line.

This will have the added benefit of embedders not necessarily needing to implement the JSON message codec; currently the use of it by these internal channels force embedders to implement it even though plugins all use the standard codec.

- [ ] [flutter/keyevent](https://github.com/flutter/flutter/issues/33521)
- [ ] [flutter/mousecursor](https://github.com/flutter/flutter/issues/71117)
- [ ] [flutter/platform](https://github.com/flutter/flutter/issues/71116)
- [ ] [flutter/settings](https://github.com/flutter/flutter/issues/71099)
- [ ] [flutter/textinput](https://github.com/flutter/flutter/issues/71118)
Repository: flutter
Issue: Unable to compile an AppBundle containing multiple CPU architectures, while using a local engine
Labels: platform-android,tool,P3,team-android,triaged-android

## Description

So, the current flutter engine/framework does not allow GIF insertion. I have modified the engine and framework so that it supports basic Google Keyboard GIF insertion. That said, I have a local engine that I've compiled, and now would like to make an AppBundle build, suitable for the Play Store with it. The only issue is that the `flutter build` command only lets you specify one `--local-engine` parameter. I have tried the following:

 * `flutter build appbundle --release --target-platform=android-arm64,android-arm --local-engine=android_release,android_release_arm64 --local-engine-src-path "/path/to/my/src/dir"`
 * `flutter build appbundle --release --target-platform=android-arm64,android-arm --local-engine=android_release --local-engine=android_release_arm64 --local-engine-src-path "/path/to/my/src/dir"`

Unfortunately, the commands above, specifying multiple local engines in different ways, does not work. In the case of the first one, it will throw an error. In the case of the second one, it will complete the build process, however, it will only build for the `android_arm` architecture.

Also, for those of you wondering if I used `ninja` to build for `arm64`, yes, I did. I compiled the Flutter engine for `android-arm64`

Does anyone have any idea how I can build an AppBundle with multiple architectures, using a local flutter engine? If this isn't possible, what's the best way to get the app on the Play Store?

## Steps to Reproduce

Reproduction is more just trying to build using multiple CPU architectures, while also specifying a local engine.

1.  Build your own local flutter engine
2. Try to build an AppBundle using multiple architectures

## Flutter Doctor

```
[✓] Flutter (Channel stable, 1.22.4, on Linux, locale en_US.UTF-8)
    • Flutter version 1.22.4 at /home/zach/snap/flutter/common/flutter
    • Framework revision 1aafb3a8b9 (10 days ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

 
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /home/zach/Android/Sdk
    • Platform android-30, build-tools 30.0.1
    • ANDROID_HOME = /home/zach/Android/Sdk/
    • Java binary at: /snap/android-studio/current/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[!] Android Studio
    • Android Studio at /snap/android-studio/current/android-studio/
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • android-studio-dir = /snap/android-studio/current/android-studio/
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.
```
Repository: rust
Issue: Rustc suggests the same method twice when a mismatched type is found
Labels: T-compiler,C-bug,A-suggestion-diagnostics,D-invalid-suggestion,D-verbose

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
let what_rustc_thinks = clean::Item::from_def_id_and_parts(did, Some(name), kind, cx);
```

I expected to see this happen: Rustc suggests `name.to_string()`.

Instead, this happened:

```
error[E0308]: mismatched types
   --> src/librustdoc/clean/inline.rs:127:74
    |
127 |     let what_rustc_thinks = clean::Item::from_def_id_and_parts(did, Some(name), kind, cx);
    |                                                                          ^^^^ expected struct `std::string::String`, found struct `Symbol`
    |
help: try using a conversion method
    |
127 |     let what_rustc_thinks = clean::Item::from_def_id_and_parts(did, Some(name.to_string()), kind, cx);
    |                                                                          ^^^^^^^^^^^^^^^^
127 |     let what_rustc_thinks = clean::Item::from_def_id_and_parts(did, Some(name.to_string()), kind, cx);
    |                                                                          ^^^^^^^^^^^^^^^^
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version`: rustc 1.48.0-beta.3 (4708ac76e 2020-10-15)
Repository: TypeScript
Issue: unnecessary generic type in quick info for class methods in some namespaces
Labels: Bug,Domain: Quick Info

**TypeScript Version:**  3.9, 4.0, 4.1

**Search Terms:** generic namespace interface signature method

**Code**

```ts
interface Foo<S> {}

namespace Foo {
  export class Bar<T> {}
}

const a = new Foo.Bar<number>()
                  ^^^ hover on it!
```

**Expected behavior:**

```
constructor Foo.Bar<number>(): Foo.Bar<number>
```

**Actual behavior:**

```
constructor Foo<S>.Bar<number>(): Foo<S>.Bar<number>
               ^^^                   ^^^
```

If you hover on `a`, everything seem just right:

```
const a: Foo.Bar<number>
```

**Playground Link:** https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgGIHt0B4DKA+ZAbwF8BYAKApDgFsIBnAB0RQ3SIuWQgA9H0oYZAgA2cevWQAhOFCwAVAiQplK5BOhD0hcZAF5kICAHc0mAHQy5IAK40ARtDwAKAJQUgA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: pytorch
Issue: PyTorch Mobile speed_benchmark_torch crashes on mobile optimized model
Labels: oncall: mobile

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

## To Reproduce

Steps to reproduce the behavior:

1. Build binary using:
BUILD_PYTORCH_MOBILE=1 ANDROID_ABI=arm64-v8a ./scripts/build_android.sh -DBUILD_BINARY=ON

2. Export MobileNet v2:
import torch
from torch.utils.mobile_optimizer import optimize_for_mobile
model = torch.hub.load(‘pytorch/vision:v0.6.0’, ‘mobilenet_v2’, pretrained=True)
model.eval()

scriptedm = torch.jit.script(model)
torch.jit.save(scriptedm, “mobilenet_v2_scripted.pt”)
optedm = optimize_for_mobile(scriptedm)
torch.jit.save(optedm, “mobilenet_v2_opted.pt”)

3. Run the optimized model:
(python3.7) user1$ adb shell “/data/local/tmp/speed_benchmark_torch --model=/data/local/tmp/mobilenet_v2_opted.pt” --input_dims=“1,3,224,224” --input_type=“float”
Starting benchmark.
Running warmup runs.
Main runs.
Segmentation fault

mobilenet_v2_scripted.pt however works fine. Device is Pixel 3a on Android 10.

## Expected behavior

Well, it shouldn't crash


## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

 - PyTorch Version (e.g., 1.0): 4ed7f36ed in master
 - OS (e.g., Linux): Android 10
 - How you installed PyTorch (`conda`, `pip`, source): N/A
 - Build command you used (if compiling from source): BUILD_PYTORCH_MOBILE=1 ANDROID_ABI=arm64-v8a ./scripts/build_android.sh -DBUILD_BINARY=ON
 - Python version: 3.7
 - CUDA/cuDNN version:
 - GPU models and configuration:
 - Any other relevant information:

## Additional context
Repository: create-react-app
Issue: Bump y18n to >=5.0.5
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

y18n@4.0.0 is being flagged by automated security checks. Recommended to upgrade to 5.0.5.

```
This affects the package y18n before 5.0.5. PoC by po6ix: const y18n = require('y18n')(); y18n.setLocale('proto'); y18n.updateLocale({polluted: true}); console.log(polluted); // true
```
Repository: create-react-app
Issue: Are const enums not supported now ?
Labels: stale,needs triage

Are const enums now not supported ?
Sandbox: https://codesandbox.io/s/great-fermat-y1pup?file=/src/App.tsx
Repository: flutter
Issue: Volume keys can't be caught by focusScope with autofocus
Labels: a: text input,framework,f: focus,has reproducible steps,P3,team-framework,triaged-framework,found in release: 3.19,found in release: 3.20

I use code like this to catch volume key events and prevent system behavior, but it can't listen to the volume key unless normal keys like 'A' pressed or other events takes the focus( like call up a keyboard),
```
MaterialApp(
        home: Scaffold(
            body: FocusScope(
                autofocus: true,
                child: Focus(
                    autofocus: true,
                    canRequestFocus: true,
                    onKey: (data, event) {
                      if (event
                          .isKeyPressed(LogicalKeyboardKey.audioVolumeUp)) {
                        print("Volume up");
                        return true;
                      }
                      if (event
                          .isKeyPressed(LogicalKeyboardKey.audioVolumeDown)) {
                        print("Volume down");
                        return true;
                      }
                      return false;
                    },
                    child: Text("Hallochen")))));
```
Repository: godot
Issue: RigidBody created by script cannot be selected in editor
Labels: bug,topic:editor,confirmed

**Godot version:**
4.0 and 3.2.3


**OS/device including version:**
Windows 10


**Issue description:**
The RigidBody created by the script in the "tool" mode cannot be selected in the editor.


**Steps to reproduce:**
Add a RigidBody3d with script to the scene and try to select it in the viewport. Script for object creation:
```
@tool
extends RigidBody3D


var _collision : CollisionShape3D
var _mesh : MeshInstance3D


func _init():
	_collision = CollisionShape3D.new()
	_collision.shape = SphereShape3D.new()
	self.add_child(_collision)
	
	_mesh = MeshInstance3D.new()
	_mesh.mesh = SphereMesh.new()
	self.add_child(_mesh)
	
	return
```


**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->

[Test-RigidBody.zip](https://github.com/godotengine/godot/files/5588498/Test-RigidBody.zip)