sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: deno doc --html : incorporate the content of the readme.md file into the documentation (if available)
Labels: suggestion

The issue title tells it all. It is always a good idea to write a GitHub readme.md file that would be some sort of an introduction to a package, but it should also be used as part of the documentation on the front page. Converting that file into the HTML index page is very helpful.

(I am obviously influenced by the fact that typedoc does exactly that, and I found that a really useful feature when writing a documentation.)
Repository: rust
Issue: Tracking issue for release notes of #86319: Tracking Issue for Path::file_prefix
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #86319.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Tracking Issue for Path::file_prefix](https://github.com/rust-lang/rust/issues/86319)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @mbhall88 -- origin issue/PR authors and assignees for starting to draft text
Repository: deno
Issue: run::spawn_kill_permissions is flaky
Labels: flaky

```
---- run::spawn_kill_permissions stdout ----
command /Users/runner/work/deno/deno/target/debug/deno run --quiet --allow-run=cat spawn_kill_permissions.ts
command cwd /Users/runner/work/deno/deno/tests/testdata
OUTPUT
error: Uncaught (in promise) TypeError: Child process has already terminated.
child.kill("SIGTERM");
      ^
    at ChildProcess.kill (ext:runtime/40_process.js:357:5)
    at file:///Users/runner/work/deno/deno/tests/testdata/spawn_kill_permissions.ts:6:7

OUTPUT
thread 'run::spawn_kill_permissions' panicked at tests/integration/run_tests.rs:1990:1:
bad exit code, expected: 0, actual: 1
stack backtrace:
   0:        0x1068f9366 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hcaf66bc4c0c453df
   1:        0x10691ddcb - core::fmt::write::hc9c5f1836b413410
   2:        0x1068f50a2 - std::io::Write::write_fmt::h5ce5bc7686de8484
   3:        0x1068faba8 - std::panicking::default_hook::{{closure}}::h52c0b2f44f6107c5
   4:        0x1068fa728 - std::panicking::default_hook::h5a6cf31501c161b2
   5:        0x10482903b - test::test_main::{{closure}}::h3d665f637d89df05
   6:        0x1068fb910 - std::panicking::rust_panic_with_hook::hda4640ee332466e9
   7:        0x1068fb195 - std::panicking::begin_panic_handler::{{closure}}::haa3060694b34ea3d
   8:        0x1068f9849 - std::sys::backtrace::__rust_end_short_backtrace::h8eb44913cfe71457
   9:        0x1068faddc - _rust_begin_unwind
  10:        0x10694fb5a - core::panicking::panic_fmt::h31edc3d6ff0aadca
  11:        0x104a3496a - test_server::builders::TestCommandOutput::assert_exit_code::hf6962d833f7ce52f
  12:        0x10456b003 - integration_tests::run::spawn_kill_permissions::h10458c72b0e86c20
  13:        0x10456a9b5 - integration_tests::run::spawn_kill_permissions::{{closure}}::h4f2c7ba775890cd1
  14:        0x1044174f8 - core::ops::function::FnOnce::call_once::h8048a78777d92048
  15:        0x10482d60b - test::__rust_begin_short_backtrace::h93e921f893a90bb1
  16:        0x10482ce71 - test::run_test::{{closure}}::h42576c3f690468a6
  17:        0x1047f1b1d - std::sys::backtrace::__rust_begin_short_backtrace::hb534ca9204c87c90
  18:        0x1047f5322 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h95ab9f9938de870a
  19:        0x106900e8b - std::sys::pal::unix::thread::Thread::new::thread_start::h55ff15b5f[2276](https://github.com/denoland/deno/actions/runs/12088287790/job/33711490397?pr=27151#step:43:2277)bcd
  20:     0x7ff80ce3f1d3 - __pthread_start


failures:
    run::spawn_kill_permissions
```

https://github.com/denoland/deno/actions/runs/12088287790/job/33711490397?pr=27151
Repository: rust
Issue: Tracking issue for release notes of #133089: Stabilize noop_waker
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #133089.

### Steps

