sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Cache tags are not respected if the route previously threw `notFound()`
Labels: examples

### Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/j893gh

### To Reproduce

1. Create a page route that fetches some data using either a fetch or unstable cache. The route should return a 404 response or 200 based on the response from the fetch or unstable cache data..
2. Provide a way to invalidate the cache tag such as an api route and a button to call the route.
3. Run next server
4. Observe the 404 not-found page
5. attempt to invalidate the cache tag
6. observe the page does not re-generate.

### Current vs. Expected behavior

When using either a fetch with cache tags or the unstable_cache with cache tags, those cache tags can not be invalidated if the page eventually throws a `notFound()` function.

For example:
let's say the system is fetching from a CMS to gather page data. If the page in the CMS doesn't exist, it's expected to throw 404 response using the `notFound()`. This works as expected using appropriate logic.

Then if that page is later created in the CMS, the CMS should trigger the NextJS to invalidate the cache tag. But using `revalidateTags()` does not have any effect.

The alternative is to use `revalidatePath()`, but that would have cascading effects by invalidating more data than necessary such as fetch data in the layout. This then causes more ISR than is necessary just to get a 404 to resolve correctly.

Expected Behavior:

Regenerate the route if the cache tag for that route is invalidated.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 15.0.4-canary.4 // Latest available version is detected (15.0.4-canary.4).
  eslint-config-next: 14.2.1
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```

### Which area(s) are affected? (Select all that apply)
Output (export/standalone)

### Which stage(s) are affected? (Select all that apply)
next start (local), Vercel (Deployed)

### Additional context
Verified on the caranary release.
Repository: rust
Issue: `extern "x86-interrupt" fn` allows absurd signatures
Labels: A-LLVM,O-x86_64,T-compiler,C-bug,A-ABI,O-x86_32,F-abi_x86_interrupt,A-hardware-interrupts

I tried this code:

```rust
#![feature(abi_x86_interrupt)]
extern "x86-interrupt" fn three_args(_a: u8, _b: u8, _c: u8) {}

fn main() {
    three_args(1, 2, 3);
}
```

I expected to see rustc reject this code, because this signature makes no sense for this ABI.

Instead, this happened:
> rustc-LLVM ERROR: unsupported x86 interrupt prototype
> error: could not compile `playground` (bin "playground")

## Meta

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (a0d98ff0e 2024-10-31)
binary: rustc
commit-hash: a0d98ff0e5b6e1f2c63fd26f68484792621b235c
commit-date: 2024-10-31
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```

@rustbot label: +F-abi_x86_interrupt +A-LLVM +O-x86_64 +O-x86_32 +A-ABI +T-compiler

### Related Issues
- https://github.com/rust-lang/rust/issues/40180
- https://github.com/rust-lang/rust/issues/63018
- https://github.com/rust-lang/rust/issues/126418
- https://github.com/rust-lang/rust/issues/132834
Repository: rust
Issue: Directly calling `extern "riscv-interrupt-{m,s}" fn`... compiles?
Labels: A-LLVM,T-compiler,C-bug,O-riscv,O-AVR,A-ABI,A-hardware-interrupts

I tried this code with `rustc --target riscv64gc-unknown-linux-gnu rust_code.rs`:

```rust
#![feature(abi_riscv_interrupt)]
pub extern "riscv-interrupt-m" fn interrupt_machine() {}

pub extern "riscv-interrupt-s" fn interrupt_supervisor() {}

pub fn main() {
    interrupt_machine();
    interrupt_supervisor();
}
```

I expected to see this happen: rustc *or LLVM* reject the direct call.

Instead, this happened:

...wait, why does it compile? This doesn't seem like it should compile...

## Meta

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (a0d98ff0e 2024-10-31)
binary: rustc
commit-hash: a0d98ff0e5b6e1f2c63fd26f68484792621b235c
commit-date: 2024-10-31
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.
```

@rustbot label: +A-hardware-interrupts +A-LLVM +O-riscv +A-ABI +T-compiler

### Related Issues
- https://github.com/rust-lang/rust/issues/111889
- https://github.com/rust-lang/rust/issues/132834
Repository: rust
Issue: Most `extern "*-interrupt-*" fn` should enforce 0-sized signatures
Labels: A-LLVM,T-compiler,C-bug,O-riscv,O-AVR,A-ABI,O-msp430,A-hardware-interrupts

I tried this code with `rustc --target riscv64gc-unknown-linux-gnu rust_code.rs`:

```rust
#![feature(abi_riscv_interrupt)]
pub extern "riscv-interrupt-m" fn interrupt_machine(_a: u8, _b: u8, _c: u8) {
}

