sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: Storybook ComponentMeta ts errors after upgrading to 6.4.18
Labels: bug,typescript,csf

**Describe the bug**
Storybook ComponentMeta only excepts optional props in the component's interface

@storybook/react v6.4.18
    "@storybook/addon-a11y": "^6.4.18",
    "@storybook/addon-actions": "^6.4.18",
    "@storybook/addon-controls": "^6.4.18",
    "@storybook/addon-essentials": "^6.4.18",
    "@storybook/addon-links": "^6.4.18",
    "@storybook/react": "^6.4.18",
     "msw-storybook-addon": "^1.6.0",

**Additional context**
After updating to the latest version (v6.4.18), I got a typescript error when the component's props are not optional.

For example the following code:
```
import {mswDecorator} from "msw-storybook-addon";

interface FooProps {
  foo: string;
}
function Foo(props: FooProps){
  return <div>{props.foo}</div>
}
export default {
  title: "Foo",
  component: Foo,
  decorators: [mswDecorator],
} as ComponentMeta<typeof Foo>;
const FooTemplate: ComponentStory<typeof Foo> = (args) => {
  return (
    <>
      <Foo {...args} />
    </>
  );
};

export const DefaultFoo = FooTemplate.bind({});
DefaultFoo.args = {
    foo: "baz",
}
```
Will throw the following error:


```
Conversion of type '{ title: string; component: (props: FooProps) => JSX.Element; decorators: (DecoratorFunction<unknown> | DecoratorFunction<StoryFnReactReturnType>)[]; }' to type 'ComponentMeta<(props: FooProps) => Element>' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type '{ title: string; component: (props: FooProps) => JSX.Element; decorators: (DecoratorFunction<unknown> | DecoratorFunction<StoryFnReactReturnType>)[]; }' is not comparable to type 'BaseAnnotations<ReactFramework, FooProps>'.
    Types of property 'decorators' are incompatible.
      Type '(DecoratorFunction<unknown> | DecoratorFunction<StoryFnReactReturnType>)[]' is not comparable to type 'DecoratorFunction<ReactFramework, FooProps>[]'.
        Type 'DecoratorFunction<unknown> | DecoratorFunction<StoryFnReactReturnType>' is not comparable to type 'DecoratorFunction<ReactFramework, FooProps>'.
          Type 'DecoratorFunction<StoryFnReactReturnType>' is not comparable to type 'DecoratorFunction<ReactFramework, FooProps>'.
            Types of parameters 'fn' and 'fn' are incompatible.
              Types of parameters 'update' and 'update' are incompatible.
                Type 'StoryContextUpdate<Args>' is not comparable to type 'StoryContextUpdate<FooProps>'.
                  Property 'foo' is missing in type 'Args' but required in type 'FooProps'.  TS2352

    10 |   return <div></div>;
    11 | }
  > 12 | export default {
       |                ^
    13 |   title: "Foo",
    14 |   component: Foo,
    15 |   decorators: apiDecorators,
```


Changing the interface's properties to be optional 

```
interface FooProps {
  foo?: string;
}
```

will fix the error.
Also removing 
`decorators: [mswDecorator],`
fixes the error.
Repository: godot
Issue: Editor viewport global_canvas_transform auto reset when mouse hover on viewport
Labels: bug,discussion,topic:editor,topic:plugin,topic:2d

### Godot version

3.4.2 stable[45eaa2daf] steam version

### System information

windows 10

### Issue description

