sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Lint: `unused_assignments` lint not triggered when assigning through `Option` on a `Copy` type
Labels: A-diagnostics,T-compiler

When matching over a `&mut Option` and binding the result to a `mut PATTERN` instead of a `ref mut PATTTERN` or `PATTERN`, the resulting pattern is moved out, for copy types this will usually result in an `unused_assignments` lint.

Given the following code ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1a5bc95859328b95d21023136c0c743f)), this doesn't happen, despite the local copy never being read after being assigned.
Changing the Type `A` to not being `Copy` correctly gives an error that the pattern is attempting to move out the value.

```rust
#[derive(Debug, PartialEq)]
struct Container(Option<A>);

#[derive(Debug, Clone, Copy, PartialEq)]
struct A(Option<i32>);

impl Container {
    fn f(&mut self, int: i32) {
        if let Some(mut inner) = &mut self.0 {
            // inner: &mut A
            // mut inner: mut A
            // ref mut inner: &mut A
            // this should trigger a unused_assignments lint as inner is copied out and written but never read
            inner.0 = Some(int);
        }
    }
}

fn main() {
    let mut container = Container(Some(A(None)));
    container.f(42);

    // this fails as the actual variable was not set as expected
    assert_eq!(container, Container(Some(A(Some(42)))));
}
```

The current output is:

```
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
```

Ideally the output should look like:

```
warning: variable `inner` is assigned to, but never used
  --> src/main.rs:9:25
   |
22 |         if let Some(mut inner) = &mut self.0 {
   |                         ^^^^^
   |
   = note: `#[warn(unused_variables)]` on by default
   = note: consider using `_inner` instead

warning: value assigned to `inner.0` is never read
  --> src/main.rs:13:13
   |
23 |            inner.0 = Some(int);
   |            ^^^^^^^
   |
   = note: `#[warn(unused_assignments)]` on by default
   = help: maybe it is overwritten before being read?

warning: `playground` (bin "playground") generated 2 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.13s
```
This was tested on:
```
rustc 1.66.0-nightly (f5193a9fc 2022-09-25)
binary: rustc
commit-hash: f5193a9fcc73dc09e41a90c5a2c97fc9acc16032
commit-date: 2022-09-25
host: x86_64-unknown-linux-gnu
release: 1.66.0-nightly
LLVM version: 15.0.0
```
and on:
```
rustc 1.64.0 (a55dd71d5 2022-09-19)
binary: rustc
commit-hash: a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52
commit-date: 2022-09-19
host: x86_64-unknown-linux-gnu
release: 1.64.0
LLVM version: 14.0.6
```
Repository: PowerToys
Issue: Mouse highlighter ghosting
Labels: Issue-Bug,Area-Quality,Needs-Triage,Needs-Team-Response,Product-Mouse Utilities

### Microsoft PowerToys version

0.63

### Running as admin

- [X] Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

I experience ghosting of the highlighted areas that stay there and do not fade away. I need to reboot the system to "fix" this. For evidence I have added a screenshot of this window while creating the issue...
![image](https://user-images.githubusercontent.com/84451910/194536496-59c18276-4b3f-4fc9-88fa-cb0fe35b3e45.png)


### ✔️ Expected Behavior

After left-click or right-click the highlighted area should not remain highlighted 

### ❌ Actual Behavior

highlighted areas after mouse clicks sometimes remain highlighted.

### Other Software

For what it's worth highlighting stays as an overlay for every application window, but it dissapears (temporarily) when hovering over the open application windows (in the taskbar)
Repository: opencv
Issue: [RISCV] Incompatible change for RVV intrinsics
Labels: optimization,RFC,platform: riscv

Hi all,

The RVV intrinsic community is discussing on the possibility to simplify the intrinsics that will break compatibility. Regarding such change, we are discussing to have a conservative approach that hopes to give the community enough time to adapt to the change. Please consider to drop by and share your thoughts on this [0, 1].

The full letter has been posted on OpenCV forum [2].

[0] https://github.com/riscv-non-isa/rvv-intrinsic-doc/issues/145
[1] https://github.com/riscv-non-isa/rvv-intrinsic-doc/pull/171
[2] https://forum.opencv.org/t/rfc-riscv-possible-incompatible-change-for-rvv-intrinsics/10473

@asmorkalov @joy2myself
Repository: rust
Issue: Make (most?) `std::os::wasi::fs::FileExt` functions available on all Unix platforms
Labels: C-enhancement,T-libs-api,A-io

The methods in `std::os::wasi::fs::FileExt` look a lot like the POSIX `*at` methods.  Would it be possible to make this extension available for all Unix platforms, rather than limiting it to wasi?

There are a lot of reasons to want to use these methods from other Unix operating systems:

- They make it possible to work with paths longer than MAX_PATH.
- They are the only way to interact with files in a Capsicum sandbox on FreeBSD.
- They can prevent TOCTOU vulnerabilities where a directory is moved between accesses to files within that directory.

Tracking issue for `wasi_ext`: https://github.com/rust-lang/rust/issues/71213
Repository: rust
Issue: Deprecated field should not be warned against when it must be used during struct initialization
Labels: A-diagnostics,T-compiler


Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
pub struct Foo {
    #[deprecated(since = "0.52.16", note = "use some other field instead")]
    pub is_project: bool
}

fn main() {
    let _ = Foo {
        is_project: false
    };
}
```

