sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Can't get frameBuilder and loadingBuilder to work together
Labels: framework,d: api docs,a: images,has reproducible steps,P2,found in release: 3.7,found in release: 3.9,team-framework,triaged-framework

"loadingBuilder" works all the time (with or without frameBuilder) but "frameBuilder" works only if it is alone (i.e. commenting loadingBuilder out).

The documentation ( https://api.flutter.dev/flutter/widgets/Image/frameBuilder.html ) talks about "chaining" frameBuilder with loadingBuilder, it's not obvious that is something happens internally or it is something we have to consider.

```
Image.network(_imageUrl,
    height: 400,
    width: MediaQuery.of(context).size.width,
    fit: BoxFit.fitWidth,

    frameBuilder: (BuildContext context, Widget child, int frame, bool wasSynchronouslyLoaded) {
        if (wasSynchronouslyLoaded) return child;
        return AnimatedOpacity(
                opacity: frame == null ? 0 : 1,
                duration: Duration(seconds: 5),
                curve: Curves.easeOut,
                child: child,
            );
    },

    loadingBuilder: (BuildContext context, Widget child, ImageChunkEvent loadingProgress) {
        if (loadingProgress == null) return child;
        return Center(
            child: CircularProgressIndicator(
                        value: loadingProgress.expectedTotalBytes != null ?
                        loadingProgress.cumulativeBytesLoaded / loadingProgress.expectedTotalBytes :
                        null,
                    ),
                );
    },

    errorBuilder: (BuildContext context, Object exception, StackTrace stackTrace) {
        return Text('Failed to load image');
    },
),
```

### What Happens Exactly:

Case 1: When loadingBuilder is ALONE the CircularProgressIndicator is showing and the loading process is completed then the indicator disappears and the loaded image is showing without fading. (Perfect)

Case 2: When frameBuilder is ALONE the image takes its time to load (of course there is the indicator), then the loaded image is showing gradually as expected. (Perfect)

Case 3: When the frameBuilder and loadingBuilder BOTH are enabled, what happened is **CASE 1** exactly without any fading of the image. (Wrong)

### Expected Behavior:

The indicator is shown while the loading process is going, then disappear and the image is shown with a fading effect.

### The Question:

Is there is some bug or I'm missing something?
Repository: go
Issue: cmd/compile: negative shift check with trailing zeros
Labels: Performance,NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.2 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
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
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-build070218119=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Tried to remove the trailing bit in a loop.
A simple example of this pattern which counts each bit: https://play.golang.org/p/iQc490A5DRV
Same thing with instruction dump: https://godbolt.org/z/E54rY4

### What did you expect to see?

The compiler produces a tight loop, optimizing away the negative shift check.
It would be nice if the bounds check could be eliminated too, but that does not seem to be quite as straightforward to prove.

### What did you see instead?

There is a runtime check to see if `bits.TrailingZeros64` is negative.
Repository: deno
Issue: Streaming stdout output does not play nice with the REPL
Labels: bug,repl

Start something that will write to stdout/stderr in a repl

```typescript
$ deno
> setInterval(() => console.log(Math.random()), 1000);
```

And try to edit a line, not a good experience.

Problem is that rustyline does not give us any control of any kind of writer or access to the line buffer. So we can't do anything about it until https://github.com/kkawakam/rustyline/pull/235 or a variant of it lands. Or we move away from rustyline, linefeed seems to handle this well.
Repository: flutter
Issue: [a11y] Set semantics sort key order and value on embedder ax bridge nodes
Labels: c: new feature,engine,a: accessibility,customer: dream (g3),P2,team-engine,triaged-engine

https://b.corp.google.com/issues/170206566. May or may not require engine support. Keep details on the upstream, bug, please.
Repository: flutter
Issue: [a11y] Hit test not generating hover events for top nav elements
Labels: engine,a: accessibility,customer: dream (g3),P2,team-engine,triaged-engine

https://b.corp.google.com/issues/170969395.
Repository: PowerToys
Issue: Add Quick tasks to Start Menu and task bar
Labels: Idea-Enhancement,Product-Tweak UI Design,Product-Settings,Area-Setup/Install,Area-Runner

## 📝 Provide a description of the new feature

I would like to suggest to add quick tasks to the shortcut in Start Menu for the PowerToys icon, for quick acces to toys like Color Picker, FZ Editor or other (future) things. _suggestions are welcome_
Existing examples:

![image](https://user-images.githubusercontent.com/65828559/96738882-7bb3e300-13bf-11eb-8eab-6a68882e4524.png)
_Firefox_

![image](https://user-images.githubusercontent.com/65828559/96738848-72c31180-13bf-11eb-9663-1336581f8855.png)
_CCleaner_

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: pytorch
Issue: Suggestion: link individual APIs in docs with tutorials that use them
Labels: module: docs,triaged

## 📚 Documentation

It'd be pretty useful to link each function in pytorch docs to example usages of it in tutorials or in other curated sample stuff (e.g. maybe some TorchHub models or ipython notebooks). These links can be probably auto-generated if we run tutorials code with monkey-patched PyTorch that keeps track of which APIs has been invoked.

The inspiration from TF (see the "Used in" section): https://www.tensorflow.org/api_docs/python/tf/nest/map_structure#used-in-the-notebooks_1

cc @jlin27 @mruberry
Repository: PowerToys
Issue: Replace Thread.Sleep with task.Delay
Labels: Help Wanted,Product-PowerToys Run,Area-Tests,Area-Quality,Cost-Small,Product-Color Picker

### Performance Improvement of PT Run

Similar to PR #7401, replacing `Thread.Sleep` with `Task.Delay` throughout the codebase would improve the performance of PT Run as `Thread.Sleep` blocks the thread that it is called on whereas `Task.Delay` uses a timer instead and schedules a thread to resume work after the interval has passed. This does not block the thread.
Repository: flutter
Issue: Apps don't repaint on Linux when raised if they haven't been resized (noticeable on ratpoison)
Labels: engine,platform-linux,a: desktop,P2,team-linux,triaged-linux

STEPS TO REPRODUCE:
1. Use ratpoison.
2. Open a Flutter application.
3. Switch to another window in the same tab as the Flutter application.
4. Switch back to the Flutter application.

The application is black except for the frame.
Repository: create-react-app
Issue: production build doesn't work while develpment build do 
Labels: stale,needs triage,issue: bug report

i have this func that simply calculate ax²+bx+c 
```js
handleSubmit = (event) => {
    event.preventDefault();
    let a = this.state.a;
    let b = this.state.b;
    let c = this.state.c;
    let ac4 = a * 4 * c;
    let delta = b * b - ac4;
    let result = {};
    if (delta < 0) result = { x1: "imag.!", x2: "imag.!" };
    else {
      delta = delta ** (1 / 2);
      a = 2 * a;
      let x1 = (-b - delta) / a;
      let x2 = (-b + delta) / a;
      result = { x1, x2 };
    }
```
but with the production build it looks like this 
```js
            n.handleSubmit = function(e) {
                e.preventDefault();
                var t = n.state.a
                  , l = n.state.b
                  , r = l * l - 4 * t * n.state.c
                  , o = {};
                r < 0 ? o = {
                    x1: "imag.!",
                    x2: "imag.!"
                } : o = {
                    x1: (-l - (r = a.pow(r, .5))) / (t *= 2),
                    x2: (-l + r) / t
                };
```
and while submitting i get this error: `a.pow is not a function` 
and the `a` is clearly not defined inside this function
Repository: storybook
Issue: Vue decorators not reacting to toolbar in Canvas
Labels: bug,vue,has workaround,addon: toolbars,args

**Describe the bug**
I have setup a toolbar and global decorator for changing a class to show theme changes. When I select an option from the toolbar, in Canvas, the session storage changes, if I console.log it it changes but the class doesn't change. It does work in Docs tab and if I select a different story. I'm guessing because it re-renders the DOM.

My example scenario is switching a light and dark theme class in a decorator using toolbar and globals.

**To Reproduce**
Example repo: https://github.com/andywd7/storybook
Example demo: https://trusting-montalcini-282027.netlify.app

**Expected behavior**
I would expect the class in the decorator to change.

**System**
```
Environment Info:

  System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
    npm: 6.14.8 - ~/.nvm/versions/node/v14.4.0/bin/npm
  Browsers:
    Chrome: 86.0.4240.80
    Safari: 14.0
  npmPackages:
    @storybook/addon-a11y: ^6.0.26 => 6.0.26 
    @storybook/addon-actions: ^6.0.26 => 6.0.26 
    @storybook/addon-cssresources: ^6.0.26 => 6.0.26 
    @storybook/addon-essentials: ^6.0.26 => 6.0.26 
    @storybook/addon-links: ^6.0.26 => 6.0.26 
    @storybook/vue: ^6.0.26 => 6.0.26
```
Repository: material-ui
Issue: [Select] MenuItem is missing docs for the value prop
Labels: docs,component: select

<!-- Provide a general summary of the issue in the Title above -->
The [MenuItem](https://material-ui.com/api/menu-item/#menuitem-api) docs don't mention the `value` prop at all, yet it is used on the `Select` `multiple` example in the docs.  In fact, pairing down the example [it works fine](https://codesandbox.io/s/material-demo-forked-5upc3?file=/demo.js)

I'm not getting the same effect in my application so I went to check the docs to see what happens if its an object and not a string and...no documentation.

Not filling out the rest of the template because this is a documentation bug, not a code bug. 

Thanks for the cool library!


<!-- Checked checkbox should look like this: [x] -->

- [X] The issue is present in the latest release.
- [X] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
Repository: rust
Issue: Improve error for missing braces in const block
Labels: C-enhancement,A-diagnostics,A-parser,T-compiler,D-confusing,F-inline_const

Someone may try to write code like this ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=14c47489294acc468ca46b036fef4086)):

```rust
#![allow(incomplete_features)]
#![feature(inline_const)]

fn foo() {
    let x = 2;
    match x {
        const 2 => {}
    }
}
```

Yet this produces these misleading errors:

```rust
   Compiling playground v0.0.1 (/playground)
error: expected identifier, found keyword `const`
 --> src/lib.rs:7:9
  |
7 |         const 2 => {}
  |         ^^^^^ expected identifier, found keyword

error: expected one of `=>`, `@`, `if`, or `|`, found `2`
 --> src/lib.rs:7:15
  |
7 |         const 2 => {}
  |               ^ expected one of `=>`, `@`, `if`, or `|`

error: aborting due to 2 previous errors

error: could not compile `playground`

To learn more, run the command again with --verbose.
```

---

Another example ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=b4eaa0866c85e582f1b7770910764a82)):