pub extern "riscv-interrupt-s" fn interrupt_supervisor(_a: u8, _b: u8, _c: u8) {
}

pub fn main() {
    interrupt_machine(1, 2, 3);
    interrupt_supervisor(4, 5, 6);
}
```

I expected to see rustc catch this invalid signature.

Instead, this happened:
> rustc-LLVM ERROR: Functions with the interrupt attribute cannot have arguments!

My understanding is that the same story applies for non-x86 interrupt ABIs like MSP430's.

## Meta

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (a0d98ff0e 2024-10-31)
binary: rustc
commit-hash: a0d98ff0e5b6e1f2c63fd26f68484792621b235c
commit-date: 2024-10-31
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```

@rustbot label: +A-hardware-interrupts +A-LLVM +O-riscv +O-msp430 +A-ABI +T-compiler

### Related Issues
- https://github.com/rust-lang/rust/issues/38487
- https://github.com/rust-lang/rust/issues/111889
- https://github.com/rust-lang/rust/issues/132835
- https://github.com/rust-lang/rust/issues/132836
Repository: rust
Issue: Directly calling `"msp430-interrupt" fn` should also be invalid
Labels: A-LLVM,T-compiler,C-bug,A-ABI,O-msp430,A-hardware-interrupts

I tried this code:

```rust
#![feature(abi_msp430_interrupt)]

pub extern "msp430-interrupt" fn msp430_isr() {}

pub fn call() {
    msp430_isr();
}
```

I expected to see rustc reject the erroneous code somewhere before final LLVM lowering, because the notion of "calling" an interrupt still seems nonsensical to me, no matter what its signature is.

Instead, this happened:
> rustc-LLVM ERROR: ISRs cannot be called directly

## Meta

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (a0d98ff0e 2024-10-31)
binary: rustc
commit-hash: a0d98ff0e5b6e1f2c63fd26f68484792621b235c
commit-date: 2024-10-31
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```

@rustbot label: +A-hardware-interrupts +A-LLVM +O-msp430 +A-ABI +T-compiler

### Related Issues
- https://github.com/rust-lang/rust/issues/38487
- https://github.com/rust-lang/rust/issues/132834
- https://github.com/rust-lang/rust/issues/132836
Repository: svelte
Issue: `oncanplay` event called after video element is removed
Labels: bug

### Describe the bug

When a video element is removed in svelte 4 the `on:canplay` event handler isn't called, however in svelte 5 (with and without runes) the event is called. In firefox it also causes the video to continue playing in the background, because `e.currentTarget.play()` is called in the event handler.

### Reproduction

https://svelte.dev/playground/d901783aed2c4df68c14459b90b3f47f?version=4.2.19
https://svelte.dev/playground/698042a4c231415fa69892808ac7a247?version=5.1.13

### Logs

_No response_

### System Info

```shell
Firefox 132.0.1
```


### Severity

annoyance
Repository: PowerToys
Issue: 视频文件缩略图预览，和psd文件预览
Labels: Needs-Triage

### Description of the new feature / enhancement

视频文件缩略图预览，和psd文件预览

### Scenario when this would be used?

视频文件缩略图预览，和psd文件预览

### Supporting information

_No response_
Repository: rust
Issue: All interrupt ABIs should enforce either `()` or `!` as return types
Labels: A-LLVM,O-x86_64,T-compiler,C-bug,O-riscv,A-ABI,O-msp430,O-x86_32,F-abi_x86_interrupt,A-hardware-interrupts

I tried this code: [Godbolt](https://godbolt.org/z/75xfedEa9)

I expected to see this happen: ...interrupts don't really return things, they're side effects, that's kind of in the definition, so these shouldn't return anything, and the ABI should enforce that, or during lowering..?

Instead, this happened:
> rustc-LLVM ERROR: ISRs cannot return any value
> rustc-LLVM ERROR: Functions with the interrupt attribute must have void return type!
> rustc-LLVM ERROR: X86 interrupts may not return any value


## msp430

```rust
#![feature(abi_msp430_interrupt)]

