sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Search highlight not cleared sometimes
Labels: bug,search

Type: <b>Bug</b>

Sometimes the search highlight is not cleared when it becomes invalid.

VS Code version: Code - Insiders 1.93.0-insider (39d98602020ddefe53ed217a8c50b9040673a737, 2024-08-05T05:03:45.159Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz (8 x 3691)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: unavailable_off<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.95GB (5.65GB free)|
|Process Argv|--crash-reporter-id 59c38a97-6b20-42ad-b729-8c40ade347e9|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
vsaa593:30376534
py29gd2263:31024238
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythonregdiag2:30926734
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
724cj586:31013169
a69g1124:31018687
dvdeprecation:31040973
dwnewjupytercf:31046870
impr_priority:31057980
nativerepl1:31104042
refactort:31084545
pythonrstrctxt:31093868
hdi1a554:31091669
flighttreat:31105043
nativeloc1:31106922
cf971741:31108168

```

</details>

<!-- generated by issue reporter -->


https://github.com/user-attachments/assets/590f6c57-dd55-4c09-8ee6-43ebc9e71042


Not sure if it is related to this specific regex: `^(  )* [^ ]`.  It should only match an odd amount of spaces at the start of a line. In index.php this should result in no matches.
It doesn't happen often, but when it happens the highlighted parts stay as long as the file remains open.
Repository: ant-design
Issue: Date picker quarterly no longer allows user to type in dates v5
Labels: Inactive,🚌 External Dependency

### Reproduction link

[https://ant.design/components/date-picker](https://ant.design/components/date-picker)

### Steps to reproduce

https://ant.design/components/date-picker

In v4 you can type 2020-Q4 to change date

in v5 this no longer works. 

### What is expected?

When a user types in the quarterly formatted date and then hits enter a change action to occur.

### What is actually happening?

Nothing. 

| Environment | Info |
| --- | --- |
| antd | 5.20.0 |
| React | 18 |
| System | mac |
| Browser | Chrome |

---
This is affecting testing with react test library as well. Generally more tricky to get unit tests to behave as expected for other date picker types. I believe you can still use the original date picker to type in dates, but not for instance weekly or quarterly types.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: x/tools/go/analysis/passes/fieldalignment: mutates AST
Labels: NeedsInvestigation,Tools

Noticed in passing: the [fieldalignment](https://pkg.go.dev/golang.org/x/tools/go/analysis/passes/fieldalignment) analyzer (which as of gopls/v0.17.0 is now used in x/tools only by its tests) potentially mutates the AST it is passed by the analysis framework:

[x/tools/go/analysis/passes/fieldalignment/fieldalignment.go](https://cs.opensource.google/go/x/tools/+/master:go/analysis/passes/fieldalignment/fieldalignment.go;l=113;drc=1028e3027a6d05d0a9b3e5f1920f95c3bb299757):
```go
func fieldalignment(pass *analysis.Pass, node *ast.StructType, typ *types.Struct) {
	...
	for _, f := range node.Fields.List {
		// TODO: Preserve comment, for now get rid of them.
		//       See https://github.com/golang/go/issues/20744
		f.Comment = nil
		f.Doc = nil
```

No analyzer should do that. Similar mutations in other analyzers could be a cause of a variety of bugs, inconsistencies, and crashes in tools such as gopls.

We should consider developing the [deepHash](https://cs.opensource.google/go/x/tools/+/master:internal/refactor/inline/inline_test.go;l=1646;drc=4a264773f4ed8f75534b9f5e3df6618b398fc4cd) approach used in x/tools/internal/refactor/inline/inline_test.go so that we can dynamically check for unwanted AST mutations around certain operations such as Analyzer.Run. (Of course, it is not cheap, and is only as good as the test coverage.)
Repository: godot
Issue: Subsequent serializations of empty arrays get their type overwritten
Labels: bug,topic:gdscript

### Tested versions

v4.3.rc2.official [3978628c6]
v4.2.2.stable.official [15073afe3]

### System information

Ubuntu

### Issue description

```
E 0:00:00:0552   assign: Cannot assign contents of "Array[int]" to "Array[String]".
  <C++ Error>    Method/function failed.
  <C++ Source>   core/variant/array.cpp:276 @ assign()
```

### Steps to reproduce

```swift
@tool
extends Control

var prop_a: Array[int]
var prop_b: Array[String]


func _get_property_list() -> Array[Dictionary]:
	var properties: Array[Dictionary]

	properties.append({
	   "name": "prop_a",
	   "type": TYPE_ARRAY,
	   "hint": PROPERTY_HINT_TYPE_STRING,
	   "hint_string": "%d:" % [TYPE_INT]})

	properties.append({
	   "name": "prop_b",
	   "type": TYPE_ARRAY,
	   "hint": PROPERTY_HINT_TYPE_STRING,
	   "hint_string": "%d:" % [TYPE_STRING]})

	return properties
```

Using `_get_property_list` we add two arrays of different types.

However, when these properties are serialized in the scene file, then `prop_b` will for some reason be given the same type as `prop_a`:

```
prop_a = Array[int]([])
prop_b = Array[int]([])
```

This then leads to the above error message at runtime. This appears to only happen when one or both of the arrays are empty.

Even when providing an empty array as default value via `_property_can_revert()` and `_property_get_revert()`, the empty array still gets serialized. Although perhaps that is a different bug.

### Minimal reproduction project (MRP)

[godot_4_property_array_bug.zip](https://github.com/user-attachments/files/16501163/godot_4_property_array_bug.zip)
Repository: PowerToys
Issue: Regarding the function of the software timer switch. 
Labels: Needs-Triage

### Description of the new feature / enhancement

Add the function that can shut down the running software at regular intervals. And add other functions according to the wishes of each developer. 

### Scenario when this would be used?

When some software needs to be closed or stopped running at regular intervals, but the software does not provide this function, then this tool needs to be used. 

### Supporting information

_No response_
Repository: pytorch
Issue: DISABLED test_device_mode_ops_sparse_sampled_addmm_cpu_complex64 (__main__.TestDeviceUtilsCPU)
Labels: triaged,module: flaky-tests,skipped,module: unknown

Platforms: asan, linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_device_mode_ops_sparse_sampled_addmm_cpu_complex64&suite=TestDeviceUtilsCPU&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/28356072275).

Over the past 3 hours, it has been determined flaky in 33 workflow(s) with 99 failures and 33 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_device_mode_ops_sparse_sampled_addmm_cpu_complex64`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_utils.py", line 1164, in test_device_mode_ops
    for sample in samples:
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/testing/_internal/common_utils.py", line 388, in __next__
    input_idx, input_val = next(self.child_iter)
                           ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 36, in generator_context
    response = gen.send(None)
               ^^^^^^^^^^^^^^
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/testing/_internal/common_methods_invocations.py", line 1214, in sample_inputs_sparse_sampled_addmm
    .to_sparse_csr()
     ^^^^^^^^^^^^^^^
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/testing/_internal/common_utils.py", line 1461, in __torch_function__
    r = func(*args, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Please register PrivateUse1HooksInterface by `RegisterPrivateUse1HooksInterface` first.

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_CROSSREF=1 python test/test_utils.py -k TestDeviceUtilsCPU.test_device_mode_ops_sparse_sampled_addmm_cpu_complex64

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_utils.py`

cc @clee2000
Repository: vscode
Issue: Custom title bar not hiding on startup in Zen mode
Labels: bug,titlebar,workbench-zen

<!-- ⚠️⚠️ 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.92
- OS Version: Kubuntu 24.04

Steps to Reproduce:

1. Hide the title bar
2. Enable zen mode
3. Restart vscode

After the latest update, whenever I start vscode in zen mode or reloading the window, the custom title bar reappears, and using the dropdown menu option to hide it doesn't work.
I found that disabling zen mode and then reloading the window does hide it, but its annoying to do this each time
Repository: TypeScript
Issue: Feature request: TS/JS: during object destructurization show autocomplete for props after user type comma `,`
Labels: Suggestion,Help Wanted,Domain: Completion Lists,Experience Enhancement

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

TS/JS: during object destructurization show autocomplete for props after user type comma `,` w/o need to press `ctrl + space` to call autocompleter

![зображення](https://github.com/user-attachments/assets/39f784df-63f5-4af0-95d9-7c9dcf690705)
Repository: vscode
Issue: No way to score a generic language feature above `'*'` but below a selector match
Labels: under-discussion,editor-highlight

See #224884 for relevant code. To repeat:

shines light up another issue though, scoring for language providers falls into one of three buckets:
- `score: 10` is for a match on the selector
- `score: 5` is for anything with `language: '*'`
- `score: 0` is an explicit mismatch

now you have to consider, what if someone created a different textual highlight provider for whatever reason (perf, dif behavior, etc), and wanted to be scored above our default textual provider, but below a perfect match. 

Could our textual fallback be scored at maybe a new score of 1? leaving room for some new heuristic to score at 5? time to think

cc: @jrieken // @rebornix
Repository: pytorch
Issue: INTERNAL ASSERT FAILED in BatchLinearAlgebra.cpp
Labels: triaged,module: mkl,module: linear algebra

### 🐛 Describe the bug

The message **Intel oneMKL ERROR: Parameter 4 was incorrect on entry to SGELSD.** is printed, followed by a `RuntimeError` indicating that an internal assertion has failed in `BatchLinearAlgebra.cpp`, and asking that it be reported. The error occurs when a call is made to `torch.linalg.lstsq` with a cholesky factor which contains nans.

```python
import math

import torch

bad_cholesky_factor = torch.tensor([[[math.nan, 0.0], [math.nan, math.nan]]])
data = torch.randn((1, 2, 1))

torch.linalg.lstsq(bad_cholesky_factor, data, driver='gelsd')
```

```python
Traceback (most recent call last):
  File "C:\...\torch_error_reproduction.py", line 8, in <module>
    torch.linalg.lstsq(bad_cholesky_factor, data, driver='gelsd')
RuntimeError: false INTERNAL ASSERT FAILED at "C:\\actions-runner\\_work\\pytorch\\pytorch\\builder\\windows\\pytorch\\aten\\src\\ATen\\native\\BatchLinearAlgebra.cpp":1538, please report a bug to PyTorch. torch.linalg.lstsq: Argument 4 has illegal value. Most certainly there is a bug in the implementation calling the backend library.

Intel oneMKL ERROR: Parameter 4 was incorrect on entry to SGELSD.
```


### Versions

PyTorch version: 2.4.0+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Home
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect
Libc version: N/A

Python version: 3.12.3 (tags/v3.12.3:f6650f9, Apr  9 2024, 14:05:25) [MSC v.1938 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-11-10.0.22631-SP0
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture=9
CurrentClockSpeed=2000
DeviceID=CPU0
Family=107
L2CacheSize=4096
L2CacheSpeed=
Manufacturer=AuthenticAMD
MaxClockSpeed=2000
Name=AMD Ryzen 7 5825U with Radeon Graphics
ProcessorType=3
Revision=20480

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.4.0
[conda] Could not collect


cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: rust
Issue: `UdpSocket` lacks methods to operate on wildcard sockets
Labels: T-libs-api,T-libs

`UdpSocket` allows binding to wildcard IPs like `IpAddr::V6(Ipv6Addr::UNSPECIFIED)` which means it can accept packets targeted to multiple IPs. However the `send` method does not allow specifying the source IP which means any reply packets may be send from the wrong interface. The `recv` method also doesn't allow getting the target IP which would need to be passed to `send`.

This is a bit of a trap which isn't warned against in the documentation either.

Similar issue for `tokio` which mirrors the APIs: https://github.com/tokio-rs/tokio/issues/6737
Repository: flutter
Issue: package:http in the flutter/flutter repo is 15 months old
Labels: tool,P2,c: tech-debt,team-tool,triaged-tool

See https://github.com/flutter/flutter/blob/master/packages/flutter_tools/pubspec.yaml#L25 and https://pub.dev/packages/http/versions. This was first flagged in https://github.com/flutter/flutter/pull/152692, although I don't believe it is being constrained by package:usage, as the only dependencies I see it having are on meta and path: https://github.com/dart-archive/usage/pull/192/files#diff-8b7e9df87668ffa6a04b32e1769a33434999e54ae081c52e5d943c541d4c0d25R13

To figure out what package is constraining this, I would run `flutter update-packages --force-upgrade --synthetic-package-path=$TEMP_DIR` and then navigate to `$TEMP_DIR`, edit the pubspec.yaml to have a newer `package:http` version, say 1.0.0, and then run `pub get` and I would expect to get a version solve error indicating the package in our global solve that constrains package:http at less than 1.0. We should then either consider whether we can delete that (apparently abandoned) package, or if not, roll deps to that package and publish it.
Repository: go
Issue: internal/ascii: new internal package consolidating common functions
Labels: NeedsInvestigation

### Proposal Details

The standard packages write their own ASCII helper functions many times, for examples you can find ASCII-only `isSpace`, `toUpper` and `equalFold` in "encoding/json", "net", "internal/filepathlite". The "net/http" also has a internal package called `net/http/internal/ascii`.

Handling ASCII-encoded characters is a common requirement in the standard library, so a new package can share these logic and eliminate duplicate codes.

Based on my investigation of the standard library code, the new package should have these functions in it:
- Is/IsString (check if it is ASCII)
- IsLower/IsUpper
- ToLower/ToUpper (for single char)
- ToLowerString/ToUpperString
- EqualFold
- IsSpace
- TrimSpace
- IsDigit
- IsLetter
- IsPrint

This package should minimize external dependencies, and some necessary constants can be copied from packages such as "unicode".

Normal users can continue to use "bytes", "strings" and "unicode" for most tasks, so there is little point in making this package public. However, many standard packages can't directly import packages like "unicode", "strings", etc., so I thought it would be appropriate to put this new package in "internal".
Repository: ui
Issue: [bug]:  Autoplay from embla works but not AutoScroll and others
Labels: bug

### Describe the bug

[bug]: The bug was with the carousel and embla carousel extension that the owner uses to add plugins to the carousel in the library. When you use "Autoplay," it works, but when you try to use "AutoScroll," it does not allow because of a type mismatch. However, funny enough, this problem does not occur in the development server; instead, it only happens in the production. In conclusion I managed to fix temporarily for my project by ignoring the type checking for that specific section of the code I am reporting this bug so that the author will be aware of it and maybe update the docs or fix the bug.

the code:
```

 return (
    <>
     <div className="h-[300px] relative w-full overflow-hidden bg-slate-900 flex flex-col items-center justify-center ">
     <div className="absolute inset-0 w-full h-[300px] bg-slate-900 z-20 [mask-image:radial-gradient(transparent,white)] pointer-events-none" />
      
     <RevealBottom>
    <Carousel className="w-screen border-t-2 border-b-2 pt-4 pb-4 hover:border-yellow-400 hover:cursor-grab  active:cursor-grabbing focus-within:border-blue-400 "
    /**  @ts-ignore */
    plugins={[AutoScroll({  playOnInit: true, stopOnInteraction:false })]}>

      <CarouselContent className="-ml-4 flex flex-row items-center  ">
        {content.map((value, index) => (
          <CarouselItem key={index} className="pl-1 max-[767px]:basis-3/12 md:basis-3/12 lg:basis-2/12">
            

```

I used  /**  @ts-ignore */ for ignoring the type checking at that section

### Affected component/components

Carousel

### How to reproduce

1.Create a Carousel component ussing shad cn
2. Use a plugin from embla carousel other than "AutoPlay"
3. run npm run build

### Codesandbox/StackBlitz link

https://github.com/FelipeBarrosCode/portfolio-

### Logs

```bash
go to initial commit and run npm "run build"
```


### System Info

```bash
Any computer will give this error
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: [Impeller] tiny scalars can break the mask blur
Labels: P2,e: impeller,team-engine,triaged-engine

Spawned from https://github.com/flutter/flutter/issues/152778

The numbers were chosen specifically since numbers closer to zero have no issue.

## observed result
A black screen.

## expected result
A blurred circle.

## reproduction
```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const Test());
}

class Test extends StatefulWidget {
  const Test({super.key});

  @override
  State<Test> createState() => _TestState();
}

class _TestState extends State<Test> {
  @override
  void initState() {
    super.initState();
  }

  @override
  void dispose() {
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Stack(
      textDirection: TextDirection.ltr,
      children: [
        CustomPaint(
          painter: Painter(),
        )
      ],
    );
  }
}

class Painter extends CustomPainter {
  Painter();

  @override
  void paint(Canvas canvas, Size size) {
    canvas.scale(9.999999999999991e-18);
    final Paint paint = Paint()
      ..color = const Color(0xFF66BBFF)
      ..maskFilter = MaskFilter.blur(BlurStyle.normal, 10000000000000008000.0);
    canvas.drawCircle(Offset.zero, 50000000000000040000.0, paint);
  }

  @override
  bool shouldRepaint(Painter oldDelegate) => true;
}
```
Repository: deno
Issue: Directory-to-directory cp into an existing directory leaves different structure than Node
Labels: bug,node compat

Deno 1.45.5. Windows.

Given either of these programs
```js
import fs from "node:fs";
fs.cp("./source", "./dest", { recursive: true }, _ => {});
```
```js
import fs from "node:fs/promises";
await fs.cp("./source", "./dest", { recursive: true });
```
and this directory structure (where `dest` already exists, and is empty),
```
📂 source
┕ 📄 hello.txt
📁 dest
```
running with node v22.5.1 results in this
```
📂 source
┕ 📄 hello.txt
📂 dest
┕ 📄 hello.txt
```
but running with Deno 1.45.5 results in this.
```
📂 source
┕ 📄 hello.txt
📂 dest
┕ 📂 source
  ┕ 📄 hello.txt
```

To be fair, I think [Node's documentation](https://nodejs.org/api/fs.html#fscpsrc-dest-options-callback) is incorrect; it says "the behavior is similar to `cp ./source ./dest`", but at least on my machine `cp -r ./source ./dest` produces the same structure as Deno when `dest` already exists.

If `dest` does *not* exist, same behavior as Node. So I can fix my program by deleting `dest` first.