sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: realworld
Issue: Realistic data for RealWorld?
Labels: Status: RFC,v2 changelog

I wonder if it's possible/feasible/helpful to fill the production db with more realistic data from some open data sets that might be floating around. It would look better in FE demos than "aaaaa", "sample title" etc... BE repos could also use it for testing their dbs. Just a thought.
Repository: go
Issue: spec: clean up initialization language
Labels: Documentation,NeedsInvestigation

The spec provides an value for uninitialized variables of some types, such as "The value of an uninitialized pointer is `nil`." This text is additionally redundant with the text at the end of the Variables section, which reads "A variable's value is retrieved by referring to the variable in an expression; it is the most recent value assigned to the variable. If a variable has not yet been assigned a value, its value is the zero value for its type."

However, there's an extra wrinkle here. This quoted text refers to assignment, but not to initialization. Initialization is not assignment (although expression initialization follows "the rules for assignments"). So we also need to make clear that expression initialization does count as assignment.
Repository: go
Issue: spec: un-conflate variables and values
Labels: Documentation,NeedsInvestigation

The notions of *variable* and *value*, although meaningfully distinct, are often conflated in the spec. Some examples:

1. Dynamic types are defined as a property of interface variables, but are properly a property of interface values. The definition of static type also treats elements of structs, arrays, and slices as variables (see next point).
2. There is a definition of structured type that provides that elements of slices, arrays, and structs and like variables. Putting aside the question of whether slices have elements or not, this is not true in any case of unaddressable arrays.
3. Pointers are defined as pointing to variables, not addressable values.
4. Variables of interface type are capable of storing values of any compatible type, but no mention is made of interface values.
5. "In other words, the switch expression is treated as if it were used to declare and initialize a temporary variable t without explicit type; it is that value of t against which each case expression x is tested for equality." does not seem like it actually clarifies anything to me; rather, it is just gymnastics to work around the possibility that values don't have a properly defined existence.

This is probably all of them, but I'm not sure.
Repository: pytorch
Issue: BatchNorm should use Bessel's correction consistently
Labels: module: nn,triaged,module: norms and normalization

Currently, Bessel's correction is applied to the running variance estimator in BatchNorm on [this line](https://github.com/pytorch/pytorch/blob/master/torch/lib/THCUNN/BatchNormalization.cu#L196) and the correction is not applied at train time. While the original paper for [BatchNorm](https://arxiv.org/abs/1502.03167) agrees with this, in the follow-up paper of the author, [Batch Renormalization](https://arxiv.org/abs/1702.03275), they state on page 2 when talking about BatchNorm during training:

> [...] the computation of the sample mean µ_B and sample standard deviation σ_B are part of the model architecture [...]

and on page 3 state:

> Batch Normalization, in fact, simply sets r = 1

where r is the ratio of minibatch standard deviation and estimated standard deviation, implying that during both training and testing, Bessel's correction is applied.

I think the approach for BatchNorm in Batch Renormalization makes more sense than unbiasing one variance but not the other, so I believe that PyTorch should allow an argument to BatchNorm that toggles this behaviour and perhaps consider switching the default. An argument would also bring visibility towards this implementation difference in Deep Learning frameworks.

