sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/tools/cmd/imports: prefer latest versions of modules
Labels: NeedsInvestigation,modules,Tools,gopls/imports

**Is your feature request related to a problem? Please describe.**
It's nice to rely on the auto-import feature, but it seems to always default to an older version.

**Describe the solution you'd like**
It would be better to always prefer the latest version of a package

**Describe alternatives you've considered**
To manually add `v2` behind the import path ( gets boring after a while )

**Additional context**
In this screenshot, you can see it defaults to `v1` even though I have `v2` installed

![](https://i.imgur.com/w4Av2Ir.png)

![](https://i.imgur.com/QzRT5m0.gif)

![](https://i.imgur.com/NEgcCK7.gif)
Repository: PowerToys
Issue: [Functional: Power toys Settings>Fancy Zones>Appearance]: Validations are not applied properly for R,G,B and H,S,V  edit field in Appearance section.
Labels: Issue-Bug,Product-FancyZones,External Dependency,Priority-3,Area-Accessibility,External Dependency-WinUI 3,Status-Blocked,A11yE+D

[Power toys settings- Fancy Zones- Appearance]

User Experience:
It will impact all the users if the edit field is taking alphabet also in numeric value.

Test Environment:
"OS Version: 20221.1000
App Name: Power Toy Preview
App Version: v0.23.0
Screen Reader: Narrator"

Repro-steps:
"1. Open Power Toys Settings App.
2. Navigate to Fancy Zone menu item in left pane and activate it. Fancy Zone will open in right pane.
3. Navigate to 'Zone Highlight Color' and activate it.
4. Navigate to 'Red' edit field and enter any character and verify the issue."

Actual Result:
"Validations are not applied properly for R,G,B and H,S,V  edit field in Appearance section. It is taking alphabets which is not appropriate and the changed value is getting restored with old value.

Note:
Same issue is repro in all the combo box"

Expected Result:
Error validation should be applied to the edit field So that, users will be notified.

[80_Fancy Zones_Appearance_alphabet is also taking as an input.zip](https://github.com/microsoft/PowerToys/files/5329263/80_Fancy.Zones_Appearance_alphabet.is.also.taking.as.an.input.zip)
Repository: pytorch
Issue: Do we have plan to offer C++ binding for prune related features. 
Labels: module: cpp,triaged,enhancement,module: pruning

## 🚀 Feature
On the python side, there is a range of classes/functions to support the pruning functionality of the neural network:
https://pytorch.org/docs/stable/search.html?q=prune&check_keywords=yes&area=default

The motivation to add pruning is mentioned well in this feature request when pruning is added on python side:
https://github.com/pytorch/pytorch/issues/20402

CC the folks who worked on the python side for this: @mickypaganini @ezyang


cc @yf225 @glaringlee
Repository: node
Issue: url.pathToFileURL should not dedup '/' in path
Labels: url,whatwg-url

Found while checking: https://github.com/nodejs/node/issues/35429

Currently it is not possible to have a path represent the file URL `new URL('file:///a//b')` when going through `url.pathToFileURL`. `url.fileURLToPath` does property preserve the `//` in the path already. This causes round trips to be lossy.

<!-- 
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: 14
* **Platform**: OSX
* **Subsystem**: url

### What steps will reproduce the bug?

```mjs
console.log(url.pathToFileURL('/a//b').href);
```

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior?

<!--
If possible please provide textual output instead of screenshots.
-->

```
file:///a//b
```

### What do you see instead?

<!--
If possible please provide textual output instead of screenshots.
-->

```
file:///a/b
```

### Additional information

<!--
Tell us anything else you think we should know.
-->
Repository: rust
Issue: Provide suggestion on E0277 Sized error when `&**`/`as_ref()` would be appropriate
Labels: C-enhancement,A-diagnostics,A-DSTs,T-compiler,A-suggestion-diagnostics,D-newcomer-roadblock

Given

```rust
fn foo(_: &dyn std::error::Error) {}

enum E {
    A(Box<dyn std::error::Error>),
}
fn bar(e: &E) {
    match e {
        E::A(err) => {
            foo(err);
        }
    }
}
```

[`rustc` currently emits](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=a67a4175d237081471dc60cbd5aea953)

```
error[E0277]: the size for values of type `(dyn std::error::Error + 'static)` cannot be known at compilation time
 --> src/main.rs:9:17
  |
9 |             foo(err);
  |                 ^^^ doesn't have a size known at compile-time
  |
  = help: the trait `Sized` is not implemented for `(dyn std::error::Error + 'static)`
  = note: required because of the requirements on the impl of `std::error::Error` for `Box<(dyn std::error::Error + 'static)>`
  = note: required for the cast to the object type `dyn std::error::Error`
```

Trying the usual go-to fixes ([`foo(&err)`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=aa7e29118a0b702909015b1409ced9d8), [`foo(&*err)`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=89e9d9e8f1b5d3049b24de9e388d891c)) produce further errors that aren't helpful either.

The solution to the code is to write [`foo(&**err)`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=48e1e65c049117d9069c77d3a0356c9f) or [`foo(err.as_ref())`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=ca4baa1bce9772ebb510a8d8a8e7864d). We already provide some suggestions for `foo(&err)`, `foo(*err)` and `foo(&*err)` when appropriate and this causes [general confusion to enough people](https://twitter.com/ekuber/status/1313177770659201024) that it would be good to extend that machinery to also handle this case, as well as improving the [`foo(&err)`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=aa7e29118a0b702909015b1409ced9d8) and [`foo(&*err)`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=89e9d9e8f1b5d3049b24de9e388d891c) cases.
Repository: PowerToys
Issue: [Screen Reader - Utility  - PowerToys Run Window]: Narrator does not announce the state of the selected  suggestion list after opening the PowerToys Run Window second time.
Labels: Issue-Bug,Product-PowerToys Run,Area-User Interface,Priority-3,Area-Accessibility,A11yE+D,A11yUsable

[PowerToys Run -Utility  - PowerToys Run Window]

**User Experience:**
If the object role, state(s), properties, boundary, name, and description are not programmatically determinable, it would be difficult for the platforms that provide Accessibility APIs, and would in turn affect the screen reader dependent users to determine the object properties. 

**Test Environment:**
OS Version: 20221.1000
App Name: Power Toy Preview
App Version: v0.23.0
Screen Reader: Narrator

**Repro Steps:**
1. Open Power Toys App
2. Launch Narrator.
3. Navigate to PowerToys Run Button  present on the left side and activate it.
4. Now press "Ctrl + Shift + V" to open PowerToys Run window.
5. PowerToys Run utility window will get open.
6. Focus will land on power launcher edit field.
7. Now enter any data say 'word'. Suggestion list will get appear.
8. Now close the PowerToys Run utility window.
9. Again open the PowerToys Run utility window.
10. Observe the issue.

**Actual Result:**
Narrator does not announce the state of the selected  suggestion list after opening the PowerToys Run Window second time.

**Expected Result:**
Narrator should announce the state of the selected  suggestion list after opening the PowerToys Run Window second time.
When Powertoys run window is getting open 2nd time with the suggestion list and the focus is present on the selected suggestion list, then narrator should announce its state as 'Selected' also.

Note:
Issue does not repro with NVDA (NVDA announce its state as selected)


[Narrator Usable_PowerToys run utility_state selected not announced opening run window 2nd time.zip](https://github.com/microsoft/PowerToys/files/5329433/Narrator.Usable_PowerToys.run.utility_state.selected.not.announced.opening.run.window.2nd.time.zip)
Repository: svelte
Issue: Top-level await
Labels: feature request

This is continuation for #5351.

The problem is that there's no way to render an asynchronously loaded component on SSR. My use-case for asynchronously loaded components is rendering JAM-stack site's content from JSON files. My JSON-files describe page content as blocks, that are different components (type) and their props (data).

I want to have top-level await support for component's `<script>` that will allow awaiting for promises before component's initialization is finished.

I've done [an implementation](https://github.com/joas8211/svelte/tree/top-level-await) for this, but changing initialization asynchronous is quite a breaking change. After the change it's not possible to initialize component with constructor, but instead we have to use a static async builder method `Component.init(options)`. Not being able to initialize synchronously breaks custom elements. Component updating also becomes asynchronous so assignments to props don't get reflected to DOM synchronously. That will also break a lot of code.

If I make async initialization a compiler option, so that it doesn't trash backwards compatibility, would maintainers be willing to merge the changes? Is there any demand for this feature?
Repository: go
Issue: x/review/git-codereview: make 'git codereview mail' run 'git push' using --no-follow-tags
Labels: NeedsDecision

I have the `push.followTags = true` option set in my global gitconfig because it's convenient for my typical git workflows on non-Go projects. But it breaks `git codereview mail`:

```
$ git mail
remote: Processing changes: refs: 9, done
To https://go.googlesource.com/tools
 ! [remote rejected]   HEAD -> refs/for/master (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.0 -> gopls/v0.1.0 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.1 -> gopls/v0.1.1 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.2 -> gopls/v0.1.2 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.3 -> gopls/v0.1.3 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.4 -> gopls/v0.1.4 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.5 -> gopls/v0.1.5 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.6 -> gopls/v0.1.6 (cannot combine normal pushes and magic pushes)
 ! [remote rejected]   gopls/v0.1.7 -> gopls/v0.1.7 (cannot combine normal pushes and magic pushes)
error: failed to push some refs to 'https://go.googlesource.com/tools'
(running: git push -q origin HEAD:refs/for/master)
```

Of course, I can set `push.followTags = false` for all my Go repos on all the machines I use, but it's hard to remember to do that. `git-codereview` could warn if the option isn't set. But better yet, it could just supply the flag `--no-follow-tags` to the `git push` command.

(I didn't check how long the `--no-follow-tags` flag has existed and whether we need to care about git versions older than that.)
Repository: rust
Issue: Allow applying pub(crate) visibility to query accessor functions
Labels: C-enhancement,A-visibility,T-compiler,A-query-system

There are many queries in https://github.com/rust-lang/rust/blob/ea7e131435a960d154e9a5d6a9297039574ffd7d/compiler/rustc_middle/src/query/mod.rs with comments like 'do not invoke this directly - use this other function instead'. If the wrapper method in defined in `librustc_middle,` we could enforce this by applying `pub(crate)` visibility to the generated query accessor methods on `TyCtxt`.

Note that we would still want the fields in `Providers` to be public, so that the query implementation can be defined in a different crate.
Repository: rust
Issue: interface inconsistency with char::is_ascii_... functions
Labels: T-libs-api

There is an interface inconsistency between `char::is_ascii_...` and other `char::is_...` functions. The first all take a reference to a `char`, the latter take a `char`.

This causes point-free style on many `str` functions to be possible with the non-ascii `char::is_...` functions, but not with the `char::is_ascii_...` functions, e.g. see the examples at [`str::split`](https://doc.rust-lang.org/std/primitive.str.html#method.split) for what is possible.

### concrete example
This works:
```rust
let s="a b";
assert_eq!(s.find(char::is_whitespace), Some(1));
```
This does not work:
```rust
let s="a b";
assert_eq!(s.find(char::is_ascii_whitespace), Some(1));
```
The error is:
```text
error[E0631]: type mismatch in function arguments
[...]
expected signature of `fn(char) -> _`
found signature of `for<'r> fn(&'r char) -> _`
note: required because of the requirements on the impl of `std::str::pattern::Pattern<'_>` for
      `for<'r> fn(&'r char) -> bool {std::char::methods::<impl char>::is_ascii_digit}`
```

I think this might be an oversight from porting AsciiExt. I am aware that the API can probably not be changed anymore. But maybe there is another solution?
Repository: angular
Issue: feat(core): narrower event binding types
Labels: area: core,cross-cutting: types,P3

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄 

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->


# 🚀 feature request

### Relevant Package
<!-- Can you pin-point one or more @angular/* packages the are relevant for this feature request? -->
This feature request is for @angular/core.


### Description
With the `strictTemplates: true` Angular compiler setting, it can be tough to deal with native `$event` in event bindings.

### Describe the solution you'd like
I would like to be able to do
- `<input (input)="onInput($event.target.value)">` where `$event` is `InputEvent` or `$event.target`/`$event.currentTarget` is `HTMLInputElement`
- `<button (click)="onClick($event.target.textContent)>Hello <span>World</span></button>` where `$event` is `MouseEvent` and `$event.target`/`$event.currentTarget` is `HTMLButtonElement`

### Describe alternatives you've considered
We can use `$any()` casting, but that is counterintuitive when having `strictTemplates` compilation enabled.

Maybe `$event.currentTarget` is easier to work with than `$event.target` for this feature.
Repository: tensorflow
Issue: Possibility to compile python code when @tf.function is used in TensorFlow 2.x 
Labels: stat:awaiting tensorflower,type:feature,comp:autograph

**System information**
- TensorFlow version (you are using): **2.3.0**
- Are you willing to contribute it (Yes/No): **No**

**Describe the feature and the current behavior/state.**

With TensorFlow 2.x, eager mode is enabled by default, so it is essential to use @tf.function to speed up the performance.
tf.function decorator needs access to the python source code, therefore it makes it impossible to compile our python code and create an executable python build (binary) because the decorator (autograph) always needs access to the python source code. This issue makes it impossible to obfuscate the code and can create a security concern at some situations.  


**Will this change the current api? How?**

Probably yes, but if there is any workaround with the current api, please let me know!


**Who will benefit with this feature?**

Anyone who deploys a deep learning solution in the customer site or cloud or willing to create code obfuscation
Repository: flutter
Issue: Write tests to track reuse of oldLayer mechanism in PaintingContext
Labels: a: tests,framework,engine,P2,team-engine,triaged-engine

The PaintingContext has a number of methods to push a new compositing layer into the scene description via methods such as `PaintingContext.pushClipRect(...)`. The last parameter of these methods is an optional reference to the engine layer that was created on the previous call to that method from the same RenderObject, typically named `oldLayer`.

Currently, the use of this oldLayer mechanism is on the honor system as its optional nature means that code in the framework never really needs to save the prior layers and send them back down in terms of producing the correct output.

With the introduction of code to [track the stable parts of a Flutter Engine scene](https://github.com/flutter/flutter/issues/33939) via these oldLayer objects, it will become more important for the framework to actually save the previous layer objects and pass them down in subsequent push*Layer methods. If this is not done then the engine will have to assume that the layer represents brand new content that has not appeared in previous scenes and it may spend time and (battery) energy redrawing pixels that haven't changed.

We can manually look for such cases where there are calls to any of the pushLayer methods that don't save the return value, but we have no way to test for compliance.

We should be able to write tests that pump a tree of widgets into the widget tester and then pump them again through a PaintingContext that can detect if oldLayer parameters are used in all cases. This will help us both to initially find code that does not save and reuse the layers and also to track them for regressions over time.
Repository: godot
Issue: OS Class Bugs on Linux
Labels: topic:core

**Godot version:**
3.2.3 stable


**OS/device including version:**
KaOS (Arch Linux)


**Issue description:**

Using shell open produces error telling the user the path to the project doesnt exits:
```
OS.shell_open("<godot_executable_path> -d --path <project_folder_path>")
```

Using Shell execute ignore passed arguments

```
OS.execute(OS.get_executable_path(),PoolStringArray(["-d","-w","--resolution 720x480"]),false)
```

placing `OS.get_cmd_args()` after the `OS.execute`, produces `[--args]`

**Steps to reproduce:**

Mentioned above.

**Minimal reproduction project:**

[unknown.multipleinstance.zip](https://github.com/godotengine/godot/files/5330629/unknown.multipleinstance.zip)
Repository: PowerToys
Issue: Image Adjusters for Desktop Wallpaper -or- Inactive Windows
Labels: Idea-New PowerToy

## 📝 Provide a description of the new feature


**Expected Behavior**

Brightness/Contrast, Gamma, Sharpness controls for whatever image (or solid color) is currently assigned to the desktop, These controls would, in effect, turn the Desktop itself into an _**image filter,**_ so that any new desktop appearance would still be adjusted the same way.

A significant enhancement -- or a separate tool -- would be to image-adjust all the windows that don't have focus. They could be rendered with different brightness/contrast, gamma, sharpness, or even transparency. 

If individual window settings were possible, that would be even more useful -- each application gets a dab of metadata that sets how it will be displayed over the desktop when it is not active. Some windows could turn into translucent flat panels, while others are dimmed but still visible, and others lose sharpness just enough so they can't be read by people nearby.


**Usage Scenarios**

Other than aesthetic amusement, it is often useful to DIM the desktop when running certain image editing software. Also, if the desktop is used to display sensitive information, image filtering could obscure desktop contents. 

Adjusting background windows would be especially useful during group sessions. 

Window-specific adjustments, saved with each app, would be even more useful during group sessions, as described above.


But for starters, I would dearly love to be able to **_put a beautiful photo on my desktop and then darken it and reduce contrast_** so it doesn't dominate. Currently I do this by editing dozens of wallpaper pictures, and that's a drag.

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: godot
Issue: Can't access constant in the parent class inside a static function
Labels: bug,topic:gdscript,confirmed

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.2.3.stable
<!-- Specify commit hash if using non-official build. -->


**OS/device including version:**
Windows 10
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->


**Issue description:**
Trying to use a constant in the parent class using static function returns an error

I strongly believe that this is a bug, as you can access a constant within the same class using static function
and you can use static function from the parent class, so it's probably not a dependency related stuff
<!-- What happened, and what was expected. -->


**Steps to reproduce:**
1. Create a parent class and declare a constant
2. Create a child class and a static function
3. Try to print the constant inside the static function


**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
Repository: rust
Issue: Handle type errors in fn args caused by type parameter divergence
Labels: C-enhancement,A-diagnostics,T-compiler,D-newcomer-roadblock

[Given](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=af5fba0e96614644f655970036f29635)

```rust
fn foo<T>(a: T, b: T) {}

fn main() {
    foo(42, "");
}
```

we currently emit

```
error[E0308]: mismatched types
 --> src/main.rs:4:13
  |
4 |     foo(42, "");
  |             ^^ expected integer, found `&str`
```

It should be closer to

```
error[E0308]: mismatched types
 --> src/main.rs:4:13
  |
4 |     foo(42, "");
  |         --  ^^ expected integer, found `&str`
  |         |
  |         expected because this is an integer
  |
note: all arguments that reference the same type parameter must be of the same type
  |
1 | fn foo<T>(a: T, b: T) {}
  |        -  -     - this argument was found to be `&str`
  |        |  |
  |        |  this argument was found to be an integer
  |        this type parameter was found to be an integer and `&str`
```