```rust
#![allow(incomplete_features)]
#![feature(inline_const)]

fn foo() {
    let x = const 2;
}
```

Error:

```rust
   Compiling playground v0.0.1 (/playground)
error: expected expression, found keyword `const`
 --> src/lib.rs:5:13
  |
5 |     let x = const 2;
  |             ^^^^^ expected expression

error: aborting due to previous error

error: could not compile `playground`

To learn more, run the command again with --verbose.
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: rust
Issue: Improve errors for async block in pattern
Labels: C-enhancement,A-diagnostics,A-parser,T-compiler,A-async-await,D-confusing,D-verbose,A-patterns

Not a big issue since I don't think someone would think to do this, but it produces 4 errors that are a bit misleading:

```rust
fn foo() {
    let x = 2;
    match x {
        async { 2 } => {}
    }
}
```

([Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=b6c8dbaa3300fa65539de3c9e6c0b27c))

Errors:

```rust
   Compiling playground v0.0.1 (/playground)
error: expected identifier, found keyword `async`
 --> src/lib.rs:7:9
  |
7 |         async { 2 } => {}
  |         ^^^^^ expected identifier, found keyword
  |
help: you can escape reserved keywords to use them as identifiers
  |
7 |         r#async { 2 } => {}
  |         ^^^^^^^

