sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: The entire component is redrawn when props are changed in the "Docs" section
Labels: question / support,vue,addon: docs,args,addon: controls

**Describe the bug**
The entire component is redrawn when properties are changed in the "Docs" section.

**To Reproduce**
Steps to reproduce the behavior:

1. `git clone https://github.com/schoonc/test-storybook-vue-docs-render`
2. `npm i`
3. `npm run storybook`
4. Change the prop in "Canvas" section. We see that the color of the element changes smoothly (storybook changes only the class of the element).
5. Change the prop in "Docs" section. We see that the color of the element changes immediately (storybook completely redraws the element).

**Expected behavior**
The component must not be completely redrawn.

**Screenshots**
![image](https://user-images.githubusercontent.com/4659633/95054054-f27f8980-06f9-11eb-99e4-977af8e09479.png)
![image](https://user-images.githubusercontent.com/4659633/95054235-3ffbf680-06fa-11eb-81ad-47f3cc066d12.png)

**Code snippets**
dependencies in the package.json:
```
"devDependencies": {
    "@babel/core": "^7.11.6",
    "@storybook/addon-actions": "^6.0.25",
    "@storybook/addon-essentials": "^6.0.25",
    "@storybook/addon-links": "^6.0.25",
    "@storybook/vue": "^6.0.25",
    "babel-loader": "^8.1.0",
    "react-is": "^16.13.1"
  },
  "dependencies": {
    "vue": "^2.6.12",
    "vue-loader": "^15.9.3",
    "vue-template-compiler": "^2.6.12"
  },
```

.storybook/main.js:
```
module.exports = {
  "stories": [
    "../stories/**/*.stories.js"
  ],
  "addons": [
    "@storybook/addon-essentials"
  ]
}
```

stories/testdiv.css:
```
.testdiv {
  background: blue;
  transition: all 1s;
}
.testdiv-red {
  background: red;
}
```

stories/Testdiv.stories.js:
```
import Testdiv from './Testdiv.vue';

export default {
  title: 'testdiv',
  component: Testdiv,
};

export const Default = (args, { argTypes }) => ({
  props: Object.keys(argTypes),
  components: { Testdiv },
  template: '<testdiv v-bind="$props" />',
})
```

stories/Testdiv.vue:
```
<template>
  <div class="testdiv" :class="{'testdiv-red': red}">TEST</div>
</template>

<script>
import './testdiv.css';

export default {
  name: 'testdiv',

  props: {
    red: Boolean
  },
};
</script>
```

**System**
```
Environment Info:

  System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  Binaries:
    Node: 12.18.4 - /usr/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.6 - /usr/bin/npm
  Browsers:
    Chrome: 84.0.4147.125
    Firefox: 81.0
```

It would be interesting to know the reason for such behavior. And if it is technically justified (e.g. technically difficult to implement at the moment), it would be cool to describe this behavior in documentation.
Repository: PowerToys
Issue: [FZ Editor] get PowerToysIssuesURL from a common settings
Labels: FancyZones-Editor,Product-FancyZones,Area-Quality,Priority-3,Cost-Small

Need a common place for URLs like `https://aka.ms/powerToysReportBug`,  that can be used by C++ and C# projects.
Repository: flutter
Issue: Theming improvements for Input Decoration
Labels: framework,f: material design,d: api docs,c: proposal,team-design,triaged-design

## Use case

I am unhappy with the default color used for Input Decorations that do not have the focus.  When an Input has focus, the icon, label, and underline (for a TextFormField example) are drawn with the Theme's primary color.  However, when the input does not have focus, a gray (or partially transparent black) is used.  We seem to not really have any control over that default color.

In my case, the gray combined with the off-white surface color (not illustrated), creates insufficient contrast and makes things hard to read.  For a pixel perfect framework, we should be able to adequately control the color palettes used by widgets.

<img width="398" alt="Screen Shot 2020-10-05 at 2 58 14 AM" src="https://user-images.githubusercontent.com/123887/95066041-b840c880-06b6-11eb-88e9-8bced04c9bd7.png">


## Proposal

I imagine the most logical approach is to _add_ a `color` field to [InputDecorationTheme](https://api.flutter.dev/flutter/material/InputDecorationTheme-class.html) so that an app can customize it along with the rest of the [ThemeData](https://api.flutter.dev/flutter/material/ThemeData-class.html).

Then, the framework uses that color to draw Input Decorations that do not have focus.  (Note that `focusColor` already exists.)

Finally, clear documentation on how to use Themes to control the colors of built-in widgets is very welcome.

## Related Issues

 * #48882
 * #18478
Repository: flutter
Issue: Widget Inspector: Edit-in-place and inheritance markups for properties
Labels: framework,f: inspector,a: debugging,c: proposal,d: devtools,P3,team-framework,triaged-framework

## Use case

Most common use case for the inspector is the debugging of rogue spaces in the UI. However, once you identify the offending widget in the widgets tree, it is very difficult to locate that widget in the code, and make the necessary changes to it. And once you locate it, you may end up editing the wrong widget because there's no clear inheritance markup (like you might find in a browser's inspector tab).

Adding the possibility to both link directly from the widget tree to the relevant widget in the code, along with the inheritance tree for any given property will greatly improve this workflow.

## Proposal

I propose the following:
1. When selecting a widget in the **Details Tree** view, a new panel should be added to the view (on the right / on the bottom / floating / user-configured) that will show the widget's properties, along with a new **Inheritance Tree** of the whatever property the user selects. From there, the user can edit the selected property, and have the app refresh the view based on the changes. (Again, this is basically copying the behavior of of modern browsers, like Chrome.)
2. Add the ability to "Jump to definition" from the inspector window. Preferably via a context menu option. (Right click on a widget/property and select **Go to definition**.)

Now that The DevTools are being more closely integrated with the IDEs, it makes sense to add the above.
Repository: pytorch
Issue: Support torch.mean for BoolTensors and other integer tensor inputs (without manual upcasting and hopefully without hidden upcasting)
Labels: triaged,module: numpy,module: type promotion,module: reductions

I suggest that it upcasts to torch.float32 automatically, like in NumPy. For sum it works and upcasts to torch.long.

Is it a duplicate? Could not easily find the previous issue :/  Or in https://github.com/pytorch/pytorch/issues/38349

```python
import torch
import numpy

print(torch.__version__)
# 1.6.0

a = numpy.array([True, False, True])
print(a.mean())
# 0.6666666666666666

b = torch.tensor([True, False, True])
print(b.mean())
#   File "bug2.py", line 10, in <module>
#    print(b.mean())
# RuntimeError: Can only calculate the mean of floating types. Got Bool instead.
```

Mean on a bool tensor is a frequent way to compute accuracy. Of course, the workaround is to cast to float() before mean().

cc @mruberry @rgommers @nairbv
Repository: PowerToys
Issue: Save desktop layout and opened windows per project
Labels: Idea-Enhancement,Product-Window Manager

Hello there,

It would be awesome to be able to save an entire desktop, so that it can be restored in one click.

Let's say you are working on several projects (whether these a professional projects or personal ones), each project having its own set of applications opened (vscode, db tools, terminals, browser with specific URLs etc ...), what would be nice is

1. using PowerToys, I can save this configuration (including windows positions)
2. Give it a name
3. and have everything saved somewhere

And then, later on, I can select this "profile" and have all my applications reopened (vscode / vs studio with the correct project loaded, browser with the correct tabs opened, windows position as it was before etc ...)

I can imagine how huge this feature would be in term of development, but it would also be a huge time saver .. (which is, unless I am mistaken, the purpose of these amazing tools 😇).

Cc @ThomasLebrun who actually came with this idea!

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: TypeScript
Issue: Variadic element of tuple-like intersection types are spreading incorrectly
Labels: Bug

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:** 4.0.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** variadic tuple, variadic element, intersection type, tuple-like type

**Code**

```ts
type T1 = [...unknown[] & []]; // never[]
type T2 = [...number[] & [1, 2, 3]]; // (3 | 1 | 2)[]
```

**Expected behavior:** for `T1`, I expected it to be `[]`(empty tuple type) and for `T2`, I expected it to be `[1, 2, 3]`.

**Actual behavior:** Both `T1` and `T2` became Array rather than tuple somehow. (`T1` is deduced to `never[]`, `T2` is deduced to `(3 | 1 | 2)[]`)

#### detailed explanation

In some perspective, `unknown` could be recognized as *type of all types*. Therefore, `[unknown]` is *type of all type-level 1-tuples* and intuitively, `unknown[]` is *type of all type-level n-tuples*. 

So `[] <: unknown[]` is true (i.e. *all empty type-level tuple* is subtype of *all type-level n-tuples*) and you can check it simply with this code:
```
type M = [] & unknown[] extends [] ? [] extends [] & unknown[] ? true : false : false; // true
```

However, in spite of the fact that `[]` is subtype of `unknown[]` therefore `[] & unknown[]` is actually `[]`, variadic element of `[] & unknown[]` somehow spreads as `never[]`, which is incorrect and unintuitive.

**Playground Link:** [Playground](https://www.typescriptlang.org/play?#code/C4TwDgpgBAKgjFAvFA2gOgwVwHYGtsD2A7tigLpQBkqZZA3FAPSNTYQBuEATuQLABQoSLABMSVBjTZMAWwBG3clVRwANFBHqAzLQbMoACi1QAPlARmRASnJA)
Repository: deno
Issue: Adding Resource Timing API
Labels: cli,suggestion

Deno has support for User Timing API, but I couldn't find reference to Resource Timing API https://w3c.github.io/resource-timing. Is there I would like to help implementing this if it doesn't exist already
Repository: create-react-app
Issue: error in creating react app
Labels: stale

i face an error in create-react-app

Error: EPERM: operation not permitted, mkdir 'C:\Users\M'
command not found: create-react-app

Please help me!
Repository: PowerToys
Issue: [Screen Readers - Power Toys - Power ToysRun]: Screen reader conveys incorrect information as the 'Power ToyRun' is launched using the Shortcut key defined.
Labels: Issue-Bug,Product-PowerToys Run,Priority-2,Area-Accessibility,A11yE+D,A11ySev3,A11yWCAG

[Power Toys Utility-Power ToysRun]

User Impact:
If the object role, state(s), properties, boundary, name, and description are not programmatically determinable, it would be difficult for the platforms that provide Accessibility APIs, and would in turn affect the screen reader dependent users to determine the object properties. 

Test Environment:
OS Version: 20221.1000
App Name: Power Toy Preview
App Version: v0.23.0
Screen Reader: Narrator

Reproe-Steps:
1. Launch Narrator.
2. Open Power Toys Settings App.
2. Navigate to 'Power ToyRun' menu item and activate it.
3. Set the shortcut key for Power ToyRun say 'Ctrl+Shift+U'. 
4. Launch the Power ToyRun using shortcut key defined.
5. Observe the issue.

Actual Result:
Screen reader conveys incorrect information as the 'Power ToyRun' is launched using the Shortcut key defined. On launching 'Power ToyRun' using defined shortcut key, screen reader conveys, "Power launcher... edit query... suggestion available" even when no suggestion is visible.

Expected Result:
Screen reader should convey correct information as the 'Power ToyRun' is launched using the Shortcut key defined. On launching 'Power ToyRun' using defined shortcut key, screen reader should convey including placeholder value like, "Power launcher... edit query... type here" when no suggestion is visible.

MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7Ba12f3779-bdf1-40c2-bbcc-0e314ea94858%7D&cid=527f8cbc-bff7-4ac3-ab35-5b2a8b2f6762

[49_UIA.zip](https://github.com/microsoft/PowerToys/files/5328753/49_UIA.zip)
[49_MAS4.2.1_Screen_reader_incorrect_information_search_power_launcher.zip](https://github.com/microsoft/PowerToys/files/5328754/49_MAS4.2.1_Screen_reader_incorrect_information_search_power_launcher.zip)
Repository: PowerToys
Issue: [Keyboard Navigation: Settings>Keyboard Manager>Remap a Key]: Keyboard focus is lost on the window after activating 'Remap a Key' button. 
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Product-Settings,Area-User Interface,Priority-2,Area-Accessibility,A11yE+D,A11ySev3,A11yWCAG

[Power Toys Settings- Keyboard Manager>Remap Key]

User Experience:
"This will impact the keyboard users if after activating a button focus is lost on the window.
"

Test Environment:
"OS Version: 20221.1000
App Name: Power Toy Preview
App Version: v0.23.0
Screen Reader: Narrator"

Repro-steps:
"1. Open Power Toys Settings App.
2. Naviagate to Keyboard Manager list item present in left pane and activate it.
3. Navigate to 'Remap a key' button in right pane  and activate it.
4. Verify the issue."

Actual Result:
"Keyboard focus is lost on the window after activating 'Remap a Key' button. After pressing tab key , focus lands to 'OK' button.

Note:
Same issue is repro after activating 'Remap Shortcuts'."

Expected Result:
"Keyboard focus is lost on the window after activating 'Remap a Key' button. After pressing tab key , focus lands to 'OK' button.

Note:
Same issue is repro after activating 'Remap Shortcuts'." Keyboard focus should not be lost on the window after activating 'Remap a Key' button. It should land on 'OK' button and Screen reader should announce the opened dialog info like Remap keys Dialog Ok Button.

MAS Reference:
"https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0de7fbe1-ad7e-48e5-bcbb-8d986691e2b9}
"
[10_Remap key_MAS3.2.1_After activating Remap a key focus is lost.zip](https://github.com/microsoft/PowerToys/files/5328820/10_Remap.key_MAS3.2.1_After.activating.Remap.a.key.focus.is.lost.zip)
Repository: pytorch
Issue: The same function can have different signatures in  the torch and torch.nn.functional namespaces
Labels: module: nn,triaged

## 🐛 Bug

Some functions like max_pool* have different signatures in torch and torch.nn.functional namespaces. In particular, the code in https://github.com/pytorch/pytorch/blob/cf48872d28f945d47793f63e19c54dd15bf580f7/torch/nn/functional.py#L588 is creating this divergence since it adds the return_indices param to max_pool that does not exist in native_functions (only max_pool*_with_indices have it).

## Expected behavior

The signatures should match.

## Additional context

Related issue https://github.com/pytorch/pytorch/issues/45494


cc @albanD @mruberry
Repository: PowerToys
Issue: [FancyZones] Move newly created windows based on their window title to defined zones with title wildcards
Labels: Idea-Enhancement,Product-FancyZones

## 📝 Provide a description of the new feature
Instead of using only the Application, use the Window TITLE with editable "Wildcards".

_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_

If i have recurring Pop-Ups within a Chromium-Browser (or any other application) i can define a Window TITLE with a wildcard and snap these Windows automatically to a pre-defined zone.

For example a new window with Title
   "Ticket 20020202.1002 Microsoft Teams"
snap to Zone 1, a new Window with Title
   "Ticket 20200303.1003 Chocolatey"
snap to Zone 1, but ANY OTHER Window from Edge Chromium, snap to Zone 3.

Configure is possible within the Editor:

   "Ticket*" and Application "edge.exe" to "Zone 1"


---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: PowerToys
Issue: [Keyboard Navigation - Power Toys - Fancy Zones > Launch Zone Editor]: Focus gets lost after activating 'Launch Zones Editor' button.
Labels: Issue-Bug,FancyZones-Editor,Resolution-Fix Committed,Priority-2,Area-Accessibility,A11yE+D,A11ySev3,A11yWCAG

[Power Toys Utility-Launch Zones Editor]

User Impact:
If a user navigates sequentially from one element to another, forced focus changes can confuse the keyboard dependent user. User will face difficulty in interacting with desired element.

Test Environment:
OS Version: 20221.1000
App Name: Power Toy Preview
App Version: v0.23.0
Screen Reader: Narrator

Reproe Steps:
1. Open Power Toys Settings App.
2. Navigate to 'Fancy Zones' menu item and activate it. 'Fancy Zone' pane will open.
3. Navigate to 'Launch Zone Editor' button and activate it. 'Choose your layout for this desktop' window will open.
4. Observe the issue.

Note:
1. Same issue is repro after activating Edit Selected layout button. Please refer the attachment, "59_MAS3.2.1_Focus_not_land_choose_layout_fancy_pane.wmv".
2. This issue is repro for all the dialog which opens thorughout the app.

Actual Result:
Focus gets lost after activating 'Launch Zones Editor' button.

Expected Result:
Focus should not get lost after activating 'Launch Zones Editor' button. Focus should land on first interactive element of the 'Choose your layout for this desktop' window which opens after activating 'Launch Zones Editor' button. 

MAS Reference:
https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7Ba4bbd37d-ee11-485e-b5c8-0539f0ac94b2%7D&cid=1fa2e1bd-4f2b-4da7-ba32-1b5727eb74ae

[59_MAS3.2.1_Focus_not_land_choose_layout_fancy_pane.zip](https://github.com/microsoft/PowerToys/files/5329058/59_MAS3.2.1_Focus_not_land_choose_layout_fancy_pane.zip)
[59_UIA.zip](https://github.com/microsoft/PowerToys/files/5329060/59_UIA.zip)
[59_MAS3.2.1_Focus_not_land_choose_layout_fancy_window.zip](https://github.com/microsoft/PowerToys/files/5329062/59_MAS3.2.1_Focus_not_land_choose_layout_fancy_window.zip)
Repository: vscode
Issue: Incorrect syntax error highlighting in workspace folder list
Labels: under-discussion,file-decorations


Issue Type: <b>Bug</b>

I use VS Code to develop WordPress plugins in PHP.

1) Create a PHP file with a syntax error in it.
2) Save it.

VS Code will highlight the file name in the folder list in red indicating the presence of an error. Further, it will red highlight all of the files parent folders all the way up the tree to indicate the presence of a syntax error.

I find this functionality to be very helpful.

3) Go to VS Code Settings and exclude the file from the workspace.

The file disappears from the  folder list under the Explorer tab. That's what I would expect.

But the parent folders all the way up the tree, continue to be red highlighted indicating the presence of a syntax error.

That is bad. I would expect that if the file with a syntax error is not included in the workspace, then the parent folders would no longer be red highlighted.

While developing, I will move code that's not working correctly, that I'm rewriting and replacing, to a subfolder. Sometimes I do that because the broken code shows the proper way to call a particular function, or is a way of doing something that I don't want to forget, etc. I want to keep the code, and keep it associated with the project. I may use some of it later.

Often those code snippets have errors. So, I exclude those folders and files from the project with .gitignore, and VS Code Settings Exclusions.

Unfortunately, VS Code continues to show me there is an error in the not-displayed, not-included file by highlight the parent folders in red. This renders the whole functionality of highlighting folders and files with errors useless because I just ignore the highlighting.

VS Code version: Code 1.49.3 (2af051012b66169dde0c4dfae3f5ef48f787ff69, 2020-10-02T17:57:01.595Z)
OS version: Windows_NT x64 10.0.19041

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3392)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>opengl: enabled_on<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.89GB (9.27GB free)|
|Process Argv|--crash-reporter-id 4a8c61d7-f6d3-495d-9576-c69834d93045|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (2)</summary>

Extension|Author (truncated)|Version
---|---|---
php-debug|fel|1.13.0
php-intellisense|fel|2.3.14


</details>
<!-- generated by issue reporter -->
Repository: PowerToys
Issue: [Screen Readers - Power Toys - Power Rename]: Screen reader do not convey the confirmation feedback after successfully activating Rename button.
Labels: Issue-Bug,Product-PowerRename,Priority-1,Area-Accessibility,Needs-Triage,A11yE+D,A11ySev3,A11yWCAG

[Power Toys Utility - Power Rename]

**User Experience:**
If there is no notification of events relevant to user interactions, changes in the component’s state(s), value, name, description, or boundary it would be difficult for the platforms that provide Accessibility APIs, and would in turn affect the screen reader dependent users to determine the information of any new page , new dialog box etc. 

**Test Environment:**
OS Version: 20221.1000
App Name: Power Toy Preview
App Version: v0.23.0
Screen Reader: Narrator

**Repro Steps:**
1. Launch Narrator.
2. Open Power Toys Settings App.
2. Open File explorer and select multiple files and open context menu and select Power rename. 'Power Rename' dialog will open.
3. Make some changes like 'Enter character' in 'Search for edit box and and enter character in 'Replace' edit box.
4. Navigate to 'Rename' button and activate it.
5. Observe the issue.

**Actual Result:**
Screen reader do not convey the confirmation feedback after successfully activating Rename button.

**Note:**
This issue is repro with other screen reader(NVDA and JAWS)
This issue is repro throughout the app.

**Expected Result:**
Screen reader should convey the confirmation feedback after successfully activating Rename button like 'Renamed' so that user would get to know some action has been performed.

**MAS Reference:**
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7Bb19c05bd-d82f-4d6d-a8e5-7081bf5c2dba%7D&amp;cid=a71d15c7-f265-41b8-8e0c-8731d60f0a6c

[38_Screen_reader_no_confirmation_rename.zip](https://github.com/microsoft/PowerToys/files/5329112/38_Screen_reader_no_confirmation_rename.zip)
[38_UIA_dialog.zip](https://github.com/microsoft/PowerToys/files/5329117/38_UIA_dialog.zip)