sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: opencv does not build on Mac OS X 10.12.2 with Xcode 8.2
Labels: feature,category: build/install,platform: ios/osx

my cmake version is 3.1.0
execute the shell:
python ../platforms/ios/build_framework.py ios

then output:
```
-- Setting up iPhoneOS toolchain for IOS_ARCH='armv7'
-- iPhoneOS toolchain loaded
-- The CXX compiler identification is unknown
-- The C compiler identification is unknown
-- Configuring incomplete, errors occurred!
See also "/Users/moon/dev/cpp-lib/opencv-master/build/ios/build/armv7-iPhoneOS/CMakeFiles/CMakeOutput.log".
See also "/Users/moon/dev/cpp-lib/opencv-master/build/ios/build/armv7-iPhoneOS/CMakeFiles/CMakeError.log".
-master/build/ios/build/armv7-iPhoneOS
CMake Error at CMakeLists.txt:98 (project):
  No CMAKE_CXX_COMPILER could be found.



CMake Error at CMakeLists.txt:98 (project):
  No CMAKE_C_COMPILER could be found.



============================================================
ERROR: Command '['cmake', '-GXcode', '-DAPPLE_FRAMEWORK=ON', '-DCMAKE_INSTALL_PREFIX=install', '-DCMAKE_BUILD_TYPE=Release', '-DIOS_ARCH=armv7', '-DCMAKE_TOOLCHAIN_FILE=/Users/moon/dev/cpp-lib/opencv-master/platforms/ios/cmake/Toolchains/Toolchain-iPhoneOS_Xcode.cmake', '-DENABLE_NEON=ON', '/Users/moon/dev/cpp-lib/opencv-master', '-DCMAKE_C_FLAGS=-fembed-bitcode', '-DCMAKE_CXX_FLAGS=-fembed-bitcode']' returned non-zero exit status 1
============================================================
Traceback (most recent call last):
  File "../platforms/ios/build_framework.py", line 88, in build
    self._build(outdir)
  File "../platforms/ios/build_framework.py", line 82, in _build
    self.buildOne(t[0], t[1], mainBD, cmake_flags)
  File "../platforms/ios/build_framework.py", line 138, in buildOne
    execute(cmakecmd, cwd = builddir)
  File "../platforms/ios/build_framework.py", line 34, in execute
    retcode = check_call(cmd, cwd = cwd)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['cmake', '-GXcode', '-DAPPLE_FRAMEWORK=ON', '-DCMAKE_INSTALL_PREFIX=install', '-DCMAKE_BUILD_TYPE=Release', '-DIOS_ARCH=armv7', '-DCMAKE_TOOLCHAIN_FILE=/Users/moon/dev/cpp-lib/opencv-master/platforms/ios/cmake/Toolchains/Toolchain-iPhoneOS_Xcode.cmake', '-DENABLE_NEON=ON', '/Users/moon/dev/cpp-lib/opencv-master', '-DCMAKE_C_FLAGS=-fembed-bitcode', '-DCMAKE_CXX_FLAGS=-fembed-bitcode']' returned non-zero exit status 1
```
Repository: You-Dont-Know-JS
Issue: Making *You Don't Know JS* easier to read
Labels: for second edition

@getify, I love your work on this amazing book! I know the topic of making *You Don't Know JS* has been brought up in the past, but I was hoping to open up some more discussion on it.

- https://github.com/getify/You-Dont-Know-JS/issues/635
- https://github.com/getify/You-Dont-Know-JS/issues/831
- https://github.com/getify/You-Dont-Know-JS/issues/869
- https://github.com/getify/You-Dont-Know-JS/issues/537
- https://github.com/getify/You-Dont-Know-JS/issues/524
- https://github.com/getify/You-Dont-Know-JS/issues/725
- https://github.com/getify/You-Dont-Know-JS/issues/630

From https://github.com/getify/You-Dont-Know-JS/issues/635, it appears the main issue with using gitbooks is that it allows PDF exports, which O'Reilly does not permit.I was wondering if there's a way to leverage gitbooks or a similar technology, in a way that does not violate agreements with publishers. 

Here are a few thoughts - 

