sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Modifying a static variable in a extended script modifies the parent script static variable instead
Labels: discussion,topic:gdscript

### Tested versions

- Reproducible since 4.1-dev2

### System information

Godot v4.3.dev2 - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 SUPER (NVIDIA; 31.0.15.4617) - Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 Threads)

### Issue description

The way static variables are handled in GDScript differ from other programming languages, where they're not inherited to children GDScript classes. Instead, the parent class controls the static variables of all children.

### Steps to reproduce

The MRP has the following structure:

**Parent.gd**
```
class_name Parent
extends Node

static var PROPERTY_1 : int
static var PROPERTY_2 : String
```

**Child1.gd**
```
class_name Child1
extends Parent

static func _static_init():
	PROPERTY_1 = 10
	PROPERTY_2 = "Child1"
```

**Child2.gd**
```
class_name Child2
extends Parent

static func _static_init():
	PROPERTY_1 = 5
	PROPERTY_2 = "Child2"
```


**Main.gd**
```
extends Node2D

func _ready():
	print(Child1.PROPERTY_1)
	print(Child1.PROPERTY_2)
	
	print(Child2.PROPERTY_1)
	print(Child2.PROPERTY_2)
```

Main.gd is included in the main scene.
The assumption goes that the result in the console would look like this
```
10
Child1
5
Child2
```
But instead it prints the following.
```
5
Child2
5
Child2
```


### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/godotengine/godot/files/14068840/MRP.zip)
Repository: material-ui
Issue: [material-ui][docs] Revise Transfer List docs
Labels: docs,package: material-ui,component: transfer list,support: docs-feedback

### Related page

https://mui.com/material-ui/react-transfer-list/

### Kind of issue

Other

### Issue description

Every other entry on the sidebar of the docs iterates and presents a component that may be used directly from Material UI. Meanwhile, transfer list is more a demo of something that could hypothetically be built if required, more suiting a how-to or placed within one of its constituent components.

Therefore, I suggest the Transfer List page is removed.

### Context

Ideally, the documentation, when browsed, should immediately demonstrate the direct functionality of React MUI.

### Decision

After the discussion below, and with https://github.com/mui/material-ui/issues/27579#issuecomment-894700501 in mind, the decision was to keep the Transfer List doc in its current place but revise it to add more details and context about how this isn't documented in the Material Design specs. It is a solid example of what's possible with Material UI composition.

We'll repurpose this issue for this work.

_This decision section was edited by @DiegoAndai_

**Search keywords**: Transfer List, shuttle
Repository: go
Issue: cmd/trace: analyze Go 1.22+ traces scalably
Labels: NeedsInvestigation,FeatureRequest,compiler/runtime

Currently cmd/trace loads the entire expanded trace into memory, always. However, the Go 1.22+ trace API is a streaming API, so it's totally possible for the tool to split up traces and only touch the necessary parts.

This will require some refactoring, and will definitely be easier once we remove the old tracer and the old tracer parser (putting old trace parsing behind the new API in internal/trace/v2).
Repository: pytorch
Issue: Increase default bucket_cap_mb value to from 25MB to a more optimal value
Labels: oncall: distributed,triaged

### 🚀 The feature, motivation and pitch

Context: https://github.com/pytorch/pytorch/issues/117748

All-reduce comms are used in DDP's backward pass and by default the bucket size is set to 25MB via bucket_cap_mb. Documentation about this can be found here: https://github.com/pytorch/pytorch/blob/main/benchmarks/distributed/ddp/README.md?plain=1#L160

Default 25mb bucket size is very small and most users would have to increase it. Hence this feature request to find and set more optimal default value for general usage.

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @ptrblck @malfet @roywei @chrisG

### Alternatives

_No response_

### Additional context

_No response_
Repository: flutter
Issue: [material] Simplify building responsive layouts based on window size classes.
Labels: c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design

### Use case

