sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: App Containers can't inherit Init Containers CPUs - CPU Manager Static Policy
Labels: kind/bug,priority/backlog,area/kubelet,sig/node,triage/accepted

<!-- 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**:. 
CPU Manager was configured with static policy.
AppContainer couldn't be placed on the same NUMA node as InitContainer, thus couldn't inherit CPUs used by InitContainer, so it ended up with multi NUMA locality hint generated (ex. [11-false]). This can cause a pod rejection, depending on Topology Manager policy. 

**What you expected to happen**:
AppContainer to be placed on the same NUMA node as InitContainer, if there is enough resources (and inherit InitContainer CPUs). If not, it should be placed on another NUMA node and CPUs used by InitContainer should be released back to the pool. 

**How to reproduce it (as minimally and precisely as possible)**:
Leave small amount of free CPUs on NUMA0, enough to fit InitContainer, but not enough to fit AppContainer. On NUMA1 there should be enough CPUs to fit AppContainer.

**Anything else we need to know?**:
Part of the code that is responsible for discarding other hints: 
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/cm/cpumanager/policy_static.go#L384-L392

**Environment**:
- Kubernetes version (use `kubectl version`): v1.19.0-rc.4.190+436f1afaf30c22
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
Repository: go
Issue: x/tools/cmd/present: Presenter notes closer to the webcam
Labels: help wanted,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.14.7 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/deleplace/.cache/go-build"
GOENV="/home/deleplace/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/deleplace/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/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-build635615335=/tmp/go-build -gno-record-gcc-switches"

</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.
-->

In the directory containing my `presentation.slide`:
```
$ present -notes
```

Then in my browser: pressed N to open the Presenter Notes window


### What did you expect to see?

Feature request: an option to have

- the Presenter notes at the top of the notes window
- the slides at the bottom of the notes window

