sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Improve logging when AD controller lets kubelet attach volumes
Labels: priority/backlog,sig/storage,kind/feature,lifecycle/frozen

<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:
Add a lower-level log (2) and/or pod event (info level) whenever the attach detach controller decides to skip processing a volume and let kubelet handle the attaching.

**Why is this needed**:
The typical volume attach handling is done by the attach detach controller running in the master. 
 It used to be handled by kubelet, but was moved to a single controller in the 1.3 timeframe, and this configuration is not being used or supported in most configurations anymore. I would also like to deprecate this option, but that's [another discussion](https://github.com/kubernetes/kubernetes/issues/55517).

However, the mechanism to transition to controller attach detach uses Node annotations is not a reliable mechanism to communicate configuration between master and nodes, as the Node objects can be modified and annotations modified or dropped.  In these situations, it would be useful to surface a more visible message to make it easier for users to debug.

@kubernetes/sig-storage-feature-requests
Repository: TypeScript
Issue: Include sourcemaps in Typescript NPM package.
Labels: Suggestion,Awaiting More Feedback

## Search Terms
typescript.js.map typescript.js source map

## Suggestion
I would like `typescript.js.map` to be included in the distributed NPM package, along with the original sources.  This could be achieved either with `inlineSources: true` or by including the `src` folder in the NPM package.

## Use Cases
I'm working on a compiler transformer and this has resulted in me stepping through `typescript.js`.  Since source maps are not included, this results in me stepping through a 125,000 line JavaScript file.  Not only does my editor hate me for this and sometimes locks up, the code is significantly harder to read than the original TypeScript source code.

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: rust
Issue: pthread_cond_signal/pthread_cond_broadcast return EAGAIN after retrying 8192 times in macOS
Labels: O-macos,T-libs-api

Since OSX 10.7 (Lion), pthread_cond_signal and pthread_cond_broadcast return EAGAIN after retrying 8192 times.

- 10.7.0 (Lion):          http://www.opensource.apple.com/source/Libc/Libc-763.11/pthreads/pthread_cond.c
- 10.8.0 (Mountain Lion): http://www.opensource.apple.com/source/Libc/Libc-825.24/pthreads/pthread_cond.c
- 10.10.0 (Yosemite):     http://www.opensource.apple.com/source/libpthread/libpthread-105.1.4/src/pthread_cond.c
- 10.11.0 (El Capitan):   http://www.opensource.apple.com/source/libpthread/libpthread-137.1.1/src/pthread_cond.c
- 10.12.0 (Sierra):       http://www.opensource.apple.com/source/libpthread/libpthread-218.1.3/src/pthread_cond.c
- 10.13.0 (High Sierra):  http://www.opensource.apple.com/source/libpthread/libpthread-301.1.6/src/pthread_cond.c
- 10.14.0 (Mojave):       http://www.opensource.apple.com/source/libpthread/libpthread-330.201.1/src/pthread_cond.c
- 10.14.1 (Mojave/latest):       http://www.opensource.apple.com/source/libpthread/libpthread-330.220.2/src/pthread_cond.c

