sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Suspense infinite fallback loading state with javascript turned off
Labels: Lazy Loading,Runtime

### Link to the code that reproduces this issue

https://github.com/vladshcherbin/suspense-infinite-loading

### To Reproduce

1. Start the app
2. From home page go to /recipes and see loading state and recipes list
3. Turn off javascript and do same thing (or reload the page)
4. See infinite loading state

- Check server logs to confirm data was fetched (logs output recipes number)
- Check page source to see data actually exists, hidden at the end

### Current vs. Expected behavior

**Current**

When javascript is turned off, suspense fallback state is infinite and never shows actual data. For the end user or search engine bot it results in an infinite loading state. Data is actually fetched on the server (can be seen in server logs) and exists hidden at the end of the page.

Screenshots:

<details>
 <summary>Infinite loading state</summary>

<img width="536" alt="image" src="https://github.com/user-attachments/assets/c8c344ec-6832-4b98-9668-85d7eff2bef3" />
</details>

<details>
 <summary>Server logs with data fetched</summary>

<img width="440" alt="image" src="https://github.com/user-attachments/assets/c4570848-3c84-4ed9-8ab8-87f3397a7296" />
</details>

<details>
 <summary>Actual data and hidden html tags</summary>

<img width="643" alt="image" src="https://github.com/user-attachments/assets/3051c2ce-7720-4f8c-b0c8-77f22c88080a" />
</details>

If `Suspense` is removed, data is shown to the end user but loading state is gone 🥲

**Expected**

Since data is actually fetched and exists on the page, it should be shown to the end user even with javascript turned off

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:45 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8112
  Available memory (MB): 8192
  Available CPU cores: 8
Binaries:
  Node: 22.10.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: 9.14.2
Relevant Packages:
  next: 15.1.0 // Latest available version is detected (15.1.0).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


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

Lazy Loading, Runtime

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

next dev (local), next start (local)

### Additional context

_No response_
Repository: svelte
Issue: onclick seems to not be working on web components
Labels: custom element

### Describe the bug

Using `onclick` on a web-component (ApplePay button, on this case) is not working. The handler function is not being called. If I change to Svelte's 4 `on:click` the handler function is called normally

As far as I understand the `apple-pay-button` web-component fires a click event

### Reproduction

https://github.com/GCastilho/svelte-5-onclick-bug-reproduction

(Note the usage of 'vite-plugin-mkcert' to use https on localhost. HTTPS is required for the ApplePay button to be displayed)

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 11 10.0.26100
    CPU: (8) x64 Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz
    Memory: 3.05 GB / 15.77 GB
  Binaries:
    Node: 20.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.7.0 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (131.0.2903.86)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    svelte: ^5.2.7 => 5.11.2
