sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: TypeScript colorizer confused by comments after colon in class member function signature with Generic return type
Labels: Bug,Help Wanted

### 🔎 Search Terms

color
comment
white
Promise
async
function
type
declaration


### 🕗 Version & Regression Information

- I was unable to test this on prior versions because no idea when this started

### ⏯ Playground Link

https://vscode.dev

### 💻 Code

```typescript
import os from 'os';

type Test<T> = T;

export class test {
  fine(): Test<void> {
    const test = 0;
  }
  ok(): /**/ Test<void> {
    const test = 0;
  }
  bad(): // any comment with a new line breaks colorizer for a function
  Test<void> {
    const test = 0;
    os.hostname();
    true ? false : undefined;
    throw new Error('');
    return;
  }
  fixed() // Not broken this way. Compare colorization with the bad function.
  : Test<void> {
    const test = 0;
    os.hostname();
    true ? false : undefined;
    throw new Error('');
    return;
  }
  alsoBad(): /* can be a /* comment too, but formatters usually remove the new line unless it is really long */
  Test<void> { // all but { colors are different
    const test = 0; // const is white
    os.hostname(); // all alpha is white
    true ? false : !!undefined; // true and false are different
    throw new Error(''); // throw is different, but not new or Error
    return; // return is different
  }
}

function ok(): // not broken outside of class
Test<void> {
  const test = 0;
}
```


### 🙁 Actual behavior

In the class functions that have comments after the `:` in the signature but before the actual Generic type, I noticed many differences from normal:
 - Type coloring is different
 - `const` is *white*
 - global variables are *white*
 - `true` and `false` are different in ternary
 - `throw` is different, but not `new` or `Error`
 - `return` is different

### 🙂 Expected behavior

Consistent colorizing, no matter the comments

### Additional information about the issue

