sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: "Start Extension Profile Host" does nothing (error: failed to connect)
Labels: bug,extension-host

<!-- ⚠️⚠️ 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?: N/A - cannot use this feature without extensions running

<!-- 🪓 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 (5c3e652f63e798a5ac2f31ffd0d863669328dc4c)
- OS Version: macOS Sonoma 14.4.1

Steps to Reproduce:

I am trying to follow the instructions [here](https://github.com/microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions) to create a profile for an extension to report a CPU issue (specifically the [GitHub Pull Requests](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension). However, when I press "Start Extension Profile Host", nothing happens. I tried on another extension to be sure and still nothing.

Checking in Output > Window, I see the following log each time I try:
```
2024-04-10 11:35:16.140 [error] failed to connect: Error: failed to connect
    at connectWithRetry (/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/v8-inspect-profiler/index.js:47:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.startProfiling (/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/v8-inspect-profiler/index.js:61:20)
    at async N.startProfiling (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:58:47467)
```
Repository: godot
Issue: Can't easily drag mutiple node into property shared by multiple node
Labels: enhancement,discussion,topic:editor,usability

### Tested versions

409c71bdfd8e0a08fd726225ebdce16bc60a4570

### System information

macOS 13.3.0 - Vulkan (Forward+) - integrated Apple M1 Pro - Apple M1 Pro (8 Threads)

### Issue description

Since #90378 you can now easily drag and drop a batch of node inside a property of a node. Unfortunately this doesn't work for putting it in properties in multiple nodes. This is a small usability issue which is not urgent especially since improving this will most likely be hard. Maybe here the good solution would be to be able to pin the Inspector.

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: [flutter release] track metrics related automated cherry pick
Labels: P2,team-release,triaged-release

Come up with ways to track useful metrics related to [automated cherry pick](https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process) 
which metrics we are interested in, and how to write from github to plx?

potential approach: write comment to an open issue, and use github query api to collect metrics. (subject to public users not spamming our open issue)
Repository: flutter
Issue: [flutter release] google testing flake rate over 4 percent
Labels: P2,team-release,triaged-release

SLO is set at 2 percent, but we have been getting flake rate at 4 percent / 5 percent.
Repository: TypeScript
Issue: Declaration emit of private properties should strip jsdoc
Labels: Bug,Help Wanted

### 🔎 Search Terms

jsdoc dts declaration emit private properties property

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/KYDwDg9gTgLgBAYwDYEMDOa4DEITgbwCg4S4B6AKgrgBUALAS0ybhTjAFcAjJBhOALbAYdCABMAdHAplipTjz7tuvBAFlhosQAoAlAQC+hOSUrV6LFmzBQGANxQxggzeIA0rAHZi4AdwZISHBczmgwtmBgwD4MnnAizmLAyChQjgwQcQBmAcBSMibstg5ORfaOwBoi4nqGhAZAA

### 💻 Code

```ts
export class Foo {
    /** This is a public method. */
    public publicMethod() {}

    /** This is a private method, and will be stripped in the declaration file. */
    private privateMethod() {}
}
```


### 🙁 Actual behavior

```ts
export declare class Foo {
    /** This is a public method. */
    publicMethod(): void;
    /** This is a private method, and will be stripped in the declaration file. */
    private privateMethod;
}
```

Note the jsdoc on the private method.

### 🙂 Expected behavior

```ts
export declare class Foo {
    /** This is a public method. */
    publicMethod(): void;
    private privateMethod;
}
```

### Additional information about the issue

It sure seems like this info should be stripped; after all, the type information is gone, leaving only a marker to inform child classes.

This causes TypeScript's own dts files to be filled with private method jsdoc. https://github.com/microsoft/TypeScript/pull/57492/files#r1559884318
Repository: flutter
Issue: Auto reboot DeviceLab bots when a quarantine state is detected
Labels: team-infra,P2,infra: device lab,triaged-infra

As of 04/09/2025, 29 out of 50 recent closed `infra: device lab` bugs are related to `Mac bots Lost external connection phone device`. Example: https://github.com/flutter/flutter/issues/146456

Current recovery action:
1) file a tracking bug
2) manual reboot the bot