The current output is:

```
warning: use of deprecated field `Foo::is_project`: use some other field instead
 --> src/main.rs:8:9
  |
8 |         is_project: false
  |         ^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(deprecated)]` on by default
```

Ideally there should be no warning. Because it's nice to be allowed to use the simple way of constructing a struct, in which case there's no point in avoiding initializing deprecated structs to some default values, or am I the only one who thinks so? I just don't see how this warning can be useful in this use case.
Repository: vscode
Issue: Editor: subpixel font rendering issue
Labels: bug,linux,font-rendering

Type: <b>Bug</b>

Issue:

Subpixel rendering is broken for some character columns.

![Screenshot_20221007_132722](https://user-images.githubusercontent.com/11392016/194549248-4fa267ce-ffef-4b5c-8b63-df606bd8ff22.png)

Steps to Reproduce:

1. Open the attached text file (with a set of characters on which it is easy to spot the problem).
[Squares.txt](https://github.com/microsoft/vscode/files/9733769/Squares.txt)

VS Code version: Code - Insiders 1.73.0-insider (fad3a77833b9249158dfd88477114a06435e46a2, 2022-10-07T05:18:21.081Z)
OS version: Linux x64 5.19.13-1-default
Modes:
Sandboxed: Yes

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (8 x 3090)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: disabled_software<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|1, 0, 0|
|Memory (System)|7.65GB (3.19GB free)|
|Process Argv|--unity-launch --crash-reporter-id d05f2a7e-d301-4bc0-b91d-db5f7c340441|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|/usr/share/xsessions/default|
|XDG_CURRENT_DESKTOP|KDE|
|XDG_SESSION_DESKTOP|KDE|
|XDG_SESSION_TYPE|x11|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30404738
cppdebug:30492333
vscaat:30438846
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pylantcb52:30568093
vscccc:30564267
pyindex848:30577858

```

</details>

<!-- generated by issue reporter -->
Repository: create-react-app
Issue: CRA within yarn workspace, how to make ESLint also check code from local dependency within the same workspace.
Labels: needs triage

Hi there, I have a monorepo yarn workspace with one CRA and multiple other packages, I notice CRA ESLint only check codes within CRA folder, is there any way also make ESLint check codes from local dependencies within the same yarn workspace?
Repository: flutter
Issue: Add the file `url` and / or `path`  in the `video_player` error handling
Labels: c: new feature,p: video_player,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case

I am playing videos using `video_player` and i do see reports in my Crashlytics dashboard telling me things like this : 

