sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Visual Script property selector
Labels: bug,topic:visualscript

3.3.rc8
WIN 10 
GLES3

The visual script editor provides a limited amount of property's to select from. 
That the VSeditor gives the same options as GDscript

I will give a example using the Timer Node timer.time_left
<img width="870" alt="Timer Node VScript autocompete example" src="https://user-images.githubusercontent.com/20573784/114446719-d80af900-9bd1-11eb-8a7b-466659cb0d81.PNG">
<img width="269" alt="Timer Node GDScript autocompete example" src="https://user-images.githubusercontent.com/20573784/114446722-d8a38f80-9bd1-11eb-997d-6a61ffbd0aa7.PNG">
<img width="878" alt="Timer Node propeties sourcecode" src="https://user-images.githubusercontent.com/20573784/114446786-ece78c80-9bd1-11eb-84db-1bb14fc374ce.PNG">

I assume this is due to this code difference in propery_selector.cpp vs visual_script_property_selector.cpp
(my understanding of c++ and the Godot project is minimal)

Control drag property
Add visual script try to get any autocomplete hints in the editor

[Projects debug.zip](https://github.com/godotengine/godot/files/6299280/Projects.debug.zip)


Being able to edit the inspector-property in line edit would be a awesome work around

Similar to #28136 

workaround created using https://godotengine.org/asset-library/asset/922
Repository: flutter
Issue: Allow RestorationAPI to restore any StatefulWidget at runtime
Labels: framework,c: proposal,P3,a: state restoration,team-framework,triaged-framework

When switching navigation routes it is often desired to retain various view state such as ScrollPosition, TextFields and Animation state. 

Currently this requires using something like an `IndexedStack`, where all Widgets are kept in the tree and in memory. This is really not conducive to changing routes with Navigator or MaterialApp.router.

It would be nice if somehow we could instead use the StateRestoration API to handle this.  Ideally this would be syncronous, and restore data from RAM rather than disk, at least for the most recently cached states.

**Desired Result:**
When a state is disposed, it saves it's restorable fields. When a state with the same id is loaded again, it fetches any restored state it can. Ideally there is some way we can skip `initState()` here as well. Or incorporate it into it:
```
void initState(){
  if(canRestoreState == true) restoreState();
  else {
     // First init
  }
}
```
Repository: rust
Issue: Make `TokenCursor` cheaper to clone
Labels: A-macros

Cloning a `rustc_parse::parser::TokenCursor` is a convenient way to save our current position im the overall token stream. Unfortunately, any code that needs to clone it is very hot, so actually cloning it can easily lead to regressions of several percentage points on rustc-perf.

For example, the token collection code goes to a lot of effort to avoid cloning the `TokenCursor` when possible:

https://github.com/rust-lang/rust/blob/d0695c9081b16077d0aed368bccaf437d77ff497/compiler/rustc_parse/src/parser/attr_wrapper.rs#L205-L221

Speeding up the cloning of `TokenCursor` would probably give us nice wins on attribute-heavy code.
In https://github.com/rust-lang/rust/pull/82844, I attempted to make the parser use a 'flattened' list of tokens instead of a `TokenStream`. This would have allowed the cursor to be 'cloned' by just copying the index into the flat stream. Unfortunately, the cost of 'flattening' a `TokenStream` made this a net performance loss.

Some ideas to try:
* Use an `ArrayVec` instead of a `Vec` for the `stack` field - if the majority of code we parse is not nested very deeply within brackets/braces/parens, this could improve performance. However, I'm not sure how much time is actually being spent allocating an new `Vec`
Repository: create-react-app
Issue: React-scripts causes yarn workspaces to fail silently
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

Attempting to run yarn install in a large workspaces project gets about 75% through linking dependencies and then fails silently. On subsequent tries it fails almost immediately after starting linking dependencies. Even with --verbose there is no error or any indication of why it stops. 

After removing packages one by one I was able to narrow it down to an interaction between yarn workspaces and react-scripts from one of the workspaces that uses create react app. If I remove the react-scripts package, yarn installs fine for the whole workspaces project. If I move the create react app workspace to a separate project it runs correctly.


### Did you try recovering your dependencies?
Yes

### Which terms did you search for in User Guide?
Workspaces, Yarn, Install, react-scripts


### Environment

Environment Info:

  current version of create-react-app: 4.0.3
  running from C:\Users\ccourtney\AppData\Roaming\npm-cache\_npx\11380\node_modules\create-react-app

  System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
  Binaries:
    Node: 12.20.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - C:\Program Files\nodejs\yarn.CMD
    npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 89.0.4389.114
    Edge: Spartan (44.19041.423.0), Chromium (89.0.774.75)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    react: Not Found
    react-dom: Not Found
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

1.  Pull a project with yarn workspaces that has a create react app in one of the workspaces
2.  Run yarn install
3. It fails silently

### Expected behavior

Yarn finishes installs correctly

### Actual behavior

Yarn fails silently about 75% through when react-scripts is present



A couple notes, the project installs correctly on some other peoples machines. Also, I have opened a ticket on yarn here https://github.com/yarnpkg/yarn/issues/8603  but wanted to check if the issue might be here.
Repository: electron
Issue: [Bug]: unable to close and reopen native window with same frame name
Labels: bug :beetle:,platform/all,status/confirmed,10-x-y,has-repro-gist,11-x-y,12-x-y,13-x-y,24-x-y

### Preflight Checklist

I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version

- 13.0.0-beta.12
- 12.0.1
- 11.4.2
- 10.4.2
- 9.4.4

### What operating system are you using?

- macOS
- Windows

### Operating System Version

- macOS Big Sur 11.2.3
- Windows 10 20H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

When running the following, the window should be closed and reopened.
```ts
let win = window.open('about:blank', 'frameName');
// ...
win.close();
win = window.open('about:blank', 'frameName');
```

Here's what happens in Chrome:

```
data:text/html,<button id="b">open</button><script>b.onclick=()=>{if (window.win) { win.close() } window.win=window.open("about:blank","frameName","width=256,height=256,top=0,left=0")}</script>
```

https://user-images.githubusercontent.com/1656324/114467390-db918680-9bb7-11eb-8c8c-62ff7ee18a15.mov

### Actual Behavior

Upon calling `window.open` a second time with the same frame name, the window is not opened. This is with `nativeWindowOpen` enabled, I haven't tested with it disabled.

https://user-images.githubusercontent.com/1656324/114467471-f82dbe80-9bb7-11eb-8a73-c26803b063a3.mov

### Testcase Gist URL

https://gist.github.com/samuelmaddock/a9e014c30b16dbefb17e16f5954c2422
Repository: flutter
Issue: Consider filtering INSTALL_FAILED_UPDATE_INCOMPATIBLE warning message from non-verbose tool logs
Labels: c: new feature,platform-android,tool,P3,team-android,triaged-android

I ran flutter to create a new project.
I did:
     1. flutter create p2
     2. cd p2
     3. dart migrate --apply-changes
     4. flutter run
 During the Gradle build process receive error message:

✓ Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...                12.1s
Error: ADB exited with exit code 1
Performing Streamed Install

adb: failed to install /home/leemke/proj/flutter/p2/build/app/outputs/flutter-apk/app.apk: Failure
[INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.example.p2 signatures do not match previously installed
version; ignoring!]
Uninstalling old version...
Installing build/app/outputs/flutter-apk/app.apk...                17.3s
Syncing files to device Google Pixelbook...                        275ms

==========================================

I don't know what this means, or what caused it. 
The application seems to run. 
I am wondering if this is normal.  Is there something in error in my environment?
Will this situation continue in the future? will it get worse?
I view any exceptions as an indication of future problems (small or large).

How do I fix this? Is it possible?
Repository: flutter
Issue: Android applications that crash on startup cause flutter run to hang forever
Labels: tool,a: quality,P3,team-tool,triaged-tool

Reproducing this with a normal app is a bit tricky, but in a pinch you can patch the following bit of code into your flutter tool:

```diff
--- a/packages/flutter_tools/lib/src/base/build.dart
+++ b/packages/flutter_tools/lib/src/base/build.dart
@@ -152,7 +152,7 @@ class AOTSnapshotter {
         genSnapshotArgs.add(option);
       }
     }
-
+    String aotSharedLibrary;
     final String assembly = _fileSystem.path.join(outputDir.path, 'snapshot_assembly.S');
     if (platform == TargetPlatform.ios || platform == TargetPlatform.darwin_x64) {
       genSnapshotArgs.addAll(<String>[
@@ -160,7 +160,7 @@ class AOTSnapshotter {
         '--assembly=$assembly',
       ]);
     } else {
-      final String aotSharedLibrary = _fileSystem.path.join(outputDir.path, 'app.so');
+      aotSharedLibrary = _fileSystem.path.join(outputDir.path, 'app.so');
       genSnapshotArgs.addAll(<String>[
         '--snapshot_kind=app-aot-elf',
         '--elf=$aotSharedLibrary',
@@ -215,6 +215,11 @@ class AOTSnapshotter {
       _logger.printError('Dart snapshot generator failed with exit code $genSnapshotExitCode');
       return genSnapshotExitCode;
     }
+    var file = _fileSystem.file(aotSharedLibrary)
+      .openSync(mode: FileMode.write);
+    file.setPositionSync(1000);
+    file.writeFromSync(List.filled(1000, 23));
+    file.closeSync();
```

The `flutter run --profile` when targeting an Android device and you will get a crash on startup like so:

```
✓  Built build\app\outputs\flutter-apk\app-profile.apk (41.8MB).
Installing build\app\outputs\flutter-apk\app.apk...              2,787ms
E/flutter ( 6037): [ERROR:flutter/runtime/dart_vm_data.cc(18)] VM snapshot invalid and could not be inferred from settings.
E/flutter ( 6037): [ERROR:flutter/runtime/dart_vm.cc(257)] Could not set up VM data to bootstrap the VM from.
E/flutter ( 6037): [ERROR:flutter/runtime/dart_vm_lifecycle.cc(84)] Could not create Dart VM instance.
F/flutter ( 6037): [FATAL:flutter/shell/common/shell.cc(155)] Check failed: vm. Must be able to initialize the VM.
```

Unfortunately after this crash happens, the CLI is still waiting for the launch intent to return and is otherwise unresponsive. Unless we get a clear signal from the `am` command, our best guess might be some sort of timeout - though this needs to find a way to fit into the framework/tooling timeout policy.

One idea would be to display a Y/N prompt to keep waiting after N seconds have passed, or to attach the `q` quit terminal handler much earlier. I don't believe that would violate the timeout policy, though @Hixie to confirm.
Repository: react-native
Issue: const TVEventHandler = require('TVEventHandler'); not found
Labels: Issue: Author Provided Repro,Platform: tvOS

## Description
const TVEventHandler = require('TVEventHandler'); not found
In other versions it is found in node_modules/react-native/Libraries/Components/AppleTV/TVEventHandler.js

## React Native version:
System:
    OS: Linux 5.10 Kali GNU/Linux Rolling 2021.1
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 6.73 GB / 32 GB
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 12.21.0 - /usr/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.5.2 - /usr/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 11.0.11-ea - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1 
    react-native: 0.64.0 => 0.64.0 
  npmGlobalPackages:
    *react-native*: Not Found
Thanks for you atention.
Repository: flutter
Issue: [google_maps_flutter] Enable gesture handling on web
Labels: p: maps,platform-web,package,c: proposal,P3,team-web,triaged-web

 
https://developers.google.com/maps/documentation/javascript/interaction#gesture-handling

I believe the flutter maps are from Javascript. And most needed feature is missing, In the flutter web we need the Scroll and zooming option.

The current implementation is only allowing user to Use two fingers to zoom or pan the map is not the desired way. 

Please enable the gestureHandling:

Thanks!
Repository: youtube-dl
Issue: Add option of hours to --dateafter
Labels: request

## Checklist

- [X] I'm reporting a feature request
- [X] I've verified that I'm running youtube-dl version **2021.04.07**
- [X] I've searched the bugtracker for similar feature requests including closed ones


## Description

I would like to specify an upload date of within the last X hours. Currently, only the following options are supported:
```
Relative dates: Dates in the format (now|today)[+-][0-9](day|week|month|year)(s)?
```

e.g .
```
youtube-dl --dateafter now-1hour ...
```
Repository: youtube-dl
Issue: Add option to get last modified time from header
Labels: request

## Checklist

- [X] I'm reporting a feature request
- [X] I've verified that I'm running youtube-dl version **2021.04.07**
- [X] I've searched the bugtracker for similar feature requests including closed ones


## Description

I would like to request the Last-modified header of the video I am about to download before downloading it.
Currently, the only options are:

```
   -g, --get-url                        Simulate, quiet but print URL
    -e, --get-title                      Simulate, quiet but print title
    --get-id                             Simulate, quiet but print id
    --get-thumbnail                      Simulate, quiet but print thumbnail URL
    --get-description                    Simulate, quiet but print video description
    --get-duration                       Simulate, quiet but print video length
    --get-filename                       Simulate, quiet but print output filename
    --get-format                         Simulate, quiet but print output format
```

e.g .
```
youtube-dl --get-mtime ...
```
Repository: youtube-dl
Issue: Telegram
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 2021.04.07. 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 **2021.04.07**
- [ 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://t.me/r_Damnthatsinteresting/23326
- Channel https://t.me/s/r_Damnthatsinteresting



## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
Requesting support for native Telegram videos. Channels can be displayed in browser, groups cannot but being able to crawl all of the videos uploaded on a channel (instead of using Telegram's export tool which kindof blows) would be pretty sweet.
Repository: go
Issue: doc: Effective Go section about Errors uses type assertion without mentioning errors.As
Labels: Documentation,NeedsDecision

### What version of Go are you using (`go version`)?
n/a

### Does this issue reproduce with the latest release?
n/a

### What operating system and processor architecture are you using (`go env`)?
n/a

### What did you do?
Read about errors in ["Effective Go"](https://golang.org/doc/effective_go#errors)

### What did you expect to see?
Examples that use the current best way of inspecting concrete error values or acknowledgment that there is a better way with a reference to details about the alternatives.

### What did you see instead?
Use of a type assertion in the style typically used with Go 1.12 and earlier without any mention of [`errors.As`](https://golang.org/pkg/errors/#As) available since Go 1.13.
Repository: flutter
Issue: [webview_flutter] outerHTML is incomplete on Android and contains unicode characters from evaluateJavascript
Labels: platform-android,p: webview,package,has reproducible steps,P2,found in release: 2.0,found in release: 2.2,team-android,triaged-android

webview_flutter: ^ 2.0.4

**[Android]** 
When I use WebViewController to get html through String html = await _controller.evaluateJavascript (
         "window.document.getElementsByTagName ('html') [0] .outerHTML;");
The value in the other html is incomplete, it only contains part of the html of the page. I do not know why?
I have tried quite a few devices and the different websites fail?
And I can't parser string html to Document in html library?
 **[IOS]** 
Everything works fine, still fetching full html.
Repository: pytorch
Issue: Don't define __assert_fail on systems using `musl-dev` headers
Labels: module: build,triaged

## 🐛 Bug

## To Reproduce

Steps to reproduce the behavior:

1. Install system dependencies for system using `musl`, would include something like a `musl-dev`/`musl-devel` package
2. Follow install from source directions

```
In file included from /usr/include/c++/10.2.1/cassert:44,
                 from /pytorch/c10/util/Optional.h:31,
                 from /pytorch/c10/util/numa.h:4,
                 from /pytorch/c10/core/CPUAllocator.h:8,
                 from /pytorch/c10/core/CPUAllocator.cpp:1:
/usr/include/assert.h:19:16: error: conflicting declaration of C function 'void __assert_fail(const char*, const char*, int, const char*)'
   19 | _Noreturn void __assert_fail (const char *, const char *, int, const char *);
      |                ^~~~~~~~~~~~~
In file included from /pytorch/c10/core/DeviceType.h:8,
                 from /pytorch/c10/core/Device.h:3,
                 from /pytorch/c10/core/Allocator.h:6,
                 from /pytorch/c10/core/CPUAllocator.h:6,
                 from /pytorch/c10/core/CPUAllocator.cpp:1:
/pytorch/c10/macros/Macros.h:291:5: note: previous declaration 'void __assert_fail(const char*, const char*, unsigned int, const char*)'
  291 |     __assert_fail(
      |     ^~~~~~~~~~~~~
```

## Expected behavior

Build of `torch` to succeed.

** Actual behavior

https://github.com/pytorch/pytorch/blob/5ba4cfb7bfbfe5f1be303a5326bb3d2397e011ea/c10/macros/Macros.h#L291

This hard-codes in a function that is already declared in the `assert.h` header provided by `musl-dev`-like packages.

## Environment

ENV Vars set before build:

```
BLAS="OpenBLAS"
BUILD_CAFFE2=OFF
BUILD_TEST=OFF
BUILD_DISTRIBUTED=OFF
USE_QNNPACK=OFF
USE_PYTORCH_QNNPACK=OFF
USE_NUMPY=OFF
USE_CUDA=OFF
USE_ROCM=OFF
USE_MKLDNN=OFF
USE_NUMA=OFF
```

```
/pytorch # python3 ./torch/utils/collect_env.py 
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Alpine Linux v3.13 (x86_64)
GCC version: (Alpine 10.2.1_pre1) 10.2.1 20201203
Clang version: Could not collect
CMake version: version 3.18.4

Python version: 3.8 (64-bit runtime)
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.20.2
[conda] Could not collect
```

cc @malfet @seemethere @walterddr
Repository: pytorch
Issue: We should perhaps prevent linking against LibTorch DLLs with the wrong configuration (debug vs release)
Labels: module: windows,triaged

Right now all the official LibTorch builds are DLLs compiled with dynamic CRT (/MD for release and /MDd for debug). When the users are linking against LibTorch, there's no way to tell if a `torch_cpu.dll` is built with `Debug` or `Release`. This causes a problem called "mixing C runtime library versions". Say the user is building with `CMAKE_BUILD_TYPE=Debug`, but consuming the *release* version of LibTorch. Passing variables with `std::string` type would cause immediate crash due to the memory layout not correctly recognized at the CRT boundary.

cc @peterjc123 @mszhanyi @skyline75489 @nbcsm