sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Allow scaling up to meet PDB constraints
Labels: sig/node,sig/autoscaling,kind/feature,needs-triage

**What would you like to be added**:

Currently if you have a PDB spec like `minAvailable: 1`, and a HPA defining minReplicas=1 and maxReplicas=N, you may end up in a scenario where disruptions get "stuck" if the HPA has scaled to 1. At any point an increase in load could cause the HPA to scale up to 2+, allowing the PDB to be satisfied, which leads to a weird scenario where a disruption can only occur if there is high load.

Ideally, the PDB would be able to trigger the HPA to scale up to meet constraints. For example, if I have 1 replica and a disruption is triggered, scale up a new replica first, then terminate the old one. Given an HPA is in place, I have already clearly specified I am OK with my pod being scaled up, so this shouldn't have negative impact on stateful workloads.

Some more context: https://github.com/istio/istio/issues/12602
Repository: terminal
Issue: Color picker window closes unexpectedly when clicking on the combobox multiple times
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

<!--
This bug tracker is monitored by Windows Terminal development team and other technical folks.

**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible.

-->

# Environment

```none
Windows build number: 10.0.19041.388
Windows Terminal version: 1.1.2021.0
```

# Steps to reproduce


1. Right click on a tab
2. Click "Color..."
3. Click "Custom..."
4. Click "More"
5. Click on the combobox with RGB and HSV
6. Click on an empty area, so the combobox closes
7. Click on the combobox again

<!-- A description of how to trigger this bug. -->

# Expected behavior

The combobox opens again

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

# Actual behavior

The color picker window closes

<!-- What's actually happening? -->
Repository: PowerToys
Issue: Explorer right click copy image to clipboard (not file)
Labels: Idea-New PowerToy,Status-In progress

# Summary of the new feature/enhancement

Right-click and copy the image, not the file, for pasting into other apps.

## Instructions
Explorer right click copy image to clipboard , there should be a "Copy Image" option when right-clicking PNG, JPG or other image files.

