sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vue
Issue: Strange ssr behavior in v-for loop with if-else and v-text
Labels: bug,has workaround,feat:ssr

### Version
2.6.11

### Reproduction link
[https://github.com/TrueCarry/linktest](https://github.com/TrueCarry/linktest)







### Steps to reproduce
Run server, open localhost:8080. Problem is in components/textWrapper.vue file. I've used some vue ssr template and removed almost everything unneeded. Same error as before.

### What is expected?
ssr and client side versions are the same. It works if we don't use v-text on span. I changed it to v-text1, to test.
No hydration errors with v-text1
![image](https://user-images.githubusercontent.com/5431520/99122979-58700280-2610-11eb-8b5c-0952d78fe951.png)


### What is actually happening?
Server doesn't render custom element.
Console output: 
![image](https://user-images.githubusercontent.com/5431520/99123015-70e01d00-2610-11eb-8196-28840adbdfc8.png)
Server generated html:
![image](https://user-images.githubusercontent.com/5431520/99123039-7b9ab200-2610-11eb-85e4-2fcce636ae34.png)


---
Can you give me few hours to respond next time you decide to close issue please? 

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: terminal
Issue: Group Tabs
Labels: Issue-Feature,Area-UserInterface,Area-Extensibility,Product-Terminal

The Color feature is neat, but I always need to open several Tabs and after few Tabs I loose the overview. 

What I would like to see, are Groups which when clicked on it, it opens every Tab located in the Group and maybe with a icon on the left side to minimize the group again. 
![1](https://user-images.githubusercontent.com/67190487/99127251-25297580-2608-11eb-813d-f9ca18ab09e1.jpg)
![2](https://user-images.githubusercontent.com/67190487/99127257-26f33900-2608-11eb-8a93-4a19f8076d5e.jpg)
Repository: flutter
Issue: CupertinoDatePicker's "mode" field can't be changed once the widget has been created
Labels: framework,f: cupertino,a: quality,P3,team-design,triaged-design

A widget should allow any of its fields to be changed and should correctly handle such changes, otherwise there will be bad behaviour in cases where unrelated widget hierarchies happen to collide with different arguments (basically it requires that you use a `key` on the widget keyed to the "immutable" property).
Repository: flutter
Issue: google_sign_in: Is there a way to not request the email?
Labels: d: api docs,p: google_sign_in,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

## Lack of privacy
If a user uses Google Sign In you will get by default `displayName`, `photoURL`, `email`. This is for us a problem in terms of privacy. We want  to act data friendly and we don't need `displayName`, `photoURL`, `email`. Unfortunately the data is directly stored in the Firebase User. This is an other big privacy issue for us, because Firebase Auth is a US-only service. Therefore we store personal data (`displayName`, `photoURL`, `email`) in the US. In terms of GDPR this is a big grey area.

## Our goal: Don't request displayName, photoURL and email
Apple Sign In gives the option to request specifics data, like:
```
final credential = await SignInWithApple.getAppleIDCredential(
  scopes: [
    AppleIDAuthorizationScopes.email,
    AppleIDAuthorizationScopes.fullName,
  ],
);
```

You see that you have to pass `email` and `fullName` as `scopes` parameter to get this data. If you pass an empty list (`scopes: []`), you will don't get any data, but the login still works. Is very data friendly 👍 

This also our goal with Google Sign In. Don't request any personal data when signing with Google.

`google_sign_in` gives also the option to set `scopes`:
```
GoogleSignIn _googleSignIn = GoogleSignIn(
  scopes: [
    'email',
    'https://www.googleapis.com/auth/contacts.readonly',
  ],
);
```

**But if you pass an empty list (`scopes: []`) you still get `displayName`, `photoURL`, `email`.** This is for me an **unexpected behavior** because specified with `scopes: []` that I don't want any data (like I did it with Apple Sign In)

According to the documation this should be possible, because `displayName`, `photoURL`, `email` are optional fields:
```
{
 // These six fields are included in all Google ID Tokens.
 "iss": "https://accounts.google.com",
 "sub": "110169484474386276334",
 "azp": "1008719970978-hb24n2dstb40o45d4feuo2ukqmcc6381.apps.googleusercontent.com",
 "aud": "1008719970978-hb24n2dstb40o45d4feuo2ukqmcc6381.apps.googleusercontent.com",
 "iat": "1433978353",
 "exp": "1433981953",

 // These seven fields are only included when the user has granted the "profile" and
 // "email" OAuth scopes to the application.
 "email": "testuser@gmail.com",
 "email_verified": "true",
 "name" : "Test User",
 "picture": "https://lh4.googleusercontent.com/-kYgzyAWpZzJ/ABCDEFGHI/AAAJKLMNOP/tIXL9Ir44LE/s99-c/photo.jpg",
 "given_name": "Test",
 "family_name": "User",
 "locale": "en"
}
```

**So my final question:** How can I achieve the behavior like with Apple Sign In. I still want to use Google Sign In, but I don't want to request `displayName`, `photoURL`, `email` from the user.
Repository: pytorch
Issue: [Feature] torch.bitwise_where
Labels: triaged,enhancement,shadow review

## 🚀 Feature

I suggest adding a new operator `torch.bitwise_where(mask, tensor1, tensor2)`

This operator is similar to `torch.where`, except that the operation is done at bit level.

I suggest this because I want to experiment with numerical stability vs the number of mantissa required for a computation, and I want to replace some bits with noise to see what would happen to a computation:

```python
noise = torch.randn(....)
mask = torch.full(..., my_mantissa)
x_with_noise = torch.bitwise_where(mask, x, noise)
y = compute(x_with_noise)
```

cc @ezyang
Repository: node
Issue: [TEST] fs: read test rejects with "cannot be written"
Labels: buffer

Multiple errors in [test-fs-read-empty-buffer.js](https://github.com/nodejs/node/blob/master/test/parallel/test-fs-read-empty-buffer.js) are rejecting/throwing read errors with `The argument 'buffer' is empty and cannot be written`. Instead of `written`, shouldn't it be `read`? Like so: `The argument 'buffer' is empty and cannot be read`?
Repository: flutter
Issue: [State Restoration] PageStorage
Labels: framework,P3,a: state restoration,team-framework,triaged-framework

PageStorage is used in the Flutter Gallery for maintaining scrollable page states. For example, in the home page, whether or not the category pages are expanded is dependent upon on an _isExpanded property, which is looked up via `PageStorage.of(context).readState`.

Since the return type of `readState` is `dynamic`, this might be a little complicated and require a separate API for state restoration, or some other solution.

cc/ @goderbauer
Repository: neovim
Issue: HOME and END does not work properly in neovim in tmux in FreeBSD 12.1
Labels: bug,tui,platform:bsd

<!-- Before reporting: search existing issues and check the FAQ. -->

**Note:** Neovim installed using `pkg install neovim`, not from ports.

- `nvim --version`:
```
NVIM v0.4.4
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/cc -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wno-c11-extensions -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/wrkdirs/usr/ports/editors/neovim/work/.build/config -I/wrkdirs/usr/ports/editors/neovim/work/neovim-0.4.4/src -I/usr/local/include -I/usr/include -I/wrkdirs/usr/ports/editors/neovim/work/.build/src/nvim/auto -I/wrkdirs/usr/ports/editors/neovim/work/.build/include
Compiled by root@121amd64-quarterly-job-08

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/share/nvim"

Run :checkhealth for more info
```
- `vim -u DEFAULTS` (version: ) behaves differently?

> I am not using vim, but HOME & END works properly in `zsh`, in `tmux`, and in `nano`

- Operating system/version:

```
# freebsd-version                                                                                                                                                                                                                                                   [12:46:12]
12.1-RELEASE
```

- Terminal name/version:

> KiTTY v0.74.2.5p @ 09/10/2020-17:13:24(GMT)
>
> (KiTTY is a fork of PuTTY)

- `$TERM`:

>  - `putty-256color` in zsh outside tmux
>  - `tmux-256color` in zsh _inside_ tmux

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
# Alternative for shell-related problems:
# env -i TERM=ansi-256color "$(which nvim)"

```

### Actual behaviour

Home & End key do not move the cursor.

### Expected behaviour

Home & End key should move the cursor to the beginning and end of line, respectively.

`infocmp` output attached:

* [infocmp-putty-256color.txt](https://github.com/neovim/neovim/files/5540263/infocmp-putty-256color.txt)
* [infocmp-tmux-256color.txt](https://github.com/neovim/neovim/files/5540264/infocmp-tmux-256color.txt)
Repository: pytorch
Issue: TorchScript is unable to distinguish int and ScalarType
Labels: oncall: jit,weeks,TSRootCause:DefaultTypes,TSUsability

## 🐛 Bug

I am adding a new operator `tensor.view(dtype)` in https://github.com/pytorch/pytorch/pull/47951, and getting lots of JIT failures.

With https://github.com/pytorch/pytorch/pull/47951, the script to reproduce this issue is

```python
import torch

def f(x):
    return x.view(-1)

s = torch.jit.script(f)
print(s.graph)

x = torch.randn(5, 5, 5)
s(x)
```

and there will be an error message

```
graph(%x.1 : Tensor):
  %4 : int = prim::Constant[value=-1]() # jit-view.py:4:18
  %5 : Tensor = aten::view(%x.1, %4) # jit-view.py:4:11
  return (%5)

Traceback (most recent call last):
  File "jit-view.py", line 10, in <module>
    s(x)
RuntimeError: The following operation failed in the TorchScript interpreter.
Traceback of TorchScript (most recent call last):
  File "jit-view.py", line 4, in f
def f(x):
    return x.view(-1)
           ~~~~~~ <--- HERE
RuntimeError: Viewing a tensor as a new dtype with different bytes is not supported.
```

cc @gmagogsfm @mruberry
Repository: go
Issue: x/crypto/argon2: docs on thread parameter might make users inadvertently create non-portable hashes
Labels: Documentation,help wanted,NeedsFix

Both `IDKey` and `Key` from [`golang.org/x/crypto/argon2`][pkg] take a `threads` parameter which is documented as following:

> The number of threads can be adjusted to the numbers of available CPUs.

While it's obviously wrong in hindsight, this sentence lead me to pass the (dynamic) value of `runtime.NumCPU()` as the value for `threads` when hashing passwords, which means the hashes Argon2 would create are different (i.e. stop matching) on hosts with different numbers of CPUs.

Would it make sense to extend the comments here to point out that `threads` is not purely performance related, but also has an effect on the hash output (e.g. by stating it needs to be a fixed value and you can use the number of CPUs as a guideline)?

[pkg]: https://pkg.go.dev/golang.org/x/crypto/argon2
Repository: flutter
Issue: Method to request focus for first focusable element in element/focus tree
Labels: c: new feature,framework,c: proposal,f: focus,P3,team-framework,triaged-framework

Assume you have a deep widget tree and you tag a part of the tree with a `GlobalKey` X.

Now, you want to programmatically (due to some user action) give the focus to the first focusable widget that is below X.

One approach would be to add a function to `FocusNode` like `requestFocusForLeaf` that would descend into the tree in traversal oder and focuses the first `FocusNode` that has no more children. 

Another approach would be to make `FocusNode.requestFocus` to delegate focus to its first traversable descendant if `canRequestFocus` is `false`.

A third approach would be to have a method on `Element like` `Element.requestFocus` that delegates focus to the first `FocusNode` below it in traversable order.

A fourth approach would be to make FocusTraversalPolicy.sortDescendants public or have other means to query the focus order of FocusNodes in a subtree.

The following shows an example of what to achieve by this request under the assumption of the fourth approach:

```Dart
import 'package:flutter/material.dart';

void main() {
  runApp(Foo());
}

class Foo extends StatefulWidget {
  @override
  State createState() => FooState();
}

class FooState extends State<Foo> {
  /// FocusNode used to tag the subtree
  final focusNode = FocusNode(canRequestFocus: false);

  void initState() {
    super.initState();

    /// Request focus of the first focusable widget below `focusNode`
    void f() {
      final policy = FocusTraversalGroup.of(focusNode.context);
      // ignore: invalid_use_of_protected_member
      final node = policy.sortDescendants(focusNode.traversalDescendants, null).first;
      node.requestFocus();
    }
    Future.delayed(
      const Duration(seconds: 1),
      f,
    );
  }

  @override
  Widget build(BuildContext context) => MaterialApp(
        home: Scaffold(
          body: Focus(
            focusNode: focusNode,
            child: BarWidget(),
          ),
        ),
      );
}

class BarWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Column(
        children: [
          Text("Foo"),
          TextField(),
          Text("Bar"),
        ],
      );
}
```
Repository: vue
Issue: Consider detecting browser environment just-in-time
Labels: discussion

### What problem does this feature solve?
When testing Vue components on Node with [@vue/test-utils](https://www.npmjs.com/package/@vue/test-utils), it is important that you mock a browser environment with [jsdom-global](https://www.npmjs.com/package/jsdom-global) *before* vue is loaded. If you fail to do this, you get a `TypeError: Cannot read property 'child' of undefined` (see https://github.com/vuejs/vue-test-utils/issues/1192) when trying to mount your component.

The reason is that when Vue is loaded, it checks the environment as
```js
const inBrowser = typeof window !== 'undefined';
```
It would be useful - at least for the mounting of components - if this check is performed just in time so that the order of loading is not important here.

While one could argue that this is not a problem if you simply get the loading order correct, there is actually a problem when trying to load `.vue` files natively in Node. I've written an experimental library for this, call [vue-esm-loader](https://www.npmjs.com/package/vue-esm-loader). The problem I had when trying to get this to work with [@vue/test-utils](https://www.npmjs.com/package/@vue/test-utils) is that there's a cyclic problem: [vue-esm-loader](https://www.npmjs.com/package/vue-esm-loader) needs [vue-template-compiler](https://www.npmjs.com/package/vue-template-compiler), which in turn loads Vue first to check for a version mismatch. However, as the loader is loaded as the very first file, this means it's impossible to mock the browser environment before vue is loaded the first time.

I was able to bypass this by directly requiring the build of vue-template-compiler which does not provide the version check, but this is not a good solution (see https://github.com/sebamarynissen/vue-esm-loader/commit/252f1df2337684613346373727f0f6203ac6aea9#diff-5dfe38baf287dcf756a17c2dd63483781b53bf4b669e10efdd01e74bcd8e780aR7). Therefore it would be useful if the environment check in Vue is done on the fly.

### What does the proposed API look like?
I propose to replace the `inBrowser` constant by an `env` object, which can look like
```js
const env = {
  get inBrowser() {
    return typeof window === 'undefined';
  }
};
```
Subsequently the `$mount` method can use this as 
```js
Vue.prototype.$mount = function (
  el,
  hydrating
) {
  el = el && env.inBrowser ? query(el) : undefined;
  return mountComponent(this, el, hydrating)
};
```

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: material-ui
Issue: Support for a 'true black' mode 
Labels: waiting for 👍,design

<!-- Provide a general summary of the feature in the Title above -->

MUI has a great dark mode but for mobile devices that support AMOLED a real true black mode is going to be needed.

True black is basically #000000 for the background so that there is no light coming from those pixels on amoled... the backlighting is essentially off.

Text is much more readable on ipad , android, etc.

<!--
  Thank you very much for contributing to Material-UI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->

- [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.

## Summary 💡

<!-- Describe how it should work. -->

Probably just another palette color set.  Not a TON of work and if we do it before you guys do I'll add the changes to this bug.

## Examples 🌈

<!--
  Provide a link to the Material design specification, other implementations,
  or screenshots of the expected behavior.
-->

https://www.google.com/search?q=twitter+true+black&rlz=1C5CHFA_enUS920US920&sxsrf=ALeKk001aTMV5VNl6O9t9gtBJraZdKp8cg:1605382573826&source=lnms&tbm=isch&sa=X&ved=2ahUKEwixj6qQ5ILtAhUDQ80KHac8D_sQ_AUoAnoECAwQBA&biw=1629&bih=925&dpr=2.2

## Motivation 🔦

Just trying not to burn my eyes out.  With the current dark mode it's still too light on ipad... would look a lot better with a true black mode.
Repository: rust
Issue: Call macro error depending on the context
Labels: A-macros,C-bug

Details in https://github.com/botika/yarte/pull/195/commits/3a54fa5da4bc01d8c2f12b7eeff5bb5e332b9d42,

When I use `ascii!`, built this way:
```rust
macro_rules! ascii_builder {
    ($($n:literal)+) => {
        #[macro_export]
        macro_rules! ascii {
            $(($n) => { unsafe { Ascii::new($n) } };)+
            ($t:tt) => {
                compile_error!(
                    concat!("No valid ascii token select another or report: ", stringify!($t))
                );
            };
        }
    };
}

ascii_builder!(
    b'!' b'"' b'#' b'$' b'%' b'&' b'\'' b'(' b')' b'*' b'+' b',' b'-' b'.' b'/' b'\\'  
);
```

It returns the compile error according to this inside or outside the crate. That is to say, in the tests it works correctly while in the crate, uncommenting the line, returns the compilation error that I have marked.
Repository: flutter
Issue: [proposal] detect or guide set-up for snapcraft android studio installation
Labels: c: new feature,tool,P3,team-tool,triaged-tool

## Use case

While I think snapcraft installation for linux user is a great idea
the synergy between android studio and flutter could be improved (examples: [1](https://github.com/canonical/flutter-snap/issues/16), [2](https://stackoverflow.com/questions/63356096/flutter-not-detecting-android-studio/))
specifically setting android studio directory might not be intuitive
`flutter config --android-studio-dir=/snap/android-studio/current/android-studio`

## Proposal

either automatically detect android studio in the default path of a snap installation 
or provide useful warning to the user prompting the correct steps to follow
Repository: material-ui
Issue: [TimePicker] A new Material Design specification
Labels: design: material,component: time picker

## Current one

<img width="400" src="https://user-images.githubusercontent.com/59839368/95446377-d68c1a00-097d-11eb-9670-1b0446736df4.jpg" />

## New Material Design Spec:
Two modes - `select` & `enter`

Potrait mode:
![](https://lh3.googleusercontent.com/UkK_zGA7g_7rPsBFg_bXZMihxH33Dnaiw3DCVw7fLSkimv4mUzruVTA6qgciQK_0DgecFGi4Y918bE0zASce_kyp2tXqazwIuQ29=w1064-v0)

Landscape mode:
![](https://lh3.googleusercontent.com/Zwf3dX4T3Wufm1hbmoQ4zioizZ6NBUjtA4unG11VHEv7vMaecwIIGMqMEpeA3YsalyG8lJdH_BpyW8WlBc-_nLHKO2Mq2WPuvHiL=w1064-v0)


More info: https://material.io/components/time-pickers
Repository: rust
Issue: Copying build files to a different drive and then building them
Labels: A-diagnostics,I-ICE,T-compiler,C-bug

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.

http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/

-->

I took all the build files so, src, target, Cargo.lock and Cargo.toml from one drive and moved them over to another drive and then ran `cargo run`. This resulted in a compiler error and it almost certainly shouldn't be supported and can be fixed simply by clearing the target directory and compiling again but it should possibly give a readable error to the user maybe suggesting they clear their target directory?

### Code

Unfortunately I'm not really sure of a minimum example as this was a basic bevy build but I don't think this depends on the code, if it does I can share the code I used.


### 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.47.0 (18bf6b4f0 2020-10-07)                                                                                     
binary: rustc                                                                                                           
commit-hash: 18bf6b4f01a6feaf7259ba7cdae58031af1b7b39                                                                   
commit-date: 2020-10-07                                                                                                 
host: x86_64-pc-windows-msvc                                                                                            
release: 1.47.0                                                                                                         
LLVM version: 11.0
```

### Error output

```
warning: Hard linking files in the incremental compilation cache failed. Copying files instead. Consider moving the cache directory to a file system which supports hard linking in session dir `\\?\D:\Programming\my_project\my_project\target\debug\incremental\my_project-3ke2er1e5ymyw\s-ft2dwv8bhb-19eyne6-working`
thread 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: Utf8Error { valid_up_to: 1, error_len: Some(1) 
}', /rustc/18bf6b4f01a6feaf7259ba7cdae58031af1b7b39\src\librustc_serialize\opaque.rs:309:87                             
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: rustc 1.47.0 (18bf6b4f0 2020-10-07) running on x86_64-pc-windows-msvc
note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental --crate-type bin

note: some of the compiler flags provided by cargo are hidden
```