sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Zones size is in scaled pixels❌ (scaled by % set in Windows>Settings>Display>Scale&Layout ) while screen size is in absolute pixels✅
Labels: Issue-Bug,FancyZones-Editor,Area-User Interface,Priority-2

### Microsoft PowerToys version

0.62.1

### Running as admin

- [X] Yes

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

First go to Windows > Settings > System > Display > Scale and layout > 175%
Then go to FancyZones Editor > Edit zones
![image](https://user-images.githubusercontent.com/64386272/191534713-9c82fe6a-a012-4881-821d-e71a1940bb9f.png)
![image](https://user-images.githubusercontent.com/64386272/191535070-43b24c7c-25c1-4247-9d5f-e8c55066431e.png)
![image](https://user-images.githubusercontent.com/64386272/191535665-499fe987-2472-49a0-82c2-43aaefe7cbf9.png)


### ✔️ Expected Behavior

Zone size has to be displayed as absolute in pixels, to match with screen resolution **(and not calculated with the scale % applied in Windows settings)**

For example, if you open OBS, you can define a recording area in absolute pixels, not in pixels relative to the scale parameter.

Otherwise, FancyZone Editor should display both size, absolute and scaled if some users still need this last one.

### ❌ Actual Behavior

**Zones size in pixels mismatches with screen size in pixels** (sum of widths is lower than screen width)

The problem is:
- screen resolution is indicated as absolute.
- zone resolution is calculated with the scale % applied in Windows settings (175% in my screenshots)

### Other Software

_No response_
Repository: godot
Issue: get_script_method_list is missing defaults in some cases
Labels: bug,discussion,topic:core,topic:gdscript

### Godot version

4.0.alpha17

### System information

macOS 10.15.7

### Issue description

Some default values do not appear in the script method metadata `default_args`.  When they are missing, there is no way to know which parameters have defaults.  For example, the defaults listed in the metadata for
```
func mixed_example(p1, p2 = {}, p3 = "a", p4 = 1, p5 = []):
	pass
```
Contains two entries
```
"default_args": ["a", 1 ],
```
From this information, you cannot determine how many parameters have been defaulted and which get the default values that are provided.

In order to reliably find defaulted parameters and associate values with them, you need to know 
* the total number of defaulted parameters
* the indexes of the parameters that appear in `default_args`

Something like this would work
```
"default_arg_count": 4,
"default_arg_indexes":[2, 3],
"default_args": ["a", 1 ],
```
or
```
"default_args":{
  "count":4,
  "value_indexes":[2, 3],
  "values":["a",1],
}
```

For my purposes, simply knowing how many parameters are defaulted is extremely useful.  I use this information to generate doubles of objects in the GUT testing framework addon.

### Steps to reproduce

Given this script at `res://demo_missing_defaults.gd`
```
extends SceneTree


func mixed_example(p1, p2 = {}, p3 = "a", p4 = 1, p5 = []):
	pass


func _init():
	var script = load('res://demo_missing_defaults.gd')
	var methods  = script.get_script_method_list()
	for m in methods:
		print('-- ', m.name, ' (', m.default_args.size(), ')')
		print(JSON.stringify(m, '  '))

	quit()
```
You get the following output:
```
-- mixed_example (2)
{
  "args": [
    {
      "class_name": "",
      "hint": 0,
      "hint_string": "",
      "name": "p1",
      "type": 0,
      "usage": 262150
    },
    {
      "class_name": "",
      "hint": 0,
      "hint_string": "",
      "name": "p2",
      "type": 0,
      "usage": 262150
    },
    {
      "class_name": "",
      "hint": 0,
      "hint_string": "",
      "name": "p3",
      "type": 0,
      "usage": 262150
    },
    {
      "class_name": "",
      "hint": 0,
      "hint_string": "",
      "name": "p4",
      "type": 0,
      "usage": 262150
    },
    {
      "class_name": "",
      "hint": 0,
      "hint_string": "",
      "name": "p5",
      "type": 0,
      "usage": 262150
    }
  ],
  "default_args": [
    "a",
    1
  ],
  "flags": 1,
  "id": 0,
  "name": "mixed_example",
  "return": {
    "class_name": "",
    "hint": 0,
    "hint_string": "",
    "name": "",
    "type": 0,
    "usage": 6
  }
}
-- _init (0)
{
  "args": [

  ],
  "default_args": [

  ],
  "flags": 1,
  "id": 0,
  "name": "_init",
  "return": {
    "class_name": "",
    "hint": 0,
    "hint_string": "",
    "name": "",
    "type": 0,
    "usage": 6
  }
}
```

### Minimal reproduction project

See Steps to reproduce.
Repository: next.js
Issue: operation not permitted
Labels: bug,Output (export/standalone)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.3.2-canary.0
      eslint-config-next: 12.3.1
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

When I run the build I have this error

```
> Build error occurred
[Error: EPERM: operation not permitted, scandir 'C:\Users\axell\Documents\Development\pikas-template\apps\app\.next\standalone\apps\app\node_modules\next'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'scandir',
  path: 'C:\\Users\\axell\\Documents\\Development\\pikas-template\\apps\\app\\.next\\standalone\\apps\\app\\node_modules\\next'
}
```

And in my next.config.js I have this

```js
require('dotenv-flow').config({ path: '../..' });

const withPWA = require('next-pwa');
const withPlugins = require('next-compose-plugins');
const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true',
});
const { join } = require('path');
const withTM = require('next-transpile-modules')([]);

const plugins = [withTM, withBundleAnalyzer, withPWA];

/**
 * @type {import('next').NextConfig}
 */
const nextConfig = {
  swcMinify: true,
  reactStrictMode: true,
  output: 'standalone',
  experimental: {
    outputFileTracingRoot: join(__dirname, '../../'),
  },
  i18n: {
    locales: ['en', 'fr'],
    defaultLocale: 'en',
  },
  pwa: {
    disable: process.env.NODE_ENV === 'development',
    dest: 'public',
  },
};

module.exports = withPlugins(plugins, nextConfig);
```

I found these issues that talk about it too:
#36645
#1537


### Expected Behavior

I just want to build my app

### Link to reproduction

https://github.com/Achaak/pikas-template

### To Reproduce

Use this command

```
pnpm i

pnpm generate

pnpm build:packages

cd apps/app

pnpm build  <-- The bug appears here
```
Repository: go
Issue: x/vulndb: worker should add comment to issue and re-open when a new alias is found
Labels: vulncheck or vulndb
Repository: TypeScript
Issue: Make private field name parsing ecma 262 compliant
Labels: Bug,Help Wanted,Effort: Moderate,Rescheduled

[This](https://github.com/tc39/test262/blob/6f8e0f67cad29a92a23ed7b596a9be8d7ba34644/test/language/expressions/class/elements/after-same-line-static-async-method-rs-privatename-identifier-alt.js) file has parse errors, but probably shouldn't.

Considerations: 
 - https://github.com/microsoft/TypeScript/pull/50856 added support for starting with a unicode escape
 - The names `#ZW__NJ` and `#ZW__J` contain `\u200c` and `\u200d`, respectively (not here, but in the file)
 - Support for _extended_ unicode escapes (i.e. `\u{6F}`, rather than `\u006F`) depends on ES2015, but we appear to parse the file as ES5.
 - Converting the extended unicode escapes to regular unicode escapes does not seem to eliminate the errors

Discovered as part of https://github.com/microsoft/TypeScript/issues/50835
Repository: flutter
Issue: Checkbox is taking its fill color from primary swatch, instead of colorScheme.primary
Labels: framework,f: material design,has reproducible steps,found in release: 3.3,team-design,triaged-design

In the docs, it says that primary swatch will be deprecated and that we should use ColorScheme to define colors. However, if we don't provide primary swatch in themeData, the checkbox widget paints itself blue when checked (which is the default primarySwatch color), and ignores the colorScheme.

DartPad  example:
```
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

ColorScheme light = ColorScheme(
      brightness: Brightness.light,
      primary: Colors.orange,
      onPrimary: Colors.white,
      secondary: Colors.black,
      onSecondary: Colors.white,
      error: Colors.red,
      onError: Colors.white,
      background: Colors.grey,
      onBackground: Colors.black,
      surface: Colors.white,
      onSurface: Colors.black);

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(colorScheme: light),
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: const Center(
          child: MyStatefulWidget(),
        ),
      ),
    );
  }
}

class MyStatefulWidget extends StatefulWidget {
  const MyStatefulWidget({super.key});

  @override
  State<MyStatefulWidget> createState() => _MyStatefulWidgetState();
}

class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  bool isChecked = false;

  @override
  Widget build(BuildContext context) {

    return Checkbox(
      checkColor: Colors.white,
      value: isChecked,
      onChanged: (bool? value) {
        setState(() {
          isChecked = value!;
        });
      },
    );
  }
}

```

**Expected result when checkbox is checked**: it paints itself orange (as defined in the color scheme)
**What actually happens**: It paints itself blue (which is the default primary swatch)
Repository: node
Issue: `esm_loader` should use a primordial to get `cwd`
Labels: loaders

### Version

v18.9.0

### Platform

`Linux vhost1 5.18.10-76051810-generic #202207071639~1657252310~22.04~7d5e891 SMP PREEMPT_DYNAMIC Fri J x86_64 x86_64 x86_64 GNU/Linux`

### Subsystem

esm_loader

### What steps will reproduce the bug?

```js
process.cwd = () => {
    (async () => {
        await import('.');
    })();
};

await import('.');
```

### How often does it reproduce? Is there a required condition?

Always.

### What is the expected behavior?

No `RangeError`s.

### What do you see instead?

```
Exception in PromiseRejectCallback:
node:internal/modules/esm/resolve:1110
  };

RangeError: Maximum call stack size exceeded
Exception in PromiseRejectCallback:
node:internal/modules/esm/loader:163
      const output = await hook(arg0, meta.context, nextNextHook);
```

### Additional information

_No response_
Repository: pytorch
Issue: Feature Request: Deterministic Algorithm for MaxPool3d
Labels: feature,module: nn,good first issue,triaged,module: determinism,module: pooling

### 🚀 The feature, motivation and pitch

I am working on an encoder that involves use of [torch.nn.MaxPool3d](https://pytorch.org/docs/stable/generated/torch.nn.MaxPool3d.html#torch.nn.MaxPool3d)
I was wondering if there can be a deterministic version for the same

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @kurtamohler @kshitij12345 @saketh-are
Repository: stable-diffusion-webui
Issue: [Feature Request] in single column mode (mobile UI) float the progress bar in fixed position to reduce scrolling to check progress
Labels: enhancement

when I'm using the gui on mobile, I must scroll to the bottom and back up if I want to check the rendering process, this is a simple addition that would slightly improve quality of life
Repository: go
Issue: misc/cgo/test: TestSetgidStress failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "misc/cgo/test" && test == "TestSetgidStress"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/fdf5beddd880fd3753510461debd0ef826ac43de)):

    SIGQUIT: quit
    PC=0x472f41 m=0 sigcode=0
    
    rax    0xca
    rbx    0x0
    rcx    0x472f43
    rdx    0x0
    rdi    0x6f9528
    rsi    0x80
    rbp    0x7ffdb4ddd6a0
    ...
    	/workdir/go/src/runtime/proc.go:363 +0xd6 fp=0xc000054e60 sp=0xc000054e40 pc=0x440a76
    runtime.chanrecv(0xc0000ce000, 0x0, 0x1)
    	/workdir/go/src/runtime/chan.go:583 +0x49b fp=0xc000054ef0 sp=0xc000054e60 pc=0x40de7b
    runtime.chanrecv1(0x6a6b08?, 0x3e8?)
    	/workdir/go/src/runtime/chan.go:442 +0x18 fp=0xc000054f18 sp=0xc000054ef0 pc=0x40d9b8
    misc/cgo/test.testSetgidStress(0x486337?)
    	/workdir/go/misc/cgo/test/setgid2_linux.go:36 +0xd7 fp=0xc000054f58 sp=0xc000054f18 pc=0x5613d7
    misc/cgo/test.TestSetgidStress(0x0?)
    	/workdir/go/misc/cgo/test/cgo_linux_test.go:23 +0x19 fp=0xc000054f70 sp=0xc000054f58 pc=0x526619
    testing.tRunner(0xc000093040, 0x5b8510)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: build: unrecognized failures on openbsd-arm-jsing
Labels: NeedsInvestigation

```
#!watchflakes
post <- builder == "openbsd-arm-jsing" && pkg == "" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/d882e5dd9db880f40e94f8d63e60504e2fd9717a)):

    /home/gopher/build/go/src/make.bash: line 201: 55958 Segmentation fault      (core dumped) GOROOT="$GOROOT_BOOTSTRAP" GOOS="" GOARCH="" GO111MODULE=off GOEXPERIMENT="" GOENV=off GOFLAGS="" "$GOROOT_BOOTSTRAP/bin/go" build -o cmd/dist/dist ./cmd/dist
    
    build failed: make script failed: exit status 139


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: build: unrecognized failures on openbsd-arm64-jsing
Labels: NeedsInvestigation

```
#!watchflakes
post <- builder == "openbsd-arm64-jsing" && pkg == "" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/76db7b9a2cdcc46b9bfbd35105e06b07eb804223)):

    go tool compile: signal: killed
    
    build failed: make script failed: exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: build: unrecognized failures on linux-ppc64-buildlet
Labels: NeedsInvestigation

```
#!watchflakes
post <- builder == "linux-ppc64-buildlet" && pkg == "" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/12e8445a652b001d97f62a242211f040d4aa61ce)):

    Test "go_test:cmd/go/internal/mvs" ran over 40m0s limit (40m0.001064589s); saw output:
    
    XXXBANNERXXX:Test execution environment.
    # GOARCH: ppc64
    # CPU: POWER8
    # GOOS: linux
    # OS Version: Linux 4.4.0-130-powerpc64-smp #156-Ubuntu SMP Thu Jun 14 09:28:49 UTC 2018 ppc64


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: runtime/trace: TestTraceCPUProfile failures
Labels: NeedsFix,compiler/runtime

```
#!watchflakes
post <- (pkg == "runtime/trace" && test == "TestTraceCPUProfile") || log ~ `--- FAIL: TestTraceCPUProfile`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/2ad1940fd3468610aa1b13786ac7d4c77452a02a)):

    SIGQUIT: quit
    PC=0x86d24 m=7 sigcode=0
    
    trap    0x0
    error   0x0
    oldmask 0x0
    r0      0x2fbadc
    r1      0x80
    r2      0x0
    r3      0x0
    ...
    	/workdir/go/src/runtime/proc.go:1090 +0x98 fp=0x183acfc sp=0x183acdc pc=0x53e88
    runtime.stopTheWorldGC({0x1c6ecd, 0xc})
    	/workdir/go/src/runtime/proc.go:1137 +0x48 fp=0x183ad10 sp=0x183acfc pc=0x54054
    runtime.StopTrace()
    	/workdir/go/src/runtime/trace.go:320 +0x24 fp=0x183ad28 sp=0x183ad10 pc=0x74ab8
    runtime/trace.Stop()
    	/workdir/go/src/runtime/trace/trace.go:148 +0x78 fp=0x183ad44 sp=0x183ad28 pc=0xe697c
    runtime/trace_test.TestTraceCPUProfile(0x1c04e10)
    	/workdir/go/src/runtime/trace/trace_test.go:621 +0x1a4 fp=0x183af98 sp=0x183ad44 pc=0x1885ec
    testing.tRunner(0x1c04e10, 0x1d3994)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: crypto: boringcrypto cgo pointer failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- builder ~ `boringcrypto` && `cgo argument has Go pointer to Go pointer`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/f43d88fee894998bab34e157c7a2b6ca66e3d074)):

    --- FAIL: TestVersion (0.00s)
    panic: runtime error: cgo argument has Go pointer to Go pointer [recovered]
    	panic: runtime error: cgo argument has Go pointer to Go pointer
    
    goroutine 488 [running]:
    panic({0x3af200, 0x40002fc4c0})
    	/workdir/go/src/runtime/panic.go:987 +0x3e0 fp=0x4000400f60 sp=0x4000400ea0 pc=0x12e190
    testing.tRunner.func1.2({0x3af200, 0x40002fc4c0})
    	/workdir/go/src/testing/testing.go:1396 +0x1c8 fp=0x4000401010 sp=0x4000400f60 pc=0x1d7308
    testing.tRunner.func1()
    ...
    crypto/tls.TestVersion(0x40002a04e0)
    	/workdir/go/src/crypto/tls/handshake_server_test.go:390 +0xc4 fp=0x4000401f60 sp=0x4000401c30 pc=0x3317c4
    testing.tRunner(0x40002a04e0, 0x436b00)
    	/workdir/go/src/testing/testing.go:1446 +0x10c fp=0x4000401fb0 sp=0x4000401f60 pc=0x1d6a3c
    testing.(*T).Run.func1()
    	/workdir/go/src/testing/testing.go:1493 +0x2c fp=0x4000401fd0 sp=0x4000401fb0 pc=0x1d777c
    runtime.goexit()
    	/workdir/go/src/runtime/asm_arm64.s:1165 +0x4 fp=0x4000401fd0 sp=0x4000401fd0 pc=0x1617a4
    created by testing.(*T).Run
    	/workdir/go/src/testing/testing.go:1493 +0x328


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Square brackets break Emmet in TypeScript files
Labels: bug,emmet,emmet-parse

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.71.2
- OS Version: MacOS 12.5.1

