sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Flutter doesn't honor the Gradle service directory path setting of Android Studio
Labels: platform-android,tool,t: gradle,P3,team-android,triaged-android

## Steps to Reproduce

1. Change the setting "Build, Execution, Deployment" - Gradle - "Service directory path" in Android Studio (it is `%userprofile%\.gradle` by default).
2. Build an Android Studio project. Note that it creates the configured path and places Gradle there.
3. Build a Flutter projct. Note that it does **not** use the configured path but instead creates the default path (`%userprofile%\.gradle`) and places Gradle there.

Note: I do not have a Gradle directory configured in `flutter config`. As far as I know this should mean that it takes the one from Android Studio.

## Logs

`flutter doctor -v`:
```
[√] Flutter (Channel stable, v1.7.8+hotfix.4, on Microsoft Windows [Version 10.0.17763.615], locale de-AT)
    • Flutter version 1.7.8+hotfix.4 at C:\Android\flutter
    • Framework revision 20e59316b8 (3 weeks ago), 2019-07-18 20:04:33 -0700
    • Engine revision fee001c93f
    • Dart version 2.4.0


[√] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
    • Android SDK at C:\Android\Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.1
    • ANDROID_HOME = C:\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 38.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.
```
Repository: terminal
Issue: Feature Request: Bundle more icons with good names
Labels: Issue-Feature,Area-Settings,Product-Terminal

# Description of the new feature/enhancement

There are a number of interesting icons that could apply in various situations, such as the VS icon, the Azure or Office/Exchange logos, SQL, GitHub, etc as well as various generic icons like a database drum or a terminal icon.

# Proposed technical implementation details (optional)