![Capture d’écran 2022-10-07 à 14 33 43](https://user-images.githubusercontent.com/32631467/194554373-574e7256-0eb0-4b0c-9f66-01a25c31cbcb.png)

This is just non-actionable as i don't see what file is throwing this exception. 
This happens in my case with my beta test users. 

## Proposal

It would be really nice to have the `url` or the `path` of the file that can't be read by the player, for any kind of error. 
It is actually the case for `Image` widgets that allows you to quickly check the URL and see what's wrong.
Repository: godot
Issue: Single `[indent]` not working properly in `RichTextLabel`
Labels: bug,topic:gui

### Godot version

v4.0.beta.custom_build [61021c08f]

### System information

Kubuntu 22.04

### Issue description

A single `[indent]` (or `push_indent`) is handled incorrectly (indented only after `\n`) if there is another open `Item` before it. However, if `[indent]` is the first one, or there are multiple `[indent]`, then the indentation is correct.

In particular, this bug can be seen in Editor Help:

![](https://user-images.githubusercontent.com/47700418/194553685-cc7d0d64-7074-464a-9704-9123138f2a9d.png)


### Steps to reproduce

<table>

<tr>
<th>BBCode</th>
<th>Result</th>
<th>Comment</th>
</tr>

<tr>
<td>
<pre>[indent]123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194558632-b8ecfdd0-cd7f-462a-899e-c08ae04e2161.png)

</td>
<td>Correct.</td>
</tr>

<tr>
<td>
<pre>[u][indent]123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194550247-632ce819-baa0-4d33-a4ef-bf9c9ca1476d.png)

</td>
<td>The bug.</td>
</tr>

<tr>
<td>
<pre>[indent][u]123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194550523-ee25c77b-5266-4b18-bd12-f53bbb99d077.png)

</td>
<td>Correct.</td>
</tr>

<tr>
<td>
<pre>[u][indent][indent]123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194550750-b3b20ee5-bade-4c2f-83dd-3dc8a5a19601.png)

</td>
<td>If there is more than one <code>[indent]</code>, then it is correct.</td>
</tr>

<tr>
<td>
<pre>[u][indent]
123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194551101-6f5c4bb6-5b82-489e-b260-44fe8a10db8d.png)

</td>
<td></td>
</tr>

<tr>
<td>
<pre>000[u][indent]123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194551337-301a9ec2-9ace-442c-b86f-55141aa3aff4.png)

</td>
<td>Is this also a bug? What should be in this case?</td>
</tr>

<tr>
<td>
<pre>[u][indent][u]123
456</pre>
</td>
<td>

