sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: InlineCompletion selectedSuggestInfo context enrichment
Labels: feature-request,inline-completions

# Problem statement

TLDR: Having the snippetText exposed allows for deeper understanding of where the users cursor would land, allowing for more precise (and conditioned) inline completions. (with no completions added before the cursor position).

Currently the InlineCompletion context provides a limited view over the selectedSuggestInfo context (provides only parsed text and range of replacement). This makes it hard for the inline completion providers to better understand where the users cursor will end after accepting the suggest completion in case its a snippet text.

E.g. suggest completion `foo()` and suggest completion `foo($0)` may show totally different behavior when retrieving & applying the current completion. In current case (when `foo($0)` is used) the `foo()` as a whole would be used as a prefix to code completion models without additional extension side guessing (or none of the text would be used as prefix potentionally completing also between the `foo` & `()`), when instead the completion models might want to only complete from the cursor position, allowing to insert the arguments after `foo(` (e.g. `bar, baz)`).

# Solution

With the current selectedSuggestInfo, pass in optional semanticText, which would be provided inside context to the `provideInlineCompletions()` so that downstream providers can have tighter control over the inline completion.

(The extension of the selectedSuggestInfo could be added to the current vscode.proposed.inlineCompletionsAdditions.d.ts)
Happy to add the change, if agreed on.
Repository: vscode
Issue: Can't sign in to settings sync with GitHub if using non-default profile and `--user-data-dir`
Labels: bug,github-authentication

<!-- ⚠️⚠️ 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

<!-- 🪓 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.88.0 (system setup) x64
- OS Version: Windows 11 Enterprise, 23H2, 22631.3296

Steps to Reproduce:

1. Create a new user data dir `%APPDATA%\Code - Personal`
   * Default is `%APPDATA%\Code`.
3. Start VSCode from CMD with `code --user-data-dir "%APPDATA%\Code - Personal"`
4. Try to sign in to settings sync with GitHub account.
   * Web browser opens.
   * You sign in.
   * After successfully signing in a new VSCode windows using default profile and default data path opens.
5. Result: You can't sign in to settings sync with GitHub if using non-default profile with non-default data path.

Observation: Settings sync with Microsoft account works though.

Related feature request:

* #209810
Repository: pytorch
Issue: torch.onnx.errors.UnsupportedOperatorError: Exporting the operator 'quantized::linear_dynamic' to ONNX opset version 17 is not supported. Please feel free to request support or submit a pull request on PyTorch GitHub: https://github.com/pytorch/pytorch/issues
Labels: module: onnx,low priority,triaged,OSS contribution wanted

### 🚀 The feature, motivation and pitch

I am trying to convert quantized Pytorch model to onnx. However, the operator 'quantized::linear_dynamic' is no supported.

### Alternatives

_No response_

### Additional context

_No response_
Repository: PowerToys
Issue: Random exceptions and screen blackouts
Labels: Issue-Bug,Needs-Repro

### Microsoft PowerToys version

0.80.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Unfortunately, I cannot reproduce the issue.  It just happens randomly.   All of my screens go black for about 5 or so seconds and then upon returning, I get a message box with an error.

The first time it happened, there message box error was a low-level exception from `Spotify`. The exception was coming from Windows.  `Spotify` did not restart or shut down.  I did not get the error message for the first occurrence of the issue.

The second time, it was the same thing about 5 minutes later but the error message was `dotnet.exe`.  The error message box was the same as the dotnet error as it was for the `Spotify` one.  