error: expected identifier, found `2`
 --> src/lib.rs:7:17
  |
7 |         async { 2 } => {}
  |         -----   ^ expected identifier
  |         |
  |         while parsing the fields for this pattern

error[E0422]: cannot find struct, variant or union type `r#async` in this scope
 --> src/lib.rs:7:9
  |
7 |         async { 2 } => {}
  |         ^^^^^ not found in this scope

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0422`.
error: could not compile `playground`

To learn more, run the command again with --verbose.
```

This error seems the weirdest to me:

```rust
error[E0422]: cannot find struct, variant or union type `r#async` in this scope
 --> src/lib.rs:7:9
  |
7 |         async { 2 } => {}
  |         ^^^^^ not found in this scope
```
Repository: flutter
Issue: [LUCI] Recipe should rebase PRs on tip of tree
Labels: team-infra,P3,triaged-infra

There have been several issues that are hard to diagnose because LUCI is currently cloning the PR and testing it.

If that branch isn't up to date, it may not be running the most recent tests.

https://github.com/flutter/cocoon/pull/973 took several tries and weird errors until we realized the branch was using an older upstream sha.
Repository: flutter
Issue: Make package:web_installers accessible from flutter/flutter
Labels: team,platform-web,P3,team-web,triaged-web

`package:web_installers` is our standard package for installing and manipulating webdrivers. However, the package only exists on Github. There's no way to add a dependency on it using flutter/flutter's standards means. Therefore some of the functionality is duplicated in flutter/flutter.

This is not currently blocking anything. It's more of a code health issue.

/cc @nturgut
Repository: godot
Issue: Edits in a new built-in script are lost
Labels: bug,topic:gdscript,topic:editor

**Godot version:**
Godot Engine v3.2.3.stable.official

**OS/device including version:**
Windows 10

**Issue description:**
Creating a builtin script, editing it and saving may not actually save the edited script; This seems to happen after deleting a scene or detaching a builtin script. The editor does not switch to the new script after it is created.

**Steps to reproduce:**
Create a new project, add a spatial node and save the scene
Create a builtin script for the node and then detach it
Create again a new builtin script for the node, edit the script and save and close the scene
Reopen the scene and open the script we edited - it should be blank


The same issue can happen if the scene is closed instead:
Create a new scene, add a spatial node
Create a builtin script, edit it and close the scene (do not save)
Create again a new spatial root node and add a builtin script to it - the previous script should be open instead of a new one
Repository: pytorch
Issue: error in bazel build //...
Labels: module: build,triaged,module: bazel

## 🐛 Bug

`bazel build //...` fails with an error in `XNNPACK`.