Ex: [https://github.com/lucent-sea/copy-image](https://github.com/lucent-sea/copy-image)

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Explorer right click copy image to clipboard , there should be a "Copy Image" option when right-clicking PNG, JPG or other image files.
Repository: terminal
Issue: Show tab previews when the user hovers over the tab bar
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

Bring tab previews when hovering terminal tabs. Just in the Legacy Microsoft Edge, tab previews must also be implemented on tabbed based programs like Terminal and Terminal Preview. This feature is accessed by simply hovering the tab then it shows a simple thumbnail of whatever content is on that particular tab and the title at the same time.

This feature is very useful most especially nowadays where apps have a tabbed user interface (particularly the discontiuned Windows 10 feature called "Sets") and users tend to open too many tabs that they won't be able to fit anymore.

Since this a UWP app, you might as well implement the same tab preview feature as it is already implemented in the Legacy Microsoft Edge on the Windows 10 Creators Update version 1703 build 15063.

No matter how many tabs you have, when the user simply hovers that tab a tab preview including the thumbnail of that tab's content and the tab's title will appear.
Repository: opencv
Issue: Can't parse simple TensorFlow model. Error:Error parsing text-format opencv_tensorflow.GraphDef: 714:5: Unknown enumeration value of "DT_RESOURCE" for field "type"
Labels: feature,category: dnn


- OpenCV => 4.3
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017

##### Detailed description

Hi, i'm trying to run some simple model, but it gives me an error during parse:
`Error parsing text-format opencv_tensorflow.GraphDef: 714:5: Unknown enumeration value of "DT_RESOURCE" for field "type".`
Is there any way to fix this issue?
It is cnn from deep sort alghoritm.
https://drive.google.com/file/d/11VKR4sMX2XIRov_qT9k4r7XDSnlBnNT9/view?usp=sharing - here are .pb and .pbtxt file

https://github.com/nwojke/deep_sort/blob/d303103724d38ee4b4734974986e1f1c9b4dc6ef/tools/freeze_model.py - here is a code to generate this model from scratch
Repository: go
Issue: runtime: fatal error: checkdead: inconsistent counts
Labels: NeedsInvestigation,compiler/runtime

_Originally posted by @apmattil in https://github.com/golang/go/issues/40368#issuecomment-664604178_

I used 1.14.4 compiler

I do get the sched variable at frame 11:
```
(dlv) frame 11
> runtime.raise() /usr/local/go/src/runtime/sys_linux_amd64.s:165 (PC:
0x465511)
Warning: debugging optimized function
Frame 11: /usr/local/go/src/runtime/proc.go:4386 (PC: 440a12)
  4381:         run := mcount() - sched.nmidle - sched.nmidlelocked -
sched.nmsys
  4382:         if run > run0 {
  4383:                 return
  4384:         }
  4385:         if run < 0 {
=>4386:                 print("runtime: checkdead: nmidle=", sched.nmidle,
" nmidlelocked=", sched.nmidlelocked, " mcount=", mcount(), " nmsys=",
sched.nmsys, "\n")
  4387:                 throw("checkdead: inconsistent counts")
  4388:         }
  4389:
  4390:         grunning := 0
  4391:         lock(&allglock)
(dlv) p sched
runtime.schedt {
        goidgen: 0,
        lastpoll: 0,
        pollUntil: 0,
        lock: runtime.mutex {key: 0},
        midle: 0,
        nmidle: 0,
        nmidlelocked: 0,
        mnext: 0,
        maxmcount: 0,
        nmsys: 0,
        nmfreed: 0,
        ngsys: 0,
        pidle: 0,
        npidle: 0,
        nmspinning: 0,
        runq: runtime.gQueue {head: 0, tail: 0},
        runqsize: 0,
        disable: struct { runtime.user bool; runtime.runnable
runtime.gQueue; runtime.n int32 } {
                user: false,
                runnable: (*runtime.gQueue)(0x1367030),
                n: 0,},
        gFree: struct { runtime.lock runtime.mutex; runtime.stack
runtime.gList; runtime.noStack runtime.gList; runtime.n int32 } {
                lock: (*runtime.mutex)(0x1367048),
                stack: (*runtime.gList)(0x1367050),
                noStack: (*runtime.gList)(0x1367058),
                n: 0,},
        sudoglock: runtime.mutex {key: 0},
        sudogcache: *runtime.sudog nil,
        deferlock: runtime.mutex {key: 0},
        deferpool: [5]*runtime._defer [
                *nil,
                *nil,
                *nil,
                *nil,
                *nil,
        ],
        freem: *runtime.m nil,
        gcwaiting: 0,
        stopwait: 0,
        stopnote: runtime.note {key: 0},
        sysmonwait: 0,
        sysmonnote: runtime.note {key: 0},
        safePointFn: nil,
        safePointWait: 0,
        safePointNote: runtime.note {key: 0},
        profilehz: 0,
        procresizetime: 0,
        totaltime: 0,}
(dlv)
```
Repository: rust
Issue: Lints about `unsafe {}` blocks propagate inside macros
Labels: C-enhancement,A-lints,A-macros,T-compiler

Coming from #74200.

I used `#![deny(unsafe_op_in_unsafe_fn)]` in `std/panicking.rs`. This raised an error about a missing `unsafe {}` block in `std/thread/local.rs`. Adding it raised a warning about extraneous `unsafe {}` in other parts of the code. This forced me to use `#[allow(unused_unsafe)]`.

It was noted that lints like those (whatever *those* is) should maybe not propagate inside macros.

cc @Mark-Simulacrum who raised the point in the first place
Repository: rust
Issue: Creating a raw pointer to an external static requires an unsafe block
Labels: A-FFI,T-compiler,C-bug,F-raw_ref_op

I tried this code ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=aa3de5e9a5f3c18514232c0baf1b29b6)):

```rust
#![feature(raw_ref_op)]

extern {
    static FOO: u32;
}

mod foo {
    #[no_mangle]
    static FOO: u32 = 5;
}

fn main() {
    dbg!(core::ptr::addr_of!(FOO));
    dbg!(&raw const FOO);
}
```

I expected to see this happen: it compile and print the address of `FOO` twice.

Instead, this happened: compilation failed because accessing `FOO` requires an `unsafe` block

