sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Possible fix for webpackHotDevClient disconnecting from server.
Labels: issue: bug

Hello I would like to submit a fix for the issue people are having with the websocket in webpackHotDevClient.js disconnecting from the server. The websocket is timing out after some time, so we simply ping the server periodically to prevent it from timing out. Here is the code I've been using.

```
// Ping the server to prevent the client from disconnecting
var ping = function() {
  if (connection && (connection.readyState === connection.OPEN)) {
    connection.send("ping");
    setTimeout(ping, 3000);
  }
};

connection.onopen = function() {
  if (typeof console !== 'undefined' && typeof console.info === 'function') {
    console.info(
      'The development server has connected.'
    );
  }

  ping();
};
```

I have a branch ready here. I can submit a PR.
https://github.com/vibelife/create-react-app/blob/master/packages/react-dev-utils/webpackHotDevClient.js#L85
Repository: rust
Issue: `rustc_parser` incorrectly parses groups with `Delimiter::None`
Labels: A-parser,A-macros,T-lang,C-bug

Such groups can currently be created by proc macros.

Reproduction, proc macro crate:
```rust
#[proc_macro]
pub fn add_mul(_: TokenStream) -> TokenStream {
    // ⟪ 2 + 2 ⟫ * 2
    vec![
        TokenTree::from(Group::new(Delimiter::None, "2 + 2".parse().unwrap())),
        TokenTree::from(Punct::new('*', Spacing::Alone)),
        TokenTree::from(Literal::u8_unsuffixed(2)),
    ].into_iter().collect()
}
```

User crate:
```rust
fn main() {
    let x = add_mul!();
    assert_eq!(x, 8); // FAIL: the result is 6 != 8
}
```

This is not a huge issue right now because proc macros have no reasons to created `Delimiter::None` delimiters themselves (but they can still get them from input and return them if they return their input partially or fully, see the example below).

However, this will became a huge issue when interpolated tokens like `$e: expr` migrate from AST pieces to token streams, because in the token stream model they are represented exactly like groups with `Delimiter::None` delimiters (proc macros already see them in this way).
Repository: pytorch
Issue: Torch getting stuck transfering model to GPU in multiple GPU setting
Labels: needs reproduction,module: multiprocessing,module: cuda,triaged

While using torch multiprocessing pool to paralelize the run of multiple equal experiences in multiple GPUs I ran into the fact that a lot of times the processes block in the transfer of the model from CPU to the assigned GPU. I don't understand the reason of the blocking.

I've tried manually deleting the model at the end of each run and collecting the not used GPU memory to no avail. I would like to understand why.

I'm running this on python 3.7 in a linux system with pytorch 1.2.0 and CUDA 10.0.130 with 4 NVIDIA 1080.

My main code is the following. VGG16 is just a big network. I can add the code of it too if you feel it's necessary.

```
import torch

from torch.multiprocessing import Process, Manager, Pool
from VGG16 import VGG16

def run_experiment(name, manager_dict, manager_lock):
    device_id = None
    manager_lock.acquire()
    for device_id in manager_dict.keys():
        if device_id == "n_processes":
            continue
        if manager_dict[device_id] < manager_dict["n_processes"]:
            manager_dict[device_id] += 1
            device_id = device_id
            break
    manager_lock.release()
    print(manager_dict, flush=True)
    device = torch.device(device_id)
    print(str(name)+ "selected device: " + str(device_id), flush=True)
    
    torch.cuda.ipc_collect()
    torch.cuda.empty_cache()
    torch.cuda.synchronize(device)
    print(str(name), "Emptied cuda")
    model = VGG16()
    print(str(name), "Initialized model")
    model = model.to(device)
    print(str(name), "LOADED MODEL to the device")

    manager_dict[device_id] -= 1
    model_cpu = model.to(torch.device("cpu"))
    del model
    print(name, "Should have returned", flush=True)
    #return 1
    return model_cpu.state_dict()

def normal_experiments():
    n_processes_per_gpu = 2
    manager = Manager()
    manager_dict = manager.dict()
    manager_dict["n_processes"] = n_processes_per_gpu
    n_gpu = torch.cuda.device_count()
    print("Running on %d"%n_gpu, flush=True)
    for i in range(n_gpu):
        manager_dict[i] = 0
    manager_lock = manager.Lock()

    with Pool(processes=n_processes_per_gpu*n_gpu) as pool:
        #We call run experiment with seeds with its type of arguments
        iterable_arguments = [(str(i), manager_dict, manager_lock) for i in range(30)]
        res = pool.starmap(run_experiment, iterable_arguments)
    print("Done")

def main():
    torch.multiprocessing.set_start_method('spawn')
    normal_experiments()

if __name__ == "__main__":
    main()

```

