sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [feat]: Tracker Chart
Labels: area: request

### Feature description

How to build this type of chart?
<img width="577" alt="image" src="https://github.com/user-attachments/assets/af4d7690-7665-4201-a63c-76a9acd24518">


### Affected component/components

_No response_

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: TypeScript
Issue: Interface type coercion fails with unsatisfied properties in unions
Labels: Bug,Help Wanted

### 🔎 Search Terms

interface type coercion
type coercion
unsatisfied union constraints
property missing in but required
conditional interference


### 🕗 Version & Regression Information

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


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYOwLgpgTgZghgYwgAgILIN4Chm+QZ0gAcAuZARiwF8stRJZEUAhTHPQiU5AJmtvrR4SZMwD6AUQAeYZBBkQQAE3yi2eAsTJ8N8sFDj4yAIgBu0AJ7IEAexsAbY-yxgLRFAGViyALwVkAD68Lm4oAMI2IPgArgC20L5ogcgAFKxB4tJgAJQA3LS2UbIw0SAIiSnZZF5cvgB8yACycGAAFgB0Bso2sZXIDQAM7QCsyAD8vMhk5PmFhNaRMfFQFQDurS0Q5lBkEVFx0Nn1mMg0BYuynESJJWWV+VgA9I-IgKDkyKs2UADW+HQwKSuvh8fnIR2wGjmBygKQwmlqVGy1Dk9nwKAheChy1h8OuiOcz2QgBlyZDwYCorBY6A4oGIoA

### 💻 Code

```ts
interface A {
    step: 1
}

interface B {
    step: 2
}

interface B_Ext extends B {
    step: 2
    extras: "very cool"
}

type Step = 1 | 2
type Consumer = A | (B | B_Ext);

const func = (): Step => Math.random() > 0.5 ? 2 : 1;
const consumer = (whatever: Consumer) => { }


const step = func();

// ✅ works
if(step === 1) {
    consumer({ step })
} else {
    consumer({ step })
}

// ❌ fails
consumer({ step })
```


### 🙁 Actual behavior

The compiler expects that all properties of a sub-constituent be satisfied

### 🙂 Expected behavior

The union defines that it is either `A | B` and `B` might be `B` or `B & Extras`  

### Additional information about the issue

The same happens with types instead of interfaces as well as a the extras being passed as union of the type:

```ts
// causes the same issues
type A = { step: 1 }
type B = { step: 2 } & ({} | { extras: 'very good' })
```
Repository: node
Issue: node:events once isn't working as expected in node-redis tests
Labels: events

### Version

v18.19.1

### Platform

```text
Linux spotterT490 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun  7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```


### Subsystem

node:events

### What steps will reproduce the bug?

In node-redis we fire events (such as a connection being made to a server 'connect', the connection being ready 'ready', and the connection being shutdown, 'end') amongst others.  In practice, these are proxied to the user from an underlying object.

see - https://github.com/redis/node-redis/blob/949b944b0f01fa207980b5aa925590d7c32f6073/packages/client/lib/client/index.ts#L438-L464

We have a test to make sure these fires correctly, but that test is failing at the moment in a manner that we can't figure out (but can play around with to get to work, which makes us scratch our head even more)

test - https://github.com/redis/node-redis/blob/949b944b0f01fa207980b5aa925590d7c32f6073/packages/client/lib/client/index.spec.ts#L119-L133

If I rewrite the test to be 
```
    const p1 = once(client, 'connect');
    const p2 = once(client, 'ready');
    const p3 = once(client, 'end');

    await Promise.all([
      p1,
      p2,
      client.connect()
    ]);

    await Promise.all([
      p3,
      client.close()
    ]);
```

the test reliably passes as the once receives the 'end' event that it expects.  However, if I rewrite it to be 

```
    const p1 = once(client, 'connect');
    const p2 = once(client, 'ready');

    await Promise.all([
      p1,
      p2,
      client.connect()
    ]);

    const p3 = once(client, 'end');

    await Promise.all([
      p3,
      client.close()
    ]);
```

the test now reliably fails again.

In the code in index.ts (that I linked to above) where we listen and refire the events, for 'end' I stuck in a console.log to indicate that the event is being received, and it prints out as expected always, i just don't receive the 'end' event that should be fired unless the test is structured as noted above.

I'm very confused.

