sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: encoding/base64: make encoding/base64.init() smaller and faster
Labels: Performance,NeedsDecision

### What version of Go are you using (`go version`)?
go version go1.9 darwin/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/a/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/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/m9/qtbxkp6s3p96fk54rln7qhj80000gp/T/go-build906670350=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

### What did you do?
review code from https://github.com/golang/go/blob/master/src/encoding/base64/base64.go#L96

### What did you expect to see?
var StdEncoding = Encoding{....}

### What did you see instead?
var StdEncoding = NewEncoding(encodeStd)

I think we can write a simple program to generate that Encoding golang code to Encoding{....} to make  encoding/base64.init() smaller and faster.
In current golang compile `NewEncoding(encodeStd)` in global variable will compile code into encoding/base64.init().
`Encoding{....}` in global variable will compile that data to some place.
Repository: ant-design
Issue: Calendar Day View (extend dateCellRender)
Labels: 🗣 Discussion,💡 Feature Request,Inactive,IssueHuntFest

### What problem does this feature solve?
I think it would be helpful to also have a day view for the calendar, not just month or year, so we can see and manipulate the data from dataCellRender.

I'm trying to build a calendar where users can add items/events per hour(s) on a specific day or on multiple days (repeating event, full week let's say).

At this moment, from what I understand, you can not select, edit or view a full item from dataCellRender.



### What does the proposed API look like?
I do not have code samples, but I believe that the first thing it would be a day switch (maybe even week), just as it's the case for month/year.  

With the day selected from the week/month view, when entering on the day view, the user would see rows for each hour. When you click an hour row, a modal or something like that would appear to add your data/content and it would be added into a list that contains the details for each hour.

Maybe the developers can choose how to insert & display the data/events per hour, but the actual really valuable thing it would be the view for a day, with selectable/manageable rows.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vue
Issue: <input> rerenders while changes affects only sibling elements
Labels: bug,has workaround

### Version
2.5.2

### Reproduction link
[https://codepen.io/anon/pen/OxKqbL?editors=1111](https://codepen.io/anon/pen/OxKqbL?editors=1111)

### Steps to reproduce
Please open codepen example and type something into input

### What is expected?
Input should not lose focus

### What is actually happening?
input rerenders and loses focus

---
happens only if there is such conditional elements exists before and after input. Workaround is to use v-show instead of v-if in such cases.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: react
Issue: React should recognize the `valueAsDate` property on DOM elements
Labels: Type: Feature Request,Component: DOM

The `valueAsDate` property on the ES6 definition of `HTMLInputElement` is not yet recognized by React. It should be, though.

The `valueAsDate` property relieves the pain of having to deal with both browsers that support HTML5 date inputs and those who don't; the former require the `value` property to be of the form `"YYYY-MM-DD"` and the latter require a nicely formatted date (e.g. `"MM/DD/YYYY"`) since the user will see exactly that. (React won't even allow that in conjunction with `type="date"`, though, and proclaim that the machine readable format should be used.) 
The browsers that do support HTML5 date input (should) alternatively support the date being passed in through the `valueAsDate` property. If we use that, we can always put a nicely formatted date in the `value` property. Pain relieved! (And also React should allow any format in the `value` property in that case.)

As indicated above, browser support is still lacky at best, even with the most avant garde browsers. Hence this is not an urgent issue for React. It will get relevant, though, and is herein duly noted.
Repository: three.js
Issue: Feature Suggestion : Sphere and Cylinder impostors shaders
Labels: Suggestion

Hi everyone,

I needed to be able to generate a very large number of spheres or cylinders. To do so, I've implemented a sphere impostor and a cylinder impostor shaders. Those shaders are generating pixel perfect objects with a reduced cost in memory.