When use set_global_canvas_transform() on editor viewport,  the editor viewport transform immediately
![EditorTransform tscn - EditorCanvasTransform - Godot Engine-2022-02-10 16_20_52](https://user-images.githubusercontent.com/9168814/153366420-c03fbc93-3154-4b46-a41c-2b79ba5a4b49.png)
But when any input(keyboard pressed, or mouse hovered on canvas editor), it will be reset as before. And the transform only change the item on canvas but not the hints( grids, axis..etc)


### Steps to reproduce

Add a tool script then call
get_tree().edited_scene_root.get_viewport().set_global_canvas_transform()

### Minimal reproduction project

[EditorCanvasTransform.zip](https://github.com/godotengine/godot/files/8039327/EditorCanvasTransform.zip)
Repository: vscode
Issue: Can Quickpick Separator be displayed when scrolling down? - aka sticky separators
Labels: feature-request,quick-pick

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

When I'm trying the new Quickpick Separator API, I find the Separator is missing when I scroll down the list.

Initial state:
![image](https://user-images.githubusercontent.com/45906942/153365869-c65fb12b-32c2-4b88-9179-b6ec7dd8f343.png)

When scroll down:
![Screenshot 2022-02-10 161841](https://user-images.githubusercontent.com/45906942/153366106-7ff81dfd-5bfa-42b6-b931-67e2b8c6d5f0.png)

It makes users confused when the quick pick list is long. It would be great if we could show the current separator info in the red square of the last screenshot. I'm not sure if it can be realized easily since it's a "separator" but we'd like to use it to help us group items.
Repository: neovim
Issue: `vim.highlight.range` doesn't result into latest added highlight
Labels: bug-regression,has:bisected,marks

### Neovim version (nvim -v)

NVIM v0.7.0-dev+1048-gdba1df635

### Vim (not Nvim) behaves the same?

No, Vim doesn't have Lua functions

### Operating system/version

Ubuntu 20.04

### Terminal name/version

kitty 0.23.1

### $TERM environment variable

xterm-kitty

### Installation

nvim.appimage

### How to reproduce the issue

1. `nvim --clean -u NONE`.
2. Type `abc`.
3. `:lua vim.highlight.range(0, 1, 'Comment', {0, 0}, {0, -1})` (whole line should be highlighted as comment)
4. `:lua vim.highlight.range(0, 1, 'Delimiter', {0, 0}, {0, -1})` (whole line should be highlighted as delimiter)
5. `:lua vim.highlight.range(0, 1, 'Comment', {0, 0}, {0, -1})`

### Expected behavior

Whole line again should be highlighted as comment.

### Actual behavior

Highlighting doesn't change.

Notes:
- If last highlighting is done with bigger priority ( `:lua vim.highlight.range(0, 1, 'Comment', {0, 0}, {0, -1}, 'v', false, 51)`), everything is as expected.
- Everything works as expected in 0.6.0.
Repository: PowerToys
Issue: PowerRenamer: Monitor folder for changes
Labels: Issue-Bug,Product-PowerRename

### Description of the new feature / enhancement

It would be good if the windows contents updated when the folder contents change.

For example the tool offers the option to not close after renaming but will not show any new or removed files in the folder.



### Scenario when this would be used?

Whenever dealing with generated data that changes the filenames but keep a pattern.

### Supporting information

_No response_
Repository: yt-dlp
Issue: brandnewtube.com extractor/downloader
Labels: site-request

### Checklist

- [X] I'm reporting a new site support request
- [X] I've verified that I'm running yt-dlp version **2022.02.04**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've checked that none of provided URLs [violate any copyrights](https://github.com/ytdl-org/youtube-dl#can-you-add-support-for-this-anime-video-site-or-site-which-shows-current-movies-for-free) or contain any [DRM](https://en.wikipedia.org/wiki/Digital_rights_management) to the best of my knowledge
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and am willing to share it if required

### Region

World

### Example URLs

Single video: https://brandnewtube.com/watch/it-039-s-time-to-be-terrified_SQO8773gPTABngN.html

# channel
Playlist: https://brandnewtube.com/@DrVernonColeman


### Description

Support for downloading single videos and channels on brandnewtube.com

### Verbose log

```shell
[debug] Command-line config: ['--dump-single-json', '--verbose', 'https://brandnewtube.com/@DrVernonColeman']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8 (No ANSI), err utf-8, pref UTF-8
[debug] yt-dlp version 2022.02.04 [c1653e9ef]
[debug] Python version 3.10.2 (CPython 64bit) - Linux-5.15.19-1-MANJARO-x86_64-with-glibc2.33
[debug] exe versions: ffmpeg 4.4.1 (setts), ffprobe 4.4.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
[debug] [generic] Extracting URL: https://brandnewtube.com/@DrVernonColeman
[generic] @DrVernonColeman: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] @DrVernonColeman: Downloading webpage
[generic] @DrVernonColeman: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://brandnewtube.com/@DrVernonColeman
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1381, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1451, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3.10/site-packages/yt_dlp/extractor/common.py", line 612, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.10/site-packages/yt_dlp/extractor/generic.py", line 3986, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://brandnewtube.com/@DrVernonColeman
```
Repository: vscode
Issue: Custom editor group contributions.configuration
Labels: feature-request,settings-editor

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Hi vscode 

We have multiple extensions as part of an extension pack, I would like to create some settings for these extensions, the main extension should create 1 entry in settings and then any dependencies would add there settings underneath it.

Current behaviour appears to be every extension has to have its own entry in preferences/settings/extensions

thanks
Repository: flutter
Issue: Add Offstage widget to bottomChild of AnimatedCrossFade and set offstage: true when !_isTransitioning
Labels: framework,f: material design,c: proposal,P3,team-design,triaged-design

Right now both widgets from the AnimatedCrossFade widget are being painted on the screen.
```dart
 AnimatedCrossFade(
          duration: const Duration(milliseconds: 200),
          crossFadeState: CrossFadeState.showFirst,
          firstChild: Container(key: const Key('firstChild')),
          secondChild: Container(key: const Key('secondChild')),
        ),
```

I would like that the bottom widget in the AnimatedCrossFade widget is offstage when it is not being transitioned and it is hidden.

The implementations will be very straight forward and would allow to consume less resources while using this widget with large subtrees. At the same time, it would improve testing as Finder by default would only find the visible widget when it is not transitioning 

## Implementation

It would be add a Offstage widget here: 

https://github.com/flutter/flutter/blob/db747aa1331bd95bc9b3874c842261ca2d302cd5/packages/flutter/lib/src/widgets/animated_cross_fade.dart#L342

```dart
bottomChild = TickerMode(
      key: bottomKey,
      enabled: _isTransitioning,
      child: Offstage(
       offstage: !_isTransitioning,
       child: IgnorePointer(
         child: ExcludeSemantics( // Always exclude the semantics of the widget that's fading out.
          child: ExcludeFocus(
            child: FadeTransition(
              opacity: bottomAnimation,
              child: bottomChild,
            ),
          ),
        ),
       ),
      ),
    );

```


## Use case

We could write test like this: 

```dart

      await tester.pumpWidget(
        AnimatedCrossFade(
          duration: const Duration(milliseconds: 200),
          crossFadeState: CrossFadeState.showFirst,
          firstChild: Container(key: const Key('firstChild')),
          secondChild: Container(key: const Key('secondChild')),
        ),
      );
      await tester.pumpAndSettle();

      expect(find.byKey(const Key('firstChild')), findsOneWidget);
      expect(find.byKey(const Key('secondChild')), findsNothing);

      await tester.pumpWidget(
        AnimatedCrossFade(
          duration: const Duration(milliseconds: 200),
          crossFadeState: CrossFadeState.showSecond,
          firstChild: Container(key: const Key('firstChild')),
          secondChild: Container(key: const Key('secondChild')),
        ),
      );
      await tester.pumpAndSettle();

      expect(find.byKey(const Key('firstChild')), findsNothing);
      expect(find.byKey(const Key('secondChild')), findsOneWidget);

```
Repository: vscode
Issue: Tangle `searchEditor` <=> `search`
Labels: debt,search,under-discussion,engineering

I wonder if we should simply move all of `searchEditor` into `search`?

![image](https://user-images.githubusercontent.com/900690/153411837-57b28a1f-bde1-4023-bec9-65c7290ad67b.png)
Repository: vscode
Issue: Tangle of 5 in text model languages
Labels: debt,editor-core,engineering

![image](https://user-images.githubusercontent.com/900690/153413434-e1b749a4-06c8-4bda-8cf9-dd9a0367b2c6.png)
Repository: godot
Issue: HTML5 GLES3 export crashes on macOS when 3D is being rendered
Labels: bug,platform:web,topic:rendering,topic:porting,confirmed,crash

### Godot version

3.4.2 stable

### System information

macOS 11.6, MacBook Pro 2017, processor: 2,3 GHz Dual-Core Intel Core i5, memory: 16 GB 2133 MHz LPDDR3, graphics: Intel Iris Plus Graphics 640 1536 MB, rendering backend: GLES3 (WebGl 2.0)

### Issue description

Exported HTML5 build using GLES3 crashes browser when 3D is being rendered. Runs fine using GLES2.
Computer:
Tested with: 
Firefox: 96.0.3
Chrome: 98.0.4758.80 (Official Build) (x86_64)
Safari Technology Preview: Release 139 (Safari 15.4, WebKit 16613.1.14.41.2)

### Steps to reproduce

Exported project is located in builds folder.
Running localhost and opening in browser should reproduce.

### Minimal reproduction project
[html_gles3_test.zip](https://github.com/godotengine/godot/files/8041786/html_gles3_test.zip)
Repository: kubernetes
Issue: [feature request] add --node-annotations command flag for kubelet
Labels: sig/node,kind/feature,needs-triage

### What would you like to be added?

Reopening #60832.

Add a `--node-annotations` command flag for kubelet, analogous to the existing `--node-labels` flag.

### Why is this needed?

We want to be able to report metadata about a node without being constrained by label limits, especially the 63 character limit.

Previously @liggitt raised concerns about this in relation to https://github.com/kubernetes/community/pull/911. However, annotations are not used for scheduling purposes, so this argument is not relevant.
Repository: godot
Issue: Jittering and Non Screen Tearing even when disabling V-Sync
Labels: bug,platform:windows,topic:porting,regression

### Godot version

Godot 4 Alpha 2

### System information

Windows 10 - GTX 980

### Issue description

After disabling V-Sync the screen tearing is gone, it should appear, also the game Start jittering and stuttering, and when enabling V-Sync the game still jittering/stuttering
In Alpha 1 after disabling V-Sync, the screen tearing will appear, but there is no Jitter, and the game runs very smooth no matter what compared to Alpha 2
All of this happen when in Full screen

**Edit : You can download this Advanced movement system template and test it, Before you test it add this line of code in _ready()**

`DisplayServer.window_set_mode(DisplayServer.WINDOW_MODE_FULLSCREEN)`

![Untitled](https://user-images.githubusercontent.com/51128638/153620098-6c575d3a-1057-47d1-8783-8569ae75fc6f.png)


**now open it in Alpha 1, You will see the game runs very smooth, but in Alpha 2 the game stuttering, press shift to run and rotate the camera around you and you will see**

### Steps to reproduce

in any 3D project that contain a fast moving camera, open it in Alpha 1 and Alpha 2, and see the difference

### Minimal reproduction project

None
_
Repository: terminal
Issue: Azure Cloud Shell Fails to connect when you have multiple tenants and 1 of them requires MFA
Labels: Help Wanted,Issue-Bug,Product-Terminal,Area-AzureShell,Priority-2

I have several Azure AD tenants attached to my account. 

When starting cloud shell, I can choose my tenant however, a terminating error appears when one of the other tenants needs MFA and exits instead of continuing to sign in to the chosen tenant. 

Steps to Reproduce:

Have an Azure AD account that is used in multiple tenants.

1. Start the Azure Cloud Shell Connector
2. Proceed with the device sign in
3. Choose the tenant that you wish sign in with

You will see an error for the other tenants about requiring MFA even though it is not the tenant you are trying to use. 

![image](https://user-images.githubusercontent.com/18618111/153442576-89c3bb28-1c60-46ed-b101-76333c4fbe3b.png)


The only workaround is to sign in to each tenant and then go back and sign in to the tenant you intended to in the first place.

When you do this through shell.azure.com you simply get a warning for each tenant that needs to be refreshed but you end up signed in to the correct tenant.
Repository: create-react-app
Issue: Errors emitted by `react-scripts build` don't include any trace after upgrading to `5.0.0`
Labels: needs triage

I'm not sure if this is a bug or intended so I've marked it as a question for now...

I am upgrading an application from `4.0.3` to `5.0.0`, one thing we noticed immediately however, is that build errors no longer include any kind of file trace with them, here's an example:

4.0.3:

```ts
/src/components/app.tsx
TypeScript error in /src/components/app.tsx(22,2):
'faPaperPlane' is declared but its value is never read.  TS6133

    20 | import { FontAwesomeIcon } from '@fortawesome/react-fontawesome';
    21 | import {
  > 22 | 	faPaperPlane,
       | 	^
    23 | 	faHandPointRight,
    24 | 	faLocationCircle,
    25 | 	faKey,
```


5.0.0

```ts
TS6133: 'faPaperPlane' is declared but its value is never read.
    20 | import { FontAwesomeIcon } from '@fortawesome/react-fontawesome';
    21 | import {
  > 22 | 	faPaperPlane,
       | 	^^^^^^^^^^^^
    23 | 	faHandPointRight,
    24 | 	faLocationCircle,
    25 | 	faKey,
```

The former is a lot more convenient to debug than the latter, and I'm not sure what about upgrading has caused the error to be less verbose, but is there something I'm missing, or a change I need to make since upgrading?
Repository: storybook
Issue: Passing multiple components as an array props will crash the app when docs tab is opened.
Labels: question / support,performance issue,addon: docs

**Describe the bug**
If I pass multiple components as an array prop it will crash the app when docs tab is opened. Basically the browser tab becomes unresponsive, and suggest a warning of unresponsiveness. This did not happen before on version 6.2.9.
Also the story inside canvas tab will crash the application if interacted with.

**To Reproduce**
Pass components as an array prop inside your story:

`<Button arrayProp={[<Component1 />, <Component2 />]} />`

**System**
Environment Info:

System:
OS: macOS 11.6
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Binaries:
Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
Browsers:
Chrome: 98.0.4758.80
Firefox: 96.0.3
Safari: 15.0
npmPackages:
@storybook/addon-a11y: 6.4.18 => 6.4.18
@storybook/addon-backgrounds: 6.4.18 => 6.4.18
@storybook/addon-viewport: 6.4.18 => 6.4.18
Repository: pytorch
Issue:  Add a unit test which uses an extension module + ordered importer 
Labels: oncall: package/deploy,imported

[Torch.package ](https://pytorch.org/docs/stable/package.html) is a handy tool to serialize and deserialize python code. It works as you expect a packager to but with the added benefit of also saving the actual code itself when desired. It was primarily designed with the intention of being the delivery mechanism for [torch::deploy](https://github.com/pytorch/pytorch/blob/master/docs/source/deploy.rst) which is a runtime for getting pytorch models to run on multiple threads in eager mode. There's a great whitepaper about `torch.package` and `torch::deploy` [here](https://arxiv.org/pdf/2104.00254.pdf).

Motivation: A common use case of torch.package is to package a module, tweak it a bit, and repackage it. Unfortunately, after tweaking, it can be confusing if something comes from a torch.package or the outside environment. In these cases we default to the outside environment through our OrderedImporter (`torch/package/importer.py`). (this case is tested in https://github.com/pytorch/pytorch/pull/72367). Extension modules have a bizarre behavior in which they don't have a __file__ attribute and are a package (an example would be collections). https://github.com/pytorch/pytorch/pull/72533 deals with this case. We want a create a unit test for this case.

1. In `test/package/test_repackage.py` create a unit test which repackages a C extension module (like collections). An example of repackaging can be found in `test_repackage_mocked_module` in `test/package/test_dependency_api.py` or the test in `test/package/test_repackage.py` Be sure that the OrderedImporter is invoked by setting an importer for the second PackageExporter, and that the C extension module is added to the second PackageExporter.
2. Make sure that reverting the changes in https://github.com/pytorch/pytorch/pull/72533 cause you're test to fail

To run tests in OSS just use python `{PyTorch dir}/test/package/test_repackage.py`.