sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: The migration removedglobalclientapis report false positive
Labels: bug,help wanted,automigrations,sev:S3

### Describe the bug

When running `npx storybook@latest upgrade` and in `.storybook/preview.tsx` you have a property of function named e.g. getStorybookTheme, the removedglobalclientapis migration will trigger a "Manual migration detected" warning on that `getStorybook` API is deprecated.

So, this is truly a minor one, but it requires me to change the name of the method in order for the migration to run without prompting me to do something.

### To Reproduce

1. Add for example `const getStorybookColor = '#fff';` to the .storybook/preview.tsx
2. run `npx storybook@latest upgrade`

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 12.6.8
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.19.4 - ~/Work/develop/spx-react-ui/node_modules/.bin/npm <----- active
  Browsers:
    Chrome: 118.0.5993.117
    Safari: 16.6
  npmPackages:
    @storybook/addon-actions: ^7.5.2 => 7.5.2 
    @storybook/addon-docs: ^7.5.2 => 7.5.2 
    @storybook/addon-essentials: ^7.5.2 => 7.5.2 
    @storybook/addon-interactions: ^7.5.2 => 7.5.2 
    @storybook/addon-links: ^7.5.2 => 7.5.2 
    @storybook/addon-mdx-gfm: ^7.5.2 => 7.5.2 
    @storybook/addon-storysource: ^7.5.2 => 7.5.2 
    @storybook/addons: ^7.5.2 => 7.5.2 
    @storybook/blocks: ^7.5.2 => 7.5.2 
    @storybook/core-events: ^7.5.2 => 7.5.2 
    @storybook/jest: ^0.2.3 => 0.2.3 
    @storybook/react: ^7.5.2 => 7.5.2 
    @storybook/react-webpack5: ^7.5.2 => 7.5.2 
    @storybook/testing-library: ^0.2.2 => 0.2.2 
    @storybook/theming: ^7.5.2 => 7.5.2 
    eslint-plugin-storybook: ^0.6.15 => 0.6.15 
    storybook: ^7.5.2 => 7.5.2 
    storybook-dark-mode: ^3.0.1 => 3.0.1
```


### Additional context

_No response_
Repository: vscode
Issue: Configurable styling of the indent guide line
Labels: feature-request,editor-indent-guides,bracket-pair-guides

<!-- ⚠️⚠️ 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. -->

Basically I'd like to resurface the request made in https://github.com/microsoft/vscode/issues/123981 because the suggested Monkey Patch extension  is no longer supported.

It'd be a nice visual improvement if we could have dashed indentation indicator lines instead of the current, rather thick ones. The ability to also specify the line width would also be useful.

![Visual Studio screenshot](https://devblogs.microsoft.com/visualstudio/wp-content/uploads/sites/4/2023/02/BracePairColorization.png)
Repository: next.js
Issue: hls.js doesn't contain default export in "app" router
Labels: bug

### Link to the code that reproduces this issue

https://github.com/maybephilipp/repro-repo-nextjs-hls-bug

### To Reproduce

1. `npm run dev`
2. Go to /test-pages
3. It shows HLS export is OK
4. Go to /test-app
5. It shows HLS export is undefined

Code in both routes exactly same.

btw `swcMinify: false` doesn't help.

Except non-helping `swcMinify: false`, the issue is very similar to https://github.com/vercel/next.js/issues/43292

### Current vs. Expected behavior

Current:
default export of hls.js is broken

Expected:
default export to return hls.js export

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
Binaries:
  Node: 19.0.1
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 7.16.0
Relevant Packages:
  next: 14.0.2-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Additional context

Tested in 13.5.6 and 14+ versions.
Repository: rust
Issue: Rust compiler hangs when compiling code with complex struct
Labels: T-compiler,C-bug,I-hang

<!--
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 with `rustc -C opt-level=1 code.rs`

```rust
#![recursion_limit = "1024"]
#![allow(dead_code)]
use std::mem;
pub struct S0<T>(T, T);
pub struct S1<T>(Option<Box<S0<S0<T>>>>, Option<Box<S0<S0<T>>>>);
pub struct S2<T>(Option<Box<S1<S1<T>>>>, Option<Box<S1<S1<T>>>>);
pub struct S3<T>(Option<Box<S2<S2<T>>>>, Option<Box<S2<S2<T>>>>);
pub struct S4<T>(Option<Box<S3<S3<T>>>>, Option<Box<S3<S3<T>>>>);
pub struct S5<T>(Option<Box<S4<S4<T>>>>, Option<Box<S4<S4<T>>>>, Option<T>);
trait Foo {
    fn xxx(&self) {}
}
impl<T> Foo for T
where
    T: Foo,
    T: Sync,
{
    fn xxx(&self) {}
}
impl Foo for S5<u8> {
    fn xxx(&self) {}
}
trait Bar {}
impl<T> Foo for T
where
    T: Bar,
    T: Sync,
{
    fn xxx(&self) {}
}
impl Foo for S5<u8> {
    fn xxx(&self) {}
}
```

I expected to see this happen: *The compiler compiles successfully or outputs an error message.*

Instead, this happened: *The Rust compiler hangs indefinitely.*

### 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 (cc66ad468 2023-10-03)
binary: rustc
commit-hash: cc66ad468955717ab92600c770da8c1601a4ff33
commit-date: 2023-10-03
host: x86_64-unknown-linux-gnu
release: 1.73.0
LLVM version: 17.0.2
```
The same problem is reproduced on the nightly version(1.75.0-nightly  `31bc7e2c4 2023-10-30`)

