sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Replace codecvt in wstring_conversion.h
Labels: engine,platform-windows,P2,team-engine,triaged-engine

`codecvt`'s `wstring_convert` is deprecated in C++17, with no standard-based replacement. The suggested migration path in the warning message is [MultiByteToWideChar](https://docs.microsoft.com/en-us/windows/win32/api/stringapiset/nf-stringapiset-multibytetowidechar)/[WideCharToMultiByte](https://docs.microsoft.com/en-us/windows/win32/api/stringapiset/nf-stringapiset-widechartomultibyte). It's an uglier API, but if nothing else standards-based is introduced by the time we actually have to stop using it, that will presumably be our best option.
Repository: go
Issue: x/pkgsite: keyboard shortcut to report a typo to package author
Labels: NeedsInvestigation,pkgsite,UX

<!--
Please answer these questions before submitting your issue. Thanks!
For questions, please email go-discovery-feedback@google.com.
-->
 
### What is the URL of the page with the issue?
https://pkg.go.dev/github.com/kardianos/service?tab=doc#Interface
 
 
### What is your user agent?
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36 

<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
 
 
 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
 
![2020-02-04-021801_1216x766_scrot](https://user-images.githubusercontent.com/10779755/73699401-bfad6d80-46f4-11ea-9a54-7f3f86363be4.png)

 
 
### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 
I am reading documentation and see typo made by author of package.
 
### What did you expect to see?
 
 A keyboard shortcut to report a selected typo to the author of package.
 
### What did you see instead?
No such shortcut.
Repository: rust
Issue: llvm.dbg.value should be used instead of llvm.dbg.declare wherever possible.
Labels: A-LLVM,A-debuginfo,C-enhancement,P-medium,T-compiler

*(I'm opening this issue because I can't find a pre-existing one)*

`llvm.dbg.declare` describes the location in memory of a debuginfo variable, whereas `llvm.dbg.value` describes the value itself directly. Today we only use the former, which means that in debug mode, all named variables are placed on the stack, even if they're simple scalars (e.g. integers).

Ideally, we'd use `llvm.dbg.value` in the same situations where we skip creating a stack slot (e.g. LLVM `alloca`), i.e. for scalars, vectors and pairs of scalars.

<hr/>

However, this is much harder than I expected, mostly due to LLVM being too eager to throw away `llvm.dbg.value` if computing the value can be avoided (i.e. it's not used by anything else).

I think `llvm.dbg.declare` *only* fares better because at `opt-level=0`, the lack of SROA means `alloca`s are kept around pretty much completely intact.

`FastISel` (used at `opt-level=0`) [throws away any non-trivial `llvm.dbg.value`](https://github.com/llvm/llvm-project/blob/30a8865142abe309bb9aceede2708c171a2904ea/llvm/lib/CodeGen/SelectionDAG/FastISel.cpp#L1445-L1446), but disabling it with `-C llvm-args=-fast-isel=0` only helps some simple cases (such as a reference to another stack variable - IMO `FastISel` should be improved to handle those, I don't see why it couldn't).

In general, it looks like Instruction Selection ("`ISel`") in LLVM ignores `llvm.dbg.value`s while building all of the machine instructions for a BB, and only *afterwards* does it come back to the `llvm.dbg.value`s and lower them to `DBG_VALUE`, using the value *only* if it already exists (i.e. something else needs that same value, at runtime), and otherwise it leads to `<optimized out>` vars.

Maybe the upcoming `GlobalISel` approach handles `llvm.dbg.value` better, but I would need to target `AArch64` to even try it out, from what I hear (I might still do it out of curiosity).

<hr/>

While investigating this I also came across https://github.com/rust-lang/rust/pull/8855#discussion_r374392128 - but setting `AlwaysPreserve` to `true` only keeps the debuginfo variable around, it doesn't help at all with keeping any value alive (so you end up with `<optimized out>` in the debugger, instead of the variable missing).

I haven't seen anything that would make `llvm.dbg.value` keep the value alive so it's guaranteed to be available to the debugger, but if there is such a thing, it's probably the way to go, if we want to avoid relying on the stack so much.

cc @nikomatsakis @michaelwoerister @hanna-kruppe
Repository: godot
Issue: The custom icon for a Script Class is only shown in the node creation dialog before restarting the editor
Labels: bug,topic:editor,confirmed

**Godot version:**
3.2 stable

**OS/device including version:**
Windows 10 x64 version 1909

**Issue description:**
The icon defined in a _Script Class_ is displayed in the node creation dialog but not in the scene tree dock. Reopening the project solves the issue. 

Node creation dialog             |  Scene tree dock
:-------------------------:|:-------------------------:
![dialog](https://user-images.githubusercontent.com/37230539/73703312-40a53e80-46ce-11ea-9263-bbdf63586c45.png)  |  ![dock](https://user-images.githubusercontent.com/37230539/73703311-40a53e80-46ce-11ea-90f6-a9d4ed254e13.png)

Also, several errors that seem to be related to image handling occur when using a _Script Class_, providing or not the optional icon. I guess those could be related, see #35895 

**Steps to reproduce:**
1. create a new project.
2. create a GDScript script and open it.
3. register it as a type with the Godot icon: `class_name MyClass, "res://icon.png"`
4. save the script.
5. open the node creation dialog and search for the Script Class, it will be using the custom icon.
6. add the node to the tree. Now, instead of the custom icon, the Script Class appears with the icon from the class that it extends from.
8. save the scene. The editor will output several erros.
9. Reopen the project and open the scene created in the last step. The Script Class will now be using the custom icon in both the scene tree dock and node creation dialog.
Repository: storybook
Issue: Create storybook app for Adobe Experience Manager
Labels: feature request

**Is your feature request related to a problem? Please describe.**
Many implementations for using storybook with AEM use React wrapper components. I’d like a solution where aem components are compiled down and rendered within storybook

**Describe the solution you'd like**
An AEM app option that renders aem components

**Are you able to assist bring the feature to reality?**
Yes and work is being done here: https://github.com/storybookjs/aem/tree/master/app/aem

**Additional context**
Add any other context or screenshots about the feature request here.
Repository: flutter
Issue: Specify tab size in Text widget
Labels: c: new feature,framework,engine,a: typography,P3,team-engine,triaged-engine

Hi, is there any parameter to specify tab size in text widget such as `Text` and `RichText`?

Seems it is 8 by default. In some cases developers may want to specify it as 4 or 2, for example [code synatx highlighting lib](https://github.com/pd4d10/highlight), like the [`tab-size` prop](https://developer.mozilla.org/en-US/docs/Web/CSS/tab-size) in CSS

### Screenshot

![image](https://user-images.githubusercontent.com/9524411/73716312-97a02780-4751-11ea-84ee-b5f6d6352e7c.png)


### Reproduce steps

Paste the code below to https://dartpad.dev/flutter

```dart
import 'package:flutter/material.dart';

final Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(scaffoldBackgroundColor: darkBlue),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Column(
      crossAxisAlignment: CrossAxisAlignment.start,
      children: <Widget>[
        Text(
          '#\tTab in Text',
          style: TextStyle(fontFamily: 'Courier New'),
        ),
        RichText(
          text: TextSpan(
            text: '#\tTab in RichText',
            style: TextStyle(fontFamily: 'Courier New'),
          ),
        ),
        Text.rich(
          TextSpan(text: '#\tTab in Text.rich'),
          style: TextStyle(fontFamily: 'Courier New'),
        ),
      ],
    );
  }
}

```
Repository: godot
Issue: editor/editor_node.cpp:5268 - An EditorPlugin build callback failed
Labels: bug,topic:editor,confirmed,topic:dotnet

**Godot version:**  3.2 mono 

**OS/device including version:** Ubuntu 18.04

**Issue description:** Projects fail to run, error message is editor/editor_node.cpp:5268 - An EditorPlugin build callback failed. This happened on an imported project, and later happened in a blank project as well. On the blank project, I can run it once, then the bug appears. Deleting the .sln file seems to fix the problem, restoring it causes the error to pop up again.

**Steps to reproduce:** Do not know.

**Minimal reproduction project:** https://github.com/TZubiri/godot-mcve-bug

**Related issues:** https://github.com/godotengine/godot/issues/23562 https://github.com/godotengine/godot/issues/29232
Repository: rust
Issue: Misleading error when incorrectly using crate as a module.
Labels: A-diagnostics,T-compiler,D-terse

I had a source file used as a module in my binary crate. At some point, I have decided to turn this file into a second binary crate instead. But I forgot to remove the corresponding `mod` statement in the first crate. It took me a while to figure it out because the error message was very misleading.

Here is the situation boiled down:

`Cargo.toml`
```toml
[package]
name = "rust_test"
version = "0.1.0"
authors = ["Iago-lito"]
edition = "2018"
default-run = "first_bin"

[[bin]]
name = "first_bin"
path = "src/first_bin.rs"

[[bin]]
name = "second_bin"
path = "src/second_bin.rs"
```

`src/first_bin.rs`
```rust
mod common_module;
mod second_bin; // That is very wrong..

fn main() {
    common_module::common_function();
} 
```
`src/second_bin.rs`
```rust
mod common_module; // .. but the error blames this line.

fn main() {
    common_module::common_function();
} 
```

`src/common_module.rs`
```rust
pub fn common_function() {}
```

I'd expect getting something like:
```
error[EXXX]: binary crate root file cannot be used as a module.
--> src/first_bin:2:5
  |
2 | mod second_bin;
  |     ^^^^^^^^^^
  |
  = help: remove this statement or consider not declaring `src/second_bin.rs` as the root of a binary crate in `Cargo.toml`
```

But the actual error is:
```
error[E0583]: file not found for module `common_module`
 --> src/second_bin.rs:1:5
  |
1 | mod common_module;
  |     ^^^^^^^^^^^^^
  |
  = help: name the file either second_bin/common_module.rs or second_bin/common_module/mod.rs inside the directory "src"
```

Because of this, I had to dig the whole way through [Chapter 7 of the Book](https://doc.rust-lang.org/book/ch07-00-managing-growing-projects-with-packages-crates-and-modules.html) again before I figured out that there was nothing wrong with the location of `src/common_module.rs`. Then I had to scroll the other files line by line to eventually spot the mistake.

Would this be considered a bug? Is it the correct place to report it?
Repository: godot
Issue: HTTPClient is_response_chunked (seemingly) always returns false
Labels: enhancement,documentation,topic:network

**Godot version:**
3.2 Release

**OS/device including version:**
Linux Mint 19.3

**Issue description:**
`httpclient.is_response_chunked() == false` even though the response is split into chunks

**Steps to reproduce:**
Load a file >4096 bytes and read the output. It will be chunked regardless of `is_response_chunked()`

```swift
const MY_HOST := "https://gist.githubusercontent.com"
const MY_EP := "/The5heepDev/a15539b297a7862af4f12ce07fee6bb7/raw/7164813a9b8d0a3b2dcffd5b80005f1967887475/entire_bee_movie_script"

func _ready() -> void:
	var httpclient := HTTPClient.new()
	
	assert(httpclient.connect_to_host(MY_HOST, -1, true) == OK)
	while httpclient.get_status() == HTTPClient.STATUS_RESOLVING or httpclient.get_status() == HTTPClient.STATUS_CONNECTING:
		assert(httpclient.poll() == OK)
		yield(Engine.get_main_loop(), "idle_frame")
	
	print(MY_HOST + MY_EP)
	
	assert(httpclient.request(HTTPClient.METHOD_GET, MY_EP, []) == OK)
	while httpclient.get_status() == HTTPClient.STATUS_REQUESTING:
		assert(httpclient.poll() == OK)
		yield(Engine.get_main_loop(), "idle_frame")
	
	print()
	print("Chunked?: " + str(httpclient.is_response_chunked()))
	print("Full Body: " + str(httpclient.get_response_body_length()))
	print()
	while httpclient.get_status() == HTTPClient.STATUS_BODY:
		var size := httpclient.read_response_body_chunk().size()
		if size != 0:
			print("Chunk: " + str(size))

```

**Minimal reproduction project:**
[Test7.zip](https://github.com/godotengine/godot/files/4153043/Test7.zip)
Repository: kubernetes
Issue: When a lot of persistentvolumes are created together, POST persistentvolume request latency grows significantly
Labels: kind/bug,sig/scalability,sig/storage,lifecycle/frozen

**What happened**:
I was running a scale test where I created ~8 PV/s for some period of time. I observed that POST persistentvolume latency started growing

I debugged this already:
* kube-controller-manager created PD objects in GCE
* due to rate limited error, it failed to fetch labels for new disk: https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/gcepd/gce_util.go#L191
* PersistentVolumeLabel admission controller tried to add missing GCE labels, but failed due to the same rate limited error (this also caused significant delay in request processing)

**What you expected to happen**:

POST persistentvolume latency to be ~constant during the test.

This can be achieved by:
1. removing cloud.GetAutoLabelsForZonalPD call from https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/gcepd/gce_util.go#L188
   * this way, there is no API call that can fail after object is created
   * since we just successfully created a PD, we know all parameters for that PD (zone, region, potentially in future some other disk's properties as well) and we can use this information for labels computation and there is no point in validating if it still exists.
2. Implementing proper retry strategy for cloud.GetAutoLabelsForPD calls so that we do not move load to kube-apiserver when kube-controller-manager is overloaded.
3. (partially) by simply passing zone argument in https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/gcepd/gce_util.go#L188 we can reduce number of calls there 3-4x times in case of zonal disks, but this is a mitigation only

For me, 1 is the most reasonable thing to do (and I have some draft PR for that), but I wanted to hear your opinion on this before I start cleaning the PR.

Potential drawbacks of this approach are:
* Right now, if disk with given name already exists, we simply reuse that disk (https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/legacy-cloud-providers/gce/gce_disks.go#L732). In this case, we in fact don't know what replicationZones have been used for creation of that PD, so we do need to get them in that case. We can limit get calls to only this case.

**How to reproduce it (as minimally and precisely as possible)**:
Just create a lot of pvs together.
**Anything else we need to know?**:

**Environment**:
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:

/assign @saad-ali 
/cc @wojtek-t
Repository: vscode
Issue: Allow to reveal an empty TreeView programmatically
Labels: feature-request,api,tree-views,api-proposal

Currently, it i possible to reveal/expand a TreeView only when there is an element in the TreeView. it is oputting revealing this element in the TreeView.

it would useful to be abel to expand the TreeView even when there are no elements in the Tree.

Use case:
- when testing https://github.com/camel-tooling/vscode-camelk/pull/291
- when writing a tutorial guiding users https://github.com/redhat-developer/vscode-didact/issues/4#issuecomment-557648413

asked on StackOverflow https://stackoverflow.com/questions/59983711/how-to-programmatically-make-a-treeview-visible
Repository: rust
Issue: rustc generates a lot of LLVM IR when using a match in struct field initialization
Labels: C-enhancement,A-codegen,I-compiletime,T-compiler

In https://github.com/rusterlium/rustler/issues/299, we detected compile time to increase non-linearly when using a rather simple proc-macro. In https://github.com/rusterlium/rustler/issues/299#issuecomment-579213528, we found that our decoder function results in a lot of IR. We were able to fix the issue in https://github.com/rusterlium/rustler/pull/300 by making a simple transformation for generated struct initialization.

## Transformation

The change to our proc-macro resulted in the following transformation of the resulting code.

Before:

```rust
Ok(SomeStruct {
  field1: match Decoder::decode(term[1usize])? { ... }
// .. more fields
})
```

After:

```rust
let field1 = match Decoder::decode(term[1usize]) { ... };
// .. more bindings
Ok(SomeStruct {
  field1,
// .. more fields
})
```

## Simplification

I simplified our case in https://github.com/evnu/rust-slow-compilation. I haven't been able to simplify this further: when I tried to get rid of the rustler-specific `Decoder`, or when using `map_err()`, compilation became very fast. The [README](https://github.com/evnu/rust-slow-compilation#run-the-benchmark) of the repository indicates compilation times on my machine for specific revisions of the repository.

## Meta

```
$ rustc --version --verbose
rustc 1.40.0 (73528e339 2019-12-16)
binary: rustc
commit-hash: 73528e339aae0f17a15ffa49a8ac608f50c6cf14
commit-date: 2019-12-16
host: x86_64-unknown-linux-gnu
release: 1.40.0
LLVM version: 9.0
```
Repository: terminal
Issue: Ability (perhaps shortcut?) to evenly resize splits
Labels: Help Wanted,Area-Settings,Product-Terminal,Issue-Task

Can we have added functionality that (via a keystroke) automatically resizes any multiple rows/columns  equally within the window, please.
Repository: pytorch
Issue: which pytorch do i install for running this project in my windows.link for this is ::  https://github.com/xiaojunxu/SQLNet  .IN this they have used python 2.7 ,but i am unable to install pytorch on python 2.7 environment .help me with this
Labels: module: binaries,triaged

## ❓ Questions and Help

### Please note that this issue tracker is not a help form and this issue will be closed.

We have a set of [listed resources available on the website](https://pytorch.org/resources). Our primary means of support is our discussion forum:

- [Discussion Forum](https://discuss.pytorch.org/)


cc @ezyang
Repository: tensorflow
Issue: How can I clear GPU memory in tensorflow 2?
Labels: stat:awaiting tensorflower,type:bug,comp:gpu,TF 2.7



### System information
- Custom code; nothing exotic though.
- Ubuntu 18.04
- installed from source (with pip)
- tensorflow version v2.1.0-rc2-17-ge5bf8de
- 3.6
- CUDA 10.1
- Tesla V100, 32GB RAM

I created a model, nothing especially fancy in it. When I create the model, when using nvidia-smi, I can see that tensorflow takes up nearly all of the memory. When I try to fit the model with a small batch size, it successfully runs. When I fit with a larger batch size, it runs out of memory. Nothing unexpected so far. 

However, the only way I can then release the GPU memory is to restart my computer. When I run nvidia-smi I can see the memory is still used, but there is no process using a GPU. Also, If I try to run another model, it fails much sooner. 

Nothing in the first five pages of google results works. (and most solutions are for TF1)

Is there any way to release GPU memory in tensorflow 2?
Repository: terminal
Issue: Add "Run As Administrator" menu option to Start Menu and Taskbar
Labels: Area-UserInterface,Product-Terminal,Issue-Task

# Description of the new feature/enhancement

Ability, primarily in Windows, to easily open the terminal app in an elevated session. Either via the Start Menu icon, as the PowerShell app does it, or via the taskbar icon.

Example for Start Menu:
![image](https://user-images.githubusercontent.com/11204251/73772649-2dce5080-4746-11ea-8193-c4d3e34ffb6c.png)

Example for Taskbar icon:
![image](https://user-images.githubusercontent.com/11204251/73762287-9b25b580-4735-11ea-9868-6c525b884012.png)
Repository: react-native
Issue: Android: textInput: secureTextEntry toggle causes keyboard change; keyboard does not automatically come up
Labels: Platform: iOS,Issue: Author Provided Repro,Component: TextInput,Platform: Android,Needs: React Native Team Attention

Description:
When enabling the user to toggle the secure text entry flag on a text input, on Android, two issues are occurring:
1. The keyboard does not automatically come up when rendering; the user must tap on the field.
2. Tapping the 'eye' icon to toggle the secureTextEntry flag from false to true switches the keyboard type.

React Native version:

System:    OS: Windows 10 10.0.17134
    CPU: (4) ia32 Intel(R) Pentium(R) CPU G4560T @ 2.90GHz
    Memory: 1.65 GB / 7.43 GB
  Binaries:
    Node: 12.10.0 - C:\Program Files (x86)\nodejs\node.EXE
    Yarn: 1.10.1 - C:\Users\mjfiandaca\AppData\Roaming\npm\yarn.CMD
    npm: 6.13.4 - C:\Program Files (x86)\nodejs\npm.CMD
  SDKs:
    Android SDK:
      API Levels: 23, 25, 26, 27, 28
      Build Tools: 23.0.1, 25.0.1, 26.0.3, 27.0.3, 28.0.0, 28.0.3
      System Images: android-23 | Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: Version  3.5.0.0 AI-191.8026.42.35.6010548
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.6 => 0.60.6


## Steps To Reproduce

1. Sign onto the provided snack.
2. Intermittently, the keyboard will not come up (I tested this several times; sometimes, no keyboard, sometimes, app starts, flashes, and then the keyboard comes up).
3. Tap on the 'eye' icon to toggle the secure text entry.
4. Notice the keyboard changes. 

## Expected Results
The keyboard should not change based on the secure text entry value.

## Snack, code example, screenshot, or link to a repository:
https://snack.expo.io/@mjfiandaca/toggle-securetextentry