sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: PowerToys Run - Additional Folders & Drives to look up files and applications
Labels: Run-Results (Indexer)

### Description of the new feature / enhancement

I have many files, applications, and documents running off several drives, however it doesn't seem like PowerToys Run will allow me to search on other drives for these items.  

### Scenario when this would be used?

Locating applications which are installed on other drives
Documents and files on other drives
Overall customizability to add arbitrary locations to the PowerToys Run search index

### Supporting information

_No response_
Repository: kubernetes
Issue: We should delete unused functions on internal (unsupported for external users, not staging/...) pkgs.
Labels: sig/architecture,area/code-organization,needs-triage

non-staging is effectively internal and we DO NOT make API guarantees there.  We just can't.

_Originally posted by @thockin in https://github.com/kubernetes/kubernetes/issues/111628#issuecomment-1203117518_
Repository: storybook
Issue: custom-elements-manifest -> attributes are overriden by members
Labels: bug,web-components

**Describe the bug**
The members that are contained in the manifest override other defined properties. As all attributes in [FAST](https://github.com/microsoft/fast) are also members of a class, all attributes are always overriden by the members while analyzing the manifest.

See [the extractArgTypesFromElements](https://github.com/storybookjs/storybook/blob/7035ea7389393da041985ebc491ee58dedb50d06/code/renderers/web-components/src/docs/custom-elements.ts#L148) method defined by _storybook/web-components_. The order used to define the class overrides the attributes.

**Solution proposal**
I would like to change the order of the map method to this:

```typescript
export const extractArgTypesFromElements = (tagName: string, customElements: CustomElements) => {
  const metaData = getMetaData(tagName, customElements);
  return (
    metaData && {
      ...mapData(metaData.members, 'properties'),
      ...mapData(metaData.properties, 'properties'),
      ...mapData(metaData.attributes, 'attributes'),
      ...mapData(metaData.events, 'events'),
      ...mapData(metaData.slots, 'slots'),
      ...mapData(metaData.cssProperties, 'css custom properties'),
      ...mapData(metaData.cssParts, 'css shadow parts'),
    }
  );
};
```

This ensured in first tests that properties and members are overriden by attributes, thus correctly displayed in the Storybook.


**Pull Request**
I'm open to create a PR for this change. I just wanted to verify that a change like this is accepted before I submit a PR.

**Environment Info**
```
  System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
  Binaries:
    Node: 16.16.0 - ~\AppData\Roaming\nodejs\node.EXE
    npm: 8.11.0 - ~\AppData\Roaming\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (100.0.1185.39)
  npmPackages:
    @storybook/addon-actions: ^6.5.9 => 6.5.9
    @storybook/addon-essentials: ^6.5.9 => 6.5.9
    @storybook/addon-links: ^6.5.9 => 6.5.9
    @storybook/addons: ^6.5.9 => 6.5.9
    @storybook/builder-webpack4: ^6.5.9 => 6.5.9
    @storybook/core-common: ^6.5.0 => 6.5.9
    @storybook/csf-tools: ^6.5.0 => 6.5.9
    @storybook/manager-webpack4: ^6.5.9 => 6.5.9
    @storybook/store: ^6.5.0 => 6.5.9
    @storybook/test-runner: ^0.5.0 => 0.5.0
    @storybook/theming: ^6.5.9 => 6.5.9
    @storybook/web-components: ^6.5.9 => 6.5.9
```
Repository: material-ui
Issue: Tabs component Typescript types can't be extended for custom variants
Labels: new feature,component: tabs,customization: theme

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

As shown in this sandbox: https://codesandbox.io/s/mui-tabs-variant-issue-lk9v5c?file=/src/App.tsx 

While I can add a new variant for `Button` and have it pass type checks via module augmentation, if I try the same thing for `Tabs` with:
```
declare module "@mui/material/Tabs" {
  interface TabsPropsVariantOverrides {
    outlined: true;
  }
}
```
both the theme declaration and component `variant` prop don't pass type checks.

### Expected behavior 🤔

I should be able to add a custom variant to `Tabs` and have it pass TS type checks. I shouldn't have to `@ts-ignore` it.

### Steps to reproduce 🕹

Steps:

1. Go to this sandbox: https://codesandbox.io/s/mui-tabs-variant-issue-lk9v5c?file=/src/App.tsx:1018-1055
2. Note `variant` displays an error


### Context 🔦

I'm creating a new custom theme variant for tabs.

### Your environment 🌎

@mui/material 5.9.3

typescript 4.5.5
Repository: go
Issue: x/tools/go/analysis: change `RelatedInformation` to work without fileset
Labels: NeedsInvestigation,Tools,Analysis

[`RelatedInformation`]( https://pkg.go.dev/golang.org/x/tools/go/analysis#RelatedInformation
) is used to add information related to a diagnostic.  Currently it is defined as:

```
type RelatedInformation struct {
	Pos     token.Pos
	End     token.Pos
	Message string
}
```

I believe this corresponds to LSP's [`DiagnosticRelatedInformation`](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnosticRelatedInformation) and the `Pos`/`End` would be translated to LSP  `Location`.

The use of `token.Pos` in `RelatedInformation` implies we need to depend on a certain `token.FileSet`. If the positions of the related information belong to the same package, that's fine. Otherwise, it is awkward to use. For example, I hoped I could annotate reports on functions that transitively call known vulnerable symbols. But the vulnerable symbols may be in different package and we learned about it from Facts generated by the analyzer run on the package.

Will `Position` be too inefficient?

cc @adonovan @timothy-king
Repository: angular
Issue: Form control value is null when initialized with undefined
Labels: area: forms,P3,bug,forms: strictly typed,canonical

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When you initialize a `FormControl` with an `undefined` value (initial state) the `FormControl#value` is null.
The value is `null` instead of `undefined` to be short

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-x37dzv

### Please provide the exception or error you saw

```true
If you try to do test something like the test will fail


// control was initialized with undefined
expect(control.value).toBe(undefined) // <-- in fact, this is null
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 14.1.0
Node: 16.16.0
Package Manager: npm 8.15.1
OS: win32 x64

Angular: 14.1.0
... animations, cdk, cli, common, compiler, compiler-cli, core 
... forms, material, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------      
@angular-devkit/architect       0.1401.0
@angular-devkit/build-angular   14.1.0
@angular-devkit/core            14.1.0
@angular-devkit/schematics      14.1.0
@angular/flex-layout            14.0.0-beta.40
@schematics/angular             14.1.0
rxjs                            7.5.6
typescript                      4.7.4
```


### Anything else?

_No response_
Repository: axios
Issue: Support customisation of supported protocols
Labels: state::triage

#### Is your feature request related to a problem? Please describe.

Since version 0.27.0 the supported protocols are a fixed set specified in platform.
https://github.com/axios/axios/blob/cd8989a987f994c79148bb0cacfca3379ca27414/lib/platform/browser/index.js#L42

We are using axios in a capacitor app that uses the special capacitor protocol. 

#### Describe the solution you'd like
We need an option to specify additional supported protocols.

#### Describe alternatives you've considered
Use version 0.26.2 as a workaround.
Repository: pytorch
Issue: DecompositionInterpreter creates invalid graphs for FX graph modules created with torch.fx.symbolic_trace
Labels: triaged,module: fx,fx

### 🐛 Describe the bug

```py
import torch
from torch.fx.experimental.proxy_tensor import DecompositionInterpreter

class Model(torch.nn.Module):

    def __init__(self):
        super(Model, self).__init__()
        self.bn = torch.nn.BatchNorm2d(3)
        self.relu = torch.nn.ReLU()

    def forward(self, inp):
        o = self.bn(inp)
        o = self.relu(o)
        return o

input = torch.randn(2, 3, 4, 5)
m = Model()
gm = torch.fx.symbolic_trace(m)

graph = torch.fx.Graph()
DecompositionInterpreter(gm, graph).run(input)
print(graph)
```
```py
graph():
    %inp : [#users=1] = placeholder[target=inp]
    %native_batch_norm_default : [#users=3] = call_function[target=torch.ops.aten.native_batch_norm.default](args = (%inp, Parameter containing:
tensor([1., 1., 1.], requires_grad=True), Parameter containing:
tensor([0., 0., 0.], requires_grad=True), tensor([0.0085, 0.0026, 0.0262]), tensor([1.0102, 1.0085, 0.9952]), True, 0.1, 1e-05), kwargs = {})
    %getitem : [#users=1] = call_function[target=operator.getitem](args = (%native_batch_norm_default, 0), kwargs = {})
    %getitem_1 : [#users=0] = call_function[target=operator.getitem](args = (%native_batch_norm_default, 1), kwargs = {})
    %getitem_2 : [#users=0] = call_function[target=operator.getitem](args = (%native_batch_norm_default, 2), kwargs = {})
    %relu_default : [#users=2] = call_function[target=torch.ops.aten.relu.default](args = (%getitem,), kwargs = {})
    %detach_default : [#users=1] = call_function[target=torch.ops.aten.detach.default](args = (%relu_default,), kwargs = {})
    %detach_default_1 : [#users=0] = call_function[target=torch.ops.aten.detach.default](args = (%detach_default,), kwargs = {})
    return relu_default
```
Arguments to the `native_batch_norm_default` call contain repr of parameters instead of being referenced as constants.

The source of this problem is that `DecompositionInterpreter` uses `torch.fx.proxy.GraphAppendingTracer` instead of `torch.fx.experimental.proxy_tensor.PythonKeyTracer`.

### Versions

Latest master

cc @ezyang @SherlockNoMad @davidberard98
Repository: yt-dlp
Issue: Allow an immediate break when a server responds with HTTP Error 429
Labels: enhancement,triage,core:downloader

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2022.07.18** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

It seems that yt-dlp will continue to cycle through fragment retries even when a server responds with a rate-limiting rejection such as '`HTTP Error 429`'. This seems time-wasting and counterproductive to potentially having to wait for that rate-limiting block to expire.

My request is for a feature or option to not allow retries to continue to cycle when the server is responding (or perhaps repeatedly responding?) with status error 429. 

Thank you for your time and consideration. My apologies if I could not find a duplicate of this request.

### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
Not a complete verbose, but an example snippet of the unnecessary retries:

[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 182
[download] Destination: C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4
[debug] File locking is not supported. Proceeding without locking
WARNING: The download speed shown is only of one thread. This is a known issue and patches are welcome
[download] C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4.part-Frag179 has already been downloaded
[download] C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4.part-Frag180 has already been downloaded
[download]  97.8% of ~774.51MiB at   91.97MiB/s ETA  Unknown (frag 178/182)[download] C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4.part-Frag181 has already been downloaded
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 178 (attempt 1 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 182 (attempt 1 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 178 (attempt 2 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 182 (attempt 2 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 178 (attempt 3 of 999) ...
```
Repository: rust
Issue: x86_64-unknown-linux-gnu using 'target-feature=+crt-static' exits with: Segmentation fault (core dumped).
Labels: A-linkage,O-linux,C-bug,A-target-feature

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

<!--
I tried this code:

```rust
<code>
```
-->

I expected to see this happen: complied program with static linking runs normally.

Instead, this happened: 

* when i debug, it exits with: `Stop reason: signal SIGSEGV: invalid address (fault address: 0xe5)`
* when i run the executable directly, it exits with: `Segmentation fault (core dumped)`

But when i debug the executable without static linking, it works well. And when i build with '--target x86_64-unknown-linux-musl', it works well, too.

I think it's not a code error, but some config problems.

### 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.59.0 (9d1b2106e 2022-02-23)
binary: rustc
commit-hash: 9d1b2106e23b1abd32fce1f17267604a5102f57a
commit-date: 2022-02-23
host: x86_64-unknown-linux-gnu
release: 1.59.0
LLVM version: 13.0.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

<img width="979" alt="image" src="https://user-images.githubusercontent.com/49806272/182656129-c7a05510-9002-4206-989b-80d009c603be.png">

</p>
</details>
Repository: next.js
Issue: [NEXT-481] preview doesn't work when there are more than 1 nextjs instance running
Labels: bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

npx --no-install next info

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Wed Jul 13 21:34:30 UTC 2022
    Binaries:
      Node: 16.16.0
      npm: 8.11.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 12.2.4-canary.9
      eslint-config-next: 12.2.0
      react: 17.0.2
      react-dom: 17.0.2

warn  - Latest canary version not detected, detected: "12.2.4-canary.9", newest: "12.2.4-canary.10".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue


### What browser are you using? (if relevant)

Google Chrome 103.0.5060.134 (Official Build) (64-bit) 

### How are you deploying your application? (if relevant)

Kubernetes (AWS EKS) running node:16-alpine Docker image with "next start" as main process (pid 1)

### Describe the Bug

When I have more than 1 instance of Docker container running, "preview" feature intermittently fails and renders usual web-page (last published in Sanity) because of the 2nd instance invalidating the "preview"-cookies by setting them to `empty` value and `expiration` field in the past (see attached diagram).

![preview issue](https://user-images.githubusercontent.com/20296197/182644668-cd979fb1-4f92-4af5-8dc9-39794e222a52.jpg)

It works when there is exactly 1 instance of the application running in cluster.
BUILD_ID is the same for both instance, "preview secret" string is the same (shared via Kubernetes Secret) and using this string it's possible to validate signature of the token stored in `__next_preview_data` using [jwt.io](https://jwt.io)

### Expected Behavior

Several instances shouldn't clear cookies set by another instance.

### Link to reproduction

n/a

### To Reproduce

1. enable preview feature in Sanity Studio and deploy it
2. create simple Nextjs application connected to Sanity CMS
3. deploy multiple Nextjs instances on-premise infrastructure behind the reverse-proxy (a load-balancer)
4. in Sanity Studio try to switch from "editor" to "preview" and watch the requests/responses/cookies

<sub>[NEXT-481](https://linear.app/vercel/issue/NEXT-481/preview-doesnt-work-when-there-are-more-than-1-nextjs-instance-running)</sub>
Repository: rust
Issue: Unclear doctest error when implementing a trait in a different file.
Labels: C-enhancement,A-diagnostics,T-compiler,D-newcomer-roadblock,D-terse

Consider a library with the following directory structure (no playground because multiple files, but [this git repository](https://github.com/mark-schultz/doctest)).

```
src
├── lib.rs
├── module_one.rs
└── module_two.rs
```
where `module_one.rs` is

```rust
#[derive(Clone, Debug)]
pub struct MyStruct {}

pub trait MyTrait {
  fn returns_true(self) -> bool;
}
```
and `module_two.rs` is
```rust
use crate::module_one::{MyStruct, MyTrait};

impl MyTrait for MyStruct {
  /// This doctest has a confusing error message
  ///
  /// ```rust
  /// use doctest::module_one::{MyStruct, MyTrait};
  /// use doctest::module_two::returns_true;
  /// let my_struct : MyStruct = MyStruct {};
  /// assert!(my_struct.returns_true());
  /// ```
  ///
  fn returns_true(self) -> bool {
    true
  }
}
```
The current output of `cargo test --doc` is 

```rust
failures:

---- src/module_two.rs - module_two::MyStruct::returns_true (line 6) stdout ----
error[E0432]: unresolved import `doctest::module_two::returns_true`
 --> src/module_two.rs:8:5
  |
5 | use doctest::module_two::returns_true;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `returns_true` in `module_two`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
```

This error message suggests that the issue is the *visibility* of `returns_true` in `module_two`.
This is not the issue though.
Deleting the entire line `use doctest::module_two::returns_true;` instead fixes the issue.
Repository: TypeScript
Issue: Use snippets for extract refactorings 
Labels: Suggestion,Help Wanted,Domain: Refactorings,Experience Enhancement

# Feature request

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms
- Refactor / refactorings
- Code action

### Problem
Today our extract refactorings run in two stages:

1. Extract to a new constant / function using a placeholder symbol name (such as `newFunction`)
2. Rename the placeholder using a normal rename operation.

This has a few problems:

- If the user quickly types, they end up typing into the editor before the rename input box shows up. This breaks the rename
- This requires two calls to TSServer
- The rename UX can feel a bit jarring since it shows a new box to users 

### Proposal
VS Code now supports including snippets in the workspace edits that extensions provide on refactorings. My proposal is that TS Server uses snippet syntax in the edit returned for extract method/constant so that users immediately start renaming the new function/constant instead of using the two phase flow we have to day 


### Example
For the TS:

```ts
1 + 2;
```

If I select `1 + 2` and select the `extract to function in global scope` refactoring, I should get the following snippet (note that I'm using VS Code's snippet annotation here):

```ts
${1:newFunction}();$0

function ${1:newFunction}() {
    1 + 2;
}
```

Typing would update both places where newFunction is used:


<img width="559" alt="Screen Shot 2022-08-03 at 12 00 34 PM" src="https://user-images.githubusercontent.com/12821956/182688302-f1cf9de4-5a33-4f53-a55f-dd20159e466e.png">

<img width="469" alt="Screen Shot 2022-08-03 at 12 00 39 PM" src="https://user-images.githubusercontent.com/12821956/182688303-92439c27-d865-45b4-b94a-1d99cd9a5818.png">
Repository: flutter
Issue: Cocoon should implement an API to schedule experimental devicelab builds on a PR
Labels: c: new feature,team-infra,P2,triaged-infra

Recently, when we tried to upgrade our gradle version, 3 attempts had to be reverted because they passed pre-submit checks but failed in the devicelab:

- https://github.com/flutter/flutter/commit/ca6cecf034d9c18fcb6ea70309cc855e353aa0f8
- https://github.com/flutter/flutter/commit/c4b3625d62b39b03f4ac9cb1b05533545a760ded
- https://github.com/flutter/flutter/commit/1f8c490c82a5162caa39d626181fa9b96ef5e2e2
- https://github.com/flutter/flutter/commit/7cfbdadc33fac2399c1a1fb4e0ab3e30793f0634

Although it is technically possible to schedule led builds for all devicelab targets on a PR (https://github.com/flutter/flutter/pull/108472#issuecomment-1197465024), it is non-trivial, and generally involves writing a script to parse .ci.yaml, grab the task names of interest, and delegate them to a carefully crafted led invocation.

Most of this logic already exists in cocoon (not sure how easy it would be to schedule an experimental build that doesn't interfere with the rest of our build metrics and reporting), so we should expose a new endpoint that would allow PR authors of these types of configuration/platform changes to verify their changes.

It would be ideal if the endpoint took in as inputs:

1. The PR number opened against flutter/flutter
2. The devicelab platform(s) of interest (for example, when making an Xcode change, the platforms might be `Mac_ios,Mac_arm64_ios`