what's more, to get more information,I also tried '-Z time-passes' (using nighly version):
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Output</summary>
<p>

```
time:   0.001; rss:   29MB ->   31MB (   +2MB)	parse_crate
time:   0.006; rss:   34MB ->   48MB (  +13MB)	expand_crate
time:   0.006; rss:   34MB ->   48MB (  +13MB)	macro_expand_crate
warning: unused import: `std::mem`
 --> code.rs:3:5
  |
3 | use std::mem;
  |     ^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error[E0601]: `main` function not found in crate `code`
  --> code.rs:33:2
   |
33 | }
   |  ^ consider adding a `main` function to `code.rs`

time:   0.014; rss:   51MB ->   56MB (   +6MB)	looking_for_entry_point
time:   0.014; rss:   51MB ->   57MB (   +6MB)	misc_checking_1
time:   0.001; rss:   57MB ->   60MB (   +3MB)	type_collecting
```

</p>
</details>
Repository: storybook
Issue: [Bug]: @storybook/addon-docs/jest-transform-mdx.js jest bug
Labels: bug,help wanted,compatibility with other tools,addon: docs

### Describe the bug

@storybook/addon-docs/jest-transform-mdx.js file bug:
1. jest need process function, but this file use processAsync
2. @mdx-js/react version2 did not export mdx, but this file use mdx
![image](https://github.com/storybookjs/storybook/assets/63383310/33d9a28f-2d62-46c6-b073-65f1197f7b29)


### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Build Storybook fails in monerepo
Labels: bug,help wanted,svelte,nx,sveltekit,sev:S3

### Describe the bug

 I have set up a monorepo with nx workspace. The sveltekit app is located in a subdirectory. When building storybook with `nx build-storybook toolapp` the build fails with `NX src/app.html does not exist`. When I create a folder `src` in the workspace `root` folder and copy the file `app.html` into this folder the build works.

I can use storybook with `nx storybook toolapp` without problems.

### To Reproduce

[storybook-sveltekit-nx-workspace](https://github.com/floratmin/storybook-sveltekit-nx-workspace)

to make it work rename `src-throws` to `src`

### System

_No response_

### Additional context

_No response_
Repository: bitcoin
Issue: Evicting and filling attack for linking multiple network addresses
Labels: Brainstorming,P2P

I've [discovered a paper](https://cybersecurity.springeropen.com/articles/10.1186/s42400-023-00182-9) published earlier this month. I haven't found any discussion in the repo, so I will summarize the relevant parts here and share my thoughts.

Let's say we have a node that operates both over ipv4 and TOR. We don't want an observer to link these two addresses to the same node. For example, ADDR caching (#18991) was implemented for this reason.

The paper suggests the following attack:
1. Fill all (115?) victim's inbound slots in `networkA.`
2. Make sure these connections are candidates for eviction (higher latency, etc.).
3. Make connection to the presumably-victim's node in `networkB`
4. Observe whether `networkA` connections from (1) are dropped as you add connections in networkB.

I haven't verified the experiments, but even understanding the attack assures me the problem exists. Authors claim to reach high precision at a very low cost (optimized by inspecting`VERSION` data and block relay data).

They suggest the following countermeasures:
1. Have separate connection pools (for the sake of eviction) for each network (say TOR and ipv4).
2. Make eviction unpredictable (e.g. after a random delay)
Repository: material-ui
Issue: [ButtonGroup][material-next] Add ButtonGroup component
Labels: on hold,component: ButtonGroup,design: material you

This issue is to track the work for adding the ButtonGroup component to @mui/material-next, moving forward the Material You effort (https://github.com/mui/material-ui/issues/29345)

Material You SegmentedButton (this styles should be used for ButtonGroup) specification: https://m3.material.io/components/segmented-buttons/overview

Migration Guide steps

- [x] Copy component files from material (v5) to material-next: #39739
- [x] ~Remove deprecated components and componentsProps props:~ Skipped, no props to remove
- [ ] Drop support for ThemeProvider in favor of CssVarsProvider: #40124
- [x] Migrate component to Typescript: #39794
- [x] ~Refactor component to use Base UI’s hook if it exists:~ Skipped, no hooks needed
- [ ] Implement Material You design specs: #40124
- [ ] Add component playground to v5 docs: #40124

Note: This comment will be updated to show the progress and list possible issues.

@DiegoAndai
Repository: flutter
Issue: [file_selector] getDirectoryPath() initialDirectory is ignored on Android
Labels: platform-android,package,P2,p: file_selector,team-android,triaged-android

case-1
 ```
final result = await FileSelectorAndroid().getDirectoryPath(
        confirmButtonText: confirmButtonText,
        initialDirectory: 'content://com.android.externalstorage.documents/tree/primary%3APictures',
      );
```
case-2
 ```
final result = await FileSelectorAndroid().getDirectoryPath(
        confirmButtonText: confirmButtonText,
        initialDirectory: '/storage/emulated/0/Pictures',
      );
```

I am using `file_selector: ^1.0.1` package and in both case the initial directory is not working. I have tried using both imports 

```
import 'package:file_selector_android/file_selector_android.dart';
or 
import 'package:file_selector/file_selector.dart';

```


If I am wrong, then kindly correct me here.
Repository: storybook
Issue: [Bug]:  "Failed to load static files" error with Yarn PnP with global cache on windows
Labels: bug,windows

### Describe the bug

A minimal storybook setup fails to run on windows  with the following callstack:

```
Error: Failed to load static files, no such directory: .\C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-manager-npm-7.5.1-b9f503fb19-10c0.zip\node_modules\@storybook\manager\static
Make sure this directory exists, or omit the -s (--static-dir) option.
    at parseStaticDir (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\presets\common-preset.js:14:2310)
    at async C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\presets\common-preset.js:17:2925
    at async Promise.all (index 0)
    at async Object.favicon (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\presets\common-preset.js:17:2687)
    at async useStatics (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\index.js:48:6508)
    at async Promise.all (index 2)
    at async storybookDevServer (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\index.js:104:1159)
    at async buildDevStandalone (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\index.js:119:3007)
    at async withTelemetry (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-core-server-npm-7.5.1-02b6f24941-10c0.zip\node_modules\@storybook\core-server\dist\index.js:103:3903)
    at async dev (C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-cli-npm-7.5.1-8d005d3abc-10c0.zip\node_modules\@storybook\cli\dist\generate.js:473:401)
```

On linux, works fine

The path ".\C:\Users\camar\AppData\Local\Yarn\Berry\cache\@storybook-manager-npm-7.5.1-b9f503fb19-10c0.zip\node_modules\@storybook\manager\static" is almost correct except for the ".\\" prefix

Somehow [parseStaticDir](https://github.com/storybookjs/storybook/blob/994689d607fad867829b5409b53bafdd70af0f1b/code/lib/core-server/src/utils/server-statics.ts#L61) is adding '.\\' prefix when should not


### To Reproduce

https://github.com/blikblum/yarn-storybook

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.0.0 - ~\AppData\Roaming\npm\yarn.CMD <----- active
    npm: 8.10.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (116.0.1938.81)
```


### Additional context

_No response_
Repository: material-ui
Issue: [docs][joy-ui][input] Inputs as decorators for other inputs in forms
Labels: docs,component: text field,design: joy,support: docs-feedback

### Duplicates

- [X] I have searched the existing issues

### Related page

https://mui.com/joy-ui/react-input/#decorators

### Kind of issue

Other

### Issue description

The decorator documentation of `Input` kicks off with an `Input` that has another `Input` as its `endDecorator`. But as soon as you'd want to use that in an actual form with a `FormLabel` and `FormHelperText` component wrapped in a `FormControl`, Joy UI will start throwing errors at you that you aren't allowed to do this.

```
A FormControl can contain only one control component (Autocomplete | Input | Textarea | Select | RadioGroup)
You should not mix those components inside a single FormControl instance
```

### Context 🔦

I feel like this demo should be something that can actually be used in a context that goes beyond "I just want 2 inputs" and works with Joy UI's other components. This demo specifically could be fixed by replacing the `Select` with a `Dropdown` to achieve roughly the same result.

Then again... mayhaps changes should be made to `FormControl` to allow 2 or more inputs. Examples like the demo feel like a common usecase (e.g.: a search box with a control to specify where you want to look).
Repository: go
Issue: x/telemetry: improve readability of merged reports
Labels: NeedsInvestigation,telemetry

On https://telemetry.go.dev, we're starting to get more data in the merged reports, which is great. However, as reports get larger (e.g. https://storage.googleapis.com/prod-telemetry-merged/2023-10-28.json), it's getting harder to identify individual stacks.

We should consider ways to improve the readability of these merged reports. Perhaps we can have an html handler that summarizes them and collapses stacks. For non-devel versions, perhaps we can map the stack to a cs.opensource.google link...
Repository: PowerToys
Issue: PowerToys Run only searches files on main/Windows drive
Labels: Needs-Triage

### Description of the new feature / enhancement

I'd like PowerToys Run to also search other drives connected to the computer, not only the main drive. Perhaps removable/temporary drives must not be included, but permanent, indexed drives should. 

### Scenario when this would be used?

This would be helpful every time I type the name of a file I want to open in PowerToys run. I'm not sure how the current implementation chooses what drive to show results from, but I'm guessing it's the one Windows/PowerToys run is installed on. But I have an SSD drive inside my computer with many important files I use for work often, and in my head these files are like any other, so it doesn't make sense to not show them when I type in file names in PowerToys run. It's honestly a waste of time trying to open a file with PowerToys, remembering it won't show in results, then having to do it by hand, opening explorer, etc. 

### Supporting information

_No response_
Repository: go
Issue: x/tools/go/analysis/passes/testinggoroutine: do not ignore calls in goroutines (false negative)
Labels: help wanted,NeedsInvestigation,Analysis

```
$ go vet -testinggoroutine some_test.go
```

```go
func TestSomething(t *testing.T)
	go func() {
		helper(t)       // No warning :(
	}()
}

func helper(t *testing.T) {
        t.Helper()
	t.Fatal()
}
```
Repository: TypeScript
Issue: Replace Node interface with discriminated unions
Labels: Suggestion,Experimentation Needed

### 🔍 Search Terms

discrimnated type union node internal source api

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Happy Halloween 🎃! In the spirit of the holiday, I'd like to resurrect #13634: using a discriminated unions for `Node` categories. Roughly paraphrasing #18285's very good description here:

As mentioned in https://github.com/Microsoft/TypeScript/pull/18214#issuecomment-326823448, TypeScript's source can remove a lot of casts by using a discriminated union for `Node`. 
While this should not affect TypeScript's runtime performance (as it just changes its types, mostly) it may cause TypeScript to take longer to compile itself.

#13634 was declined in 2018 for performance concerns (https://github.com/microsoft/TypeScript/issues/13634#issuecomment-413289616) but I hope that the years of performance improvements since then have since made this possible.

### 📃 Motivating Example

Switching TypeScript's `Node` from an interface from a discriminated type union would allow `.kind` checks to narrow types of values declared as `Node`.

```ts
import * as ts from "typescript";

declare const node: ts.Node;

if (node.kind === ts.SyntaxKind.FunctionDeclaration) {
  node.name?.text;
  //   ~~~~
  // Property 'name' does not exist on type 'Node'.
}
```

### 💻 Use Cases

In TypeScript itself, a match-case-and-full-word search for `/(?:name|node|parent) as \w{5,}/` in `src/**/*.ts` excluding `*test*` yields **1879** matches right now. After prototyping it locally and enabling [`@typescript-eslint/no-unnecessary-type-assertion`](https://typescript-eslint.io/rules/no-unnecessary-type-assertion), I mostly-automatically reduced it to **987** matches. More removals could likely be enacted with manual effort.
* Previous attempt: https://github.com/microsoft/TypeScript/pull/18285
* My attempt: https://github.com/Microsoft/TypeScript/pull/56274
* (edit) Wes' PR, which everyone else in this thread except Andarist has previous commented on but somehow forgot about: #54148

In community projects that use the TypeScript AST, including [typescript-eslint](https://typescript-eslint.io), we'd similarly be able to have more precise type information on TS AST nodes.

#13634 mentions other consumers too, such as Babel's https://github.com/babel/babel/blob/c446ff85c28e117ebf3cd72cd34ef358f1077aa8/packages/babel-types/src/validators/is.ts.
Repository: vscode
Issue: Better support for /help with chat agents
Labels: feature-request,api,api-proposal,panel-chat

We should either

- Make vscode own `/help`. It lists all commands and the default agent is able to contribute a paragraph
  - I think I prefer this option. `/help` should list commands from extensions, but there is no reason for the default agent to be able to get a list of these. But it does still need heavy customization from the default agent to look nice and match our current experience.
- The default agent owns it, and is able to get a list of all agents/commands, including from other extensions
  - Need special API to contribute the slash command and get the list of agents

Forked from https://github.com/microsoft/vscode-copilot/issues/1682

10/31/23 API call notes
- This can be owned by vscode, and probably the extension can just contribute the last section after the list of agents/commands


<img width="428" alt="image" src="https://github.com/microsoft/vscode/assets/323878/8f973389-ba3a-495e-88ec-e334257d1b4f">
Repository: PowerToys
Issue: [Color Picker] Add option "Open editor and pick a color"
Labels: Idea-Enhancement,Needs-Triage,Product-Color Picker

### Description of the new feature / enhancement

Hi,

Please add the option to "**Open the editor and pick a color.**" I mean Color Picker open the editor window first. If you don't want to pick a new color, you can simply right-click with your mouse to cancel. And if you want to pick a new color, there's no need to click on the button to activate the picker.

![color-picker](https://github.com/microsoft/PowerToys/assets/45882853/8bd39b66-6b76-48fa-8a59-562b53c60a0e)

I love this tool, thx!

### Scenario when this would be used?

Sort action (open window editor first)

### Supporting information

_No response_