Error Message:
![image](https://github.com/microsoft/PowerToys/assets/85414302/1a411563-8459-4d56-a336-27db6f0da43f)

The first time I got the error message, I did not think it was PowerToys so I thought it was a `Spotify` issue.  But the same behavior happened 5 minutes later but with `dotnet.exe` instead.  The second time though, a powertoys was displayed with error information but this did not show the first time.  I am assuming at this point based on what I saw, that they were both 
a power toys issue.


Here is the bug report:
[PowerToysReport_2024-04-08-11-44-24.zip](https://github.com/microsoft/PowerToys/files/14904535/PowerToysReport_2024-04-08-11-44-24.zip)


### ✔️ Expected Behavior

1. No exceptions to be thrown.
2. No screen blackout

### ❌ Actual Behavior

1. Screens blacked out
2. Exception/message box was shown.

### Other Software

_No response_
Repository: deno
Issue: SIGTRAP with --unstable-temporal
Labels: bug,upstream

deno 1.42.1 (release, x86_64-unknown-linux-gnu)

```js
function dateToCalendars(year, month, day, op = {}) {
  const fromCalendar = op.from ?? "gregory";
  const toCalendar = op.calendar ?? fromCalendar;
  const date = Temporal.PlainDate.from({
    year,
    month,
    day,
    calendar: fromCalendar,
  })
    .withCalendar(toCalendar);
  return date.toLocaleString(op.locale ?? "en", {
    ...op,
    calendar: toCalendar,
  });
}

dateToCalendars(2024, 4, 8);
```

```
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7ffc074c93b0
==== C stack trace ===============================

    deno(+0x2a55fc3) [0x557e7615afc3]
    deno(+0x2a5547b) [0x557e7615a47b]
    deno(+0x2a5104f) [0x557e7615604f]
    deno(+0x2eeff4f) [0x557e765f4f4f]
    deno(+0x2b04bc1) [0x557e76209bc1]
    deno(+0x3d0bb36) [0x557e77410b36]
fish: Job 1, 'deno run --unstable-temporal a.…' terminated by signal SIGTRAP (Trace or breakpoint trap)
```
Repository: angular
Issue: Build visualize  not working as mentioned in Doc
Labels: P4,area: docs

### Describe the problem that you experienced

Angular Build Stats Json 

### Enter the URL of the topic with the problem

https://angular.io/cli/build

### Describe what you were looking for in the documentation

![image](https://github.com/angular/angular/assets/29145245/74662cbd-80c1-4251-aead-ba56f1c406d0)





### Describe the actions that led you to experience the problem

Stats genentration had a issue since build analyzer consider as invalid format

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

After uploading stats.json file

![image](https://github.com/angular/angular/assets/29145245/4efc4270-4802-4fb8-b4c7-be5640659d09)

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

_No response_

### Provide any additional information here in as much as detail as you can

_No response_
Repository: rust
Issue: Codegen significantly worse when using u128 rather than two u64
Labels: A-LLVM,I-slow,A-codegen,T-compiler,C-bug,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
fn read_bits(data: &mut u128, n_bits: u32) -> u32 {
    let ret = *data & ((1 << n_bits) - 1);
    *data >>= n_bits;
    ret as u32
}
```

This replaces the original code which was emulating the same operation using two u64:
```rust
struct Bitstream {
    low: u64,
    high: u64,
}

impl Bitstream {
    fn read_bits(&mut self, num_bits: u32) -> u32 {
        let mask = (1 << num_bits) - 1;
        let bits = self.low & mask;
        self.low >>= num_bits;
        self.low |= (self.high & mask) << (u64::BITS as u64 - num_bits as u64);
        self.high >>= num_bits;
        bits as u32
    }
}
```

I expected to see this happen: no conditional code should be generated, resulting in the same performances as the u64 code.

Instead, this happened: the codegen is significantly worse.  For a [BC7 decoding crate](https://github.com/ScanMountGoat/image_dds/tree/main/bcdec_rs) the blocks are decoded 20 ns slower when using u128 instead of the existing high and low u64 (163.48 ns per block → 145.83 ns per block, -10.749% including randomness overhead). The same happens with an [ASTC decoding crate](https://github.com/wwylele/astc-decode). This is a followup of https://github.com/rust-lang/rust/issues/122252.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.79.0-nightly (9d5cdf75a 2024-04-07)
```
Repository: PowerToys
Issue: [File Actions Menu] Migrate to more modern progress dialog
Labels: Idea-Enhancement,Needs-Triage,Product-File Actions Menu

### Description of the new feature / enhancement

Currently File Actions Menu uses an old looking dialog to show the progress of file operations. We should move to a WinUi3 one.

### Scenario when this would be used?

More modern looking UI

### Supporting information

_No response_
Repository: vscode
Issue: Mouse middle button could close a pinned tab
Labels: feature-request,workbench-tabs

It now takes either two keyboard shortcuts or two mouse gestures to close a tab. Maybe we could allow mouse middle button to close a pinned tab instead?
Repository: ant-design
Issue: Resize Icon weird rendering on mobile devices
Labels: help wanted,Inactive,📱Mobile Device

### Reproduction link

[https://ant.design/components/input](https://ant.design/components/input)

### Steps to reproduce

Watch resizeable textareas on mobile devices. The resize icon is rendered as dot?

### What is expected?

IMO, the icon should not be present or be the default icon on mobile devices.

### What is actually happening?

Weird rendering of a dot

![image](https://github.com/ant-design/ant-design/assets/16700053/a9881e19-4e9f-47ae-b8c4-7bff68311a97)


| Environment | Info |
| --- | --- |
| antd | 5.16.1 |
| React | 18.2.0 |
| System | Windows 11 |
| Browser | Latest Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: stable-diffusion-webui
Issue: [Feature Request]: Use GTT with AMD cards perhaps?
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

A CLI flag or a setting that uses GTT to store data that doesn't fit into the VRAM of the GPU. ROCm itself doesn't work with GTT because of reasons, and 12G VRAM isn't enough to generate pictures with a larger resolution

### Proposed workflow

1. Go to settings 
2. Press a convenient switch labeled "Use GTT with AMD cards" or something
3. Relaunch webui(?)
4. PROFIT


### Additional information

_No response_
Repository: pytorch
Issue: Support FP16 accumulation for faster LLM inference on 4090 like GPUs
Labels: module: performance,triaged,module: half

### 🚀 The feature, motivation and pitch

## Background
Many existing Large Language Models (LLMs) utilize FP16 during inference to improve performance. Downstream inference libraries, such as vllm, rely on fundamental operators in PyTorch, like `F.Linear`. Presently, PyTorch only supports two levels of FP16 GEMM, controlled by `allow_fp16_reduced_precision_reduction`. Both levels use FP32 as the computation accumulation data type.

## Opportunity
Commodity NVIDIA RTX GPUs, such as the 3090 and 4090, show double throughput when doing FP16 GEMM with FP16 accumulation compared to FP32 accumulation. By benchmarking following simple perplexity test script, it can be demonstrated that using FP16 accumulation results in a 40% end-to-end speedup on 4090, with a minimal perplexity increase (0.0006) in LLM serving scenarios. 
```python
# from https://huggingface.co/docs/transformers/perplexity
import torch
from tqdm import tqdm
from datasets import load_dataset
from transformers import AutoTokenizer, AutoModelForCausalLM

name = "meta-llama/Llama-2-7b-hf"
tokenizer = AutoTokenizer.from_pretrained(name)
model = AutoModelForCausalLM.from_pretrained(name,torch_dtype=torch.float16).cuda()
ds = load_dataset("wikitext", "wikitext-2-raw-v1", split="test")
encodings = tokenizer("\n\n".join(ds["text"]), return_tensors="pt")

max_length = 2048
stride = 1024
seq_len = encodings.input_ids.size(1)

nlls = []
prev_end_loc = 0
for begin_loc in tqdm(range(0, seq_len, stride)):
    end_loc = min(begin_loc + max_length, seq_len)
    trg_len = end_loc - prev_end_loc  # may be different from stride on last loop
    input_ids = encodings.input_ids[:, begin_loc:end_loc].to('cuda')
    target_ids = input_ids.clone()
    target_ids[:, :-trg_len] = -100

    with torch.no_grad():
        outputs = model(input_ids, labels=target_ids)
        neg_log_likelihood = outputs.loss

    nlls.append(neg_log_likelihood)
    prev_end_loc = end_loc
    if end_loc == seq_len:
        break

ppl = torch.exp(torch.stack(nlls).mean())
print(ppl)
```
## Proposed Feature
Introduce a new API named `torch.set_float16_matmul_precision` to offer three levels of precision:

1. "highest": FP16 matmul uses FP32 as all the intermediate accumulation mode, which may lead to performance regression. This aligns with setting `torch.backends.cuda.matmul.allow_fp16_reduced_precision_reduction` to `False`.
   
2. "high" (default): FP16 matmul uses FP32 as the computation accumulation mode. This aligns with setting `torch.backends.cuda.matmul.allow_fp16_reduced_precision_reduction` to `True`, which is also the current default behavior.

3. "medium": FP16 matmul uses FP16 as the computation accumulation mode.

This feature enhancement aims to provide users with more control over the precision levels during FP16 matmul operations, catering to needs in inference scenarios

### Alternatives

_No response_

### Additional context

Migrated from #123157, make the feature more clear here.
Repository: node
Issue: Inconsistent behavior of `stdio[3]: 'ignore'`
Labels: child_process

### Version

v21.7.2

### Platform

Linux my-laptop 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar  5 21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

child_process

### What steps will reproduce the bug?

With `print.js`:

```js
import {writeSync} from 'node:fs'

const fdNumber = Number(process.argv[2])
writeSync(fdNumber, '.')
```

With `example.js`:

```js
import {spawn} from 'node:child_process'

spawn('node', ['./print.js', '1'], {stdio: ['pipe', 'ignore', 'inherit', 'ignore']})
```

Prints nothing. But:

```js
import {spawn} from 'node:child_process'

spawn('node', ['./print.js', '3'], {stdio: ['pipe', 'ignore', 'inherit', 'ignore']})
```

Prints the following:

```
node:fs:933
  handleErrorFromBinding(ctx);
  ^

Error: EINVAL: invalid argument, write
    at writeSync (node:fs:933:3)
    at file:///home/ether/Desktop/print.js:4:1
    at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:323:24)
    at async loadESM (node:internal/process/esm_loader:28:7)
    at async handleMainPromise (node:internal/modules/run_main:120:12) {
  errno: -22,
  syscall: 'write',
  code: 'EINVAL'
}

Node.js v21.7.2
```

### How often does it reproduce? Is there a required condition?

No.	

### What is the expected behavior? Why is that the expected behavior?

`ignore` should behave consistently regardless of the same descriptor.

### What do you see instead?

`ignore`'s behavior differs between `stdio[1]` and `stdio[3]`.

### Additional information

I understand the reason might be that child processes should always have a `stdin`/`stdout`/`stderr` even when ignored, while this does not apply to other file descriptors. So `stdio[3]: 'ignore'` probably results in no file descriptor being created, as opposed to `stdio[1]: 'ignore'`.

On one hand, the current behavior is more efficient, as it does not waste creating a file descriptor that's not going to be used.
On the other hand, this results in inconsistent behavior.

Any change there would be breaking too. So this probably won't be fixed, but I reported it in case this was not intentional.
Repository: kubernetes
Issue: CEL cost budget exceeded when using messageExpression
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

I have a CRD with the following property within the top level spec schema:
```
config:
  type: object
  x-kubernetes-validations:
    - messageExpression: '''invalid attempts: '' + string(self.attempts)'
      rule: self.attempts >= 0
  properties:
    attempts:
      type: integer
      maximum: 2147483647
      minimum: -2147483648
```

The API server rejects the CRD with the following error:
```
* spec.validation.openAPIV3Schema.properties[spec].properties[config].x-kubernetes-validations[0].messageExpression: Forbidden: estimated messageExpression cost exceeds budget by factor of more than 100x (try simplifying the rule, or adding maxItems, maxProperties, and maxLength where arrays, maps, and strings are declared)
* spec.validation.openAPIV3Schema.properties[spec].properties[config].x-kubernetes-validations[0].messageExpression: Forbidden: contributed to estimated rule cost total exceeding cost limit for entire OpenAPIv3 schema
* spec.validation.openAPIV3Schema: Forbidden: x-kubernetes-validations estimated rule cost total for entire OpenAPIv3 schema exceeds budget by factor of more than 100x (try simplifying the rule, or adding maxItems, maxProperties, and maxLength where arrays, maps, and strings are declared)
```

This entire CRD contains a single CEL rule, and this is only a problem when using `messageExpression` in the validation rule. 

### What did you expect to happen?

I would expect `string(intValue)` to not cause the cost budget of the validation rule to be exceeded.

### How can we reproduce it (as minimally and precisely as possible)?

Use a similar schema as shown in the example.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.1", GitCommit:"4c9411232e10168d7b050c49a1b59f6df9d7ea4b", GitTreeState:"clean", BuildDate:"2023-04-14T13:21:19Z", GoVersion:"go1.20.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"29", GitVersion:"v1.29.2", GitCommit:"4b8e819355d791d96b7e9d9efe4cbafae2311c88", GitTreeState:"clean", BuildDate:"2024-02-14T22:24:00Z", GoVersion:"go1.21.7", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.27) and server (1.29) exceeds the supported minor version skew of +/-1
```

</details>


### Cloud provider

Kind cluster


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: vscode
Issue: Website release notes do not load on my iPad
Labels: bug,vscode-website,ios-ipados

ipad, edge

https://code.visualstudio.com/updates/v1_88

1. Try to read the release notes.
2. Very badly rendered. And then it crashes my MS Edge browser

Happy to provide additional info if needed.

![Image](https://github.com/microsoft/vscode/assets/1926584/942cd251-203b-4629-909f-28efd4b2e68a)


fyi @ntrogh
Repository: TypeScript
Issue: No error when accessing setter-only properties
Labels: Suggestion,In Discussion

### 🔎 Search Terms

"setter only", "setter-only"

### 🕗 Version & Regression Information

- This behavior is present in the current version of TypeScript, 5.4.4

### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/MYGwhgzhAEBiD29oG8BQ0PQgUwC7QCMwAnACiIC8AuLXYgSwDsBzAShWgF9VvVh5GEfADNE0ALzRG2AO5xEpVgG4+AodABuYEAFdsNIQxYToo+ADoixJdAD0t6ABUAFvRiQI9ZowC22RvgQzvA6IAAmUvD4BNjQ2iDwMthhADSmiJYk0DL0ICBxIDJgAJ4wMdA6jGHYwkzJAIRAA

### 💻 Code

```ts
class Foo {
    set bar(baz: string) { }
}

const foo = new Foo();
const value: string = foo.bar; // This assignment should not be allowed, foo.bar will always be undefined!
```


### 🙁 Actual behavior

There is no error reported during type-checking.

### 🙂 Expected behavior

The type-checking should report an error for the assignment in the last line as `foo.bar` will always be undefined.

### Additional information about the issue

#21759 is related, but that issue proposes a whole new language feature, this issue is solely about the lack of a type error.
Repository: axios
Issue: Issue CVEs for vulnerabilities fixed by #6167 and #6163
Labels: priority::medium

### Describe the issue

The release notes for version 1.6.4 fixed two vulnerabilities that are missing CVEs, and as a result are not found by GitHub Dependabot or other tools dependent on the GitHub Advisory Database or other CVE databases.

https://github.com/axios/axios/releases/tag/v1.6.4
* [Prototype pollution in formToJSON](https://github.com/axios/axios/issues/6167)
* [Security vulnerability in follow-redirects](https://github.com/axios/axios/issues/6163)

Could these be published as CVEs? One easy way to do so is to create a GitHub security advisory on the repository: https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/publishing-a-repository-security-advisory

Thanks!

### Example Code

_No response_

### Expected behavior

When possible, security vulnerabilities should be reported as advisories via CVEs so they can be automatically detected by tools.

### Axios Version

_No response_

### Adapter Version

_No response_

### Browser

_No response_

### Browser Version

_No response_

### Node.js Version

_No response_

### OS

_No response_

### Additional Library Versions

_No response_

### Additional context/Screenshots

_No response_