This incurs expensive maintenance time, and we should automate the recovery process.

Suggestion:
- [ ] add bot reboot logic + device recovery logic when a quarantine state is detected. Note: only the quarantine state from the device doctor should be counted, excluding cases like `manual quarantine`.
- [ ] track the number of reboot, avoiding endless reboot when the quarantine state persists
- [ ] monitor/report `swarming.log` when this happens again to understand if reboot has been skipped due to weird device doctor behavior /cc @kentnguyen99 please help with this.
Repository: flutter
Issue: Auto free disk space for Mac DeviceLab bots
Labels: team-infra,P2,infra: device lab,triaged-infra

As of 04/09/2025, 7 out of 50 recent closed `infra: device lab` bugs are related to `Mac bots low on disk space`. Example: https://github.com/flutter/flutter/issues/146353

Current action: manually clean up some non critical logs/temp/cache dirs to free space. 
We should auto the process to relieve maintenance burden.

- [ ] Collect list of common dirs that need to free up /cc @kentnguyen99 Please help with this.
- [ ] Implement auto free logics in device doctor and executed from bot config
Repository: flutter
Issue: Auto set android device screen timeout from Salt
Labels: team-infra,P2,infra: device lab,triaged-infra

It happens that the android device screen timeout was miss-setup during initial device setup. To make the process more stable, we should move it to salt as an auto-provision step.

Example: https://github.com/flutter/flutter/issues/146346
Repository: flutter
Issue: Re-investigate Windows salt state
Labels: team-infra,P2,infra: device lab,triaged-infra

Context:
https://github.com/flutter/flutter/issues?q=is%3Aissue+label%3A%22infra%3A+device+lab%22+win
https://github.com/flutter/flutter/issues/145724
https://github.com/flutter/flutter/issues/144776

This has caused bots dead frequently, and a manual run of salt state is needed to bring them back.

More investigation is needed to make the salt status on windows bots stable.
Repository: flutter
Issue: ☔ Enable execution of framework tests using presubmit engine artifacts
Labels: a: tests,framework,team-infra,P2,triaged-infra

One of the objectives of the engine v2 builds is to add the ability of running framework end to end tests (devicelab, flutter driver, flutter test, integration tests) using engine presubmit artifacts. The foundational work is already completed but there are still a few more steps to release this functionality.

**Upload engine artifacts to a gcs namespace including an orchestrator build identifier.** 

The initial expectation was that engine subbuilds won't be duplicated across builds of the same commit. This expectation was not true as subbuilds reuse names even though sometimes they use different gn | ninja options. Furthermore to take advantage of subbuild reuse across builds of the same commit will require a graph scheduler that is still work in progress.

To unblock the execution of framework tests using presubmit engine artifacts while the scheduler is completed we need to upload presubmit artifacts to `https://storage.googleapis.com/flutter_archives_v2/flutter_try/<orchestrator_id>/<commit>`.

Upload logic is encapsulated in this recipe module https://cs.opensource.google/flutter/recipes/+/main:recipe_modules/archives/api.py

**Generalize the logic to find a good framework build**

There use to be a script in the engine to find a good framework build to test, however when looking at the engine-framework recipes they are always checking out master. We need to find out if the logic to find a new commit will be necessary.