- [x] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [x] Issue is nominated for release team review of clarity for wider audience.
- [x] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Stabilized APIs
- [`std::task::Waker::noop`](https://doc.rust-lang.org/stable/std/task/struct.Waker.html#method.noop)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @eholk, @compiler-errors -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #129322: Tracking Issue for `ptr::fn_addr_eq`
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #129322.

### Steps

- [X] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Stabilized APIs
- [`ptr::fn_addr_eq`](https://doc.rust-lang.org/std/ptr/fn.fn_addr_eq.html)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @Urgau -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Missed optimizations: Err returns should be out of line, loop not recognized as iterating at least once
Labels: T-compiler,C-optimization

As of today (2024-11-29), neither the release nor the nightly compiler
does an ideal job of optimizing this string validation function.

```rust
pub enum IdError {
    IdEmpty,
    IdTooLong,
    IdNotAscii,
}

#[inline(never)]
pub fn check_id(value: &str, limit: usize) -> Result<(), IdError> {
    if value.is_empty() {
        return Err(IdError::IdEmpty);
    }
    if value.len() > limit - 1 {
        return Err(IdError::IdTooLong);
    }
    if value.as_bytes().iter().any(|c| !(1u8..=127u8).contains(c)) {
        return Err(IdError::IdNotAscii)
    }
    Ok(())
}
```

There are two missed optimizations.  For code like this, the compiler
would ideally recognize that conditional `Err` returns are unlikely,
and make the fall-through path be the one that (eventually) returns
`Ok`.  Nightly gets this right for the first two checks but not the
third.  Second, the compiler does not notice that, if the first two
checks succeed, then the loop in the third check must iterate at least
once.  In addition to the redundant test, this might be inhibiting
vectorization of the loop.

The dec/cmp/jb sequence used for the second test can also be
micro-optimized to cmp/jbe but that’s extremely minor.

[playground link](https://play.rust-lang.org/?version=nightly&mode=release&edition=2021&gist=7b445753298ffbd4f08469ea576172b1)

<details><summary>assembly generated by 1.85.0-nightly (2024-11-28 a2545fd6fc66b4323f55)</summary>

```asm
playground::check_id:
    testq   %rsi, %rsi
    je      .LBB0_1

    decq    %rdx
    movb    $1, %al      ; 1 = Err(IdTooLong)
    cmpq    %rsi, %rdx
    jb      .LBB0_8

    xorl    %eax, %eax
.LBB0_4:
    cmpq    %rax, %rsi
    je      .LBB0_5

    cmpb    $0, (%rdi,%rax)
    leaq    1(%rax), %rax
    jg  .LBB0_4

    movb    $2, %al      ; 2 = Err(IdNotAscii)
.LBB0_8:
    retq

.LBB0_1:
    xorl    %eax, %eax   ; 0 = Err(IdEmpty)
    retq

.LBB0_5:
    movb    $3, %al      ; 3 = Ok(())
    retq
```

</details>

<details><summary>hand-optimized desired assembly (no vectorization)</summary>

```asm
playground::check_id:
    xor     %eax, %eax   ; 0 = Err(IdEmpty); recycled as index register
    test    %rsi, %rsi
    je      .L3
    cmp     %rsi, %rdx
    jbe     .L2

.L1:
    cmpb    $0, (%rdi,%rax)
    jng     .L4
    inc     %rax
    cmp     %rax, %rsi
    jb      .L1
    mov     $3, %al      ; 3 = Ok(())
    ret

.L2:
    mov     $1, %al      ; 1 = Err(IdTooLong)
.L3:
    ret
.L4:
    mov     $2, %al      ; 2 = Err(IdNotAscii)
    ret
```

</details>
Repository: deno
Issue: WebSocket memory leaks
Labels: needs investigation,ext/websocket

Version: Deno 2.1.2

https://github.com/denoland/deno/blob/8626ec7c25e25c628eed9fdd517c0ec20b01d0a6/ext/websocket/01_websocket.js#L431

This line will wait even if the connection is closed locally.

Running the following code may reproduce the issue unstablely.

```ts
Deno.test("ws leak", async () => {
  const ws = new WebSocket(`validTarget`);
  await new Promise((resolve, reject) => {
    ws.addEventListener("open", resolve);
  });
  ws.close();
});
```

Run `deno test` would return the following error sometimes:

```
error: Leaks detected:
  - "serverWebSocket" was created during the test, but not cleaned up during the test. Close the resource before the end of the test.
  - An async operation to receive the next message on a WebSocket was started in this test, but never completed. This is often caused by not closing a `WebSocket` or `WebSocketStream`. The operation was started here:
    at op_ws_next_event (ext:core/00_infra.js:250:13)
    at WebSocket.[[[eventLoop]]] (ext:deno_websocket/01_websocket.js:431:26)
    at eventLoopTick (ext:core/01_core.js:175:7)
```
Repository: rust
Issue: Tracking issue for release notes of #131784: Stabilize unsigned and float variants of `num_midpoint` feature
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #131784.

### Steps

- [X] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Stabilized APIs
- [`{float}::midpoint`](https://doc.rust-lang.org/core/primitive.f32.html#method.midpoint)
- [Unsigned `{integer}::midpoint`](https://doc.rust-lang.org/std/primitive.u64.html#method.midpoint)
- [`NonZeroU*::midpoint`](https://doc.rust-lang.org/std/num/type.NonZeroU32.html#method.midpoint)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @Urgau, @dtolnay -- origin issue/PR authors and assignees for starting to draft text
Repository: kubernetes
Issue: Failure cluster [796ac905...] `[sig-node] [NodeFeature:SidecarContainers] Containers Lifecycle when A pod with restartable init containers is terminating when The PreStop hooks don't exit should terminate sidecars simultaneously if prestop doesn't exit`
Labels: sig/node,kind/failing-test,needs-triage

### Failure cluster [796ac905269872192a09](https://go.k8s.io/triage#796ac905269872192a09)

##### Error text:
```
[FAILED] expected PostStart 1 to live for ~32 seconds, got 0) 2024-11-16 19:59:45.714 +0000 UTC restartable-init-1 Starting
1) 2024-11-16 19:59:45.727 +0000 UTC restartable-init-1 Started
2) 2024-11-16 19:59:45.736 +0000 UTC restartable-init-1 Delaying
3) 2024-11-16 19:59:46.784 +0000 UTC restartable-init-2 Starting
4) 2024-11-16 19:59:46.803 +0000 UTC restartable-init-2 Started
5) 2024-11-16 19:59:46.819 +0000 UTC restartable-init-2 Delaying
6) 2024-11-16 19:59:47.775 +0000 UTC restartable-init-3 Starting
7) 2024-11-16 19:59:47.784 +0000 UTC restartable-init-3 Started
8) 2024-11-16 19:59:47.791 +0000 UTC restartable-init-3 Delaying
9) 2024-11-16 19:59:48.851 +0000 UTC regular-1 Starting
10) 2024-11-16 19:59:48.872 +0000 UTC regular-1 Started
11) 2024-11-16 19:59:48.902 +0000 UTC regular-1 Delaying
12) 2024-11-16 19:59:53.932 +0000 UTC regular-1 Exiting
13) 2024-11-16 19:59:54.952 +0000 UTC PreStop-restartable-init-2 Starting
14) 2024-11-16 19:59:54.952 +0000 UTC PreStop-restartable-init-1 Starting
15) 2024-11-16 19:59:55.004 +0000 UTC PreStop-restartable-init-3 Starting
16) 2024-11-16 19:59:55.081 +0000 UTC PreStop-restartable-init-1 Started
17) 2024-11-16 19:59:55.087 +0000 UTC PreStop-restartable-init-3 Started
18) 2024-11-16 19:59:55.09 +0000 UTC PreStop-restartable-init-2 Started
19) 2024-11-16 19:59:55.134 +0000 UTC PreStop-restartable-init-1 Delaying
20) 2024-11-16 19:59:55.136 +0000 UTC PreStop-restartable-init-2 Delaying
21) 2024-11-16 19:59:55.138 +0000 UTC PreStop-
```
#### Recent failures:
[11/28/2024, 9:19:03 PM ci-cri-containerd-node-e2e-features](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cri-containerd-node-e2e-features/1862320113907142656)
[11/28/2024, 8:18:03 PM ci-cri-containerd-node-e2e-features](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cri-containerd-node-e2e-features/1862304762922274816)
[11/28/2024, 6:18:01 PM ci-cri-containerd-node-e2e-features](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cri-containerd-node-e2e-features/1862274563467907072)
[11/28/2024, 4:18:08 PM ci-cri-containerd-node-e2e-features](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cri-containerd-node-e2e-features/1862244364151951360)
[11/26/2024, 7:11:03 PM ci-cri-containerd-node-e2e-features](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cri-containerd-node-e2e-features/1861562867275272192)


/kind failing-test
<!-- If this is a flake, please add: /kind flake -->

/sig node
Repository: stable-diffusion-webui
Issue: [Bug]: Unable to create venv, The system cannot find the path specified. on error code 9009
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

I tried to change the set PATH variable in the webui-user.bat file because its trying to get a Python exe file in the wrong path, but does not work even after saving the bat file.
![image](https://github.com/user-attachments/assets/ac4110e0-1231-4a70-a384-e6633f1c4a6f)


### Steps to reproduce the problem

1. Fresh install python
2. Run the webui.bat file or the webui-user.bat file

### What should have happened?

Should get the right location for the Python executable

### What browsers do you use to access the UI ?

_No response_

### Sysinfo

I dont know how to get the sysinfo because I dont know where to put the --dump-sysinfo commandline argument

### Console logs

```Shell
Creating venv in directory C:\HardDrive\stable-diffusion-webui-1.10.0 (1)\stable-diffusion-webui-1.10.0\venv using python "C:\Users\keyto\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\python.exe"
Unable to create venv in directory "C:\HardDrive\stable-diffusion-webui-1.10.0 (1)\stable-diffusion-webui-1.10.0\venv"

exit code: 9009

stderr:
'"C:\Users\keyto\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\python.exe"' is not recognized as an internal or external command,
operable program or batch file.

Launch unsuccessful. Exiting.
Press any key to continue . . .
```


### Additional information

_No response_
Repository: rust
Issue: Tracking issue for banning field projecting into `[rustc_layout_scalar_valid_range_*]` types (MCP807)
Labels: T-compiler,C-tracking-issue,A-mir-opt,T-libs,WG-mir-opt

For https://github.com/rust-lang/compiler-team/issues/807

Steps:
- [ ] Update the standard library to stop doing this
  - #133651
  - #135236
  - …
- [ ] Update the compiler to stop doing this
  - https://github.com/rust-lang/rust/blob/490b2cc09860dd62a7595bb07364d71c12ce4e60/compiler/rustc_mir_transform/src/elaborate_box_derefs.rs#L37
  - #135182
  - …
- [ ] Add MIR-opts for any new patterns that show up from doing this
  - #133324 
  - …
- [ ] Ban it in the MIR validator
  - …
- [ ] Update MIR-opts to be more willing to merge projections and such
  - …

SEO: `rustc_layout_scalar_valid_range_start` `rustc_layout_scalar_valid_range_end` `NonZero` `NonNull` "pattern types".
Repository: godot
Issue: Cut shortcut in readonly TextEdit copies text
Labels: discussion,topic:gui

### Tested versions

4.4 dev5

### System information

W10

### Issue description

When you have readonly TextEdit and do Ctrl+X on selected text, the text will be copied to clipboard.
Should it behave like that?

For reference, here you can check the behavior in browser: (this is more a LineEdit, but I think they should be consistent)
https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_input_readonly
In Chrome Ctrl+X will do nothing, in Firefox it behaves like in Godot.

idk how it behaves in other apps. Note however that Cut option in context menu is disabled for readonly TextEdits.
![](https://private-user-images.githubusercontent.com/2223172/391192773-d229738d-743b-475c-bde1-2ae8da134677.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzI5MTkwNjksIm5iZiI6MTczMjkxODc2OSwicGF0aCI6Ii8yMjIzMTcyLzM5MTE5Mjc3My1kMjI5NzM4ZC03NDNiLTQ3NWMtYmRlMS0yYWU4ZGExMzQ2NzcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MTEyOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDExMjlUMjIxOTI5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MWVlN2M3MjczNTcxNGU3NDUwYzNkNGZiZGJiOTBjOWYyZjBiM2JiNTkyZTY1MDZlYTk4MDU3ZTA2NDcxMGE5NiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.3Hk_Fe6Oq9MejWc35yJUaaQ0mumhJ2L1Ptde_geUtcA)

### Steps to reproduce

1. Add TextEdit
2. Put some text in `text`
3. Disable `editable`
4. Run and press Ctrl+X after selecting text
5. Paste it somewhere

### Minimal reproduction project (MRP)

N/A
Repository: angular
Issue: docs: first app tutorial still uses assets folder for images instead of public
Labels: area: docs-infra

### Describe the problem that you experienced

When a new project is generated, a `public` folder is created for images. The tutorial still uses the older `assets` folder. The tutorial should stay up to date with how projects are generated on users local machines, as it is very confusing when they encounter something different in their generated project.

Already had multiple people ask questions about this on Discord.

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

https://angular.dev/tutorials/first-app/02-HomeComponent#add-the-new-component-to-your-apps-layout

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

_No response_

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

_No response_

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

I want the tutorial to stay up to date with what users experience on their local machine, when they generate a project.

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

_No response_

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

```true

```

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

```true

```

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

```true

```
Repository: PowerToys
Issue: Microsft Mouse and Keyboard Center breaks Keyboard Manager
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I use Keyboard Manager to remap the Previous Track/Pause Play/Next Track buttons to use in LIghtroom.  That worked well until today, when I installed the "Microsoft Mouse and Keyboard Center" to use with a Microsoft Mouse I had on the shelf.

After installing this program from the Window store, every remapped key is sent twice. I also have "Browser Home" mapped to Ctrl+Z for Undo, and when I press it, it does the Undo and opens a new instance of Firefox (my default browser).

To summarize: the Microsoft Mouse and Keyboard Center breaks Powertoys Keyboard Manager.  As soon as I uninstalled the Microsoft Mouse and Keyboard Center, Keyboard Manager started working properly again.

Note that I do not have a Microsoft Keyboard, but I do have a Microsoft Mouse.

### ✔️ Expected Behavior

I expected Keyboard Manager to continue working as before after I installed "Microsoft Mouse and Keyboard Center".

### ❌ Actual Behavior

Every re-mapped keystroke was duplicated.  Also, when I double-checked my settings, when pressing "Save", I got a pop up message about the keys I had assigned NOT being assigned.

### Other Software

Microsoft Mouse and Keyboard center from the Windows store.  I got a popup suggesting that I install this after I connected a Microsoft Mouse, but the problem did not go away when I resumed using my Logitech mouse.