This work has been developped thanks to this [scientific publication](http://reality.cs.ucl.ac.uk/projects/quadrics/pbg06.pdf)

I planned to add my work to ThreeJS but encountered problems with [Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=740560).

My shaders can now do the following : 
- use true impostors by using gl_PointSize in vertex shader
- use some quads to emulate the sprites (Chrome issue fix)

I don't really know where it will be better to add this to ThreeJS. I can either add this feature by adding it to /examples or /src.

By adding it to /examples, we may need to fix uniform updates from onBeforeRender callback #9927. By adding it to /src, I will be able to directly code uniform updates on WebGLRenderer.

Because those two possibilities are totally different, is it possible to know what do you prefer before going further ?

Thanks !
Repository: TypeScript
Issue: Use before declaration errors when using let statements within a switch case 
Labels: Bug

**TypeScript Version:**  2.5.3

**Code**

```ts
function test(value) {
    switch (value) {
        case 1:
            let foo = 10;
            break;
        case 2:
            foo = 20; // Runtime ReferenceError: foo is not defined
            break;
        default:
    }
}

test(2);

tsc --target es2015 (or higher)
```

**Expected behavior:**
This should probably produce a compile time error: `Block-scoped variable 'pen' used before its declaration.` on reference to foo in `case 2`.

**Actual behavior:**

The code type-checks and compiles fine, however, when running the es2015 transpiled output, you will receive a ReferenceError error at runtime. Ideally this type of error could be caught at compile time.
Repository: flutter
Issue: Add warning comment to Debug/Release.xcconfig files
Labels: platform-ios,tool,t: xcode,P3,team-ios,triaged-ios

We should add some warning boilerplate to the `Debug.xcconfig` and `Release.xcconfig` templates above the `#include "Generated.xcconfig"`. Something along the lines of:

```
// Generated.xcconfig is critical for Flutter builds and must be #included in all Flutter projects
#include "Generated.xcconfig"
```
Repository: flutter
Issue: Flutter iOS builds should verify that Generated.xcconfig is included in the configuration
Labels: platform-ios,tool,t: xcode,P3,team-ios,triaged-ios

The `FLUTTER_*` variables defined in `Generated.xcconfig` are critical to successfully building for iOS. These are used in at least two key places:
1. To locate the the `xcode_backend.sh` file in the build run-script phase.
2. Within of `xcode_backend.sh`, for the various Flutter build settings.

We should detect that this file is (transitively) included from the build configuration's `.xcconfig`. One way to do this might just be to use `xcodebuild -showBuildSettings` and verify that all required variables are set. That avoids parsing Xcode project files and tying ourselves to a proprietary file format that could change.
Repository: flutter
Issue: Verify that xcode_backend.sh snapshot build phase is in Xcode project
Labels: platform-ios,tool,t: xcode,P3,team-ios,triaged-ios

We should verify that the two xcode_backend.sh run-script build phases are present in the Xcode project when building for iOS.

There are two phases where we use this script:
1. Dart snapshotting phase: `xcode_backend.sh build`
2. Framework architecture-thinning phase: `xcode_backend.sh thin`

For the time being, even a quick grep with a regex might be a reasonable heuristic for spotting this.
Repository: flutter
Issue: Emit an actionable error message if FLUTTER_* not defined in Xcode run-script phases
Labels: platform-ios,tool,t: xcode,P3,team-ios,triaged-ios

If `Generated.xcconfig` has not been `#include`d in the Xcode project configuration, `FLUTTER_ROOT` is undefined and Xcode will be unable to locate `xcode_backend.sh`. In the `flutter create` project template, we should include something similar to the following boilerplate above the execution of the `xcode_backend.sh` script:

```
if [ ! -f "$FLUTTER_ROOT"/packages/flutter_tools/bin/xcode_backend.sh" ]; then
  echo "xcode_backend.sh not found"
  echo "FLUTTER_ROOT is '$FLUTTER_ROOT'"
  echo "Verify that your Xcode project is configured to use the Debug or Release profile"
  exit 1
fi
```
Repository: rust
Issue: std::process::Command hangs if piped stdout buffer fills
Labels: E-help-wanted,C-bug,T-libs,A-process

There's an issue on Windows when using `Stdio::piped()` for `stdout`.  If the child process writes too many bytes to stdout, it appears to get permanently blocked.  A minimal test case (echo 2049 blank lines to cmd) is:

```rust
fn main() {
    ::std::process::Command::new("cmd")
        .args(&["/c", "for /l %i in (1, 1, 2049) do @echo["])
        .stdout(::std::process::Stdio::piped())
        .status();
}
```

This hangs for me, but succeeds if only 2048 `echo`s are specified (which is why I'm suspecting it's related to filling the 4096-byte buffer).
Repository: go
Issue: go/types: some facts are missing after an error
Labels: NeedsInvestigation

The type checker `go/types` records various facts about well-typed trees. For example, `Uses` records the relationship between each "using" (non-defining) identifier and the object to which it refers. However, when the type checker detects certain kinds of errors, it does not attempt to record facts about the errant subtree.  This issue is a request that it work harder to record facts about errant subtrees.

By way of motivation, consider a tool for generating completions in an IDE. The input to such a tool is an unsaved editor buffer that usually fails to type-check, but the tool must nonetheless extract type information from the partial tree.  Consider the following fragment of a Go program in an unsaved editor buffer, with the current insertion point marked by a caret:

```
func _() {
	fmt.⁁
	test := 0
}
```

A completion tool should generate a list of qualified identifiers such as fmt.Print, fmt.Fprintf, and so on.  The parser ignores the newline and generates a tree containing `fmt.test := 0`, for which the type checker emits an error because each operand on the left of `:=` must be an identifier, not a qualified identifier (*ast.SelectorExpr). Having emitted the error, the type checker does not then visit the LHS subtree, so no `Uses` fact is recorded for `fmt`.  As a result, the completion tool simply doesn't work on programs of this form, which are fairly common.

The fix in this specific example is for the type checker, once it has reported the error, to visit the left subtree for side effects (facts) only, and ignore the resulting type. The more general problem is to find any other places in the type checker that skip visitation of a subtree after an error.
Repository: react
Issue: createPortal: support option to stop propagation of events in React tree
Labels: Type: Feature Request,Component: DOM

**Do you want to request a *feature* or report a *bug*?**
Feature, but also a bug cause new API breaks old `unstable_rendersubtreeintocontainer`

**What is the current behavior?**
We cannot stop all events propagation from portal to its React tree ancestors. Our layers mechanism with modals/popovers completely broken. For example, we have a dropdown button. When we click on it, click opens popover. We also want to close this popover when clicking on same button. With createPortal, click inside popover fires click on button, and it's closing. We can use stopPropagation in this simple case. But we have tons of such cases, and we need use stopPropagation for all of them. Also, we cannot stop all events.

**What is the expected behavior?**
createPortal should have an option to stop synthetic events propagation through React tree without manually stopping every event. What do you think?
Repository: angular
Issue: [Bug] strange behaviour with error handlers and events
Labels: freq1: low,area: common/http,type: use-case,P4

## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>

I am trying to implement a general error handler capable of showing me a message after each error and let the application continue, but when I catch errors coming from http,  something breaks.
## Current behavior
<!-- Describe how the issue manifests. -->
After I catch and rethrow an error from an http request, the application stops updating templates and everything stops working. If the error does not come from an http request (but comes from an observable), the message error updates fine.

## Expected behavior
<!-- Describe what the desired behavior would be. -->
No matter what the source of the error, the application should update and respond without problems


## Minimal reproduction of the problem with instructions

https://plnkr.co/edit/9vLZqf?p=preview

## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->


## Environment

<pre><code>
Angular version: 4.4.5
<!-- Check whether this is still an issue in the most recent Angular version -->

Browser:
- [x] Chrome (desktop) version 61 (64 bit)
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: v8.6.0
- Platform:  Windows 10 Creator Update

Others:
<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
Repository: opencv
Issue: Building against OpenBLAS complains about missing lapacke.h
Labels: category: build/install,category: 3rdparty

##### System information (version)
- OpenCV => 3.3.1
- Operating System / Platform => Ubuntu 16.04. (xenial)

##### Detailed description

It is not possible to build openCV against libOpenBLAS unless one also installs an additional LAPACK implementation that includes the ```lapacke.h``` header, e.g. ```liblapacke-dev``` on Ubuntu.

To me that does not look like the intended behavior and it might be explained by the fact, that OpenBLAS on Ubuntu only include ```cblas.h``` and ```f77blas.h``` as an header. 

On the other hand ```OpenCVFindOpenBLAS.cmake``` does not check for ```lapacke.h```, so it might just be the case that ```ocv_lapack_check()``` is too strict when it comes to OpenBLAS.

@alalek You seem to have some experience with this. Any thoughts on this?

##### Steps to reproduce

If I only install ```libopenblas-dev```, I get the following cmake output once ```ocv_lapack_check()``` inside ```OpenCVFindLAPACK.cmake``` is called:

```
-- LAPACK(OpenBLAS): LAPACK_LIBRARIES: /usr/lib/libopenblas.so
CMake Warning at cmake/OpenCVFindLAPACK.cmake:29 (message):
  LAPACK(OpenBLAS): CBLAS/LAPACK headers are not found in '/usr/include'
Call Stack (most recent call first):
  cmake/OpenCVFindLAPACK.cmake:155 (ocv_lapack_check)
  CMakeLists.txt:596 (include)

```

If I now install any LAPACK implementation that includes a ```lapacke.h```, e.g.: ```liblapacke-dev```, everything passes and OpenBLAS will be used:

```
-- LAPACK(OpenBLAS): LAPACK_LIBRARIES: /usr/lib/libopenblas.so
-- LAPACK(OpenBLAS): Support is enabled.
```
Repository: ant-design
Issue: Add support for css grid layout
Labels: 🗣 Discussion,💡 Feature Request,Inactive,IssueHuntFest

### What problem does this feature solve?
CSS Grid Layout is now supported in every modern browser.
Usage of Grid Layout will allow for more flexibility and ease of use than flexbox.

### What does the proposed API look like?
grid layput can be achieved without modifying the current api

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: puppeteer
Issue: Support response interception
Labels: feature,chromium

As of today, we have "request interception" that allows puppeteer to intercept and amend requests before they are sent to the server.

Similarly to this, it would be really handy to have "Response interception" that would allow to intercept and amend responses from server before they are delivered to the browser.
Repository: kubernetes
Issue: Admission webhook configuration API should report if the configuration is honored
Labels: sig/api-machinery,kind/feature,area/admission-control,priority/important-longterm,lifecycle/frozen

The webhook [api](https://github.com/kubernetes/kubernetes/blob/v1.9.0-alpha.1/staging/src/k8s.io/api/admissionregistration/v1alpha1/types.go#L152) doesn't tell if a webhook configuration is honored by the kube-apiserver or the extension apiservers. We should support it.

The problem is less critical for initializers, because users can observe objects's `metadata.initializers` to check if the initializer configuration is honored

cc @lavalamp @cheftako @kubernetes/sig-api-machinery-misc
Repository: thefuck
Issue: Doesn't handle quotes and arguments with spaces well
Labels: help wanted,hacktoberfest,HackIllinois

v3.24 using Python 3.5.3, on Ubuntu 17.04, GNU bash 4.4.7(1)-release.

Using an alias, but with no alias is indifferent:

    $ theheck "catt 'My File'"
    cat My File [enter/↑/↓/ctrl+c]
    
    $ theheck "catt My\ File"
    cat My File [enter/↑/↓/ctrl+c]
    
    $ theheck "ehco -e '\n'"
    echo -e \n [enter/↑/↓/ctrl+c]
    
    $ theheck "ehco -n $'\n'"
    echo -n $\n [enter/↑/↓/ctrl+c]

The debug output is here: https://pastebin.com/GjXPpQbs
Repository: TypeScript
Issue: Try enforcing contextual type of array literal elements
Labels: Suggestion,Breaking Change,Committed

Part of #19236 

**Code**

```ts
const s1: string[] = ["x", 3, null as any];
const s2: string[] = ["x", 3];
```

**Expected behavior:**
* `s1` should be an error
* `s2` should have an error span on `3`

**Actual behavior:**
* `s1` is not an error
* `s2` has an error span on `s2`, which makes it impossible to figure out which element is wrong

Hypothesis: When checking a contextually-typed array literal, if an element type isn't assignable to the contextual type, issue an error on *that element* and return `unknownType`
Repository: godot
Issue: Warn on connected functions without correct argument count
Labels: enhancement,topic:core,usability

**Operating system or device, Godot version, GPU Model and driver (if graphics related):**
MacOS, Godot 3.0 alpha

**Issue description:**
<!-- What happened, and what was expected. -->
Connecting a signal to a function that doesn't have the correct number of arguments means that the function is never called (and I haven't seen any warnings in the debugger being called).  Ideally, either the editor puts a lint warning up, or when attempting to call the function it complains that the function is invalid.

**Steps to reproduce:**
I connected a no-argument function to an animation_finished callback, which never is called.  Can upload examples if needed!

**Link to minimal example project:**
<!-- Optional but very welcome. You can drag and drop a zip archive to upload it. -->
Happy to make one if it helps; might poke around to see if I can cobble something together!
Repository: TypeScript
Issue: `SVGElement.className` should be read-only
Labels: Bug,Help Wanted,Domain: lib.d.ts

When trying to assign a value to it, the browser yells: `TypeError: Cannot assign to read only property 'className' of object '#<SVGAElement>'`.

Furthermore, the type of the `className` property is set as `any`, but it should be `SVGAnimatedString`.
Repository: rust
Issue: Use systems page size instead of a hard-coded constant for File I/O?
Labels: I-slow,C-enhancement,T-libs,A-io

Hi, I have a question regarding the following constant that is used throughout the `BufReader`:

https://github.com/rust-lang/rust/blob/6ccfe68076abc78392ab9e1d81b5c1a2123af657/src/libstd/sys_common/io.rs#L10

Shouldn't this variable rather be the page size for the system (determined at runtime) instead of 8KB hard-coded (for better IO performance)? This avoids that the system accidentally splits memory between pages that should really be contiguous on one page. For example, if my page size was 16KB, the system could accidentally allocate the memory in an unfortunate way so that the 8KB from the `BufReader` are now split across two pages. If it used 16KB pages, the system could map it 1:1 to a memory page. Why is the `BufReader` size hard-coded to 8KB?