```
error[E0133]: use of extern static is unsafe and requires unsafe function or block
  --> src/main.rs:13:10
   |
13 |     dbg!(core::ptr::addr_of!(FOO));
   |          ^^^^^^^^^^^^^^^^^^^^^^^^ use of extern static
   |
   = note: extern statics are not controlled by the Rust type system: invalid data, aliasing violations or data races will cause undefined behavior
   = note: this error originates in the macro `core::ptr::addr_of` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0133]: use of extern static is unsafe and requires unsafe function or block
  --> src/main.rs:14:10
   |
14 |     dbg!(&raw const FOO);
   |          ^^^^^^^^^^^^^^ use of extern static
   |
   = note: extern statics are not controlled by the Rust type system: invalid data, aliasing violations or data races will cause undefined behavior
```

As far as I can tell none of the potential causes of UB can be caused by just creating a raw pointer to the static. This should be a safe operation, and only when attempting to use the pointer in the future should you need to prove validity of it.
Repository: rust
Issue: libtest should set RUST_TEST_THREADS environment variable
Labels: C-feature-request,A-libtest

We can configure the test runner concurrency by using either the `--test-threads` parameter, or by setting the environment variable `RUST_TEST_THREADS`:

https://github.com/rust-lang/rust/blob/efc02b03d18b0cbaa55b1e421d792f70a39230b2/src/libtest/lib.rs#L245

As some tests might need to read the current concurrency configuration, the only way to do this currently is by reading the said environment variable. However, if we use `--test-threads`, this information is not passed further to tests. I think this behaviour is a bit inconsistent and the env var should be always set to the actual value, e.g.:

```rust
let concurrency = opts.test_threads.unwrap_or_else(get_concurrency);
env::set_var("RUST_TEST_THREADS", concurrency.to_string());
```
Repository: TypeScript
Issue: End tags ignore indentation rules in Javascript React
Labels: Bug,Help Wanted,Domain: Formatter,PursuitFellowship


*TS Template added by @mjbvz*

**TypeScript Version**: 4.0.0-dev.20200727

**Search Terms**
- jsx
- format

---

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:18:50.054Z)
- OS Version: MacOS 10.14.6

Steps to Reproduce:

1. Create a file of type "Javascript React" (e.g. by creating a `.jsx` file)
2. Write some markup with incorrect indentation:

```jsx
    <div>
hello
        </div>
```
3. Run "Format Document" (or Shift+Alt+F)

Everything will be auto-indented except the closing `</div>` tag:

```jsx
<div>
    hello
        </div>
```

This happens with any type of element including custom React components. It seems to only occur when an element contains plain text.

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: TypeScript
Issue: Auto imports from referenced project not working until already imported once in project
Labels: Suggestion,Experience Enhancement,Cursed?

*TS Template added by @mjbvz*

**TypeScript Version**: 4.0.0-dev.20200727

**Search Terms**
- angular
- project references
- auto imports 

---

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.47.2
- OS Version: Mac OS Catalina 10.15.5

Steps to Reproduce:

I have an Angular project, and just 1 of the files don't have a proper suggestion support in it.
Same happens when I create a file via plus sign from the side bar.
VSCode doesn't suggest "obvious(necessary)" things, quite the contrary happens:
it suggests everything else what's available, but not what I need and not what really exists in the project.

Also, when I try to import environment object with 'src/environments/environment',
it doesn't seem to know about src folder(project_name/src).
Although it already works this way for all the other files in the project.

Cache cleaning && insiders build didn't help out, no errors in debug console and I couldn't find any useful tsserver logs.
Although I can send if necessary.
Having 3.9.7 TS

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: rust
Issue: debuginfo test hanging on `arm-android`
Labels: A-debuginfo,O-android,T-compiler,C-bug

