sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Shared Dataset Functionality
Labels: module: dataloader,triaged,better-engineering

## 🚀 Feature

We want to build a unified data pipeline interface that offers building blocks for others to build on with the following objectives:
* Standardize datasets across domains.
* Offer flexible building blocks that can be combine to obtain other datasets.
* Enable datasets that do not fit in memory.
* Share code among domains.
* Facilitate parallel loading and processing of data.
* Decouple data loading and preprocessing/transformation.
* Offer static typing for datasets

## Motivation

* The Domains currently each have their own non-standard dataset structure that may also download the data. This duplicate efforts and adds complexity to the user.
* A common bottleneck when generating datasets is reading the data. We want to offer an interface that enables reading the data and running initial preprocessing while maximizing available computing resources utilization.
* We may want to leverage specialize libraries such as NVIDIA DALI.

## Additional Information

* [torch.utils.data](https://github.com/pytorch/pytorch/blob/master/torch/utils/data/)
* [tf.data](https://www.tensorflow.org/beta/guide/data) (e.g. uses dictionary for data point iteration)
* fast.ai's [basic_data](https://docs.fast.ai/basic_data.html) and [data_block](https://docs.fast.ai/data_block.html)
* [tnt](https://github.com/pytorch/tnt/blob/master/torchnet/dataset/dataset.py)
* [torchnet](https://github.com/torchnet/torchnet/tree/master/dataset)
* [~~torchdata~~](https://pypi.org/project/torchdata/)

Datasets:
* pytorch/text#624 pytorch/text#610 pytorch/audio#303 new datasets in domains
* pytorch/vision#1193 wants to select which metadata to return
* Internal: [overview](https://fb.quip.com/vlWwA35cmq0t) [torchtext](https://fb.quip.com/LncwAsC1cUZt) [core](https://fb.quip.com/B0PeACndlZEE) [torchvision](https://fb.quip.com/WGsUApsce6xN)
* [safe datasets](https://github.com/msamogh/nonechucks)

Dataloader:
* [torchaudio background iterator](https://github.com/pytorch/audio/blob/master/torchaudio/datasets/utils.py#L314)
* #24915 wants to re-use worker processes
* [FastDataLoader](https://github.com/pytorch/pytorch/issues/15849#issuecomment-573921048)
* [python 3.8 shared memory](https://docs.python.org/3/library/multiprocessing.shared_memory.html)
* Internal: [torchdata](https://fb.quip.com/ekJJAsYqMG7X) [gil](https://docs.google.com/document/d/1InJP79dWTIYj-xGVU65Y2r-K2HeL6t2l1xGDfKTU4Rw/edit#) [experiment](https://fb.quip.com/imVLAOdyJfAI) [DataLoader+Iterable](https://fb.workplace.com/groups/2162019300778793/permalink/3398854433474998/)

Features:
* #12672 wants to move collate_fn functionality to datasets
* #26547 wants distributed random sampling
* #28743 for sampler for iterable datasets
* pytorch/vision#1315 wants to apply an instance of random transform sequence to many images

cc @SsnL @fmassa @zhangguanheng66 @vincentqb @mrshenli
Repository: flutter
Issue: Allow setting the paint used on icons
Labels: c: new feature,framework,P2,team-framework,triaged-framework

For example, if you wanted to draw a stroked icon rather than filled, it is not possible without custom code today. We should allow specifying a foreground paint on icons, which would allow for specifying shaders or stroke/fill styles.
Repository: node
Issue: http2 compat missing writableFinished
Labels: http2

http2 compat is missing `writableFinished` for `OutgoingMessage`.

I tried fixing this myself but the whole finished flow for http2 compat confuses me.

- `finished` seems to be looking at a lot of different stuff (e.g. what does abort have to do with finish?).
- `'finish'` is emitted on `stream.on('close', ...)`.
- Sometimes we listen to `this.on('finish', ...)` and sometimes `stream.on('finish', ...)`.

I think someone with a clearer understanding needs to look at this.
Repository: flutter
Issue: Support full-screen for GLFW embedding
Labels: engine,a: desktop,e: glfw,P3,team-linux,triaged-linux

May be this implementation can be useful for Full Screen Apps
This Also requires minimize, maximize and close handles Api for App, so that we can do such tasks within Full Screen App
Repository: godot
Issue: Mouse input remains disabled even after re-enabling viewport input
Labels: bug,topic:input

**Godot version:** 
3.1.1.stable.mono.official



**OS/device including version:**
Windows 7 Professional Service Pack 1


**Issue description:**
After a SetDisableInput(true); if I try to enable again the viewport input with SetDisableInput(false); it won't be processed until I minimize and bring back the test window.


**Steps to reproduce:**
-Place a button on the scene;
-Disable the root viewport input;
-Enable the viewport input back, you should now see that, at a first look, the button doesn't catch the "hovered" state anymore, it cannot be clicked either, to solve this simply minimize the window and then recover the window back and the button will catch the mouse.
-After 3.2-alpha1 the input is recovered only if the mouse passes beyond the application canvas (see posts below)


**Minimal reproduction project:**
[InputBug.zip](https://github.com/godotengine/godot/files/3699253/InputBug.zip)
Repository: pytorch
Issue: Successive Layer Normalization in nn.Transformer
Labels: module: nn,triaged

In the nn.transformer.py module, the Transformer*Layer objects always have a layer norm at the very end of their forward method. However, the main Transformer object passes additional layer norms to both the TransformerEncoder and TransformerDecoder, effectively computing layer norm twice after the encoder, and twice after the decoder.

This seems wrong, I'm not sure there is a need for the extra layer norms inside Transformer.

Let me know if I'm missing something!


cc @SsnL
Repository: pytorch
Issue: Consider not checking in autogenerated core/{Tensor.h,TensorMethods.h}
Labels: module: build,module: cpp,triaged

ATen/core/Tensor.h, ATen/core/TensorMethods.h are autogenerated and checked in. However, checking in autogenerated files is a recipe for merge conflicts; I've ran into 3 in the past two weeks. I think this is because git thinks it can merge two of these files from different branches together but they get merged together in a way that isn't consistent with how they get autogenerated.

Potential solutions:
- stop checking in the autogenerated files
- Have some sort of landing hook (I'm not sure if this is possible) where if the generated file doesn't match what is checked in, then we block the land.

cc @gchanan @ezyang
Repository: flutter
Issue: Move desktop target platform artifacts out of host platform artifact directory.
Labels: tool,a: desktop,P3,c: tech-debt,team-tool,triaged-tool

The debug desktop target platform is currently cohabitating with the host platform artifacts of the same name. The debug target platform artifacts should be moved to `platform-debug` to match the reset of the artifact repository.

This could be done via a soft transition by upload the artifacts to both directories, and then removing the old upload once the tool is updated.
Repository: pytorch
Issue: [RPC] Make ProcessGroupAgent send task non-blocking
Labels: todo,triaged,module: rpc

@xush6528 pointed out in #23968 that we should make send task non-blocking in `ProcessGroupAgent`. It currently [waits](https://github.com/pytorch/pytorch/blob/0bf63f483a9cf4fbb63c680cb9b71e2dd09a110a/torch/csrc/distributed/rpc/process_group_agent.cpp#L181) until both preamble and payload send finishes. We could use a separate send GC thread that captures the `preamble`, `payload` and `ProcessGroup::Work` (all as `std::shared_ptr`) in a GC work, keep them in a queue, wait for completion in order, and destruct `preamble` and `payload` tensors. 

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera
Repository: rust
Issue: The rules for how non-Send local variables "infect" an async function, making its Future type non-Send also, are stricter than they need to be.
Labels: T-lang,C-feature-request,A-async-await,AsyncAwait-Triaged

Here's an example which I think should compile, but which doesn't (cargo 1.39.0-nightly 3f700ec43 2019-08-19):

```rust
#![feature(async_await)]

fn require_send<T: Send>(_: T) {}

struct NonSendStruct { _ptr: *mut () }

async fn my_future() {
    let nonsend = NonSendStruct { _ptr: &mut () };
    async {}.await;
}

fn main() {
    require_send(my_future()); // error: `*mut ()` cannot be sent between threads safely
}
```

The error is "`*mut ()` cannot be sent between threads safely", which is to say `my_future()` is `!Send`. I'm surprised by that, because the `nonsend` variable is never used after the `.await` point, and it's not `Drop`. Some other notes:

- Adding a `drop(nonsend)` call after the `let nonsend = ...` line doesn't help.
- This _does_ compile if swap the two lines in `my_future`. That is, if `nonsend` is created after the `.await` point, the future is still `Send`.

Are there any future plans to have the rustc look more closely at which locals do or do not need to be stored across an `.await`?
Repository: flutter
Issue: Provide a way to configure the open/close animation curves for the BottomSheet widget
Labels: c: new feature,framework,a: animation,f: material design,c: proposal,P3,team-design,triaged-design

<!-- Thank you for using Flutter!

     Please check out our documentation first:
      * https://flutter.dev/
      * https://api.flutter.dev/

     If you can't find the answer there, please consider asking a question on
     the Stack Overflow Web site:
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     Please don't file a GitHub issue for support requests. GitHub issues are
     for tracking defects in the product. If you file a bug asking for help, we
     will consider this a request for a documentation update.

-->
Repository: pytorch
Issue: [RPC] Fix logging initialization warning in ProcessGroupAgent
Labels: module: internals,triaged

## 🐛 Bug

On existing of RpcAgent process, the log lines shows that the logger was not initialized.

```Bash
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0820 23:57:09.260012 428932 process_group_agent.cpp:232] Shutting down ProcessGroupAgent w:3
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0820 23:57:09.259994 428921 process_group_agent.cpp:232] Shutting down ProcessGroupAgent w:2
WARNING: Logging before InitGoogleLogging() is written to STDERR
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0820 23:57:09.260094 428930 process_group_agent.cpp:232] Shutting down ProcessGroupAgent w:0
I0820 23:57:09.260102 428931 process_group_agent.cpp:232] Shutting down ProcessGroupAgent w:1
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0820 23:57:09.260113 428928 process_group_agent.cpp:232] Shutting down ProcessGroupAgent w:4
```

## Reason

Caffe2/C10 logging is used [here](https://github.com/pytorch/pytorch/blob/b6803d62fd996bcd5ec6775f2a898cdbf645a106/torch/csrc/distributed/rpc/process_group_agent.cpp#L232).

## Fix

In Caffe2 code base, logger is usually initialized by calling 
```
core.GlobalInit(["python", "--caffe2_log_level=0", "--caffe2_omp_num_threads=1"])
```

It calls [`InitCaffeLogging`](https://github.com/pytorch/pytorch/blob/c25e33789e45e20d3fa317f60e29bdbe49bffd28/c10/util/Logging.cpp#L153).
Repository: opencv
Issue: aligned allocation in c++17 dialect
Labels: priority: low,category: build/install,platform: ios/osx,incomplete

> Headers/core/utility.hpp:581:7: error: aligned deallocation function of type 'void (void *, enum std::align_val_t) noexcept' is only available on iOS 11 or newer
> 
> class ParallelLoopBodyLambdaWrapper : public ParallelLoopBody
>       ^
> 
> Headers/core/utility.hpp:598:26: note: in implicit destructor for 'cv::ParallelLoopBodyLambdaWrapper' first required here
> 
>     parallel_for_(range, ParallelLoopBodyLambdaWrapper(functor), nstripes);
>                          ^
> 
> Headers/core/utility.hpp:581:7: note: if you supply your own aligned allocation functions, use -faligned-allocation to silence this diagnostic
> 
> class ParallelLoopBodyLambdaWrapper : public ParallelLoopBody
Repository: rust
Issue: Improve bytes per second benchmark output
Labels: C-enhancement,T-compiler,T-dev-tools,A-libtest

I'm building a library that implements a somewhat slow compression algorithm and I wanted to see what sort of speeds I was getting. Using the benchmark I can get the speeds for some tests; but not for the slower ones:

```
test compress_large::level_0  ... bench:  10,848,110 ns/iter (+/- 343,409) = 1 MB/s
test compress_random::level_0 ... bench: 257,280,250 ns/iter (+/- 19,228,907)
```

It would be nice to have the speed output in other units, like KB/s and B/s. It could also be extended to produce GB/s if needed.
Repository: youtube-dl
Issue: is there have a way to skip vedio doesn't have subtitle?
Labels: question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [ y ] I'm asking a question
- [ y ] I've looked through the README and FAQ for similar questions
- [ y ] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

i want to download the video with subtitle instead of auto-subtitle, so i only use write-sub options, but it will download the vedio anyway, is there a way to skip those vedios without subtitles ?
Repository: rust
Issue: debuginfo/issue-22656.rs fails with LLVM/clang Assertion `Prior->FD->hasAttr<NoUniqueAddressAttr>() && "should not have reused this field's tail padding"' failed.
Labels: A-debuginfo,P-low,T-compiler,C-bug

I haven't been running debuginfo tests locally for a long while due to a variety of issues, but I was surprised to get only 1 failure, `src/test/debuginfo/issue-22656.rs` with LLDB:
```cpp
python2.7: /home/eddy/Projects/rust-2/src/llvm-project/clang/lib/CodeGen/CGRecordLayoutBuilder.cpp:603:
  void (anonymous namespace)::CGRecordLowering::clipTailPadding():
  Assertion `Prior->FD->hasAttr<NoUniqueAddressAttr>() &&
    "should not have reused this field's tail padding"' failed.
```

If I had to guess, LLDB was trying to compile something as C++, and probably ran into something that's different in Rust (is it synthesizing C++ `struct`/`union` definitions from DWARF?).

cc @michaelwoerister 

**EDIT**: this is the test, and, well, this looks like a regression?
https://github.com/rust-lang/rust/blob/bea0372a1a7a31b81f28cc4d9a83a2dc9a79d008/src/test/debuginfo/issue-22656.rs#L1-L49
Repository: TypeScript
Issue: Cannot use nesting computed property name in an interface
Labels: Bug

**TypeScript Version:**  3.5.1

**Code**

```ts
const enum Types {
    FOO = 0,
};

const Names = {
    [Types.FOO]: 'foo',
} as const;

interface Baz {
    [Names[Types.FOO]]: string;
}
```

**Expected behavior:**
No error

**Actual behavior:**
Error: A computed property name in an interface must refer to an expression whose type is a literal type or a 'unique symbol' type.

**Playground Link:** https://www.typescriptlang.org/play/index.html#code/MYewdgzgLgBApmArgWxgFQJ4Ac4RgbwFgAoGMmAMQHkqYBeGABgBoSBfAbhJNElgDkAhslz0CJcjADamHBAB01KgF0AXDADkAMxAgNrYmxiC8vaF2IkAlmChwATlsHA4MAEKCAXuNLkpQkQgZbFxFGmU1GGh7GwBzCzYgA
Repository: kubernetes
Issue: Give the proper reason for killing pods
Labels: sig/node,kind/feature

Add the reason the pod was killed, e.g. exceeded memory limit, liveness probe, readiness probe...

Kubelet outputs
"Killing container with id docker://your-example-application:Need to kill Pod"
Reason: "Killing"

This message is unhelpful when it comes to diagnosing why the pod was killed, and can be improved with the reason from Kubelet to aid debugging.
Repository: flutter
Issue: SwitchListTile style different based on subtitle
Labels: framework,f: material design,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,team-design,triaged-design

If I have a SwitchListTile with one line of subtitle, it works fine. All the SwitchListTile are the same height. 
As soon as the subtitle is longer and takes two lines, the SwitchListTile is even smaller than with one line. 

This is a very strange behaviour. Shouldn't it stay at least the same height as with one line?

Flutter version: stable, v1.7.8+hotfix.4
Repository: pytorch
Issue: torch.cuda.synchronize blocks CUDA execution on other threads using other devices.
Labels: module: cuda,triaged

## 🐛 Bug

In a situation in which different Python threads execute CUDA operations on different devices, calling torch.cuda.synchronize blocks CUDA executions on all threads, including those on other CUDA devices.

## To Reproduce

1. `git clone https://gist.github.com/c812a38a338878f5c02f6193511afc6a.git cudasync`
2. `cd cudasync/`
3. `OMP_NUM_THREADS=1 python cudasync.py` (produces trace file)

## Expected behavior

`torch.cuda.sync(device=my_device)` should not affect execution of CUDA operations on devices other than `my_device`.

## Environment

```
PyTorch version: 1.3.0.dev20190816
Is debug build: No
CUDA used to build PyTorch: 10.0.130

OS: Ubuntu 18.04.2 LTS
GCC version: (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
CMake version: version 3.12.2

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 9.2.88
GPU models and configuration:
GPU 0: Quadro GP100
GPU 1: Quadro GP100

Nvidia driver version: 410.79
cuDNN version: Could not collect

Versions of relevant libraries:
[pip] numpy==1.16.4
[pip] torch==1.3.0.dev20190816
[pip] torchvision==0.5.0a0+19315e3
[conda] blas                      1.0                         mkl
[conda] mkl                       2019.4                      243
[conda] mkl_fft                   1.0.12           py37ha843d7b_0
[conda] mkl_random                1.0.2            py37hd81dba3_0
[conda] pytorch                   1.3.0.dev20190816 py3.7_cuda10.0.130_cudnn7.6.2_0    pytorch-nightly
[conda] torchvision               0.5.0.dev20190816      py37_cu100    pytorch-nightly
```

## Additional context

Trace file: [cudasync.trace.gz](https://github.com/pytorch/pytorch/files/3525922/cudasync.trace.gz)

This probably isn't a GIL issue as it doesn't seem to happen when the other threads execute CPU PyTorch operations.

Perfetto link to trace: https://ui.perfetto.dev/#!/?s=76397c96cea6a47c45aed36cd84586cf54469d34089d3578afb7e795219229

Screenshot: 
![image](https://user-images.githubusercontent.com/69371/63443305-73af8a80-c42c-11e9-82f8-0ef765e55978.png)
Repository: node
Issue: `socket.setTimeout` destroys connection automatically
Labels: question,http,doc

<!--
Thank you for reporting a possible bug in Node.js.

Please fill in as much of the template below as you can.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify the affected core module name

If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you can.
-->

* **Version**: v10.15.3
* **Platform**: Windows 10 Pro 64-bit

<!-- Please provide more details below this comment. -->

When a socket timeouts via `socket.setTimeout()`, it is automatically destroyed, even though the [documentation ](https://nodejs.org/api/net.html#net_socket_settimeout_timeout_callback) states that it should not be.

> When an idle timeout is triggered the socket will receive a 'timeout' event but the connection will not be severed. The user must manually call socket.end() or socket.destroy() to end the connection.

Code to reproduce:
```
const http = require('http');

const server = http.createServer(function (req, res) {
});

server.on("connection", socket => {
    console.log('on connection');
    socket.setTimeout(2000, () => {
        console.log('on socket timeout', socket.destroyed);
    });
});

server.listen(3000);
```
Repository: TypeScript
Issue: `esModuleInterop` breaks circular imports
Labels: Bug

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.5.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

`./tsconfig.json`:

``` json
{
    "compilerOptions": {
        "esModuleInterop": true
    },
    "files": ["./src/main.ts"]
}
```

`./src/main.ts`

```ts
import { other } from './other';

console.log(other.foo1);
```

`./src/other.ts`

```ts
export const foo1 = 1;
export const foo2 = 2;

// Import *this* module as a namespace
// Unexpected error:
// Circular definition of import alias 'other'
import * as other from './other';

// Re-export the namespace as a named export
export { other };
```

(For context on why you might do this: [it allows you to give namespace imports a common name](https://medium.com/unsplash/named-namespace-imports-7345212bbffb).)

**Expected behavior:**

No error

**Actual behavior:**

Error (see code comment)
Repository: flutter
Issue: Instrumentation test plugin should report test results individually as they finish
Labels: a: tests,c: new feature,team,framework,f: integration_test,P3,team-framework,triaged-framework

Right now the instrumentation_test plugin batches up all the test results into a single result. It should report each individual Dart test as an instrumentation test result as soon as it finishes.
Repository: flutter
Issue: [camera] plugin – cannot select telephoto lens
Labels: c: new feature,p: camera,package,team-ecosystem,P2,triaged-ecosystem

There appears to be no way to select the telephoto lens on an iPhone 8+ using `camera: ^0.5.4`. It only shows two cameras, one front, one back.
Repository: godot
Issue: Improve Godot shutdown process on Android
Labels: enhancement,platform:android,topic:porting

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
Any version < 3.2
<!-- Specify commit hash if non-official. -->


**OS/device including version:**
Android
<!-- Specify GPU model and drivers if graphics-related. -->


**Issue description:**
PR #31521 provides a temp solution to properly shutdown Godot apps on Android by killing the entire app process.
The proper fix involves tracking down the native components that are initialized at startup and properly cleaning them at application shut down.
This is a more involved fix as it might involve multiple refactors across the codebase.
<!-- What happened, and what was expected. -->