sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: After upgrading to 1.9 `flutter logs` on iOS displays system logs
Labels: platform-ios,tool,P3,team-ios,triaged-ios

After upgrading to Flutter 1.9, `flutter logs` on a connected iOS device shows the full system logs, and not the filtered logs for Flutter as it was with previous versions.

```
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.9.1+hotfix.2, on Mac OS X 10.14.5 18F203, locale en-PT)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.38.1)
[✓] Connected device (1 available)

• No issues found!

```

The same occurs in stable
Repository: rust
Issue: Document how ptr::drop_in_place behaves when dropping a slice panics
Labels: C-enhancement,A-FFI,T-lang,A-docs

When dropping a slice `[T]` using `ptr::drop_in_place`, a `T::drop`  can panic. I can't find any documentation of what the behavior of the program is in that case.
Repository: go
Issue: net: spurious EADDRINUSE from connect syscall on FreeBSD when connecting from IPv6 wildcard to IPv4 address
Labels: ExpertNeeded,OS-FreeBSD,NeedsInvestigation

Observed in a `freebsd-amd64-12_0` TryBot: https://storage.googleapis.com/go-build-log/2e4c3b9c/freebsd-amd64-12_0_d1b5be43.log

```
--- FAIL: TestDialerLocalAddr (0.00s)
    dial_test.go:647: tcp [::]:0->127.0.0.1: got dial tcp [::]:0->127.0.0.1:22464: connect: address already in use; want <nil>
FAIL
FAIL	net	54.481s
```