As part of [this pull request](https://github.com/rust-lang/rust/pull/74105) we wrote a test which is apparently causing `debuginfo` tests to hang when run on `arm-android`. @matthewjasper suggested we decouple the test harness issue from the PR. So this issue serves to track the issue with the test harness problem.
Repository: react-native
Issue: Line height is distributed unevenly when lineHeight <= fontSize
Labels: Resolution: Fixed

## Description
When `lineHeight` is less than the `fontSize`, `Text` shrinks the line's bounding box only by removing space from above the text, rather than distributing the space evenly above and below, as is done with extra line height. Actually, the issue manifests when `lineHeight` is less than `fontSize` plus some small amount (perhaps the font bounding box height?)—e.g. <= 45px for 40px Helvetica.

This leads to clipped glyphs and produces differences in text rendering between react-native-web and react-native (https://github.com/necolas/react-native-web/issues/1687). After some discussion with @necolas, my inclination is that RNW's behavior is the more reasonable one, so I thought I'd open an issue here.

This issue reproduces across a variety of fonts.

![image](https://user-images.githubusercontent.com/2771/88598530-50b72e80-d01e-11ea-8dac-6d712e667e38.png)

Unfortunately,I worry that fixing this issue will create subtle and surprising source compatibility issues for existing clients. 
## React Native version:
```
System:
    OS: macOS 10.15.5
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 337.02 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.21.0 - ~/.nvm/versions/node/v10.21.0/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v10.21.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5900203
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.2 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    *react-native*: Not Found
```

## Steps To Reproduce
Run example app here: https://snack.expo.io/W51F2OAqD

## Expected Results
The extra line spacing should be removed evenly from both above and below the type.

## Snack, code example, screenshot, or link to a repository:
https://snack.expo.io/W51F2OAqD
Repository: flutter
Issue: ScrollController.maxScrollExtent of NestedScrollView limited to header (outer scroll), doesn't allow for inner CustomScrollView scrolling
Labels: framework,f: scrolling,d: examples,has reproducible steps,P2,workaround available,team-framework,triaged-framework,found in release: 3.19,found in release: 3.20

I have a CustomScrollView inside a NestedScrollView. The NestedScrollView has an attached ScrollController. The maxScrollExtent property of the ScrollController is only 100 pixels or so, which is the height of the header (i.e., the outer scroll). This prevents me from being able to use the ScrollController to scroll the CustomScrollView (i.e., inner scroll) all the way down to the bottom.

After digging around, it appears that it's not possible to attach a second ScrollController to the CustomScrollView since it breaks the NestedScrollView's ability to control it.

Is there a suggested alternative or a workaround for controlling the scroll position of a NestedScrollView, so that we can include the inner CustomScrollView and scroll it all the way down to the bottom?
Repository: pytorch
Issue: Support Python type() in TorchScript
Labels: oncall: jit

## 🚀 Feature
Allow using of type() to get type string of a Python object in TorchScript

## Motivation

type() is commonly used when creating meaningful error messages, especially so after we [support raising exception with custom error messages](https://github.com/pytorch/pytorch/pull/41907).

## Pitch

type() should be supported and return a string in TorchScript.

## Example

```
 cat type_error_msg.py                                                                                                                                                                                       [ruby-2.5.1p57]
import torch


@torch.jit.script
def fn(cond: torch.Tensor):
    if bool(cond):
        raise RuntimeError("incorrect type:" + str(type(cond)))

fn(torch.Tensor(1))
```

Currently this example errors out:
```
Traceback of TorchScript (most recent call last):
  File "type_error_msg.py", line 7, in fn
def fn(cond: torch.Tensor):
    if bool(cond):
        raise RuntimeError("incorrect type:" + str(type(cond)))
                                                   ~~~~ <--- HERE
RuntimeError:  expected value of type Tensor for return value but instead got value of type type.
Value: <class 'torch.Tensor'>
```

cc @suo @gmagogsfm
Repository: vscode
Issue: Git - gutters don't show on filenames that have changed case
Labels: bug,git,uri

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.47.3 91899dcef7b8110878ea59626991a18c8a6a1b3e
- OS Version: MacOS 10.14.6

Steps to Reproduce:

~~1. Initialize a git repository~
2. Add a capitalized filename, e.g. `Counter.jsx`
3. Commit the file
4. Make some changes in the file and save~~

~~The file will show as modified in the explorer, but the changes are not shown in the gutter. If you follow the same step but with a lowercase filename instead, the modifications will appear in the gutter. This is problematic for React projects where uppercase filenames are not uncommon.~~

**Edit:** See my modified instructions [below](https://github.com/microsoft/vscode/issues/103444#issuecomment-666541057)

This issue was already brought up in #48714 and closed by 375411e, but the issue still occurs. I'm opening this new issue since the old one is locked.

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: vscode
Issue: [python] Add #region and #endregion to python autocomplete
Labels: help wanted,feature-request,languages-basic

Issue Type: <b>Feature Request</b>

The autocomplete feature does not have #region or #endregion in list 

VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.17763


<!-- generated by issue reporter -->