sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Shared Element Transitions not working properly in nested layouts in App Router.
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/eloquent-kirch-m4cgrw?file=%2Fapp%2F%28main%29%2Fwritings%2Fpage.tsx%3A1%2C1-31%2C1

### To Reproduce

open the codesandbox, and interact with the preview. Click on links and visit different pages. You will see the shared element animations are not working properly. From "Home" to any is working but when going from "x"(other than home) to "y", the layout animations are not working properly.

### Current vs. Expected behavior

"Current" =>
The elements in does not animate properly if there is no layout.tsx file present or even if present.

"Expected" =>
 The elements should animate without any glitching.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: angular
Issue: Consider setting up  "Custom Properties" feature in Angular repositories
Labels: area: dev-infra,P4,area: docs

### Describe the problem that you experienced

I noticed a **new** label in the Angular repositories, in the metadata section, named `Custom Properties`. When clicking it, you are redirected to the new "Custom properties" page at https://github.com/angular/angular/custom-properties.

---

Github has a new beta feature for setting `Custom Properties` at Organization level to your repositories and decorate them with custom metadata or similar, as described at [Github docs](https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization). 

> Custom properties allow you to decorate your repository with information such as compliance frameworks, data sensitivity, or project details.

### Add a screenshot if that helps illustrate the problem

