sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Backup Save Location cannot be Changed
Labels: Issue-Bug,Product-Settings,Area-User Interface,Priority-1

### Microsoft PowerToys version

0.71.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

I've setup a backup location directory with a lengthy path (some 145 characters) and as a result the button to change the location is kicked out of the location and becomes inaccessible.

I think this issue might exist in previous versions too; I have not checked.


![image](https://github.com/microsoft/PowerToys/assets/16124883/5b9f262a-da6a-47d6-9942-dfba4c94ecc1)


### ✔️ Expected Behavior

There should be a 'change backup location' button.

### ❌ Actual Behavior

There is no 'change backup location' button.

### Other Software

_No response_
Repository: rust
Issue: Explain how to fix “no field on type” on a TAIT / ATPIT typed value
Labels: A-diagnostics,T-compiler,A-impl-trait,F-type_alias_impl_trait,D-terse,F-impl_trait_in_assoc_type

### Code

```Rust
#![feature(impl_trait_in_assoc_type)]

pub trait Transaction {
    type Check: 'static;
    fn check(&self) -> Self::Check;
    fn commit(&self, check: Self::Check);
}

pub mod foo {
    pub struct Foo;

    struct FooC {
        field: (),
    }

    impl super::Transaction for Foo {
        type Check = impl Sized;

        fn check(&self) -> Self::Check {
            FooC { field: () }
        }

        fn commit(&self, check: Self::Check) {
            assert_eq!(check.field, ());
        }
    }
}
```


### Current output

```Shell
error[E0609]: no field `field` on type `<Foo as Transaction>::Check`
  --> src/lib.rs:24:30
   |
24 |             assert_eq!(check.field, ());
   |                              ^^^^^

For more information about this error, try `rustc --explain E0609`.
error: could not compile `playground` (lib) due to previous error
```


### Desired output

```Shell
help: to access fields of the underlying type `FooC`, coerce the value to it:
      `(check as FooC).field`
```


### Rationale and extra context

If users are not given this advice, it will not be obvious how to proceed; they may think that it is not even possible. For me at least, it is obvious _only in hindsight_ that

* the incoming `check` argument is of a different type than the outgoing return value, and
* a type coercion would solve the problem here.

The alternate mental model I was working with before I understood the problem was something like:

* `Self::Check` is an alias for a particular `impl Sized`
* which, *only this `impl` or module knows* (being in the defining scope of the `impl Trait`), is an alias for `FooC`

so `check` should be of type `FooC` already. Now that I understand what's actually going on, it makes much more sense that the compiler would work this way (scope-dependent type equality would be a nightmare), but it wasn't obvious when I started.

### Other cases

_No response_

### Anything else?

This exact same problem happens with TAIT; I just think it's just a little less clear and more important for associated types in traits.

Another detail to consider is what the output should be when the underlying type does not have such a field (or method). I think there should still be a similar hint, but phrased differently — in general, this hint should show up whenever

* an opaque type is used,
* in a place where the coercion would be allowed,
* at a use site which does not itself cause a coercion already (e.g. a generic rather than concrete function parameter).

@rustbot label +A-impl-trait +F-type_alias_impl_trait
Repository: go
Issue: x/tools/go/analysis: report informative error message about gob.Register(fact) conflicts
Labels: NeedsInvestigation,Tools

gob.Register has an unfortunately unfixable bug whereby two packages registering types `*p/a.T` and `*q/a.T` get a panic because internally their names are both mapped to `*a.T`. Witness: https://go.dev/play/p/HtGLdqhHvaG

The analysis.Validate function has the opportunity to detect and report this confusing problem with a helpful explanation. Basically one of the types must be renamed.

@hyangah
Repository: flutter
Issue: dart-internal drone builds should use the branched recipe bundle
Labels: team-infra,P2,triaged-infra

https://flutter-dashboard.appspot.com/#/build?repo=engine&branch=flutter-3.13-candidate.0 has green drone builders, when they should have failed due to the missing recipe bundle.

To ensure builds are using matching recipe versions, the drone build configs should use the branched recipe bundle.
Repository: vscode
Issue: Default log level does not work in vscode.dev
Labels: bug,log,web

Repro:

1. Open https://insiders.vscode.dev/github/microsoft/vscode-markdown-languageservice
2. Set default log level to trace
3. Reload the window
4. Open set log level, it shows the default is trace but the active is info

![image](https://github.com/microsoft/vscode/assets/2193314/4f4d16f5-4d43-4f70-ba94-cfcfb320a9cf)
Repository: kubernetes
Issue: Statefulset with podManagementPolicy=Parallel ignores minReadySeconds on statefulset rollout update
Labels: kind/bug,sig/apps,priority/important-longterm,triage/accepted

### What happened?

Deployed a statefulset with `podManagementPolicy: Parallel` and with `minReadySeconds: 15`, have waited for all the pods being ready. Then, issued a rollout restart on the sts.

### What did you expect to happen?

Expected that the rollout update happens the same way as with `podManagementPolicy: OrderedReady`, that is the last pod is terminated, then restarted, waited to be ready, and then waiting for the extra `minReadySeconds` to pass before moving the next pod. Instead, once the pod became ready, the rollout process instantly moved to the next pod, ignoring the `minReadySeconds` setting.

### How can we reproduce it (as minimally and precisely as possible)?

Apply the following sts:

```yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web
spec:
  minReadySeconds: 10
  podManagementPolicy: Parallel
  replicas: 5
  selector:
    matchLabels:
      application: web
  serviceName: web
  template:
    metadata:
      labels:
        application: web
    spec:
      containers:
      - image: nginx
        name: web
  updateStrategy:
    type: RollingUpdate
```

Wait until all pods become ready. Then, issue a rollout restart:

```
$ kubectl rollout restart sts web
```

Then, observe that as soon a pod enters ready state, the upgrade process moves to the next pod, ignoring `minReadySeconds` value.

If the sts is created with default `podManagementPolicy`, the update procedure works as expected.


### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-14T09:53:42Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-15T00:36:28Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ uname -a
Linux k-desktop 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
```

</details>


### Install tools

<details>
kind
</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: vscode
Issue: Realtime Performance icons always show up when the view is visible
Labels: bug,workbench-views

Repro::

1. Open a node project
2. Debug
3. Open the debug sidebar

The realtime performance icons are always showing, even when not hovered:

![image](https://github.com/microsoft/vscode/assets/2193314/963cae1c-92bb-42c3-99dc-c908510144c2)
Repository: go
Issue: x/pkgsite: consider surfacing fork status and activity details vs upstream
Labels: FeatureRequest,pkgsite

While in some cases a fork may actually be the better, more maintained, more adopted version, when the parent does have more activity than the fork, it would probably be helpful to show the parent in the Links or elsewhere in the header section of the pkg page

Somewhat related also would be to rank it lower in search results

Example:

https://pkg.go.dev/search?q=fortio&m=

shows

https://pkg.go.dev/github.com/lemonlinger/fortio
and
https://pkg.go.dev/github.com/CrowdStrike/fortio
and
https://pkg.go.dev/github.com/MUzairS15/fortio

all stale forks with minor to no updates and not the original

https://pkg.go.dev/fortio.org/fortio
 
which isn't at all on the list (only sub packages are somehow)

### Screenshot

<img width="1069" alt="Screenshot 2023-07-11 at 12 14 40 PM" src="https://github.com/golang/go/assets/3664595/34a0fc9c-7324-47c9-b337-18a5a18eb693">

<img width="977" alt="Screenshot 2023-07-11 at 12 15 15 PM" src="https://github.com/golang/go/assets/3664595/61f1cc3f-992d-4acb-ae86-419dc832a6da">


### What did you expect to see?

<img width="1007" alt="Screenshot 2023-07-11 at 12 15 47 PM" src="https://github.com/golang/go/assets/3664595/a93ed29d-9ab8-417f-8682-b9d7d9515696">
Repository: storybook
Issue: [Bug]: (Storybook v7) React autodocs incorrectly generating with TypeScript >= v5.1.3
Labels: bug,typescript,argtypes

### Describe the bug

Hi there, we're seeing a difference in API document generation of component props. HTML attributes are being added. See below. Is this a known issue?

Current:
![without-ts5](https://github.com/storybookjs/storybook/assets/12474067/f419caf6-d5d3-486a-8847-8a39af085336)

Prior to TypeScript v5:
![with-ts5](https://github.com/storybookjs/storybook/assets/12474067/9d2d615a-2130-4b5c-98ef-b1647d4009d4)


### To Reproduce

Please see open PR below:

https://github.com/zendeskgarden/react-components/pull/1554

and the staging deployment where we see the issue:

https://64ad6f40bf19b7052b7f32ba--zendeskgarden-react-components.netlify.app/?path=/docs/packages-accordions-accordion--docs

For the expected results, see:

https://zendeskgarden.github.io/react-components

### System

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: [export] tensor creation ops burn in device
Labels: triaged,enhancement,oncall: pt2,oncall: export

```
import torch
import torch._export

def foo(x):
    return x + torch.ones(2, 2)

e = torch._export.export(foo, (torch.ones(2, 2),))
print(e.graph_module.graph)
```
produces:
```
graph():
    %arg0_1 : [num_users=3] = placeholder[target=arg0_1]
    %sym_size_int : [num_users=1] = call_function[target=torch.ops.aten.sym_size.int](args = (%arg0_1, 0), kwargs = {})
    %sym_size_int_1 : [num_users=1] = call_function[target=torch.ops.aten.sym_size.int](args = (%arg0_1, 1), kwargs = {})
    %eq : [num_users=1] = call_function[target=operator.eq](args = (%sym_size_int_1, 2), kwargs = {})
    %scalar_tensor_default : [num_users=1] = call_function[target=torch.ops.aten.scalar_tensor.default](args = (%eq,), kwargs = {})
    %_assert_async_msg : [num_users=0] = call_function[target=torch.ops.aten._assert_async.msg](args = (%scalar_tensor_default, Input arg0_1.shape[1] is specialized at 2), kwargs = {})
    %eq_1 : [num_users=1] = call_function[target=operator.eq](args = (%sym_size_int, 2), kwargs = {})
    %scalar_tensor_default_1 : [num_users=1] = call_function[target=torch.ops.aten.scalar_tensor.default](args = (%eq_1,), kwargs = {})
    %_assert_async_msg_1 : [num_users=0] = call_function[target=torch.ops.aten._assert_async.msg](args = (%scalar_tensor_default_1, Input arg0_1.shape[0] is specialized at 2), kwargs = {})
    %full_default : [num_users=1] = call_function[target=torch.ops.aten.full.default](args = ([2, 2], 1), kwargs = {dtype: torch.float32, layout: torch.strided, device: cpu, pin_memory: False})
    %add_tensor : [num_users=1] = call_function[target=torch.ops.aten.add.Tensor](args = (%arg0_1, %full_default), kwargs = {})
    return (add_tensor,)
```

Note the following line burns in `device=cpu`.
```
    %full_default : [num_users=1] = call_function[target=torch.ops.aten.full.default](args = ([2, 2], 1), kwargs = {dtype: torch.float32, layout: torch.strided, device: cpu, pin_memory: False})
```

These kwargs are optional; I'd like for them to not show up in the graph if the user didn't specify them.



cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @ydwu4 @wconstab
Repository: PowerToys
Issue: Connection issues, windows 11 to windows 10 (no admin rights/work laptop)
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.71.0

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Only working from work pc to the main pc not backwards and when it works it shows the mouse in both computers the work computer and the main pc at the same time. it has worked in the past several times just fine. Attempt to connect to both computers or just to the main computer from a work laptop with windows 10

EDIT:

I apologize for not expressing myself correctly in the initial report, the problem I am having is due to firewalls I believe, I have a work computer and a main PC and had wished to use the mouse from the main pc on the work computer, it initially worked and connected right away, I do not have admin rights for this work computer but powertoys installed on it and mwb was working perfectly until one day it stopped and never reconnected again, nothing that I believe has to do with particular settings, I even tried connecting with IP address mapping with no improvement, this happens while connected on the same network, with or without a VPN. Is this because I don't have the admins rights to allow firewall ports on the app, i did get a notification for that more than once but as mentioned couldn't give it the rights due to not having credentials for it

### ✔️ Expected Behavior

Connection successful from main pc to work laptop as it has worked previously.

### ❌ Actual Behavior

Only working from work pc to the main pc not backwards and when it works it shows the mouse in both computers the work computer and the main pc at the same time.

### Other Software

_No response_
Repository: vscode
Issue: view is not updated for markdown cell content change
Labels: bug,notebook-markdown

1. set `"ipynb.pasteImagesAsAttachments.enabled": false` (this setting hides the bug)
2. open a notebook and create a markdown cell with content and render the preview for that cell
3. split the editor `ctrl+\`
4. edit the markdown cell in one of the editors while keeping the other in preview
🐛 preview of the cell does not update
Repository: flutter
Issue: [file_selector/image_picker] [web] Use `showPicker` API.
Labels: platform-web,p: image_picker,package,c: proposal,P3,p: file_selector,team-web,triaged-web

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

The current implementation of both `file_selector` and `image_picker` for the web use a simulated `click` event on the `input type=file` driving them to trigger the file selection, like so:

* https://github.com/flutter/packages/blob/6fbc9f9018b2053dffd5f16b84e005bf5677f6fe/packages/file_selector/file_selector_web/lib/src/dom_helper.dart#L54-L56


### Proposal

Use the new `showPicker` API whenever it's supported (for now, this is Safari 16+).

See documentation:

* [MDN / showPicker](https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/showPicker)
Repository: rust
Issue: TAIT: typed patterns don't count as defining uses
Labels: A-impl-trait,C-bug,F-type_alias_impl_trait

The following code compiles successfully:

```rust
#![feature(type_alias_impl_trait)]

pub struct Foo {
    field: (),
}

pub type Tait = impl Sized;

pub fn func1(input: Tait) {
    let Foo { .. } = input;
}

pub fn func2(input: Tait) {
    let Foo { field: _ } = input;
}

pub fn func3(input: Tait) {
    let Foo { field } = input;
}
```

However, if `func3` is commented out, then neither `func1` nor `func2` suffices to constrain `Tait`:

```
error: unconstrained opaque type
 --> src/lib.rs:7:17
  |
7 | pub type Tait = impl Sized;
  |                 ^^^^^^^^^^
  |
  = note: `Tait` must be used in combination with a concrete type within the same module
```

It seems that the pattern only counts as actually constraining the type if one of the fields is actually destructured. The same behavior happens for tuple types; e.g. `let () = input;` does not constrain.

Of course, it would be difficult for this to actually matter, since nothing ever _produces_ a value of type `Tait`, so none of the functions can be called, but this might be a sign of a deeper problem (or just something to nail down about TAIT semantics), so I figured I'd report it anyway. I discovered it while minimizing #113594.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.73.0-nightly (8ca44ef9c 2023-07-10)
binary: rustc
commit-hash: 8ca44ef9caa4049d584fbbce218c219cdca33a2f
commit-date: 2023-07-10
host: x86_64-apple-darwin
release: 1.73.0-nightly
LLVM version: 16.0.5
```

@rustbot label +A-impl-trait +F-type_alias_impl_trait
Repository: PowerToys
Issue: Network profiler for apps
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

A feature that allows users selectively allow which apps on their laptop can use network/cellular data/wifi, allowing them to save bandwidth. Users can easily see which apps are using data, and choose to block those apps from using data over cellular or Wi-Fi. This can prevent a significant amount of data usage.

### Scenario when this would be used?

This feature can be especially useful on a limited data plan avoiding overage charges and allowing me to use my data usage on task that is most important to me. Additionally, it can protect privacy by disabling apps that may collect data in the background without my knowledge.

### Supporting information

_No response_
Repository: PowerToys
Issue: Always On Top: Add toggle icon in window title bar
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Add an icon next to the traditional minimise, maximise, close icons in window title bars that allows users to toggle pinning a window on top.

The icon can be an open (unfilled) circle for an unpinned window (the default), which changes to a closed (filled) circle when pinned.

Alternatively, it could be an icon of a pin (although this does not follow the minimalistic design of the minimum, maximum, close icons).

### Scenario when this would be used?

This would be available at all times. It is natural, intuitive and quicker to click to pin the window itself, rather than clicking to activate a window and then pressing the activation shortcut.

The intent is to move from the 3 traditional window icons to 4 with its inclusion.

### Supporting information

_No response_
Repository: pytorch
Issue: DISABLED test_homogeneous_attributes (__main__.TestFSDPMiscMultiThread)
Labels: oncall: distributed,module: flaky-tests,skipped,module: fsdp

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 6 failures and 2 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_homogeneous_attributes`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `distributed/fsdp/test_fsdp_misc.py`

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: material-ui
Issue: [RSC] The entire `@mui/joy/node` bundle is included in the client bundle when Joy UI component is being imported into a RSC
Labels: performance,priority: important,package: material-ui,package: base-ui,package: joy-ui,scope: code-infra

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://github.com/mwskwong/mui-joy-nested-grid-in-server-component

Steps:

1. Create a Next.js app router app
2. Import any MUI Joy components in `page.tsx`, which is my default RSC.
3. Build the project and observe the tree map of the client bundle. The entire `@mui/joy/node` will be included.

### Current behavior 😯

The node bundle of ` @mui/joy` is being bundled in the client bundle.

### Expected behavior 🤔

The client-side bundle + tree-shaking should be used instead.

### Context 🔦

Doesn't seem to affect functionality though. Just that the client bundle becomes massive. 

Not sure if only Joy is affected. Or all MUI packages.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.22621
  Binaries:
    Node: 18.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22621.1928.0), Chromium (114.0.1823.58)
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.7
    @mui/core-downloads-tracker:  5.14.0
    @mui/joy: ^5.0.0-alpha.87 => 5.0.0-alpha.87
    @mui/private-theming:  5.13.7
    @mui/styled-engine:  5.13.2
    @mui/system:  5.14.0
    @mui/types:  7.2.4
    @mui/utils:  5.13.7
    @types/react: 18.2.14 => 18.2.14
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.1.6 => 5.1.6
```
</details>
Repository: rust
Issue: Require (and potentially enforce) attribute-style `// issue: rust-lang/rust#12345` comments in issue-related tests
Labels: A-testsuite,T-bootstrap

This comes as a followup to #113583

The goal is to add meta comments to all tests related to an issue or ICE (e.g. regression tests) so that we can programmatically extract this information. For example:

```rust
// issue: rust-lang/rust#12345
// issue: rust-lang/rust#6789
// ice: rust-lang/rust#1234

// sample link to different repo:
// issue: rust-lang/cargo:1234   
```

We should make having this a goal for all regression tests going forward, and as a requirement with any renaming that might happen to suit #113583. We can likely do some of this programmatically.