Steps to Reproduce:

1. Enable Emmet for TypeScript files, using the `html` language 
2. Type a snippet with an attribute, like `a[href]`. Emmet does not expand the snippet. 

Emmet behaves as expected in HTML files. This feature used to work prior to the VS Code update that came out in mid-May 2022. 

Video showing unexpected behavior in a TypeScript file: 
https://user-images.githubusercontent.com/883698/191588848-4f666b06-0d4e-49a1-8ac5-1fc59f34df36.mp4

Video showing expected behavior in an HTML file. 
https://user-images.githubusercontent.com/883698/191589152-29a0712a-b7c7-49df-9002-0c573fc07680.mp4
Repository: go
Issue: proposal: x/text/transform: Add func (*Reader).Reset(r io.Reader, t Transformer)
Labels: Proposal

The [x/test/transform.Reader](https://pkg.go.dev/golang.org/x/text/transform#Reader) constructor allocates two 4kb buffers. I want to reuse existing `Reader`s with a `sync.Pool` to reduce allocations. I'm proposing a `Reset` method similar to [bufio.Reader.Reset](https://pkg.go.dev/bufio#Reader.Reset)

``` go
func (rd *Reader) Reset(r io.Reader, t Transformer) {
	t.Reset()
	rd.r = r
	rd.t = t
	rd.err = nil
	rd.dst0 = 0
	rd.dst1 = 0
	rd.src0 = 0
	rd.src1 = 0
}
```
Repository: godot
Issue: Mouse cursor disappears inside GDScript editor with scripts in 4.0 beta
Labels: bug,platform:windows,topic:porting,needs testing

### Godot version

4.0 beta

### System information

Win 11, NVidia 3000 series

### Issue description

Hi all, 

I've recently shifted to a newer machine, and i'm running into issues when trying to edit the code. 

This issue isn't persistent, but the mouse cursor keeps disappearing and appearing, seemingly at random. Clicking around a few times sseems to fix it for some time. 

It consistently disappears if I use the scroll wheel on my mouse. 

### Steps to reproduce

Create new project in Godot 4. 

Write some code in a script. 

Try to edit the script. Use the scroll wheel. 

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Use new code action widget in problems view
Labels: feature-request,error-list,editor-code-actions

Tracks adopting the new code actions widget when you click on a lightbulb in the problems panel
Repository: pytorch
Issue: Prim Output Spec is Not Always Consistent With Eager
Labels: triaged,module: primTorch

### 🐛 Describe the bug

For instance, [chunk prim](https://github.com/pytorch/pytorch/blob/master/torch/_refs/__init__.py#L2577 ) returns a tuple while [chunk aten](https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/native_functions.yaml#L1269) returns a list.

To test this you could test the specs [here](https://github.com/pytorch/pytorch/pull/85417#discussion_r976977602), among other places.

### Versions

master

cc @ezyang @mruberry @ngimel @Lezcano @fdrocha
Repository: flutter
Issue: Add flutter/assets-for-api-docs to flutter/tests
Labels: team,good first issue,P2,c: tech-debt,team-framework,triaged-framework

We are breaking this repo without any warning.
Example: https://github.com/flutter/flutter/issues/112114
Repository: angular
Issue: ExpressionChangedAfterItHasBeenCheckedError when *ngIf and asyncValidator use the same observable
Labels: area: forms,core: change detection,forms: validators,P4

### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

No

### Description

```html
<ng-container *ngIf="observable|async">
    <input formControlName="name">
  </ng-container>
```
When `nameFormControl` has an `asyncValidator` that depends on `observable`
The console prints out the following error:
ERROR
Error: NG0100: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'true'. Current value: 'false'. Find more at https://angular.io/errors/NG0100

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-z9hej4?file=src/app/app.component.html

### Please provide the exception or error you saw

```true
ERROR
Error: NG0100: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'true'. Current value: 'false'. Find more at https://angular.io/errors/NG0100
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
See stackblitz
https://stackblitz.com/edit/angular-ivy-z9hej4?file=src/app/app.component.html
```


### Anything else?

_No response_
Repository: storybook
Issue: Migration.md documentation link is broken
Labels: bug,needs triage

The link here:
https://github.com/storybookjs/storybook/blob/ea70649db9bce2ed4ad2b1eaa13a380fb8cc8e57/MIGRATION.md#docs-framework-refactor-for-react

Goes to a 404:
https://github.com/storybookjs/storybook/blob/next/app/react/src/server/framework-preset-react-docs.ts