I'm not sure this is correct, ruby [retries until pthread functions don't return EAGAIN](https://redmine.ruby-lang.org/issues/5155).(This issue is written in Japanese)
Repository: go
Issue: syscall: Stat_t with different fields' name between Darwin and Linux
Labels: Unfortunate,NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$go version

go version go1.12.6 darwin/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
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/MC/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/MC/Golang/pkgs"
GOPROXY=""
GORACE=""
GOROOT="/Users/MC/Golang/go"
GOTMPDIR=""
GOTOOLDIR="/Users/MC/Golang/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/MC/Workspaces/qutoutiao/godis/go.mod"
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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/th/22jxv0q12c5c23v02rt67gg00000gp/T/go-build623000608=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

Access file `ctime` from `os.FileInfo`;

https://play.golang.org/p/LD80qQy5qyC

### What did you expect to see?

All `os.FileInfo.Sys()`  should have the same fields' name across OS.

### What did you see instead?

Within Linux OS, it should call `Stat_t.Ctim.Sec`; But under Darwin OS, you have `Stat_t.Ctimespec.Sec` in hand.
Repository: TypeScript
Issue: MediaQueryList.prototype.addListener & removeListener are marked as deprecated
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:** master

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

MediaQueryList addListener
addListener
MediaQueryList

**Code**

```ts
const listener = window.matchMedia("(max-width: 1000px)");
const handler = () => {};
listener.addListener(handler);
listener.removeListener(handler);
```

**Expected behavior:**

`addListener` and `removeListener` are "valid" signatures to invoke

**Actual behavior:**

`addListener` and `removeListener` are deprecated

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior --> 
https://www.typescriptlang.org/play/#code/MYewdgzgLgBANgS2gUzMgTjAvDA7gsAExFwDoBbAQymAAsBZZQhSgCgCJWqAPAWn0JRaALhgBGAAxSADtwCU7OQG4AUKEixalInAzYYrOdgB8MAN4BfVYhRp0pSoUIAZJFFQZWWnRmUqb7nak6MjkIABuyK62nt6EuujKQA

**Related Issues:** <!-- Did you find other bugs that looked similar? --> 
None

**Notes:**
This document describes the `MediaQueryList` interface: https://drafts.csswg.org/cssom-view/#dom-mediaquerylist-addlistener

It doesn't list `addListener` and `removeListener` as deprecated, does not give an indication that they will be deprecated in the future, it also does not say that you should use `addEventListener` and `removeEventListener` instead.

It did say that `addListener` and `removeListener` are direct aliases. 

**Source:**
https://github.com/microsoft/TypeScript/blob/master/lib/lib.dom.d.ts#L10018

**Why would I bring this up:**

Because **Safari** and Internet Explorer do not support `addEventListener` and `removeEventListener`, but they do support `addListener` and `removeListener`.

Because `addListener` and `removeListener` are deprecated it means that people are more likely to use the alternatives without looking at the issues with doing so. 

A lot of examples with the usage of `MediaQueryList` show `addListener` and `removeListener` usage, even the documentation on MDN: https://developer.mozilla.org/en-US/docs/Web/API/MediaQueryList#Examples
Repository: flutter
Issue: CupertinoSegmented control widget doesn't work as intended with SingleChildScrollView widget
Labels: framework,f: scrolling,f: cupertino,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-design,triaged-design

**CupertinoSegmentedControl** doesn't work properly under **SingleChildScrollView** if the child container becomes scrollable (when it exceeds the viewport and needs to scroll to see further).  Switch the segments for a few times to understand
[Code to reproduce](https://pastebin.com/PkCiZp5e)
Repository: TypeScript
Issue: Suggestion: Add built-in vanilla constructor interface
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

1. built-in constructor interface

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

Consider the below from the [official TS docs on decorators](https://www.typescriptlang.org/docs/handbook/decorators.html): 

```TypeScript
function classDecorator<T extends {new(...args:any[]):{}}>(constructor:T) {
    return class extends constructor {
        newProperty = "new property";
        hello = "override";
    }
}
```
vs:

```TypeScript
function classDecorator<T extends Constructor>(constructor:T) {
    return class extends constructor {
        newProperty = "new property";
        hello = "override";
    }
}
```

I suggest we have a built-in `Constructor` interface so we can save typing.

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

See above.

## Examples

<!-- Show how this would be used and what the behavior would be -->

See above.

## Checklist

My suggestion meets these guidelines:

* [x ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x ] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [ x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: TypeScript
Issue: Support Unicode RegExp property escapes
Labels: Suggestion,In Discussion

TypeScript currently doesn't transpile Unicode property escapes (of the form `\p{ID_Start}` or `\P{ASCII}`) in regular expressions.

It would be great if it did!

https://www.typescriptlang.org/play/?target=1#code/MYewdgzgLgBATgUwOYIB4wLwwPQB0AOA3gMrBwCW+UGA4oggNYC+2ArgNwBQokIANggB0fEEgAUiFKkFQE0MQHJAA8AKAlKvZA

## Search Terms

regexp, regular expression, Unicode, property escapes, ES2018

## Suggestion

Support transpiling Unicode property escapes in regular expressions. Examples:

```js
/\p{ID_Start}/u;
/\P{ASCII}/u;
/\p{Script_Extensions=Greek}/u;
```

## Use Cases

One particular use case is matching identifier characters in JavaScript parsers. This is currently commonly implemented as [a large script-generated regular expression pattern](https://github.com/jquery/esprima/issues/1979) (like in Esprima) or as [a magical-looking list of code point ranges](https://github.com/microsoft/TypeScript/issues/32213) (like in TypeScript itself). However, it would be [much simpler to use property escapes](https://github.com/tc39/proposal-regexp-unicode-property-escapes#other-examples).

```js
const regexIdentifierStart = /[$_\p{ID_Start}]/u;
const regexIdentifierPart = /[$_\u200C\u200D\p{ID_Continue}]/u;
const regexIdentifierName = /^(?:[$_\p{ID_Start}])(?:[$_\u200C\u200D\p{ID_Continue}])*$/u;
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: create-react-app
Issue: Clarify polyfilling and browserlist usage documentation
Labels: issue: proposal,tag: documentation

Hi,

The [docs about supported browsers](https://facebook.github.io/create-react-app/docs/supported-browsers-features) is not clear.

After reading it i still dont understand the following : 
- If the polyfills are not imported, what the browserlist field in package.json is used for ? 
- If i need to support ie11 (and Array.includes for example), what do i need to do exactly ?
- Is @babel/preset-env used to automatically require polyfills ?
- Moreover the [docs from @babel/preset-env](https://babeljs.io/docs/en/babel-preset-env#usebuiltins-entry) (included with preset react app) indicates to import @babel/polyfill which is now deprecated. `react-app-polyfill/stable.js` requires the correct package `core-js/stable` but is browserlist still used using this file ?

Thanks for your help
Repository: TypeScript
Issue: Code completion: suggest tokens from "paths" in tsconfig.json
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

Code completion; module


## Suggestion
## Use Cases

For those paths which contains no wildcard character, can we suggest tokens from module it points?

For example:

```json
{
  "baseUrl": '.',
  "paths": {
    "my-base-module": [
        "../../dest/base"
    ],
}
```

in the example, we can say that bare module specifier `"my-base-module"` is mapped to path `"../../dest/base"`, which is actually a .d.ts.

However, my IDE(Visual Studio Code) do not list available symbols in `"my-base-module"`,
such as, When I type:

```ts
const v: Ve // I 'm going to type Vec3, which is defined in "../../dest/base".
```

I hopo IDE can suggest `Vec3` and auto-complete the importing statement as:

```
import { Vec3 } from "my-base-module";
```

You may ask: Why don't you put `"../../dest/base"` in `"types"` option in `tsconfig.json`.

Well, the `"../../dest/base"` is just a library of me. It is indeed another Typescript project's output **bundle** file(bundling use rollup). It is bundled as a single module, which, in later, maybe registered as a SystemJS module with name `"my-base-module"` because I hope users of the library treat the library as a single JS module so they can write:

```
import /* xx */ from "my-base-module";
```

## Examples

As stated above, I would upload my example if it's needed.

## Checklist

My suggestion meets these guidelines:

* [-] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [-] This wouldn't change the runtime behavior of existing JavaScript code
* [-] This could be implemented without emitting different JS based on the types of the expressions
* [-] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [-] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: User touch and draw polygon over google map
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: pytorch
Issue: Tracing an RNN does not support torch.nn.utils.rnn.PackedSequence as input
Labels: oncall: jit,triaged

## 🐛 Bug

`torch.jit.trace` over a RNN (GRU, LSTM) does not work when you feed it with a PackedSequence (as the ones created by `torch.nn.utils.rnn.pack_padded_sequence`). However, this works in eager mode.

## To Reproduce

```python
import torch

torch.jit.trace(nn.LSTM(input_size=300,
                        hidden_size=32,
                        batch_first=False,
                        num_layers=2,
                        bidirectional=True),
                torch.nn.utils.rnn.pack_padded_sequence(torch.rand(10,2,300), torch.tensor([10,3]))
               )
```
Returns:
```
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-2-32df167805c9> in <module>
      6                         num_layers=2,
      7                         bidirectional=True),
----> 8                 (torch.nn.utils.rnn.pack_padded_sequence(torch.rand(10,2,300), torch.tensor([10,3]))
      9                 )
     10                )

~/anaconda3/envs/pytorch/lib/python3.6/site-packages/torch/jit/__init__.py in trace(func, example_inputs, optimize, check_trace, check_inputs, check_tolerance, _force_outplace, _module_class)
    686         traced = _module_class(func, **executor_options)
    687         traced._c._create_method_from_trace('forward', func, example_inputs,
--> 688                                             var_lookup_fn, _force_outplace)
    689     else:
    690         name = getattr(func, '__name__', 'forward')

RuntimeError: Only tensors and (possibly nested) tuples of tensors or dicts are supported as inputs or outputs of traced functions, but instead got value of type NoneType.
Value: None

```

## Expected behavior
In order to be able to feed variable length input to an RNN and export it to ONNX, support for either `torch.nn.utils.rnn.PackedSequence` or a Tuple with 4 elements (the 4 attributes a `PackedSequence` has) is needed when tracing RNNs is needed.

## Additional context
ScriptModule is not an option in some cases either; since a RNN layer has to be traced in order to export successfully to ONNX
Repository: pytorch
Issue: Move csrc/distributed/c10d/{comm,reducer} to libtorch.so
Labels: oncall: distributed,triaged

These classes should be part of `libtorch.so` but are currently part of `libtorch_python.so`.

cc @mrshenli
Repository: TypeScript
Issue: Offer an auto-import for unresolved shorthand-named object literal properties
Labels: Suggestion,Awaiting More Feedback

<!-- Please search existing issues to avoid creating duplicates. -->
suppose I have exported an object called `Foo` in `foo.js`, and in another file I want to use something like this:
```JavaScript
export default configure({Foo})
```
autocomplete will not show `Foo` and of course, will not auto import from that file.
to use auto import, I have to write the code like this:
```JavaScript
export default configure({Foo:Foo})
```
actually autocomplete shows `Foo`, But it doesn't auto import. it has `abc` icon.
could you support object shorthand in autocomplete?
<!-- Describe the feature you'd like. -->
Repository: godot
Issue: Tilemap_editor_plugin add tile information to item tooltip
Labels: enhancement,topic:editor

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if non-official. -->
3.2 or later feature proposal

**OS/device including version:**
<!-- Specify GPU model and drivers if graphics-related. -->
all

**Issue description:**
<!-- What happened, and what was expected. -->

### Resume:
There is no quick way to see information about the tiles when editing a tilemap. Item tooltip is a good place to get changed properties of the tile.

### Explanation:
Tileset information is shadowed when editing a tilemap. You need to find the resource in the inspector, click the resource, find the tile by name and open the folded properties... You have no feedback from the tile in tilemap editor (only the image, the name of the tile, and the number) nor in the inspector (once you click in the tileset resource, the tilemap editor is closed, and if you click in the tilemap node, the tileset resource is closed).

I find myself writing in the name of the tiles some information... and this is because there is no direct way to get that (open the resource all time is slow)

### Objetive:
Send useful tile information to the tooltip of the item in the tilemap editor item list.
 - Not empty shapes
 - Offsets different that 0,0 (if have shape)
 - Shape One Way
 - Z Index

### Alternative:
Instead having the name and the number of each tile in their item (that requires space), it can be great to have a rich text label on the bottom of the tilemap editor that can display the information of the selected tile... space is freed in the item list and some clarity gained.
Repository: flutter
Issue: Analyze generated code in flutter_tools 
Labels: a: tests,c: new feature,team,tool,P3,team-tool,triaged-tool

flutter_tools generates some dart code to run tests, see https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/test/flutter_platform.dart.

Unfortunately it seems like that generated code is never analyzed and currently has analyzer issues. We should add some kind of a test that runs the output of the code generator through the analyzer to ensure it's error/lint/hint free.

/cc @jonahwilliams
Repository: flutter
Issue: Update attach to not require a device
Labels: tool,c: proposal,P3,team-tool,triaged-tool

As we discussed with @jonahwilliams in the document, the device is required only so that we know how to do port forwarding, and for embedding Flutter on Java Swing we don't need this.