![](https://user-images.githubusercontent.com/47700418/194551782-6dc1b85e-a316-48e8-b60d-9978c274852f.png)

</td>
<td></td>
</tr>

</table>


### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: Auto renaming when resizing images
Labels: Product-Image Resizer,Needs-Triage

### Description of the new feature / enhancement

Love love the Image Resizer. We always need both 500x500 and 100x100 product pictures for our e-commerce website, this saves so much time. What would make it even awesomer, would be if it could replace a specified string in the file name with another string. For example, when I have the 500x500 image, it must be named ProductPic-large.jpg and when is resized down to 100x100 it must be names ProductPic-small.jpg . So if Image Resizer could take -large out of the filename and replace it with -small all in the same operation, that would be so slick!!

### Scenario when this would be used?

See above

### Supporting information

_No response_
Repository: PowerToys
Issue: ppm support for preview pane in file explorer
Labels: Idea-New PowerToy,Product-File Explorer

### Description of the new feature / enhancement

Similar to what we have for pdf, markdown, svg, etc. in the preview pane in file explorer, we should add support to preview ppm image files as well. 

### Scenario when this would be used?

Whenever someone outputs to a ppm file, they can easily view what the image looks like without needing to open an image viewing program

### Supporting information

_No response_
Repository: PowerToys
Issue: Move window onscreen
Labels: Needs-Triage

### Description of the new feature / enhancement

An easy way to move a window that is completely off-screen back onto the screen again so I can interact with it.

### Scenario when this would be used?

When the application that I am using opens a window that is completely off-screen.

### Supporting information

_No response_
Repository: flutter
Issue: 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'
Labels: engine,platform-mac,c: proposal,a: desktop,P3,team-macos,triaged-macos

## Background

I am attempting to extend my flutter application to load VST plugins and I'm unsure if there's a workaround for this exception on MacOS. 

In case the reader is unaware, it is common for music production software to load plugins (distributed as a dll/so/dylib) that perform various kinds of audio processing (like emulating a synthesizer), into the address space of your host software. These plugins will process audio passed to them by the host software, and can render their own GUIs. One common plugin specification is the VST format, which I'm attempting to load into my application. 

## Steps to Reproduce

A loader for the VST format has already been implemented in the [JUCE](https://docs.juce.com/master/classAudioPluginInstance.html) framework, so I wrote a small C++ wrapper around JUCE, that builds as a dynamic library, and exports a few functions like `ffi_create_plugin`, `ffi_plugin_process_audio` and `ffi_plugin_show_gui`. My flutter application can then load this dynamic library, and call the exported functions, which will in turn load a selected VST plugin. 

I can successfully load a headless VST plugin this way. The problem is when I call `ffi_plugin_show_gui`, (when a user presses a button). At this point the application crashes with an unhandled exception: `'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'`. 

## The Cause

UIKit is not thread safe, so all calls to it must be made by the main thread. Most VST plugins will use UIKit. So the exception is caused by triggering the GUI creation on a non-main thread. Therefore, I need a way in flutter to call the export that creates the GUI from the main thread, instead of whatever thread it is currently being called from.

## Potential Solutions

 - **Create the GUI from the main thread**: I don't have a great understanding of Flutter's threading model, but perhaps there's a way to call `ffi_plugin_show_gui` from the main thread. I've dug through the docs and have not found a documented way to do this.
 - **Disable Main Thread Checker**: The apple [developer docs](https://developer.apple.com/documentation/xcode/diagnosing-memory-thread-and-crash-issues-early) show it is possible to disable the check that causes this exception. Perhaps because each window will be be calling UIKit on a single thread, it doesn't matter that it isn't called on the main thread. I'm not sure if doing this would be safe, and I'm not sure how to configure this in flutter.
 - **Something else**: Perhaps someone who understands Flutter better than me can propose a better solution.

I'm worried that Flutter's architecture will make this impossible, which would pose a significant problem for my project.

Thanks in advance for any assistance or advice.
Repository: vscode
Issue: Terminal quick fix API
Labels: feature-request,api,api-proposal,terminal-quick-fix

Forking this off from https://github.com/microsoft/vscode/issues/145234 as that one is more focused on listening for and reacting to commands generally, not quick fixes.
Repository: svelte
Issue: Context functions documentation is misleading/incomplete
Labels: documentation

### Describe the bug

The documentation for the various context functions does not really communicate that contexts are inherited by all descendants, referring to "parent" and "children" rather than ancestors and descendants.

Additionally, for context retrieval the *current component* is used as reference *not* the parent or another ancestor.

[`setContext`](https://svelte.dev/docs#run-time-svelte-setcontext)
> The context is then available to **children** of the component (including slotted content) with `getContext`.

[`getContext`](https://svelte.dev/docs#run-time-svelte-getcontext)
> Retrieves the context that belongs to the **closest parent** component with the specified `key`.

[`hasContext`](https://svelte.dev/docs#run-time-svelte-hascontext)
> Checks whether a given `key` has been set in the context of a **parent** component.

[`getAllContexts`](https://svelte.dev/docs#run-time-svelte-getallcontexts)
> Retrieves the whole context map that belongs to the **closest parent** component.

I am unsure how exactly this should be phrased instead.

For `setContext` I considered the use of "descendants" instead of "children" but maybe it would be unclear that is referring to the component hierarchy.

For the get-functions maybe something along the lines of "current component or any of its ancestors" would be better.


### Reproduction

See:
- `site/content/docs/04-run-time.md`
- `src/runtime/internal/lifecycle.ts`

### Logs

_No response_

### System Info

```shell
-
```


### Severity

annoyance
Repository: flutter
Issue: NavigationRail needs tooltips
Labels: c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design



## NavigationRail needs Tooltips

We use a bottom controlbar, this has iconbuttons and we can use tooltips to let the user know what the icon is.
NavigationRail sort of has icon buttons.  We can use the labeltype, but it uses too much space.
Adding this feature of "tooltip" allows for desktop consistency with other iconbuttons
## Proposal
Add a property of **toolTip** just like the IconButton has.
or 
add a new label type  **NavigationRailLabelType.toolTip**
This way, we can keep our skinny rail skinny.

Picture below shows our app.  If we show all labels, we waste space.

![image](https://user-images.githubusercontent.com/18184280/194586563-de8cbeb2-d74b-416b-b436-d3a756d6074b.png)
Repository: storybook
Issue: Digest method not supported
Labels: question / support,angular

### Discussed in https://github.com/storybookjs/storybook/discussions/19392

<div type='discussions-op-text'>

<sup>Originally posted by **naveenkal** October  7, 2022</sup>
I upgraded to Angular 14 and I can't get storybook to build successfully.

Getting below error :

```
99% done plugins webpack-hot-middlewarewebpack built preview c4fd3adfedabce8e8e4b in 28712ms
WARN Force closed manager build
ModuleBuildError: Module build failed (from /node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Digest method not supported
    at /node_modules/@ngtools/webpack/src/ivy/loader.js:81:18
    at processResult (/node_modules/@storybook/builder-webpack5/node_modules/webpack/lib/NormalModule.js:701:19)
    at /node_modules/@storybook/builder-webpack5/node_modules/webpack/lib/NormalModule.js:807:5
    at /node_modules/loader-runner/lib/LoaderRunner.js:399:11
    at /node_modules/loader-runner/lib/LoaderRunner.js:251:18
    at context.callback (/node_modules/loader-runner/lib/LoaderRunner.js:124:13)
    at /node_modules/@ngtools/webpack/src/ivy/loader.js:81:9
ModuleBuildError: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Digest method not supported
```

Here are the relevant packages I have installed:


```
   "@angular-devkit/build-angular": "14.2.0",
    "@angular-eslint/eslint-plugin": "14.0.0",
    "@angular-eslint/eslint-plugin-template": "14.0.0",
    "@angular-eslint/template-parser": "14.0.0",
    "@angular/cli": "~14.2.0",
    "@angular/compiler-cli": "14.2.0",
    "@angular/language-service": "14.2.0",
    "@storybook/angular": "6.5.11",
    "@storybook/builder-webpack5": "6.5.11",
    "@storybook/manager-webpack5": "6.5.11",
```
Repository: storybook
Issue: Support multiple types for Vue
Labels: bug,needs triage

**Describe the bug**
Some of my components can accept props of different types, for example String or Number, but when It comes to the Storybook - it renders input as object. 

I'm not sure if that's a bug or it suppose to behave like that, but would be perfect if there is a possibility to select one of types that are specified in props and render input field for that type

**To Reproduce**

_component.vue_
```javascript
<template>
  <element :height=""height" :width="width" />
</template>

<script lang="ts">
import Vue from "vue";

export default Vue.extend( {
  name: 'component',
  props: {
    'width':{
      type: [String, Number],
      default: undefined,
    },
    'height':{
      type: [String, Number],
      default: undefined
    },
  },

) 
</script>
```

_component.stories.js_
```javascript
import component from "../components/component.vue";

export default {
  title: "Component",
  component: component,
};

export const Component = (args, { argTypes }) => ({
  components: {
    component,
  },
  props: Object.keys(argTypes),
  template: '<component v-bind="$props" />',
});

```