sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: PowerToys.MonacoPreviewHandler crashes when rendering UTF-8 BOM
Labels: Issue-Bug,Severity-High,Product-File Explorer

### Microsoft PowerToys version

0.85.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

File Explorer: Preview Pane

### Steps to reproduce

The PowerToys.MonacoPreviewHandler.exe crashes when trying to render UTF-8 BOM file
![image](https://github.com/user-attachments/assets/12341c9a-dcc0-4549-9125-a9bead9ca952)


### ✔️ Expected Behavior

To render the file correctly

### ❌ Actual Behavior

PowerToys.MonacoPreviewHandler.exe crashes

### Other Software

_No response_
Repository: vscode
Issue: Inlay hints appearing when they should not
Labels: info-needed,inlay-hints

<!-- ⚠️⚠️ 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?: I don't think so but it doesn't seem like an extension issue.

<!-- 🪓 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.94.0
- OS Version: Windows 11 Pro

Steps to Reproduce:

1. Have a project with dart and `Dart-code/Dart-code` (https://marketplace.visualstudio.com/items?itemName=Dart-Code.dart-code)
2. Open the project:

https://github.com/user-attachments/assets/67c595d0-ecdd-45e6-ad32-e2bd6b9b8c56

On previous versions this would not appear unless holding down the keys.

---

@DanTup
Repository: go
Issue: runtime: use .openbsd.randomdata for startupRand
Labels: help wanted,OS-OpenBSD,NeedsFix,compiler/runtime

OpenBSD has its version of AT_RANDOM, the .openbsd.randomdata ELF section documented at SPECS.randomdata. We should use that instead of reading from `/dev/urandom`.
Repository: Python
Issue:  Consolidating LCS and LIS Algorithm Implementations into a Single File
Labels: enhancement

### Feature description

Hello 

I would like to work on this issue and consolidate the algorithms for **Longest Common Subsequence (LCS)** and **Longest Increasing Subsequence (LIS)** into one file. Could you please assign this issue to me? I am excited to contribute and will ensure the file is well-organized with clear documentation for each method.

Thank you!
Repository: vscode
Issue: Allow grouping of `package.nls*.json` files in a custom folder
Labels: feature-request,l10n-platform

### Description:

Currently, the `package.nls.json` and `package.nls.{locale}.json` files are expected to be located in the root of the project for VSCode to properly detect and apply translations. However, for projects with multiple locales, this can result in a large number of translation files cluttering the root directory.

### Feature Request:

I'd like to propose a feature that allows grouping all `package.nls*.json` files inside a custom folder (e.g., `packages-nls`). The `package.json` would still reference these files in the usual way, but with the option to define their location, similar to how the `l10n` folder is currently used for `bundle.l10n.json`.

### Example:

Instead of placing all translation files in the root, we could organize them as follows:
```bash
PROJECT_NAME
├── l10n
│   └── bundle.l10n.json
├── packages-nls
│   ├── package.nls.json
│   ├── package.nls.es.json
│   └── package.nls.de.json
├── src
│   └── extension.ts
└── package.json
```

And in the `package.json`, we could still use translation keys like this:

```json
{
  "name": "my-extension",
  "version": "0.0.1",
  "main": "./out/extension.js",
  "l10n": "./l10n",
  "nls": "./packages-nls",
  "contributes": {
    "commands": [
      {
        "command": "my-extension.helloWorld",
        "title": "%my-extension.helloWorld.title%"
      }
    ]
  }
}

```

This way, developers could keep their root directory cleaner while still providing translation files.

### Current Behavior:
If the `package.nls*.json` files are moved to a custom folder, VSCode does not recognize keys and extension shows `%my-extension.helloWorld.title%`
Repository: kubernetes
Issue: PVC with a non-empty selector can’t have a PV dynamically provisioned
Labels: kind/bug,sig/storage,needs-triage

### What happened?

This issue is spun off from #57878 - I can't specify a label selector on a PVC without first provisioning the PV with labels; I want to use dynamic provisioning and apply labels to the PV from the PVC. As I read in the above issue, there might be problems with doing this via `selector` so I thought to open this to request a new field for setting PV metadata labels and annotations from the PVC.

### What did you expect to happen?

I expected that in the 6 years since the previous issue was opened, this would be improved.

### How can we reproduce it (as minimally and precisely as possible)?

Try to provision a volume with dynamic provisioning by applying a PVC with selector labels specified. It fails.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
Client Version: v1.30.4
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.4
```

</details>

### Cloud provider

<details>
Azure
</details>


### OS version

<details>
MacOS Sonoma 14.6.1

```console
Darwin WCG-MN64J410FL 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:04 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6020 arm64
```

</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: godot
Issue: Godot DAP "Completions Request" from the DAP spec is not implemented
Labels: enhancement,topic:gdscript,topic:editor

### Tested versions

Reproducible on master after https://github.com/godotengine/godot/pull/97585 is merged, because the ability to evaluate expressions in debugger was introduced.

### System information

All OS

### Issue description

"Completions Request" from the DAP [spec](https://microsoft.github.io/debug-adapter-protocol//specification.html) is not implemented


### Steps to reproduce

Start debugging with DAP in vscode.
Stop on a brakepoint
In the Watch area try to type `self.` and there would be no completion.

### Minimal reproduction project (MRP)

Empty project with a scene and one gd script is enough.
Repository: PowerToys
Issue: Complete setting backup for restore to new devices
Labels: Issue-Bug,Product-Settings,Resolution-Fix Committed,Product-Workspaces

### Description of the new feature / enhancement

To be able to backup settings, workspaces, and tool options for restore on a new computer.

### Scenario when this would be used?

Computer1  is configured with Workspaces and FanzyZones locations. A backup is taken and restored on Computer2.

On Computer2 launching the Workspace or attempting the snap to FancyZones with no further interaction with PowerToys should act the same as Computer1.

### Supporting information

Currently backups do not bring over the workspaces, which seem to be store here by default:

c:\Users\USER\AppData\Local\Microsoft\PowerToys\Workspaces\workspaces.json

Backups do bring over FancyZones but do not select the same one that was selected when the backup was taken.
Repository: flutter
Issue: Refactor and document how to add support for more test actions to `et`
Labels: P2,c: tech-debt,team-engine,triaged-engine,e: engine-tool

@reidbaker rightly points out in https://github.com/flutter/engine/pull/55638#pullrequestreview-2348773329 that how to encode actions so that `et` interprets them as testable executables is not documented (true, because the feature didn't exist until https://github.com/flutter/engine/pull/55638).

After https://github.com/flutter/engine/pull/55638 is merged, let's refactor a tad and document:

- Let's `s/actions = ["dart test"]/actions = ["et_test_executable"]` or something instead
- How to add support for new actions that are interpreted as tests (i.e. for iOS, Java, what have you)
- What type of API is expected by the wrapped action (I believe today it's just exit code 0/1)
Repository: next.js
Issue: React Spring on development server not working on initial load
Labels: bug

### Link to the code that reproduces this issue

https://github.com/gdapps-studio/nextjs-minimal-reproduction-react-spring

### To Reproduce

1. `pnpm install`
2. `pnpm dev`
3. no content on initial load

### Current vs. Expected behavior

Following the reproduction steps, you will expect seeing the content, but actually you won't see anything on initial load.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: 1.22.19
  pnpm: 9.4.0
Relevant Packages:
  next: 14.2.14 // Latest available version is detected (14.2.14).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
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 dev (local)

### Additional context

_No response_
Repository: deno
Issue: Panic on inconsistent exports in package.json
Labels: bug,node compat

Version: Deno 2.0.0-rc.10

Steps to reproduce:

1. Create a dir with a `package.json` containing `{ "exports": { ".": "./a", "a": "./a" } }`
2. Run `RUST_BACKTRACE=1 deno task`

Expected result: Some reasonable error message.

Result:

```
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: linux x86_64
Version: 2.0.0-rc.10
Args: ["deno", "task"]

thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_package_json-0.1.2/src/lib.rs:401:7:
"exports" cannot contains some keys starting with '.' and some not.
        The exports object must either be an object of package subpath keys
        or an object of main entry condition name keys only.
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: deno_package_json::PackageJson::load_from_value
   3: deno_package_json::PackageJson::load_from_path
   4: deno_config::workspace::discovery::discover_workspace_config_files_for_single_dir::{{closure}}
   5: deno_config::workspace::discovery::discover_workspace_config_files_for_single_dir
   6: deno_config::workspace::WorkspaceDirectory::discover
   7: deno::args::CliOptions::from_flags
   8: deno::factory::CliFactory::cli_options
   9: deno::tools::task::execute_script::{{closure}}
  10: deno::spawn_subcommand::{{closure}}
  11: <deno_unsync::tokio::task::MaskFutureAsSend<F> as core::future::future::Future>::poll
  12: tokio::runtime::task::raw::poll
  13: deno::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
Repository: go
Issue: x/website: publish sitemaps
Labels: NeedsInvestigation,website

go.dev has many pages. Publish sitemaps to help search engines and crawlers discover contents.

Related: https://github.com/golang/go/issues/69600

Sitemaps: https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview
 
go.dev endpoints: https://github.com/golang/website/blob/5f6954e6fcc9468bce96e01d8ebf374e37043a8c/cmd/golangorg/server.go#L153
Repository: flutter
Issue: Proposal: `run_tests.py` becomes "TAP", delegates to `et test` to find/run tests
Labels: engine,c: proposal,P2,team-engine,triaged-engine,e: engine-tool

Today, the `flutter/engine` repository (soon to become the `engine` _folder_ in a merged repo) uses `./testing/run_tests.py` to (a) collect, (b) configure, and (c) run (and report on the results of) test executables across the repository.  It will be non-trivial to replace this with another tool (i.e. `et test`).

My proposal is to move _elements_ from `run_tests.py` to `et`, but keeping `run_tests.py` as the entrypoint (i.e. for CI) until all behavior is either emulated or sufficiently completed in `et` respectively. Even once we do that, we will need a way to create lists of tests that run (i.e. TAP in google3), and this could continue to be `run_tests.py`'s area of ownership until we decide on another format.

In other words, doing something like:

```sh
./testing/run_tests.py --variant host_debug_unopt_arm64 --type engine
```

Is still _useful_, even with a fully functional `et test, because the collection of tests that make up `--type engine` (and potential configuration they need to run, i.e. conditionally wiring up SwiftShader and such) are not tasks that are going to be (directly) supported by `et test`.

We might end up _tweaking_ `run_tests.py` to have arguments similar to `et`, however:

```sh
./testing/run_tests.py --config host_debug_unopt_arm64 --type engine
```
Repository: flutter
Issue: `et test`: Add a flag (enum?) for variants of logging output
Labels: P2,c: tech-debt,team-engine,triaged-engine,e: engine-tool

@johnmccutchan in https://github.com/flutter/flutter/issues/156240#issuecomment-2394401776:

> et command line flag to enable test logging to be enabled (e.g. roboelectric tests throw away all log output by default).

This also reminds me of [`--test-summary`](https://bazel.build/docs/user-manual#test-summary) and [`--test-output`](https://bazel.build/docs/user-manual#test-output).
Repository: flutter
Issue: `et test`: Standard place to store test artifacts (i.e. stdout/stderr logs)
Labels: P2,c: tech-debt,team-engine,triaged-engine,e: engine-tool

@johnmccutchan in https://github.com/flutter/flutter/issues/156240#issuecomment-2394401776:

> standard place for tests to store arbitrary artifacts as part of the run (stdout and stderr logs would be written here)
Repository: flutter
Issue: `et test`: Run a test N number of times
Labels: P2,c: tech-debt,team-engine,triaged-engine,e: engine-tool

@johnmccutchan in https://github.com/flutter/flutter/issues/156240#issuecomment-2394401776:

> et command to run a test in a loop
Repository: PowerToys
Issue: Workspaces removes Discord from saved Workspace after each Discord update
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.85.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Workspaces

### Steps to reproduce

After each Discord update Workspaces no longer finds Discord and says "application cannot be found" thus effectively removing Discord from a saved Workspace.

### ✔️ Expected Behavior

Discord should remain in the saved Workspace after an update.

### ❌ Actual Behavior

Workspaces cannot find Discord app and do not launch it.

### Other Software

Discord
![Screenshot 2024-10-04 211729](https://github.com/user-attachments/assets/4dd98105-8727-4cab-ba2a-4f19060d2899)
Repository: flutter
Issue: Default Animation Style Design Document
Labels: framework,a: animation,P2,design doc,team-framework,triaged-framework,:scroll:

### Document Link

[flutter.dev/go/default-animation-style](https://flutter.dev/go/default-animation-style)

### What problem are you solving?

I'm putting forward a proposal to add a default `AnimationStyle` inherited theme that will be used by all implicitly animated widgets to reduce boilerplate and make it easier to apply consistent animation configuration across an app.
Repository: deno
Issue: createImageBitmap from blob [v.2.0.0-rc10]
Labels: feat,web

**Version**: Deno 2.0.0-rc10

The Web Canvas API in Deno for [createImageBitmap](https://docs.deno.com/api/web/~/createImageBitmap) supports blobs. Added earlier this year in https://github.com/denoland/deno/pull/21898

### Observations
Currently seeing failures against standard jpg/pngs. The same code in a non-Deno environment, e.g. browser, works. Omission of jpg [seems intentional](https://github.com/denoland/deno/blob/2de4faa483982478e9a36ad4ab891a887b4779f1/ext/canvas/01_image.js#L235) from the deno library , but is worth bringing up as its widely supported in [web apis](https://developer.mozilla.org/en-US/docs/Web/API/Window/createImageBitmap)

```
async function loadImage(url) {
  try{
    const response = await fetch(url);
    const blob = await response.blob();
    const imageBitmap = await createImageBitmap(blob);
    return imageBitmap;
  }
  catch (error) {
    console.log(error)
  }
}
```

```
const jpg = await loadImage("https://deno.com/images/artwork/deno_city.jpeg")

InvalidStateError: Unsupported type 'image/jpeg'
    at ext:deno_canvas/01_image.js:236:15
    at eventLoopTick (ext:core/01_core.js:175:7)
```


```
const png = await loadImage("https://deno.com/images/artwork/deno_news.png")

TypeError: Color type 'Rgb8' not supported
    at ext:deno_canvas/01_image.js:241:50
    at eventLoopTick (ext:core/01_core.js:175:7)
```

### Environment
![Screenshot 2024-10-04 at 3 35 58 PM](https://github.com/user-attachments/assets/e13bc516-7057-4c82-a8b4-9b40377753dc)
Repository: pytorch
Issue: [CD] Docker images for Nightly. Allow rebuilding and retagging for Release
Labels: oncall: releng,triaged

### 🐛 Describe the bug

Currently for OSS releases we tag images using this script when we do branch cut:
https://github.com/pytorch/pytorch/blob/main/scripts/release/tag-docker-images.sh

Instead we should allow Docker conda, libtorch and manywheel build on release branch on push the the files:
https://github.com/pytorch/pytorch/blob/main/.github/workflows/build-conda-images.yml
https://github.com/pytorch/pytorch/blob/main/.github/workflows/build-libtorch-images.yml
https://github.com/pytorch/pytorch/blob/main/.github/workflows/build-manywheel-images.yml

This will allow to cherry-pick changes to the release branch. And rebuild Docker images for release.

In Release 2.5 we had to implement workaround for this issue, but we need to avoid this in future:
https://github.com/pytorch/pytorch/pull/137148
https://github.com/pytorch/pytorch/pull/137177


### Versions

2.6.0
Repository: pytorch
Issue: `lr`, `momentum`, `weight_decay` and `dampening` parameter of `optim.SGD()` work with `bool` values
Labels: module: optimizer,triaged

### 🐛 Describe the bug

[The doc](https://pytorch.org/docs/stable/generated/torch.optim.SGD.html) of `optim.SGD()` doesn't say that the type of `lr`, `momentum`, `weight_decay` and `dampening` parameter are `bool` as shown below:

> Parameters
> - ...
> - lr ([float](https://docs.python.org/3/library/functions.html#float), optional) – learning rate (default: 1e-3)
> - momentum ([float](https://docs.python.org/3/library/functions.html#float), optional) – momentum factor (default: 0)
> - weight_decay ([float](https://docs.python.org/3/library/functions.html#float), optional) – weight decay (L2 penalty) (default: 0)
> - dampening ([float](https://docs.python.org/3/library/functions.html#float), optional) – dampening for momentum (default: 0)
> - ...

But `lr`, `momentum`, `weight_decay` and `dampening` parameter work with `bool` values as shown below:

```python
from torch import nn
from torch import optim

class MyModel(nn.Module):
    def __init__(self):
        super().__init__()
        self.linear_layer = nn.Linear(in_features=4, out_features=5)
    
    def forward(self, x):
        return self.linear_layer(x)

mymodel = MyModel()

sgd = optim.SGD(params=mymodel.parameters(), lr=True, momentum=True, 
                dampening=True, weight_decay=True)
sgd
# SGD (
# Parameter Group 0
#     dampening: True
#     differentiable: False
#     foreach: None
#     fused: None
#     lr: True
#     maximize: False
#     momentum: True
#     nesterov: False
#     weight_decay: True
# )
```

### Versions

```python
import torch

torch.__version__ # '2.3.0'
```

cc @vincentqb @jbschlosser @albanD @janeyx99 @crcrpar
Repository: transformers
Issue: Flash attention 2 support for PaliGemma model
Labels: Feature request,Flash Attention

### Feature request

Hi,
 
Is it possible to enable flash attention for PaliGemma models?

### Motivation

This feature is required to speed up inference using PaliGemma VLMs

### Your contribution

If someone can point me to the steps required to do this I 'll be happy to help. Is it as simple as enabling [this flag?](https://github.com/huggingface/transformers/blob/main/src/transformers/models/paligemma/modeling_paligemma.py#L195)
Repository: pytorch
Issue: [CD] Implement a fix for: add +PTX to CUDA 12.4 nightly binaries
Labels: oncall: releng,triaged

### 🐛 Describe the bug

Currently the way this was implemented:
https://github.com/pytorch/builder/pull/1932

Will apply to nightly and release builds. We need to add code similar to triton builds like this:
https://github.com/pytorch/builder/blob/main/conda/build_pytorch.sh#L288

```
if [[ -n "$OVERRIDE_PACKAGE_VERSION" && "$OVERRIDE_PACKAGE_VERSION" =~ .*dev.* ]]; then
...
```

To apply this change only to nightly builds. We need to apply it to nightly builds only since it increases size 200+ MB.

### Versions

2.6.0
Repository: godot
Issue: TileMap Editor: Switching between Select and Draw/Rect/Paint should switch modes.
Labels: bug,topic:editor,topic:2d

### Tested versions

4.3 stable

### System information

Win11, Godot 4.3 stable, Compatibility

### Issue description


I thought the TileMap editor was broken because it wouldn't draw when I pressed 'D' to switch to drawing from 'S' (Selection). I have to move my mouse down to the GUI and press the button, then I see the Eraser option show up and then I can draw on the TileMap.

### Steps to reproduce

- Enter "Select" mode in a TileMapLayer.
- Press the hotkey for "Draw" (D)
- Notice that you cannot draw or switch to the eraser
- Click the 'Draw' tool icon
- You can now draw and switch to the eraser.

### Minimal reproduction project (MRP)

pass