pub extern "msp430-interrupt" fn msp430_isr() -> u64 {
    9001u64
}

pub fn call() {
    let _ = msp430_isr();
}
```

## riscv

```rust
#![feature(abi_riscv_interrupt)]
pub extern "riscv-interrupt-m" fn interrupt_machine() -> u64 {
    9001u64
}

pub extern "riscv-interrupt-s" fn interrupt_supervisor() -> u64 {
    9002u64
}

pub fn main() {
    let a = interrupt_machine();
    let b = interrupt_supervisor();
    println!("{}", a + b);
}
```

## x86

```rust
#![feature(abi_x86_interrupt)]
pub extern "x86-interrupt" fn interrupt_machine() -> u64 {
    9001u64
}


pub fn main() {
    let a = interrupt_machine();
    println!("{}", a);
}
```

## Meta

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (a0d98ff0e 2024-10-31)
binary: rustc
commit-hash: a0d98ff0e5b6e1f2c63fd26f68484792621b235c
commit-date: 2024-10-31
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```

@rustbot label: +A-ABI +A-hardware-interrupts +A-LLVM  +F-abi_x86_interrupt  +O-x86_64 +O-x86_32 +O-riscv +O-msp430 +T-compiler

### Related Issues
- https://github.com/rust-lang/rust/issues/38487
- https://github.com/rust-lang/rust/issues/40180
- https://github.com/rust-lang/rust/issues/111889
- https://github.com/rust-lang/rust/issues/132835
- https://github.com/rust-lang/rust/issues/132836
- https://github.com/rust-lang/rust/issues/132837
- https://github.com/rust-lang/rust/issues/132839
Repository: svelte
Issue: Missing type in Svelte compiler AST
Labels: types / typescript

### Describe the bug

The script part of AST specifically imports are missing `importKind` type

### Reproduction

  ```ts
import { parse } from 'svelte/compiler';
  
const ast = parse(`
  <script lang="ts">
    import type { Snippet } from 'svelte'
    import { mount } from 'svelte'
  </script>
`, { modern: true })

// narrow down type to import declarations
if (ast.instance?.content.body[0].type === 'ImportDeclaration') {
    // this gives error // Property 'importKind' does not exist on type 'ImportDeclaration'.
    ast.instance?.content.body[0].importKind
    
    // But if we log it we can see it dose have them
    console.log(ast.instance?.content.body[0].importKind) // type
    console.log(ast.instance?.content.body[1].importKind) // value
}
  ```

### Logs

_No response_

### System Info

```shell
Not important
```


### Severity

annoyance
Repository: vscode
Issue: Strcky scroll cannot support multi line declaration in C.
Labels: feature-request,editor-sticky-scroll


Type: <b>Bug</b>

void test(u8 a,
          u8 b,
          u8 c,
          u8 d)
{
/**
 * @brief 
 * 
 * 
 */
}

VS Code version: Code 1.95.2 (Universal) (e8653663e8840adaf45af01eab5c627a5af81807, 2024-11-07T11:07:22.054Z)
OS version: Darwin arm64 23.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M2 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<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>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|1, 1, 1|
|Memory (System)|16.00GB (0.39GB free)|
|Process Argv|--crash-reporter-id 958beaca-28e6-46a8-afa8-aed297dcf1f7|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (23)</summary>

Extension|Author (truncated)|Version
---|---|---
language-x86-64-assembly|13x|3.1.4
doxdocgen|csc|1.4.0
githistory|don|0.6.20
gitlens|eam|15.6.3
comment-translate|int|3.0.0
cortex-debug|mar|1.12.1
asm-code-lens|maz|2.6.1
debug-tracker-vscode|mcu|0.0.15
memory-view|mcu|0.0.25
peripheral-viewer|mcu|1.4.6
rtos-views|mcu|0.0.7
git-graph|mhu|1.30.0
cpptools|ms-|1.22.11
hexeditor|ms-|1.11.1
makefile-tools|ms-|0.11.13
vscode-serial-monitor|ms-|0.13.1
color-highlight|nau|2.8.0
phind|phi|0.25.4
excalidraw-editor|pom|3.7.4
highlight-words|rsb|0.1.4
markdown-preview-enhanced|shd|0.8.15
open-in-browser|tec|2.0.0
vscode-conventional-commits|viv|1.26.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
h409b430:31177055

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: `RenderingServer.material_set_param` doesn't work with texture based objects
Labels: enhancement,discussion,topic:rendering