![image](https://user-images.githubusercontent.com/13508141/91173196-b78f3c80-e6dd-11ea-9a6f-a00da8991d99.png)

Currently (2020) many speakers around the world present from home. The camera filming the speaker is always above its physical screen, with few exceptions. Eye contact is very important to engage the audience, so for a speaker who reads notes it would be optimal to place the notes as close as possible to the webcam, at the top of the screen.

### What did you see instead?

- Slides at the top of the notes window
- Presenter notes at the bottom of the notes window

![image](https://user-images.githubusercontent.com/13508141/91173114-9595ba00-e6dd-11ea-99b3-249b6a65c884.png)
Repository: flutter
Issue: Show suffix/prefix text in TextField even when it is not in focus and empty.
Labels: a: text input,c: new feature,framework,f: material design,c: proposal,P2,team-text-input,triaged-text-input

Closed related issue: https://github.com/flutter/flutter/issues/19488

@willlarche has closed the issue on 21 Aug 2018 because it was impossible to support both the floating animation behaviour and keeping the suffix/prefix at all times. Since flutter v.1.13.2 in 2020 the floating behaviour got smarter and I believe it should now be possible to always show the suffix when `floatingLabelBehavior: FloatingLabelBehavior.always` is set, since the disabled animation would not interfere with the suffix widget.
Repository: create-react-app
Issue: Module resolution: direct dependencies should take precedence
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

In a Yarn workspace, a typically layout might be:

```
workspace/
    - component_library
    - app1
    - app2
```
Where `app1` and `app2` are dependent on `component_library`, which is a library of common components with a _peer dependency_ on React.

This is fine and _normally_ React will be hoisted to the top level node_modules:

```
workspace/
    - node_modules
        -- react 
        -- react-dom
    - component_library
    - app1
    - app2
```

However, situations may arise such as described here:
https://github.com/facebook/react/issues/13991#issuecomment-680010966

In this case, ``component_library`` has dev dependencies on storybook and various storybook plugins, which have their own dev dependencies on a _different_ version of React. With Yarn hoisting, you can end up with a layout like this:

```
workspace/
    - node_modules
        -- react (from storybook)
        -- react-dom (from storybook)
    - component_library
    - app1
        -- node_modules
             --- react
             --- react-dom
    - app2
```

Running ``app1`` will result in ``component_library`` using the top level React and ``app1`` using its' own React and calamity ensues.


### Describe the solution you'd like

I would expect that the ``node_modules`` directly under ``app1`` should take precedence over other ``node_modules`` in a workspace.
I.e switch the resolve order from:

```javascript
modules: ['node_modules', paths.appNodeModules].concat(
        modules.additionalModulePaths || []
      ),
```

to:

```javascript
modules: [paths.appNodeModules, 'node_modules'].concat(
        modules.additionalModulePaths || []
      ),
```

I cannot think of any reason why you would *not* want the listed dependencies of the _actual app you are building_ to take precedence over other (indirect) dependencies? 
This also respects Yarns' hoisting logic, since any direct dependencies which are hoisted would still be resolved (due to nodejs module resolution looking at parent directories)


### Describe alternatives you've considered
Setting 'nohoist' to all the 'storybook' dependencies does not work in this scenario. Either the unwanted version React is *not* hoisted, in which case it is still resolved since it lives directly under the ``component_library`` or it _is_ hoisted, in which case it is still resolved since the node module resolution will look at parent directories....

Another solution would be to allow editing the module resolution paths without having to ``eject``, although I have no suggestions on how to achieve this.
Repository: rust
Issue: tidy on NTFS spuriously warns about executable bit
Labels: T-infra,C-bug

When I run `./x.py tidy`, I get a lot of errors:

```
$ ./x.py test tidy
Updating only changed submodules
Submodules updated in 0.02 seconds
    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
Building stage0 tool tidy (x86_64-unknown-linux-gnu)
    Finished release [optimized + debuginfo] target(s) in 0.14s
tidy check
* 615 error codes
* highest error code: E0772
Checking which error codes lack tests...
Found 509 error codes
Found 0 error codes with no tests
Done!
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/annotate_snippet_emitter_writer.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/Cargo.toml
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/diagnostic.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/diagnostic_builder.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/emitter.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/json/tests.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/json.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/lib.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/lock.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/registry.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/snippet.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_errors/styled_buffer.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_middle/arena.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_middle/benches/lib.rs
tidy error: binary checked into source: /mnt/rust/src/librustc_middle/Cargo.toml
tidy error: binary checked into source: /mnt/rust/src/librustc_middle/dep_graph/dep_node.rs
```
(Followed by about 22900 similar errors).

I reported the issue [on URLO][urlo-issue]. @daboross found where in the code the error is emitted ([here][error-emission-place]). According to them, the error comes from the fact I am running `./x.py test tidy` on a NTFS partition on Linux (see [their comment][daboross-comment]).

[urlo-issue]: https://users.rust-lang.org/t/contributing-to-rustc-x-py-test-tidy-gives-a-lot-of-errors/47712
[error-emission-place]: https://github.com/rust-lang/rust/blob/c35007dbbe4846c641b5edad9fddf3f72a5a035a/src/tools/tidy/src/bins.rs#L40
[daboross-comment]: https://users.rust-lang.org/t/contributing-to-rustc-x-py-test-tidy-gives-a-lot-of-errors/47712/5
Repository: terminal
Issue: Add an action to gracefully upgrade a connection to a debug tap connection
Labels: Area-TerminalConnection,Product-Terminal,Issue-Task

/cc @DHowett 

The debug tap is _great_. Really helpful for figuring out what we're getting from conpty. However, sometimes it's hard to get the terminal into a bugged state (see #6901, #6987), and if you didn't already have the debug tap open, then you can't use it.

I think it would be _awesome_ if we could add an action to take the current connection, wrap it up in a debug tap, and open up a new pane to see the debug output.
Repository: go
Issue: x/pkgsite: document how to add experiments locally
Labels: Documentation,NeedsFix,pkgsite

We should add a `doc/experiment.md` file which describes how to add experiments when running locally, including:

- Running `go run devtools/cmd/experiment/experiment.go create <experiment> <rollout>`
- Where to find existing experiments
- How to add a new experiment to the codebase
Repository: godot
Issue: FileDialog always ask to override file even at creation if register_text_center is used with get_line_edit
Labels: bug,confirmed,topic:gui

**Godot version:**
3.2.2-stable


**OS/device including version:**
Linux Manjaro KDE 20.0.3


**Issue description:**
Hi, 
I'm creating a dialogue editor application. To gain time, I wanted to improve the user's workflow with FileDialog. If the user tries to save a new file with ctrl+s, the FileDialog is displayed in save mode, he wrote his file name and then press enter to create the file.
Since it wasn't the default behavior (was closing the modal when pressing enter) I use the following workaround to make it save (base on the AcceptDialog class).

`register_text_enter(get_line_edit())`


After that, the FileDialog correctly submitted the data when enter is pressed. But every time, the override confirmation dialog is displayed, even if the file didn't exist before the manipulation.


**Steps to reproduce:**
![ezgif-4-5433e0eb8a89](https://user-images.githubusercontent.com/1162446/91182888-0e4f4300-e6eb-11ea-9d73-204a71bf2fc0.gif)
- Create a project with a FileDialog pop-up.
- Add a Serialize.gd singleton to save and load a fake JSON file
- Add *.json to his filter pool string
- Add the following script to the FileDialog

```
extends FileDialog


func _ready():
	connect("confirmed", self, "_on_Confirmed")
	connect("file_selected", self, "_on_File_selected")
[error_save_overwrite.zip](https://github.com/godotengine/godot/files/5124117/error_save_overwrite.zip)

	register_text_enter(get_line_edit())


func _on_dialog_opened(new_mode: int) -> void:
	mode = new_mode
	popup()


func _on_Confirmed() -> void:
	print_debug("json will be save inside %s" % current_path)
	if mode == 0:
		Serialize.load(current_path)
	if mode == 4:
		Serialize.save_as(current_path)


func _on_File_selected(path: String) -> void:
	if mode == 0:
		Serialize.load(current_path)


```


**Minimal reproduction project:**

[error_save_overwrite.zip](https://github.com/godotengine/godot/files/5124121/error_save_overwrite.zip)
Repository: pytorch
Issue: FP16 gives NaN loss when using pre-trained model
Labels: module: cuda,triaged,module: amp (automated mixed precision)

I tried the new fp16 in native torch. However, when I continue my model training for my segmentation task I get loss as NaNs. With the same script, if I initialize the same model architecture from scratch then it works fine.
I set adam's 'ep' to 1e-4 as well but it made no difference. I get NaN loss from the first batch continuing my trained model. 

The model that I am continuing is already quite good at the task. I am guessing it is due to very low loss value but am not sure. How can I fix this?

Python 3.6 
Pytorch 1.6
Linux
pip installed lightning
CUDA Version: 10.1
Nvidia-V100


cc @mcarilli @ngimel
Repository: pytorch
Issue: [RFC] RPC BENCHMARK
Labels: triaged,module: rpc

## Background

This will allow potential users to see what kind of throughput they can expect if they use RPC for their use case.  Also so the throughput effects of changes made to RPC can be measured.

Users of the benchmark can invoke a script, passing multiple arguments to specify what kind of environment they want to see benchmark numbers for. 

## API

The following arguments will be available
- `model_layers` (default=2)
- `model_weight` (default=10)
- `model_bias` (default=10)
- `agent_count` (default=1)
- `observer_count` (default=100)
- `batch` (default=True)
- `rpc_framework` (default=ProcessGroup), (options=ProcessGroup,TensorPipe,Postman)
- `device_type` (default=CPU), (options=CPU,GPU)

## Example Output

```
-----------------------------------
PyTorch RPC benchmark suite
-----------------------------------

* PyTorch version: 1.4.0a0+05140f0
* CUDA version: 10.0
* Core Count: 12
* Device: CPU
* Batch: True
* Observers: 100
* Agents: 1
* Framework: ProcessGroup
* Model Layers, Weight, Bias: (2, 10, 10)

         sec/iter    ex/sec      sec/iter    ex/sec      sec/iter    ex/sec      sec/iter    ex/sec
  p50:    0.162s     197/s  p75:  0.162s     197/s  p90:  0.162s     197/s  p95:  0.162s     197/s
```

## Implementation Plan

- **Phase 1:** Single machine CPU with TensorPipe and ProcessGroup frameworks working
- **Phase 2:** Should work with GPU in addition to CPU, should work with postman backend, and finally should work with multiple machines


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar @jiayisuse
Repository: pytorch
Issue: `torch.svd()` CUDA gives incorrect results when input contains `nan`
Labels: triaged,module: NaNs and Infs,module: linear algebra

## 🐛 Bug

In at least one case, `torch.svd()`'s CUDA implementation gives an incorrect result when the input contains a `nan` value.

This issue shows up when the input is `torch.tensor([[float('nan'), 1.0]])`.

## To Reproduce

```
>>> import torch
>>> torch.svd(torch.tensor([[float('nan'), 1.0]]))
torch.return_types.svd(
U=tensor([[1.]]),
S=tensor([nan]),
V=tensor([[nan],
        [nan]]))
>>> torch.svd(torch.tensor([[float('nan'), 1.0]]).cuda())
torch.return_types.svd(
U=tensor([[1.]], device='cuda:0'),
S=tensor([1.4142], device='cuda:0'),
V=tensor([[nan],
        [nan]], device='cuda:0'))
```

## Expected behavior

In the above code snippet, the CUDA result is `S=1.4142`, but it should be `S=nan`. The CPU result is correct.

## Environment

PyTorch version: 1.7.0a0+5ff1ce3
Is debug build: False
CUDA used to build PyTorch: 10.2

OS: Ubuntu 18.04.3 LTS (x86_64)
GCC version: (crosstool-NG 1.24.0.123_1667d2b) 7.5.0
Clang version: Could not collect
CMake version: version 3.18.0

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: 10.2.89
GPU models and configuration: 
GPU 0: TITAN RTX
GPU 1: TITAN RTX

Nvidia driver version: 440.33.01
cuDNN version: /usr/local/cuda-10.2.89/targets/x86_64-linux/lib/libcudnn.so.7

Versions of relevant libraries:
[pip3] numpy==1.19.1
[pip3] torch==1.7.0a0+5ff1ce3
[conda] magma-cuda101             2.5.2                         1    pytorch
[conda] mkl                       2020.2                      256    conda-forge
[conda] mkl-include               2020.2                      256    conda-forge
[conda] numpy                     1.19.1           py38h8854b6b_0    conda-forge
[conda] torch                     1.7.0a0+5ff1ce3           dev_0    <develop>

## Additional context

<!-- Add any other context about the problem here. -->


cc @vincentqb @vishwakftw @jianyuh
Repository: TypeScript
Issue: Strange intersection/variance behavior
Labels: Needs Investigation

**TypeScript Version:**  Nightly (d6dda230bce0828144e5f17539d6e3f9bf4c4f3b)

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** variance, intersection

**Code**

```ts
interface BaseEvent {
    type: string;
}
interface DerivedEvent extends BaseEvent {
    type: "mytype";
    payload: number;
};
type TransitionConfig<TEvent extends BaseEvent> = (event: TEvent) => void;
type TransitionsConfigMap<TEvent extends BaseEvent> =
    & { splendiferous?: never } // Un/comment this line
    & { [K in TEvent['type']]?: TransitionConfig<TEvent>; };
type TransitionsConfigArray<TEvent extends BaseEvent> = {
    [K in TEvent['type']]: TransitionConfig<TEvent extends { type: K; } ? TEvent : never>;
}[TEvent['type']];
type AssignAction<TEvent extends BaseEvent> = (meta: TransitionsConfigMap<TEvent> | TransitionsConfigArray<TEvent>) => void;
declare const d1: AssignAction<DerivedEvent>;
declare const b1: AssignAction<BaseEvent>;
const d2: typeof d1 = b1; // Sometimes an error
const b2: typeof b1 = d1; // Sometimes an error
```

As-is, there are errors on both `d2` and `b2`.  If you comment out the "splendiferous" line, the error on `b2` goes away.  (If you disable strict function types, the error on `d2` also goes away.)  I find this strange, since that line does not reference `TEvent`.

The type names give breadcrumbs back into `xstate`, but I've inlined and deleted so many things that the structure is substantially different.

**Playground Link:** https://www.typescriptlang.org/play?ts=4.0.2#code/JYOwLgpgTgZghgYwgAgEJwM4QKIDcLjIDeAUMucmAJ4AOEAXMhmFKAOYDcJAviaJLEQoAItGD4AJngJhkEAB6QQEjGkw58hUhUq0GyAEQBbKtToGuOmnCoAbAPZwJjEAFcjAI2hduXMygAVKDgQDGAwYHsQAGEomGA2AB4A6UIFJRU1LFSwAD5kAF5kAAoITTBGFPKASkL83HtgCT89ZCCQsIiojFiQeLYAWTgaZJy5RQJM9Gzy-IKyCgAyYiYaW0ngGGh7VwwAfhcy6GReHWWiZABtAGlkUDacy4ByfyeAXTeDtuDQ8MiYuIJUazDgnFp0b4dP7dXr9ACCUGCVGBMnGGVU0w0MjmxAW5BudxAD3Kz1eH0qP06-1hQKqqPSk1UF38jGuoO4yD2xNRh3wUFyPkudPApL07ze4JQcIwYTYIDhCC6IBRaQmygx6hyOOKRggYDgFKhSp6gMGwxVeWQAB9Ib9jTS2AikRbcrUCvVGs0SBIIAhbHAoCgEN1ZBIAIyMaWy+WK-6JUSsSRarg+v0BoMh5AeCPIKMJGNKxKY5MkYOhUMAJkY-nsMGQ4cKWbDXDLzCzVd0dFrTcb4Y4QA
Repository: flutter
Issue: Create a clear ownership model for `Layer`s, `Picture`s, and `RenderObject`s.
Labels: c: new feature,framework,c: API break,P3,team-framework,triaged-framework

In Flutter, `Image` objects are underpinned by `SkImage`s, which are immutable refcounted objects. An SkImage cannot release its underlying image data until its refcount drops to zero. The same is true for `Path`s, `Vertices`, and other things we draw into `Pictures`, but it's especially important for `Image`s since they tend to use more memory.

We draw `SkImage`s into `SkPicture`s, so whatever picture we draw an image into also has to have its refcount go to zero to release the image memory.

`SkPicture`s end up being held by `Picture` objects in Dart, which in turn are held by `Layer` objects. They are also held internally by the engine by `PictureLayer` objects, which do not have an exact Dart peer but are indirectly held by other Dart peer Layers (which hold on to `EngineLayer` objects eventually). Layers have a somewhat ambiguous ownership model - they are owned potentially by other layers or by `RenderObject`s. RenderObjects have no disposal method.

In an ideal world, we would have a proper lifecycle established for RenderObjects, Layers, EngineLayers, Pictures, and Images. Unfortunately, doing this will require a number of breaking changes. 

If we could figure out all the breakages necessary for this and create some clearer ownership models, we could have a better Image API (and generally allow people to reason a bit more about when potentially expensive resources they've drawn into a Picture can be freed).

I believe this is an API break because application code would have to update the way it interacts with RenderObjects and/or Layers.