This test is also flaky on macOS (#22019), but the symptom on FreeBSD is different from the one observed on macOS (`connect: address already in use` vs. `getsockopt: operation timed out`).

Note that the `freebsd-arm-paulzhol` flake reported in https://github.com/golang/go/issues/22019#issuecomment-355091973 matches this one.

CC @ianlancetaylor @mikioh
Repository: terminal
Issue: Setting cursor position has too many routes
Labels: Product-Conhost,Help Wanted,Area-Interaction,Issue-Bug

Based on #2731, repeated here:

>>When it came to actually setting the cursor position, I found there were a number of options to choose from, with quite different behaviours. Some operations use a variation of SetConsoleCursorPosition, some use AdjustCursorPosition, and some call the SCREEN_INFORMATION::SetCursorPosition method directly, or even just Cursor::SetPosition. It wasn't always clear to why a particular method was chosen.
>
>This certainly needs a follow up work item. I'm reviewing some of the code in each of these to try to come up with reasoning why you should use one over the other... and I'm realizing that this is probably the source of our "the cursor is blinking weirdly or is on when it shouldn't be while text is outputting" problems.
>
>As far as I can tell, you've chosen the correct one with SCREEN_INFORMATION::SetCursorPosition because that one is responsible for updating the delay status on the cursor so it stays off or on instead of blinking wildly as it is moving rapidly around the screen when things are happening. The cursor is supposed to temporarily suspend blinking when there is activity (by the delay).
>
>I am certain the inconsistency in application of which cursor-setting-function is being used is responsible for graphical glitches.

This work item represents auditing the cursor position setting methods to reconcile them into a (hopefully) more unified entry point. It probably also represents analyzing the assorted delay booleans that temporarily suspend cursor drawing to reconcile those as well. (`Cursor::_fDelay` and `Cursor::_fIsVisible` and `Cursor::_fBlinkingAllowed` and `Cursor::fIsOn`. and `Cursor::f_DeferCursorRedraw`.)
Repository: kubernetes
Issue: Reconsider using etcd+chunking for reflector lists
Labels: sig/scalability,kind/feature,lifecycle/frozen

Filing issue for the discussion I brought up in SIG scalability meeting today, as I couldn't find one for it already.

**Background**:
Currently all our informers, which use reflectors underneath, list from apiserver's watch cache. This was a decision made quite some time ago to use watch cache instead of etcd - to avoid overloading etcd with several lists.

Now, since the watch cache doesn't support chunking (due to lack of history), informers make a full list (without chunking) to the apiserver. This is causing an issue that we recently encountered where multiple watches trying to list at the same time caused apiserver CPU/memory to spike quite a bit:

![Screen Shot 2019-09-12 at 10 33 22 AM](https://user-images.githubusercontent.com/4333971/64806881-f10c7d80-d548-11e9-9677-3eccb6ae66ca.png)

And indeed such a scenario can happen if for e.g the watch from apiserver to etcd doesn't receive an event before that resource version gets compacted from etcd:

```
E0824 09:43:50.201103 8 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
W0824 09:43:50.201169 8 reflector.go:256] storage/cacher.go:/pods: watch of *core.Pod ended with: The resourceVersion for the provided watch is too old.
W0824 09:43:51.201450 8 cacher.go:125] Terminating all watchers from cacher *core.Pod
```

And as a result when apiserver terminates all watches from the cacher, that caused multiple clients to relist at the same time, causing the resource spike on apiserver.

From our discussion, it seems that apiserver watch falling out of etcd window can happen in at least two scenarios currently:

- set of objects being watched are not changing frequently enough, causing that latest RV to go out of etcd's window. @wojtek-t - IIUC this issue will be solved with an etcd 3.4's feature you mentioned that's similar to our watch bookmark. Can you confirm?

- watch cache not able to handle the throughput of incoming events from etcd. This problem FMU still remains even after moving to etcd 3.4. So to avoid apiserver spike in such cases, IMO we should reconsider the option of allowing informers to list from etcd with chunking (since we have it now) instead of watch cache. It seems feasible, per Wojtek's thoughts, to be able to do this starting from etcd 3.4 as it has significant read concurrency improvements

**What would you like to be changed**:
- Switch to etcd 3.4
- Allow informers to list from etcd (with chunking)
- Scale test it

cc @kubernetes/sig-scalability-feature-requests @wojtek-t @liggitt @smarterclayton
Repository: pytorch
Issue: Support the AVX512 runtime dispatch
Labels: feature,low priority,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Enhance the runtime dispatch to support AVX512

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

We are optimizing some quantized kernels by using AVX2 or AVX512 instruction set. It gave significant performance win for server side quantized model. Currently in OSS, we already have support for dispatching for AVX and AVX2 in pytorch/aten/src/ATen/native/DispatchStub.h.  

## Pitch

<!-- A clear and concise description of what you want to happen. -->

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @jerryzh168 @jianyuh @dzhulgakov @raghuramank100 @jamesr66a
Repository: bitcoin
Issue: Syncing headers with feeler-peers
Labels: Brainstorming,P2P

It occurred to me that we should eliminate the distinction between feelers -- peers we connect to on average every couple minutes to test entries in addrman -- and the extra outbound peers we connect to if our tip is stale (#11560).  Instead, why not just sync headers with feeler connections, and if we happen to learn of a new block from that feeler when our tip had been stale, consider evicting an older connection (just as we do with our extra outbounds)?

It seems to me that this should increase the cost to an adversary trying to eclipse a node, because they'd need to control a large fraction of the addrman in order to withhold the most-work chain for any sizeable amount of time.

Moreover since we're already making these feeler connections already, it should be a small amount of additional bandwidth to sync headers with such a peer.  (Perhaps we should avoid doing this in IBD...?)

@EthanHeilman Any thoughts?
Repository: pytorch
Issue: Access data_ptr in RNN.cpp
Labels: module: rnn,triaged

https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/RNN.cpp#L598 is trying to access `data_ptr` of Tensor inside `TypeDefault` context. This won't work for backends like XLA. In general if we want to access `data_ptr`, it's preferred to be a backend implementation. 
In fact in this case it seems `batch_sizes` can be a `int[]` instead of `Tensor`. But we need to consider BC for this change. 
Related issue: https://github.com/pytorch/xla/issues/927
there's a PR but it's not a preferred way to fix: https://github.com/pytorch/pytorch/pull/26056 
cc: @gchanan 

cc @zou3519
Repository: flutter
Issue: Reference to "old widget" when navigating with PageRouteBuilder (or others)
Labels: c: new feature,framework,f: routes,P3,team-framework,triaged-framework

### Feature ###

The idea is to have `Navigator` save a reference or a copy of the current base widget when pushing a new one. Kinda like a Hero Widget. The added flexibility for transitions would make a lot of things possible!

PageRouteBuilder makes the "new widget" enter screen with an animation, but the "old widget" doesn't change at all.

Something like this is happening now: 

> Old Page ---> Transitions (new widget superimpose old one) ----> new Page

Currently you can make it slide using `CupertinoPageRoute`, but IMHO a builder should grant some more flexibility. 

I have successfully built this desired result once by passing my "old page" widget as an argument in my RouteSettings.
```
return PageRouteBuilder(
      transitionDuration: const Duration(milliseconds: 1000),
      pageBuilder: (context, animation, _) => widget,
      transitionsBuilder: (context, animation, _, child) =>
        leavingWidget == null ? 
          ScaleTransition(
            scale: animation.drive(CurveTween(curve: Curves.decelerate)),
            child: child,
          ) :
          Stack(
            children: [
              SlideTransition(
                position: Tween(
                  begin: Offset.zero, 
                  end: Offset(-1.0, 0.0),
                ).animate(animation),
                child: leavingWidget.widget,
              ),
              SlideTransition(
                position: Tween(
                  begin: Offset(1.0, 0.0),
                  end: Offset.zero, 
                ).animate(animation),
                child: widget,
              ),
            ],
          ),
        // if (?:) statement
      // transitionBuilder
    );
```
So the idea is to have some optimization on getting the `leavingWidget` (in this example I used `Navigator.pushNamed( _, arguments: this)` in a widget's state.

The above transition makes the "old widget" slide out of the screen as the new one enters it. It removes the feeling of "overlapping" for a feeling of "pushing away".

### Conclusion ###

Request to have Navigator hold a reference or copy to the old page widget when pushing a new one for more animation options.
Repository: angular
Issue: Adding a migration to replace TestBed.get with TestBed.inject
Labels: area: testing,freq2: medium,P5

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->


# 🚀 Feature request


### Command (mark with an `x`)
<!-- Can you pin-point the command or commands that are relevant for this feature request? -->
<!-- ✍️edit: -->
```
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
```

### Description


With the deprecation of `TestBed.get` (https://github.com/angular/angular/pull/32406), would it be a good addition to add a schematic to update the usages to `TestBed.inject`?

### Describe the solution you'd like

Something like the following?

https://github.com/angular/angular-cli/compare/master...timdeschryver:pr/testbed-migration?expand=1

### Describe alternatives you've considered

/
Repository: kubernetes
Issue: Migrate kubelet to use v1beta1 Events
Labels: sig/scalability,sig/node,kind/feature,sig/instrumentation,do-not-merge/hold,lifecycle/frozen

Now that the scheduler is migrated to new Events API, we can migrate the kubelet to emit events against the new API

This is part of #76674

List of the files that needs to be migrated:
```
./pkg/kubelet/kubelet.go
./pkg/kubelet/prober/prober.go
./pkg/kubelet/kubelet_pods.go
./pkg/kubelet/config/config.go
./pkg/kubelet/images/image_gc_manager.go
./pkg/kubelet/pod_workers.go
./pkg/kubelet/network/dns/dns.go
./pkg/kubelet/kuberuntime/kuberuntime_manager.go
./pkg/kubelet/active_deadline.go
./pkg/kubelet/oom/oom_watcher_linux.go
./pkg/kubelet/container/helpers.go
./pkg/kubelet/preemption/preemption.go
./pkg/kubelet/kubelet_node_status.go
./pkg/kubelet/cm/node_container_manager_linux.go
./pkg/kubelet/eviction/eviction_manager.go
./pkg/kubelet/images/image_manager.go
```
/assign @tedyu @yastij @wojtek-t 

FYI @dims 

/sig instrumentation
/sig scalability
/sig node
/priority important-soon
Repository: flutter
Issue: Support Google AdSense in Flutter Web applications
Labels: c: new feature,would be a good package,customer: crowd,platform-web,package,c: proposal,P1,team-web,triaged-web

I tried to implement the next script(Google Ad-sense) at my Flutter Web site, but unsuccessful by now. The code is:
```
<script type="text/javascript">var nend_params={"media":00000,"site":000000,"spot":000000,"type":1,"oriented":1};0</script>
<script type="text/javascript" src="https://js1.nend.net/js/nendAdLoader.js"></script>
```
I understood, that Flutter web is currently in technical preview, but may be any route? Any advice and suggestions will be greatly appreciated.
Repository: flutter
Issue: There should be a test for interacting with an app after hot restart
Labels: a: tests,team,framework,P3,team-framework,triaged-framework

This path is a critical user journey, a test for it would have caught #40303.
Repository: pytorch
Issue: Tracing non-constant shapes is broken
Labels: oncall: jit,triaged

## 🐛 Bug

```
import torch
def foo(x):
    return torch.full(x.shape, 2)

x = torch.randn(3)
ge = torch.jit.trace(foo, x)
y = torch.randn(2, 5)
z = torch.randn([])

>>> ge(x).shape  # expected: 3
3
>>> ge(y).shape  # expected: (2, 5)
2
```

Tracing non-constant shapes seem to be broken if the shapes have different dimensions. I ran the above code on both linux and windows on master.

cc @suo @eellison
Repository: pytorch
Issue: Make GloballyUniqueId a common type for both rpc and dist autograd
Labels: triaged,better-engineering,module: rpc

Both RPC and Distributed Autograd require globally unique id in various places. #25499 partially implements that in `GloballyUniqueId` for RRefs, which can be shared between rpc and dist autograd after adding overflow checks and `int()` operator.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528
Repository: pytorch
Issue: Process fails with assertion error in magma-cuda100
Labels: module: dependency bug,needs reproduction,module: crash,triaged,module: linear algebra

## 🐛 Bug

During training the process dies with the following error:

```
...
global_step=101292, batch=73, batch_group=0:  30%|███████████████████▏                                             | 74/250 [05:01<10:25,  3.56s/it]
python: /opt/conda/conda-bld/magma-cuda100_1564975479425/work/interface_cuda/interface.cpp:897: void magma_queue_create_from_cuda_internal(magma_device_t, cudaStream_t, cublasHandle_t, cusparseHandle_t, magma_queue**, const char*, const char*, int): Assertion `queue->dAarray__ != __null' failed.
[1]    71261 abort      python train_reconstruct.py --resume 

```


## To Reproduce

Steps to reproduce the behavior:

1. Training a fairly large network while almost using all GPU memory (32GB on a Tesla V100).
1. The dataloader is rendering using OpenGL and then returning CPU tensors.

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

Program should not crash or if out of memory should return the relevant error.

## Environment

PyTorch version: 1.2.0
Is debug build: No
CUDA used to build PyTorch: 10.0.130

OS: Ubuntu 16.04.5 LTS
GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
CMake version: version 3.5.1

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration: 
GPU 0: Tesla V100-SXM2-32GB
GPU 1: Tesla V100-SXM2-32GB
GPU 2: Tesla V100-SXM2-32GB
GPU 3: Tesla V100-SXM2-32GB
GPU 4: Tesla V100-SXM2-32GB
GPU 5: Tesla V100-SXM2-32GB
GPU 6: Tesla V100-SXM2-32GB
GPU 7: Tesla V100-SXM2-32GB
  
Nvidia driver version: 410.48
cuDNN version: Could not collect
  
Versions of relevant libraries:
[pip3] numpy==1.17.1
[pip3] torch==1.2.0
[pip3] torchfile==0.1.0
[pip3] torchnet==0.0.4
[pip3] torchvision==0.4.0





cc @vishwakftw @SsnL @jianyuh
Repository: godot
Issue: Bug in display of 64-bit integers in the debugger
Labels: enhancement,topic:editor,confirmed

**Godot version:**
Godot_v3.1.1-stable_win64

**Issue description:**
I saw some suspicious values when using the debugger with my project, so I wrote the following snippet to investigate it (putting a breakpoint on the "pass" to look at the debugger):
```
   var r     := RandomNumberGenerator.new()
   var seeds := []
   var nums  := []
   r.randomize()
   for i in 5:
      nums.append(r.randi())
      seeds.append(r.get_seed())
   print(seeds)
   pass
```

The code works fine and printed (in one run):
[5283336804004298712, -9206889307139333561, 918266396063285450, -3754841591890928943, -1916577486000920820]

However, in the same run, when I looked at the seeds array in the debugger, what I saw was:
![godot_64b_debugger_bug](https://user-images.githubusercontent.com/53791975/64818645-7c523700-d57a-11e9-8875-5f046ca03faa.JPG)

The numbers in the debugger are obviously close, but no cigar.

I reran this code several times and this bug is consistent. The least-significant 2-4 digits are always wrong. The last digit is always zero and the second-to-last digit is usually zero (but not always).
Repository: vscode
Issue: "editor font zoom" does not persist
Labels: feature-request,accessibility,editor-core

- VSCode Version:1.38
- OS Version:Win 10

"Editor font zoom in" and "out" does not persist.  This is inconsistent with "view zoom" which does persist.  I understand that this is basically a shortcut to the "editor.fontSize" setting, but in that same vein, view zoom is just a shortcut to change the "window.zoom level" setting

Duplicate
1. "editor: font zoom out"
2. close & restart
3. font will have reverted pre-zoom size

Edit: updated title and text to reflect correct command "editor font zoom in/out"
Repository: rust
Issue: io::Stderr should be line-buffered by default, not unbuffered
Labels: T-libs-api,C-feature-request

`std::io::stderr` does no buffering at all by default, which means that a Rust program that uses the most obvious way to print error messages (`eprintln!`) will make individual `write` syscalls not only for each call to the macro, but for each subcomponent of the formatted string:

```plain
$ cat test.rs
fn main() {
  eprint!("partial ");
  eprintln!("line");
  eprintln!("a one and a two and a {} and a {}", 3, 4.0);
}
$ rustc test.rs
$ strace -e trace=write sh -c 'exec ./test 2> /dev/null'
write(2, "partial ", 8)                 = 8
write(2, "line\n", 5)                   = 5
write(2, "a one and a two and a ", 22)  = 22
write(2, "3", 1)                        = 1
write(2, " and a ", 7)                  = 7
write(2, "4", 1)                        = 1
write(2, "\n", 1)                       = 1
```

This behavior is undesirable in any context where multiple programs might be emitting error messages to the same terminal, logfile, or whatever at the same time (for instance, `make -j`) because partial lines from different programs can get mixed up with each other.   If stderr instead buffered up a full line and wrote it to the OS all at once, then different programs' output could only get mixed together on a line-by-line basis, which is usually much less confusing for a person reading the logs.

This behavior is also troublesome for programs that incrementally parse stderr output; for instance, it may be the reason why emacs' compilation-mode occasionally doesn't detect all of the diagnostics in `cargo build` output (I don't know if there's an existing bug report for this).

(There is a strong case for having `eprint!` flush out the partial line that it generates, but that could be handled inside of `eprint!`.)

(This is closely related to, but not the same as, #60673, which is about stdout.  Block buffering is _not_ normally appropriate for `stderr`, even when writing to a file.)
Repository: electron
Issue: Implement setAlwaysOnBottom
Labels: enhancement :sparkles:,component/BrowserWindow


### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem Description
I have a need to place a BrowserWindow to the very bottom, as it's supposed to be a desktop decoration. `type: 'desktop'` unfortunately won't work for me since I still want to be able to receive events on it, and it seems to not be supported on Windows.
 
### Proposed Solution
Implementing the `setAlwaysOnBottom` API that would do the opposite of the currently implemented `setAlwaysOnTop`.

### Alternatives Considered
N/A

### Additional Information
N/A

Thank you very much for maintaining this beautiful piece of software!
Repository: pytorch
Issue: There should be gating around BFloat16
Labels: module: performance,triaged,enhancement,module: bfloat16

As we add support for BFloat16 we should add some gating mechanism which will allow user to opt in to bfloat16 usage. The reason for this is that it will be a while till the devices which support bf16 will be mass available and before that will happen, the performance of bf16 operations wont be the best.
Repository: flutter
Issue: [web] allow controlling the window/iframe/screenshot parameters in engine tests
Labels: a: tests,team,engine,platform-web,P2,team-web,triaged-web

Screenshot tests in the engine use headless Chrome's default window size and pixel density, hard-code 500x500 iframe size, and always take the screenshot of the entire window. This makes tests less predictable. Let's allow tests customize this.

Let's try to capture as many of the following as we can:

- [ ] control window size
- [ ] control iframe size
- [x] control screenshot rect
- [ ] control screen pixel density
- [x] use the most predictable rasterizer available (although this might be the default already: https://bugs.chromium.org/p/chromium/issues/detail?id=765284)

/cc @ditman filing this issue so we can track it as part of the infra project. Feel free to adjust the description.