sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Swagger spec: Incorrect response model for namespaces/{namespace}/pods/{name}/binding
Labels: kind/bug,sig/api-machinery,lifecycle/frozen

Swagger definition for "/api/v1/namespaces/{namespace}/pods/{name}/binding" is incorrect. 

The current definition is:

``` json
"/api/v1/namespaces/{namespace}/pods/{name}/binding": {
  "parameters": [
    ... ],
  "post": {
    ...
    "responses": {
      "200": {
        "description": "OK",
        "schema": {
          "$ref": "#/definitions/v1.Binding"
        }
      },
```

But the "/api/v1/namespaces/{namespace}/pods/{name}/binding" API actually returns a Status object, not a v1.Binding.

This was determined while attempting to write a Python application that acts as a custom scheduler: kubernetes-client/python#825
Repository: flutter
Issue: Support multiple entrypoints to Dart via flutter driver
Labels: tool,t: flutter driver,c: proposal,P3,team-tool,triaged-tool

If apps implement multiple entrypoints to their app via `@pragma("vm:entry-point")`, the `flutter drive` command still assumes the entrypoint is `main` and fails.

We need to be able to specify the name of the entrypoint to be executed among the parameters.
Repository: rust
Issue: Error message referring to non-existent variable: "cannot return value referencing local variable `__next`"
Labels: A-diagnostics,T-compiler,C-bug

Compiling the following code on stable result in an error message which is referring to a non-existent variable `__next`

```rust
use std::collections::HashMap;
use std::hash::Hash;

fn group_by<I, F, T>(xs: &mut I, f: F) -> HashMap<T, Vec<&I::Item>>
where
    I: Iterator,
    F: Fn(&I::Item) -> T,
    T: Eq + Hash,
{
    let mut result = HashMap::new();
    for ref x in xs {
        let key = f(x);
        result.entry(key).or_insert(Vec::new()).push(x);
    }
    result
}

```

The error message:

```
$ rustup run stable rustc --crate-type lib lib.rs
error[E0515]: cannot return value referencing local variable `__next`
  --> lib.rs:15:5
   |
11 |     for ref x in xs {
   |         ----- `__next` is borrowed here
...
15 |     result
   |     ^^^^^^ returns a value referencing data owned by the current function

error: aborting due to previous error

For more information about this error, try `rustc --explain E0515`.
```

`rustc --version --verbose`:
```
rustc 1.36.0 (a53f9df32 2019-07-03)
binary: rustc
commit-hash: a53f9df32fbb0b5f4382caaad8f1a46f36ea887c
commit-date: 2019-07-03
host: x86_64-unknown-linux-gnu
release: 1.36.0
LLVM version: 8.0
```
Repository: flutter
Issue: Add OnReject to DragTarget
Labels: c: new feature,framework,a: animation,P3,team-framework,triaged-framework

## Use case

Simply need a callback to occur when a Draggable is dropped on the DragTarget and gets rejected. Currently there is only 'onAccept'. I want to trigger some animation events and functions on rejection.

## Proposal
Just add extra property onReject to the widget DragTarget 'drag_target.dart' in packages/flutter/lib/widgets/
Repository: scrcpy
Issue: "pull from" mouse gesture
Labels: feature request

This really is a 'feature request', but using the scroll wheel from the mouse should initiate a swipe for the direction rolled. This would enable things like expanding the notification area, etc.
Repository: flutter
Issue: CupertinoActionSheet doesn't perfectly match with native
Labels: framework,a: fidelity,f: cupertino,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-design,triaged-design

