sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Mouse utilities --> Find My Mouse --> Activation Mode: Shake mouse clashes with Windows "Shake to minimize"
Labels: Idea-Enhancement,Priority-3,Product-Mouse Utilities

### Microsoft PowerToys version

0.57.0

### Running as admin

- [X] Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

- Ensure Windows "Shake to minimize" is enabled
- Grab a window
- Shake to minimize the window
- Observe that "Find my mouse" highlighting occurs

### ✔️ Expected Behavior

- "Find my mouse" highlight occurring with activation method "Shake mouse" should only engage when mouse buttons not held down
- This seems consistent with user expectations; if you are searching for your mouse cursor, will you ever hold mouse buttons down at the same time?

### ❌ Actual Behavior

- As well as shaking the window to minimize, mouse highlighting occurs on top of the window shake.

### Other Software

_No response_
Repository: ant-design
Issue: Select Ref scrollTo 函数参数在使用 OptGroup 分组时 无法快捷的定位到 OptGroup 位置，index没有区分 OptGroup 和 Option 的关系。
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

在使用分组时可以快速定位到OptGroup

问题预览：
https://codesandbox.io/s/fen-zu-antd-4-19-4-forked-wmpzxm?file=/index.js

此 Demo 中入参index无法体现出层级关系，在某些场景中需要快速定位到分组节点。





### What does the proposed API look like?

未使用分组时：scrollTo({ index: 1, align: 'top' })
使用分组时：scrollTo({ index: [2,1], align: 'top' }) 定位子节点
使用分组时：scrollTo({ groupIndex: 2, align: 'top' }) 直接定位到父级节点

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Color Picker - Name and Date for Editor
Labels: Idea-Enhancement,Product-Color Picker

### Description of the new feature / enhancement

the date that a given color was captured on would be displayed in the Editor dialog plus a field that would allow the user to add a name

### Scenario when this would be used?

As a user I want to easily identfiy differnent captures for different project over time.  Currently if I have two (particularly close) colors it's not clear which is which other than the component values.  

### Supporting information

For example:

