sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: nvm
Issue: NVM D
Labels: needs followup,installing nvm

<!-- Thank you for being interested in nvm! Please help us by filling out the following form if you‘re having trouble. If you have a feature request, or some other question, please feel free to clear out the form. Thanks! -->

- Operating system and version:
OSX 10.11.6
- `nvm debug` output:
No output from that command.  It just disappeared back to the command prompt.
<!-- do not delete the following blank line -->

```sh

```
sh-3.2

- `nvm ls` output:
<details>
<!-- do not delete the following blank line -->

```sh
         v9.3.0
default -> v0.10.32 (-> N/A)
node -> stable (-> N/A) (default)
unstable -> 9.3 (-> v9.3.0) (default)
iojs -> iojs- (-> N/A) (default)
```
</details>

- How did you install `nvm`? (e.g. install script in readme, homebrew):
install script
- What steps did you perform?
```sh
Als-iMac:.nvm alspohn$ nvm --version
0.25.1
Als-iMac:.nvm alspohn$ nvm use 0.25
N/A: version "v0.25" is not yet installed
```
- What happened?
It shows that -.25.1 is installed, but then says it isn't when I attempt to use it.
- What did you expect to happen?
I expected it to use 0.25.1
- Is there anything in any of your profile files (`.bashrc`, `.bash_profile`, `.zshrc`, etc) that modifies the `PATH`?
In .bash_profile: 
```sh
export NVM_DIR="/Users/alspohn/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm
```