```


### Severity

blocking an upgrade
Repository: godot
Issue: SceneTreeTween not work properly when tween one axis with from()
Labels: bug,topic:animation

### Tested versions

Reproduce in Godot 3.5.3( Issue not exist in 4.x)

### System information

Windows10 Pro

### Issue description

When tween "One Axis" with SceneTreeTween with tween_property(self, "position:x").from(), tween looks different and clunky from tween both axis, or without from().

### Steps to reproduce

Create  a normal sprite and attach the script:[TweenAxis.zip](https://github.com/user-attachments/files/18127865/TweenAxis.zip)

`if _Tween:
		_Tween.kill()
	_Tween = create_tween()
	_Tween.set_ease(Tween.EASE_OUT).set_trans(Tween.TRANS_BACK)
	_Tween.tween_property($Sprite, "position:x", 300, 0.3).from(0)
	_Tween.play()`

### Minimal reproduction project (MRP)

[TweenAxis.zip](https://github.com/user-attachments/files/18127874/TweenAxis.zip)
Repository: go
Issue: x/website: anchor links don't show up if one hovers directly on a heading
Labels: help wanted,NeedsInvestigation,website

Splitting from https://github.com/golang/go/issues/68596#issuecomment-2402302152, which got ignored as it was a closed issue.

When I hover over ["Doc Links"](https://go.dev/doc/comment#doclinks), nothing happens - which is why I didn't even realise this got fixed earlier today. I have to move my cursor to the right of the heading - where the "reverse P" anchor symbol would be - for it to appear, as if I had to know ahead of time it would be there.

Can we make the anchor link show up whenever I hover over any of the heading area too? I think this is how anchor link hovers usually work on other websites, or at least that's how I intuitively think they work.

cc @hyangah @matttproud @cespare
Repository: go
Issue: cmd/compile: better error message for ambiguous parse
Labels: NeedsInvestigation,compiler/runtime,BadErrorMessage

### Go version

go version 1.23

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

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/smu/.cache/go-build'
GOENV='/home/smu/.config/go/env'
GOEXE=''
GOEXPERIMENT='fieldtrack,boringcrypto'
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/smu/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/smu/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/google-golang'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/google-golang/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23 [redacted] X:fieldtrack,boringcrypto'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/smu/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1689118444=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

I expected

```
if mErr := &MyError{}; errors.As(err1, &mErr) {
...
}
```

to be parse correctly. See https://go.dev/play/p/XHkampOkowJ for a reproduction case. 

Actual result of that playground snippet was:

./prog.go:23:10: syntax error: cannot use mErr := &MyError as value
./prog.go:26:1: syntax error: non-declaration statement outside function body

Changing the line

```
if mErr := &MyError{}; errors.As(err1, &mErr) {
```

into

```
if mErr := &(MyError{}); errors.As(err1, &mErr) {
```

or into 

```
mErr := &MyError{}
if errors.As(err1, &mErr) {
```

makes the code work, but I would expect the first variant to work just as well.

### What did you see happen?

./prog.go:23:10: syntax error: cannot use mErr := &MyError as value
./prog.go:26:1: syntax error: non-declaration statement outside function body

### What did you expect to see?

A compiled program
Repository: TypeScript
Issue: instantiation expression usage leading to an invalid d.ts file generation
Labels: Bug,Fix Available

### 🔎 Search Terms

partial function generic application, function generic variant from another function, instantiation-expressions

### 🕗 Version & Regression Information

- This changed between versions 5.6.2 and 5.7.2


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.2#code/C4TwDgpgBAyg9gWwgBQE50q0BpCIDOUAvFAEoQCGAJnAHYA2IAgqqhSADxoYRYi4gAfAChQkKE2AcmUCAA9gEWlULlqdRizacArrQDWtOAHdaggDRQAkrIVKVUWjoQAjXsUfO3qQR6YBtKwBdYWF5MDgsKAAzPQBjYABLOigECkTaAQBxHQpUKg5hKChsW0VlQlRKGgYQKH9uTBw8SwA6dvgkRt5mgiDzYUEACiKofTx8AC4SgYBKaY4AFTL7QjgXACsIBOHRgDcKeh0IacW54l8Do+hEwgBRBTYEpctyOMiCyQ5sSwAGCygekMJjMvgA3qMqsAdKhaFAlisKlB1lsdiNisUrsdTgNivMoFibvdHhRnmcyNsPtIpD8oP9LECjKZBL4iODRsUoTC4eMCP5fkEoBkCYdjqMAL7CSWicDQABicDgHjBMUVAEZpvhgKgMgBzSzRRUAJk12r1UElYmgACE8sqoC48hqoFqdbR9Q68iaXWb3RaZeIFXBbagPEGoAAfKAh4TvWhaz2oASEEj+ADkjtQarTlgzXrTgoohDjWrCcgiURLwCF+BDHjSGWyuXyQ0zydmHCDIZEoSAA

### 💻 Code

```ts
type SomePropertyKeys = ReadonlyArray<PropertyKey>
type At<A extends ReadonlyArray<unknown>, I extends number = number> = A[I]

export function mainKeyGuard<
  K extends readonly [PropertyKey, ...SomePropertyKeys],
>(
  keys: K,
): <T extends object>(
  value: T,
) => value is Extract<T, Record<At<K, 0>, unknown>> {
  return <T extends object>(
    value: T,
  ): value is Extract<T, Record<At<K, 0>, unknown>> => {
    return keys[0] in value
  }
}

type Foo = { foo1: string, foo2: string }
type Bar = { bar1: string, bar2: string }
type FooBar = Foo | Bar
const barKeys = ['bar1', 'bar2'] as const
export const isBar = mainKeyGuard(barKeys)<FooBar>
```


### 🙁 Actual behavior

Starting with the v5.7.2, the generated d.ts file declares `isBar` as a function which reference a missing generic type T, so an error is raised
```ts
export declare const isBar: (value: FooBar) => value is Extract<T, Record<At<K, 0>, unknown>>;
```

### 🙂 Expected behavior

I would expect the `isBar` function d.ts declaration to not reference a missing generic type T.
Previously, the generated d.ts file behaved like the following
```ts
export declare const isBar: (value: FooBar) => value is Bar;
```

### Additional information about the issue

The title mentions "instantiation expression" but I'm not totally sure about how the involved feature is actually named
Repository: react-native
Issue: Textinput Issue
Labels: Component: TextInput,Needs: Author Feedback,Needs: Repro

### Description

While typing in a TextInput, moving to the next line causes the top line of text to partially hide under the input area. It reappears only after typing a character, creating a poor UI/UX experience.

### Steps to reproduce

1. while typing

### React Native Version

0.76.5

### Affected Platforms

Runtime - Android, Runtime - iOS, Build - MacOS, Build - Windows

### Output of `npx react-native info`

```text
System:
  OS: Windows 11 10.0.22631
  CPU: "(8) x64 AMD Ryzen 3 5300U with Radeon Graphics         "
  Memory: 556.77 MB / 7.33 GB
Binaries:
  Node:
    version: 22.11.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 10.9.0
    path: ~\AppData\Roaming\npm\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 33.0.0
      - 34.0.0
      - 35.0.0
    Android NDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
IDEs:
  Android Studio: AI-241.18034.62.2411.12169540
  Visual Studio: Not Found
Languages:
  Java: javac 23
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.3
    wanted: ^15.1.3
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.5
    wanted: 0.76.5
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
none
```


### Reproducer

none

### Screenshots and Videos


https://github.com/user-attachments/assets/ddcc07a5-68e2-4dfd-b559-0e7d60b41bb8
Repository: kubernetes
Issue: DaemonsetSetStatus need CurrentRevision to tracking controllerrevision
Labels: kind/feature,sig/apps,needs-triage

### What would you like to be added?

DaemonsetSetStatus need CurrentRevision to tracking controllerrevision

### Why is this needed?

We need to track current controllerrevision for the daemonset like StatefulSetStatus does
<img width="380" alt="截屏2024-12-14 00 00 35" src="https://github.com/user-attachments/assets/cf43607d-ad3e-44fa-ab86-4f23f831dbe1" />
<img width="542" alt="截屏2024-12-14 00 10 51" src="https://github.com/user-attachments/assets/b5993e32-36ef-41f8-b36f-8967fa94d26b" />
Repository: neovim
Issue: `vim.diagnostic.config` does not apply options returned from functions
Labels: bug,diagnostic

### Problem

`:h vim.diagnostic.Opts` says


```
    Each of the configuration options below accepts one of the following:
    • `false`: Disable this feature
    • `true`: Enable this feature, use default settings.
    • `table`: Enable this feature with overrides. Use an empty table to use
      default values.
    • `function`: Function with signature (namespace, bufnr) that returns any
      of the above.
...
      • {float}?             (`boolean|vim.diagnostic.Opts.Float|fun(namespace: integer, bufnr:integer): vim.diagnostic.Opts.Float`)
                             Options for floating windows. See
                             |vim.diagnostic.Opts.Float|.
```

but

```lua
vim.diagnostic.config({
  float = {
    border = 'rounded',
    header = '',
    scope = 'cursor',
  },
})
```

and

```lua
vim.diagnostic.config({
  float = function (namespace, bufnr)
    return {
      border = 'rounded',
      header = '',
      scope = 'cursor',
    }
  end,
})
```

have totally different behaviors; the function version doesn't seem to do anything at all.


### Steps to reproduce

Add

```lua
vim.diagnostic.config({
  float = function (namespace, bufnr)
    return {
      border = 'rounded',
      header = '',
      scope = 'cursor',
    }
  end,
})
```

to your config and open a diagnostic floating window `vim.diagnostic.show_float()`



### Expected behavior

Should look the same as 

```lua
vim.diagnostic.config({
  float = {
    border = 'rounded',
    header = '',
    scope = 'cursor',
  },
})
```

### Nvim version (nvim -v)

 v0.10.2 

### Vim (not Nvim) behaves the same?

n/a

### Operating system/version

macOS 15.2

### Terminal name/version

Terminal.app

### $TERM environment variable

xterm-256color

### Installation

brew
Repository: TypeScript
Issue: Adding documentation comments to the return values of destructuring syntax
Labels: Suggestion,Awaiting More Feedback


Type: <b>Feature Request</b>

- In ReactJS, we often write code similar to `const [stateX, setStateX] = useState({ ... });`.
- I would like to hover over the variable name `stateX` with the mouse in other places where this variable is used to get an explanation similar to JSDoc (not for type, but to more clearly annotate the purpose of the variable).

- The reason I think this way is because the following approach often works:
```typescript
/** It's a ref for X */
const refX = useRef({ ... });
```
(When I hover over the `refX` variable in other places where it is accessed, the tooltip can display the documentation "It's a ref for X".)

- However, I have not found any way to annotate without disrupting the original code structure, so that VSCode can recognize my documentary comments for the tuple.
- I'm not sure whether this should be considered a feature request or a bug report.

VS Code version: Code 1.95.3 (Universal) (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Darwin arm64 22.3.0
Modes:


<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Include constant type properties in navtree
Labels: Suggestion,Awaiting More Feedback

TypeScript code: Intl. DisplayNames.supportedLocalesOf ();
SupportedLocalesOf Go to Definitions and view the outline:
One is vscode and the other is WebStorm.
![Image](https://github.com/user-attachments/assets/e2a166df-26ec-4716-b222-fc6f4c4de5aa)
![Image](https://github.com/user-attachments/assets/f2f9418c-cf57-4663-a6c1-df18c99303d5)

VScode does not have this outline item, WebStorm does
Repository: node
Issue: node:net blocklist upgrade 
Labels: feature request

### What is the problem this feature will solve?

the save of the blocklist into the disk to not have do reblock manualy 

### What is the feature you are proposing to solve the problem?

a parameter in the class named file who is the storage off the rules 

### What alternatives have you considered?

manualy create a loader
Repository: PowerToys
Issue: [QuickAccent] Missing ć for Slovenian
Labels: Issue-Bug,Status-In progress,Product-Quick Accent

### Microsoft PowerToys version

0.84.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Quick Accent

### Steps to reproduce

While Slovenian doesn't use ć in words, this letter is common in surnames. For QuickAccent to be fully complete for Slovenian, this letter is required.

How to reproduce: Set QuickAccent to Slovenian and press C + Space on the keyboard.

### ✔️ Expected Behavior

Both č and ć should show up in the list. In this order, since č is more common.

### ❌ Actual Behavior

Only č is displayed.

### Other Software

_No response_
Repository: pytorch
Issue: Define release branch creation readiness process
Labels: oncall: releng,triaged

### 🐛 Describe the bug

It feels like current process for creating release branch is based purely on the date, not on some state of release readiness.

In my opinion, it would be good to have a list of well defined criteria that must be made before release branch as created. Few of those:
 - CI for all HW/SW architectures important to release must be green
 - Binary builds for all respective architecture should complete and pass some basic smoke tests
 - (Optional, but was used in the past ) Branch base must be merged thru DiffTrain

### Versions

nightly?
Repository: storybook
Issue: [BUG] Environment Variables Undefined After Adding Storybook Packages to Next.js 14 + NX 19 Project
Labels: bug,needs triage

### Describe the bug

After adding any of the following Storybook packages (@storybook/nextjs, @storybook/react-webpack5, or @storybook/server-webpack5) to a Next.js 14 + NX 19 project, all environment variables become undefined after the build. The issue occurs even without implementing any Storybook-specific code. Changing the environment variable file from `.env.serve.local` to `.env` resolves the issue, but this is not a desirable solution since we need to use runtime environment variables with the serve prefix.

**Expected behavior:**
 The environment variables should be accessible in runtime (after the build) with the serve prefix, and the Storybook packages should not interfere with this configuration.

**Actual behavior:** 
When any of the mentioned Storybook packages are added to package.json, the environment variables become undefined after the build. This happens even if no code implementation for Storybook is added. Changing the file name from .env.serve.local to .env makes the variables accessible again, but this is not a desired solution since we need to inject environment variables during runtime, not at build time.

**Questions:**
How can I prevent Storybook packages from overwriting my existing environment variable configuration during build?

Is there a way to integrate Storybook with the existing runtime environment variable setup without causing issues with the build configuration?

### Reproduction link

-

### Reproduction steps

Steps to reproduce:

1) Set up a project using Next.js 14 and NX 19.

2) Configure environment variables in runtime (using `.env.serve.local` with a serve prefix as per [[NX's documentation]](https://nx.dev/recipes/tips-n-tricks/define-environment-variables)(https://nx.dev/recipes/tips-n-tricks/define-environment-variables)).
Only files with `serve` prefix, without original `.env file`

3) Add one of the following Storybook packages to package.json:
@storybook/nextjs
@storybook/react-webpack5
@storybook/server-webpack5

4) Build the application.

5) Run application using `serve:[appropriate prefix for the environment variable file]`

5) Observe that all environment variables are undefined in runtime

### System

```bash
OS: [e.g., macOS, Windows, Linux]
Node version: [e.g., 18.18.0]
Next.js version: 14.x
NX version: 19.x
```

### Additional context

1) The environment variables are correctly injected during runtime with the serve prefix (.env.serve.local).

2) The issue appears to stem from the configuration in the Storybook packages, which may be overriding the NX/webpack setup for environment variables.

3) We do not want to change the variable file naming convention to .env, as this would affect the runtime behavior.
Repository: pytorch
Issue: We should switch Tensor object (and other perf-critical objects) to use the new managed dict feature from CPython
Labels: triaged,actionable,module: python frontend

This should lead to small perf benefit, in particular for programs using a lot of these objects.
This will be because the dict creation will be lazy (so not initialized when not used) and it's access will be more efficient within the object.

This is done by passing Py_TPFLAGS_MANAGED_DICT when creating the class and making sure it is properly propagated to the python version of Tensor.

cc @msaroufim
Repository: flutter
Issue: Prepare to enable `explicit-package-dependencies`
Labels: P1,c: tech-debt,team-tool

This flag gates the new "label plugins as dev_dependencies" feature, as well as deprecates two old features:

- https://docs.flutter.dev/release/breaking-changes/flutter-generate-i10n-source
- https://docs.flutter.dev/release/breaking-changes/flutter-plugins-configuration

As of the time of this writing `flutter_tools/test/general.shard` has 100+ tests that fail with this flag enabled, mostly because they use `compute_dev_dependencies` transitively, and a fake `Pub` instance is not hooked up. I have yet to try the other test suites, but likely some fail in `commands.shard` and `integration.shard`.

Two options:

1. Opt failing tests out explicitly (turn off the feature), turn the feature on, work through failing tests
2. Fix failing tests before turning on the feature (opt-them in early)

Will chat with @bkonyi and @andrewkolos to figure out what they prefer.

My intuition is (2) leaves us in a better incremental state. Here is an example: https://github.com/flutter/flutter/pull/160258.

---

## TODOs

- [ ] Update `test/commands.shard/permeable/create_test.dart` (and `templates/skeleton`)
   Potentially also a bug in `lib/src/dart/generate_synthetic_packages.dart`
Repository: godot
Issue: Distant Shadow Splits have Wrong Bias
Labels: bug,topic:rendering,topic:3d

### Tested versions

since https://github.com/godotengine/godot/pull/68339

### System information

Vulkan

### Issue description

https://github.com/godotengine/godot/pull/48776 and https://github.com/godotengine/godot/pull/68339 Modify Blur and Bias respectively, but the latter adjusts bias based on the non modified blur value and doesn't take blur modification that the first PR is doing inside the shader.

The bias modification code should be applied to the modified - Final blur values, not the base blur.

### Steps to reproduce

Observe Distant Splits bias increase as blur levels increase, without blending splits, and observe how blur levels are the same for the splits, but the bias still increases for those distant splits

### Minimal reproduction project (MRP)

N/A