![ColorPicker](https://user-images.githubusercontent.com/2076297/161227347-05bf76e9-95af-4178-a98f-1a468b6cfeae.png)
Repository: vscode
Issue: Flicker with inline suggestions
Labels: bug,inline-completions

```
Version: 1.67.0-insider
Commit: 909602cf04e0fa42528d692676d0d4e15e67bba2
```

I could only get this repro with these very specific steps:
* duplicate line down at line 48 in `src/vs/editor/test/common/services/modelService.test.ts`
* select `modelService`
* type out `instantiationService`
* press `cmd+/` (notice that something weird begins to happen because `Mock` now shows)
* do cursor right and cursor left (notice the flicker on cursor right)

https://user-images.githubusercontent.com/5047891/161239402-171243b9-6ad0-4af6-b78a-7f63748cc93f.mp4
Repository: kubernetes
Issue: go vet lostcancel errors in legacy-cloud-providers files
Labels: kind/bug,good first issue,sig/cloud-provider,triage/accepted

### What happened?

We found go vet issues of `lostcancel` in #109184. (It seems that go vet checks are not running under `/staging` dir.)

```
staging/src/k8s.io/legacy-cloud-providers/vsphere/nodemanager.go:190:5: lostcancel: the cancel function is not used on all paths (possible context leak) (govet)
				ctx, cancel := context.WithCancel(context.Background())
				^
staging/src/k8s.io/legacy-cloud-providers/vsphere/nodemanager.go:236:3: lostcancel: this return statement may be reached without using the cancel var defined on line 190 (govet)
		}()
```

We should fix them to ensure we don't introduce context leak as the message said.

### What did you expect to happen?

These issues from go vet are fixed.

### How can we reproduce it (as minimally and precisely as possible)?

Running go vet under `staging/src/k8s.io/legacy-cloud-providers/`

### Anything else we need to know?

_No response_

### Kubernetes version

latest master

### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: youtube-dl
Issue: Channel name
Labels: clarification-needed,question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

I can't seem to find out how to include the name of a channel. This way, I can use the downloaded file to track down the channel later. Any ideas, please?
Repository: node
Issue: startup snapshot integration in packaging solutions
Labels: embedding,snapshot

The recently landed [build-time user-land snapshot](https://github.com/nodejs/node/pull/42466) is related to packaging solutions (e.g. [pkg](https://github.com/vercel/pkg), [nexe](https://github.com/nexe/nexe)) in that if the user puts all the resources (modules, assets) in the snapshot, the compiled binary is a single-executable containing a bundle of user code, similar to what these packaging solutions produce, only that

1. We do not provide APIs for the user to specify the run-time entry point in the snapshot entry point yet (it's a WIP), so for now you still have to start the deserialized app with another JS entry point script (i.e. you need to have two files to get it up and running)
2. For now with these packaging solutions you'd usually still need to parse/execute some initialization code before the app is up and running, while with snapshots you can simply deserialize an initialized heap and may not have to execute the initialization code.

On the other hand, the user land snapshot we have right now is still a bit limited - a fair amount of builtins are not yet supported (pending more refactoring), and we still need to collect more user feedback to find states in builtins that might be out-of-sync with the system/native layer when being deserialized from the. snapshot. We also do not support user modules yet (the entry point must contain a bundle of all the modules that's needed by the app). In terms of user-experience, it might still be better to have some kind of tooling that allows users to load assets from the binary as if the assets are in the file system (i.e. virtual file system that packaging solutions provides).

I think that user snapshots in Node.js core is not a complete replacement of these packaging solutions (unless we decide to provide an "official" solution ourselves, but still packaging is different from just snapshotting), but rather it's something that packaging solutions can make use of (i.e. they can build a snapshot into the packaged binary too, while providing features like virtual file systems or compression of assets for a better user experience). So this is an issue to gather ideas and feedback, etc.

Refs: https://github.com/nodejs/node/issues/42566
Repository: godot
Issue: [3.x] Using GLOBAL_DEF for Color values causes errors in Mono glue.
Labels: bug,topic:buildsystem,topic:dotnet

### Godot version

3.x branch

### System information

Arch Linux 5.15.7-zen1-1-zen, GLES3, NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

### Issue description

In the context of the development of Godot and its extensions, using the GLOBAL_DEF macro to define Color constants or default values may result in the glue generation step generating code such as the following:
```
public static void DrawRegion(Rect2 region, Nullable<Color> color = null, bool filled = true, float width = 1f)
{
     color_in = color.HasValue ? color.Value : new Color(0,0.6,0.7,1);
     NativeCalls.godot_icall_4_381(method_bind_11, ptr, ref region, ref color_in, filled, width);
}
```
What is wrong here is the fact that double constants are being passed to Color's constructor in GodotSharp, causing compilation errors in the final build to enable Mono support in Godot.

A possible workaround (that works on my end) could be adding a constructor that accepts `double` arguments to GodotSharp's Color implementation, but I don't know if it's alright to just ignore the semantics of floating-point maths by casting double values to float without warning the user.

I've yet to confirm this happening on `master` since i'm using extensions based on `3.x`.

### Steps to reproduce

While writing engine code for `3.x`, use the GLOBAL_DEF macro to define a default Color variable. Then build the engine with Mono support as described in the relevant documentation.

### Minimal reproduction project

N/A
Repository: vscode
Issue: Request of new feature: Format On Delay.
Labels: feature-request,formatting

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
I would like to request a new feature which I will phrase **Format On Delay**.

Compared to [the existing **Format on Save**](
https://code.visualstudio.com/docs/editor/codebasics#_formatting),
 it would give me more flexibility (not having to save just because I want to auto format).

For this to work as intended, it is crucial that **Format On Delay** may be combined with
 [**Save On Delay** (`"files.autoSave": "afterDelay"`)](
https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save).

---

### Background – existing options

The existing options are explained at [the official VS Code documentation on formatting](
https://code.visualstudio.com/docs/editor/codebasics#_formatting).

There are currently three options :
* `editor.formatOnType` - Format the line after typing.
* `editor.formatOnSave` - Format a file on save.
* `editor.formatOnPaste` - Format the pasted content.

Each of these three options has its limitation – not offering the functionality I want.

In short, the only of the three options that formats the entire file, is `formatOnSave`.  
To format a file on save, [_the file must not be saved after delay_](
https://code.visualstudio.com/docs/getstarted/settings#_default-settings).

But I want to have the freedom to both **Format on Delay** _and_ [**Auto Save (on Delay)**](
https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save).

As far as I know this is not possible in the current release of VS Code (April 2022).
Repository: vscode
Issue: Add an `onExtensionActivated` activation event
Labels: feature-request,extension-activation

I have an extension (https://github.com/intersystems/language-server) that depends on another one (https://github.com/intersystems-community/vscode-objectscript). Instead of having to duplicate activation events between them to ensure that the dependent extension always activates when the main extension does, it would be nice to have a single activation event `onExtensionActivated:intersystems-community.vscode-objectscript`.
Repository: go
Issue: go/types, types2: improve API for setting type parameter constraints in importers
Labels: NeedsInvestigation

As we saw in #51219, the fact that SetConstraint eagerly computes the constraint type set makes the API awkward to use for importers.

We should investigate if this API restriction can be removed or improved.

CC @griesemer
Repository: vscode
Issue: SCM - Ability to change background of rows that are new or changed
Labels: feature-request,scm

<!-- ⚠️⚠️ 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. -->

I like gutter indicators about new, updated and deleted lines. It would be great if we could somehow style or highlight the rows with same color (update, new).
Repository: go
Issue: x/tools/gopls: consider to suppress diagnostics on code in GOMODCACHE
Labels: FeatureRequest,gopls,Tools

Spin-off from https://github.com/golang/go/issues/51947#issuecomment-1083265556

> Gopls is not suppressing diagnostics because GOMODCACHE is under the repo root, even though it is not included in the workspace. We should fix this.

That will help handling https://github.com/golang/vscode-go/issues/2080 and https://github.com/golang/vscode-go/issues/170 too - which may end up encouraging users to add the source code of the dependencies to the workspace.
Repository: vscode
Issue: Perf: optimizing notebook cell status bar items creation
Labels: debt,notebook-layout

<img width="495" alt="image" src="https://user-images.githubusercontent.com/876920/161309921-8e9d1028-14f0-4f64-8cc0-3655bd817837.png">

While scrolling in a notebook, it seems we will create statusbar items (through `_itemFactory`) for every visible cell (and dispose them when cells are moved out of view) even if the cell is not in an execution state (exciting, succeed, fail). Though the code is already pretty minimal and performant, it would save some cycles if we can push to its limits. Some ideas:

* Share the same visible visible observer (https://github.com/microsoft/vscode/blob/6e622ca1a23363c656a564d035364e850d6d9a64/src/vs/workbench/contrib/notebook/browser/contrib/cellStatusBar/executionStatusBarItemController.ts#L40-L41, https://github.com/microsoft/vscode/blob/4633aa5ed59fed97f2bce6f4e4d4aa91f0ddb354/src/vs/workbench/contrib/notebook/browser/contrib/cellStatusBar/contributedStatusBarItemController.ts#L27-L28) and listener.
* Create and start the scheduler only when the state is `Executing`, other than creating it in `ctor` https://github.com/microsoft/vscode/blob/6e622ca1a23363c656a564d035364e850d6d9a64/src/vs/workbench/contrib/notebook/browser/contrib/cellStatusBar/executionStatusBarItemController.ts#L219-L220
Repository: go
Issue: crypto/x509: come up with better solution for testing platform verifiers
Labels: Builders,NeedsFix

As evidenced by #52094 and #51599, there are issues with relying on third-party services for testing the platform verifier implementations. Ideally we'd run these tests entirely locally, but this requires mutating the trust store on the systems being tested.

While we absolutely cannot start inserting arbitrary certificates into the trust stores of developers, it may be reasonable to do this on the trybots (although there will still be some gaps here, since user added roots are always going to be treated _somewhat_ differently than roots the system chooses to trust.)

We should still have some kind of local testing that doesn't rely on trust store mutation though, perhaps just retaining the existing badssl.com based tests but gating them behind a flag?
Repository: TypeScript
Issue: Decorators broken with private fields, generated code has syntax error
Labels: Bug,Fix Available

# Bug Report

### 🔎 Search Terms

decorator private field syntax error

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?emitDecoratorMetadata=false#code/GYVwdgxgLglg9mABAEwKYTgJwIZSwCggCMAuRfASkQF4A+RbMATwrMacQG8AoRRTVFBCYklGvQxgAznAA2qAHSy4Ac0JFKFbgF9u3CLOxSpiAGJw4XXoilRcMCIgDERbJhqIAjACYAzNYABNAwcPEx8MTozCwUXNypgCzFOXV1uMFQAd2i4biA)

### 💻 Code

```ts
function decorator(cb: () => any): any {
  return () => console.log(cb())
}

class Foo {
  static #bar = 123
  @decorator(() => Foo.#bar) foo() {}
}

new Foo
```

### 🙁 Actual behavior

I expect this code to either be a compile error or to compile successfully and print `123` when run.

### 🙂 Expected behavior

The code compiles without any errors but the generated code contains a syntax error:

```js
"use strict";
var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
    return c > 3 && r && Object.defineProperty(target, key, r), r;
};
var _a, _Foo_bar;
function decorator(cb) {
    return () => console.log(cb());
}
class Foo {
    foo() { }
}
_a = Foo;
_Foo_bar = { value: 123 };
__decorate([
    decorator(() => Foo.)
], Foo.prototype, "foo", null);
new Foo;
```

Context: I discovered this issue while investigating how TypeScript handles various decorator edge cases, which I'm doing because I'm trying to replicate TypeScript's behavior into esbuild's TypeScript transpiler for this issue: https://github.com/evanw/esbuild/issues/2147.
Repository: go
Issue: x/net/http2: When using an http2.Transport with http.Client, TLS-related httptrace callbacks are not invoked
Labels: NeedsInvestigation

First, thank you *so* much for the awesome httptrace functionality! It's a lifesaver. Second, I have a patch that fixes the issue here -- I am submitting an Issue first because 

> Excluding very trivial changes, all contributions should be connected to an existing issue.

and I want to make sure that I am following best practices. And now, on with the report:

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.19-e72cd2de38 Sun Mar 27 02:50:33 2022 -0400 linux/amd64
</pre>

*Note*: Same behavior seen with the "Release" versions of 1.18. 

### Does this issue reproduce with the latest release?

Yes (see above)

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/hawkinsw/.cache/go-build"
GOENV="/home/hawkinsw/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/hawkinsw/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/hawkinsw/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/hawkinsw/code/gosrc/goroot"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/hawkinsw/code/gosrc/goroot/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.19-e72cd2de38 Sun Mar 27 02:50:33 2022 -0400"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/hawkinsw/code/goresponsiveness/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3289694319=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

A fully buildable and executable program (with flags for eliciting expected and unexpected behavior) is available at

[https://github.com/hawkinsw/bugs/tree/main/httptrace](https://github.com/hawkinsw/bugs/tree/main/httptrace)

`
$ go build ./repro.go
`

To get expected behavior,
`
$ ./repro
`

To get unexpected behavior,
`
$ ./repro -bug
`

All code (and rationale behind it) in the MRE is commented. I look forward to submitting my (simple) patch and contributing! 

I hope that all this information is helpful!
Will
Repository: pytorch
Issue: [BE] add documentation for adjust learning rate when going to distributed training
Labels: oncall: distributed,triaged,better-engineering

### 🚀 The feature, motivation and pitch

In our doc, it's better that we could add a note in the doc for adjusting learning rate when going from one to multiple, there're some issues that user confused about adjusting it, i.e. https://discuss.pytorch.org/t/how-to-scale-warmup-the-learning-rate-for-large-batch-size/146519/3

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: electron
Issue: [Bug]: double logging in the renderer devtools console from a preload of a cross-site nav when webContents.debugger is attached
Labels: bug :beetle:,has-repro-gist

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

18.0.1 x64

### What operating system are you using?

Windows

### Operating System Version

win7 sp1 x64

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

a single `console.log('preload', process.hrtime.bigint());` in the preload should be logged once

### Actual Behavior

1. run the fiddle
2. switch to the renderer devtools console
3. configure the console to "preserve log" and not "group similar messages"
4. cross-site navigate via the console: `location = 'https://example.com/'`
5. `console.log('preload', process.hrtime.bigint());` in the preload is logged twice

### Testcase Gist URL

https://gist.github.com/b0f7f70505ff3d225736ac27ec06fc7d

### Additional Information

_No response_