[Gitbook CLI](https://github.com/GitbookIO/gitbook-cli) lets you easily package and serve books written in Markdown. It requires a `SUMMARY.md` file to be supplied, listing chapters and paths to corresponding files. The tool does not automatically publish to [gitbook.com](gitbook.com), nor does it automatically export to pdf (although the option to export to pdf does exist). 

- Running `gitbook build` creates a directory containing the book packaged as html files. Users can read the book by opening `index.html`. This directory can be included in this repository, or served elsewhere ([Github Pages](https://pages.github.com) could be a neat solution). Including only the output of the command (html files) in the repo ensures end users do not have the ability to easily export to pdf.

- Another option to make this more accessible could be to include the `SUMMARY.md` file and a docker setup that runs `gitbook serve` in a docker container. An end user can simply run `docker-compose up` to serve the book locally and be able to read the book inside a browser. 

What do you and the wider community think about this? I'm happy to provide more information or examples if required. I know the contribution guide mentions that this repo is not primarily intended to optimize reading experience. Given that, what are your thoughts on forks?
Repository: react
Issue: [Fiber] Should we clear an error boundary's update queue whenever it captures an error?
Labels: Component: Core Utilities,Type: Discussion,React Core Team

Seems like we should at least do this on the root.
Repository: go
Issue: net: dns lookup sometimes fails with "no such host" when there are too many open files
Labels: Unfortunate,help wanted,NeedsFix

#### What did you do?
My network-intensive code would sometimes fail resolving domain names, returning "no such host" using the default resolver (pure go).The domains that fail resolving are valid domains that are successfully resolved using dig and the same dns server address.

I noticed that increasing the number of open files limit fix the issue.

I managed to reproduce the failure with:  https://play.golang.org/p/MEZUS8h-o5
```
go build test.go
ulimit -n 20 # Set open file limit to something low
$ ./test 
2017/01/10 11:01:11 lookup munic.io on 127.0.1.1:53: dial udp 127.0.1.1:53: socket: too many open files
$ ./test 
2017/01/10 11:01:11 lookup munic.io on 127.0.1.1:53: dial udp 127.0.1.1:53: socket: too many open files
$ ./test 
2017/01/10 12:01:12 lookup munic.io on 127.0.1.1:53: no such host

```


#### What did you expect to see?
Always "too many open files"

#### What did you see instead?
Sometimes Lookup returns "no such host" when it shouldn't.

#### Does this issue reproduce with the latest release (go1.7.4)?
I first noticed the problem with 1.7.3. I reproduced the problem on 1.8beta2.

#### System details

```
go version go1.8beta2 linux/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/costanzj/projects/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build335463609=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
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"
GOROOT/bin/go version: go version go1.8beta2 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.8beta2 X:framepointer
uname -sr: Linux 4.4.0-38-generic
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu GLIBC 2.23-0ubuntu5) stable release version 2.23, by Roland McGrath et al.
gdb --version: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
```
Repository: go
Issue: cmd/compile: fixedbug/issue10958.go failures
Labels: Testing,NeedsInvestigation,compiler/runtime

The `fixedbug/issue10958.go` test, introduced in 7f1ff65c3947b916cc4d0827fd8c1307d7efd7bf ( cmd/compile: insert scheduling checks on loop backedges), is flaky.

### What version of Go are you using (`go version`)?

`go version devel +7f1ff65 Mon Jan 9 21:01:29 2017 +0000 linux/amd64`

### What operating system and processor architecture are you using (`go env`)?

```GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="XXX/gocode"
GORACE=""
GOROOT="XXX/go1.7/go"
GOTOOLDIR="XXX/go1.7/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build124360425=/tmp/go-build"
CXX="g++"
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?

Ran `all.bash` 3 times on a CentOS 6.5 server.

### What did you see?

It failed reliably with:

```
##### ../test
# go run run.go -- fixedbugs/issue10958.go
signal: killed
```

It happened on the linux/mips64 builder too:

https://build.golang.org/log/3f4be6b0c792fd179683d0046a2e6f178f8928d2
Repository: TypeScript
Issue: Compiler API Example in Wiki fails to run as described
Labels: Docs

<!-- BUGS: Please use this template. -->
I am not able to use example provided at https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API#using-the-type-checker. It throws following exception:


```
-- typescript@2.1.4
node docGenerator.js interface.ts
C:\Users\...\node_modules\typescript\lib\typescript.js:33364
            if (location.kind === 70 /* Identifier */) {
                        ^
TypeError: Cannot read property 'kind' of undefined
    at Object.getTypeOfSymbolAtLocation
```
Repository: go
Issue: x/net/http2: support consuming PUSH_PROMISE streams in the client
Labels: Proposal,Proposal-Accepted,FeatureRequest

Go 1.8 will contain support for servers to produce PUSH_PROMISE streams, but there is no support for clients to receive them.

Specifically, it would be nice if proxies built with net/http/httputil's ReverseProxy to be able to proxy server pushes.
Repository: rust
Issue: Add some mechanism for catching structured exceptions on Windows 
Labels: O-windows,C-feature-request

There are a number of places where we are forced to catch these exceptions in Gecko (see MOZ_SEH_TRY). The usual reason is for handling some bug in code that we have no control over.

Structured exceptions are also used for naming threads on Windows so it would be nice to have that too.
Repository: go
Issue: cmd/gofmt: Slice literal condensed to one line and comment moved outside if comment is last line
Labels: NeedsFix

Perhaps a duplicate of #9460, but the issue discussion says it's restricted to `for` statements, and at the very least this is another symptom of the same problem.

### What version of Go are you using (`go version`)?
go 1.7.3

### What operating system and processor architecture are you using (`go env`)?
go playground

In my work, it's common to have a list of cases I want to run, and comments are a good way to remove them selectively. All of the following conditions format as is

````
// All on one line
cases := []int{1, 2, 3}
```` 
````
// Cases each on own line
cases := []int{
	1,
	2,
	3,
}
````
````
// Trailing comment in the list
cases := []int{
	1,
	2,
	//3,
}
````
````
// Trailing comment with newline at the start
cases := []int{
	1, 2, 3,
	//4,
}
````
````
// All items on the same line, with first commented
cases := []int{ // 1
	2, 3, 4}
````

But, in the specific case where there is no newline between the start of the slice and the slice items, and the comment is on a newline between the items and the trailing brace, the comment is moved outside of the slice literal.

Specifically:
````
cases := []int{1, 2, 3,
	//4,
}
````
Formats to:
````
cases := []int{1, 2, 3}//4,
````
Furthermore, newlines are kept if there are multiple trailing comments
````
cases := []int{1, 2, 3,
	//4,
	//5,
}
````
is formatted to
````
cases := []int{1, 2, 3}//4,
//5,
````

This is undesirable formatting, particularly this last case since the newline comment feels uncoupled from the literal.
Repository: go
Issue: cmd/compile: performance problems with many long, exported identifiers
Labels: ToolSpeed,NeedsInvestigation

### What version of Go are you using (`go version`)?

1.7, 1.8+

### What operating system and processor architecture are you using (`go env`)?

win64 and nix64

### What did you do?

Tried to compile 150MB of code in a single package. Really it was a simple main.go that referenced this huge package and I executed "go build" but it is the compile executable that consumed ridiculous resources. But this even happens in my case when I get the code down to half that size (~75 MB). Not removing inlining and/or optimizations only delays the extreme resource usage, it does not remove it.

### What did you expect to see?

A successful result and timid RAM usage that does not climb to extreme proportions and "streams" the build limited only by disk space of the result.

### What did you see instead?

Consumed proportional amount of memory to code size, running out of memory (Win) or swapping forever until receiving a kill signal (Nix).

I am afraid I cannot provide the large set of code at the immediate moment. But if necessary, I can build a go generator that generates a ton of interfaces, structs, and functions. Orig thread: https://groups.google.com/forum/#!topic/golang-nuts/sBBkQ1_xf2Q.
Repository: TypeScript
Issue: Add support for diagnostic severities
Labels: Suggestion,Needs Proposal,VS Code Tracked

TypeScript has added compiler options for lint level checks like `noUnusedParameters` or `noUnusedLocals` in tsconfig.json (which is goodness). Today when such an option is enabled then the corresponding issues are reported by TypeScript in the same way as semantic or syntax errors. There is no notion of severity. 

##  Background
We are using tslint to develop VS Code and we have used tslint rules to detect unused locals. TSLint rule failures are reported in VS code as warnings and we had the setup that lint style issue are shown as warnings and the typescript issues (syntax, semantic) are shown as errors. Now that typescript added more lint style checks we no longer get the distinction when developing between lint level warnings and semantic errors. The situation has become worse with tslint 4.0, there tslint has started to deprecate rules which are covered by TypeScript compiler options. This makes good sense, but it means we are now starting to see 'unused locals' reported as errors and no longer as warnings as we did before.

## Suggestion
Support that the user can define in the tsconfig.json whether a check enabled by compiler option should be reported as `error` or `warning`.

`eslint` supports to configure the severity of an option. Here is an example the [eslint documentation](http://eslint.org/docs/user-guide/configuring):

```json
{
    "rules": {
        "eqeqeq": "off",
        "curly": "warn",
        "quotes": ["error", "double"]
    }
}
```

// CC @waderyan @mjbvz
Repository: neovim
Issue: Fold improvements discussion
Labels: enhancement,needs:design,needs:discussion

I've been working to improve the terminal folding display and some things I think are LGTM:
- [x] multibyte display (so one can use '│' to replace the pipe,'▸' instead of + ▾ etc)
 see ![2017-01-11-130542_956x613_scrot](https://cloud.githubusercontent.com/assets/886074/21848343/92813ca8-d800-11e6-91b3-4eb969ec599f.png)
- [x] don't repeat initial folding character on wrapped lines
- [x] with the current code it should be easy to adjust dynamically the foldcolumn width depending on the nesting fold depth
- [x] character customization ? it's easy to change foldcolumn characters in the source but that might be a nice setting to have ? In fillchars ? 
- [ ] inline folds https://github.com/neovim/neovim/issues/9817 https://github.com/neovim/neovim/pull/12194
- [x] ex_fold should use visual block
   - [ ] support foldexpr
   - [ ] ability to save/restore folds with columns (`put_folds` , use https://github.com/vim/vim/issues/6004 or the API https://github.com/neovim/neovim/pull/11523)
   - [x] use 2 shades to differentiate the text on a line before/after the inline fold (added `FoldedLight` highlight)
   - [ ] deal with foldopen (now disabled to ease testing)
   - [ ] deal with concealcursor (folds ) otherwise cursor can move past end of line
   - [ ] (warn for wrong pos in match_add )
   - [ ] how to display inline folds on the foldcolumn ? (no display ?)
   - [ ] `:2,1fold` fails with `fdm=marker` because foldCreate uses start/end instead of start_rel/end_rel
   - [ ] take into account column when using zo,zc etc.
   - [ ] ability to click on an inline fold

But some aspects I am less confident with and would like some input:
- [ ] ~~multicell display ? I wonder if some multicell character can improve the foldcolumn look enough to justify the addition. Which character would you like (I could only find that one '＋') ?~~
- [ ] add nvim_create_fold() to API ? https://github.com/neovim/neovim/pull/11523
- [ ] help with folds UI externalization ? GUIs could draw better folds for sure. could be solved by api

Nb: as a reminder for myself: lines displayed on screen are generated by win_line and fold_line. Both functions write their result in `current_ScreenLine` which is copied later at the right offset.
fold_line fills `current_ScreenLine` via `copy_text_attr` calls but this function doesn't support multibytes characters. `screen_puts_len` is a powered up version of `copy_text_attr` that support multibytes characters BUT it can't write to 'current_ScreenLine' because it can't compute its offset.
Repository: go
Issue: proposal: spec: use zero receiver for value method embedded via nil pointer
Labels: LanguageChange,Proposal,LanguageChangeReview

Consider this program:

```go
package main

import (
	"fmt"
)

type Pointer struct{}

func (d *Pointer) IsNil() bool {
	return d == nil
}

type Danger struct {
	Pointer
}

func main() {
	var d *Danger
	fmt.Println(d.IsNil())
}
```

If a struct type embeds another struct type with pointer methods, the pointer method set of the outer struct (`*Danger` in this example) includes the pointer methods of the embedded value.

However, calling these embedded methods is dangerous: the mere act of computing the address of the receiver results in a nil panic (see https://play.golang.org/p/jfrCruVC6l).  (You can more clearly see that the panic occurs when computing the receiver address by using a method expression instead of actually calling the method: https://play.golang.org/p/629rZ7rs6l.)

This somewhat limits the usefulness of embedding for composition, as the caller must either know the concrete type in which the struct is embedded (https://play.golang.org/p/3ciUa4kiOQ) or use reflection to check whether the concrete pointer is nil before making the call (https://play.golang.org/p/zGDh6Hk5U9).

This style of embedding could be made significantly more useful by defining pointer methods on embedded structs to receive `nil` if the pointer to the struct in which they are embedded is `nil`.

Specifically, I propose to add the following sentence to https://golang.org/ref/spec#Struct_types:
> * If S contains an anonymous field *T, the method sets of S and *S both include promoted methods with receiver T or *T.  __Evaluating a call or method value of a promoted method with a nil *S receiver evaluates the corresponding *T method with a nil *T.__

The spec is currently a bit vague on the exact semantics of calls to methods obtained by embedding.  This proposal certainly represents a change to the language as implemented, but it is not obvious to me whether it is a "language change" in the Go 1 compatibility sense or merely a spec clarification.
Repository: kubernetes
Issue: Dynamically change loglevel of infrastracture components
Labels: sig/api-machinery,kind/feature,lifecycle/frozen

etcd has the ability to increase/decrease its running loglevel which is really useful in debugging individual operations. 

https://coreos.com/etcd/docs/latest/v2/admin_guide.html (see "Enabling Debug Logging" section)

It would be nice to support this for all of our components (apiserver, scheduler, etc.).

@kubernetes/sig-api-machinery-misc
Repository: kubernetes
Issue: kubectl should warn user if they attempt to authenticate to the cluster using an expired certificate
Labels: priority/backlog,kind/feature,sig/auth,sig/cli,lifecycle/frozen

<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->

**Is this a request for help?** (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):


**What keywords did you search in Kubernetes issues before filing this one?** (If you have found any duplicates, you should instead reply there.):

---

**Is this a BUG REPORT or FEATURE REQUEST?** (choose one):
Feature request

<!--
If this is a BUG REPORT, please:
  - Fill in as much of the template below as you can.  If you leave out
    information, we can't help you as well.

If this is a FEATURE REQUEST, please:
  - Describe *in detail* the feature/behavior/change you'd like to see.

In both cases, be ready for followup questions, and please respond in a timely
manner.  If we can't reproduce a bug or think a feature already exists, we
might close your issue.  If we're wrong, PLEASE feel free to reopen it and
explain why.
-->

**Kubernetes version** (use `kubectl version`):
v1.5.1

**Environment**:
- **Cloud provider or hardware configuration**: Kubernetes on self-hosted private cloud 
- **OS** (e.g. from /etc/os-release): CoreOS 1235.6.0
- **Kernel** (e.g. `uname -a`):  4.7.3-coreos-r2
- **Install tools**: 
- **Others**:


**What happened**:
When a user with an expired client certificate attempts to use `kubectl` to interact with a cluster, they get a very unhelpful error:
```
%  kubectl get pods
error: You must be logged in to the server (the server has asked for the client to provide credentials)
```
After a lot of digging, the user may discover that their client certificate has expired and needs to be renewed.   

**What you expected to happen**:
I expected to get a more helpful error.   The API service returned a `401 Unauthorized`, yet this is never shown to the user, except when verbosity is bumped up.

I'd like to see two improvements:

* Before attempting to connect to the API service, `kubectl` checks the TLS certificate to see if it the expiration date < current time.  If it has indeed expired, print a helpful message to the user.
* When an API request returns a 401 Unauthorized message, print a more helpful message, perhaps something along the lines of "Server response: client is not authorized to request this resource.  Please verify your authentication credentials and/or certificates for validity". 

**How to reproduce it** (as minimally and precisely as possible):
1. Generate a client certificate that expired before the current system time.
2. Attempt to use it with `kubectl` to interact with the cluster

**Anything else do we need to know**:
Repository: kubernetes
Issue: FEATURE REQUEST:  kubectl unset command
Labels: kind/feature,sig/cli,lifecycle/frozen

Since we have kubectl set command to configure the resources. Should we add the unset command to cancel some configs?
Repository: clean-code-javascript
Issue: What about Magic strings?
Labels: help wanted

Do you think that can be good to include something about magic strings?

**Bad:**
```javascript
let posts = getPostsFromCategory('sports');
```

**Good**:
```javascript
const categories = {
  sports: 'sports',
  economy: 'economy'
};

let posts = getPostsFromCategory(categories.sports);
```