sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: GDScript: missing/possible constant folding
Labels: bug,topic:gdscript

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:** 5abb53be689475cf368b1d032bd3aecbe0f18051


**OS/device including version:** windows10


**Issue description:** 
Most of the method calls on builtin type constant could be resolved and const folded at compile time (example below), but currently they are being called at runtime.

![Capture](https://user-images.githubusercontent.com/41085900/91844090-75817000-ec74-11ea-9825-c6ee12121140.JPG)
Repository: rust
Issue: Tracking issue for future-incompatibility lint `const_evaluatable_unchecked`
Labels: A-lints,T-lang,T-compiler,C-future-incompatibility,C-tracking-issue,A-const-eval,A-const-generics

This is the **summary issue** for the `CONST_EVALUATABLE_UNCHECKED` future-compatibility warning. The goal of this page is to describe why this change was made and how you can fix code that is affected by it. It also provides a place to ask questions
or register a complaint if you feel the change should not be made. For more information on the policy around future-compatibility warnings, see our [breaking change policy guidelines](https://github.com/rust-lang/rfcs/blob/master/text/1122-language-semver.md).

### What is the warning for?

In version 1.43 we accidentally allowed some uses of generic parameters in repeat expressions. This has a few problems which are outlined in the [following document](https://hackmd.io/aZYPCFBBTyOdKTrqqy4Q3g?view) for now.

### When will this warning  become a hard error?

Most probably after [const well-formedness bounds](https://hackmd.io/OZG_XiLFRs2Xmw5s39jRzA?view) get stabilized, which is currently not yet implemented. There might be a subset of cases here which we can allow without needing any changes, but these require further careful consideration.

### How to fix this?

As we only allowed generic constants where the actual type did not matter, it should always be possible to replace the generic parameters with dummy types. For example `[0; std::mem::size_of::<*mut T>()]` can be changed to `[0; std::mem::size_of::<*mut ()>()]`.

**Please report your case here so we may take it into consideration when deciding on how to proceed.**
Repository: flutter
Issue: Tapping on a multi-line text box in a WKWebView makes the focus jump out of the webview and into Flutter
Labels: platform-ios,engine,a: accessibility,p: webview,package,customer: money (g3),P2,team-ios,triaged-ios

Internal: b/164972023

Unfortunately, there's no straight-forward repro for this. You can:

- Turn on voice over on iOS.
- Install an app that contains a Flutter scaffold + appbar with action buttons. The body of the scaffold should be webview_flutter plugin.
- Via webview_flutter plugin, open up a webpage which contains a multi-line text edit box.
- Focus on the text box via swipes.
- Double tap to activate the text box. You will notice the keyboard will show and the focus will jump to one of the action buttons in the appbar.

Expected behavior is that focus stays on the text box.
Repository: TypeScript
Issue: allowJs should default to true
Labels: Suggestion,Needs More Info,Breaking Change

allowJs should default to true. It works well enough that there aren't significant downsides to using it.

It does, however, change some settings, such as JS resolution in node_modules, I think. I need to list those here before going ahead with this proposal.
Repository: storybook
Issue: addon-controls - Disabling controls for a component does not disable them on docsPage
Labels: bug,addon: docs,addon: controls,block: argstable

**Describe the bug**
When I set the parameter for controls to disabled, the `Controls` tab disappears, but controls are still present on the `docsPage`.

**To Reproduce**
Steps to reproduce the behavior:

0. In a `*.stories.js` file (maybe MDX too, but I have only verified this on `*.stories.js`), set the export default as such:

```
export default {
  title: 'Components/MyNiceComponent',
  component: MyNiceComponent,
  parameters: {
    controls: {
      disabled: true,
    }
  }
}
```
1. Serve Storybook.
1. Navigate to `MyGreatComponent`
1. See that the `Controls` tab is no longer visible.
1. Click on the `Docs` tab.
1. See that the controls are still visible, and still function.

**Expected behavior**
When I disable controls for a component, I expect both the controls tab to disappear AND the controls column on the `docsPage` to disappear, as well.

**System:**
```
  System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
  Binaries:
    Node: 12.18.3 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.6 - /usr/local/bin/npm
  Browsers:
    Chrome: 85.0.4183.83
    Firefox: 80.0
    Safari: 13.1.2
```
Repository: electron
Issue: Document failureReasons of print callback
Labels: enhancement :sparkles:,documentation :notebook:

### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:** Electron 9

The possible failure reasons in the print callback ([docs](https://www.electronjs.org/docs/api/web-contents#contentsprintoptions-callback)) have no documentation. I think having a list of failures could help. I just noticed that I was getting a failure (and was showing an error popup) when the user cancelled out of the print dialog (failure reason: "cancelled"), which I didn't expect.
Repository: pytorch
Issue: Make it so that leading underscore operators are truly private and can be changed without worry for BC
Labels: triaged

Classically, the leading underscore was an indication that an API is private, and that it can refactored without worrying about backwards compatibility. Functions with leading underscore in `native_functions.yaml` don't have this property, as they may show up in traces and serialized format, making it bc breaking to refactor them.

It would be nice to figure out some way (or figure out some "even more private") designation by which we can guarantee that they actually are private and safe to change in this way.
Repository: rust
Issue: Typo'd Imports Result in Confusing Error Message
Labels: C-enhancement,A-diagnostics,A-resolve,T-compiler

I wanted to use the chrono crate, so I added it to Cargo.toml and put an import at the top of main.rs: `use chono::prelude::*`, where I typo`d chrono as chono. I got this error message:

```
error[E0433]: failed to resolve: use of undeclared type or module `chono`
 --> src/main.rs:2:5
  |
2 | use chono::prelude::*;
  |     ^^^^^ use of undeclared type or module `chono`
```

I didn't see the typo, and I was confused because I thought I must have put the import in the wrong place, because it said I hadn't declared the module that I was declaring on that line. I checked the docs for E0433, and in the example given someone had forgotten to import the module at all, so I was surprised to see that error on an import line.

### 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 --verbose`:
```
rustc 1.45.0
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.45.0
LLVM version: 10.0
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"TaKO8Ki"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: [Explorer Preview] Taskbar flashes when clicking into preview pane
Labels: Issue-Bug,Area-Quality,Status-In progress,Priority-3,Product-File Explorer

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

## ℹ Computer information

- PowerToys version: v0.20.1
- PowerToy Utility: File Explorer Add ons/Preview panes
- Running PowerToys as Admin: False
- Windows build number: 2004/Build 19041.450

## 📝 Provide detailed reproduction steps (if any)

1. Open explorer with preview pane
2. Select a markdown or SVG file
3. Click into the preview pane

### ✔️ Expected result

The display should not change (or ideally, a context menu would appear, or you could use the keyboard for selecting/scrolling, ...).

### ❌ Actual result

On every mouse click into the preview pane, the explorer window temporarily loses the focus, causing the title bar and the taskbar to flash.
Repository: vscode
Issue: Add streaming support in vscode
Labels: feature-request,editor-contrib,quick-open

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
this is a conceptually dup of https://github.com/microsoft/vscode/issues/20010. creating a new issue since the previous one is closed and that one is using custom streaming support rather than official streaming (partial results) support added to LSP.

Language Server Protocol has added partial results (streaming) supports (https://microsoft.github.io/language-server-protocol/specifications/specification-current/#partialResults) and VS has already added support for it.

As long as I know, the support is added to LSP since it was one of the top complaints from VS users, especially from people who have large codebases. 

For example, Finding Symbols from the workspace (WorkspaceSymbol) can easily take several seconds for big codebase and return a lot of results, Streaming takes the same amount of time to get full results, but most of the time, users get what they want before getting full results. so rather than users get the worst-case scenario all the time, streaming reduces the time users have to wait. 

VS has FULL SUPPORT for streaming. 
(Find all references, Document symbols, document highlights, Pull model diagnostics, workspace symbols and completion)

So they even support partial results (streaming) for document-level features such as "Document Symbol", "Document Highlights" and etc.

but, we (Python LS for vscode - Pylance) are not asking that much, but at least support for workspace-wide features such as "Workspace Symbol", "Find all references", "Call Hierarchy" and etc.

We do understand streaming (partial results) requires an incremental update of UI and that is not easy (flickering, ordering, sizing, grouping, etc issues). I believe VS had that issue as well when they started adding streaming supports (even before LSP), but once it is done, I believe they got a lot better at supporting large codebase.
Repository: vscode
Issue: Webview View onDidChangeVisibility fired when moving the view
Labels: bug,webview

Testing #105764

1. Use https://github.com/Microsoft/vscode-extension-samples/tree/master/webview-view-sample as starting point, add a visibility change listener
2. Drag the view from the explorer viewlet to the output panel, and then back

When dragging back into the activity bar, a visibility change event is fired on the view that is about to be disposed, which I didn't expect
Repository: vscode
Issue: Line height setting consistency
Labels: feature-request,markdown,debug-console

Issue Type: <b>Feature Request</b>

There are a few Line Height settings, but they're a little inconsistent.

Units:
editor.lineHeight and debug.console.lineHeight use pixels, whereas markdown.preview.lineHeight and terminal.integrated.lineHeight are decimal (ex: 1.6). Ideally all line heights should be decimal so that they would look consistent with different font sizes and/or on different systems which may have different pixel densities, etc.

Application:
The "Output" panel uses editor.lineHeight, but it would be better if it were in sync with the terminal. It should either have it's own setting or use terminal.integrated.lineHeight.


VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:09:08.021Z)
OS version: Darwin x64 20.0.0
Remote OS version: Linux x64 4.19.76-linuxkit


<!-- generated by issue reporter -->
Repository: rust
Issue: meta: Release tags show as "Unverified"
Labels: C-bug,T-release,A-meta

See for example the tag for 1.46.0:

![image](https://user-images.githubusercontent.com/37223377/91919368-94830080-ec7a-11ea-8853-6fe6fac1acb9.png)

Is there any way to remedy that? Likewise, the Git CLI shows:

```console
$ git tag -v 1.46.0
object 04488afe34512aa4c33566eb16d8c912a3ae04f9
type commit
tag 1.46.0
tagger Pietro Albini <pietro@pietroalbini.org> 1598541310 +0200

1.46.0 release
gpg: Signature made Thu Aug 27 08:15:27 2020 PDT
gpg:                using RSA key C13466B7E169A085188632165CB4A9347B3B09DC
gpg: Can't check signature: No public key
```

---

@rustbot modify labels: A-meta T-release C-bug
Repository: neovim
Issue: :put=execute fails when using double quotes instead of single quotes
Labels: enhancement,vimscript,lua

<!-- Before reporting: search existing issues and check the FAQ. -->

When calling the `execute` function using the expression register, using double quoted strings results in an error.
This error only occurs when using the ex command `:put=`; using `<c-r>=` seems to work fine with both double and single quoted strings.

- `nvim --version`:
- `vim -u DEFAULTS` (version: ) behaves differently?
- Operating system/version:
- Terminal name/version:
- `$TERM`:

```
NVIM v0.5.0-606-g409a1dcdc
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-5 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/travis/build/neovim/bot-ci/build/neovim/build/config -I/home/travis/build/neovim/bot-ci/build/neovim/src -I/home/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/include -I/home/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/home/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by travis@travis-job-683d4f49-1aef-4253-b2fc-0b52a0e7e071

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/home/travis/build/neovim/bot-ci/build/neovim/build/nvim.AppDir/usr/share/nvim
"
```

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
:put=execute("echo 5")
```

### Actual behaviour

```
E116: Invalid arguments for function execute
E15: Invalid expression: execute(
```

### Expected behaviour

```

5
```

I'll note that this bug also seems to be present on vanilla vim - I'd be happy to close this issue and open it on the vim repo if you feel that it is more relevant there.

```
VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)                                                                                                                          
Included patches: 1-2269 
```
Repository: ant-design
Issue: Tree组件draggable时,将移入非叶子节点时,非叶子节点的自动展开设为可配置
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
当父节点下的子节点很多时,自动展开会影响目录结构的展示。特别是当移动时,总会无意中滑到其他父节点,使用的时候总得小心翼翼的

### What does the proposed API look like?
```
<Tree
    dragEnterExpandParent
/>
```


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Bundling assets only on a specific platform (and remove assets on another platform)
Labels: c: new feature,tool,a: assets,a: images,c: proposal,P3,team-tool,triaged-tool

**NOTE: This is *not* a duplicate!** My previous issue https://github.com/flutter/flutter/issues/64993 is closed because of wrongly marked as a duplicate. Thus I have no choice but to create it again :/

(Why not duplicate of #8230 : I want to bundle those 1MB photos only in Android. Thus, in the final .ipa file of iOS, there are no such photos taking space.)

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

Hi thanks for the wonderful Flutter! I have some images (1.1MB) that should only be used in Android, not iOS. Therefore, I want to *remove* those images from the IPA file in iOS. I have read the official doc, but it did not mention things like this :/

**Expected results:** 

Give some options, such as (pubspec.yaml):
```
flutter:
  assets:
    android:
      - some_images_only_in_android/
    ios:
      - some_images_only_in_ios/
   all:
      - some_images_for_both/
```

**Actual results:** No such feature

<details>
  <summary>Logs</summary>

<!--
      Run your application with `flutter run --verbose` and attach all the
      log output below between the lines with the backticks. If there is an
      exception, please see if the error message includes enough information
      to explain how to solve the issue.
-->

```
```

<!--
     Run `flutter analyze` and attach any output of that command below.
     If there are any analysis errors, try resolving them before filing this issue.
-->

```
```

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
```

</details>
Repository: tensorflow
Issue: TensorArray issues in XLA
Labels: stat:awaiting tensorflower,type:bug,comp:xla,TF 2.11

<em>Please make sure that this is a bug. As per our
[GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md),
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template</em>

**System information**
- Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
- TensorFlow installed from (source or binary): binary
- TensorFlow version (use command below): 2.3 (exists in 1.5 as well)
- Python version: 3.7.6
- Bazel version (if compiling from source): NA
- GCC/Compiler version (if compiling from source): NA
- CUDA/cuDNN version: NA
- GPU model and memory: NA

You can collect some of this information using our environment capture
[script](https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh)
You can also obtain the TensorFlow version with:
1. TF 1.0: `python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"`
2. TF 2.0: `python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"`


**Describe the current behavior**
I know it was documented in xla official doc that xla doesn't support TensorArray with `dynamic_size=True`, however, I still ran into issues even w/ `dynamic_size=False`(it is default).

**Describe the expected behavior**
expect the tensorarray related stuffs are supported.

**Standalone code to reproduce the issue**
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.

```
import numpy as np
import tensorflow as tf
tf.compat.v1.enable_eager_execution()

@tf.function(experimental_compile=True)
def test_tensor_array_scatter_gather():
    dtype = "float32"
    t = tf.constant(np.array([[1.0], [2.0], [3.0]]).astype(dtype))
    scatter_indices = tf.constant([2, 1, 0])
    gather_indices = tf.constant([1, 2])
    ta1 = tf.TensorArray(dtype=dtype, size=3, infer_shape=True)
    ta2 = ta1.scatter(scatter_indices, t)
    t1 = ta2.gather(gather_indices)
    return t1

test_tensor_array_scatter_gather()
```

**Other info / logs** Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Repository: flutter
Issue: Let pigeon be pub global activated
Labels: c: new feature,package,c: proposal,team-ecosystem,p: pigeon,P3,triaged-ecosystem

There's nothing about pigeon that we need locally, either during run time or persistently in dev. We should be able to just pub global activate/run it since it's a one time fire and forget command.
Repository: go
Issue: cmd/compile: optimize redundant iface->iface type assertions
Labels: Performance,NeedsInvestigation,compiler/runtime

See https://go-review.googlesource.com/c/go/+/247478

For the real-world cases see https://github.com/VKCOM/noverify/blob/77ed62ed18e976f619031a5c828ea1f4b49c15ba/src/ir/irutil/clone.go#L219

That code was initially auto-generated, but it has a minor problem: it did `F().(T)` even in cases where `F()` already returns `T`. This is not a big problem, but since this optimization is so simple to implement in the compiler, maybe we can do it?

### What version of Go are you using (`go version`)?

<pre>
$ go version

go version devel +5c7748dc9d Mon Aug 10 23:44:58 2020 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/isharipov/.cache/go-build"
GOENV="/home/isharipov/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/isharipov/CODE/go/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/isharipov/CODE/go/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build237409555=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Compile this program:

```go
package foo

import "io"

func example1(x io.Reader) io.Reader {
	return x
}

func example2(x io.Reader) io.Reader {
	return x.(io.Reader)
}
```

### What did you expect to see?

Both `example1` and `example2` compiled to the same (efficient) code without type assertions.

### What did you see instead?

`example1` produces the type assertion `CALL runtime.assertI2I(SB)` (and a lot of code around it, as expected).