### How often does it reproduce? Is there a required condition?

always as noted

### What is the expected behavior? Why is that the expected behavior?

the promise that events.once() returns should be satisfied.

### What do you see instead?

event promise not being satisfied.

### Additional information

_No response_
Repository: tauri
Issue: [feat] [ios] native background color
Labels: type: feature request,platform: iOS

### Describe the problem

cant change native background color(native navbar color)
![image](https://github.com/user-attachments/assets/d723e289-41bd-4913-be3c-47b03ab858e5)


### Describe the solution you'd like

Provides a method to change native's background color in Rust

### Alternatives considered

Provides a method to change native's background color in Rust


### Additional context

_No response_
Repository: flutter
Issue: Builds on mac in prod are occasionally much slower than usual
Labels: team-infra,P2,triaged-infra

For example 

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/429218/infra <- ninja build 44 minutes on x64

vs

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/430933/overview <- 14 minutes on arm64

This is possibly only due to the arm64 machines being faster, but I also want to investigate whether we have to worry about thermal throttling on the intel machines.
Repository: pytorch
Issue: Loss of size-like ness when size-like expression is involved in expression that makes it smaller
Labels: triaged,module: dynamic shapes

### 🐛 Describe the bug

Internal xref: https://fb.workplace.com/groups/1075192433118967/posts/1486796491958557/

Repro:

```
import torch
import torch._dynamo

torch._dynamo.config.capture_scalar_outputs = True

@torch.compile(backend="eager", fullgraph=True)
def fn(x):
    u0, *_ = x.tolist()
    t = torch.empty(u0)
    return t[:-1] + t[1:]

fn(torch.tensor([3, 1]))
```

Fails with

```
torch._dynamo.exc.UserError: Tried to use data-dependent value in the subsequent computation. This can happen when we encounter unbounded dynamic value that is unknown during tracing time.  You will need to explicitly give hint to the compiler. Please take a look at torch._check OR torch._check_is_size APIs.  Could not guard on data-dependent expression Eq(u0 + 1, 0) (unhinted: Eq(u0 + 1, 0)).  (Size-like symbols: none)

Potential framework code culprit (scroll up for full backtrace):
  File "/data/users/ezyang/b/pytorch/torch/utils/_stats.py", line 21, in wrapper
    return fn(*args, **kwargs)

For more information, run with TORCH_LOGS="dynamic"
For extended logs when we create symbols, also add TORCHDYNAMO_EXTENDED_DEBUG_CREATE_SYMBOL="u0"
If you suspect the guard was triggered from C++, add TORCHDYNAMO_EXTENDED_DEBUG_CPP=1
For more debugging help, see https://docs.google.com/document/d/1HSuTTVvYH1pTew89Rtpeu84Ht3nQEFTYhAX3Ypa_xJs/edit?usp=sharing

User Stack (most recent call last):
  (snipped, see stack below for prefix)
  File "/data/users/ezyang/b/pytorch/a.py", line 9, in fn
    t = torch.empty(u0+1)

For C++ stack trace, run with TORCHDYNAMO_EXTENDED_DEBUG_CPP=1
For more information about this error, see: https://pytorch.org/docs/main/generated/exportdb/index.html#constrain-as-size-example

from user code:
   File "/data/users/ezyang/b/pytorch/a.py", line 9, in fn
    t = torch.empty(u0+1)
```

The problem is that although we give a VR [2, inf] when u0 is size like, when we subtract one from the expression, we end up with VR [1, inf], and so we no longer can conclude that the size is no longer equal to one.

In this particular example, you can work around it with a change of variables:

```
import torch
import torch._dynamo

torch._dynamo.config.capture_scalar_outputs = True

@torch.compile(backend="eager", fullgraph=True)
def fn(x):
    u0, *_ = (x - 1).tolist()
    torch._check_is_size(u0)
    t = torch.empty(u0 + 1)
    return t[:-1] + t[1:]

fn(torch.tensor([3, 1]))
```

But it's not obvious to me that this is always convenient to do.

### Versions

main

cc @penguinwu
Repository: vscode
Issue: ERROR: unable to resolve text model content for notebook cell output
Labels: bug,notebook-output

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No - Another error takes over preventing this:
![image](https://github.com/user-attachments/assets/9cfdd9b7-8151-48da-bc9a-e6c4c0365d25)


<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.92.2
- OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:

1. Run a Jupyter notebook cell with output spanning >500 outputs
2. Click on openLargeOutput link: _There are more than 500 outputs, show more (open the raw output data in a text editor)_ _command:workbench.action.openLargeOutput_
3. Watch the command fail with error
"The editor could not be opened due to an unexpected error: Unable to resolve text model content for resource vscode-notebook-cell-output:/xxxxxxx_redacted_xxxxxxx

Unfortunately, I am unable to run the insiders build as requested due to organizational constraints.   I see this bug should've been fixed "in the next release" per bug report ticket #189673, closed on Sep 6, 2023.  I seem to be unable to open Jupyter notebooks without enabling the Jupyter extension and so don't know how to test with all extensions disabled.
Repository: storybook
Issue: [Bug]: Storybook index crashes when directories match glob as stories
Labels: bug,sev:S3,portable stories

When running vitest tests where `test.browser.screenshotFailures` is set to true, upon test failures a screenshot is stored in a path like `src/components/__screenshots__/Button.stories.tsx/Primary.png`.

Because there is a directory named `Button.stories.tsx`, it causes Storybooks indexer to crash.

We should probably handle directories as not stories, or at least add `__screenshots__` as a default ignored path in the indexer.

More context: https://github.com/vitest-dev/vitest/issues/6239
Repository: PowerToys
Issue: 在浏览器地址栏等自动补全的位置应用快速重音时原字母不删除
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Quick Accent

### Steps to reproduce

1. 光标选定地址栏
2. 按下键盘按键不放，此时输入框显示该字母与选定状态下的自动补全，如g|<font style="background: blue">ithub.com</font>，其中 `|` 为光标
4. 按下 空格、左箭头或右箭头
5. 松开后，原有字符未删除

### ✔️ Expected Behavior

ğ

### ❌ Actual Behavior

gğ

### Other Software

Microsoft Edge 127.0.2651.105 (正式版本) (64 位)
Google Chrome 127.0.6533.120（正式版本） （64 位）
Repository: neovim
Issue: Terminal softwrapping
Labels: enhancement,terminal

### Problem

It is not possible to yank (`ggyG`, `"+yj`...) text from Neovim's terminal buffers without Neovim hard-wrapping lines that were longer than the terminal buffer's width.

### Expected behavior

Now that libvterm is vendored and that reflow is enabled, Neovim might have access to enough information to not hard-wrap yanked text?
Repository: TypeScript
Issue: Generic type narrowing for truthy check has inconsistent / incorrect behavior
Labels: Needs Investigation

### 🔎 Search Terms

generic truthy narrowing generic index

### 🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about narrowing truthy generic types


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.0-dev.20240821&ssl=29&ssc=2&pln=1&pc=1#code/MYewdgzgLgBATgU1HAJgLhgJSSVAeaOASzAHMAaGAVzAGswQB3MAPhgF4YBvAXwG4AsAChhAMxrAoRcDFEgQeACowEADygIwKCDEIlSMAD6yAhgBsICIzDBUzZlgAoAbuYyKAlN2ExfMIqIwLuZeXD5+Ea5mgkIREQD08QB6APzhcTAARiZwwWYeMRm+iMgoANpRALocMACshX48KhZWYbFFUelxialdPML9IkLiYJLSYLLyAEx5GHpk1qLmlta29qFdAUFRG+0ZUQ0ZPWl7cdm5O4dxJbjlVTX1fc0rbUUwnacJyScRg4NiEikMnOs10UGIZF2EUQUCocAmBwGQA

### 💻 Code

```ts
const record: Record<string, unknown> = {};

function foo<T extends string | false | null>(val: T) {
    if (val) {
        val;
        //^?
        bar(val);
        record[val] = 5;
    } else {
        val
        //^?
    }
}

function foo2(val: string | false | null) {
    if (val) {
        val;
        //^?
        bar(val);
        record[val] = 5;
    } else {
        val
        //^?
    }
}

function bar(val: string) {
    return val;
}
```


### 🙁 Actual behavior

Error on line 8, cannot use val to index object type with string key.
Val appears to be narrowed to `NonNullable<T>` yet I can use it as string when calling functions?
Note: `foo2` does not use generics and has more expected bahavior.

### 🙂 Expected behavior

`type Falsy = false | null | undefined | 0 | "";`
(might remove `0 | ""` from this because that gets into negated types... false seems like a common enough one to matter though)

On line 5 inside of the if check, I expect val to be narrowed to `Exclude<T, Falsy>` but instead, is incorrectly (imo) narrowed to `NonNullable<T>` which does not exclude false.

What is exceptionally strange, is that the type narrowing behavior seems to differ depending on how `val` is used. I can pass it to the function that takes a string parameter, but when I try to use it to index an object on line 8, I get an error.

### Additional information about the issue

This issue was discussed in detail by others more experienced than me in this typescript discord thread:
https://discord.com/channels/508357248330760243/1275942751724372110

Invite to server if you aren't a member:
https://discord.com/invite/typescript
Repository: pytorch
Issue: [CI] Binary Test Workflows are failing when updating triton hash
Labels: module: binaries,oncall: releng,triaged

### 🐛 Describe the bug

Example this PR: https://github.com/pytorch/pytorch/pull/133438
Comment: https://github.com/pytorch/pytorch/pull/133438#issuecomment-2304178969

Seeing errors like this during test:
```
2024-08-21T16:56:46.0878306Z ERROR: Could not find a version that satisfies the requirement pytorch-triton==3.0.0+55a4ab051c; platform_system == "Linux" and platform_machine == "x86_64" and python_version < "3.13" (from torch) (from versions: 2.0.0+0d7e753227, 2.0.0+3aa3d7024e, 2.0.0+af76c989eb, 2.0.0+b8b470bc59, 2.0.0+c8bfe3f548, 2.0.0+d54c04abe2, 2.1.0, 2.1.0+2c32f43999, 2.1.0+3c400e7818, 2.1.0+440fd1bf20, 2.1.0+46672772b4, 2.1.0+6e4932cda8, 2.1.0+7d1a95b046, 2.1.0+9820899b38, 2.1.0+9e3e10c5ed, 2.1.0+bcad9dabe1, 2.1.0+e6216047b8, 2.1.0+e650d3708b, 2.2.0+e28a256d71, 3.0.0+45fff310c8, 3.0.0+901819d2b6, 3.0.0+989adb9a29, 3.0.0+a9bc1a3647, 3.0.0+dedb7bdf33)
2024-08-21T16:56:46.1309596Z ERROR: No matching distribution found for pytorch-triton==3.0.0+55a4ab051c; platform_system == "Linux" and platform_machine == "x86_64" and python_version < "3.13"
```

We do build triton pytorch-triton==3.0.0+55a4ab051c however since we are on PR we are running upload step with dryrun ON. Hence these binaries are not uploaded to download.pytorch.org.  However build and test jobs builds pytorch with version+hash. During the test pip install is failing since these binaries can't be found on our index.

### Versions

2.5.0

cc @seemethere @malfet @osalpekar
Repository: godot
Issue: [Web] Bus volume ignored for `AudioStreamPolyphonic`
Labels: bug,platform:web,topic:audio

### Tested versions

4.4.dev [568589c]
4.2.3.dev [12ae52fd7d345330ec716ce5738cd67144a83c75]

### System information

Windows 11 - Chrome 127.0.6533.120 (Official Build) (64-bit)

### Issue description

`AudioStreamPolyphonic` does not update the volume from assigned bus (except from `Master`) once played, doesn't seem related to sampling as it happens in 4.2.3.dev, happens both with and without threads

Possibly related to:
* https://github.com/godotengine/godot/issues/95811
* https://github.com/godotengine/godot/issues/91605

But isn't related to the volumes of other options here but specifically the server itself

Works correctly on Windows

### Steps to reproduce

See MRP

### Minimal reproduction project (MRP)

[audio_mrp.zip](https://github.com/user-attachments/files/16714029/audio_mrp.zip)
Repository: flutter
Issue: Add a CupertinoCollapsible widget
Labels: c: new feature,framework,f: cupertino,P3,team-design,triaged-design

### Use case

A an animated "container" widget that can be expanded/collapsed similar to many native iOS apps.
Examples:

- iPadOS sidebar (#60762) (source: iOS 17 Music app)

https://github.com/user-attachments/assets/bccc61d2-5225-4b21-876d-986c2fac50a4

- "Show-on-load" list groups


- Calendar/Time inline widget (#63693) (source: iOS 17 Calendar app)

https://github.com/user-attachments/assets/ad463b2a-0ac8-47d4-8e7f-7714ce753b96


- Collapsible groups (source: iOS 17 Mail app)

https://github.com/user-attachments/assets/1f7427ee-1d14-4c61-9378-bedadaaaf9a3

### Proposal

I've already started working on it as a part of https://github.com/flutter/flutter/issues/60762 and I'm ready to open a PR to contribute this feature.

I suggest the name "collapsible" due to it being closer to native iOS SwiftUI nomenclature (https://developer.apple.com/documentation/swiftui/section/collapsible(_:))

The suggested API is very simple something along the lines of:

```dart
CupertinoCollapsibleContainer(
  collapsed: true,
  child: Text("Hello World!"),
),
```
Repository: transformers
Issue: clarify the label shifting behavior of llama models when `labels` is given.
Labels: Feature request

### Feature request

i believe `labels` in the training of causal LMs means the value to predict at time `n`, i.e., the next token. in other words, i'd assume, if `labels` is given, it should be already shifted by one in the data loader w.r.t. the `input_ids`.


however, in `LlamaForCausalLM.forward()`, i found the labels are always shifted, silently.

https://github.com/huggingface/transformers/blob/f1d822ba337499d429f832855622b97d90ac1406/src/transformers/models/llama/modeling_llama.py#L1205-L1210

```python

        Args:
            labels (`torch.LongTensor` of shape `(batch_size, sequence_length)`, *optional*):
                Labels for computing the masked language modeling loss. Indices should either be in `[0, ...,
                config.vocab_size]` or -100 (see `input_ids` docstring). Tokens with indices set to `-100` are ignored
                (masked), the loss is only computed for the tokens with labels in `[0, ..., config.vocab_size]`.

```

...

```python


        if labels is not None:
            # Shift so that tokens < n predict n
            shift_logits = logits[..., :-1, :].contiguous()
            shift_labels = labels[..., 1:].contiguous()
            # Flatten the tokens
            loss_fct = CrossEntropyLoss()
            shift_logits = shift_logits.view(-1, self.config.vocab_size)
            shift_labels = shift_labels.view(-1)
            # Enable model parallelism
            shift_labels = shift_labels.to(shift_logits.device)
            loss = loss_fct(shift_logits, shift_labels)

```

i found it quite unexpected hence calling it "silently". as this is for a causal LM, shouldn't it be not shifting the labels by default? in modeling GPT2, this is at least documented explicitly.

https://github.com/huggingface/transformers/blob/f1d822ba337499d429f832855622b97d90ac1406/src/transformers/models/gpt2/modeling_gpt2.py#L1309-1314

in gemma2, it has the same behavior and no explicit mentioning in the docstring.

https://github.com/huggingface/transformers/blob/f1d822ba337499d429f832855622b97d90ac1406/src/transformers/models/gemma2/modeling_gemma2.py#L978-L982

i think at least we should force the docstring to mention this, if making a change is too dangerous at this point. 

### Motivation

i didn't expect this behavior and used my data loader, which does the shifting already, as i believe that is what `labels` should mean. as a result, i ended up finetuning a model to predict the next next token, which outputted gibberish.



### Your contribution

- hopefully leaving this issue helps communication across users
- i can make a one line change in the docstring.
- not sure how exactly, but if this potential misunderstanding could be checked, it'd be great. technically, we can check if the labels are already shifted. though i don't know where is the best place for this.
Repository: terminal
Issue: enable Intel CET
Labels: Product-Meta,Issue-Task,Area-CodeHealth

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

Compile Windows Terminal with `/guard:ehcont` and link with `/guard:ehcont /cetcompat`
<!-- 
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)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: rust
Issue: [CODE IMPROVEMENT] handle `doc(hidden)` differently in rustdoc
Labels: C-cleanup,T-rustdoc

Currently, the handle of `doc(hidden)` in rustdoc is very complex and needs to go through multiple strip passes which are all very fine-tuned, making the whole very fragile and difficult to keep up with.

Instead of these passes, we could instead check whether or not an item is doc hidden directly when rendering them. With a top-down approach, if an item is `doc(hidden)`, none of its children will be rendered either.

Gonna give it a try in the few weeks to see how much of it is actually doable.