![image](https://github.com/angular/angular/assets/112062588/424cf6d3-2df7-4eb6-82da-22a9cd03ecd6)

### Enter the URL of the topic with the problem

https://github.com/angular/angular

### Suggestion

I suggest to consider digging in on the new feature and setting it up or disabling it, if possible, to clear up boilerplate labels in the repositories metadata section.

### References

 - https://github.blog/changelog/2023-10-12-github-repository-custom-properties-beta/
 - https://github.com/orgs/community/discussions/69914
 - https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization
Repository: flutter
Issue: Auto-set `SystemUiOverlayStyle` separately for each route
Labels: c: new feature,framework,f: routes,c: proposal,P3,team-framework,triaged-framework

### Use case

I set the notification bar color differently for each screen in my app, using 

```dart
SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle(statusBarColor: color));
```

Let's say I set `statusBarColor` to `Colors.amber`.  When I open a full-screen modal with a white background, I still see the notification bar in amber color. The notification bar color should change to white, if a full-screen modal is opened with a white background.

Additionally, when I navigate between pages in my app, I have to manually change the `statusBarColor` in response to navigation events, which requires boilerplate (I would like this change to happen automatically).

### Proposal

A navigation route should have an optional `SystemUiOverlayStyle` associated with it, and if available, `SystemChrome.setSystemUIOverlayStyle` will be set with this style when the route is navigated to.

If the route is a full-screen modal, then the style should be determined automatically, by setting the style based on the background color of the modal, unless an override `SystemUiOverlayStyle` is provided when the modal is opened.

All navigation actions should call `SystemChrome.setSystemUIOverlayStyle` to whatever style information is available, or fall back on the system default if a style is not available for a given route.
Repository: svelte
Issue: Bad error messages (Svelte 5 & 4)
Labels: feature request,compiler

### Describe the bug

When referencing properties of `undefined` state, you'll get a "cryptic" error message: `get(...) is undefined`, which is not very helpful while debugging. Filed as a Bug because I think exposing errors that reference the compiled code, is not the intended way of describing problems with the code to the dev.

Keep in mind that this is not only Svelte 5 specific. Svelte 4 also has these cryptic errors like `ctx[0] is undefined`. It'd be nice if Svelte 5 finally fixes this.

### Reproduction

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA42PQU_DMAyF_4qxdgBpbe-lm4S48B8oh9C4zFIaR4k3bar630lTMQ5cOD77PT9_M47sKGH7PqM3E2GLLyHgHvUWVpEu5JSyTnKOwzrp0hA56LH3vfIUJCq8nthZGKNM0GPdFFlvyR6fszFbHSkMxXeAXVKj9PiUV13ze85326FP9rbVE6fDXBILNGW9qTpECRT1tkD3UFVgrAXjQYKyeONyiWHP_gtWl1GJoAIjX6GqjpljEssjk8VW45mW_R27dP8XnK4FfBCfFH4eymQ9vpFzUqjvaH9bP5ZvR6JTq3gBAAA=

### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 6.5 Pop!_OS 22.04 LTS
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1235U
    Memory: 7.08 GB / 15.32 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 19.3.0 - ~/.nvm/versions/node/v19.3.0/bin/node
    npm: 9.2.0 - ~/.nvm/versions/node/v19.3.0/bin/npm
  Browsers:
    Chrome: 119.0.6045.199
    Firefox: 120.0
```


### Severity

annoyance
Repository: material-ui
Issue: [pigment-css][POC] Performance improvement on mui.com/blog
Labels: proof of concept,package: pigment-css

## Goal

Get a real scenario result when the current styled engine (emotion) is replaced with zero-runtime.

| /blog        	| Pages router 	| App router 	|
|--------------	|--------------	|------------	|
| emotion      	|   [result](https://www.webpagetest.org/result/240126_BiDc20_5XT/)          	|     [result](https://www.webpagetest.org/result/240126_AiDc07_6AH/)       	|
| hybrid  (components migrated except `sx`)         	|              	|      [result](https://www.webpagetest.org/result/240209_AiDcBS_8H2/)      	|
| zero-runtime 	|              	|     [result](https://www.webpagetest.org/result/240212_AiDc39_1SV/)       	|

## Components

These components need to be migrated to opt in to zero-runtime API:

- [x] ⏳ Alert https://github.com/mui/material-ui/pull/41230
- [x] Avatar https://github.com/mui/material-ui/pull/40324
- [x] ⏳ AvatarGroup https://github.com/mui/material-ui/pull/41485
- [ ] Box
- [x] ⏳ Button https://github.com/mui/material-ui/pull/41378
- [ ] Container
- [x] ⏳ Chip https://github.com/mui/material-ui/pull/41592
- [x] ⏳ Divider https://github.com/mui/material-ui/pull/41366
- [x] ⏳ FormLabel https://github.com/mui/material-ui/pull/41613
- [ ] ⏳ FormHelperText (waiting for codemod)
- [x] ⏳ IconButton https://github.com/mui/material-ui/pull/41850
- [ ] ⏳ InputBase
- [ ] ⏳ Link - Need solution for `extendSxProp`
- [ ] ⏳ Typography - Need solution for `extendSxProp`
- [ ] ⏳ Paper - uses `useTheme`
- [x] ⏳ Pagination, PaginationItem https://github.com/mui/material-ui/pull/41848
- [x] ⏳ SvgIcon https://github.com/mui/material-ui/pull/41779
Repository: next.js
Issue: window is not assignable on server side
Labels: bug,TypeScript

### Link to the code that reproduces this issue

https://github.com/2wheeh/lexical-nextjs-ssr.git

### To Reproduce

can reproduce here: https://stackblitz.com/~/github.com/2wheeh/lexical-nextjs-ssr
or on your local
1. clone the repo
2. install packages and run dev
3. open `localhost:3000` in your browser
4. check the log on the terminal

### Current vs. Expected behavior

### Current
`window` seems not assignable while `global.window` is assigned.
After `global.window` is assigned, `typeof window` is still `undefined`

### Expected
`typeof window` should be `object` after `global.window = /* object */`

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:34 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8103
Binaries:
  Node: 20.5.0
  npm: 9.8.0
  Yarn: 1.22.19
  pnpm: 8.14.1
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, TypeScript (plugin, built-in types)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context
There can be many packages running on headless environment, which developers expect to work in nextjs serverside with checking `typeof window`.

For example, `@lexical/headless` asserts `typeof window !== undefined` to check dom availability. but as you see, `window` is not assignable on nextjs server, which makes hard to use this.
Repository: electron
Issue: [Feature Request]: A option to start a synchronous 'application-quit' function when electron quits
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

IMHO, to properly close, and dispose of things, when an electron application quits is not trivial.

In my case I need to close and dispose of some database connections.

I tried the events 'will-quit', 'before-quit' and 'quit', but then not all code will be executed. The proposed solution for how to handle this seems awkward to me: [#9433](https://github.com/electron/electron/issues/9433).

It also looks like electron (i am using v25.2.0) uses `proces.exit()`? Or so it seems because I can't do `process.on('beforeExit', ...`.


### Proposed Solution

So now I am using `process.on('exit', ....`.

It maybe that this is what you are supposed to do, but in that case, it should be described more precisely in the documentation.

Otherwise, an 'application-quit' event that is executed synchronously would be appreciated.

### Alternatives Considered

 `process.on('exit', ....`

### Additional Information

-
Repository: go
Issue: os/user: Lookup() method returns incorrect user type when NT4 users are migrated to Active Directory
Labels: OS-Windows,NeedsInvestigation

### Go version

go version go1.20 windows/amd64

### Output of `go env` in your module/workspace:

```shell
set GO111MODULE=off
set GOARCH=amd64
set GOBIN=
set GOCACHE=****
set GOENV=****
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=****
set GONOPROXY=https://github.com/golang/go.git
set GONOSUMDB=https://github.com/golang/go.git
set GOOS=windows
set GOPATH=****
set GOPRIVATE=https://github.com/golang/go.git
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=****
set GOVCS=
set GOVERSION=go1.20
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=****
```


### What did you do?

When users from deprecated NT4 Domain controller are migrated to the new Active Directory, the method Lookup from os/user used to identify the type of user returns incorrect type.

### What did you see happen?

The returned type of user is SidTypeGroup

### What did you expect to see?

The expected type is SidTypeDomain.
Repository: vscode
Issue: Error: Provider copilot must be declared in the package.json.
Labels: bug,panel-chat

* run with your normal extensions, including copilot
* create a new completely empty profile
* switch to the new profile and back
* 🐛 see the error below and notice there is no more chat for you

```
 ERR Provider copilot must be declared in the package.json.: Error: Provider copilot must be declared in the package.json.
    at k.$registerChatProvider (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1576:26522)
    at m.S (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1590:13967)
    at m.Q (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1590:13733)
    at m.M (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1590:12826)
    at m.L (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1590:11905)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1590:10692)
    at a.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at a.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at s.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:628:14452)
    at x.onmessage (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1662:7749)
```
Repository: TypeScript
Issue: Allow `abstract` modifier on construct signature in object type literal
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

'abstract' modifier cannot appear on a type member

### ✅ Viability Checklist

- [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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Allow using `abstract new …` constructor definition keywords in an interface, i.e. in an object form (i.e., within curly braces).

### 📃 Motivating Example

Consider possible definitions of:
- a function (a callable object),
- a non-abstract constructor,
- an abstract constructor.

All of those definitions can be created through type aliasing:

```ts
type Callable = () => void // ✅
```

```ts
type Constructor = new () => void // ✅
```

```ts
type ConstructorAbstract = abstract new () => void // ✅
```

But only the first two definitions can be created using an object form:

```ts
type Callable = { (): void } // ✅
```

```ts
type Constructor = { new (): void } // ✅
```

```ts
type ConstructorAbstract = { abstract new (): void } // ❌
//                           ^^^^^^^^
// Error: 'abstract' modifier cannot appear on a type member
```

_[Try it](https://tsplay.dev/WozPMm)._

Apparently, in this form the token `new` is considered a method name, rather than a keyword.

I suggest making the last one a valid expression by parsing `new` as a keyword.

### 💻 Use Cases

This suggestion is mainly for visual consistency, there is no functional change sought to be. To the folks who prefer using interfaces whenever possible (like me), the requirement of using `type` here is somewhat unreasonable, although it doesn't pose any significant problems.
Repository: godot
Issue: Flashing lights in volumetric fog when attenuation is above 3
Labels: bug,topic:rendering,topic:3d

### Tested versions

- Reproducible in 4.2 and 4.2.1

### System information

Godot v4.2.1.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 960 (NVIDIA; 31.0.15.4617) - Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 Threads)

### Issue description

Lights with a high attenuation flicker when placed in a volumetric fog (effect appears both in scene view and when I run the project).
The effect seem to change randomly depending on the distance to the point of view.
Here the attenuations are 1;3;4 in order for those three lights.

https://github.com/godotengine/godot/assets/12957658/6989158b-ab6e-4863-bfe2-9bc612f022bd



### Steps to reproduce

- Create a scene 3d
- create a WorldEnvironment and activate volumetric fog
- create an omnilight and increase it's attenuation above 3
- (optional) move the light relative to the point of view, it makes the effect more noticeable

### Minimal reproduction project (MRP)

[LightsFlashInVolFogMRP.zip](https://github.com/godotengine/godot/files/14051497/LightsFlashInVolFogMRP.zip)
Repository: godot
Issue: Duplicating a script causes the current script to display wrong UID
Labels: bug,topic:gdscript,topic:editor,confirmed

- *Production edit: Related to https://github.com/godotengine/godot/issues/96313.*

### Tested versions

4.3 4b6ad34

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 30.0.15.1403) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When you duplicate a script and the original script is currently opened in the script editor, its UID will change and will be the same as UID of the new script. The bug is purely visual for some reason. When you open the script in external editor, you'll see that it has the old UID and it's different from the new script. The script in editor fixes itself after you save it or switch tab a couple of times. It does not happen if the script is not currently opened in the editor.

### Steps to reproduce

1. Create a GDScript
2. Open it in the script editor
3. Duplicate the script
4. Open the new script
5. Notice that both scripts have the same UID
6. It's a lie

### Minimal reproduction project (MRP)

N/A
Repository: storybook
Issue: [Bug]: Preview cannot find TypeScript types
Labels: bug,typescript,windows

### Describe the bug

Some stories are unable to render and emit the error as shown below:
![image](https://github.com/storybookjs/storybook/assets/1837417/d126f2b9-71d5-4e42-bd03-cc0d44f6e178)

The weird part is that these are TypeScript types.

If more information is needed, do not hesitate to ask.

### To Reproduce

_No response_

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (28) x64 13th Gen Intel(R) Core(TM) i7-13850HX
  Binaries:
    Node: 20.10.0 - ~\AppData\Local\fnm_multishells\14564_1706168480832\node.EXE
    Yarn: 1.22.21 - ~\AppData\Local\fnm_multishells\14564_1706168480832\yarn.CMD
    npm: 10.2.3 - ~\AppData\Local\fnm_multishells\14564_1706168480832\npm.CMD
    pnpm: 8.11.0 - ~\AppData\Local\fnm_multishells\14564_1706168480832\pnpm.CMD <----- active
  Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (120.0.2210.144)
  npmPackages:
    @storybook/addon-actions: ^7.6.10 => 7.6.10
    @storybook/addon-controls: ^7.6.10 => 7.6.10
    @storybook/addon-docs: ^7.6.10 => 7.6.10
    @storybook/addon-essentials: ^7.6.10 => 7.6.10
    @storybook/addon-knobs: ^7.0.2 => 7.0.2
    @storybook/addon-links: ^7.6.10 => 7.6.10
    @storybook/addons: ^7.6.10 => 7.6.10
    @storybook/react: ^7.6.10 => 7.6.10
    @storybook/react-vite: 7.6.10 => 7.6.10
    eslint-plugin-storybook: ^0.6.15 => 0.6.15
    storybook: 7.6.10 => 7.6.10
```


### Additional context

_No response_
Repository: TypeScript
Issue: Wrong error message for testing `void` with `??`
Labels: Suggestion,Domain: Error Messages,Experience Enhancement

### 🔎 Search Terms

nullish An expression of type 'void' cannot be tested for truthiness.

(there are many closed issues with these search term, but they are all from people confused by why this is an error in the first place)

### 🕗 Version & Regression Information

- This is the behavior in every version I tried


### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.3.3#code/CYUwxgNghgTiAEA3W8oC4kHsCWwDcAUAVPAPynwBmUEAziHkA

### 💻 Code

```ts
declare var a: void;

a ?? false;
```


### 🙁 Actual behavior

It reports "An expression of type 'void' cannot be tested for truthiness."

### 🙂 Expected behavior

The error message should not mention truthiness, since I'm not testing for truthiness. nullishness? :P

### Additional information about the issue

_No response_
Repository: next.js
Issue: getStaticPath got invoked but not getStaticProps inside pages/blog/[slug].js
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/ayush166/nextjs

### To Reproduce

Hi folks experiencing an issue with **getStaticProps**

1. Start the application in development npm run dev 
2. Click on the Blog Higher Order Functions.  localhost:3000 -> localhost:3000/blogs/higher-order-functions
3. In the Folder directory go to pages/blogs/[slug].js notice here getStaticPaths function inside that console.log shows up but getStaticProps's console dosen't show up in server/termial console 

conculusion getStaticPath function was invoked but getStaticProps don't get invoked 


### Below function is getting invoked in pages/blog/[slug].js
![gspths](https://github.com/vercel/next.js/assets/52309783/57ee03b7-f9d6-4dbc-9d8b-8c43255c1bfd)


![gsp](https://github.com/vercel/next.js/assets/52309783/9d371752-fe41-4653-976e-9401ede2eded)

only getStaticPaths get as output in the console but not getStaticProps
![image](https://github.com/vercel/next.js/assets/52309783/39a663f7-65d0-4661-a6e9-eeefcbecb122)





### Current vs. Expected behavior

Current Behaviour:  getStaticProps is not getting invoked

Expected behaviour: getStaticProps should get invoked 

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language   
Binaries:
  Node: 20.11.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, App Router, Data fetching (gS(S)P, getInitialProps)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I am using app directory and pages directory too