sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: TS2786: 'StyledFirebaseAuth' cannot be used as a JSX component.
Labels: bug,compatibility with other tools

**Describe the bug**
I am working on a project that works fine on `yarn build` before I add storybook to the project. The `package.json` has following entries in `dependencies` section
```json
"dependencies": {
    "firebase": "9.7.0",
    "firebase-admin": "10.0.2",
    "next": "12.1.6",
    "next-firebase-auth": "1.0.0-canary.8",
    "pluralize": "8.0.0",
    "react": "17.0.2",
    "react-calendly": "4.0.0",
    "react-dom": "17.0.2",
    "react-firebaseui": "6.0.0",
    "react-loader-spinner": "5.1.4",
    "sanitize.css": "13.0.0",
    "sass": "1.51.0"
  },
```
Next, I run `npx sb init` which setup storybook in the project. I have tried this process twice with `Yes` and `No` as the answer to the following question

```
✔ Do you want to run the 'eslintPlugin' fix on your project? … no
```
 When I run `yarn build` after storybook is setup, I get the following error

```
yarn run v1.22.18
$ next build
Failed to compile.

./components/FirebaseAuth.tsx:39:10
Type error: 'StyledFirebaseAuth' cannot be used as a JSX component.
  Its instance type 'StyledFirebaseAuth' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'React.ReactNode' is not assignable to type 'import("/Users/hhimanshu/Downloads/tmp/webapp/node_modules/@types/react-syntax-highlighter/node_modules/@types/react/index").ReactNode'.
        Type '{}' is not assignable to type 'ReactNode'.

  37 |     <div>
  38 |       {renderAuth ? (
> 39 |         <StyledFirebaseAuth uiConfig={firebaseAuthConfig} firebaseAuth={getAuth()} />
     |          ^
  40 |       ) : null}
  41 |     </div>
  42 |   );
error Command failed with exit code 1.
``` 

I see the same compilation issue in Webstorm IDE
<img width="660" alt="image" src="https://user-images.githubusercontent.com/6589036/167904670-2179bc1a-66d4-4379-8ff8-f2ee38b26c6a.png">