Fidelity wise speaking, the [CupertinoActionSheet](https://api.flutter.dev/flutter/cupertino/CupertinoActionSheet-class.html) isn't pixel perfect along with the native one and also there are some key features that are missing. Below are some of the findings I've gather that should be enough to make it perfectly match it.

### Environment:
- **Device:** iPhone X
- **OS version:** 12.3.1
- **Font scale:** Set to minimum

_**Flutter screenshots ar on the left, iOS native on the right**_
___
## Font scale factor shouldn't be allowed below 1.0 and bottom safe area is wrong

![IMG_0293](https://user-images.githubusercontent.com/27860743/61995741-52a18700-b084-11e9-91da-2dd88419da93.PNG) ![IMG_0292](https://user-images.githubusercontent.com/27860743/61995821-23d7e080-b085-11e9-99ac-ac022cda78ab.PNG)


The bottom safe area has more pixeis in the Flutter that it should, also, the font scaling factor, in iOS native, doesn't go below `1.0` whereas Flutter allows it, it should be `max(1.0, fontScaleFactor)`.

## When system font scale is set to maximum, the sizes don't match properly
![IMG_0295](https://user-images.githubusercontent.com/27860743/61995859-99dc4780-b085-11e9-9e78-346182a5a86a.PNG) ![IMG_0296](https://user-images.githubusercontent.com/27860743/61995860-9ba60b00-b085-11e9-9654-097683b27c62.PNG)

Looks like Flutter is scaling a bit more that it should. Fixing this, can potentially fix some other wrong scaling across cupertino widgets.

## Opacity when selected
![IMG_0294](https://user-images.githubusercontent.com/27860743/61995893-f2134980-b085-11e9-9ed8-06683469db17.PNG) ![IMG_0292](https://user-images.githubusercontent.com/27860743/61995894-f2134980-b085-11e9-8b6d-a20b3c88e86d.PNG)

Despite the fact of having different backgrounds, it looks like Flutter is using a different opacity when selecting the item in the sheet. Plus, native allows you to keep it pressed while navigating up and down without raising the finger, providing a light haptic feedback when doing so. Flutter doesn't allow this at all.
____
### Flutter doctor
```
[✓] Flutter (Channel unknown, v1.8.0, on Mac OS X 10.14.5 18F132, locale pt-PT)
    • Flutter version 1.8.0 at /Users/miguelruivo/DevTools/flutter
    • Framework revision 2fefa8c731 (4 weeks ago), 2019-07-01 11:33:22 -0700
    • Engine revision 45b66b722e
    • Dart version 2.4.0
```
Repository: rust
Issue: Formatter not capable of generating underscores in long number literals
Labels: T-libs-api,C-feature-request,A-proc-macros

When using the `quote` crate or otherwise generating Rust code (like we do in `svd2rust`) it would be immensely helpful if there was a way to `format!` long number literals in a way that `clippy` wouldn't throw an https://rust-lang.github.io/rust-clippy/master/index.html#unreadable_literal back at us when linting the code but isn't.
Repository: opencv
Issue: Feature request to use Intel Myriad chips for acceleration Depth Map from Stereo Images
Labels: feature

Feature request to use Intel Myriad chips for acceleration Depth Map from Stereo Images by using Myriad SHAVES cores - to accelerate OpenCV functions: https://docs.opencv.org/4.1.1/dd/d53/tutorial_py_depthmap.html

Currently, OpenCV can use Myriad X chips for Deep Learning tasks (via OpenVINO DL IE backend), but not for other tasks like Stereo Depth processing.

As known KEY BENEFITS of Myriad X chip is: **New Vision Accelerators including Stereo Depth** https://www.movidius.com/MyriadX But there are no examples or API for Stereo Depth processing by using OpenVINO in free access.

It would be nice to be able to use uniform OpenCV API for the basic functions of the Miriad X chip in conjunction with a very weak CPU (Intel Atom). Because Atom CPU doesn't have enough performance to get a Stereo-Depth-Map on its own with high FPS.
Repository: terminal
Issue: FR: Customizable HTML/formated copy
Labels: Issue-Feature,Help Wanted,Area-Settings,Product-Terminal

# Description of the new feature/enhancement

Text copied in formated form, like HTML, should be customizable by settings, so in case you do a lot of copy-paste you don't have to re-format each piece to match your preferences. 
All of them should be optional, with some default values. Once settings are categorized, they should go into single category.

# Proposed technical implementation details (optional)

My propositions:

| Property | Type | Default | Description |
| --- | -- | ---- | -------- |
| `htmlWidth`| String | `"terminal"` | - `terminal` - the width of the actual terminal. <br/> - `text`  - up to the last printable character. Like terminal, but with stripped blank space on the right.  <br/> - `infinite` - Scratches to available space (current behaviour). <br/> - `Valid css value` e.g. `500px` |
| `htmlBackground` | String | `background`'s value | Could anything that `background` can be or any valid css value that would be passed to `background` css property, like url. Theoretically we could support stripping the actual background (like image) and embed  it as base64. I'd like that feature, but I'm afraid it's too heavy for a while.  |
| `htmlOffsetFirstCharracter` | Boolean | `true` | In situation like this: <br/>&nbsp; &nbsp;_012`3456789`_<br/>&nbsp; &nbsp;_`ABCDEFGHIJ`_<br/>&nbsp; &nbsp;_`KLMNOPQ`RST_ <br/> where `this means selected`, true makes the paste as:<br/>&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;_3456789_<br/>&nbsp; &nbsp;_ABCDEFGHIJ_<br/>&nbsp; &nbsp;_KLMNOPQ_ </br>and false as:<br/>&nbsp; &nbsp;_3456789_<br/>&nbsp; &nbsp;_ABCDEFGHIJ_<br/>&nbsp; &nbsp;_KLMNOPQ_

Other than these above, properties `padding`, `fontFace`, `fontSize` and `colorTable` should be duplicated for the html/formated text so they can be set separately. If not set, they would match the terminal's ones.
Repository: rust
Issue: "Variable is assigned to, but never used" not thrown
Labels: A-lints,T-compiler,C-bug

```rust
fn main() {
    let mut error = 0;
    for i in 0..3 {
        error += i;
    }
}
```
This ([playground](https://play.integer32.com/?version=stable&mode=debug&edition=2018&gist=58536d969b9dce47854128a31f47454b)) correctly throws the warning 'variable `error` is assigned to, but never used'.

But _this_ ([playground](https://play.integer32.com/?version=stable&mode=debug&edition=2018&gist=89507f1543cedcc9b452ad430eab5ca8)) **doesn't**
```rust
fn main() {
    let mut error = 0;
    for i in 0..3 {
        error = error + i;
    }
}
```

[in 1.36, beta, nightly; 2015,2018]

---
I hope this isn't a duplicate.
Found by @ColinPitrat in #63046 :wink:
Repository: go
Issue: runtime: use PAGE_NO­ACCESS in sysReseve
Labels: NeedsInvestigation

Windows version of runtime.sysReseve calls VirtualAlloc with MEM_RESERVE and PAGE_READWRITE, but it should use PAGE_NO­ACCESS when using MEM_RESERVE.

According to https://devblogs.microsoft.com/oldnewthing/20171227-00/?p=97656

> Why do you have to pass a valid value even if the system doesn’t use it?
> 
> This is an artifact of how the front-end parameter validation is done. The Virtual­Alloc function does parameter validation by checking each parameter individually to confirm that the value is among the valid values.

and in particular

> Bonus chatter: You would think that the flProtect would not be used when reserving address space with MEM_RESERVE, but you’d be wrong. If reserving regular address space, then the protection should be PAGE_NO­ACCESS.

Someone would have to try and see what effect this change have on memory used by Go executable before making this change. Maybe by using vmmap or rammap tools.

I am creating this issue before I forget.

/cc @aclements and @zx2c4 because you might be interested.

Alex
Repository: electron
Issue: Unable to set default filter to 'All Files (`*.*`)' in Windows save file dialog
Labels: enhancement :sparkles:

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem Description
It is not possible to set the default filter on a save file dialog in Windows to `All Files (*.*)`. This is a nuisance because often when you want to save a file with no/unknown extension, such as `.babelrc`, it appends the first filter's extension. Example: https://github.com/microsoft/vscode/issues/28425

![image](https://user-images.githubusercontent.com/2119933/62002660-ebfd8700-b0de-11e9-9f93-51c53014cbf0.png)

Now, I know this is intentionally not allowed, as can be seen in [`shell/browser/ui/file_dialog_win#L206`](https://github.com/electron/electron/blob/34c4c8d5088fa183f56baea28809de6f2a427e02/shell/browser/ui/file_dialog_win.cc#L206):

```cpp
// By default, *.* will be added to the file name if file type is "*.*". In
// Electron, we disable it to make a better experience.
// ...
for (size_t i = 0; i < filterspec.size(); ++i) {
	if (std::wstring(filterspec[i].pszSpec) != L"*.*") {
		// SetFileTypeIndex is regarded as one-based index.
		dialog->SetFileTypeIndex(i + 1);
		dialog->SetDefaultExtension(filterspec[i].pszSpec);
		break;
	}
}
```

It basically picks the first filter as the default, **except for the All Files one** because of a supposed issue where it appends `*.*` to the file name. However, there has to be a way to do this, because other programs do (unfortunately I couldn't think of any open source one so we could look at the sources).

### Proposed Solution
No real ready solution in mind. Just gotta figure out how to allow it and avoid the issue. Maybe if instead of setting the default extension to `"*.*"` we set it `""` when the _All Files_ filter is used, we could get both things to work.

### Alternatives Considered
Verify whether the _appending `*.*` to filename_ issue actually happens. If it doesn't, we can just cut the code out.

### Additional Information
Fiddle: https://gist.github.com/e9cf0de5417180669245e79b10c2f898
Repository: rust
Issue: Tracking issue for RFC 2515, "Permit impl Trait in type aliases"
Labels: B-RFC-approved,T-lang,B-unstable,A-impl-trait,C-tracking-issue,needs-fcp,F-type_alias_impl_trait,requires-nightly,T-types,F-impl_trait_in_assoc_type

This is a tracking issue for the RFC "Permit impl Trait in type aliases" (rust-lang/rfcs#2515) which is implemented under the following `#![feature(..)]` gates:
- `type_alias_impl_trait`
- `impl_trait_in_assoc_type`: https://github.com/rust-lang/rust/pull/110237

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Implement the RFC
- [ ] Adjust documentation ([see instructions on rustc-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-guide][stabilization-guide])

[stabilization-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs

### Unresolved questions

- [x] Exactly what should count as "defining uses" for opaque types?
    - [x] Should the set of "defining uses" for an opaque type in an impl be just items of the impl, or include nested items within the impl functions etc? ([see here for example](https://github.com/rust-lang/rust/pull/52650#discussion_r204893239))
    - [ ] should return-position-impl-trait also start allowing nested functions and closures to affect the hidden type? -- independent question to be answered separately by the lang team. Would simplify compiler.
- [x] can we come up with consistent rules when cross-usage type inference can happen?
    - ```rust
      fn foo(x: bool) -> impl Debug {
          if x { return vec!["hi"] }
          Default::default()
      }
      ```
      compiles on stable, even though there is no obvious type for `Default::default()` to produce a value of. We combine all return sites though and compute a shared type across them, so we'll figure out a `Vec<&'static str>`
    - `impl Foo` can be used for associated types that expect a type that implements `Bar`, even if `Foo` and `Bar` are entirely unrelated. The hidden type must satisfy both. See https://github.com/rust-lang/rust/pull/99860/files for examples.

- [x] impl traits in consts through const fns are allowed but shouldn't be: https://github.com/rust-lang/rust/issues/87277
Repository: rust
Issue: Tracking issue for `impl Trait` in `const` and `static` items and `let` bindings
Labels: B-RFC-approved,T-lang,B-unstable,A-impl-trait,C-tracking-issue,F-impl_trait_in_bindings,requires-nightly,S-tracking-impl-incomplete

As provided for by rust-lang/rfcs#2071, this is a tracking issue for `impl Trait` in:
- `const` items
- `static` items
- `let` bindings

**Steps:**

- [x] Implement the RFC
   - In `let`: https://github.com/rust-lang/rust/pull/134185
- [ ] Adjust documentation ([see instructions on rustc-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-guide][stabilization-guide])

[stabilization-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs

**Unresolved questions:**

- [ ] Should the part about `let` bindings be recast more generally to be about *coercions*? This would allow `foo as impl Debug` and `foo: impl Debug` as well.

**Blocking issues:**

Incomplete. Search the `F-impl_trait_in_bindings` issue.

- [x] https://github.com/rust-lang/rust/issues/83021
- [ ] https://github.com/rust-lang/rust/issues/61773
Repository: rust
Issue: Meta tracking issue for `impl Trait`
Labels: metabug,T-lang,T-compiler,A-impl-trait,C-tracking-issue,S-tracking-impl-incomplete

This issue tracks the progress of `impl Trait` in general.

This issue is not for discussion about specific extensions to `impl Trait` and only exists to provide links to other places that track the progress of specific issues. If you wish to discuss some subject related to `impl Trait`, please find an existing appropriate issue below or create an new issue and comment here with a link to the newly created issue.

--------------------------

The `impl Trait` related issues currently on deck are as follows:

* [ ] [Label `A-impl-trait`](https://github.com/rust-lang/rust/labels/A-impl-trait)
* [ ] Permit `type Foo = impl Bar;`. https://github.com/rust-lang/rust/issues/63063
   * [ ] Permit `type Foo = impl Bar;` in `trait` definitions. https://github.com/rust-lang/rust/issues/29661
* [ ] In `const` and  `static` items and `let` bindings. https://github.com/rust-lang/rust/issues/63065
* [x] Member constraints in region inference: https://github.com/rust-lang/rust/issues/61997
* [ ] Existential lifetimes. https://github.com/rust-lang/rust/issues/60670
* [ ] Support lifetime elision in argument position. https://github.com/rust-lang/rust/issues/49287
* [ ] Should we allow `impl Trait` after `->` in `fn` types or parentheses sugar? https://github.com/rust-lang/rust/issues/45994
* [ ] Do we have to impose a DAG across all functions to allow for auto-safe leakage, or can we use some kind of deferral.
   - Discussion: https://github.com/rust-lang/rust/pull/35091#discussion_r73738398
   - Present semantics: DAG.
* [ ] Should we permit specifying types if some parameters are implicit and some are explicit? e.g., `fn foo<T>(x: impl Iterator<Item = T>>)`?
    - Current behavior: An error to specify types
    - Other alternatives: [treat `impl Trait` as arguments in the list, permitting migration]
* [ ] [Some concerns about nested impl Trait usage](https://github.com/rust-lang/rust/issues/34511#issuecomment-350715858)

--------------------------

Open RFCs:

None.
Repository: create-react-app
Issue: from node-10-16 lts, impossible to run nm start after npx create-react-app my_app [closed]
Labels: tag: enhancement

### Describe the bug
from node-10-16 lts, impossible to run nm start after npx create-react-app my_app
errors are:
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: spawn /usr/bin/palemoon ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! memory@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the memory@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jerome/.npm/_logs/2019-07-28T06_52_10_841Z-debug.log

after installed package-lock.json, as suggested above, the server doesn't start and no error message....
yarn.lock installed but node_modules can not with many error again:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for undefined@node_modules
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jerome/.npm/_logs/2019-07-28T06_54_34_517Z-debug.log

npm version is 6.10.2

I don't want to remove my official repos packages (it is a very bad practice) ad i hope it is possible to just use react with lts node application,if not, it housld be impossible ofr me to learn and use react due to miss-respect version lts concept and unmaintainable applications from this crucial point.

### Environment
  `npx create-react-app --info`

 Environment Info:

  System:
    OS: Linux 5.2 Arch Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
  Binaries:
    Node: 10.16.0 - /usr/bin/node
    Yarn: Not Found
    npm: 6.10.2 - /usr/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 68.0.1
  npmPackages:
    react: ^16.8.6 => 16.8.6 
    react-dom: ^16.8.6 => 16.8.6 
    react-scripts: 3.0.1 => 3.0.1 
  npmGlobalPackages:
    create-react-app: 3.0.1

### Steps to reproduce

1. npm install -g create-react-app
2. npx create-react-app my_app
3. cd my_app
4. npm start

### Expected behavior

server should run with information about server access url

### Actual behavior

![err_at_react_app_start](https://user-images.githubusercontent.com/11176132/62003374-75917100-b140-11e9-82f9-c9b50d622443.png)
Repository: rust
Issue: Tracking issue for RFC 2574, "SIMD vectors in FFI"
Labels: A-FFI,B-RFC-approved,T-lang,T-compiler,A-SIMD,C-tracking-issue,F-simd_ffi,requires-nightly,S-tracking-unimplemented

This is a tracking issue for the RFC "SIMD vectors in FFI" (rust-lang/rfcs#2574).
The feature gate is `#![feature(simd_ffi)]`.

**Steps:**

- [ ] Implement the RFC (cc @rkruppe @gnzlbg); WIP in https://github.com/rust-lang/rust/pull/59238 and #86546.
- [ ] Adjust documentation ([see instructions on rustc-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-guide][stabilization-guide])

[stabilization-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html#documentation-prs

**Unresolved questions:**

- [ ] Should it be possible to use, e.g., `__m128` on C FFI when the `avx` feature is enabled? Does that change the calling convention and make doing so unsafe ? We could extend this RFC to also require that to use certain types certain features must be disabled.