sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: loading.js does not trigger on dynamic route navigation (within same dynamic route)
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/jel-massih/loading-test

### To Reproduce

1. Start the application in Dev mode
2. Navigate to /
3. Click Dashboard (should show loading for 5s then dashboard)
4. click Dynamic A (should show loading for 5s then Dynamic A)
5. click Dynamic B (Will not show Loading, just "hangs" for 5s until dynamic B is loaded)

### Current vs. Expected behavior

I expected step 5 to show Loading for 5s then Dynamic B, but the loading fallback is never shown.


It appears to be based off navigating to the same dynamic component (even though different route with different params)

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
Binaries:
  Node: 20.7.0
  npm: N/A
  Yarn: N/A
  pnpm: 8.8.0
Relevant Packages:
  next: 14.0.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5
Next.js Config:
  output: N/A
```


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

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

### Additional context

_No response_
Repository: rust
Issue: Tracking Issue for `core_io_borrowed_buf`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(core_io_borrowed_buf)]`

This is a tracking issue for an MVP of `core::io`, which contains an OS-independent subset of `std::io`.

### Public API

The initial API of this module consists of [`BorrowedBuf`](https://doc.rust-lang.org/std/io/struct.BorrowedBuf.html) and [`BorrowedCursor`](https://doc.rust-lang.org/std/io/struct.BorrowedCursor.html), which were previously only available in `std`.

### Steps / History

- [x] https://github.com/rust-lang/rust/pull/97015
- [x] https://github.com/rust-lang/rust/pull/117694
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: flutter
Issue: The concept of `texture_id` is a misnomer: it's a _key_ and starts (confusingly) at `0`
Labels: engine,P3,c: tech-debt,team-engine,triaged-engine

Filing this for posterity because I wasted over an hour trying to figure out why `texture_id == 0`, to find out that's WAI!

---

We have the concept, including in user-facing code (https://api.flutter.dev/flutter/widgets/Texture/textureId.html) of a `textureId` (or `texture_id` in C++, see https://github.com/search?q=repo%3Aflutter%2Fengine%20texture_id&type=code). Confusingly, this is an auto-incrementing _key_ that starts at 0, meaning the first you create is `0`.

This concept is heavily overloaded, [for example in GL](https://github.com/flutter/engine/blob/a1bad0749afc20318deb5394e7b198943d204b48/shell/platform/linux/fl_pixel_buffer_texture.cc#L15).

It would be nice to:
- Not have this start at `0`
- Potentially have it called `texture_key`, or something that signifies its a lookup key, and not a GL texture.

/cc @jonahwilliams
Repository: pytorch
Issue: EPOCH_DEPRECATION_WARNING in ChainedScheduler.step
Labels: triaged,module: LrScheduler,topic: deprecation

### 🐛 Describe the bug

Using the ``ChainedScheduler`` causes the ``EPOCH_DEPRECATION_WARNING`` to be shown because it calls ``step`` with the argument ``0`` here:
https://github.com/pytorch/pytorch/blob/a8097ed4793a331fb931c3e4f8a6fde46470bdb1/torch/optim/lr_scheduler.py#L672

### Versions

This code is still in the current main branch, see the link above.
Repository: PowerToys
Issue: About "Sleep" and "Hibernate" in Powertoys Run
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage

### Microsoft PowerToys version

0.75.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

![Uploading 屏幕截图 2023-11-08 101805.png…]()
![Uploading 屏幕截图 2023-11-08 101844.png…]()
If I open "Windows System Command" in Powertoys Run, when you input "Sleep" and "Hibernate", both results are  hibernation. These two functions are different, and the hibernation icon seems to be wrong too.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: next.js
Issue: Large unused dependencies added to standalone output
Labels: bug,Output (export/standalone)

### Link to the code that reproduces this issue

https://github.com/robpc/nextjs-standalone-storybook-test

### To Reproduce

Create the project

```bash
npx create-next-app@latest nextjs-standalone-storybook-test
cd nextjs-standalone-storybook-test/
```

Edit the `next.config.js`

```js
/** @type {import('next').NextConfig} */
const nextConfig = {
    output: 'standalone'
}

module.exports = nextConfig
```

Test the standalone build

```bash
$ npm run build
# ...
$ du -sh .next/standalone/node_modules/
23M     .next/standalone/node_modules/
```

Add storybook

```bash
npx storybook@latest init
```

Retest the standalone build

```bash
$ npm run build
# ...
$ du -sh .next/standalone/node_modules/
145M    .next/standalone/node_modules/
```

### Current vs. Expected behavior

Since storybook adds no dependencies used in `app/`, the expectation is that the output would be the same as the build without storybook. In other examples this was observed to be much larger (ex 400mb). This issue is similar to https://github.com/vercel/next.js/issues/51029

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.1
  eslint-config-next: 14.0.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: standalone
```


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

Standalone mode (output: "standalone")

### Additional context

_No response_
Repository: PowerToys
Issue: window10 右键菜单中没有 PowerRename 选项
Labels: Issue-Bug,Product-PowerRename,Needs-Triage

### Microsoft PowerToys version

0.75.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

安装PowerToys，以管理员运行，进入文件夹点击鼠标右键

### ✔️ Expected Behavior

右键菜单中有 PowerRename 的选项

### ❌ Actual Behavior

右键菜单中没有 PowerRename 的选项
![PowerRename](https://github.com/microsoft/PowerToys/assets/44639502/e1bf5739-c2d3-4811-aae7-8896874fa411)
![右键菜单](https://github.com/microsoft/PowerToys/assets/44639502/babd96d2-4339-467a-b7ad-48c4ff954258)


### Other Software

_No response_
Repository: angular
Issue: Allow component template variables to be accessed by tools like ts-morph
Labels: area: compiler

### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

I'm using ts-morph to statically analyze my codebase, I have a large shared folder that is referenced by my server folder, and my client folder (Which contains my angular project). I have some big classes in the shared folder that I want to check if they have properties not reference in either project anymore.

ts-morph is not detecting references inside templates, which makes it limited in how I can apply it totally to analyzing my angular project.

Is there some sort of interim format that an angular component can be converted into which would allow those properties to be 'reached' by tools like ts-morph?

Relevant issue:
https://github.com/dsherret/ts-morph/issues/892

### Proposed solution

Provide an API that I can access to compile my angular project into an interim format, keeping the Typescript types and references for proper coverage

### Alternatives considered

I haven't found any
Repository: kubernetes
Issue: Set enableServiceLinks to false as default
Labels: sig/network,kind/feature,help wanted,triage/accepted

### What would you like to be added?

I want to make enableServiceLinks disabled by default.

### Why is this needed?

Service link environment variables are injected into every pod. It creates three environment variables for every service in a respective pod's namespace, regardless of how they are related. This behavior was observed in EKS 1.24.

In larger namespaces, this can cause pods to crash due to too many environmental variables. I assume this is due to Container runtime or Operating System Limitations.

I assume this was needed for legacy network reasons or installs that do not run cluster DNS. Regardless, Cluster DNS is added by default for most Kubernetes installers (excluding mircok8s) out there today.

I am willing to contribute if this is the direction we want to go.
Repository: vscode
Issue: VSCode forgets all opened documents after update
Labels: bug,freeze-slow-crash-leak,install-update,linux,confirmation-pending

Type: <b>Bug</b>

Each time when VSCode is updated on Ubuntu, it forget all opened documents that was saved. It restores only documents that is not saved. I have not encountered a similar problem on Windows.

VS Code version: Code 1.84.1 (2b35e1e6d88f1ce073683991d1eff5284a32690f, 2023-11-06T12:35:31.181Z)
OS version: Linux x64 5.15.0-90-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3100)|
|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>video_decode: enabled<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|28, 8, 4|
|Memory (System)|31.03GB (7.72GB free)|
|Process Argv|--unity-launch --crash-reporter-id 9971e083-5d53-4fa6-9ebd-ad3924f8b78d|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu-xorg|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu-xorg|
|XDG_SESSION_TYPE|x11|
</details><details><summary>Extensions (44)</summary>

Extension|Author (truncated)|Version
---|---|---
svgo|100|3.1.0
better-comments|aar|3.0.2
numbered-bookmarks|ale|8.4.0
toml|be5|0.6.0
search-crates-io|bel|1.2.1
ini-for-vscode|Dav|0.0.4
confluence-markup|den|1.0.2
seito-openfile|Fr4|2.2.0
kaitai-struct-vscode|fud|0.9.0
pegjs-syntax|fut|0.1.1
gc-excelviewer|Gra|4.2.58
todo-tree|Gru|0.0.226
vscode-systemd-support|han|1.0.1
plantuml|jeb|2.17.5
svn-scm|joh|2.17.0
Kotlin|mat|1.7.1
rainbow-csv|mec|3.8.0
xml-format|mik|1.1.3
vscode-docker|ms-|1.27.0
vscode-language-pack-ru|MS-|1.84.2023110109
vscode-dotnet-runtime|ms-|2.0.0
isort|ms-|2023.10.1
python|ms-|2023.20.0
vscode-pylance|ms-|2023.11.10
jupyter|ms-|2023.10.1003070148
jupyter-renderers|ms-|1.0.17
remote-containers|ms-|0.321.0
hexeditor|ms-|1.9.12
sqltools|mtx|0.24.0
linux-desktop-file|nic|0.0.21
vscode-mindmap|pmc|0.0.7
vscode-xml|red|0.26.1
vscode-yaml|red|1.14.0
rust-analyzer|rus|0.3.1722
crates|ser|0.6.3
vscode-fileutils|sle|3.10.3
code-spell-checker|str|3.0.1
code-spell-checker-russian|str|2.2.0
markdown-jira-links|Tom|1.0.0
markdown-jira-preview|tra|0.0.1
json2yaml|tux|0.2.0
rainbow-tags|vol|0.4.1
vscode-java-pack|vsc|0.25.15
vscode-todo-highlight|way|1.0.5


</details>
<!-- generated by issue reporter -->
Repository: kubernetes
Issue: nestedPendingOperations may cause leakage risks
Labels: kind/bug,sig/storage,lifecycle/rotten,needs-triage

### What happened?

if a pod use a volume, the kubelet will use VerifyControllerAttachedVolume to verify that the volume is attached.when the pendingOperations was not completed, and the pod was removed, the pendingOperations  is not deleted.This [#116886 ](https://github.com/kubernetes/kubernetes/issues/116886) is caused by this problem.


### What did you expect to happen?

when the pod was removed, the pendingOperations  is deleted

### How can we reproduce it (as minimally and precisely as possible)?

1. create a pod with pv
2. volume attach fail
3. remove pod

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```
</details>
v1.25


### Cloud provider

<details>
none
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
none
</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: next.js
Issue: NextJS export does not recognise generateStaticParams
Labels: bug

### Link to the code that reproduces this issue

https://github.com/meds/nextjs-broken-export

### To Reproduce

1. Run `pnpm build`

### Current vs. Expected behavior

I expected nextjs to build and export to an output directory with static files.

Instead I got an error:

`Error: Page "/test/[id]" is missing "generateStaticParams()" so it cannot be used with "output: export" config.`

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Tue Jul 18 20:35:35 PDT 2023; root:xnu-10002.0.199.505.1~3/RELEASE_ARM64_T6000
Binaries:
  Node: 18.12.0
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: 8.6.5
Relevant Packages:
  next: 14.0.1
  eslint-config-next: N/A
  react: 18.0.0
  react-dom: 18.0.0
  typescript: 5.0.2
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

App Router, Static HTML Export (output: "export")

### Additional context

_No response_
Repository: material-ui
Issue: [material-ui][examples] Custom fonts not changing during the initial rendering
Labels: package: material-ui,examples,nextjs

I'm facing an issue with the fonts in my Next.js 14 project with MUIv5 n TypeScript.

 I've used the following code to import and set up fonts..., 


![image](https://github.com/mui/material-ui/assets/76842801/2518bb94-5c9c-49a0-81c9-691f822826ef)


but the fonts are not changing during the initial rendering. However, after the initial rendering, the fonts switch to the customized ones. All other MUI styles are working fine. I followed this (' https://github.com/mui/material-ui/blob/master/examples/material-ui-nextjs-ts/src/components/ThemeRegistry/theme.ts ') for the setup. Can you help me identify what might be causing this font issue..??
Repository: ant-design
Issue: Doesn't show the thumb by scrolling in the dropdown list
Labels: 🐛 Bug,Inactive,4.x

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/basic-usage-antd-4-24-14-forked-nxnt7n?file=/demo.tsx)

### Steps to reproduce

enter a value in the first autocomplete,
scroll down

### What is expected?

scroll's thumb is visible

### What is actually happening?

scroll's thumb is hidden

| Environment | Info |
| --- | --- |
| antd | 4.24.14 |
| React | 18.2.0 |
| System | Win10 |
| Browser | Firefox |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Viewport Texture loosing node_path reference if SubViewport is SubScene root
Labels: bug,topic:core,confirmed

### Godot version

v4.1.3.stable.official [f06b6836a]

### System information

macOS Ventura 13.5.2 - Godot v4.1.3.stable - Forward+ renderer - Apple Silicon M1 Pro

### Issue description

**What doesn't work**
If using the Path to a SubViewport, that is the root of its own Scene, as a viewport_path of a render texture this reference is lost after restarting the editor and hitting play/saving scene.

**How should it work**
The viewport_path should not be updated by the editor on load as the target node path is a valid SubViewport Node.

**Workaround**
If the SubViewport itself is not the root of a subscene, the editor does not loose reference. So the tree structure can be changed that this works.
This is working, though it's not obvious that the scene structure is relevant here and this will throw of users who are new to viewport textures.

**Possible related issues**
This might be related to issues in Godot 3:
https://github.com/godotengine/godot/issues/27790
https://github.com/godotengine/godot/issues/83898


### Steps to reproduce

- Load the minimal reproduction project
- Hit start or save
- reference in `BrakingReference/Sprite3D::texture::viewport_path` is lost (you can git diff to see the change in reference or just see that the render texture is not rendered)<img width="413" alt="Screenshot 2023-11-08 at 09 00 33" src="https://github.com/godotengine/godot/assets/9337940/25871f14-4859-48d6-b40f-840a831e07cf">


### Minimal reproduction project

Reproduction project is located here: https://github.com/nerdlibfront/godot-4.1-viewport-scene-issue
Or here: ~[ViewportSceneIssue.zip](https://github.com/godotengine/godot/files/13294043/ViewportSceneIssue.zip)~ [ViewportSceneIssue.zip](https://github.com/godotengine/godot/files/13296486/ViewportSceneIssue.zip)
Repository: flutter
Issue: Improve "CocoaPods not installed or not in valid state." message
Labels: tool,platform-mac,c: proposal,a: error message,P2,team-ios,triaged-ios

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I was having an issue with Cocoapods installation and added the following code to the flutter_tool to better understand the problem.
My issue was that I installed a new ruby version and cocoapods with brew. In my terminal everything was working fine and I was able to build the flutter app. However when running from VS Code the build exited with "CocoaPods not installed or not in valid state." To better understand the problem I added the ruby version and environment variables output to the log message.

My ruby setup was that I added a .ruby-version file to my home drive and used the chruby setup:
```
source /opt/homebrew/opt/chruby/share/chruby/chruby.sh
source /opt/homebrew/opt/chruby/share/chruby/auto.sh
```
With auto.sh chruby will pick the ruby version from the .ruby-version file and activate it.
However when building the app the PWD of the build script is the app directory and not user home. Therefore .ruby-version was not found and the build used the system ruby that has no cocoapods installed. 

With the additional output it was way easier to understand and solve the problem. I'm seeing many questions about "CocoaPods not installed" and I think that some additional output might help here.

### Proposal

Add following code in cocoapods.dart in processPods method:
```dart
      if (!await _checkPodCondition()) {
        if (_logger.isVerbose) {
          RunResult result = await _processUtils.run(
            <String>['ruby', '--version'],
          );
          _logger.printStatus(result.toString());

          Map<String, String> env = LocalPlatform().environment;
          env.forEach((k, v) => _logger.printStatus("$k=$v"));
        }
        throwToolExit('CocoaPods not installed or not in valid state.');
      }
```

This will show the user the ruby version and the environment variables, especially the PATH variable.
Repository: vscode
Issue: Unable to open large files -VSCode either hangs or crashes
Labels: under-discussion,editor-textbuffer

<!-- ⚠️⚠️ 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.84.1`
- OS Version: MacOS 14.1 (23B74), 32GB RAM

Steps to Reproduce:

1. Open a large file (in my case a 1GB file but I have the same issues with files as small as 35MB)
2. VS Fails to load the file

I'm finding different behaviours in the latest build to earlier builds, when opening a 1GB file it does now warn you:

![image](https://github.com/microsoft/vscode/assets/254564/cd2c6b52-5ea8-4973-a84d-2bbc421ed6e4)

Accepting that though now shows an error:

![image](https://github.com/microsoft/vscode/assets/254564/c770f1b0-cc7e-4d25-9d3f-6fd20cb7e825)

Clicking Retry there then shows a different error:

![image](https://github.com/microsoft/vscode/assets/254564/af6746c7-bf41-45fc-9e58-48f2aa3bc0f9)

Which then loops back to the retry one (and loops).

Opening a smaller file e.g. 34MB opens the file without warning and shows the first line (or most of it). When you enable line wrapping, it just shows the "Show more" message below before just hanging and not doing anything:

![image](https://github.com/microsoft/vscode/assets/254564/8596730f-abd6-458a-8b84-5338a4800ad5)

The files in this instance are large JSON files but opening as `Plain Text` doesn't appear improve anything.

None of these files used to be a problem until the last few months.

I don't think it's the exact same issue but I did find this which may be related: https://github.com/microsoft/vscode/issues/196510