sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: NonNullable FormControl is assignable to Nullable FormControl, leading to deceptive type safety
Labels: area: forms

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

Use case: a component with an input of type `FormControl<boolean | null>`. User is able to assign a `FormControl<boolean>`. Component can internally set null as value. User receives an unexpected value at runtime but no compiler error.

```
const nonNullable = new FormControl(false, {nonNullable: true});
const nullable: FormControl<boolean | null> = nonNullable;
nullable.setValue(null); // nonNullable control receives value null which it does not expect;
```

Per default typescript does not handle variance / restrict variance. TypeScript 4.7 introduced [variance annotations](https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#optional-variance-annotations-for-type-parameters). Marking TValue in FormControl as invariant solves the problem in my reproduction test. But I don't know all the effects this change would have applied in Angular.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-ntzwtb?file=src/app/app.component.ts

### Please provide the exception or error you saw

```true
The error is: no compile time error for assigning the nonNullable control.
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 14.2.2
Node: 18.13.0 (Unsupported)
Package Manager: npm 9.1.2
OS: win32 x64

Angular: 14.2.1
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, material, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1402.2
@angular-devkit/build-angular   14.2.2
@angular-devkit/core            14.2.2
@angular-devkit/schematics      14.2.2
@angular/cli                    14.2.2
@schematics/angular             14.2.2
ng-packagr                      14.2.1
rxjs                            7.5.6
typescript                      4.8.3
```


### Anything else?

_No response_
Repository: flutter
Issue: Update `didChangeLocales` documentation to mention that iOS will just terminate all applications when the locale changes
Labels: platform-ios,framework,d: api docs,P3,team-ios,triaged-ios

I implemented didChangeLocales with this tutorial:

https://dev.to/pedromassango/onresume-and-onpause-for-widgets-on-flutter-27k2

```
  @override
  void didChangeLocales(List<Locale> locale) {
    print("didChangeLocales: " + locale.toString());

    setNewLanguage();

    super.didChangeLocales(locale);
  }
```


If I run the app in debug mode and change the language through app settings the app will crash:

```
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGKILL
    frame #0: 0x00000001cd6b4aa8 libsystem_kernel.dylib`mach_msg2_trap + 8
libsystem_kernel.dylib`mach_msg2_trap:
->  0x1cd6b4aa8 <+8>: ret    
libsystem_kernel.dylib`macx_swapon:
    0x1cd6b4aac <+0>: mov    x16, #-0x30
    0x1cd6b4ab0 <+4>: svc    #0x80
    0x1cd6b4ab4 <+8>: ret    
Target 0: (Runner) stopped.
```

didChangeAppLifecycleState is working perfectly but not didChangeLocales.
Whats the right way to test didChangeLocales and how should it work? Is it necessary to restart the app for working or is it working "on the fly"?

Thanks


flutter doctor:

```
[✓] Flutter (Channel stable, 3.3.10, on macOS 12.6 21G115 darwin-arm, locale
    de-DE)
    • Flutter version 3.3.10 on channel stable at
      /Users/xxx/development/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (4 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0
```
Repository: kubernetes
Issue: Valid Semver 2.0 not compatible with kubernetes labels
Labels: priority/awaiting-more-evidence,kind/feature,sig/architecture,lifecycle/rotten,needs-triage

### What happened?

[Semver](https://semver.org/#backusnaur-form-grammar-for-valid-semver-versions) is allowed to have the following syntax: `1.2.3+45`, where `45` is the build number. We are using this versioning approach, and when we tried to put that into the  `app.kubernetes.io/version` label we got the following error:

```text
a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')
```

I think this is a slight oversight and I think the regex there should be extended to:
```regex
(([A-Za-z0-9][-A-Za-z0-9_+.]*)?[A-Za-z0-9])?
                         ^ plus sign added here
```

From what I understand adding support for a `+` character doesn't have any additional implications and should be safe.

### What did you expect to happen?

I expected that a valid Semver is accepted as a label value.

### How can we reproduce it (as minimally and precisely as possible)?

Add the following K8s label to any object:

```
metadata:
  labels:
    app.kubernetes.io/version: 1.2.3+45
```

**Example:**

```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: test
  labels:
    app.kubernetes.io/version: 1.2.3+45
```

### Kubernetes version
<details>

```console
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-09T16:23:44Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.8-eks-ffeb93d", GitCommit:"abb98ec0631dfe573ec5eae40dc48fd8f2017424", GitTreeState:"clean", BuildDate:"2022-11-29T18:45:03Z", GoVersion:"go1.18.8", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider
<details>

```
AWS EKS
```

</details>

### OS version
<details>

```console
Bottlerocket OS 1.11.1 (aws-k8s-1.24)
```

</details>
Repository: PowerToys
Issue: Move notice.md check to a GitHub Action
Labels: Area-GitHub workflow

I don't know if this would be easy to migrate, but I don't think this should block the pipeline. IMO it should be another check (via GitHu actions for example.)

Spell checking and CLA are also not blocking the pipeline, just because they fail.

_Originally posted by @Aaron-Junker in https://github.com/microsoft/PowerToys/pull/23000#issuecomment-1368081084_
Repository: neovim
Issue:  vim.lsp.buf.format() invalidates changes list
Labels: status:blocked-external,lsp

### Describe the bug

I noticed that with some language servers (e.g. sumneko_lua) after calling `vim.lsp.buf.format()` entries in `:changes` are marked as invalid (`-invalid-`). This only seems to happen for lsp's sending the whole formatted document as response instead of actual text edits.

### Steps to reproduce

1. open new lua file with attached lsp "sumneko_lua"
2.  insert two lines: 
<pre>print("1")
print("2")
</pre>
3. `:lua vim.lsp.buf.format()`
4. open changes list with `:changes`

### Expected behavior

calling `:changes` should result in 

<pre>
change line  col text
    2     1    9 print("1")
    1     2    7 print("2")
>
</pre>

but instead shows

<pre>
change line  col text
    3     1    9 print("1")
    2     1    0 print("1")
    1     3    0 -invalid-
>
</pre>

### Neovim version (nvim -v)

v0.9.0-dev-581+gcb9d68fe6

### Vim (not Nvim) behaves the same?

na

### Operating system/version

5.15.0-10056-tuxedo

### Terminal name/version

konsole 21.12.3

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: vscode
Issue: the path of the terminal is incorrect
Labels: bug,confirmation-pending,terminal-process

Type: <b>Bug</b>

Open the project in the soft link and close it. When you reopen vscode, the last opened project and terminal will be loaded automatically, but the path of the terminal is incorrect, and the path is correct after creating a new terminal

VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:57:40.428Z)
OS version: Linux x64 5.15.0-57-generic
Modes:
Sandboxed: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz (4 x 2300)|
|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, 1|
|Memory (System)|11.55GB (6.59GB free)|
|Process Argv|--unity-launch /media/yutian/data/git/linux --crash-reporter-id d4d359f7-c0be-4318-be23-f62ac1c523db|
|Screen Reader|yes|
|VM|0%|
|DESKTOP_SESSION|ubuntu|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu|
|XDG_SESSION_TYPE|x11|
</details><details><summary>Extensions (24)</summary>

Extension|Author (truncated)|Version
---|---|---
include-autocomplete|ajs|0.0.4
vscode-office|cwe|2.9.5
CppSnippets|har|0.0.15
svn-scm|joh|2.15.7
vscode-language-pack-zh-hans|MS-|1.74.12140931
vscode-dotnet-runtime|ms-|1.6.0
isort|ms-|2022.8.0
python|ms-|2022.20.2
vscode-pylance|ms-|2023.1.20
jupyter|ms-|2022.11.1003412109
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.12
vscode-jupyter-cell-tags|ms-|0.1.6
vscode-jupyter-slideshow|ms-|0.1.5
remote-ssh|ms-|0.94.0
remote-ssh-edit|ms-|0.84.0
remote-wsl|ms-|0.72.0
cpptools|ms-|1.13.9
remote-explorer|ms-|0.0.3
azurerm-vscode-tools|msa|0.15.8
korofileheader|OBK|4.9.2
devicetree|plo|0.1.1
vscode-xml|red|0.23.0
tabnine-vscode|Tab|3.6.35


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vsccc:30610678
pyindex848cf:30577861
nodejswelcome1cf:30587006
282f8724:30602487
f6dab269:30613381
fim-prod:30623723

```

</details>

<!-- generated by issue reporter -->
Repository: next.js
Issue: next run build hangs indefinitely with react-rainbow-components
Labels: bug,SWC

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:20 PDT 2021; root:xnu-7195.141.6~3/RELEASE_ARM64_T8101
    Binaries:
      Node: 16.13.2
      npm: 8.1.2
      Yarn: 1.22.18
      pnpm: 6.35.1
    Relevant packages:
      next: 13.1.2
      eslint-config-next: 12.3.4
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

SWC transpilation

### Link to the code that reproduces this issue

private repository

### To Reproduce

create a new project with NextJS v13, install a npm module called react-rainbow-components, and build the project.

this issue was already in NextJS v12, someone had open an issue but unfortunately, the issue was closed without being resolved : https://github.com/vercel/next.js/issues/37573

### Describe the Bug

The build get stuck and the only way to exit thes tuck process is to kill it with its PID.

### Expected Behavior

the build should terminate without being stuck forever.

### Which browser are you using? (if relevant)

not relevant

### How are you deploying your application? (if relevant)

not relevant
Repository: go
Issue: x/tools/gopls: TestReinitializeRepeatedly failure
Labels: NeedsInvestigation,gopls,Tools

```
#!watchflakes
post <- pkg ~ `^golang\.org/x/tools` && test == "TestReinitializeRepeatedly"
```

Just saw this on a TryBot pass: the new TestReinitializeRepeatedly failed:
https://storage.googleapis.com/go-build-log/245e95df/linux-arm-aws_a852f0ae.log

Given that this test asserts on correct re-evaluation of views, this should be investigated before the next release.
Repository: godot
Issue: [4.0.beta] Bug when trying to close more than two unsaved scripts with "Close All" or "Close Other Tabs" functions
Labels: bug,topic:editor

### Godot version

v4.0.beta.custom_build [3c9bf4bc2]

### System information

Ubuntu 22.04.01

### Issue description

When trying to close more than two unsaved scripts with "Close All" or "Close Other Tabs" functions, debugger print:

`ERROR: Signal 'visibility_changed' is already connected to given callable 'ScriptEditor::_queue_close_tabs' in that object.
   at: connect (core/object/object.cpp:1270)`

and appear the save confirm dialog for two scripts, but other scripts are ignored.

https://user-images.githubusercontent.com/96838551/212343253-352becfc-066d-402e-bfe1-8f94f72ffd97.mp4


https://user-images.githubusercontent.com/96838551/212343296-d43f6255-f7c1-48e4-96b6-c6847dfca79b.mp4



### Steps to reproduce

1. Open more than two scripts in the eternal script editor.
2. Edit all scripts.
3. Try use "Close All" or "Close Other Tabs" function.
4. Click any button in the save confirm dialog.

### Minimal reproduction project

N/A
Repository: next.js
Issue: API endpoint throws error if `next/headers` is imported
Labels: bug,stale

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```
$ npx next info

    Operating System:
      Platform: linux
      Arch: x64
      Version: #104~18.04.2-Ubuntu SMP Tue Nov 29 12:13:35 UTC 2022
    Binaries:
      Node: 16.19.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.1.2-canary.8
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```

### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://github.com/hugo-vrijswijk/vercel-next-js-xez8ow

### To Reproduce

Start the repo and navigate to /api/example

![image](https://user-images.githubusercontent.com/10114577/212350122-4b8bc230-b529-4a37-a6ed-a5aef3e664a4.png)


### Describe the Bug

I have some code that uses headers that I want to use *both* in server components and in an api endpoint. To do so, I optionally pass `req` to the function, which calls `req.headers['my-header']`, or calls `headers()` from `next/navigation`. Even if my endpoint _always_ passes `req` and the `headers()` call is never done, the import still gives the error above. 

```ts
import { NextApiRequest } from 'next';
import { headers } from 'next/headers';

export function getHostHeader(req?: NextApiRequest) {
  if (req) {
    return req.headers.host;
  } else {
    return headers().get('host');
  }
}
```

If I disable `appDir` (and remove the app/page.tsx) the error is not thrown, even with the import still there.

Using a dynamic import (`(await import('next/navigation')).headers()`) is a workaround, but makes the function async which I would prefer not to do

### Expected Behavior

Client-only checking should either work differently for API endpoints or be done lazily instead of on import so that code that _exists close to it_ doesn't give an error without ever calling it.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: transformers
Issue: Add support for BLIP and GIT in image-to-text and VQA pipelines
Labels: Good First Issue

### Feature request

BLIP and GIT are 2 recent additions in the library, providing state-of-the-art performance for tasks like image captioning and visual question answering (VQA). GIT is even capable of video captioning and video QA.

Hence it makes sense to support them in our image-to-text and VQA pipelines.

### Motivation

Having support for better models in pipelines is very desired!

See also a request for it here: https://discuss.huggingface.co/t/support-for-different-models-in-text-to-image-pipeline/29504

### Your contribution

I can assist in adding support, see #18446 as a very similar case
Repository: material-ui
Issue: `TypographyVariants` type augmentation not always working
Labels: docs

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

_No response_

### Current behavior 😯

Currently https://mui.com/material-ui/customization/typography/#adding-amp-disabling-variants instructs you to add the following type augmentations:

```ts
declare module '@mui/material/styles' {
  interface TypographyVariants {
    poster: React.CSSProperties;
  }

  // allow configuration using `createTheme`
  interface TypographyVariantsOptions {
    poster?: React.CSSProperties;
  }
}

// Update the Typography's variant prop options
declare module '@mui/material/Typography' {
  interface TypographyPropsVariantOverrides {
    poster: true;
    h3: false;
  }
}
```

But in some cases accessing `theme.typography.poster` will still result in a type error:

```
    packages/theme/src/componentsOverrides/MuiCssBaseline.ts:8:21 - error TS2339: Property 'poster' does not exist on type 'Typography'.
    8     pre: typography.poster,
                          ~~~~~~
```

### Expected behavior 🤔

Accessing `theme.typography.poster` will never result in a type error.

In our project, I have only found one solution: augmenting `Typography` directly, instead of `TypographyVariants` (alias of `Typography`):

```ts
declare module "@mui/material/styles/createTypography" {
  interface Typography {
    poster: TypographyStyle;
  }
}
```

### Context 🔦

_No response_

### Your environment 🌎

_No response_
Repository: rust
Issue: incr-comp: Unstable fingerprints in mir_built
Labels: I-ICE,T-compiler,A-incr-comp,C-bug

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.

http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/

-->

### Code
https://github.com/KisaragiEffective/kisaragi-booth-utility/tree/65e168c40b0f70415f3cd16f31f7560b085b9925 (sorry, not minimized)

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.67.0-nightly (215e3cd21 2022-11-03)
binary: rustc
commit-hash: 215e3cd218b83b8a3152d84d92f17109253c25e1
commit-date: 2022-11-03
host: x86_64-unknown-linux-gnu
release: 1.67.0-nightly
LLVM version: 15.0.4
```

### Error output

due to length limit, I pasted on [gist](https://gist.github.com/KisaragiEffective/f9cf1515e04a4b2581c8f4ccd10b9165)

relevant: #84970
Repository: rust
Issue: Should enable static_position_independent_executables for i686
Labels: C-enhancement,O-x86_32

I am wonder that why it only enable static_position_independent_executables for x86_64 but no enable in i686, although i686 don't support pic instruction, but can implement it by call and get return addr(in fact, gcc use it to implement pic in i686), so I think we can think i686 support pic, so we should enable static_position_independent_executables for it ?

I just want to build a i686 musl static pie executeable file(Rust can build a x86_64 musl static pie executeable), but i found it link the crtbegin but not crtbeginS, and I finally found that static_position_independent_executables is false in i686 target.
Repository: PowerToys
Issue: Show loading times of plugins in PowerToys Run
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin,Run-Plugin Manager

### Description of the new feature / enhancement

Show loading time and query time in each plugins' dropdown

### Scenario when this would be used?

For knowing which plugin takes up a lot of processing time

### Supporting information

[plugins seems to be able to seize up PT Run on activation](https://github.com/microsoft/PowerToys/issues/17044#issuecomment-1069204690), it would be nice to know right in the settings

[Wox](https://github.com/microsoft/PowerToys/issues/17044#issuecomment-1069204690) has this in their plugin settings
Repository: storybook
Issue: [Bug]: React Library with Tailwind - Storybook does not reflect changes on save
Labels: bug,compatibility with other tools,tailwind

### Describe the bug

We are currently working on building a publishable component library within a new integrated Nx monorepo. The library is built in React with Tailwind.

We are currently experiencing an issue that occurs after editing classes on a component. After saving the changes, the Storybook webpack build completes and refreshes in the browser, but the changes are not displayed. The changes are only displayed on Chromium-based browsers after manually refreshing the page. On Firefox dev edition, the changes are not displayed after refresh. If the classes weren't in use when Storybook was started, they aren't applied after the refresh.

**Example**  
![The user add classes text-blue-700 font-bold to the component markup, saves the changes, and clicks over to storybook. The build finishes and the changes are not displayed on the refresh. After refreshing the changes are visible. The user repeats this process with another class to show how the original classes are stripped away if the new classes haven't been used yet.](https://user-images.githubusercontent.com/75320861/211816531-ef7db61c-5864-4fd0-b081-f6fb428997b4.gif)


### To Reproduce

```shell
Github Repo - https://github.com/brenden-ef/tailwind-storybook-repro

After running `npm ci` to install dependencies:

1. start storybook `nx storybook repro` and open it in a browser
2. in `packages/repro/src/lib/repro.tsx` add `p-8` class to the root `div` and  change the `h1` classes to `text-red-500 text-8xl font-bold`. Save the file after making these changes
3. note that none of the styles are applied after webpack finishes building the preview
4. refresh the page manually
5. note that now the styles are applied

Reproduced in Firefox Developer Edition (v109.0b9 ), Chrome (v109.0.5414.87), and Sizzy (v70.6) on MacOS and Windows.
```


### System

```shell
Environment Info:

  System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 16.14.0 - ~/.volta/tools/image/node/16.14.0/bin/node
    Yarn: 1.22.18 - ~/.volta/tools/image/yarn/1.22.18/bin/yarn
    npm: 8.5.5 - ~/.volta/tools/image/npm/8.5.5/bin/npm
  Browsers:
    Chrome: 109.0.5414.87
    Firefox: 108.0.2
    Safari: 16.2
  npmPackages:
    @storybook/addon-essentials: ^6.5.15 => 6.5.15 
    @storybook/builder-webpack5: ^6.5.15 => 6.5.15 
    @storybook/core-server: ^6.5.15 => 6.5.15 
    @storybook/manager-webpack5: ^6.5.15 => 6.5.15 
    @storybook/react: ^6.5.15 => 6.5.15
```


### Additional context

[This issue was originally filed on the Nx repo](https://github.com/nrwl/nx/issues/14271), but @mandarini requested to check here first as it sounds like it could be an issue with the Storybook server.