When building modern applications, making them responsive is essential. It would be great if there would be an easy way to build different layouts based on the [window size class](https://m3.material.io/foundations/layout/applying-layout/window-size-classes#2bb70e22-d09b-4b73-9c9f-9ef60311ccc8).

This could also be a foundation for issues like #142310.

### Proposal

In `material`, there should be an enum `WindowSizeClass` that represents the different [window size classes](https://m3.material.io/foundations/layout/applying-layout/window-size-classes#2bb70e22-d09b-4b73-9c9f-9ef60311ccc8). Additionally, there should be a `StatelessWidget` called `ResponsiveBuilder`, that uses its `ResponsiveWidgetBuilder` to build the child based on the current `WindowSizeClass`.

Since "window size classes" are a part of Material 3, this should not be done in a new package.
Repository: next.js
Issue: Metadata exported from `app/not-found` is not applied to 404 pages returned from dynamic paths
Labels: bug

### Link to the code that reproduces this issue

https://github.com/dstaley/not-found-metadata

### To Reproduce

1. `next dev`
2. Go to `http://localhost:3000/post/invalid-slug`

### Current vs. Expected behavior

Expected Result:
The `title` property from `metadata` in `app/not-found.tsx` is applied, and there is a `<title>` element present in the DOM.

Current Result:
The `<title>` element is removed from the DOM, causing the title to fallback to the URL of the page.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.19.0
  npm: 10.2.5
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.14 // Latest available version is detected (14.1.1-canary.14).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

App Router, Metadata (metadata, generateMetadata, next/head)

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

next dev (local), Vercel (Deployed)

### Additional context

This issue only appears on routes with dynamic segments. For example, `http://localhost:3000/route-that-doesnt-exist` correctly displays a title. Furthermore, the initial HTML response from the server correctly contains the `<title>` element, but it's removed when the DOM is hydrated.
Repository: svelte
Issue: Spreads props does not work on <svelte:window />
Labels: feature request

### Describe the bug

```svelte
<script>
	let count = $state(0);

	function increment() {
		count += 1;
	}

	const listeners = {
		onclick: increment,
	}
</script>

<svelte:window {...listeners} />

clicks: {count}
```
When running code above, window click handler should be set, instead nothing happens.

In fact no code is generated at all so this either work or should be marked as an error.

### Reproduction

[Reproduction](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE0WO0WrDMAxFf0WIPbQspNurlwz2Hc0eiqOAmCMHS2kZxv8-nLTro3TvOdyMEwdSdOeMcpkJHX4tCzZov0s99ErBCBvUuCZfP536xIt9DjJYIAMfVzHo4UXtYnR4O34MUrNpFW8cBVh8opnEDkfINRlsZ157eK9lKzvho6hBYDUSSgr9ox7FB_Y_7qlq7lh3eq6Rbh_rbixjvEFu2_ZfVuC0dTaROsjbhIINznHkiWlEZ2ml8l3-AE6V_K8TAQAA)

### Logs

_No response_

### System Info

```shell
"svelte": "5.0.0-next.40",
```


### Severity

annoyance
Repository: vscode
Issue: No merge conflict codelenses in vscode.dev
Labels: bug,merge-conflict

I ended up with a merge conflict in release notes on vscode.dev, but I don't see any codelenses to resolve the merge conflicts. I see them on stable but not insiders

![image](https://github.com/microsoft/vscode/assets/323878/8df7d32a-5f2e-41b2-853f-7c5f8b3e41bf)
Repository: node
Issue: Missing `Http2ServerResponse.setHeaders()`
Labels: feature request,http2

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

Make it possible to use `response.setHeaders()` on both old HTTP response objects and ones coming from `node:http2`.

BTW I wasn't sure if this should be a "feature request" or a "bug."

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

Add the method `http2.Http2ServerResponse.setHeaders()` to have the same API as `http.OutgoingMessage.setHeaders()`.

See <https://nodejs.org/api/http.html#outgoingmessagesetheadersheaders>.

### What alternatives have you considered?

* Avoiding using `setHeaders()` at all.
* Monkey-patching `Http2ServerResponse`.
* Just writing two versions of my own set-headers code, on the assumption that, when available, `setHeaders()` is the most efficient option.
Repository: ollama
Issue: Add LLaVAR model
Labels: model request

Please add the LLaVAR model (from https://llavar.github.io/) to ollama. The model is based on llava and offers enhanced text recognition abilities, which seems like a great addition to the current range of ollama models.
Repository: next.js
Issue: Vercel Logging Broken on app router
Labels: bug

### Link to the code that reproduces this issue

https://github.com/iFixit/react-commerce/pull/2221

### To Reproduce

Migrating a route from the pages router to the app router seems to break the way Vercel parses / interprets `console.log()` logging output.

### Current vs. Expected behavior

Expected Behavior: all log lines for a request are grouped under one request. This is what we see for the pages router:
![image](https://github.com/vercel/next.js/assets/26855/0ae1aaaa-280f-4e5c-8a92-1bbc596a8e1c)

Current Behavior: After migrating a route to use the app router, all log lines are treated as individual and separate requests. This breaks all logging integrations and makes logs rather useless.
![image](https://github.com/vercel/next.js/assets/26855/d1c39415-67b8-4c4c-ae63-92503c0d71cf)


### Provide environment information

```
Next: 13.4.12 deployed on vercel
```

### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

I'm not sure if the fault lies with next.js, vercel, or some error in their integration.
Repository: pytorch
Issue: DISABLED test_inductor_all_reduce_single (__main__.C10DFunctionalNativeTest)
Labels: module: rocm,triaged,skipped

Platforms: rocm

Probably same as https://github.com/pytorch/pytorch/issues/118403

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22distributed%2Ftest_c10d_functional_native.py%3A%3AC10DFunctionalNativeTest%3A%3Atest_inductor_all_reduce_single%22%5D)).

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: rust
Issue: rustdoc "Aliased Type" view is wrong
Labels: T-rustdoc,C-discussion,A-rustdoc-ui

![screenshot_2024-01-27_01:56:48](https://github.com/rust-lang/rust/assets/96552222/b659d0ab-1901-4fc8-8c5f-855767fe6008)

In this rustdoc output, rustdoc seems to claim that `MatrixView` aliases a `struct MatrixView`.

This is wrong, since no such `struct` exists. It seems like there was some sort of mistake when implementing this feature that ended up using the wrong name there? It should say `Matrix` instead.
Repository: ant-design
Issue: table开启虚拟列表以后summary无效了
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://codepen.io/mldpxnef-the-sasster/pen/wvOPjKM?editors=001](https://codepen.io/mldpxnef-the-sasster/pen/wvOPjKM?editors=001)

### Steps to reproduce

上面的virtual注掉summary就会显示出来，开启就不会显示

### What is expected?

支持合计显示，我看文档上写着的支持，为什么没显示呢？https://github.com/ant-design/ant-design/discussions/41500

### What is actually happening?

没显示合计

| Environment | Info |
| --- | --- |
| antd | 5.10.3 |
| React | 18 |
| System | win10 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: youtube-dl
Issue: Fatal error messages should remind me about 429 errors.
Labels: request

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description
I put too much effort into trying to report what seemed to be a bug, only to then discover in the log that there was a "HTTP Error 429: Too Many Requests" earlier. Can we make it so that any non-fatal 429 sets a kind of "tainted" flag and have all subsequent fatal errors start their message with something like "This might be caused by an earlier error: HTTP Error 429: Too Many Requests –"? That way I'd instantly see I can ignore the "please report this bug" part.
Repository: deno
Issue: Non-ISO 8601 calendars don’t work as expected in Temporal
Labels: upstream,temporal

Version: Deno 1.40.0

## TLDR

```
$ deno --unstable-temporal
> Temporal.Now.zonedDateTime("hebrew").year; // should return 5784
2024
> Temporal.Now.zonedDateTime("hebrew").calendarId; // should not be empty
undefined
```

---

[Temporal’s proposal](https://tc39.es/proposal-temporal/docs/zoneddatetime.html) includes this example:


```
dt = Temporal.ZonedDateTime.from('2019-02-23T03:24:30.000003500[Europe/Rome][u-ca=hebrew]');
dt.year;        // => 5779
dt.month;       // => 6
dt.monthCode;   // => 'M05L'
dt.day;         // => 18
dt.hour;        // => 3
dt.minute;      // => 24
dt.second;      // => 30
dt.millisecond; // => 0
dt.microsecond; // => 3
dt.nanosecond;  // => 500
```

Trying the same in Deno ignores calendar:

```
dt = Temporal.ZonedDateTime.from('2019-02-23T03:24:30.000003500[Europe/Rome][u-ca=hebrew]');
dt.year;        // => 2019
dt.month;       // => 2
…
```

I tried different methods of setting calendar for a `ZonedDateTime`, like `Temporal.Now.zonedDateTime("persian")` and `obj.withCalendar("persian")` with different calendars (Persian, Chinese, Hebrew, Islamic) and all give the same result, which is using ISO 8601 instead of the specified calendar.
Repository: youtube-dl
Issue: Can we help webmasters of piped/invidious instances display their message of the day?
Labels: question

## Checklist

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

For some alternative frontends like piped/invidious, we currently just transform it to the original site's extractor (YouTube in this case). That's a good approach. Nonetheless, I'd like a way for those webmasters to still convey their message of the day, often a request for funding. What would be a good way to do that? Should we just check for an HTML element with `class="ytdl-motd"` and try to display its text in a console-appropriate way above the download progress? Is there a more standardized way for labeling such kinds of messages? (For maximum compatibility with other kinds of alternative frontends.)

Or maybe we should check for a potential text file like `/meta/motd.txt`? That way webmasters could craft a message specific to console clients, potentially even specific to the user agent. In case of HTTP 404 the reply could be much shorter and cheaper to render server-side, than the usual HTML page.
Repository: angular
Issue: Enhance @defer views for responsive design
Labels: feature,area: core,core: defer

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

**Problem :**
1. Current @defer views load or defer code uniformly across all device sizes.
2. This can lead to unnecessary code loading, potentially impacting performance and user experience, specifically for devices with limited resources and bandwidth.

### Proposed solution

**Proposal :**

Introduce device-specific conditions within @defer blocks to selectively load code based on screen size.

**Syntax examples :**

HTML
```
@defer(on mobile) {
   }

@defer(on tablet) {
   }

@defer(on desktop) {
   }

```
**Benefits :**

1. Optimized initial load: Load only the essential code for the user's device, reducing initial bundle size and improving load time.
2. Enhanced user experience: Tailored content and functionality for different screen sizes, delivering a more seamless experience across devices.
3. Improved performance: Reduced memory usage and potential network overhead, contributing to smoother interactions.
4. Code organization: Separation of concerns for different screen sizes, leading to cleaner and more maintainable code.

**Implementation :**

1. Extend the @defer directive to accept a device type as a parameter.
2. Integrate with Angular's existing responsive design mechanisms (e.g., MediaMatcher) to determine device size.
3. Lazily load deferred code only when the corresponding condition is met.


**It should be designed in a way that initial page load and content display are not affected by screen size checks, and it should work seamlessly with server-side rendering.**

### Alternatives considered

If anyone has an alternative approach, please mention it.
Repository: terminal
Issue: "Close this terminal with Ctrl+D, press Enter to restart, OR CTRL+SHIFT+ENTER TO RESTART AS ADMIN."
Labels: Issue-Feature,Needs-Triage,Needs-Attention,Needs-Tag-Fix

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
When `closeOnExit: "never"`, exiting a Terminal process outputs the message, "You can now close this terminal with Ctrl+D, or press Enter to restart." This enhancement is to suggest expanding this functionality with the self-explanatory, "or press Ctrl+Shift+Enter to restart as Administrator."

One example where this would be very helpful is when a user runs unelevated a CLI program, batch file, etc. that requires elevation to perform properly. This currently returns "Access is denied." and the user has to go relaunch the program with deliberate elevation (for example, by right-clicking the program shortcut and clicking "Run as administrator"). Instead, I propose that the user could simply press Ctrl+Shift+Enter to re-run the same command/program *with* elevation.

For a long time in Windows, users have been able to Ctrl+Shift+click on a batch file or shortcut to launch it elevated, or press Ctrl+Shift+Enter to run a command with elevation from the Win+R Run dialog. It would be consistent and intuitive UX to provide users a similar keyboard combination to elevate the command from within Terminal itself.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)
I imagine this would involve something along the lines of replacing the current Terminal process/tab with one that is elevated to Administrator privileges but otherwise identical, and re-running the initial command that called it (if any). 

Ideally it would also pass along any variables and such from the exited process. In this way, it would function similar to [gsudo](https://github.com/gerardog/gsudo). (This bit, while more complex to implement, could partially address #146 as well.)
<!-- 
A clear and concise description of what you want to happen.
-->
Repository: material-ui
Issue: [material-ui][Tabs] Ensure consistent TypeScript type for the `value` prop across all tab-related components
Labels: breaking change,component: tabs,typescript,package: material-ui

### Current behavior

The `value` type varies inconsistently across tab-related components.

### Expected behavior

For consistency, the `value` type should universally be `string | number` for all tab-related components. However, for the Tabs component specifically, it should accept `string | number | null`.

### Context

Refer to [this comment](https://github.com/mui/material-ui/issues/40630#issuecomment-1908200670) in issue #40630.


**Search keywords**: tab, value prop
Repository: rust
Issue: Incorrect types shown in an error when using `rhai`
Labels: A-diagnostics,T-compiler

### Code

```Rust
use std::{cell::RefCell, rc::Rc};

struct Wrapper {
    // this part is important - if this field is commented out, error disappears
    engine: rhai::Engine,
    // this is what actually triggers the diagnostic
    ctx: Rc<RefCell<()>>,
}

fn main() {
    let _ = Wrapper {
        engine: rhai::Engine::new_raw(),
        ctx: (),
    };
}
```


### Current output

```Shell
error[E0308]: mismatched types
  --> src/main.rs:13:14
   |
13 |         ctx: (),
   |              ^^ expected `Shared<Locked<()>>`, found `()`
   |
   = note: expected struct `Rc<Locked<()>>`
           found unit type `()`
```


### Desired output

```Shell
error[E0308]: mismatched types
  --> src/main.rs:13:14
   |
13 |         ctx: (),
   |              ^^ expected `Rc<RefCell<()>>`, found `()`
   |
   = note: expected struct `Rc<RefCell<()>>`
           found unit type `()`
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.75.0 (82e1608df 2023-12-21)
binary: rustc
commit-hash: 82e1608dfa6e0b5569232559e3d385fea5a93112
commit-date: 2023-12-21
host: x86_64-unknown-linux-gnu
release: 1.75.0
LLVM version: 17.0.6
```


### Anything else?

_No response_
Repository: angular
Issue: Allow specifying "equal" function for signal based inputs.
Labels: area: core,core: inputs / outputs,cross-cutting: signals

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Currently we have a lodash deep equals on our signals that are bound to an input setter like

```typescript
 _message = signal({} as Message, { equal: isEqual });
@Input({ required: true }) set message(value: Message) {
  this._message.set(value);
}
```
We could not find a way to do the same with a signal based input.

### Proposed solution

Allow setting an equal function on signal based inputs.

### Alternatives considered

Maybe we are getting this whole thing wrong?