Adding new icon assets and giving them a good name should be easy for Microsoft-owned properties.  Some may need to be invented (eg, C# has no logo, where F# has a rather spiff one).

Care should be taken to include variants for various contrast situations.

Giving them real names instead of GUID names would make them easier to use without having to track down random images on the web, or something buried in the file system.

Proposed icon set:

- [ ] Visual Studio
- [ ] C# (needs to be defined)
- [ ] F#
- [ ] Exchange
- [ ] GitHub
- [ ] Azure
- [ ] Microsoft
- [ ] Windows (CMD's icon is.. not great)
- [ ] Generic network terminal (eg, for SSH, Telnet, FTP, etc)
- [ ] Generic database
- [ ] Generic file system

Potential third party icons, if they agree?

- [ ] Git
- [ ] Python
- [ ] Julia
- [ ] Wolfram
- [ ] Create mechanism to propose new ones to engage
Repository: rust
Issue: Warn about 2015 edition on path & extern crate related errors
Labels: C-enhancement,A-diagnostics,A-resolve,T-compiler,D-edition

[Related forum thread](https://internals.rust-lang.org/t/warn-against-accidental-use-of-2015-edition/10666)

Users may be using 2015 edition without being aware of it, e.g. by copying an older template/tutorial or creating `Cargo.toml` by hand. 

Accidental use of 2015 edition may cause puzzling path-related errors, such as E0432 & E0433.

When 2015-edition code fails to resolve paths, rustc could say if it works in 2018 edition (#61914) or at least emit a note saying that the failing code uses 2015 edition, and that switching to 2018 may help.
Repository: vue-element-admin
Issue: 复合型输入框显示bug
Labels: enhancement :star:,feature

## Bug report（问题描述）
element的复合型输入框，在table 表头上的显示bug
#### Steps to reproduce（问题复现步骤）
custom-theme的样式导致element-ui的复合型输入框显示出问题
```css
.el-table th div {
    display: inline-block;
    padding-left: 10px;
    padding-right: 10px;
    line-height: 40px;
    -webkit-box-sizing: border-box;
    box-sizing: border-box;
    overflow: hidden;
    white-space: nowrap;
    text-overflow: ellipsis;
}
```
```html
    <el-table>
      <el-table-column align="right">
        <template v-slot:header="{row}">
          <el-input placeholder="请输入内容" class="input-with-select">
            <el-button slot="append" icon="el-icon-search" />
          </el-input>
        </template>
      </el-table-column>
    </el-table>
```
#### Screenshot or Gif（截图或动态图）
![image](https://user-images.githubusercontent.com/13636643/62534734-5c916a00-b87c-11e9-8074-6430587253ca.png)

#### Other relevant information（格外信息）
- Your OS:windows 10
- Node.js version:v12.7.0.
- vue-element-admin version:4.2.1
Repository: pytorch
Issue: model->to(device) costs over a millisecond when doing nothing
Labels: module: performance,triaged

## 🐛 Bug

On a system with a single GPU, with a model already loaded to this GPU, I expect model->to(torch::kCUDA) to be almost free. However, I find it takes approximately 1.5ms.

## To Reproduce

Steps to reproduce the behavior:

```C++
    // Set model to correct device
    using namespace std::chrono;
    auto start = high_resolution_clock::now();
    model->to(tens.device());
    std::cout << duration_cast<microseconds>(high_resolution_clock::now() - start).count() << "us for to()" << std::endl;
```

1414us for to()
1523us for to()
...

Modified as a workaround:
```C++
                        // Set model to correct device
                        using namespace std::chrono;
                        auto start = high_resolution_clock::now();
                        auto deviceIndex = tens.device().is_cpu() ? -1 : tens.device().index();
                        if (currentDevice != deviceIndex)
                        {
                            model->to(tens.device());
                            currentDevice = deviceIndex;
                        }
                        std::cout << duration_cast<microseconds>(high_resolution_clock::now() - start).count() << "us for to()" << std::endl;
```
0us for to()
0us for to()
...

## Expected behavior

It should be a similar speed to the second version (workaround)

## 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): 1.2.0-pre
 - OS (e.g., Linux): Windows 10
 - How you installed PyTorch (`conda`, `pip`, source): nightly
 - Build command you used (if compiling from source):
 - Python version: N/A
 - CUDA/cuDNN version: 10/7.5
 - GPU models and configuration: Nvidia RTX 2060
 - Any other relevant information:
Repository: TypeScript
Issue: "after" custom transformer seems to be called before the JS transformation.
Labels: Needs Investigation

Hi there,

I am trying to implement an `after` custom transformer as I am planning to make changes to the transpiled JS code.
According to the inline documentation (`Custom transformers to evaluate after built-in .js transformations.`), the transformer should be called after the source file is transpiled to JS. In the transformer API, the only provided argument is a "SourceFile" object which has  no reference to the JS code (or at least I couldn't find it).

What's the point of having an after transformer if you don't get access to the transformed source code, nor have possibilities to change it? Is it a bug or is it like that on purpose? 

Thanks in advance
Repository: TypeScript
Issue: Conditional types break with property chaining
Labels: Bug

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.5.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

property chaining, generic, object type param, conditional type

**Code**

Modified version of @fatcerberus ' attempt to break TS.

```ts
type Droste<T extends {x:number|string}> = {
    value: T,
    /**
     * Should alternate between string and number
     */
    droste: Droste<{x:(T["x"] extends number ? string : number)}>
};

declare const droste: Droste<{x:number}>;

//number
const _0 = droste.droste.droste.droste.droste.droste.droste.droste.droste.droste.droste
    .droste.droste.droste.droste.droste.droste.droste.droste.droste.droste
    .droste.droste;
const _1 = _0.droste; //string
const _2 = _1.droste; //number
const _3 = _2.droste; //string

const _4 = _3.droste; //Expected number, actual string, ???
const _5 = _4.droste; //string
const _6 = _5.droste; //string
const _7 = _6.droste; //string
const _8 = _7.droste; //string
const _9 = _8.droste; //string
//string forever and ever. Where is `number`?
```

**Expected behavior:**

Each access to `.droste` should alternate between `string` and `number`.
Or give a max instantiation depth/count error.

**Actual behavior:**

It alternates between `string` and `number` and then breaks after while.
From that point, it just sticks with `string`.

No errors given.

**Playground Link:**

[Playground](https://www.typescriptlang.org/play/#code/C4TwDgpgBAIgTgewM7AgHgCpQgD1QOwBMkoBvHALnwFcBbAIwjgB8U4BLfAcwF8A+KAF4yAKCjioANwCGAG2oQKUDABoxEgPQAqLeolaoAZQAWCarMJQ5qOPmmoojYAHcIEfFDacuVolBoMTHriWhrBhIgoirCRqGjkFAAUGADaAEQ4aQC62HjuxP50jHBQAPyewBzcUEoBxQCU-CI8ANwiIoQQAMay0nDQXQj4KFARyKhK8OPoCXVM-G0iGhpzcCKDw8BQAPoADEKjsRAAdGNRp0cX01fnZ6g393cnTw-PR8Gvny-flz-Xf7d3hIoF8jm0NiNtgBGA57V4tKDLLzcdZDSEAJlhUPhiJWRSCEK22wAzLD0TikZVvO1CTsACyw4kUjQAURwkC6qEsqxUVk51DkFSqXF5pTFqM2OwArLC6czkVwJZCAGywqXyqko2nbADssOVGuFSqJAA5YTrDdTtQBOWEmy0oynCqAAMwQ-UkTF8lggnrgxygAHVjExoOwSAADVYR0pAA)

**Related Issues:** 

It is similar to https://github.com/microsoft/TypeScript/issues/32707
Except, it gives up and resolves the type to `string`, rather than `any`.
Repository: rust
Issue: bare_trait_objects help is incorrect with Box<Trait + 'lifetime> in 2015 edition
Labels: A-lints,T-compiler,C-bug,A-suggestion-diagnostics,D-edition

The help text message for `bare_trait_objects` is incorrect when using the 2015 edition.

The following example gives a correct help text in the 2015 and 2018 edition:
```rust
pub fn test(_: Box<::std::any::Any>) {}
```
```rust
warning: trait objects without an explicit `dyn` are deprecated
 --> src/lib.rs:1:20
  |
1 | pub fn test(_: Box<::std::any::Any>) {
  |                    ^^^^^^^^^^^^^^^ help: use `dyn`: `dyn (::std::any::Any)`
  |
  = note: `#[warn(bare_trait_objects)]` on by default
```
but adding a lifetime to the trait bound produces an incorrect help message for the 2015 edition:
```rust
pub fn test(_: Box<::std::any::Any + 'static>) {
}
```
```rust
warning: trait objects without an explicit `dyn` are deprecated
 --> src/lib.rs:1:20
  |
1 | pub fn test(_: Box<::std::any::Any + 'static>) {
  |                    ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn ::std::any::Any + 'static`
  |
  = note: `#[warn(bare_trait_objects)]` on by default
```
Applying the suggest help text in 2015 edition code results in:
```rust
pub fn test(_: Box<dyn ::std::any::Any + 'static>) {
}
```
```rust
error[E0433]: failed to resolve: use of undeclared type or module `dyn`
 --> src/lib.rs:1:20
  |
1 | pub fn test(_: Box<dyn ::std::any::Any + 'static>) {
  |                    ^^^ use of undeclared type or module `dyn`

warning: trait objects without an explicit `dyn` are deprecated
 --> src/lib.rs:1:20
  |
1 | pub fn test(_: Box<dyn ::std::any::Any + 'static>) {
  |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn dyn ::std::any::Any + 'static`
  |
  = note: `#[warn(bare_trait_objects)]` on by default

error: aborting due to previous error

For more information about this error, try `rustc --explain E0433`.
error: Could not compile `playground`.

To learn more, run the command again with --verbose.
```

The code actually compiles with the 2018 edition.
The correct fix for 2015 edition code (which also works for edition 2018) is probably to include parens:
```rust
pub fn test(_: Box<dyn (::std::any::Any) + 'static>) {
}
```

I see two options:
1. Add parens to the help text so that it is correct in both editions.
2. Fix the help text only for the 2015 edition, because the suggested fix is already correct for the 2018 edition.

I personally prefer the first option for consistency with the existing help text and easier copy/pasting between editions.

## Meta

`rustc --version --verbose`:
```
rustc 1.38.0-nightly (c4715198b 2019-08-05)
binary: rustc
commit-hash: c4715198b50d1cdaad44b6e250844362b77dcdd7
commit-date: 2019-08-05
host: x86_64-pc-windows-gnu
release: 1.38.0-nightly
LLVM version: 9.0
```
Repository: TypeScript
Issue: String key-value type in basic types
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

typescript string key value type

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

Add an extra heavely used type - simple Object with string keys, used a lot as "primitive Map".
Tired writing `{ [ key: string ]: T }` each time.
Want `export type StrMap<T> = { [ key: string ]: T };` as one of basic types.
Keys in Objects are not too far from strings ( `Object.keys(_object).join('/')` ).
This is not fully related to https://github.com/microsoft/TypeScript/pull/26797 as it's a wider use case, IMHO.

<!-- A summary of what you'd like to see added or changed -->

## Use Cases

I'm using this type in a numerous projects in numerous modules.

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

<!-- Show how this would be used and what the behavior would be -->

## Checklist

My suggestion meets these guidelines:

* [ ] 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: godot
Issue: Dependency Manager doesn't validate types
Labels: bug,topic:editor,confirmed

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.1.1

**Issue description:**
When you edit scene's dependencies, you can put anything for anything and it won't complain.

**Steps to reproduce:**
1. Create a Sprite node with a texture
2. Close the scene
3. Either remove the texture and open scene or edit dependencies manually
4. Select another file for the texture, like, sound file lol
5. Confirm the changes
6. Godot doesn't see any problem, not even a warning appears

You can open the scene normally, but saving it will remove the wrong dependencies. You can however edit the dependencies again and assign correct resources.
Repository: flutter
Issue: Add "optimized with asserts" engine variants.
Labels: engine,P3,team-engine,triaged-engine

Currently, the unoptimized engine variants are used to distribute binaries for the Flutter tester that runs on the host. This is because of the desire to have an assertions enabled engine while running tests on the host. Since these use cases don't care about the actual optimizations being disabled for ease of debugging, the engine ought to have an "optimized with asserts" variant of the engine.
Repository: kubernetes
Issue: Automate skew testing for enabled/disabled alpha API fields
Labels: priority/important-soon,sig/api-machinery,sig/architecture,lifecycle/frozen

https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md#adding-unstable-features-to-stable-versions details how to add a new alpha field to an existing API, and enable it over multiple versions, ensuring:
* data is not dropped when running skewed API servers, or when disabling a previously-enabled feature gate
* persisted API objects are not treated as invalid by an n-1 API server

This is a particularly fragile/nuanced area, and is easy to get wrong (c.f. https://github.com/kubernetes/kubernetes/issues/80931, https://github.com/kubernetes/kubernetes/pull/80933, https://github.com/kubernetes/kubernetes/issues/72651).

Something like the following is required to ensure we don't regress in this area:
* Tag alpha fields using something like `// +alpha`
* In CI, detect alpha fields for served API types (via openapi or via struct traversal)
* For every alpha field, ensure there is a test fixture available for a valid object with and without the field
* Exercise all of the following cases (integration tests can start servers with all alpha features enabled, then restart them with alpha features disabled against the same etcd storage, to exercise how an API server behaves when it encounters alpha data persisted by a future beta API server)
    * feature enabled
        * creating object with alpha data is allowed and persisted
        * creating object without alpha data is allowed and persisted
        * update existing object without alpha data to one with alpha data is allowed and persisted (for objects that allow mutation)
        * update existing object with alpha data to one without alpha data is allowed and persisted (for objects that allow mutation)
    * feature disabled
        * creating object with alpha data is either rejected or persisted without the alpha data
        * creating object without alpha data is allowed and persisted
        * update existing object without alpha data to one with alpha data is either rejected or persisted without alpha data (for objects that allow mutation)
        * update existing object with alpha data to one without alpha data is allowed and persisted (for objects that allow mutation)

/sig api-machinery
/priority important-soon
Repository: pytorch
Issue: [JIT] Can't use ndim in script
Labels: oncall: jit,triaged,jit-backlog

```
import torch

def foo(x):
    if x.ndim > 3:
        return torch.neg(x)
    else:
        return x


x = torch.ones(3, 4)
x2 = torch.ones(3, 4, 5, 6)

print(foo(x))
print(foo(x2))

scripted = torch.jit.script(foo)
```

```
import torch

def foo(x):
    if x.ndim > 3:
        return torch.neg(x)
    else:
        return x


x = torch.ones(3, 4)
x2 = torch.ones(3, 4, 5, 6)

print(foo(x))
print(foo(x2))

scripted = torch.jit.script(foo)

```

cc @suo
Repository: godot
Issue: Sprite to CollisionPolygon2D improvement
Labels: enhancement,topic:core

**Godot version:**
3.2.dev

It would be useful if the Sprite to CollisionPolygon feature would also work for "closed rooms"
Example:
![image](https://user-images.githubusercontent.com/42905358/62573934-8310ce80-b897-11e9-8967-ad0b7c20879f.png)
As you can see, it's not working right now.

In addition, a "shrink" function would also be cool.
Repository: pytorch
Issue: Remove USE_C10D flag
Labels: oncall: distributed,module: build,triaged

After removing THD, `USE_C10D` flag is no longer useful (learned from @pietern ). We can now remove `USE_C10D` and keep `USE_DISTRIBUTED` to toggle distributed features.
Repository: go
Issue: proposal: review meeting minutes
Labels: Proposal,umbrella

The [proposal review group meets regularly](https://go.googlesource.com/proposal/+/master/README.md#proposal-review) (roughly weekly) to review pending proposal issues and move them along in the [proposal process](https://golang.org/s/proposal). 

Review consists primarily of checking that discussion is ongoing, commenting on issues to move discussion along, summarizing long discussions, CC’ing experts, and accepting or closing proposals when the discussion on the GitHub issue has reached a clear consensus about the outcome.

Review also includes closing proposals that are untenable (for example, because the changes are [backwards-incompatible](https://golang.org/doc/go1compat) or violate key design goals of the language or packages).

**This meta-issue records minutes of the proposal review meetings as issue comments, so that they can be cross-linked easily with the relevant issues. (This meta-issue is for minutes _only_; comments that are not meeting minutes will be deleted.)**
Repository: flutter
Issue: Should be able to limit max and min time in CupertinoDateTimePicker.
Labels: c: new feature,framework,f: cupertino,P3,team-design,triaged-design

The CupertinoDateTimePicker currently only supports limiting the maximum and minimum date. Sometimes you may also want to limit time. For instance, picking a DateTime before or after now. 

This should work in time mode and datetime mode.
Repository: go
Issue: wasm: add DWARF sections
Labels: NeedsInvestigation,FeatureRequest,arch-wasm

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.5 linux/amd64
</pre>

Output source maps for use with browser developer tools to enable simple step debugging inside browsers. Details of the spec can be found here: https://sourcemaps.info/spec.html