Does not reproduce on GitHub or playground's colorizer.
Reproduces quickly and easily on [vscode.dev](https://vscode.dev).

I wasn't sure where to post this issue. It seem like a very TypeSript specific issue, but maybe this should be a [VS Code bug](https://github.com/microsoft/vscode/issues)...
Repository: godot
Issue: Godot Editor cutting off certain characters with vertical lines
Labels: bug,topic:editor,needs testing,topic:gui

### Tested versions

Reproduced in 4.2

### System information

Godot v4.2.2.stable.mono - Ubuntu 23.10 23.10 - Wayland - Vulkan (Forward+) - integrated Intel(R) HD Graphics 4400 (HSW GT2) () - Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (4 Threads)

### Issue description

Vertical lines in the script editor cuts off letters on that line (see image for example). I don't know why the lines are there (maybe preferred line length, like in Python?)

The vertical line seems to overwrite the lines of the letters. This only applies to small font sizes, where I assume the width of a vertical line is either smaller or equal to the width of a vertical line.
![image](https://github.com/godotengine/godot/assets/85976396/4e5a94c4-030a-4782-a37c-ede11de6a994)


### Steps to reproduce

Open a new text file, start typing until lines appear, zoom out until the vertical line cuts off letters.

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: [Advanced Paste] Option to hide AI Paste from Advanced Paste window
Labels: Idea-Enhancement,Cost-Small,Product-Advanced Paste

### Description of the new feature / enhancement

Add an option to not show the AI Paste function in the Advanced Paste window.

### Scenario when this would be used?

This would benefit people who don't wish to use the AI paste or don't have OpenAI credits and don't wish to buy them, but want to use the advanced paste.


### Supporting information

The AI Paste takes up quite a bit of room in the Advanced Paste window, and it can be annoying to look at if the user doesn't want to use the feature.
Repository: deno
Issue: handle signal 0 on windows as well on process.kill
Labels: feat,windows,runtime

linux fixed in https://github.com/denoland/deno/pull/23473

I thought in windows we should just ignore the signal, but I checked now libuv and they do special case this

https://github.com/libuv/libuv/blob/d9d207774ea1f734310982300e55dd64b3f5682b/src/win/process.c#L1191


Side note: is it a deliberate choice that process.kill now requires --allow-run permission ? isn't too much ?  @littledivy
Repository: rust
Issue: Enable `f16` and `f128` in assembly on platforms that support it
Labels: A-inline-assembly,T-compiler,E-medium,F-f16_and_f128

The below should work, but errors that f16 is not usable for registers:

```rust
#![feature(f16, f128)]

use core::arch::asm;

#[inline(never)]
pub fn f32_to_f16(a: f32) -> f16 {
    a as f16
}

#[inline(never)]
pub fn f32_to_f16_asm(a: f32) -> f16 {
    let ret: f16;
    unsafe {
        asm!(
                "fcvt    {ret:h}, {a:s}",
                a = in(vreg) a,
                ret = lateout(vreg) ret,
                options(nomem, nostack),
        );
    }

    ret
}
```

On aarch64 the first function generates:

```asm
example::f32_to_f16::hc897184dfb47f3d6:
        fcvt    h0, s0
        ret
```

`f16` types should be supported as a vreg on aarch64 in order to reproduce that code.

---

The following other platforms also apparently have some level of instruction support, but are less well documented:

- `arm-*`, `armv7-*`, `aarch64-*`, https://developer.arm.com/documentation/den0024/a/Porting-to-A64/Data-types
  - https://github.com/rust-lang/rust/pull/126555
  - https://github.com/rust-lang/rust/pull/127043
- PowerPC PowerISA apparently has a half-precision format according to section 7.3.2.1 https://files.openpower.foundation/s/dAYSdGzTfW4j2r2, but I can't get LLVM to emit any instructions for it. Per others, the VSX feature on PowerISA 3.1+ has conversion support for `f16`, and the SVP64 feature (which I can't find documented anywhere) adds full hardware support
- MIPS with the MSA extension...? https://s3-eu-west-1.amazonaws.com/downloads-mips/documents/MD00868-1D-MSA64-AFP-01.12.pdf section 3.1 says "16-bit floating-point storage format is supported through conversion instructions to/from 32-bit floating-point data.", I am unsure whether its vector registers have any special support
- riscv64gc with the Q extension: https://github.com/riscv/riscv-isa-manual/blob/riscv-isa-release-2023-05-23/src/q-st-ext.adoc
  - https://github.com/rust-lang/rust/pull/126530
- `x86` specifies an ABI for these types, and AVX512fp16 can use them
  - https://github.com/rust-lang/rust/pull/126417

Additionally, for `f128`:
- s390x supports `f128`, referred to as "BFP Extended Format" in https://publibfp.dhe.ibm.com/epubs/pdf/a227832c.pdf. I am not sure if this comes with any special instructions.
- PowerPC with `-Ctarget-cpu=pwr9` seems to have f128 support via instructions like `xsaddqp`

Tracking issue: https://github.com/rust-lang/rust/issues/116909
Repository: flutter
Issue: [Proposal] Add a convenience method to get the ScrollPhysics from the ScrollConfiguration
Labels: framework,f: scrolling,c: proposal,P3,team-framework,triaged-framework

### Use case

Developers wanting to grab the nearest `ScrollPhysics` have to reuse the same `BuildContext` twice to get the ScrollPhysics.

```
ScrollConfiguration.of(context).getScrollPhysics(context);
```

Since the second use is only for a lookup of the `platform`, we should be able to provide a convenience method instead.

Currently there is one such usage in the framework, in `scroll_behavior_test.dart`, but https://github.com/flutter/flutter/pull/148094 adds another usage.

For context, there are other methods that also require a `BuildContext` - such as `getPlatform(BuildContext)`, which has two usages like this currently - but I don't think that those are very common from a developer perspective?

### Proposal

Provide a convenience method `ScrollConfiguration.scrollPhysicsOf(BuildContext context)` to avoid the second use of the BuildContext. It would internally just reuse the context.
Repository: material-ui
Issue: [material-ui][Text Field] The label and helper text flicker and change color when another Text Field is focused
Labels: component: text field,package: material-ui,platform: windows

### Steps to reproduce

Link to live example with ThemeProvider: https://codesandbox.io/p/sandbox/bitter-grass-tmzqt7?file=%2Fsrc%2FDemo.tsx%3A11%2C31
Link to live example with CssProvider: https://codesandbox.io/p/sandbox/sleepy-booth-34yfhk?file=%2Fsrc%2FDemo.tsx 


### Current behavior

When working with multiple text fields, the label and helper text flicker while focusing on any text field, and some text fields' label and helper text remain darker than others. This issue is primarily visible in dark mode (this also happens in the light mode as well), which is why I provided an example in dark mode. I have reproduced this issue using both ThemeProvider and CssVarsProvider, and it occurs in both cases. Additionally, this problem occurs only on Windows OS and appears in all major web browsers, such as Chrome, Edge, and Opera, except for Firefox.

https://github.com/mui/material-ui/assets/121926499/cc94dd9b-2ff0-47e0-af06-f3e022a1ed69

### Expected behavior

The label and helper text should remain steady, without flickering or changing color.

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD 
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD  
  Browsers:
    Chrome: Not Found
    Edge: Chromium (120.0.2210.77)
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.24
    @mui/core-downloads-tracker:  5.14.18
    @mui/lab: 5.0.0-alpha.153 => 5.0.0-alpha.153
    @mui/material: ^5.14.18 => 5.14.18
    @mui/private-theming:  5.14.18
    @mui/styled-engine:  5.14.18
    @mui/system:  5.14.18
    @mui/types:  7.2.9
    @mui/utils:  5.14.18
    @types/react:  18.2.39
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ~5.3.2 => 5.3.2
```
</details>


**Search keywords**: Text field, Label, Helper text
Repository: ant-design
Issue: Ant Design Table: filterDropdown undefined, filters and filteredValue not working together
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/vitejs-vite-dg18zf?file=src%2FApp.tsx)

### Steps to reproduce

1. Apply filter on column "Check"
2. Re-open filter

### What is expected?

Filter should display selected option.

### What is actually happening?

I applied a filter on the column “Check” and it worked fine. However, when I re-open the filter, the selected option is not displayed. This only happens when `filterDropdown` is undefined and both `filters` and `filteredValue` fields are populated.

| Environment | Info |
| --- | --- |
| antd | 5.17.3 |
| React | 18.2.0 |
| System | MacOS |
| Browser | Chrome |

---
It is a layout bug only, not a functionality bug. If you comment the line with "filterDropdown: undefined" (line number 65 in the reproduction link), it works as expected.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Hidden lines affordance should take entire editor width, in inline diff mode
Labels: feature-request,diff-editor

Notice the `hidden lines` separators don't stretch all the way to the left:

<img width="822" alt="image" src="https://github.com/microsoft/vscode/assets/22350/c16e4f8a-5ede-4d33-a18a-527b967a4a38">
Repository: PowerToys
Issue: DLL Hijack
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.81.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

I have discovered DLL hijack issue on PowerToy. It's a minor issue and CVSS 4.0 score is 1.8. But I believe it's better to fix it.

wtsapi32.dll
WindowsCodecs.dll
AUDIOSES.DLL
WINSTA.dll
PROPSYS.dll
profapi.dll
edputil.dll
urlmon.dll
Wldp.dll

### ✔️ Expected Behavior

N/A

### ❌ Actual Behavior

N/A

### Other Software

N/A
Repository: next.js
Issue: Sourcemaps are not loaded in index pages with a dynamic route level deeper than one
Labels: bug

### Link to the code that reproduces this issue

https://github.com/albertodeago/next-sourcemaps-repro

### To Reproduce

Steps described also in the readme of the reproduction repo

Clone the reproduction repo and:

```bash
npm install
npm run build
npm run start
```

Open the app in the browser (`localhost:3000`), open the devtools and navigate through the pages.
Open (in the source panel) the sourcemaps relative to the `/content/[subject]/[method]/index.page.tsx` page, you will see that the sourcemaps are not there (chrome will show a 404 error).

<img width="897" alt="image" src="https://github.com/vercel/next.js/assets/6783279/7511aeb9-bd30-4749-a107-84cf50209870">

The chunk is actually generated by `next build` but seems like it's not picked up by the server (my guess)

This happens to all the `index.page.tsx` pages with a dynamic route (`[whatever]`) with a level deeper than 1 (so `/content/[subject]/index.page.tsx` has the sourcemaps visible in the browser).

Note that it doesn't happen in a page that has a name different than `index` (e.g. `/content/[subject]/[method]/named.page.tsx`)


### Current vs. Expected behavior

### Current behaviour

sourcemaps on `index` pages with a dynamic route level deeper than 1 are not loaded

### Expected behaviour

Any page sourcemap should be loaded in the browser

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 20.8.0
  npm: 10.1.0
  Yarn: 1.22.21
  pnpm: 8.8.0
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Not sure

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

next build (local), next start (local)

### Additional context

- I tested this in multiple browsers (safari, chrome and firefox (all latest versions))
- Tried with both `pageExtensions` and without it and seems to affect both
- I did not test it with app router because this affect an application I'm working on that cannot migrate to app router yet

- The bug seems to affect only `index` pages (not pages with a different name), as it's described in the reproduction repo
Repository: puppeteer
Issue: [Bug]: Redirection is not followed and directly breaks page and execution context
Labels: bug,confirmed,P3

### Minimal, reproducible example

```TypeScript
import * as Puppeteer from "puppeteer";

const browser = await Puppeteer.launch({
    ignoreHTTPSErrors: true,
    headless: false,
    devtools: true,
    waitForInitialPage: false,
});

const page = await browser.newPage();

await page.goto("https://digitalxtend.com", {
    waitUntil: "load",
});

const element = await page.$(".foo");

// Normally, goto() should follow the redirection from https://digitalxtend.com => https://digitalxtend.com/lander
// Instead we get
// Error: Execution context was destroyed, most likely because of a navigation.
```

We are using Docker with the Node runtime and puppeteer versions indicated below

### Error string

Error: Execution context was destroyed, most likely because of a navigation

### Bug behavior

- [X] Flaky
- [ ] PDF

### Background

Trying to load a simple website: https://digitalxtend.com
If we visit this website manually, we would notice a redirect to https://digitalxtend.com/lander

If we visit this website using `goto()`, normally it would follow the redirection, but in this case it doesn't and the execution context remains destroyed.

### Expectation

To visit open the page at the redirected URL and perform the ordinary operations on it using the Page API.

### Reality

The `goto()` method is not following the redirection and the execution context remains destroyed.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.9.0

### Node version

20.13.0

### Package manager

npm

### Package manager version

9.6.7

### Operating system

Linux
Repository: godot
Issue: `Condition "!tasks.has(p_task)" is true` error message after loading project
Labels: bug,topic:editor,needs testing

### Tested versions

- Reproducible in v4.3.dev6.mono.official [89850d553]

### System information

Godot v4.3.dev6.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (NVIDIA; 31.0.15.5212) - Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 Threads)

### Issue description

Sometimes I get this error after loading project:

![kuva](https://github.com/godotengine/godot/assets/49998025/355039bf-ee3d-4e69-af09-2601c55e6a5b)

```
Godot Engine v4.3.dev6.mono.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
--- Debug adapter server started ---
--- GDScript language server started on port 6005 ---
[LSP] Connection Taken
  Task 'update_scene_groups' already exists.
  editor/progress_dialog.cpp:215 - Condition "!tasks.has(p_task)" is true.
```

### Steps to reproduce

1. Start Godot 
2. Select project from project manager
3. Wait for the project to be loaded 
-> sometimes you get this error

Unfortunately I don't know how to reliable reproduce this error. It _feels_ like get I the error very often when starting Godot first time after booting the computer. I realoaded the project using `Project | Reload Current Project` about 20 times and restarted Godot about 10 times without getting the error. So my guess is that this bug happens only when loading the project takes too long. My quite old computer takes about 12 seconds to open the project.

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: mimatched type when using a `let` binding with the same name as a struct
Labels: A-diagnostics,T-compiler,C-bug,D-confusing,S-has-mcve

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
use std::marker::*;

fn main() {
    let PhantomData = ();
}
```

I expected to see this happen: success! Or at least a better diagnostic message.

Instead, this happened: failure:

```
error[E0308]: mismatched types
 --> src/main.rs:4:9
  |
4 |     let PhantomData = ();
  |         ^^^^^^^^^^^   -- this expression has type `()`
  |         |
  |         expected `()`, found `PhantomData<_>`
  |
  = note: expected unit type `()`
                found struct `std::marker::PhantomData<_>`
```

[Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=8f4662818cd1ca4aff1c63c9826c79e9)

### Meta

`rustc --version --verbose`:
```
rustc 1.80.0-nightly (791adf759 2024-05-21)
binary: rustc
commit-hash: 791adf759cc065316f054961875052d5bc03e16c
commit-date: 2024-05-21
host: x86_64-pc-windows-msvc
release: 1.80.0-nightly
LLVM version: 18.1.6
```
Repository: godot
Issue: Editor tries to open files from totally unrelated project
Labels: bug,topic:gdscript,topic:editor,confirmed

### Tested versions

- Reproducible in v4.3.dev6.mono.official [89850d553]


### System information

Godot v4.3.dev6.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (NVIDIA; 31.0.15.5212) - Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 Threads)

### Issue description

When opening a project, I get `Attempt to open script` errors where Godot tries to open files from other project. The project I opened in Godot is not the `c:/godot/mechtech` project that is shown in the error messages.

![kuva](https://github.com/godotengine/godot/assets/49998025/4d1e4b7f-37a6-41ff-a386-99c8e401416e)


```
Godot Engine v4.3.dev6.mono.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
--- Debug adapter server started ---
--- GDScript language server started on port 6005 ---
[LSP] Connection Taken
  Attempt to open script 'file://c:/godot/mechtech/mechs/mech_builder.gd' resulted in error 'Can't open file'.
  Attempt to open script 'file://c:/godot/mechtech/mechs/mech_builder.gd' resulted in error 'Can't open file'.
  ...
```

### Steps to reproduce

1. Open project A in vscode
2. Open some gdscript files of project A in vscode
3. Make sure that vscode tries to connect to Language Server (LSP)
4. Open project B in Godot 
-> Godot tries to open files belonging to project A

To reproduce the situation again, just restart vscode.

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: SVG with icons not updating after change
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-dwwset

### To Reproduce

1. Start application
2. Edit color of icon in `/public/icons.svg`


### Current vs. Expected behavior

Current behavior:

- Color remains same as before

Expected behavior:

- Color is changed

### Provide environment information

```bash
Windows 11
Chrome 125
nextjs: 13.5.1 - 14.2.3
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Image (next/image)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

I have disabled cache in browser (`Network/disable cache`). The only way to force update is to stop dev server, delete content of `.next` folder, and to start server again
Repository: angular
Issue: Performance regression in  js web frameworks benchmark
Labels: area: performance

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

We are seeing regression between those 2 runs:
* https://krausest.github.io/js-framework-benchmark/2024/table_chrome_123.0.6312.59.html
* https://krausest.github.io/js-framework-benchmark/2024/table_chrome_124.0.6367.91.html

The clear rows scenario seem to be particularly impacted.

Needs more investigation

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_