sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: props or state change  Input Component placeholder able change but rule text unable change
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.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-pyvl8?file=/index.js)

### Steps to reproduce
1,  Click to link https://codesandbox.io/s/antd-reproduction-template-forked-pyvl8?file=/index.js
2,  onclick submit view frist input placeholder and rule (input epmty!!)
3, onclik change state button 
4, now input placeholder change, but rule not!!


### What is expected?
state props change input rule warning change

### What is actually happening?
state props change input rule warning not change

| Environment | Info |
|---|---|
| antd | 4.7.0 |
| React | 16.13,1 |
| System | win |
| Browser | chrome |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: excalidraw
Issue: Native Tabbed mode in standalone Excalidraw PWA window
Labels: enhancement,pwa

See this [Web App Manifest Issue](https://github.com/w3c/manifest/issues/737) for more background on this feature and note that this feature is distinct from what is being proposed in #1543. Think of #1543 more like the same file, but logically split into scenes (like the tabs in a spreadsheet), whereas the present #2597 is for dealing with multiple files in the same application window, think the editor tabs in VS Code. 

(I'm volunteering myself to work on what I propose here.)
Repository: opencv
Issue: Subset of Fluid/NV12PlusResizeTest.Test fails on arm64
Labels: bug,platform: linux,platform: arm,category: g-api / gapi

##### System information (version)
- OpenCV => 4.5.1-pre (git 46e275dfe4616b07cd2492c17698d1a0be0aa6df )
- Operating System / Platform => Ubuntu 20.04, arm64-v8a
- Compiler => GCC 9.3

Hardware:
```
--   CPU/HW features:
--     Baseline:                    NEON FP16
```

##### Detailed description

Full list of cases and their status:


Test/0 | 1 ms | Failed
-- | -- | --
Test/1 | 1 ms | Passed
Test/10 | 32 ms | Failed
Test/11 | 31 ms | Failed
Test/12 | 2 ms | Failed
Test/13 | 3 ms | Failed
Test/14 | 3 ms | Failed
Test/15 | 3 ms | Failed
Test/2 | 1 ms | Passed
Test/3 | 2 ms | Failed
Test/4 | 1 ms | Failed
Test/5 | 1 ms | Failed
Test/6 | 2 ms | Failed
Test/7 | 1 ms | Failed
Test/8 | 34 ms | Failed
Test/9 | 31 ms | Failed

Console output:
```
/home/opencv-cn/slave/workspace/nightly-master/ubuntu-20.04-arm64/opencv/modules/gapi/test/gapi_fluid_resize_test.cpp:753
Expected equality of these values:
  0
  cvtest::norm(out_mat(roi), out_mat_ocv(roi), NORM_INF)
    Which is: 2
```

##### Issue submission checklist

 - [ ] I report the issue, it's not a question
   <!--
   OpenCV team works with answers.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with question without real issue statement will be
   closed.
   -->
 - [ ] I checked the problem with documentation, FAQ, open issues,
       answers.opencv.org, Stack Overflow, etc and have not found solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://answers.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [ ] I updated to latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [ ] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as archive to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
Repository: excalidraw
Issue: Stroke width vs. stroke style
Labels: enhancement,discussion

<img src="https://user-images.githubusercontent.com/2797254/102199593-17dfff00-3ec4-11eb-9114-176acd020173.png" width="300" />

While "Stroke width" changes both the border stroke and the texture stroke, "Stroke style" only changes the border stroke. So, _maybe_

**Stroke width
Border stroke style**

or

**Border and texture stroke width
Border stroke style**

or

**Stroke width (border and texture)
Stroke style (border)**

might help the user to better predict the result of selecting each tool option.

<img src="https://user-images.githubusercontent.com/2797254/102199206-a011d480-3ec3-11eb-8254-80b6aef33c50.png" width="500" />
Repository: storybook
Issue: Perf: Set sideEffects false for packages
Labels: maintenance,performance issue

Most of our libraries don't have side effects, and if we set `sideEffects` to false, Webpack can optimize it. More info: https://stackoverflow.com/questions/49160752/what-does-webpack-4-expect-from-a-package-with-sideeffects-false
Repository: flutter
Issue: Add IndexedSemantics support on pageview
Labels: framework,a: accessibility,f: scrolling,c: proposal,P3,team-framework,triaged-framework

<!-- 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
-->

## Use case

Currently, the only way to tell a user on which page they are within a PageView is to manually annotate each of the pages with a label. This provides a somewhat suboptimal experience when compared with the support included in for example ListView, which allows you to pass the actual indices to the accessibility layers directly, instead of needing to encapsulate them with explaining text.

## Proposal

Allow use of IndexedSemantics with PageView, enabled by either telling the widget to create indices for each child, or manually providing the child count and encapsulating each relevant child in an IndexedSemantics widget.

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: deno
Issue: Normalize color palette across subcommands and tools
Labels: cli,suggestion

Each subcommand has their own palette to varying degrees; doc, test coverage and the repl for example do not agree on how to syntax highlight and it would be better if they were consistent.
Repository: rust
Issue: [ER] std::mem::array_len
Labels: A-type-system,T-lang,C-feature-request,T-types

This is an Enhancement Request, I'd like this since years. I'd like a const function (like `std::mem::size_of`) that given an array returns its length:

```rust
fn main() {
    use std::mem::array_len;
    let a = [0_u32; 10];
    let b = [0; array_len::<&a>()];
}
```

Note that in this code the array 'a' isn't a const, otherwise this suffices:

```rust
const fn array_len<T, const N: usize>(_: &[T; N]) -> usize { N }
```

The purporse of array_len is to avoid defining a third usize constant LEN when you only want two arrays to have the same length and you want DRY code.

In D language you don't need such special function because the normal `.length` attribute of arrays and vectors is usable in a constant context too:

```d
void main() {
    int[5] a; // An array with length fixed at compile-time, like a Rust array.
    int[a.length] b; // Another one.
}
```

But I think we can't have `array::len` const in Rust.
Repository: rust
Issue: Static lifetimes and variance: Associated const treated differently (and perhaps incorrectly?)
Labels: A-type-system,A-lifetimes,A-associated-items,T-lang,T-compiler,C-bug,A-variance,T-types

If the line after `this does not work` is commented out, _the remaining code does compile_.
If there is any other reason why the `const` can’t work, while the function can, then the error message is misleading.

```rust
struct SomethingStatic<T: 'static>(T);

trait Foo<'a> {
    // this does work
    const FUN: fn(&&'a ());
}
trait Bar<T /* <- not 'static */> {
    // this does work
    const FUN: fn(&T);
}

trait Qux<'a> {
    // this does work
    fn fun() -> SomethingStatic<fn(&&'a ())>;
    // only this does not work:
    const FUN: SomethingStatic<fn(&&'a ())>;
}
```

([Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=1beab466545fa5be643c715cf7bfabc5))

Errors:

```
   Compiling playground v0.0.1 (/playground)
error[E0477]: the type `for<'r> fn(&'r &'a ())` does not fulfill the required lifetime
  --> src/lib.rs:14:5
   |
17 |     const FUN: SomethingStatic<fn(&&'a ())>;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: type must satisfy the static lifetime

error: aborting due to previous error

For more information about this error, try `rustc --explain E0477`.
error: could not compile `playground`

To learn more, run the command again with --verbose.

```
Applies to stable as well as the current nightly (`1.50.0-nightly (fa4163942 2020-12-14)`)

[⟶ originally from this discussion on URLO](https://users.rust-lang.org/t/lifetimes-why-this-code-doesnt-compile/52622)

@rustbot modify labels: C-bug, T-lang, T-compiler, A-associated-items, A-lifetimes, A-typesystem
Repository: go
Issue: x/tools/cmd/goimports: adds flag control to delete extra blank lines before grouping
Labels: NeedsInvestigation,Tools

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.2 darwin/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="/Users/chenglong/Library/Caches/go-build"
GOENV="/Users/chenglong/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/chenglong/go/pkg/mod"
GONOPROXY="tkestack.io,k8s.io,git.code.oa.com"
GONOSUMDB="tkestack.io,k8s.io,git.code.oa.com"
GOOS="darwin"
GOPATH="/Users/chenglong/go"
GOPRIVATE="tkestack.io,k8s.io,git.code.oa.com"
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/local/Cellar/go/1.15.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/20/n4jpmhjs0hd9hjxg80yr2nww0000gn/T/go-build993050189=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

use goimports to format file.

current:
![image](https://user-images.githubusercontent.com/1881126/102221913-b64c7e80-3f1d-11eb-840a-79b4aacb28ea.png)

### What did you expect to see?

Blank lines cause incorrect grouping. These blank lines are automatically generated by IDE.

### What did you see instead?

Delete extra blank lines and regroup:
![image](https://user-images.githubusercontent.com/1881126/102222304-383ca780-3f1e-11eb-901f-ddc849d33cf8.png)
Repository: godot
Issue: Graphical glitch with two directional lights and ViewportContainer (background visible with inverted colors)
Labels: bug,topic:rendering

I don't know the term for this specific glitch, so if someone does know please amend the title.

Possibly related: #43760

**Godot version:**
```
3.2.3.stable.custom_build.662455ee8
```

**OS/device including version:**
```
Linux pc 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux

GeForce GTX 1060 6GB
NVIDIA-SMI 418.152.00   Driver Version: 418.152.00   CUDA Version: N/A 
```

**Issue description:**
If you have a mesh in a `ViewportContainer` and two (directional?) lights, the background is visible through the mesh with inverted colors. The strength of the effect seems to depend on the angle of a face to the camera. This does not happen when using GLES2.

![Screenshot_2020-12-14_22-47-49](https://user-images.githubusercontent.com/17316999/102223084-89c84080-3ee4-11eb-84da-08c9a618ad96.png)

**Steps to reproduce:**
- Create a project with **GLES3**
- Add a `Camera` with Cull Mask set to only layer 1.
- Add a `ViewportContainer`
  - Add a `Viewport` as a child with Transparent Bg enabled.
    - Add a `Camera` with Cull Mask set to only layer 2.
      - Add a `MeshInstance` with any mesh and Layer Mask set to layer 2 (and ensure it is visible for the second camera).
- Add **two** `DirectionalLight`s. Their orientation doesn't matter.
- (Optional) Add a `MeshInstance` with any mesh and Layer Mask set to layer 1

**Minimal reproduction project:**

[viewport_inverted_bg_color.zip](https://github.com/godotengine/godot/files/5696340/viewport_inverted_bg_color.zip)
Repository: go
Issue: mime/quotedprintable: support message with long lines
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.5 darwin/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

</pre></details>

### What did you do?

Tried to parse message which does not follow RFC to not having longer than 76 characters (has 4953 characters). Currently, quotedprintable is using bufio.Reader which fails on line longer than ~4k characters because of the bufio.Rader default limit.

### What did you expect to see?

Even though it's not a message following RFC, it's better to parse it anyway as there is no reason not to support it.

### What did you see instead?

Message cannot be parsed.
Repository: pytorch
Issue: PyTorch 1.7.1 on (macOS/python 3.9/conda) links libtorch_global_deps.dylib with libomp.dylib instead of libiomp5.dylib
Labels: module: binaries,module: build,triaged,module: macos

install PT 1.7.1 via conda(!!!) with python 3.9 and 3.8 and checked `otool -L libtorch_global_deps.dylib`:

with python 3.8 it has @rpath/libiomp5.dylib and libiomp5.dylib exists because was [copied to the wheel package on OS X](https://github.com/pytorch/pytorch/blob/ff097299aeb4a7e2902000c70992f0abefb8a74e/setup.py#L375-L408)
with python 3.9 it has @rpath/libomp.dylib but [libomp.dylib doesn't exist](https://app.circleci.com/pipelines/github/pytorch/csprng/810/workflows/7f1fe1a0-e583-4acf-9333-05521e2a8759/jobs/38913)

cc @ezyang @seemethere @malfet @walterddr
Repository: pytorch
Issue: Bitcode enable for iOS
Labels: module: binaries,triaged,module: ios

## 🚀 Feature
Enable bitcode.
To be able to use bitcode to distribute iOS apps with pytorch lib.
To be able to create app with pytorch lib for watchOS and tvOS.

## Motivation
Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store.

For iOS apps, bitcode is the default, but optional. For watchOS and tvOS apps, bitcode is required. If you provide bitcode, all apps and frameworks in the app bundle (all targets in the project) need to include bitcode.

[Apple Documentation](https://help.apple.com/xcode/mac/current/#/devbbdc5ce4f)

## Pitch
I would like to create and distribute an app for watchOS.

Furthermore, my app require bitcode to be enable to pass through security process before sending it to the store :
https://help.veracode.com/r/compilation_ios




cc @ezyang @seemethere @malfet @walterddr
Repository: terminal
Issue: "Toast" notifications
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

An idea I've been toying around with for a while, but haven't formalized. 

["Toasts"](https://developer.android.com/guide/topics/ui/notifiers/toasts) are an Android UI paradigm - a transient notification that can be displayed to the user. These toasts can't be interacted with, and dismiss themselves after a brief timeout.
![image](https://user-images.githubusercontent.com/18356694/102251267-32b57200-3eca-11eb-9c1b-dc64e98a28a3.png)

WinUI doesn't have Toasts, but it does have the `TeachingTip`. in the future, WinUI is planning on building this auto-dismiss behavior into the `TeachingTip` itself, but we're impatient.
![image](https://user-images.githubusercontent.com/18356694/102251368-51b40400-3eca-11eb-9762-75012bc038db.png)

Use cases that would be good for this:
* [ ] **A.** #8514 - When we open a tab in another elevated window, it might be nice to display a toast to the user "A new tab was created in an elevated window"
* [x] **B.** As mentioned in #8135: we'll need a little UI element for displaying the Window IDs/names. Maybe a window-level toast would work?
* [ ] **C.** Similar to the above, inspired by #5803, #5464, #8183: display a toast in each pane showing the Pane IDs
  - #10708
* [ ] **D.** inspired by discussion in #8330: in that PR, we'll fall back to the profile's `startingDirectory` if the provided directory doesn't exist. In that case, we could display a toast to the user as well. 
* [ ] **E.** Feature Request: Show terminal size when resizing the window #2833
  - Maybe? This might not be the best example for a toast. 
* [ ] **F.** https://github.com/microsoft/terminal/pull/14425#issuecomment-1329164354 - display the notification as a Toast, instead of an OS-level notification
* [ ] #17561: We thought about it, but also these Toasts are FAR too heavy for as lightweight a thing as we need for that. 

From the above, there are two kinds of scenarios where we want Toasts: control-level and window-level. 
* A, B, D are all window-level. There's one Toast visible, at the window level. Changing tabs wouldn't hide this toast (this is important for D, where the toast would be fired as the new tab is opening, and we probably want the toast to persist in both the original tab and the tab that's created).
* C is a control-level toast. Each pane would display a toast. Changing tabs would hide these toasts.

I'm not prescribing any interactable UI in these toasts, but `TeachingTips` do allow buttons and other rich content. 


I'm sure there are other things we could do too. This issue is so I don't lose track of the possible scenarios. 

Other things:
* [x] Something like "Unable to rename window. Another window with that name already exists."
Repository: pytorch
Issue: Add global gradcheck setting
Labels: module: autograd,triaged,better-engineering

## 🚀 Feature

There as two main use cases for gradcheck:
- User facing API to help them check their custom autograd
- Our own testing that use it to check that all our submodules work well with autograd

The problem that we encounter today while adding new features such as vmap and forward AD is that while we want the user facing API to remain stable to avoid breaking user code, we would like the internal testing to test these by default to make sure that functions we provide work with all these gradient-computing features.

## Motivation

We want to avoid having to modify each call to gradcheck in our test suite when we add a new feature.
We also want to make sure new test writer get this by default and it is hard for them to forget to test these.

## Pitch

Provide a global config for gradcheck that allows to change the default to the `gradcheck` and `gradgradcheck` functions.
It will consist in:
- Add a config to gradcheck submodule with all the relevant settings.
- Add API to set these settings easily for test. Also a decorator-based setting to disable them (to easily disable some settings for a single test).
- Changing the API of gradcheck and gradgradcheck to take `None` as default that will translate to whatever is currently in the global config if no value is passed.
- Update our default Test class to set the right setting on setUp and restore the current state in onExit.

## Alternatives

Alternative would be to change all the calls we have in our test suite, but that wouldn't cover new tests being written.
Changing the default of all gradcheck is possible as well but would lead to BC-breaking behavior for users which is not great.


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved