sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: CSF3 auto generate title exclude file path as the hierarchy？
Labels: feature request,story index

**Is your feature request related to a problem? Please describe**
Recent features of the Auto generate title is fabulous, and is a huge relieve to a codebase that maintains hundred of stories. Due to our file structure, however, the story structure that storybook currently generates is a little bit too complicated.

Say our codebase looks like below:

- components 
  - componentA
    - componentA.stories.tsx
- pages
  - pageA 
    - components 
      - componentB 
        - componentB.stories.tsx 
  - folderA 
    - pageB 
      - components 
        - componentC 
          - componentC.stories.tsx 
        - componentD
          - componentD.stories.tsx 
  // ...

At first thought I set my storybook configuration as:
```javascript
module.exports = {
stories: [
    {
      directory: '../components',
      titlePrefix: 'components',
      files: '**/*.stories.*',
    },
    {
      directory: '../pages',
      titlePrefix: 'pages',
      files: '**/*.stories.*',
    },
  ],
}
```

Ths problem now is that storybook actually parses every file hierarchy to the storybook.

- Components 
  - ComponentA 
    - ComponentA
- Pages
  - PageA 
    - Components 
      - ComponentB 
        - ComponentB
  - FolderA 
    - PageB 
      - Components 
        - ComponentC 
          - ComponentC
        - ComponentD
          - componentD
  // ...
  
but what we think is more easy to read and search is like the structure below:

```
- Components
  - ComponentA
- Pages
  - ComponentB
  - ComponentC
  - ComponentD
```

If the title could be generated through a customizable function, or can be only generated by `<titlePrefix> + <filename>`, I think it would be really helpful. Thanks!

**Describe the solution you'd like**
What would you like to see added to Storybook to solve problem?
A means to generate story hierarchy without explicitly listing full file paths
**Describe alternatives you've considered**
Any alternative solutions or features you've considered.

**Are you able to assist to bring the feature to reality?**
no | yes, I can...

**Additional context**
Add any other context or screenshots about the feature request here.
Repository: material-ui
Issue: [Autocomplete][Textfield] InputProps.inputProps isn't able to override.
Labels: component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯


An error 'Cannot read properties of null' has occurred on click autocomplete.

```Typescript
<Autocomplete
      sx={{ width: 300 }}
      options={options}
      autoHighlight
      getOptionLabel={(option) => option.label}
      renderOption={(props, option) => (
        <Box
          component="li"
          sx={{ "& > img": { mr: 2, flexShrink: 0 } }}
          {...props}
        >
          <img
            loading="lazy"
            width="20"
            src={`https://flagcdn.com/w20/${option.code.toLowerCase()}.png`}
            srcSet={`https://flagcdn.com/w40/${option.code.toLowerCase()}.png 2x`}
            alt=""
          />
          {option.label} ({option.code}) +{option.phone}
        </Box>
      )}
      renderInput={(params) => (
        <TextField
          {...params}
          label="Choose a country"
          InputProps={{
            inputProps: {}
          }}
          inputProps={{
            ...params.inputProps,
            autoComplete: "new-password" // disable autocomplete and autofill
          }}
        />
      )}
    />
```

[Codesandbox](https://codesandbox.io/s/countryselect-demo-material-ui-forked-06hg06?file=/demo.tsx:231-1247)

```Typescript
// packages/mui-material/src/TextField/TextField.js

  const InputElement = (
    <InputComponent
      aria-describedby={helperTextId}
      autoComplete={autoComplete}
      autoFocus={autoFocus}
      defaultValue={defaultValue}
      fullWidth={fullWidth}
      multiline={multiline}
      name={name}
      rows={rows}
      maxRows={maxRows}
      minRows={minRows}
      type={type}
      value={value}
      id={id}
      inputRef={inputRef}
      onBlur={onBlur}
      onChange={onChange}
      onFocus={onFocus}
      placeholder={placeholder}
      inputProps={inputProps}
      {...InputMore}
      {...InputProps}
    />
  );
```

[Link](https://github.com/mui/material-ui/blob/cb74465b5afd91e508fecedce0833dd5377e1a8a/packages/mui-material/src/TextField/TextField.js#L152)

Is it a bug?



### Expected behavior 🤔

In my opinion, It should be an error when assigning value in InputProps.inputProps.




### Steps to reproduce 🕹

Steps:

1.
2.
3.
4.


### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: flutter
Issue: App crashes and disappears when typing on the keyboard
Labels: a: text input,c: crash,engine,platform-windows,P2,team-engine,triaged-engine

![image](https://user-images.githubusercontent.com/11803121/175234898-4d8fb7a8-bdc0-4e94-99e6-c96892974673.png)
![企业微信截图_20220622153028](https://user-images.githubusercontent.com/11803121/175234979-4e84c7ad-07f3-402e-84a4-661c150482d4.png)


错误应用程序名称: wxwork_helper.exe，版本: 2.9.4.0，时间戳: 0x62b16e54
错误模块名称: ntdll.dll，版本: 10.0.17763.2989，时间戳: 0x21d18902
异常代码: 0xc0000374
错误偏移量: 0x00000000000fa979
错误进程 ID: 0x327d0
错误应用程序启动时间: 0x01d885fd0ad32a37
错误应用程序路径: C:\Commerce\wuneng\wxwork_helper.exe
错误模块路径: C:\Windows\SYSTEM32\ntdll.dll
报告 ID: 1015e06c-a703-4fc4-ac9b-4885f5c53d1d
错误程序包全名: 
错误程序包相对应用程序 ID:
Repository: ant-design
Issue: ConfigProvider 里面 form 配置期望支持配置 labelWrap
Labels: Inactive

### What problem does this feature solve?

多数情况下，想针对系统中所有的 form 进行 labelWrap 的配置，目前 ConfigProvider 的 form仅仅支持 { validateMessages?: ValidateMessages, requiredMark?: boolean | optional, colon?: boolean } 这些项，期望增加 labelWrap 配置项

### What does the proposed API look like?

import { ConfigProvider } from 'antd';

// ...

export default () => (
  <ConfigProvider 
      form={{
          labelWrap: true
      }}
>
    ...
  </ConfigProvider>
);

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: terminal
Issue: Alt-clicking a profile doesn't open in a pane when Narrator is turned on
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Area-Accessibility,Product-Terminal,Priority-1

### Windows Terminal version

1.13.10336.0

### Windows build number

10.0.19044.1706

### Other Software

Windows Narrator

### Steps to reproduce

1. Open any shell in Windows Terminal.
2. Open the profile menu and click on an entry while pressing the <kbd>Alt</kbd> key.
3. Note that the profile is opened in a pane of the current window. Close that pane.
4. Now turn on the Windows Narrator screen reader.
5. Open the profile menu again and click on an entry while pressing the <kbd>Alt</kbd> key.
6. Note that the profile is now opened in a separate tab.

### Expected Behavior

Alt-clicking on a profile should always open it in a pane of the current window.

### Actual Behavior

When the narrator is turned on, alt-clicking opens the profile in a separate tab.

Btw, if there's some accessibility reason for this, that's fine. I was just testing something with the narrator and was surprised by the behavior, but it's not something that affects me personally.
Repository: material-ui
Issue: MenuItems as Link break keyboard input
Labels: component: menu

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The issue of using menu items as router links or anchors was already discussed here: https://github.com/mui/material-ui/issues/204. But all the suggested solutions will break the keyboard navigation of the menu list. 

UPDATE: I found out, that deleting the additional `<li>` seems to restore the keyboard functionality. Unfortunately this breaks the markup. `<ul> <a/> <a/> <li/> </ul> `

### Expected behavior 🤔

When a menu list is focused and the keyboard arrows are pressed, the corresponding menu item is selected. This should also be true for navigational entries like anchors or router links.

### Steps to reproduce 🕹

Use menu items as links with the suggested way to do it.

```
<MenuList>
    <li>
        <MenuItem
            component="a"
            href="https://google.com"
            target="_blank"
        >Google</MenuItem>
    </li>
</MenuList>
```

### Context 🔦

_No response_

### Your environment 🌎

_No response_
Repository: pytorch
Issue: Expose more MAGMA backends for solve_triangular
Labels: triaged,module: linear algebra,module: magma

### 🚀 The feature, motivation and pitch

MAGMA has quite a few (at least 3) backends for triangular solvers, and their efficiency varies wildly. We should expose as many backends as we can and do a proper benchmark of all of them to have faster triangular solvers, as triangular solvers are the basis for almost all other linalg algorithms. 

This was discovered while running the benchmarks for https://github.com/pytorch/pytorch/pull/80074

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: create-react-app
Issue: Maintain CRA template as a separate repository 
Labels: issue: proposal,needs triage

Hi Team React,
 
Could you please maintain the CRA template as a separate repository so that users can fork the template and create their own templates adding  additional abstraction and features.  Though users can upload and maintain a template under their accounts they'll not get the updates made to the templates under the create-react-app

Thanks,
Arun
Repository: pytorch
Issue: [feature request] Add support for a custom DatasetFetcher in DataLoader 
Labels: module: dataloader,triaged,enhancement,module: data

### 🚀 The feature, motivation and pitch

I'm working on a time-series dataset, and I stumbled upon a limitation withing pytorch's DataLoader that I'd like to address here.

I have a custom map-style dataset that implements a `__getitem__` and `__len__` methods.

`__getitem__`  has a following signature and returns by default features of shape `(seq_length, n_features)` and an integer label.
```python
def __getitem__(self, i: int, seq_length: int = 100):
    # ....
    return features, label
```
Sequence length is fixed by default, but can be changed by passing a `seq_length` argument.

I'm using an LSTM + Transformer model that is able to process an input of variable sequence length.\
BUT I'm not leveraging this feature of my model because pytorch's DataLoader expects all the samples returned by the dataset to be of the same shape.
A traditional approach to solving this problem is **sequence padding**. This doesn't really solve the problem in my opinion (the model still gets constant sequence length as an input) and leads to a range of further questions (which values to use for padding, how to interpolate ect.).

**What I would like to do instead** is to use a custom DatasetFetcher to create batches that have constant sequence length within a batch, but **varying** sequence length over the dataset.\
So let's say or batch has a shape `batch_size, seq_length, n_features`.  (Let batch_size=32, n_features=10)\
Our DataLoader will sample indices for the first batch and then fetch samples with a constant `seq_length=100`, which will result in a batch of shape `32, 100, 10`.\
On the next batch, it will randomly (or by any other rule) pick a new sequence length (let's say 80) 
and create a batch of shape `32, 80, 10`.

```python
# Default behaviour
data = [self.dataset[idx] for idx in possibly_batched_index]
# New behaviour
data = [self.dataset.__getitem__(idx, seq_length) for idx in possibly_batched_index]
```

I'm pretty sure it will have a regularization effect.





### Alternatives

_No response_

### Additional context

_No response_

cc @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: next.js
Issue: ISR fails to serve 404 pages once the page gets deleted if experimental isr memory cache size is set to 0
Labels: bug

### Verify canary release

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

### Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Thu, 16 Jun 2022 13:32:35 +0000
    Binaries:
      Node: 16.15.0
      npm: 8.5.5
      Yarn: 1.22.18
      pnpm: N/A
    Relevant packages:
      next: 12.1.7-canary.45
      react: 18.2.0
      react-dom: 18.2.0


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

_No response_

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

next start

### Describe the Bug

Deleted ISR page shows old generated document even though it is already revalidated and should show 404 page.
This usually works as expected, but if you disable ISR memory cache (by setting `isrMemoryCacheSize: 0`) it stops and always return the stale version of the page. 

### Expected Behavior

Deleted ISR page should return 404 page

### Link to reproduction

https://github.com/pekarja5/next-isr-cache

### To Reproduce

1. Build and start the production build of provided repo.
2. Navigate to `http://localhost:3000/detail/1`
3. In `public/detail.json` file, change the enabled parameter to 0
4. After 5 seconds (revalidation period) refresh the page twice. First refresh should serve you the stale page while revalidating the page on server and the second should return 404 page, but it does not. Any later request will still serve the original stale version of the page never reaching the expected 404 page.
Repository: neovim
Issue: leak in chan_close_with_error
Labels: bug,test,robustness,ci,channels-rpc,has:backtrace



leak observed in https://github.com/neovim/neovim/pull/19059

```
RUN      T582 server -> client connecting to another (peer) nvim via named pipe: 216.50 ms OK
==================== File /home/runner/work/neovim/neovim/build/log/ubsan.31130 ====================
= 
= =================================================================
= ==31130==ERROR: LeakSanitizer: detected memory leaks
= 
= Direct leak of 30 byte(s) in 1 object(s) allocated from:
=     #0 0x4de7ad in malloc ??:?
=     #1 0x1261182 in try_malloc /home/runner/work/neovim/neovim/src/nvim/memory.c:74:15
=     #2 0x126137c in xmalloc /home/runner/work/neovim/neovim/src/nvim/memory.c:108:15
=     #3 0x1261916 in xmallocz /home/runner/work/neovim/neovim/src/nvim/memory.c:187:15
=     #4 0x1261a6e in xmemdupz /home/runner/work/neovim/neovim/src/nvim/memory.c:205:17
=     #5 0x6ec2cf in cstr_to_string /home/runner/work/neovim/neovim/src/nvim/api/private/helpers.c:338:13
=     #6 0x13167fe in chan_close_with_error /home/runner/work/neovim/neovim/src/nvim/msgpack_rpc/channel.c:566:21
=     #7 0x130c8ac in receive_msgpack /home/runner/work/neovim/neovim/src/nvim/msgpack_rpc/channel.c:219:5
=     #8 0xc4490d in read_event /home/runner/work/neovim/neovim/src/nvim/event/rstream.c:191:5
=     #9 0xc43b04 in invoke_read_cb /home/runner/work/neovim/neovim/src/nvim/event/rstream.c:204:3
=     #10 0xc424a3 in read_cb /home/runner/work/neovim/neovim/src/nvim/event/rstream.c:122:7
=     #11 0x1ecc2de in uv__stream_io /home/runner/nvim-deps/build/src/libuv/src/unix/stream.c:1288:5
= 
= SUMMARY: AddressSanitizer: 30 byte(s) leaked in 1 allocation(s).
====================================================================================================
nan ms test/helpers.lua:234: Found runtime errors in logfile(s): /home/runner/work/neovim/neovim/build/log/ubsan.31130
stack traceback:
	test/helpers.lua:234: in function 'check_logs'
	test/functional/helpers.lua:883: in function <test/functional/helpers.lua:882>
```
Repository: flutter
Issue: [camera] _startPlatformStream not working Xiaomi 11 pro 5g
Labels: e: device-specific,platform-android,p: camera,package,a: release,a: production,P2,team-android,triaged-android

We have a customer and the camera refuses to work for him and we get this error on firebase. 

It works for everyone else so it seems to be related to the device.

```
PlatformException(CameraAccess, CAMERA_ERROR (3): deleteStream:941: Camera 1: Unexpected error Invalid argument (-22) when deleting stream 0, null, null). Error thrown null.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: PlatformException(CameraAccess, CAMERA_ERROR (3): deleteStream:941: Camera 1: Unexpected error Invalid argument (-22) when deleting stream 0, null, null). Error thrown null.
       at StandardMethodCodec.decodeEnvelope(message_codecs.dart:607)
       at MethodChannel._invokeMethod(platform_channel.dart:167)
       at MethodChannelCamera._startPlatformStream(method_channel_camera.dart:295)
```

flutter doctor:
[✓] Flutter (Channel stable, 3.0.2, on macOS 12.3.1 21E258 darwin-arm, locale en-GR)
    • Flutter version 3.0.2 at /Users/nikostsesmelis/Tools/flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cd41fdd495 (2 weeks ago), 2022-06-08 09:52:13 -0700
    • Engine revision f15f824b57
    • Dart version 2.17.3
    • DevTools version 2.12.2

camera plugin version: 0.9.7+1 (not able to upgrade due to ios issue https://github.com/flutter/flutter/issues/106492)
Repository: TypeScript
Issue: Two same types (mapped type of generic param) are not assignable to each other 
Labels: Needs Investigation

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

Keywords:  generic function, mapped types

Errors: 
1. Type 'T1' is not assignable to type 'T2'.
2. Two different types with this name exist, but they are unrelated. 

I got both error messages in my original code, but only the first error message is left in the minimal reproduce.

### 🕗 Version & Regression Information

4.7.2

All other versions also have this issue.

### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/C4TwDgpgBAYgjFAvFAPAFQHwAoCGAnAcwC4o0BKJDKAJTnQwG4AoUSGuzJKAbyaigDaAaSgBLAHZQA1hBAB7AGakoOAM5QA5MAirgGqBAAe28QBN1IgPxRxEAG4Q8UEkIC6JAAzMAvsyYB6fwNDHABjYAAbEChgAAtoVRwAW2hWCBZwaBgAJi56XEISckoabPpmNNL6Ll5+YTFJGXklNBV1LR09YJNzKCsbe0dnPvcoLyZfJiZTCFCI-GgIiGAoOzgSeGYZuYWoJZW7bI3svzWuQ4YoQKgAUTw8OTwmQ-O4S+u7h6emIA

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type F1 = <T>(arg: T) => R1<T>;
type R1<T> = {
  [K in keyof T as 'test' extends K ? never : K]: 0;
};

// exactly the same type
type F2 = <T>(arg: T) => R2<T>;
type R2<T> = {
  [K in keyof T as 'test' extends K ? never : K]: 0;
};

declare let v1: F1;
declare let v2: F2;

v1 = v2; // Error
v2 = v1; // Error
```

The problem appears when a **conditional type** is used in a **key remapping of mapped types**.

### 🙁 Actual behavior

The two same types are not assignable to each other.

### 🙂 Expected behavior

The two same types should be assignable to each other. Because they are written in the same way.

In my case, the two "same-written type declarations" exist because they come from the same package with two different versions.

<!-- What you expected to happen instead, and why -->
Repository: material-ui
Issue: Menu component jumps on window resize
Labels: new feature,component: Popover

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

**How it could work** Open menu could smoothly change its position on window resize like every other component + it could stick to its parent not only horizontally, but also vertically
**How it works now** It snaps into a new horizontal position once resizing is paused, and it's no longer _attached_ to its parent

### Examples 🌈
![ezgif com-gif-maker (28)](https://user-images.githubusercontent.com/74932289/175318925-4efef489-537d-4437-abf6-0b185576a83a.gif)

### Motivation 🔦

Resizing window from wide to narrow view can result in the menu button to move out from the view, but the open dialog does not smoothly moves with the menu. Instead it snaps into its new horizontal position, it remains in the view even though its parent is no longer visible
Repository: pytorch
Issue: CPUProfilingAllocator greedy allocation plan generation failed
Labels: oncall: mobile

### 🐛 Describe the bug

Segmentation fault during greedy allocation plan generation using CPUProfilingAllocator. After carefully looking into the code, I found the root cause is the `free_size_to_offset` doesn't consider tensors with the same size. 

I fixed this issue by let `free_size_to_offset` map a size to a list of offset. When there are a new tensor allocation with existing size, it will add to the existing item's value list.


### Versions

Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.10.5 (main, Jun 16 2022, 19:48:34) [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.4.56.bsk.10-amd64-x86_64-with-glibc2.31
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] torch==1.13.0a0+git226a5e8
[conda] Could not collect
Repository: flutter
Issue: Disable animation doesn't work when using `MediaQueryData.disableAnimations`
Labels: framework,a: animation,a: accessibility,has reproducible steps,P3,found in release: 3.0,found in release: 3.1,team-framework,triaged-framework

I'm developing a Linux app, and using a showMenu function to show pop a menu where the mouse right-click, i want to disable the animation of the popup and the dismiss. I tried to disable the animation the same way I changed the textscalefactor, but failed. Here is the code of setting MediaQueryData and textscalefactor.

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {

    return MaterialApp(
      builder: (BuildContext context, Widget? child) {
        final MediaQueryData mediaQueryData = MediaQueryData.fromWindow(WidgetsBinding.instance.window);

        return MediaQuery(
          data: mediaQueryData.copyWith(
            disableAnimations: true,
            textScaleFactor: 2.0,
          ),
          child: child!,
        );
      },
      debugShowCheckedModeBanner: false,
      home: Desktop(),
    );
  }
}