sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Provide option to add "Open in Windows Terminal (Admin)" to Explorer context menu
Labels: Area-Settings,Product-Terminal,Issue-Task,Area-ShellExtension

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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!
-->

# Description of the new feature/enhancement

<!-- 
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).
-->
As well as having the option to Open in Windows Terminal as a right-click in Explorer (which should be configurable as discussed in #9902 and #6113 ) it would be really helpful to have a configurable option to ALSO have an "Open in Windows Terminal (Admin)" option to quickly open up Windows Terminal with Admin rights to be able to access those commands which need it.

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Add an option in the configuration to enable/disable an "Open in Windows Terminal (Admin)" context menu option.
Repository: godot
Issue: Arrays and Dictionaries with initial value are shared
Labels: topic:gdscript

Once upon a time: #24134

Today: Godot Engine v3.2.3.stable.official

```
extends Node

class Wave:
	extends Node
	export var spawn_data = {}
	export var flag = false
	# # Uncomment to fix
	#func _init():
	#	spawn_data = {}

func reset_waves():
	if true:
		var wave = Wave.new()
		wave.name = "Wave_1"
		wave.spawn_data[ 50] = ['L1']
		wave.flag = true
		$Map.add_child(wave)
		wave.owner = $Map
		print(wave.flag, wave.spawn_data)
	if true:
		var wave = Wave.new()
		wave.name = "Wave_2"
		wave.spawn_data[111] = ['L1']
		$Map.add_child(wave)
		wave.owner = $Map
		print(wave.flag, wave.spawn_data)
	return

func _ready():
	reset_waves()
```
Expected:
```
True{50:[L1]}
False{111:[L1]}
```
Got:
```
True{50:[L1]}
False{111:[L1], 50:[L1]}
```
I expect initial value to be constant and all instances would have it's duplicate. Turns out I expect too much, as initial value is shared until 'duplicate' is called. Maybe we should add special keyword for this behavior? Like, I dunno, 'static'? Sounds legit to me.
Repository: flutter
Issue: [maps] [proposal] Add `BitmapDescriptor.FromNetworkImages()` to load image from network
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

Hi Google, so a few days ago we ran into an issue about [pin colors](https://github.com/flutter/flutter/issues/80592). So our team sat together to search for an alternative. We talked with our client and he said if we cannot send the pin colors so why not send the pin images directly from the server?

We searched and found that google maps flutter have something **BitmapDescriptor.fromAssetImage**
![image](https://user-images.githubusercontent.com/43144366/115357052-ac8d9d00-a1d5-11eb-8baf-46051537a3cf.png)


This is very useful if we have asset images in our application. But since our application gets data from an internet server. So we searched everywhere but couldn't find a way to get images from API and set them in **BitMapDescriptor?**

**https://www.coletiv.com/blog/use-network-images-as-marker-icons-flutter-google-maps/**

we found this URL and it's a bit helpful but it's very lengthy and we have to go all the way around. I will surely give input on this method or If I devise something easier rather than 

_1) Downloading SVG images from API
2) Caching them 
3) Converting them into png format because that's the only acceptable format by BitmapDescription_

### **What could be done?**

Everything in the flutter is a widget. Can we make markers with the option of the widget? So we can use network images or images. network and directly show images with height and width set from the server? 

If not then something helpful like **Bitmapdescriptor.fromNetworkImage()** that accepts only PNG format because that's still manageable rather than going through a long process as mentioned above.
Repository: rust
Issue: Cannot borrow `*self` as mutable more than once at a time
Labels: A-lifetimes,A-borrow-checker,T-lang,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
struct Test;
impl Test {
    fn test(&mut self) -> Option<&str> {
        match self.test() {
            None => None,
            Some(txt) if txt.len() == 1 => Some(txt),
            Some(_) => self.test()
        }
    }
}
```

I expected to it to compile without erorrs.

Instead, this happened: 
```
error[E0499]: cannot borrow `*self` as mutable more than once at a time
  --> src/lib.rs:17:24
   |