## To Reproduce

Steps to reproduce the behavior:

1. `bazel build //...`

```
$ bazel build //...
ERROR: /home/mbm/ATG/tmp/pytorch/third_party/XNNPACK/BUILD.bazel:1914:1: no such package '@clog//': The repository '@clog' could not be resolved and referenced by '//third_party/XNNPACK:XNNPACK'
ERROR: Analysis of target '//third_party/XNNPACK:subgraph_size_test' failed; build aborted: no such package '@clog//': The repository '@clog' could not be resolved
INFO: Elapsed time: 1.222s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (24 packages loaded, 30 targets configured)
    Fetching @com_google_googletest; fetching
```

## Expected behavior

Expect to be able to build an entire project without errors.

## Environment

 - PyTorch Version (e.g., 1.0): current `master` f83cf2dab39bae12eeb95a2fe0b7e54db4571713
 - OS: Linux
 - How you installed PyTorch: build from source with `bazel`
 - Build command you used: `bazel build //:torch`
 - Python version: 3.9.0
 - CUDA/cuDNN version:
 - GPU models and configuration:
 - Any other relevant information:

## Additional context

I believe the problem could be that `XNNPACK` refers _back_ to the main repository here:

https://github.com/google/XNNPACK/blob/214326714cdcd106ec02087ce4cbcb1cf42bafdc/WORKSPACE#L61

The syntax `@//third_party:clog.BUILD` looks for `third_party/clog.BUILD` in the pytorch repository. I expect `//third_party:clog.BUILD` was intended.

See https://docs.bazel.build/versions/master/build-ref.html#labels


cc @malfet @seemethere @walterddr
Repository: flutter
Issue: [SelectableText] inconsistent selection background color between different character encoding
Labels: a: text input,framework,f: material design,f: selection,team-design,triaged-design

<!-- 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
Select text when text containing English and Chinese, the selection color isn't cover the all the text while part of it is smaller if English is selected while another part of it is bigger if Chinese is selected.

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->

**Expected results:** <!-- what did you want to see? -->
![image](https://user-images.githubusercontent.com/13610283/96661703-4ab3be00-137f-11eb-9bc7-5005f49e89ab.png)


**Actual results:** <!-- what did you see? -->
![image](https://user-images.githubusercontent.com/13610283/96661572-f1e42580-137e-11eb-822a-38c470027c5a.png)
Repository: react
Issue: Bug: onCompositionEnd not called
Labels: Component: DOM,Status: Unconfirmed,Type: Needs Investigation

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:  16.7.0
OS: Window 10


## Steps To Reproduce

1. Switch input method to Chinese
2. Type 1 to the input

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:  https://codepen.io/Eoyd/pen/KKMgMzz?editors=0011

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
When setting the formatted value in the render function, if the formatted return is a string, the combined input will not trigger onCompositionEnd

## The expected behavior
onCompositionEnd should be called
Repository: go
Issue: x/tools/gopls: add a mechanism for marking a setting deprecated in documentation
Labels: Documentation,NeedsInvestigation,gopls,Tools

We currently have a way of notifying users that they are using a deprecated setting, but it would also be nice to mark the deprecation in the documentation. This way, we could surface the deprecation in the `package.json` and smoothly transition users off of an outdated setting.

/cc @heschik @hyangah 

Edit: This would be doable by adding a struct tag that sets a field's status to "deprecated". We could then use reflection to check the field's status when setting it. However, we should probably only do this once we set all options using reflection, which is a big enough change that we shouldn't do it until after February.
Repository: go
Issue: cmd/compile: inconsistent error message when identifier begins with invalid character
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?
go version go1.15.2 darwin/amd64
### What did you do?
I tried to compile the following program: https://play.golang.org/p/379msfdOuwi
```Go
package main

func main() {
	var 3x = 3
	3x := 3  
	var $x = 3
	$x := 3
}
```
### What did you expect to see?
```
./prog.go:4:6: syntax error: unexpected literal 3, expecting name
./prog.go:5:3: syntax error: unexpected literal 3, expecting name
./prog.go:6:6: invalid character U+0024 '$'
./prog.go:7:2: invalid character U+0024 '$'
```

### What did you see instead?
```
./prog.go:4:6: syntax error: unexpected literal 3, expecting name
./prog.go:5:3: syntax error: unexpected x at end of statement
./prog.go:6:6: invalid character U+0024 '$'
./prog.go:7:2: invalid character U+0024 '$'
./prog.go:7:5: no new variables on left side of :=
```