cc @ngimel
Repository: rust
Issue: Clever recursive types + deref = seemingly infinite compile time
Labels: E-needs-test,T-compiler,C-bug,I-hang

The following takes an unknown, potentially infinite amount of time greater than 10 minutes to compile:
```
struct S<T>(T);
impl<T> std::ops::Deref for S<T> {
    type Target = S<(T,T)>;
    fn deref(&self) -> &Self::Target {
        self.thing()
    }
}
```
As @rkruppe pointed out on Discord,
> Most places in rustc are supposed to have limits to stop them from going in circles forever (or just for a very long time), so at first glance I'd consider this a bug
Repository: godot
Issue: Errors when instancing a sprite that contains a viewport
Labels: bug,topic:core,topic:rendering,confirmed

**Godot version:** commit 9002b045c (Godot 3.2 beta)

**OS/device including version:** Linux Mint 19

**Issue description:**

Instancing a Sprite3D with a ViewportTexture that points to a viewport which descends from it generates many errors and doesn't render correctly.

![image](https://user-images.githubusercontent.com/6402237/70269152-928a2080-1780-11ea-9499-a4f8bd5091f7.png)

![image](https://user-images.githubusercontent.com/6402237/70269100-7c7c6000-1780-11ea-8d43-8bf13f35c0ef.png)

**Minimal reproduction project:**

[viewport_wierdness.zip](https://github.com/godotengine/godot/files/3928812/viewport_wierdness.zip)
Repository: kubernetes
Issue: Pod.Status.PodIP not updated during postStart lifecycle hook
Labels: kind/bug,sig/network,sig/node,help wanted,triage/needs-information,needs-triage

<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->


**What happened**:

When using a postStart lifecycle hook, the Pod.Status.PodIP is not updated while the hook is running, even though the pod has been assigned an IP via the CNI plugin and networking is set up.

**What you expected to happen**:

The Pod.Status.PodIP should be set as soon as it's available.

**How to reproduce it (as minimally and precisely as possible)**:

The following manifest should repro the issue. Apply it and then watch the pod status.

```
apiVersion: v1
kind: Pod
metadata:
  name: test-calico-post-start
spec:
  containers:
  - name: test-calico
    image: byrnedo/alpine-curl:latest
    command:
    - sh
    - -c
    - "sleep 400000"
    lifecycle:
      postStart:
        exec:
          command: [ "/bin/sh","-c","sleep 120 && result=$(curl  http://www.google.com 1> /var/log/output.log 2> /var/log/output-error.log ); echo $result"]
```

The postStart lifecycle hook here contains a sleep for 120 seconds. During the first 120 seconds, the pod status will be ContainerCreating and the podIP will not be set. Only after the hook completes will the podIP be set.

**Anything else we need to know?**:

Why is this important? It prevents Calico network policy from operating correctly during the postStart hook since we cannot learn the pod's IP address. (Note that when Calico is also the CNI plug-in, we do learn it, but Calico is designed to run in "policy only mode" on top of other CNI plug-ins, like the AWS VPC-CNI plug-in). C.f. https://github.com/projectcalico/libcalico-go/issues/1125 and https://github.com/projectcalico/felix/issues/2008 for users who are having problems here.

**Environment**:
- Kubernetes version (use `kubectl version`): v1.16.3
- Cloud provider or hardware configuration: AWS
- OS (e.g: `cat /etc/os-release`): Ubuntu 16.04
- Kernel (e.g. `uname -a`): 4.4.0-1098-aws
- Install tools: kubeadm
- Network plugin and version (if this is a network-related bug): amazon-vpc-cni-k8s v1.5 with Calico v3.8.1
- Others:
Repository: rust
Issue: Warn if type-name in parameter-position
Labels: C-enhancement,A-lints,A-diagnostics,T-lang,T-compiler

I was surprised that one can confuse himself like in the cooked-up example below: Specifying a concrete type for a parameter on an `impl` does what one expects. This might lead to the expectation that you can specify a concrete type for a parameter on an `fn`, which is not the case:

```rust
struct Foobar<T>(T);

trait Foo {
    fn bar<H>(&self, b: H) where H: std::fmt::Display ;
}

// `String` is a type...
impl Foo for Foobar<String> {
    // `String` is not a type, it's a type-parameter named `String`.
    // This is almost guaranteed to be wrong!
    fn bar<String>(&self, _b: String) where String: std::fmt::Display {}
}
```
Here, `String` does not refer to the type `String` but is still a generic parameter, now named `String` instead of `H`.

If we don't specify the `Display`-bound, the compiler even helpfully suggests to add the requirement `String: Display`, which we can do right away. We can use `fn bar<u32>(...)` and the compiler will warn that `u32` should be upper-cased.

Maybe the compiler could warn if a parameter is given the name of a type that is in scope? Something to the tune of

> The type-parameter named `String` in `fn bar<String>(...)` has the same name as the type `std::string::String` in the local scope. Be aware that this declares a type-parameter named `String`. It does not specify a concrete type and might lead to confusion. The original definition is `fn bar<H>(...)`
Repository: rust
Issue: "undefined symbol" when loading dylib compiled on >1.36.0
Labels: A-linkage,E-needs-test,T-compiler,C-bug

`undefined symbol: _ZN42_$LT$$RF$T$u20$as$u20$core..fmt..Debug$GT$3fmt17hd0ba07f053fd4c7fE`

My project structure:
```
parent
    main.rs  # binary, loads libchild.so via libloading
    lib.rs   # dylib, shared code
child
    lib.rs   # dylib, dynamically linked to libparent.so
```
This compiles fine, but fails to load `libchild.so` when compiled on anything newer than 1.36.0. If the `parent` library is made non-dylib, it works fine, however this is not a viable solution for my project as it causes `libchild.so` to contain all the shared code, and my project has many `libchild.so`-equivalent crates.

Demo case: https://github.com/GinjaNinja32/rust-issues/tree/undefined-symbol-core-fmt-debug (has 70 dependency crates, mostly indirect; I'm not sure exactly where it goes wrong or how to make it smaller)

Bisected to merge dbebcee8d07b77eae3725988879001e6205c6e47, #59752.

```
rustc 1.39.0 (4560ea788 2019-11-04)
binary: rustc
commit-hash: 4560ea788cb760f0a34127156c78e2552949f734
commit-date: 2019-11-04
host: x86_64-unknown-linux-gnu
release: 1.39.0
LLVM version: 9.0
```
Repository: create-react-app
Issue: Since updating to 3.3.0, running out of memory
Labels: issue: bug,issue: needs investigation

### Describe the bug

After upgrading to 3.3.0 and TS 3.7.3 (was previously on 3.2.0 and TS 3.7.2), I am unable to run `yarn start`

I receive this error: `FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory`

Reverting to react-scripts v3.2.0 resolves this issue - Typescript being at 3.7.3 or 3.7.2. has no effect, so I've narrowed it to react-scripts.

### Did you try recovering your dependencies?

Yes, blew away node_modules and re-ran `yarn`, tried without a lock file, etc. No dice.

### Environment

Windows 10, VSCode (also occurs on my macbook)
Repository: flutter
Issue: Validate whether performance of fastReassemble can be improved with location objects 
Labels: tool,c: proposal,P3,team-tool,triaged-tool

The fastReassemble method is currently (via https://github.com/flutter/flutter/pull/45649) implemented by walking the Element tree and comparing the runtimeType of the each Element's widget and the string value it is provided in. Besides the fact that we walk the entire tree O(n), runtime type is also fairly slow.

We might be able to improve the performance of this method by instead using the _Location objects created by the track-widget-creation transformer. This gives each widget constructor a `_location get location` field which contains information about the source location where the widget is constructed: https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/widget_inspector.dart#L2840

If fastReassemble method can provide the location for the particular widget that is updated, and the runtime could track elements by the location and provide O(1)
Repository: flutter
Issue: Integration with Fuchsia introspection tools
Labels: c: new feature,engine,c: performance,platform-fuchsia,P2,team-engine,triaged-engine

We should make sure that any platform-specific developer introspection tools expose details of the internals of the running applications. For example, a memory viewer should not just report the Flutter engine heap size, it should expose the memory usage of individual isolates, or even lower-level, exposing Dart objects on the Dart heap to the heap viewer of the system-level memory tools. Similarly for CPU, battery usage, etc.

This is a very vague bug, intended to capture a medium-term goal. We should file sub-bugs to track individual specific features that need to be exposed on specific tools.

cc @iskakaushik @cbracken @eseidelGoogle
Repository: flutter
Issue: Enable incremental installation by default on iOS
Labels: platform-ios,tool,P3,a: plugins,team-ios,triaged-ios

Per discussion in https://github.com/FirebaseExtended/flutterfire/issues/349, we can improve build times for `flutter create` devs by enabling incremental installation in the template Podfile.

```
install! 'cocoapods',
   generate_multiple_pod_projects: true,
   incremental_installation: true
```

Benefits:
- Subsequent builds are much faster when using plugins like cloud_firestore.

Drawbacks:
- Requires CocoaPods 1.7.0 (if this is an issue we could use cocoapods-binary but then that would have to be installed as well)
- Possibly slightly longer initial build times
Repository: godot
Issue: Godot script editor does not respect Mac keyboard bindings
Labels: bug,platform:macos,topic:editor

**Godot version:** 312

**OS/device including version:** macOS 10.14.6

**Issue description:**
Mac allows users to override key bindings for customization. One such popular customization is to remap the home and end keys to behave like every other OS. For example

`~/Library/KeyBindings/DefaultKeyBinding.dict`

```
{
/* Remap Home / End */
"\UF729"  = "moveToBeginningOfLine:";                   /* Home         */
"\UF72B"  = "moveToEndOfLine:";                         /* End          */
"$\UF729" = "moveToBeginningOfLineAndModifySelection:"; /* Shift + Home */
"$\UF72B" = "moveToEndOfLineAndModifySelection:";       /* Shift + End  */
}
```

**Steps to reproduce:**
Use this custom Mac keybinding file (note you have to log out and back in) and try to use the home and end key in Godot. Godot will treat home and end as if it were the Mac default.

**Minimal reproduction project:**
 N/A
Repository: rust
Issue: Unit-like structs in const generic arguments
Labels: T-compiler,C-feature-request,C-bug,A-const-generics

```rust
#![feature(const_generics)]

#[derive(PartialEq, Eq)]
struct Unit;
trait Const<const U: Unit> {}
impl Const<Unit> for () {} // wrong number of const arguments
```

`Const<{Unit}>` works. See also #66615.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: neovim
Issue: allow options private to a window (not copied with the buffer)
Labels: enhancement,api,core,options

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: NVIM v0.4.3
- `vim -u DEFAULTS` (version: ) behaves differently?
- Operating system/version: MacOS
- Terminal name/version:
- `$TERM`: xterm-256color

### Steps to reproduce using `nvim -u NORC`

Suppose there are two files test.vim and test2.vim in the same directory:

test.vim
```vim
let id1 = nvim_open_win(bufadd('test.vim'), 1, {'relative':'win', 'width':20, 'height':5, 'row':15, 'col':15})
let id2 = nvim_open_win(bufadd('test2.vim'), 0, {'relative':'win', 'width':20, 'height':5, 'row':5, 'col':5})
echom id1 id2

call nvim_win_set_option(id2, 'cursorline', v:true)
call nvim_win_set_option(id2, 'winhighlight', 'Normal:Error')

call nvim_win_close(id1, 1)
call nvim_win_close(id2, 1)

edit test2.vim
```
test2.vim, the content can be anything.
```vim
let id1 = nvim_open_win(bufadd('test.vim'), 1, {'relative':'win', 'width':20, 'height':5, 'row':15, 'col':15})
let id2 = nvim_open_win(bufadd('test2.vim'), 0, {'relative':'win', 'width':20, 'height':5, 'row':5, 'col':5})
echom id1 id2

call nvim_win_set_option(id2, 'cursorline', v:true)
call nvim_win_set_option(id2, 'winhighlight', 'Normal:Error')

call nvim_win_close(id1, 1)
call nvim_win_close(id2, 1)

edit test2.vim
```

steps:
1. nvim -u NORC test.vim
2. `so %`

### Actual behaviour
1. the cursorline appears
2. the color of the window is the same as `Error`

### Expected behaviour
1. no cursorline
2. the color of the window does not change
Repository: ant-design
Issue: Instead of false, use value `null` to stand for feature disabling
Labels: Inactive

- [x] 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?
When using Table, people set rowSelection to `null` to disable the whole rowSelection feature, but if they want to disable pagination, they should set it to `false`, which is really confusing

Sometimes `false` itself can be a meaningful boolean value, but generally `null` won't

Also, in OpenAPI@3, fields can keep a [`nullable`](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#schemaNullable) property to specify that the value may totally be `null`, so I think `null` is more clear for this situation

What's more, only [nullish](https://developer.mozilla.org/en-US/docs/Glossary/nullish) value will fail in optional chaining and nullish coalescing operator, if still using `false`, maybe there will be some unexpected bugs someday 🤔

### What does the proposed API look like?
- rowSelection: null
- pagination: null


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: iPadOS: cannot move panes around (activity bar, panel)
Labels: feature-request,web,safari,ios-ipados

Refs: #85990

We probably did not hook up drag and drop support for moving views around.
Repository: terminal
Issue: Unusual 3rd-party keyboard layout issue; Can't type digits with Shift in Neovim in PowerShell?
Labels: Area-Input,Issue-Bug,Area-TerminalControl,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

<!--
This bug tracker is monitored by Windows Terminal development team and other technical folks.

**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.

If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible.

-->

# Environment

```none
Windows build number: 10.0.19033.0
Windows Terminal version (if applicable): 0.7.3382.0 (but it's reproduceable in earlier builds too)

Neovim: 0.4.2
PowerShell Core: 7.0.0-preview.6
Universal keyboard layout: https://github.com/braindefender/universal-layout
```

# Steps to reproduce

1. Start Terminal with PowerShell Core.
2. Start Neovim.
3. Switch to insert mode (press i).
4. Type any digit by holding Shift and pressing a key with a digit on it. Like 3.

<!-- A description of how to trigger this bug. -->

# Expected behavior

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

The digit is typed.

# Actual behavior

<!-- What's actually happening? -->

Nothing is typed.

# Additional information

I can type digits in WSL2 Ubuntu. The rest of the setup is the same.

I also can type digits in plain PowerShell Core, without Neovim.

Also, I can type digits in Neovim under PowerShell Core if I run it not in Windows Terminal, i.e. if I run the regular old school terminal.

Also, I can type digits in Vim instead of Neovim.