**To Reproduce**
Please create a reproduction by running `npx sb@next repro` and following the instructions. Read our [documentation](https://storybook.js.org/docs/react/contribute/how-to-reproduce) to learn more about creating reproductions.
Paste your repository and deployed reproduction here. We prioritize issues with reproductions over those without.

**System**
```
Environment Info:

  System:
    OS: macOS 12.3.1
    CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 101.0.4951.64
    Safari: 15.4
  npmPackages:
    @storybook/addon-actions: ^6.4.22 => 6.4.22 
    @storybook/addon-essentials: ^6.4.22 => 6.4.22 
    @storybook/addon-interactions: ^6.4.22 => 6.4.22 
    @storybook/addon-links: ^6.4.22 => 6.4.22 
    @storybook/react: ^6.4.22 => 6.4.22 
    @storybook/testing-library: ^0.0.11 => 0.0.11 
```

**Additional context**
Add any other context about the problem here.
Repository: rust
Issue: Invalid unused_constant warning
Labels: A-diagnostics,T-compiler,C-bug,D-incorrect

The following test-case:

```rust
#[macro_export]
macro_rules! const_assert {
    ($x:expr $(,)?) => {
        #[allow(unknown_lints, eq_op)]
        const _: [(); 0 - !{ const ASSERT: bool = $x; ASSERT } as usize] = [];
    };
}

const THRESHOLD: usize = 42;
const_assert!(3 < THRESHOLD);

fn main() {
    
}
```

Triggers:

```
warning: constant is never used: `THRESHOLD`
 --> src/main.rs:9:1
  |
9 | const THRESHOLD: usize = 42;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default
```

But the constant is used, so what am I missing?

Playground link: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=7bc6ce4bf160c13306805ecbf855b9dc
Repository: react
Issue: react-devtools standalone app is missing inspector (selector tool)
Labels: Type: Feature Request,Component: Developer Tools

When running react-devtools as standalone app (not as chrome extension or in react-native), The app is missing the inspector/selector tool.

It is also missing the jump to code integration with vscode.
Repository: flutter
Issue: IO thread makes OpenGL ES calls with no EGL context due to SkiaUnrefQueue/GrDirectContext shutdown
Labels: platform-android,engine,P2,team-android,triaged-android

On a Moto G4 I'm sometimes seeing "call to OpenGL ES API with no current context" warnings in the log after pressing the back button in a Flutter app.

`Shell` destruction calls `platform_view->ReleaseResourceContext` on the IO thread, which clears the thread's EGL context in preparation for destroying the context.  However, with https://github.com/flutter/engine/pull/32106 the `SkiaUnrefQueue` destructor may now post a deferred task that deletes Skia objects and the `GrDirectContext`.  This task would still need the EGL context.

After decoding completes, the image decoder task on the `ConcurrentTaskRunner` posts a task to the IO thread to upload the image to a texture.  This task checks whether the `IOManager` is alive.  If it is, then the IO thread's `GrDirectContext` and EGL context are still available and it is safe to proceed.

The IO thread then needs to post a task to the UI thread to deliver the texture to Dart.  This is not synchronized with engine shutdown, and it means that the `SkiaUnrefQueue` may still be alive even after shutdown has deleted the engine and the `IOManager`.

The shell needs some way to defer clearing of the IO thread's EGL context until after the `GrDirectContext` has been deleted.

Some options:
* wrap the `GrDirectContext` in an object that also manages the EGL context and have the `SkiaUnrefQueue` hold a reference to the wrapper
* create a thread-local object on the IO thread whose destructor deletes the EGL context on thread shutdown
* have the `Shell` destructor queue a task to the UI thread and wait for it after deleting the `IOManager`.  Then queue a task to the IO thread that clears the thread's EGL context.  By the time the second task runs all strong references to the `SkiaUnrefQueue` held by either IO or UI thread tasks should be dropped, and it should be safe to release the EGL context.

@dnfield @chinmaygarde
Repository: godot
Issue: [3.x][GLES3] ReflectionProbe not working under a viewport node with "own world" set to be true
Labels: topic:rendering,documentation,topic:3d

### Godot version

3.5.beta1.mono and 3.5.beta5.mono

### System information

Windows 10 64-bit, GLES3, GTX1060 6GB

### Issue description

I am trying to use a separated viewport to display the 3D world to have better controls of 3D rendering resolution without messing the 2D resolution. However, ReflectionProbe node doesn't work when it is placed under a viewport node and the viewport's "own world" setting set to be true. I want to use "own world" because it appears to have better performance.
![reflection-probe-viewport-bug-own-world-off](https://user-images.githubusercontent.com/48320629/167917562-70ca05f8-2510-4515-889a-e9be30753782.png)
![reflection-probe-viewport-bug-own-world-on](https://user-images.githubusercontent.com/48320629/167917568-6b9d2665-c7fd-4c6f-8f32-2770926ca1d5.png)



### Steps to reproduce

1. Open the following minimal reproduction project.
2. Open "ReflectionProbeBug.tscn"
3. Toggle on and off the "own world" setting of the viewport node.
4. The reflection probe isn't working when the viewport's "own world" setting set to be true.

### Minimal reproduction project

[ReflectionProbeBug.zip](https://github.com/godotengine/godot/files/8672330/ReflectionProbeBug.zip)
Repository: vscode
Issue: indent guides highlight in HTML interrupted in script/style sections when "editor.guides.bracketPairs": true
Labels: under-discussion,editor-indent-guides,bracket-pair-guides

Steps to Reproduce:
![guides](https://user-images.githubusercontent.com/1822013/167918509-f56d421b-8043-476a-a922-d68dcc328db0.png)

Bracket pair colorization doesn't change anything. I commented out any other guide / bracket / whatever settings I had in my settings.json.

Also I noticed that even with bracket pair colors disabled the guides are still rainbowy. Is this normal? I would expect them being grey / whatever style the theme has defined for brackets or indent guides.

Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.67.0
- OS Version: W10 21H2 19044.1645
Repository: TypeScript
Issue: Incorrect error when using generic, class and conditional typing (#43237 still exists)
Labels: Bug,Rescheduled

# Bug Report

I reported bug #43237 about a year ago. The bug is closed as fixed but it still exists current version including nightly.

### 🕗 Version & Regression Information

The incorrect error is introduced in version 3.9 and exists in nightly.

### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=4.6.2&ssl=1&ssc=1&pln=9&pc=22#code/MYGwhgzhAECyCeAlApsA9gJwCbQN4ChojoAHDASwDcwAXZUgCgEo9DiBffT-USGBAMrIaAHgAqQmtGQAPOgDss-JKkxYAfK2414JegBFaYAWgCuGYMnEpg0uckXKba6AB880ANoBrZPABcEDQU8gDmALr+YPLw0OyaALzQYjZ2CkpwKujY0AD8mZLWqOquKaie4dD+yTYVANz4QA

https://www.typescriptlang.org/play?ts=4.6.2#code/MYGwhgzhAECyCeAlApsA9gJwCbQN4ChojoAHDNAF1SpxIAoBKPQ4gX33f1EhgQGVkFADwAVARWjIAHlQB2WXklSYsAPmacK8EsmgARMBTB80AVwzBkolMEkzk8xTZXQAPnmgBtANbJ4ALggKDABLWQBzAF1-MFl4aFZ1AF5oERs7OQU4JXRsaAB+bPFrVFVXNNRPSOh-VJsqgG58IA

### 💻 Code 1

```typescript
export interface IFieldDef
{
    [name: string]: any;
}

export class Record<TRec extends IFieldDef>
{
    private a():TRec|null {
        return null;
    }
    protected b():TRec|null {
        return null;
    }
    public c() {
        return this.a();
    }
    public d() {
        return this.b();
    }
} 

export class Set<TSet extends Record<IFieldDef>>
{
    public item(): TSet|null {
        return null;
    }
}

export type DS<TRec extends Record<IFieldDef> | { [key:string]:any }> = TRec extends Record<IFieldDef> ? Set<TRec> : TRec[];
```

### 💻 Code 2

```typescript
class MyRecord {
    private p() {
    }
}

class MySet<TSet extends MyRecord> {
}

type DataSource<TRec extends MyRecord | { [key:string]:any }> = TRec extends MyRecord ? MySet<TRec>|TRec[] : TRec[];
```

### 🙁 Actual behavior

Error is reported

### 🙂 Expected behavior

No error
Repository: godot
Issue: Internal script error! Opcode: 38 (please report). when casting Resource to custom Resource type
Labels: bug,topic:gdscript

### Godot version

 v3.4.4.stable.official.419e713a2

### System information

Window 10, GLES3, nVidia RTX

### Issue description

Casting variable of type Resource to custom Resource type throws error

### Steps to reproduce

Just run attached project

### Minimal reproduction project

[GodotCastResourceBug.zip](https://github.com/godotengine/godot/files/8672850/GodotCastResourceBug.zip)
Repository: excalidraw
Issue: Text editing focus is lost if switching to and back from another browser tab/window/application, which hurts `usability`
Labels: UX/UI

Text editing focus is lost if switching to and back from another browser tab/window/application, which hurts **usability**:

- start editing text and/or select some portion of text
- switch to another application to grab (copy) some additional text
- switch back to diagramm to paste the additional text

The editing focus is lost at that point, you need to do actions to select text to start editing again (for grouped elements that may take time).
Repository: TypeScript
Issue: Condition aliasing doesn't capture optional chain expressions
Labels: Bug,Help Wanted

# Bug Report


### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

undefined optional chain aliased condition narrowing

### 🕗 Version & Regression Information


- This is the behavior in every version I tried (from 4.4 onward, when we added aliased conditions).


### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgGIHt3IN4ChkHIDmEYAanADYCuEAzgBQCUAXMiNQLYBG0A2gF0A3LgC+uXABMICSnCgoE6EHTDIYmNhiwAfZNRDSYoCJJG4lKtQDcqdZAF51mAPwA6EuSq1GTc8BhkBltKOiYcfEJLVWQADy1MR2d0EUJkAHp0tOzsgD0XMQlomzsAJiSNLAAyKuSPUgoaemZ-QOCy8Lw04riErCdK1MJMnNHkfMLcAKDK909Gn2ZOyIIe+LREgcwhghGxvILRIA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
interface Foo {
    getValues(): number[];
}

declare const foo: Foo | undefined;

const vals = foo?.getValues();
if (vals) {
    foo; // Foo | undefined
}

const vals2 = foo && foo.getValues();
if (vals2) {
    foo; // Foo
}

if (foo?.getValues()) {
    foo; // Foo
}
```

### 🙁 Actual behavior

`foo` is potentially undefined in the first if block. The assignments fail.

(Added assignments so there's some feedback now that the playground's `//^?` doesn't work pre-4.6.)

### 🙂 Expected behavior

`foo` is narrowed to `Foo` in the first if block, matching the narrowing in the other if blocks.
Repository: flutter
Issue: Multiprovider leaves some room for optimization
Labels: framework,c: performance,c: proposal,customer: money (g3),P3,team-framework,triaged-framework

Internal: b/292548138

https://pub.dev/packages/provider#multiprovider allows defining a single widget that takes a list of inherited widgets. Behind the scenes this still creates N inherited elements, including all of the machinery and hashmap copying/allocation that requires.

While this is usuallly fine, in customer:money's app there are a significant number of providers. We should see if we can create an element type that could provide more than one type per Element. This would compress the element tree substantially, and reduce the amount of book keeping.

This could involve a change in either package:provider or in the framework. We may not expose the necessary mechanisms to just do this in provider.
Repository: flutter
Issue: [ios_platform_images] Deprecate/reimplement load method.
Labels: package,team-ecosystem,P2,c: tech-debt,p: ios_platform_images,triaged-ecosystem

The framework wants to deprecate the `ImageProvider.load` method. To allow that to land, this PR was created:

* https://github.com/flutter/plugins/pull/5701

**Fix the implementation of `_FutureMemoryImage extends ImageProvider`** ([code](https://github.com/flutter/plugins/blob/c13e8a50688b65b740a47adc1f6149ffcb9640eb/packages/ios_platform_images/lib/ios_platform_images.dart#L67)), so the `ios_platform_images` package complies with the new API.
Repository: pytorch
Issue: DISABLED test_DistributedDataParallel (__main__.TestDistBackendWithSpawn)
Labels: oncall: distributed,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](http://torch-ci.com/failure/test_DistributedDataParallel%2C%20TestDistBackendWithSpawn) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/6396724783).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 red and 4 green.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: material-ui
Issue: [TextField] Autofill font size changes on page interaction
Labels: support: question,component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When a text field is prefilled the font size changes when the user interacts with the page.

**Autofill on page load**
![image](https://user-images.githubusercontent.com/4462478/167974299-bcc57140-b549-4daf-9ede-024479529092.png)

**Autofill on page interaction**
![image](https://user-images.githubusercontent.com/4462478/167974848-c9e94284-3b6e-4515-8e2e-b59d979ea786.png)

**Gif**
![autofill](https://user-images.githubusercontent.com/4462478/167974699-53db719f-90fe-425a-9f1a-bdf56b1d0e85.gif)

### Expected behavior 🤔

The font size should be consistent so the user doesn't see a flicker of resizing when interacting with the page.

### Steps to reproduce 🕹

Steps:

1. Enable autofill on Chrome or Edge
2. Have save details like username / password
3. Load a page that prefills saved details

### Context 🔦

Consistent look and feel for a prefilled text field.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 16.13.2 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.1.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 101.0.4951.54
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.39)
  npmPackages:
    @emotion/react: ^11.8.2 => 11.8.2
    @emotion/styled: ^11.8.1 => 11.8.1
    @mui/base:  5.0.0-alpha.74
    @mui/icons-material: ^5.5.1 => 5.5.1
    @mui/material: ^5.5.3 => 5.5.3
    @mui/private-theming:  5.5.3
    @mui/styled-engine:  5.5.2
    @mui/system:  5.5.3
    @mui/types:  7.1.3
    @mui/utils:  5.6.1
    @mui/x-data-grid: ^5.10.0 => 5.10.0
    @mui/x-date-pickers: ^5.0.0-alpha.2 => 5.0.0-alpha.2
    @types/react: ^17.0.43 => 17.0.43
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    typescript: ^4.6.3 => 4.6.3
```
</details>
Repository: vscode
Issue: More visibility for Critical errors
Labels: error-list,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->

When opening a Java project, the Java language server imports the project and reports errors, that are visualized in the PROBLEMS view. Among those errors, one error should stand out more. In our case, the user is blocked until the version incompatibility issue is fixed. This is now shown as a warning and buried among other errors, so users could not easily notice it. Our solution is to use notification and ask users to take action.

Here to open the discussion on whether this is the right pattern to use when dealing with such a case. Our thoughts are:
1. One error can hardly stand out in the PROBLEMS view when there are many
2. Notification could be a bit intrusive and noisy to the users
3. Is there a solution sitting in the middle?

And here's a video to demonstrate the pattern we are using:

https://user-images.githubusercontent.com/16755094/167988073-1852b1d5-2d44-4a0c-98a4-7dc989757a53.mp4
Repository: TypeScript
Issue: RFC: @internal by default
Labels: Suggestion,Awaiting More Feedback

## ⭐ Suggestion

Today you can use `@internal` JSDoc tag and `stripeInternals` flag to erase private but exported APIs. It will be good to have a reversed option, that _all_ exports are `@internal` unless they explicitly opt-out.

### Option 1: `@public` JSDoc tag

If an export is commented with `@public` JSDoc tag, the declaration is emitted. Otherwise, treat it as `@internal`.

Example:

> `A/utils/index.ts`

```ts
/** @public */
export const a = 1
export const b = 2
```

With `stripeInternal: all`, it emits the following declaration file:

```ts
export const a: number
```

### Option 2: Entry files

Allowing to specify a set of entry files (or infer it from `exports` field of `package.json`).

If a type is not viable from one of the entry files, the type of it will not be emitted.

Example:

> `A/index.ts`

```ts
export { A, B } from './utils'
```

With `typeEntries: ["./index.ts"]`, only type referenced by `A` and `B` is emitted, all other declarations are treat as private.

## 🔍 Search Terms

internal by default declaration project reference

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


Add a new compiler option: `stripeInternal: "all"`, and use `@public` JSDoc to allow the emit of declarations.

## 📃 Motivating Example

It will improve the protection of internal APIs.
Repository: PowerToys
Issue: Implementation for Wox.Plugin.ISettingProvider.CreateSettingPanel in PT Run
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

I think it would be great to implement CreateSettingPanel for additional setting options other than the current boolean PluginAdditionalOption

### Scenario when this would be used?

This will add additional settings option for plugins such as ListBox, and allow greater flexibility for settings option. 

### Supporting information

_No response_
Repository: youtube-dl
Issue: Informit EduTV & TVNews database
Labels: site-support-request,account-needed

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [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
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://search.informit.org/doi/10.3316/edutv.581578


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Informit is most well known as an online academic database that provides access to over 100 databases, some of which provide full-text sources. The media database includes two products, EduTV (containing indexed coverage of education- and media-related TV programmes since 2006) and TVNews (covering news and current affairs and TV documentaries since 2007).

Informit is owned by RMIT Training, a subsidiary of RMIT University in Melbourne, Australia. Besides institutional access are available from any Australian universities' campus, the National Library, the State Library of Queensland and the State Library of South Australia also provides both on-site or at home access for their members.