Looking through some of the most popular DL libraries, I found no implementation that uses the unbiased variance during training and inference, but some that don't unbias either. Note that the former is essentially the same as the latter when the latter initializes gamma with the correction factor, so I imagine that they should behave mostly the same even without correcting gamma.
Some of the frameworks that don't unbias at all are: [Keras](https://github.com/fchollet/keras/blob/master/keras/layers/normalization.py#L182-L184), [Lasagne](https://github.com/Lasagne/Lasagne/blob/master/lasagne/layers/normalization.py#L297-L299), [TF-Slim](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/layers/python/layers/layers.py#L696-L697).
Some of course follow the original paper by unbiasing the running variance only: [Caffe](https://github.com/BVLC/caffe/blob/master/src/caffe/layers/batch_norm_layer.cpp#L143), [Theano](http://deeplearning.net/software/theano/library/tensor/nnet/bn.html).

Anecdotally, when biasing the running unbiased variances again by inverting Bessel's correction, I get statistically significant slightly better validation accuracies when using relatively small batch sizes (32) in densely connected networks.

cc @albanD @mruberry
Repository: go
Issue: spec: an uninitialized slice (and other types) is nil, yet a slice variable is initialized to its zero (nil) value
Labels: Documentation,NeedsInvestigation

I have two small issues with the definition of a slice type:

> A slice, once initialized, is always associated with an underlying array that holds its elements.

This is not true of a `nil` slice. Since this refers to initialization, it is talking about variables and not values. Changing this to "A non-`nil` slice value..." would probably fix this, since initialization of slices is already well-defined elsewhere.

>  The capacity is a measure of that extent: it is the sum of the length of the slice and the length of the array beyond the slice; ...

This is not true of a slice whose capacity has been explicitly reduced. This is easily fixed by removing the explicit definition of capacity here and then, in the section on slice expressions, explicitly saying that the capacity of the slice `a[low:high]` is `cap(a) - low`. This also solves an ambiguity in that the capacity of `a[:]` is not actually defined and, based on the quoted statement, could be argued to extend the capacity back of up that of the underlying array if `a` is a limited-capacity slice.
Repository: realworld
Issue: Support Bearer for authentication scheme
Labels: Status: RFC,v2 changelog

The RFC specification requires the use of '**Bearer**' as the authentication scheme. The '**Bearer**' scheme is also registered with the IANA. Most JWT packages and tools use '**Bearer**' as the default scheme.

http://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml
https://tools.ietf.org/html/rfc6750
https://tools.ietf.org/html/rfc7523
https://en.wikipedia.org/wiki/JSON_Web_Token
Repository: rust
Issue: Improve diagnostics for parse errors in proc macro output
Labels: A-diagnostics,A-parser,T-compiler,A-proc-macros

Currently we make no real effort to inform users of parse errors in procedural macro output: https://github.com/rust-lang/rust/blob/9c15de4fd59bee290848b5443c7e194fd5afb02c/src/libsyntax_ext/deriving/custom.rs#L105

People are stumbling on this in the wild: https://www.reddit.com/r/rust/comments/689ogb/how_to_debug_procmacro_derive_produced/

CC @nrc @jseyfried

I have some ideas on how to move forward but should we wait until #40939 lands? I don't think it's necessary since the changes would be (mostly) orthogonal.
Repository: go
Issue: runtime/pprof: nil pointer panic in TestMathBigDivide and android/arm
Labels: NeedsInvestigation,mobile,compiler/runtime

The Android/arm builder failed once:

https://build.golang.org/log/49d8e3585a3501d3f82d92c762aa3d5724d45198

with the stack trace:

````
--- FAIL: TestMathBigDivide (0.31s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xf738b874]

goroutine 53 [running]:
testing.tRunner.func1(0xd7038120)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/testing/testing.go:712 +0x22c
panic(0xf740cef8, 0xf74e1418)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/panic.go:489 +0x218
runtime/pprof.fprintStack(0xf74e4e68, 0xd700c000, 0xd74700f0, 0x2, 0x2)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:340 +0x54
runtime/pprof.profileOk.func1(0x1, 0xd74700f0, 0x2, 0x2, 0x0)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:183 +0xd4
runtime/pprof.parseProfile(0xd7038120, 0xd7002d00, 0x719, 0x890, 0xd6fb5ea4)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:97 +0x130
runtime/pprof.profileOk(0xd7038120, 0x0, 0x0, 0x0, 0xd7002d00, 0x719, 0x890, 0x0, 0x0, 0x88b1f, ...)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:181 +0x110
runtime/pprof.testCPUProfile(0xd7038120, 0x0, 0x0, 0x0, 0xf742a140)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:140 +0x11c
runtime/pprof.TestMathBigDivide(0xd7038120)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:349 +0x3c
testing.tRunner(0xd7038120, 0xf742a144)
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/testing/testing.go:747 +0xbc
created by testing.(*T).Run
	/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/testing/testing.go:789 +0x288
exitcode=2go_android_exec: adb shell rm -rf /data/local/tmp/pprof.test-31327
FAIL	runtime/pprof	5.818s
````

I'm filing this issue so that we don't forget and in case someone else have an idea why it happens.
Repository: youtube-dl
Issue: Allow to keep all intermediate files.
Labels: request

### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.05.01*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.05.01**

### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones

### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [x] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### Description of your *issue*, suggested solution and other information

Reference: https://github.com/rg3/youtube-dl/pull/12949#discussion_r114120437

Not all temporary files are covered by ```--keep-video``` and ```--keep-fragments```. For example, metadata files from #12949 or PhantomJS scripts from #12754. Once those PRs are merged, I hope there will be an option to leave all temporary files so that debugging is easier.
Repository: TypeScript
Issue: Enum not block-scoped given closure and --target es5
Labels: Bug

**TypeScript Version:**  nightly 2.4.0-dev.20170501

**Code**

```ts
let getE;
{
    enum E { A = 1 }
    getE = () => E;
}
{
    enum E { A = 3 }
}
console.log(getE().A);
```

**Expected behavior:**

Always prints `1`.

**Actual behavior:**

Prints `3` under `--target es5`.

This issue is similar to #15403 but requires a closure to reproduce. CC @rbuckton
Repository: opencv
Issue: Support for CODEC_ID_H264_OMX
Labels: feature,priority: low,category: videoio

##### System information (version)
- OpenCV => 3.2
- Operating System / Platform => Raspberry Pi

##### Detailed description

On the Raspberry Pi, OpenMax (h264_omx) can be enabled while compiling FFMPEG. However there doesn't seem a way with OpenCV to specify the h264_omx codec in the VideoWriter class.
https://github.com/opencv/opencv/blob/master/modules/videoio/src/ffmpeg_codecs.hpp
Repository: TypeScript
Issue: Flag boolean in comparison operator operands as errors
Labels: Suggestion,Help Wanted,Good First Issue

From https://github.com/Microsoft/TypeScript/issues/15444#issuecomment-298055832

```ts
var x: boolean, y: boolean;
if (x > y) {  // suspicious!
}
```
Repository: svelte
Issue: Equivalent of Vue's out-in transition mode
Labels: feature request,temp-stale

For elements that are positioned statically or relatively, intros that happen at the same time as outros can be problematic:

```html
{{#if foo}}
  <div transition:fade='{duration:1500}'>yep</div>
{{else}}
  <div transition:fade='{duration:1500}'>nope</div>
{{/if}}
```

![yep-nope](https://cloud.githubusercontent.com/assets/1162160/25594262/c932684c-2e8d-11e7-953d-81c9d4fd08c4.gif)

Vue has a nice solution to this — [transition modes](https://vuejs.org/v2/guide/transitions.html#Transition-Modes). Since Svelte doesn't have an equivalent of `<transition>`, the concept doesn't translate directly, but it would be nice to be able to express something similar without the hacky use of `delay`.
Repository: TypeScript
Issue: Cannot have array binding patterns without iterable extensions
Labels: Bug

**TypeScript Version:**  2.2.1 / nightly (2.2.0-dev.201xxxxx)

**Code**

```ts
declare function f([x, y]: [number, string]): void;
```

**Expected behavior:**

`src/a.ts(1,20): error TS1337: Destructuring is not allowed in a declaration.`

**Actual behavior:**

`src/a.ts(1,20): error TS2488: Type must have a '[Symbol.iterator]()' method that returns an iterator.`

For an object destructuring `{ x, y }: { x: number, y: string }` we currently give no error at all, but we probably should.
Repository: svelte
Issue: Staggered transitions
Labels: feature request,stale-bot,temp-stale

A common requirement is to *stagger* transitions:

![barchart](https://cloud.githubusercontent.com/assets/1162160/25594853/6b7732a2-2e90-11e7-9f30-09652e1109f9.gif)

In the GIF, it's been faked with an index and a delay:

```html
<g class='bars'>
  {{#each points as point, i}}
    {{#if show}}
      <rect
        in:grow='{delay: i*200}'
        out:fade
        x='{{xScale(i) + 2}}'
        y='{{yScale(point.birthrate)}}'
        width='{{ barWidth - 4 }}'
        height='{{ height - padding.bottom - yScale(point.birthrate) }}'
        ></rect>
    {{/if}}
  {{/each}}
</g>
```

But that doesn't work well if new items are added, since their indices will start at *n* rather than 0.

If the intro is aborted (`show` becomes false, in the example above), if we have staggered outros then we probably want to a) reverse the stagger (last-in-first-out), and b) ignore any intro transitions that haven't yet started, so that the subject of the most recently started intro transition starts to outro immediately. That would be very hard to do with delays.

Not sure what that would look like. It probably needs to be a separate directive — something like this (means 'start each intro transition 200ms after the last one, and each outro transition 50ms after the last one but go backwards'):

```html
<rect
  in:grow
  stagger:in=200
  stagger:out=-50
  ...
```

Something else you *might* want to do is supply a fraction rather than an absolute number. This variant means 'start each intro transition once the previous one is 80% done, but use a fixed 50ms interval for outros':

```html
<rect
  in:grow
  stagger:in=0.8
  stagger:out=-50ms
  ...
```

Any thoughts?
Repository: go
Issue: runtime/pprof: improve docs around short-lived processes
Labels: Documentation,help wanted,NeedsFix,compiler/runtime

### What version of Go are you using (`go version`)?
`go version go1.8.1 darwin/amd64`

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/v832043/Code"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.8.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/zj/hgnczfs53zg8s4_d_t686715y61ynl/T/go-build686693782=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
```

### What did you do?
Added basic CPU profiling code to `main()`:
```
f, err := os.Create("test.prof")
if err != nil {
	log.Fatal(err)
}
pprof.StartCPUProfile(f)
defer pprof.StopCPUProfile()
```
Then I ran my program and threw a load tester at it.

### What did you expect to see?
Data in `test.prof` after gracefully exiting my program.

### What did you see instead?
After heavily loading my program with a load testing tool I made I observed that no bytes were ever written to `test.prof`. It seems like there is no sampling being done at all...?
Repository: flutter
Issue: "Lost connection to device" randomly when not doing anything in particular
Labels: platform-android,tool,customer: crowd,P2,team-android,triaged-android

We should keep closer track of what adb is doing. Is it dying on us? The logs don't say.

```
[+1366 ms] I/flutter (26953): <some stuff i was printing to the console>
[  +13 ms] I/flutter (26953): <ditto>
[   +1 ms] I/flutter (26953): <ditto>
[        ] I/flutter (26953): <ditto>
[        ] I/flutter (26953): <ditto>
[+128298 ms] Service protocol connection closed.
[        ] Lost connection to device.
[   +1 ms] DevFS: Deleting filesystem on the device (file:///data/user/0/io.flutter.examples.gallery/cache/flutter_galleryIgEdy5/flutter_gallery/)
[ +251 ms] TimeoutException after 0:00:00.250000: Future not completed
[        ] 'flutter run' took 561,659ms.
[  +32 ms] ensureAnalyticsSent: 31ms
[        ] exiting with code 0
```
Repository: flutter
Issue: Add a doctor validator warning for multiple adb installations
Labels: team,tool,t: flutter doctor,P3,team-tool,triaged-tool

Just helped track down an issue an internal customer was having whereby multiple `adb` instances were fighting each other:

* `/usr/bin/adb` existed as part of the `adb` Debian package that was installed on the user's system.  It seemed to be restarting its server automatically when killed because of an entry in `init.d`
* `$ANDROID_HOME/platform-tools/adb` was the user's preferred `adb` instance and was also the instance detected by flutter tools since it lived in a proper SDK folder structure.

There was initially an issue whereby one `adb` client process would detect a mismatch between the client and server versions and restart the appropriate server, and in so doing, it'd echo a message to  the terminal that flutter tools mistook for a device line (fixed in https://github.com/flutter/flutter/pull/9693).

Once that issue was fixed, the two `adb` servers still seemed to be fighting each other, causing the preferred `adb` to show no connected devices even though there were devices connected.  The solution we eventually found for this was uninstalling `/usr/bin/adb` (via `sudo apt-get remove adb`)...

This experience, along with reports within the Flutter team of multiple `adb` instances not playing nicely with each other and with Flutter tools, means we probably want to add a doctor validator that will warn the user if multiple adb binaries are detected.
Repository: godot
Issue: Rendering is broken on UWP
Labels: bug,topic:rendering,topic:porting,confirmed,platform:uwp

Just as a note to remind that the renderer is not working on UWP. I managed to get a GLES3 context but it still doesn't work with 3D games.
Repository: three.js
Issue: toJSON() and fromJSON()
Labels: Suggestion

##### Description of the problem 
We have toJSON api.
As a consistency, I think we should have fromJSON.
It will be powerful for data management.
##### Three.js version

- [x] Dev

##### Browser

- [x] All of them
- [ ] Chrome
- [ ] Firefox
- [ ] Internet Explorer

##### OS

- [x] All of them
- [ ] Windows
- [ ] macOS
- [ ] Linux
- [ ] Android
- [ ] iOS

##### Hardware Requirements (graphics card, VR Device, ...)
Repository: kubernetes
Issue: Unit test for pkg/kubelet/remote
Labels: area/kubelet,kind/cleanup,sig/node,help wanted,lifecycle/frozen,needs-triage

There is no unit tests for pkg/kubelet/remote. We should add a fake runtime and add unit tests for the package.

- [x] Add a fake remote runtime #49762
- [ ] Add unit tests
Repository: go
Issue: encoding/base64: encoding is slow
Labels: Performance,NeedsFix

Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

go 1.8.1

### What operating system and processor architecture are you using (`go env`)?

amd64, darwin

### What did you do?

go test encoding/base64 --bench=BenchmarkEncodeToString

### What did you expect to see?

It should be possible to increase the speed of the encoder by 3 or 4 times by using SIMD instructions.  So ideally, I'd like to see something like

go test --bench=BenchmarkEncodeToString
BenchmarkEncodeToString-8   	  500000	      3777 ns/op	2168.51 MB/s
PASS

### What did you see instead?

BenchmarkEncodeToString-8   	  200000	     11393 ns/op	 719.01 MB/s
PASS
ok  	encoding/base64	2.406s