13 |     fn test(&mut self) -> Option<&str> {
   |             - let's call the lifetime of this reference `'1`
14 |         match self.test() {
   |               ---- first mutable borrow occurs here
15 |             None => None,
16 |             Some(txt) if txt.len() == 1 => Some(txt),
   |                                            --------- returning this value requires that `*self` is borrowed for `'1`
17 |             Some(_) => self.test()
   |                        ^^^^ second mutable borrow occurs here
```


</p>
</details>

[Playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=6793a9891d51f3ebd14557a98e4686f3)
[Playground (version with if)](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=9f5ac590f18c786764d3bfb0d288d6eb)
Repository: flutter
Issue: ListWheelScrollView not re-rendering children on setState
Labels: framework,f: material design,f: scrolling,has reproducible steps,P2,found in release: 3.7,found in release: 3.11,team-design,triaged-design

Hi!
I'm using two ListWheelScrollViews where the state of the first one changes the children of the second one.
Basically, the first one lets the user pick a date and the second shows the available times.

Debugging, I could see that the children are changed after the setState called in the onSelectedItemChanged of the first ListWheelScrollViews, but they're not being rendered. Only after a hot-reload.

Both ListWheelScrollViews are inside a Stateful Widget under a BottomSheet and I tried putting them inside a StatefullBuilder but it also didn't help.

**Expected results:** Rendering the new children

**Actual results:** Only the "old" children

<details>
  <summary>Logs</summary>

<!--
      Run your application with `flutter run --verbose` and attach all the
      log output below between the lines with the backticks. If there is an
      exception, please see if the error message includes enough information
      to explain how to solve the issue.
-->

```
```

<!--
     Run `flutter analyze` and attach any output of that command below.
     If there are any analysis errors, try resolving them before filing this issue.
-->

```
```

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[√] Flutter (Channel stable, 2.0.2, on Microsoft Windows [Version 10.0.18363.1316], locale en-US)
    • Flutter version 2.0.2 at C:\flutter
    • Framework revision 8962f6dc68 (6 weeks ago), 2021-03-11 13:22:20 -0800
    • Engine revision 5d8bf811b3
    • Dart version 2.12.1

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\Admin-PC\AppData\Local\Android\Sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = C:\Users\Admin-PC\AppData\Local\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio1
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.55.1)
    • VS Code at C:\Users\Admin-PC\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.21.0

[√] Connected device (2 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 89.0.4389.114

• No issues found!
```

</details>
Repository: pytorch
Issue: I meet an error assert key in deserialized_objects when I torch.load(pthname),and pth file is trained on multi gpu
Labels: oncall: distributed,module: serialization,triaged,module: ddp

My train code is like this:
```
os.environ["CUDA_VISIBLE_DEVICES"] = "0,1,2,3,4,5,6,7"
device = torch.device(arg.local_rank)
net = Net().to(device)
net = torch.nn.parallel.DistributedDataParallel(net, device_ids=[arg.local_rank])
torch.save(net.state_dict(), "0.pth"))
```
and My load code "torch.load("0.pth")" reported error:
`Traceback (most recent call last):
  File "/root/PycharmProjects/test.py", line 8, in <module>
    model_dict = torch.load("0.pth")
  File "torch/serialization.py", line 529, in load
    return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
  File "torch/serialization.py", line 709, in _legacy_load
    deserialized_objects[key]._set_from_file(f, offset, f_should_read_directly)
RuntimeError: storage has wrong size: expected -4916312287391674656 got 24`

cc @mruberry @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu @gcramer23
Repository: flutter
Issue: 'flutter build' suggests wrong autocompletion with shell completion
Labels: tool,a: quality,P2,team-tool,triaged-tool

CLI `flutter build` suggests wrong autocompletion.

Available subcommands are `aar`, `apk`, `appbundle`, `bundle`, `ios`, `ios-framework`, `ipa`, and `web`.
But `aot`, `apk`, `flx`, and `ios` are suggested by autocompletion.

![Screenshot from 2021-04-20 17-50-58](https://user-images.githubusercontent.com/28584151/115367709-6817f680-a201-11eb-96ad-962f8e14623c.png)

channel: stable
Repository: godot
Issue: 2D rendering does math on srgb encoded colors
Labels: discussion,topic:rendering,topic:2d

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.2.3


**OS/device including version:**
Windows 7


**Issue description:**
![obraz](https://user-images.githubusercontent.com/5860567/115335166-f0b07b80-a19c-11eb-9003-25ba21c425c6.png)
I made a project which showcases a couple of erroneous results.

The first example sets the output COLOR in a shader to 0.5 grey. The result is 128 srgb grey. This is erroneous because it means output values in the shader are srgb encoded. Shaders exist to perform math and srgb encoding is wrong for math. This could possibly be fixed with manual conversion in shaders.

The second and third examples shows that blending colors outside shaders still provides wrong results, which means the blending is again done with no regard for srgb encoding. No fix aside from custom shader that I know of.


The fourth and fifth examples verify that values sampled from textures are also srgb encoded. This is in line with first example. This is bad because texture filtering should account for srgb encoding. Results are not fixable with manual conversions, as those occur after filtering.

I found no documentation of this behaviour, although it can be expected. More importantly, I have found no way of fixing this behaviour. As 3D rendering seems to be done correctly with linear encoding, I can't see why it would be impossible for 2D.


**Steps to reproduce:**
Run the test project. It showcases a few ways the behaviour is incorrect.


**Minimal reproduction project:**
[SRGB.zip](https://github.com/godotengine/godot/files/6340550/SRGB.zip)
Repository: pytorch
Issue: Scatter tests missing when passing a reduction operation.
Labels: triaged,module: scatter & gather ops

Depends on #54302 and #56463.
- #54302 ports `scatter` tests to `OpInfo`
- #56463 adds support for the reduce kwarg for `scatter` (the out-of-place version).

Tests for the to-be-supported reduce kwarg for the out-of-place `scatter` operation are missing.
Repository: opencv
Issue: cv2.imshow() freeze inside loop in Ubuntu 18.04 with Conda
Labels: incomplete

##### System information (version)
- OpenCV => 4.5.1
- Operating System / Platform => Ubuntu 18.04 / Conda

##### Detailed description

When used cv2.imshow() in loop, the window doesn't reload and gets stuck at the first frame.

##### Steps to reproduce

    ```.py
    def process_img(data):
          i = np.array(data.raw_data)
          i2 = i.reshape((IM_HEIGHT, IM_WIDTH, 4))
          i3 = i2[:, :, :3]
          cv2.imshow("Dashcam", i3)
          cv2.waitKey(1)
          return i3/255.0
    ```
the function block is used in a loop of multiple images where it is suppose to display all the images in a single window.
Repository: pytorch
Issue: Provide a pkg-config file
Labels: module: build,feature,triaged

## 🚀 Feature

A typical install of `libtorch` should come with a `pkg-config` file, describing how to build code relying on libtorch headers and how to link to libtorch libraries.

## Motivation

Users of `libtorch` right now must resort to major hacks in order to correctly build `torch`-dependent code or link to `libtorch`, compared to most other native libraries.

## Pitch

`pkg-config` is the standard and conventional mechanism to provide dependency information and linkage/build instructions on UNIX systems (with maybe an exception of macs).

## Alternatives

People continue to hack around lack of the standard/blessed dependency discovery using the horror known as environment variables. Building any code successfully requires one to always remember to set this environment variable up.

They might also manually hardcode the dependency information into their build tooling. And then suffer breakage or and/or continue using irrelevant dependencies once the dependencies of torch itself change.

## Additional context

https://en.wikipedia.org/wiki/Pkg-config
[Tensorflow has this since 2017](https://github.com/tensorflow/tensorflow/pull/9784)

cc @malfet @seemethere @walterddr
Repository: rust
Issue: 'static closures/FnDefs/futures with non-'static return type are unsound
Labels: A-type-system,A-lifetimes,A-trait-system,A-closures,A-associated-items,P-high,T-lang,T-compiler,I-unsound,C-bug,A-async-await,AsyncAwait-Triaged,S-bug-has-test,T-types

Argument-free closures can return non-`'static` types but be `'static` themselves:
```rust
fn foo<'a>() {
    let closure = || -> &'a str { "" };
    assert_static(closure);
}

fn assert_static<T: 'static>(_: T) {}
```

However, associated types of `'static` types must be `'static`, too. So the fact that the above compiles results in unsoundness, as demonstrated below:
```rust
use std::fmt;
trait Trait {
    type Associated;
}

impl<R, F: Fn() -> R> Trait for F {
    type Associated = R;
}

fn static_transfers_to_associated<T: Trait + 'static>(
    _: &T,
    x: T::Associated,
) -> Box<dyn fmt::Display /* + 'static */>
where
    T::Associated: fmt::Display,
{
    Box::new(x) // T::Associated: 'static follows from T: 'static
}

fn make_static_displayable<'a>(s: &'a str) -> Box<dyn fmt::Display> {
    let f = || -> &'a str { "" };
    // problem is: the closure type of `f` is 'static
    static_transfers_to_associated(&f, s)
}

fn main() {
    let d;
    {
        let x = "Hello World".to_string();
        d = make_static_displayable(&x);
    }
    println!("{}", d);
}
```
([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=f6e496bdbfb1474c8f9153aedd5acac3))
```
���IV
```

@rustbot modify labels: T-compiler, T-lang, A-closures, A-lifetimes, A-traits, A-typesystem, A-associated-items
and someone please add “I-unsound 💥”.

Found this bug while experimenting with variations of #84305.

Without the `dyn` keyword, this seems to compile “successfully” since Rust `1.4.0`. [Godbolt link.](https://godbolt.org/z/dGfW39Yn6)
Repository: rust
Issue: rustdoc: Documentation exposes the original private name instead of the public one
Labels: T-rustdoc,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
mod facade {
    pub struct Facade {}

    impl Facade {
        pub fn foo() {}
    }
}

pub use facade::Facade as Server;
```

When running `rustdoc`, and exposing some `Struct` publicly with a different name than they were defined, the `impl` documentation is using those names that aren't exposed.

![Screenshot_20210420_125004](https://user-images.githubusercontent.com/1161224/115384806-bdd7a900-a1d7-11eb-8fcd-1e36ca6651f1.png)

Documentation should use the public names, nor the original names, since they aren't visible for crate consumers.


### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.51.0 (2fd73fabe 2021-03-23)
binary: rustc
commit-hash: 2fd73fabe469357a12c2c974c140f67e7cdd76d0
commit-date: 2021-03-23
host: x86_64-unknown-linux-gnu
release: 1.51.0
LLVM version: 11.0.1
```

Originally was filled as https://github.com/rust-lang/cargo/issues/9380.
Repository: opencv
Issue: [Feature Request] Add support for sensor type cameras in MSMF
Labels: feature,category: videoio(camera),platform: win32

### Feature Description
Currently OpenCV only supports conventional cameras that would show up on a camera selector. However, there are some sensor devices (e.g. IR camera) that aren't meant to show up as a regular webcam, and therefore OpenCV is unable to recognize them.

### How to implement
These devices can be detected quite easily, by setting a flag in the MSMF loader right before `MFEnumDeviceSources` is called. In [modules/videoio/src/cap_msmf.cpp:544](https://github.com/opencv/opencv/blob/68d15fc62edad980f1ffa15ee478438335f39cc3/modules/videoio/src/cap_msmf.cpp#L544), one filter attribute is set (`MF_DEVSOURCE_ATTRIBUTE_SOURCE_TYPE`) to query video devices only. In order to make it detect sensor devices, a second attribute must be set with GUID `MF_DEVSOURCE_ATTRIBUTE_SOURCE_TYPE_VIDCAP_CATEGORY` and value `KSCATEGORY_SENSOR_CAMERA` (ks.h) like this:
```
attr->SetGUID(MF_DEVSOURCE_ATTRIBUTE_SOURCE_TYPE_VIDCAP_CATEGORY, KSCATEGORY_SENSOR_CAMERA)
```

After this, `MFEnumDeviceSources` will enumerate the desired devices, but not the conventional cameras. For this reason, this should be optional, and some sort of toggleable setting should be implemented on the user API side, so the developer can explicitly enable it if they want to work with non-conventional sensors.

### Additional info
Based on my experiments, this change is only necessary on Windows, because Linux picks up these sensors automatically through the V4L driver, and they work with OpenCV out of the box. I don't have access to a Mac, so I don't know how that would work.

I have tested this function by adding the modification in my local copy of OpenCV and recompiling it, and it works as expected.
Repository: PowerToys
Issue: Have PowerToys Run always visible (like a desktop widget)
Labels: Idea-Enhancement,Product-PowerToys Run

A option for powertoys run to stay on desktop and not disappear, this would be similar to a rainmeter skin and would be useful in many ways such as a way to choose the location of it on the desktop and be able to quickly access it without needing to do alt + space.
Repository: opencv
Issue: Performance issue: bottleneck in cv::ocl::Program::create when animating gaussian blur sigma
Labels: optimization,feature,category: imgproc,priority: low,category: ocl

OpenCV 4.5.2, using Apple OpenCL.
I wanted to use the gaussian blur OpenCL implementation to produce an animated blur on an image with varying kernel sizes and sigma.

Problem:  The separable kernel X/Y are hard-coded into constants in the kernel:
https://github.com/opencv/opencv/blob/master/modules/imgproc/src/filter.dispatch.cpp#L898

The issue is that most of the time spent by the program is within cv::ocl::Program::create to compile the kernel over and over again.

Is there any plans to integrate a *dynamic* variant of the function which does not require a kernel recompilation ?
Repository: go
Issue: cmd/go: diagnose packages listed in lexically-impossible modules in vendor/modules.txt
Labels: help wanted,NeedsFix,GoCommand

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.3 linux/amd6
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

Moved from https://groups.google.com/u/1/g/golang-nuts/c/04MtZ96TPWo

I checked out the kubernetes project at tag v1.20.4.
Then run "go list -deps -json ./... > json.txt" in the project root.
In the produced json.txt file, I noticed that the module path for
two packages look not right. The path of a package should be
prefixed with its module path. But the two aren't. Bug?

The first:
```
{
    "Dir": "/home/myname/opensource/it-infrastructure/kubernetes/vendor/github.com/Azure/go-autorest/autorest/azure",
    "ImportPath": "github.com/Azure/go-autorest/autorest/azure",
    "Name": "azure",
    "Doc": "Package azure provides Azure-specific implementations used with AutoRest.",
    "Module": {
        "Path": "github.com/Azure/go-autorest/autorest/adal",
        "Replace": {
            "Path": "github.com/Azure/go-autorest/autorest/adal",
            "Version": "v0.9.5"
        }
    },
    ...
```
The second:
```
{
    "Dir": "/home/myname/opensource/it-infrastructure/kubernetes/vendor/cloud.google.com/go/compute/metadata",
    "ImportPath": "cloud.google.com/go/compute/metadata",
    "Name": "metadata",
    "Doc": "Package metadata provides access to Google Compute Engine (GCE) metadata and API service accounts.",
    "Module": {
        "Path": "cloud.google.com/go/bigquery",
        "Replace": {
            "Path": "cloud.google.com/go/bigquery",
            "Version": "v1.4.0"
        },
        "Indirect": true
    },
    ...
```
### What did you expect to see?

The path of a package should be prefixed with the path of its containing module.

### What did you see instead?

The paths of two 2 packages are not prefixed with their module paths.