<!-- if this does not apply, please delete this section -->
- If you are having installation issues, or getting "N/A", what does `curl -I --compressed -v https://nodejs.org/dist/` print out?
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 104.20.23.46...
* Connected to nodejs.org (104.20.23.46) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.nodejs.org
* Server certificate: COMODO RSA Domain Validation Secure Server CA
* Server certificate: COMODO RSA Certification Authority
* Server certificate: AddTrust External CA Root
> HEAD /dist/ HTTP/1.1
> Host: nodejs.org
> User-Agent: curl/7.43.0
> Accept: */*
> Accept-Encoding: deflate, gzip
>
< HTTP/1.1 200 OK
< Date: Mon, 01 Jan 2018 17:13:41 GMT
< Content-Type: text/html
< Connection: keep-alive
< Set-Cookie: __cfduid=d8eab5992bf4a8489965a9e0269abfdac1514826821; expires=Tue, 01-Jan-19 17:13:41 GMT; path=/; domain=.nodejs.org; HttpOnly
< CF-Cache-Status: EXPIRED
< Vary: Accept-Encoding
< Expires: Mon, 01 Jan 2018 21:13:41 GMT
< Cache-Control: public, max-age=14400
< Server: cloudflare-nginx
< CF-RAY: 3d671c525ce94219-MSP
< Content-Encoding: gzip
<
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host nodejs.org left intact
-bash: HTTP/1.1: No such file or directory
<!-- do not delete the following blank line -->

```sh
```
</details>
Repository: rust
Issue: What to do about repr(C, simd)?
Labels: C-enhancement,A-FFI,T-compiler,A-SIMD,F-simd_ffi,A-repr

Currently, `repr(C, simd)` warns about "incompatible representation hints", but leaving off the `repr(C)` triggers the FFI lint when the SIMD type is used in FFI.

Note that `#[repr(C)] #[repr(simd)]` does not warn only due to #47094. Most uses of SIMD in FFI this in the Rust source tree use two separate repr attributes, which is why they didn't trigger this warning so far.

There's two ways to resolve this:

1. Require `repr(C, simd)` for SIMD types used in FFI.
2. Say `repr(simd)` is sufficient for FFI (in principle -- there are other concerns that keep SIMD-FFI feature gated at the moment) and keep the warning about `repr(C, simd)`. It could optionally restricted to some simd types that are known to correspond to C types on the platform in question (e.g., permit `f32x4` but not `f32x3`).

cc @alexcrichton
Repository: vscode
Issue: when writing a new CompletionItemProvider it is very hard debug as to why the item is not being offered
Labels: feature-request,suggest

Whenever I try to write a new CompletionItemProvider, I always have to bang my head against the table many times because there are many rules which hide your item from the completion menu.

I get that these rules are needed, but it is often frustrating for a developer to just see his completion items disappear. Could we get some kind of `debug` mode for CompletionItemProvider so that we can more easily see what is going on with our Completion items?

It would be great to have it something like:

```javascript
class CompletionItemProvider {
  static debug = true
  provideCompletionItems(document, position: Position, token) {}
}
```

then VSCode would log all reasons why any completion item from this provider was hidden.
Could we have this feature please?
Repository: vscode
Issue: macOS: alt+i always inserts '^' character
Labels: upstream,keybindings,macos,upstream-issue-linked,chromium

- VSCode Version: 1.19.1 & 1.20.0-insider (f9115349ef09cfef2bed669680d10ac58b490dce)
- OS Version: macOS Sierra 10.12.6

Steps to Reproduce:

1. Assign keyboard shortcut "option+i" to a command such as 'Toggle Sidebar Visibility' or 'Go to Definition':
![image](https://user-images.githubusercontent.com/593118/34482307-6d6e4954-efb7-11e7-9ec1-f93e5aaebf5a.png)
2. Try the shortcut in the editor. Sometimes the shortcut works (correct behavior), other times, the 'ˆ' character is put in the text without the command working (incorrect behavior), and sometimes the command works but the 'ˆ' character is also inserted (incorrect behavior).

Reproduces without extensions: Yes

#22664 & #22894 might be relevant.

---

> 2022.12: Edited to add the upstream link:

**Upstream issue:** https://bugs.chromium.org/p/chromium/issues/detail?id=887519
Repository: go
Issue: runtime: memmove sometimes faster than memclrNoHeapPointers
Labels: Performance,NeedsInvestigation,compiler/runtime

Memory allocation using `make([]int, K)` is surprisingly slow compared to `append(nil, ...)`, even though `append` does strictly more work, such as copying.

```
$ cat a_test.go
package main

import "testing"

const K = 1e6
var escape []int

func BenchmarkMake(b *testing.B) {
	for i := 0; i < b.N; i++ {
		escape = make([]int, K)
	}
}

var empty [K]int

func BenchmarkAppend(b *testing.B) {
	for i := 0; i < b.N; i++ {
		escape = append([]int(nil), empty[:]...)
	}
}

$ go version
go version devel +6317adeed7 Tue Jan 2 13:39:20 2018 +0000 linux/amd64

$ go test -bench=. a_test.go
BenchmarkAppend-12    	    1000	   1208800 ns/op
BenchmarkMake-12      	    1000	   1473106 ns/op
```

While reporting this issue, I initially used an older runtime from December 18 in which the effect was much stronger: 10x-20x slowdown.  But that seems to have been fixed.

Curiously, this issue is the exact opposite of the problem reported in https://github.com/golang/go/issues/14718 (now closed).
Repository: flutter
Issue: Flutter Inspector on device UI polish: visual change when entering select mode.
Labels: c: new feature,framework,f: inspector,P2,team-framework,triaged-framework

Show a mode change when first entering inspect mode (there’s no visual difference currently, so it’s not always clear to the user that clicking the inspect button did anything).
For example, show target icons in the corners of the screen.
Repository: flutter
Issue: Display of debug paint for selected widgets in the inspector
Labels: c: new feature,framework,f: inspector,P3,team-framework,triaged-framework

This will require a refactor of the binding code it flutter so that we have hooks in the appropriate places. User story is visually seeing padding, alignment, and other debug paint data for the selected widget where it is easily understandable as compared to the current behavior of seeing debug paint information for all widgets where the data displayed is overwhelming and often overlapping.
Repository: flutter
Issue: Better debugging of overflow issues using the inspector
Labels: framework,f: inspector,P3,team-framework,triaged-framework

Make sure red overflow error areas are always easily clickable bringing you directly to a description of the issue.
Also consider making it possible to jump directly from an overflow exception in the console to inspecting the associated node.
Git clone https://github.com/sergiandreplace/planets-flutter
Try to run it against Android with flutter run
Get this error: A RenderFlex overflowed by 2.0 pixels on the right.
Expect to be able to select the error area on device and jump to the appropriate widget and error property in the inspector.

Example overflow issue YAQS 4933234833227776
Repository: youtube-dl
Issue:  Add support for Adobe Pass Auth TV Provider Midco
Labels: tv-provider-account-needed

## Please follow the guide below

- [x ] I've **verified** and **I assure** that I'm running youtube-dl **2017.12.31**

### Before submitting an *issue* make sure you have:
- [x ] At least skimmed through the [README](https://github.com/rg3/youtube-dl/blob/master/README.md), **most notably** the [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

---



I noticed that my cable provider (Midcontinent) is not supported by youtube-dl although it appears to be adobe-pass tv provider. It is 49% owned by comcast so I'm hoping it's similar in some way for the setup but not sure. My credentials only work on midco.net and not comcast's xfinity for example. Any help would be appreciated. Thank you so much. :)
Repository: rust
Issue: Incorrect warning about unused const
Labels: C-enhancement,A-lints,A-diagnostics,T-compiler,WG-diagnostics

In the following program:

```
const SIZE: usize = 4;

fn _f(arr: [i32; SIZE]) {
    for x in arr.iter() {
      println!("{}", x);
    }
}

fn main() {}
```

I get a warning about `SIZE` being unused:

```
warning: constant item is never used: `SIZE`
 --> src/main.rs:1:1
  |
1 | const SIZE: usize = 4;
  | ^^^^^^^^^^^^^^^^^^^^^^
  |
```

It seems to me that this warning isn't correct, since `SIZE` is used in the signature of `_f`
Repository: pytorch
Issue: Assert that some tests must not be skipped under certain CI configurations
Labels: high priority,module: ci,module: tests,triaged,quansight-nack

It seems pretty easy to accidentally misconfigure one of our CI environments, and consequently fail to run a test. It would be great if we could somehow either:

1. Assert that all tests eventually get run under some configuration (not sure how to do this)
2. Assert that in a given CI environment, some test must not be skipped

That way, an env misconfiguration turns into an error, rather than just some more tests start getting skipped.

cc @ezyang @gchanan @zou3519 @bdhirsh @heitorschueroff @seemethere @malfet @walterddr @pytorch/pytorch-dev-infra @mruberry @VitalyFedyunin
Repository: flutter
Issue: Build Android artifacts on Windows
Labels: c: new feature,engine,platform-windows,P3,team-engine,triaged-engine

Currently, we can only build host artifacts (like `gen_snapshot` and `flutter_tester`) on Windows. We do not support building artifacts on Windows that are supposed to run on other platforms (e.g. the engine for Android).
Repository: rust
Issue: Diagnostics for conversions erroneously say that 'as' only works between primitive types.
Labels: C-enhancement,A-diagnostics,T-compiler,D-papercut,D-incorrect

See https://play.rust-lang.org/?gist=7194dac428b4355e3f2872e9c0206800&version=stable

The note says "an `as` expression can only be used to convert between primitive types. Consider using the `From` trait", but as show by the expression `Baz as i32`, this is not true.
Repository: go
Issue: syscall: use Windows FILE_FLAG_BACKUP_SEMANTICS in remaining places (Open)
Labels: OS-Windows,NeedsInvestigation

Hi,

`FILE_FLAG_BACKUP_SEMANTICS` is an optional flag to the Windows `CreateFile` API. It allows accessing files when privilege would be denied by normal Windows ACLs, except for that the user account has the `SE_BACKUP_NAME` privilege. If the calling user account does not have this privilege, adding this flag has no impact to behaviour nor performance.

Go already uses `FILE_FLAG_BACKUP_SEMANTICS` in some CreateFile calls (e.g. `Readlink`, `Utimes`, `UtimesNano`, from issues #8090 and #10804) but not in other cases (notably `Open`). So it's inconsistent.

I would like to request that `FILE_FLAG_BACKUP_SEMANTICS` is added to the `Open` call in `src/syscall/syscall_windows.go`.

As well as fixing the inconsistency, this would allow Go users to open files on disk, in those cases where their permission to do so comes via `SE_BACKUP_NAME` instead of windows ACLs.

Thanks
mappu

More information:
- https://github.com/giuliano108/SeBackupPrivilege
- https://msdn.microsoft.com/en-us/library/windows/desktop/bb530716.aspx

### What version of Go are you using (`go version`)?
`go version go1.9.2 windows/amd64`

### Does this issue reproduce with the latest release?
Yes
Repository: flutter
Issue: use package: references in the assets section of a pubspec file
Labels: tool,c: API break,a: assets,P2,team-tool,triaged-tool

You can currently refer to assets from another package using the `packages/package_name/asset_name` format. We should move to using a `package:package_name/asset_name` format - this will be the same as other url references (like imports).
Repository: rust
Issue: Some debuginfo tests are not running
Labels: A-testsuite,A-debuginfo,T-compiler,C-bug

I noticed when adding a debuginfo test that nothing I did caused the test to fail. Tracing back this seems to have been caused by 3e6c83d which broke parsing of the command/check lines, leaving all tests passing without any checking.

PR #47155 runs them again and ignores the failing ones
Repository: rust
Issue: Command-line arguments are cloned a lot on Unix
Labels: I-slow,O-linux,C-enhancement,T-libs

The `std::sys::unix::args` module does a lot of allocation and cloning of command-line parameters:

1. On startup, `std::sys::unix::args::init` copies all of the command-line arguments into a `Box<Vec<Vec<u8>>>` (except on macOS and iOS).
2. When `std::env::args` or `args_os` is called, it eagerly copies all of the args into a new `Vec<OsString>`.

On non-Apple systems, this means there is at least one allocation and clone per argument (plus 2 additional allocations, for the outer `Vec` and `Box`) even if they are never accessed.  These extra allocations take up space on the heap for the duration of the program.

On both Apple and non-Apple systems, accessing any args causes at least one *additional* allocation and clone of every arg.  Calling `std::env::args` more than once causes *all* arguments to be cloned again, even if the caller doesn't iterate through all of them.

On Windows, for comparison, each arg is cloned lazily only when it is yielded from the iterator, so there are zero allocations or clones for args that are never accessed (update: at least, no clones in Rust code; see comments below).
Repository: TypeScript
Issue: export as namespace doesn't support nesting namespaces
Labels: Suggestion,In Discussion

<!-- BUGS: Please use this template. -->
<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->
<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->

I'm using rollup to generate a UMD module from my TypeScript source. It's part of a bigger product, so one component exports to a root namespace (e.g. `mylib`) and another exports to a namespace nested under that (e.g. `mylib.plugins.myplugin`). Rollup is generating the necessary UMD logic to walk down from the global scope creating namespaces as needed, but I can't model that in my TypeScript `d.ts` file.

The `export as namespace` syntax is working great in the first case, but not the second. It looks like TypeScript doesn't support nested namespaces for this purpose. Is this by design or just an omission?

**TypeScript Version:**  2.7.0-dev.20180103

**Code**: Two files, a `d.ts` containing an `export as namespace foo.bar` declaration and a script that references it.

*declaration.d.ts*
```ts
export var baz;

export as namespace foo.bar;
```

*app.ts*
```ts
console.log(foo.bar.baz);
```

Compile with: `tsc .\test.d.ts .\main.ts`

**Expected behavior:** The file compiles correctly to the following JS:

```js
console.log(foo.bar.baz);
```

**Actual behavior:** Error

```
declaration.d.ts(3,24): error TS1005: ';' expected.
```

If I change `declaration.d.ts` to use `export as namespace foo` (and update `app.ts` as needed), the compilation succeeds.
Repository: flutter
Issue: Consistent .gitignore for Dart and Flutter projects
Labels: tool,customer: crowd,P3,team-tool,triaged-tool

We should have a standard and consistent `.gitignore` file common to Dart and Flutter that combines the [recommendations currently on GitHub](https://github.com/github/gitignore/blob/master/Dart.gitignore) with those generated by flutter create (which are different). 

From [https://github.com/github/gitignore/blob/master/Dart.gitignore](https://github.com/github/gitignore/blob/master/Dart.gitignore):
```
# See https://www.dartlang.org/tools/private-files.html

# Files and directories created by pub
.packages
.pub/
build/
# If you're building an application, you may want to check-in your pubspec.lock
pubspec.lock

# Directory created by dartdoc
# If you don't generate documentation locally you can remove this line.
doc/api/
```

From `flutter create`:
```
.DS_Store
.atom/
.idea
.packages
.pub/
build/
ios/.generated/
packages
pubspec.lock
.flutter-plugins
```

Other relevant fodder:
https://github.com/github/gitignore/blob/master/Global/JetBrains.gitignore
https://github.com/github/gitignore/blob/master/Global/VisualStudioCode.gitignore
https://github.com/github/gitignore/blob/master/Global/Xcode.gitignore
Repository: vscode
Issue: [html] extract class name to css file
Labels: feature-request,html

Steps to Reproduce:

1. click &lt;html&gt; tag;
2. light icon showing, click to show extract menu: 
    menuitem: extract class name to style tag;
    menuitem: extract class name to css file;

demo:
```
<!DOCTYPE html>
<html>
<head>
</head>
<body>
   <div class="a">
      <div class="a-1">
      </div>
   </div>
   <div class="b">
       <div class="b-1">
       </div>
   </div>
</body>
</html>
```

extract result:
```
.a {
}
.a-1 {
}

.b {
}
.b-1 {
}
```
Repository: rust
Issue: Stabilize -Z sanitize
Labels: T-compiler,C-feature-request,A-sanitizers

Hi,

I would really like to see -Z sanitize options available in stable rust. 

Today they are available in nightly. I have used them for 6 months in the 389 Directory Server project in a production ldap environment as part of the code IO event path. I have exercise the leak and address sanitize options extensively, used them to find many FFI safety issues, and tested multiple build types (exec, dylib, more).

The sanitizer support is very important for FFI assertions during development where a code base uses Rust and C in some form. It allows strict analysis of behaviour, and finding where items are not droped for example.

An important reason for inclusion in stable is *distributions*. As a project, we often have the requirement to build debug builds with the compiler that ships in a distribution to reproduce problems. That means rustc stable that ships in products like fedora or RHEL. 

If -Z sanitize isn't in stable, we can't achieve this - and this adds a barrier to adoption. It adds a hurdle to our community inclusiveness as potential developers have more complex steps to follow to create a dev environment. I want to say "dnf install -y cargo rustc ..." and someone should be able to work. 

Many people have put a lot of time into sanitizer support, and today it's locked behind nightly. :( 

I would love to see this in stable as it brings great run-time analysis features to rust especially for FFI use cases, and having paths to stabilise debugging options into stable rustc will strongly aid adoptions of rust in distributions of linux. It's an advertised feature of the language on email lists, so to have this accessible to anyone would be a huge benefit.

I'm happy to do the coding to enable this, as well as documentation and examples, but I need some help and guidance to achieve this,

Thanks, 

See also:

https://github.com/rust-lang/rfcs/issues/670
https://github.com/rust-lang/rust/pull/42711
https://users.rust-lang.org/t/howto-sanitize-your-rust-code/9378
Repository: kubernetes
Issue: Modifying nodeSelector on StatefulSet doesn't reschedule Pods
Labels: kind/bug,sig/scheduling,sig/apps,lifecycle/frozen

/kind bug

**What happened**:
Changing nodeSelector of a StatefulSet doesn't trigger rescheduling of it's existing pods. I `kubectl apply` the StatefulSet below, and wait for it's Pods to get scheduled onto Nodes with label `node_type: type1`. Then I change the nodeSelector label to `node_type: type2` and do `kubectl apply` again. 

```
apiVersion: apps/v1beta1
kind: StatefulSet
metadata:
  name: sstest
  labels:
    app: sstest
spec:
  replicas: 2
  serviceName: "service"
  template:
    metadata:
      labels:
        app: sstest
    spec:
      nodeSelector:
        node_type: type1
      containers:
            - name: nginx
              image: k8s.gcr.io/nginx-slim:0.8
```

**What you expected to happen**:

I expect the Pods to be rescheduled to the type2 Nodes, but nothing happens. The Pods only get rescheduled if I manually kill them using `kubectl delete pod sstest-0`.

**How to reproduce it (as minimally and precisely as possible)**:

1. Create a cluster in which some nodes have the label `node_type: type1` while some other nodes have the label `node_type: type2`.
2. Apply the above StatefulSet definition to the cluster.
3. Change the nodeSelector from `node_type: type1` to `node_type: type2` in the StatefulSet definition file.
4. Apply the file again.
5. Kill a Pod manually to verify that it gets rescheduled to another node.

**Anything else we need to know?**:

I tested the same scenario with Deployments. In that case the rescheduling worked as expected.

**Environment**:
- Kubernetes version (use `kubectl version`):
```
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:28:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.4-gke.1", GitCommit:"04502ae78d522a3d410de3710e1550cfb16dad4a", GitTreeState:"clean", BuildDate:"2017-12-08T17:24:53Z", GoVersion:"go1.8.3b4", Compiler:"gc", Platform:"linux/amd64"}
```

- Cloud provider or hardware configuration: GKE
- OS (e.g. from /etc/os-release): cos
Repository: pytorch
Issue: [docs] Return value type hint to be specified in docs for torch.is_grad_enabled (i.e. -> bool)
Labels: module: docs,triaged

Including master docs: https://pytorch.org/docs/master/search.html?q=is_grad_enabled


cc @jlin27