sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: When generateMetadata performs an asynchronous action, Suspense is not being rendered until generateMetadata finish
Labels: bug,Metadata,Performance

### Link to the code that reproduces this issue

https://github.com/ebidrey/suspense-generate-metadata

### To Reproduce

### To Reproduce

You can run this simple snippet

```javascript
import { Suspense } from "react"

export async function generateMetadata() {
    const results = await fetch('https://postman-echo.com/delay/2');
    await results.json();
    return {
        title: 'Test',
        description: 'Test',
    }
}

async function PageContent() {
    const results = await fetch('https://postman-echo.com/delay/2');
    await results.json();
    return  <h1>Test</h1>
}

export default async function Page() {
    return (
        <Suspense fallback={<div>loading running 2 seconds later</div>} key={Math.random()}>
            <PageContent />
        </Suspense>
    )
}
```

It is also available in [github repo](https://github.com/ebidrey/suspense-generate-metadata)

### Current vs. Expected behavior

I expect suspense fallback to be activated immediately when the page request is made and then, the page and the metadata get streamed. Instead, page stucks for the amount of time the request to the api takes, showing nothing up to the request finished, degradating the user experience and not improving SEO in any way. 

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.10
  pnpm: N/A
Relevant Packages:
  next: 15.0.4-canary.14 // Latest available version is detected (15.0.4-canary.14).
  eslint-config-next: 15.0.4-canary.14
  react: 19.0.0-rc-380f5d67-20241113
  react-dom: 19.0.0-rc-380f5d67-20241113
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

Metadata, Performance

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

Tested in latest canary and stable.
Repository: transformers
Issue: Allow to give the dataset multiprocessing_context
Labels: Feature request

### Feature request

In Huggingface Trainer, allow to pass the multiprocessing context : https://pytorch.org/docs/stable/data.html#torch.utils.data.DataLoader

### Motivation

For a dataset that is loaded on multiple cpu cores, sometimes the fork method creates problems (with polars for example) and the spawn method is more adapted. 

### Your contribution

I could do a PR. A fix could be to add one more parameter to Trainer and pass it to the Dataloader down the line.
Repository: neovim
Issue: LSP: vim.lsp.codelens.run() operates on the innermost scope
Labels: enhancement,lsp

### Problem

Some code lenses (e.g. ruby-lsp's `rubyLsp.runTest`) span multiple lines, that is, their `range.start.line` and `range.end.line` may be different.

When I am working on a test and ready to run it again, I have to navigate up to its first line before I can invoke `vim.lsp.codelens.run()`, which adds a little friction.

I have [code in my `init.lua`](https://github.com/matthewtodd/dotfiles/blob/7c6a7b0b2652e084bfcf8b21d58e93854fb81032/etc/nvim/init.lua#L59-L82) to detect enclosing code lenses for the current line and navigate up to the first line of the narrowest one, but I'm wondering if solving this for everyone would be interesting.

### Expected behavior

I would love to have a way to run the narrowest enclosing codelens without having to navigate.

Maybe this is making `vim.lsp.codelens.run()` magic, or maybe it's offering a new magic `vim.lsp.codelens.runEnclosing()` function, or maybe it's just having `vim.lsp.codelens.run()` accept an optional line number, falling back to the current cursor line.

Happy to work up a PR for any of this, but figured I'd start the conversation first!
Repository: godot
Issue: Moving C# scripts outside of Godot breaks source generation
Labels: bug,needs testing,topic:dotnet

### Tested versions
Met right now, v4.3.0, never saw before.

### System information
Godot v4.3.0

### Issue description
I have couple a code for a potions system:
``` csharp
using Godot;

namespace Workgame.Inventory.Items;

[GlobalClass] public partial class Potion : Item {
	[Export] public int Energy;
	[Export] public double Duration;

	public void Consume() {
	}
}
```

When I, as always, go to Godot and build the project I get this:
- /home/operator/projects/project-alpha/scripts/inventory/items/potions/Potion.cs (4 issues)
    - CS0579: Duplicate 'GlobalClass' attribute /home/operator/projects/project-alpha/scripts/inventory/items/potions/Potion.cs(5,2)
    - CS0102: The type 'Potion' already contains a definition for 'Energy' /home/operator/projects/project-alpha/scripts/inventory/items/potions/Potion.cs(6,22)
    - CS0102: The type 'Potion' already contains a definition for 'Duration' /home/operator/projects/project-alpha/scripts/inventory/items/potions/Potion.cs(7,25)
    - CS0111: Type 'Potion' already defines a member called 'Consume' with the same parameter types /home/operator/projects/project-alpha/scripts/inventory/items/potions/Potion.cs(9,14)
- /home/operator/projects/project-alpha/Godot.SourceGenerators/Godot.SourceGenerators.ScriptPropertiesGenerator/Workgame.Inventory.Items.Potion_ScriptProperties.generated.cs (2 issues)
    - CS0102: The type 'Potion.PropertyName' already contains a definition for 'Energy' /home/operator/projects/project-alpha/Godot.SourceGenerators/Godot.SourceGenerators.ScriptPropertiesGenerator/Workgame.Inventory.Items.Potion_ScriptProperties.generated.cs(24,61)
    - CS0102: The type 'Potion.PropertyName' already contains a definition for 'Duration' /home/operator/projects/project-alpha/Godot.SourceGenerators/Godot.SourceGenerators.ScriptPropertiesGenerator/Workgame.Inventory.Items.Potion_ScriptProperties.generated.cs(28,61)

That happened after I moved `scripts/inventory/items/Potion.cs` to `scripts/inventory/items/potions/Potion.cs`.

### Steps to reproduce
You should try to move your C# script files from one folder to other using filemanager or your code editor, I personally moved it with `mv` commands in terminal. When I moved `Potions.cs` back from `scripts/inventory/items/potions` to `scripts/inventory/items` and built the project that buggy error disappeared.

### Minimal reproduction project (MRP)
It can be ***anything***. You just do the **Steps to reproduce** section.
Repository: go
Issue: x/tools/gopls: feature: support SnippetTextEdit in codeactions
Labels: FeatureRequest,gopls,Tools

### gopls version

.

### go env

```shell
.
```


### What did you do?

Jdtls's [preview](https://github.com/redhat-developer/vscode-java) version has this feature, and lsp has [snippetTextEdit](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/#snippetTextEdit) merged

### What did you see happen?


https://github.com/user-attachments/assets/6fcb6b07-150b-4401-bd07-fee7a93cb129



### What did you expect to see?

With snippets, for extract function/method/variable, we can change function/variable name in two places at the same time; for fill struct, all the right side of property assignment can be a snippet node; and for generate missing function/method, we can select the panic("unimplemented") so user can replace it right away.

### Editor and settings

_No response_

### Logs

_No response_
Repository: next.js
Issue: Intercepted routes don't update metadata
Labels: bug,Metadata,linear: next,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/pseudotsuga-fir/nextgram-broken-metadata

### To Reproduce

1. Add unique metadata to an intercepted route
```js
export async function generateMetadata({
  params,
}: {
  params: Promise<{ id: string }>;
}): Promise<Metadata> {
  const id = (await params).id;

  return {
    title: `Page ${id} intercepted`,
  };
}
```
2. Add link to a page that leads to intercepted route, see that intercepted page does not change the metadata

### Current vs. Expected behavior

## Current
Metadata remains the same as the current page when intercepting a route, despite the intercepted route providing its own metadata. The metadata for the intercepted route WILL display however under the specific circumstance of navigating as such via the `<Link>` component: Page 1 (provides custom metadata) > Page 2 (does not provide metadata) > Intercepted Route (provides custom metadata).

<img width="1399" alt="Screenshot 2024-11-18 at 2 49 26 PM" src="https://github.com/user-attachments/assets/08a61ce3-65bc-4eef-a910-e4beec432c0c">

## Expected
Metadata updates upon navigating to an intercepted route based on the metadata provided in the `page` of that route.

<img width="1399" alt="Screenshot 2024-11-18 at 2 49 58 PM" src="https://github.com/user-attachments/assets/f1d9e3bf-476e-413b-8b89-08c464ea1950">


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:06:26 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8112
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 8.9.0
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: N/A
  react: 19.0.0-rc-fb9a90fa48-20240614
  react-dom: 19.0.0-rc-fb9a90fa48-20240614
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata, Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

**Working example**: [Repo](https://github.com/pseudotsuga-fir/nextgram-working-metadata) and [Live](https://nextgram-working-metadata.vercel.app)

This bug was fixed in `v14.0.5-canary.24`, likely by one of these two pull requests:
- [PR 59861](https://github.com/vercel/next.js/pull/59861)
- [PR 59791](https://github.com/vercel/next.js/pull/59791)

The last working version was `v14.1.4`; I was unable to find which canary version or commits broke this. Issue has remained present since.

Does not work in current canary version as of writing this issue: `v15.0.4-canary.18`
Repository: kubernetes
Issue: Division-by-zero in Horizontal Workload Autoscaler
Labels: kind/bug,sig/autoscaling,needs-triage

**Which component are you using?**:

Horizontal workload autoscaler.

**What version of the component are you using?**:

Not relevant.

**What k8s version are you using (`kubectl version`)?**:

<details><summary><code>kubectl version</code> Output</summary><br><pre>
$ kubectl version
Client Version: v1.30.6-dispatcher
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.5-gke.1443001
</pre></details>

**What environment is this in?**:

Not relevant.

**What did you expect to happen?**:

When the horizontal autoscaler computes the expected number of replicas, [it uses the following formula](https://github.com/kubernetes/kubernetes/blob/cf480a3a1a9cb22f3439c0a7922822d9f67f31b5/pkg/controller/podautoscaler/replica_calculator.go#L369):

```go
usageRatio := float64(usage) / (float64(targetUsagePerPod) * float64(statusReplicas))
```

(This formula (or a variation of it) appears a couple of times in [this file](https://github.com/kubernetes/kubernetes/blob/cf480a3a1a9cb22f3439c0a7922822d9f67f31b5/pkg/controller/podautoscaler/replica_calculator.go#L369).)

It's not impossible that `statusReplicas` (i.e. the `status.replicas` field of the `/scale` subresource) equals zero (e.g. if a user kills pods), leading to a division by zero.

[The Golang spec allows divisions by zero to trigger traps](https://github.com/golang/go/issues/43577), although most implementations would return +Inf (which leads to the correct behaviour) or NaN (if `usage == 0.`, in which case the func would return a negative number of replicas).

**What happened instead?**:

This problem could lead to a panic, or an incorrect behaviour. This could only happen as a result of a race condition, and in the unlikely situation where `status.replicas == 0`. I'm not sure of its practical significance.

**How to reproduce it (as minimally and precisely as possible)**:

This issue only appears as a result of a race condition. I couldn't produce it.
Repository: vscode
Issue: Allow extensions to augment an existing language's configuration, such as surroundingPairs
Labels: feature-request,languages-basic,extensions-editor

From #233981

I'd like for the built-in markdown math extension to add a new set of surrounding pairs for the `markdown` language. Currently this doesn't seem possible as each configuration item overwrites the previous:

https://github.com/microsoft/vscode/blob/23457f87fb66a13e910df8b2c2ae22ca9595e6d2/src/vs/editor/common/languages/languageConfigurationRegistry.ts#L254
Repository: ollama
Issue: GPU radeon not used
Labels: bug,amd,needs more info,install

### What is the issue?

GPU not used:
2024/11/18 20:38:09 routes.go:1158: INFO server config env="map[CUDA_VISIBLE_DEVICES: GPU_DEVICE_ORDINAL: HIP_VISIBLE_DEVICES: HSA_OVERRIDE_GFX_VERSION: HTTPS_PROXY: HTTP_PROXY: NO_PROXY: OLLAMA_DEBUG:false OLLAMA_FLASH_ATTENTION:false OLLAMA_GPU_OVERHEAD:0 OLLAMA_HOST:http://127.0.0.1:11434 OLLAMA_INTEL_GPU:false OLLAMA_KEEP_ALIVE:5m0s OLLAMA_LLM_LIBRARY: OLLAMA_LOAD_TIMEOUT:5m0s OLLAMA_MAX_LOADED_MODELS:0 OLLAMA_MAX_QUEUE:512 OLLAMA_MODELS:/mnt/data/read/LLM/ollama/.ollama/models OLLAMA_MULTIUSER_CACHE:false OLLAMA_NOHISTORY:false OLLAMA_NOPRUNE:false OLLAMA_NUM_PARALLEL:0 OLLAMA_ORIGINS:[http://localhost https://localhost http://localhost:* https://localhost:* http://127.0.0.1 https://127.0.0.1 http://127.0.0.1:* https://127.0.0.1:* http://0.0.0.0 https://0.0.0.0 http://0.0.0.0:* https://0.0.0.0:* app://* file://* tauri://*] OLLAMA_SCHED_SPREAD:false OLLAMA_TMPDIR: ROCR_VISIBLE_DEVICES: http_proxy: https_proxy: no_proxy:]"
time=2024-11-18T20:38:09.214-04:00 level=INFO source=images.go:754 msg="total blobs: 69"
time=2024-11-18T20:38:09.372-04:00 level=INFO source=images.go:761 msg="total unused blobs removed: 0"
time=2024-11-18T20:38:09.373-04:00 level=INFO source=routes.go:1205 msg="Listening on 127.0.0.1:11434 (version 0.3.14)"
time=2024-11-18T20:38:09.373-04:00 level=INFO source=common.go:135 msg="extracting embedded files" dir=/tmp/ollama1129448929/runners
time=2024-11-18T20:38:15.122-04:00 level=INFO source=common.go:49 msg="Dynamic LLM libraries" runners="[cpu_avx2 cuda_v11 cuda_v12 rocm_v60102 cpu cpu_avx]"
time=2024-11-18T20:38:15.122-04:00 level=INFO source=gpu.go:221 msg="looking for compatible GPUs"
time=2024-11-18T20:38:15.130-04:00 level=WARN source=amd_linux.go:61 msg="ollama recommends running the https://www.amd.com/en/support/linux-drivers" error="amdgpu version file missing: /sys/module/amdgpu/version stat /sys/module/amdgpu/version: no such file or directory"
time=2024-11-18T20:38:15.133-04:00 level=WARN source=amd_linux.go:440 msg="amdgpu detected, but no compatible rocm library found.  Either install rocm v6, or follow manual install instructions at https://github.com/ollama/ollama/blob/main/docs/linux.md#manual-install"
time=2024-11-18T20:38:15.133-04:00 level=WARN source=amd_linux.go:345 msg="unable to verify rocm library: no suitable rocm found, falling back to CPU"
time=2024-11-18T20:38:15.133-04:00 level=INFO source=gpu.go:384 msg="no compatible GPUs were discovered"
time=2024-11-18T20:38:15.133-04:00 level=INFO source=types.go:123 msg="inference compute" id=0 library=cpu variant=avx2 compute="" driver=0.0 name="" total="62.0 GiB" available="51.7 GiB"

### OS

Linux

### GPU

AMD

### CPU

AMD

### Ollama version

0.3.14
Repository: deno
Issue: Process exits before script is completed
Labels: bug,node compat

**Version:**
```
deno 2.0.6 (stable, release, aarch64-apple-darwin)
v8 12.9.202.13-rusty
typescript 5.6.2
```

**Reproduction:**

Create a file with the following contents:

```js
// node-runtime.js
import * as http from 'node:http';
http.createServer(async (request, response) => {
  response.write('Browser message');
  response.end();
  process.exit(0);
}).listen(5678);
```

... then run with Node (I'm using v20.18.0):

```bash
$ node node-runtime.js
```

.. and visit http://localhost:5678 in your browser. You should see a message:

> Browser message

.. and the script should complete in the terminal. 

Now make a new file:

```js
// deno-runtime.js
import * as http from 'node:http';
import { sleep } from "https://deno.land/x/sleep/mod.ts"
http.createServer(async (request, response) => {
  response.write('Browser message');
  response.end();
  await sleep(0.01);
  process.exit(0);
}).listen(5678);
```

... then run with Deno (version above):

```bash
$ deno --allow-net deno-runtime.js
```

.. and visit http://localhost:5678 in your browser. You should see the same message as Node. 

Now, comment out the `await sleep` statement and you will get an error in the browser that the server can't be connected to (ERR_CONNECTION_REFUSED in Chrome).
Repository: excalidraw
Issue: Support Power BI Embed Links
Labels: whitelist

Hi,

My company uses Power BI for reporting and analytics. It would be awesome to embed a Power BI report in one of my Whiteboards to help convey data in my Whiteboard presentations
Repository: flutter
Issue: `flutter doctor` should give more information about why it thinks Cocoapods is broken
Labels: c: new feature,tool,t: flutter doctor,c: proposal,P3,team-ios,triaged-ios

### Steps to reproduce

Setup your environment such that Cocoapods is broken according to `flutter doctor`.

### Actual results

Running `flutter doctor` will give a broad unhelpful message along the lines of:

> Warning: CocoaPods is installed but broken.
> For re-installation instructions, see <link>

The reason this message is unhelpful is, folks coming across this message likely already followed the Cocoapods installation step. But _something_ failed, whatever that is.

I fixed the problem, so I cannot give a clear example. But the other day, I had `pod` installed and working locally. `pod --version` was resolving correctly too. Yet `flutter doctor` considered it broken for some unknown reason.

It would be helpful to:

- show stdout/stderr of the `pod --version` internally used
- show `where pod`, if any
- suggest folks to run `where pod` in their terminal, to compare it with what Flutter is picking up (as some folks may not think about doing it)

This would give folks more information about the problem, outside of "try installing cocoapods again"
Repository: go
Issue: crypto/cipher: TestTagFailureOverwrite/POWER8 failures [consistent failure]
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/cipher" && test == "TestTagFailureOverwrite/POWER8"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8730882454928574929)):

    === RUN   TestTagFailureOverwrite/POWER8
        implementations.go:47: builder doesn't support CPU features needed to test this implementation
    --- FAIL: TestTagFailureOverwrite/POWER8 (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: [dynamo] Make dynamo own ExtraState rather than PyCodeObject
Labels: triaged,oncall: pt2,module: dynamo

Right now, `PyCodeObject`s own `ExtraState` (i.e. dynamo cache entries). Destruction of these `ExtraState`s is implemented in `destroy_extra_state`, implemented in extra_state.cpp, which is called by CPython. However, @anijain2305 has been running into segfaults involving owning `PyCodeObject`s being destroyed as `ExtraState` methods are being called. Thus, we should change ownership of `ExtraState` from `PyCodeObject` to Dynamo global state. This should also make managing memory for `ExtraState` easier since we can rely on C++ memory management instead of raw new/delete.

Source: https://github.com/pytorch/pytorch/pull/140821/files#r1847269744 

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: go
Issue: crypto/internal/fips/aes/gcm: TestAllocations failures [consistent failure]
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/internal/fips/aes/gcm" && test == "TestAllocations"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8730882754849246017)):

    === RUN   TestAllocations
        ctrkdf_test.go:31: expected zero allocations, got 4.0
    --- FAIL: TestAllocations (0.01s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: please add management for right click menu
Labels: Needs-Triage

### Description of the new feature / enhancement

please add management for right click menu

### Scenario when this would be used?

please add management for right click menu

### Supporting information

_No response_
Repository: deno
Issue: AbortSignals from Deno fetch do not work on Windows
Labels: bug,windows

Version: Deno 2.0.6

Hi there,
I'm trying to create a Hono server with a disconnect handler. When I cancel the request from my Postman client, the abort signal from the raw `Request` object never changes to true. This code works on both Node and Bun, so I think this is an issue with Deno's fetch API. See example below (requires Hono)

```ts
import { Hono } from 'hono'

const app = new Hono()

async function stall(stallTime = 3000) {
  await new Promise(resolve => setTimeout(resolve, stallTime));
}

app.get('/hello', async (c) => {

  // Should show up when hitting Cancel in Postman
  c.req.raw.signal.addEventListener("abort", () => {
    console.log("Aborted");
  })

  // Simulate a long-running task
  await stall(10000);
  return c.text("Hello from Hono!");
})

Deno.serve(app.fetch)
```
Repository: ui
Issue: [bug]: When the sidebar is collapsed to icon view, the collapsible menu cannot expand or show subItems.
Labels: bug

### Describe the bug

When the sidebar is collapsed to icon view, the collapsible menu cannot expand or show subItems.

### Affected component/components

Sidebar

### How to reproduce

1. Collapse the sidebar to icon size.
2. Click the menu icon in the collapsed state.
3. The CollapsibleContent does not appear.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
React, Next.js, Tailwind, Typescript
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: Scroll to find them every time.
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

KeyboardManager is great. I often change the functions of Hotkeys. However, it is a pain to have to scroll to find them every time.