**Adjustments to [tester recipe](https://cs.opensource.google/flutter/recipes/+/main:recipes/engine_v2/tester.py;l=49)**

These changes are required to use the orchestrator namespaced urls.

**Migrate framework tests to engine v2**

Once the changes above are completed engine specific recipes to run framework tests( https://cs.opensource.google/flutter/recipes/+/main:recipes/engine/) can be removed and the tests migrated to use the engine v2 versions.

**Separate devicelab bots running presubmit jobs to an isolated vlan**

The new lab has a dedicated vlan for on device tests that will run on presubmit.

**Cleanup**

Once all of this is completed we can remove the v2 prefix/suffix on recipes, documentation, etc.

**Add framework tests to run on engine to .ci.yaml**

Once all the changes above are completed running frameworks tests on the engine will be achieved through simple configurations in the .ci.yaml file of the engine repository and it will be limited only by resource availability.

**Optimizations**

Once we start running tests on presubmit/postsubmit in the engine it may be possible that running the same tests in the framework  won't be necessary.
Repository: ollama
Issue: MacOS Ollama not binding to 0.0.0.0
Labels: bug

### What is the issue?

So when set the OLLAMA_HOST to 0.0.0.0, I cannot access Ollama via the IP, but I can still access it via localhost.

### What did you expect to see?

I expect it to be available under <myIP>:11434

### Steps to reproduce

_No response_

### Are there any recent changes that introduced the issue?

_No response_

### OS

macOS

### Architecture

arm64

### Platform

_No response_

### Ollama version

0.1.31

### GPU

Apple

### GPU info

_No response_

### CPU

Apple

### Other software

_No response_
Repository: ollama
Issue: Add Tokenize and Detokenize Endpoints to Ollama Server
Labels: feature request

### What are you trying to do?

I would like to propose the addition of tokenize and detokenize endpoints to the Ollama server. This feature is crucial for the Ollama client interfaces (such as lollms) to effectively prepare prompts and accurately estimate the number of tokens for the LLMs. Currently, the client uses tiktoken for tokenization, which is not optimal since the token distribution depends on the model. While this can work with chatgpt compatible models, it may fail to correctly estimate the number of tokens, leading to suboptimal token computing and, in some cases, errors when the number of requested tokens exceeds the capacity of the LLM.

### How should we solve this?

Introduce two new endpoints, one for tokenization and another for detokenization, to the Ollama server:

Tokenize Endpoint:
- Input: Raw text, model name
- Output: List of tokens

Detokenize Endpoint:
- Input: List of tokens, model name
- Output: Raw text

These endpoints should return the right tokens or text depending on the model currently in use..

The tokenization endpoint should provide accurate token counting tailored to the specific LLM being used. This will ensure optimal token computing and help avoid potential errors caused by exceeding the capacity of the LLM.

### What is the impact of not solving this?

Without these endpoints, users might have to continue relying on inefficient or suboptimal solutions for tokenizing and detokenizing text data.



### Anything else?

Include documentation and examples demonstrating how to use these new functionalities effectively. Providing comprehensive guidance will help users quickly adopt these features and enhance the overall user experience.
Repository: pytorch
Issue: Support for no-frills FP8 matmuls
Labels: triaged,module: float8

### 🚀 The feature, motivation and pitch

Doing matmuls in FP8 is essential for getting the best performance out of the newest hardware (e.g. H100s and beyond). Currently, the only option for doing matmuls in FP8 is through `_scaled_mm`, which includes overhead like calculating absolute maximums, taking in a bunch of scale factors, etc, slowing it down and eroding the benefits of using FP8. What would be amazing is if there was full, accessible support for FP8 matmuls -- specifically through `torch.addbmm()` or more generally through `torch.matmul()`, where:
* The accumulation/output dtype can be specified or controlled somehow
* Potentially, an output scale factor may be applied

This would let users harness the full efficiency of FP8 math, and choosing/handling scaling factors and such could be left to the user as well.

Down the road, the ability to use `torch.compile` to efficiently fuse any input/output scaling factors into the matmul op would be dope too :)

### Alternatives

_No response_

### Additional context

_No response_

cc @yanbing-j @vkuzo @albanD @kadeng
Repository: neovim
Issue: crash when typing println!(" in Rust: ts_parser__handle_error: Assertion `did_merge' failed
Labels: has:backtrace,bug-crash,treesitter

### Problem

When working on a project I found that Neovim would consistently crash in a certain Rust file whenever I typed the characters `println!("`. It would crash exactly when I typed the `"`. The error message flashes up only for a frame or so, but I caught it in a recording:

[Screencast_20240410_211134.webm](https://github.com/neovim/neovim/assets/43073868/62d5aab8-a9a4-46bb-b492-cb18b0896e10)

I reduced the file to the following minimal example:

```rust
fn main() {
    println!("");
    for x in y {
        if true {
            true;
        } else {
            println!("");
        }
    }
}
```

Typing `println!("` in the function makes it crash. As far as I can tell, removing any other aspect of the function body suppresses the error. e.g. removing the loop body, removing branches of the if expression, removing either of the printlns.

Also, running `TSBufDisable highlight` prevents the crash, so presumably it is treesitter-related.


### Steps to reproduce

Stacktrace:

[bt.txt](https://github.com/neovim/neovim/files/14937368/bt.txt)

My neovim flake, it's not minimal but you should be able to reproduce the problem since everything is pinned:

https://github.com/ckp95/nvflake

### Expected behavior

It should not crash when I type `println!("`

### Neovim version (nvim -v)

v0.9.5

### Vim (not Nvim) behaves the same?

idk

### Operating system/version

NixOS 24.05

### Terminal name/version

konsole 24.02.0

### $TERM environment variable

xterm-256color

### Installation

custom Nix flake
Repository: pytorch
Issue: Accurately typed ValueRanges / convenient OpsHandler dtype inference
Labels: triaged,module: dynamic shapes

### 🐛 Describe the bug

I want ValueRanges to know if its an int/float/bool, so I can enforce invariants (e.g., integer ValueRanges shouldn't have fractional lower/upper bounds).  Here is a WIP diff that does some of it.

https://gist.github.com/ezyang/c9366d9c05bb7ea5939802e155a34371

However, when updating ValueRangeAnalysis OpsHandler to give accurate types, I run into a problem:

```
    @staticmethod
    def default_handler(*args, **kwargs):
        # many ops are unlikely to show up in optimizable indexing compute,
        # so we dont have full coverage
        return ValueRanges.unknown()
```

There is no convenient way to know what the dtype of this handler is going to be. I think dtype should always be in principle inferable for all handlers but I don't see any reusable mixin that lets me get what the dtype of any given handler is going to be.

cc @avikchaudhuri @eellison @lezcano 

### Versions

main
Repository: go
Issue: internal/trace/v2: TestTraceFutileWakeup failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "internal/trace/v2" && test == "TestTraceFutileWakeup"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/0e1df88c61fb194db53eb33326806feb2d68601f)):

    --- FAIL: TestTraceFutileWakeup (0.30s)
        --- FAIL: TestTraceFutileWakeup/Stress (0.15s)
            trace_test.go:292: found futile wakeup on goroutine 16


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: Fix performance problems of `flutter test --experimental-faster-testing`
Labels: tool,P2,team-engine,triaged-engine

The performance of `flutter test --experimental-faster-testing` is currently not ideal when running a large number of test files because the Lightweight Engines spawned when using this strategy get blocked from shutting down by open `ReceivePort`s. This was my latest attempt to ensure that all channels, and thus all `ReceivePort`s, get closed on the spawned isolates: https://github.com/flutter/flutter/commit/d560cf4ac29ded2198c022a0bfbdab6fd1a43e17, but this commit did not fix the problem. So, we either have to determine what other changes need to be made in order to ensure that all `ReceivePort`s get closed on spawned isolates, or alternatively we need to add a new Engine API that can forcibly kill spawned Lightweight Engines.
Repository: go
Issue: x/tools/gopls: "could not locate file for primary type checker error" bug reported by telemetry
Labels: NeedsInvestigation,gopls,Tools,gopls/telemetry-wins

```
#!stacks
"bug.Reportf" && 
  ("typeErrorsToDiagnostics.func1:+40" || 
   "typeErrorsToDiagnostics.func1:+46" ||
    "typeErrorsToDiagnostics.func1:+53")
```
This stack `aJzeGA` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2024-04-07.json):

```
gopls/bug
golang.org/x/tools/gopls/internal/util/bug.report:+35
golang.org/x/tools/gopls/internal/util/bug.Reportf:+1
golang.org/x/tools/gopls/internal/cache.typeErrorsToDiagnostics.func1:+40
golang.org/x/tools/gopls/internal/cache.typeErrorsToDiagnostics:+119
golang.org/x/tools/gopls/internal/cache.(*typeCheckBatch).checkPackage:+127
golang.org/x/tools/gopls/internal/cache.(*typeCheckBatch).handleSyntaxPackage:+70
golang.org/x/tools/gopls/internal/cache.(*Snapshot).forEachPackageInternal.func2:+1
golang.org/x/sync/errgroup.(*Group).Go.func1:+3
runtime.goexit:+0
```
```
golang.org/x/tools/gopls@v0.15.2 go1.22.1 linux/amd64 vscode (1)
```

Issue created by golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.


Closely related to:
- https://github.com/golang/go/issues/65960

Dups: 2oh2Vg 2gV6qw EJlu6A gvV3Aw uwXzpw
Repository: go
Issue: x/tools/gopls: "type checker error %q outside its Fset" bug reported by telemetry
Labels: NeedsInvestigation,gopls,Tools,gopls/telemetry-wins

```
#!stacks
"bug.Reportf" &&
  ("typeErrorsToDiagnostics.func1:+28" ||
  "typeErrorsToDiagnostics.func1:+34" ||
  "typeErrorsToDiagnostics.func1:+35" ||
  "typeErrorsToDiagnostics.func1:+37")
```

This stack `_5BDSg` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2024-02-24.json):

```
gopls/bug
golang.org/x/tools/gopls/internal/util/bug.report:+35
golang.org/x/tools/gopls/internal/util/bug.Reportf:+1
golang.org/x/tools/gopls/internal/cache.typeErrorsToDiagnostics.func1:+28
golang.org/x/tools/gopls/internal/cache.typeErrorsToDiagnostics:+119
golang.org/x/tools/gopls/internal/cache.(*typeCheckBatch).checkPackage:+127
golang.org/x/tools/gopls/internal/cache.(*typeCheckBatch).handleSyntaxPackage:+70
golang.org/x/tools/gopls/internal/cache.(*Snapshot).forEachPackageInternal.func2:+1
golang.org/x/sync/errgroup.(*Group).Go.func1:+3
runtime.goexit:+0
```
```
golang.org/x/tools/gopls@v0.15.0-pre.4 go1.21.5 darwin/amd64 vscode (1)
```

Issue created by golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.

Dups: T_TswA ypJFHg

Closely related to:
- https://github.com/golang/go/issues/65960
- https://github.com/golang/go/issues/66765
Dups: RQEPow rXJHRw 1XBmcQ igKjlQ
Repository: vscode
Issue: Webview steals focus when I right click ont he Panel
Labels: bug,webview

<!-- ⚠️⚠️ 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?: N/a

<!-- 🪓 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
- OS Version: Windows

Steps to Reproduce:

1. Compile and install the webview sample - https://github.com/microsoft/vscode-extension-samples/blob/main/webview-sample/src/extension.ts
2. "Start cat coding session"
3. Open a split view with package.json on the left and the cat coding webview on the right
4. Show Panel and drag the Timeline into the panel, then click on the package.json
5. Right click an entry in the Timeline. **Expected:** timeline stays visible. **Actual:** timeline entries disappear and webview grabs focus.

Note: I have used git bisect to identify the cause is #206529

Note: sometimes this behaviour of focus going to the webview happens when you right click in the `package.json` as well.

Note: in the recording I have made some other changes, like removing the `<img>` tag, it is to reduce file size of the gif.

![Uploading Recording 2024-04-10 at 22.55.12.gif…]()
Repository: PowerToys
Issue: File Preview Pane Request for .nss (Nilesoft Shell) support Ref: #1527
Labels: Idea-Enhancement,Needs-Triage,Product-Peek

## Request for .nss (Nilesoft Shell) preview pane support

In relation to: #1527 
The ability to view .nss files in the previewpane would be nice. .nss corresponds to Nilesoft Shell. 
>>> *Nilesoft Shell is a powerful context menu customizer with highly responsive for Windows File Explorer.*

The syntax of .nss files seems to work best if treated like an .js or .json file.


### Scenario when this would be used?

Explorer Shell

### Supporting information

_No response_