### Tested versions

- Reproducible in master, 4.4 dev 4, 4.3 stable

### System information

Godot v4.4.dev4 - Windows 10.0.19045 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated AMD Radeon RX 580 2048SP (Advanced Micro Devices, Inc.; 31.0.21921.1000) - AMD Ryzen 5 3600 6-Core Processor (12 threads)

### Issue description

As [this question](https://forum.godotengine.org/t/using-renderingserver-material-set-param-to-set-sampler2d-parameter-not-working/85165)  in Godot forum shows, `RenderingServer.material_set_param` don't allow to set sampler uniforms with a texture object, which diverges from `Material.set_shader_parameter` that works normally with textures as parameter. That happens because `RenderingServer.material_set_param` rejects any `Object` as value:

https://github.com/godotengine/godot/blob/e65a23762b36b564eb94672031f37fdadba72333/servers/rendering/renderer_rd/storage_rd/material_storage.cpp#L2223-L2232

### Steps to reproduce

1. Create a shader with an uniform variable of type Sampler2D and assign this shader to a node
2. Load any image (the Godot icon as example)
3. Try to set the shader uniform variable using `RenderingServer.material_set_param` and the loaded image
4. Godot will fail with error:  `Condition "p_value.get_type() == Variant::OBJECT" is true.`

Or play the MRP below.


### Minimal reproduction project (MRP)

[test-uniform-set-with-rendering-server.zip](https://github.com/user-attachments/files/17691279/test-uniform-set-with-rendering-server.zip)
Repository: godot
Issue: C# Reference in a Inherited Scene breaks (Null or Disposed)
Labels: bug,topic:dotnet

### Tested versions

- Reproducable in 4.3stable, 4.4dev4

### System information

Windows10

### Issue description

I have following Nodes:
- ActorBase : Node2D
- ActorFarmer: Actor
- and some Child Components

I create a Scene where the base node is an "ActorBase". I reference this in child nodes.
I create a Inherited Scene from the "ActorBase" Scene. Instead of the ActorBase Script I add an "ActorFarmer".
All references are still present in the Editor when I click the revert Button. When I start the game the Reference to the Actor is null or disposed.
When I dont set the reference in the Base Scene and directly in the Inherited Scene, I dont get the issue.


https://github.com/user-attachments/assets/488dff6b-308c-4fb2-838c-ae4c3a119ede

### Steps to reproduce

1. Create a Base Class
2. Add References to other Nodes
3. Inherit from the Base Class
4. Create a Base Scene
5. Drag the references to the Base Class
6. Create a Inherited Scene from the Base Scene

### Minimal reproduction project (MRP)

When you run the MRP, you can run on the remote tab. Then click for example on AnimationPlayer2d, then you get an ObjectDisposed Exception.
![image](https://github.com/user-attachments/assets/e156aa5f-f31f-4dfb-88be-c5ada3cb8a35)
[InheritanceBug.zip](https://github.com/user-attachments/files/17691283/InheritanceBug.zip)
Repository: PowerToys
Issue: PowerRename Utility
Labels: Needs-Triage

### Description of the new feature / enhancement

I have tried the feature and it's great! however it only maxes at 20 files. Can you make the maximum number higher like 999 or unlimited?

### Scenario when this would be used?

A lot of users handles lots of files that need renaming especially documents, music or video files, and many of us rename files by the thousands. I personally use a third party app for that but if it's already included in powertoys, accessible via context menu, it will make our renaming easier

### Supporting information

_No response_
Repository: TypeScript
Issue: "Referenced projects must have the new composite setting enabled" does not hold true
Labels: Docs

### 🔎 Search Terms

composite, project references, solution-style tsconfig

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about tsconfig.

### ⏯ Playground Link

https://vite.new/react-ts

### 💻 Code

The above link is a project created from the vite react-ts template (https://vite.new/react-ts).
It uses project references in `tsconfig.json`, but no `composite: true` specified in both `tsconfig.app.json` and `tsconfig.node.json`.

On the other hand, the [TypeScript handbook](https://www.typescriptlang.org/docs/handbook/project-references.html#composite) says:
> Referenced projects must have the new [composite](https://www.typescriptlang.org/tsconfig#composite) setting enabled.

### 🙁 Actual behavior

The project builds (`npm run build`) successfully without `composite: true`.

### 🙂 Expected behavior

If I understand correctly, the documentation means I have to specify `composite: true` when using `references`. I'd expect an error or warning if I didn't follow the guide.

### Additional information about the issue

I'm curious whether it's a bug or a feature.
If it's a bug, what's the expected behavior?
If it's a feature, I'd like to see the documentation updated accordingly.
Repository: material-ui
Issue: [joy-ui][docs] The `overlay` property of the `Skeleton` component doesn't seem to have any effect
Labels: on hold,support: docs-feedback

### Related page

https://mui.com/joy-ui/api/skeleton/

### Kind of issue

Other

### Issue description

Hi! I'm writing a React component library that styles Joy UI components the Tailwind CSS way.

I recently implemented a Skeleton component, and while writing the API documentation and reviewing it again, I found that the `overlay` property has no effect on the style of the Skeleton.

The API documentation says that when `overlay` is `true`, the position of the Skeleton becomes `absolute`, but it seems that the style is currently applied by setting the `variant` property to `overlay`.

Did they miss removing the `overlay` property during the Joy UI patching process?

### Context

_No response_

**Search keywords**: skeleton, overlay
Repository: godot
Issue: Long variable names are an issue in animation player
Labels: topic:editor,usability,topic:animation

### Tested versions

4.3-stable

### System information

Windows10

### Issue description

Due to the animation player positioning in the interface and general UX construction, anmating parameters that have long names can be challenging.

The names of the parameters aren't always under the control of the user: for example instance shader parameter have the whole `instance_shader_parameters/` prefix.

![image](https://github.com/user-attachments/assets/847bc1fe-565b-45b0-85b3-34ef78983fcf)
![image](https://github.com/user-attachments/assets/b4248bae-2dd2-421b-8961-548776220676)

Please consider showing the end of the parameter name rather than the start when needing to wrap the text.

### Steps to reproduce

- open project
- open "node3d scene"
- select animation player
- observe the amoutn of space taken by instance shader parameters

### Minimal reproduction project (MRP)

[mrp-instance-anim-param.zip](https://github.com/user-attachments/files/17691652/mrp-instance-anim-param.zip)
Repository: react
Issue: [React 19]Inquiry About React 19 Support for ReactPress
Labels: React 19

Certainly! Here's the updated version of the issue with the link to the ReactPress repository included:

---

**Title**: Inquiry About React 19 Support for ReactPress

**Body**:

Hello ReactPress Team,

I hope this message finds you well. I am currently evaluating [ReactPress](https://github.com/fecommunity/reactpress) for a project and have a question regarding its compatibility with future versions of React. Specifically, I would like to know if there are any plans or ongoing efforts to ensure that ReactPress supports React 19.

React 19 introduces several new features and improvements that could potentially benefit ReactPress. As such, I am keen to understand if the team is already working on integrating these changes or if there are any known issues that might prevent ReactPress from running smoothly on React 19.

Here are a few specific questions I have:

1. Is ReactPress currently compatible with React 19?
2. If not, are there any plans to update ReactPress to support React 19 in the future?
3. Are there any known issues or limitations that users should be aware of if they try to use ReactPress with React 19?

I appreciate your time and effort in maintaining this wonderful project. Thank you for any information you can provide regarding this matter.

Best regards,

fecommunity
Repository: ollama
Issue: install.sh should not touch the system
Labels: bug

### What is the issue?

I was horrified to see the install script attempt to install kernel headers and nvidia drivers and other GUI shit (xorg) on my headless server. It is not okay for an APPLICATION to touch the system in any way, especially doing this kind of invasive operations. This has to be opt-in - at least remove the -y from the package manager lines, seriously, not even a confirmation from the user?!

### OS

Linux

### GPU

Other

### CPU

AMD

### Ollama version

latest