sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: 
Labels: question / support,mui

### Describe the bug

Integrating Mui-base Menu in the storybook throws an error:
`The compound component's child doesn't have a key. You need to provide a missingKeyGenerator to generate it.`
![Screenshot 2023-07-12 at 3 55 38 PM](https://github.com/storybookjs/storybook/assets/110368171/b15e0ab6-8a64-48bc-9a35-f3470e444679)


### To Reproduce

1. Created a Menu component with exact same code as: https://codesandbox.io/s/c3h75q?file=/demo.tsx:0-5533
2. Added below story:
`import { Menu } from "../Components";
import type { Meta, StoryObj } from '@storybook/react';

const meta: Meta<typeof Menu> = {
  title: 'Components/Menu',
  component: Menu,
  tags: ['autodocs'],
}

export default meta;
type Story = StoryObj<typeof Menu>;

export const Primary: Story = {
  args: {
  },
};`


### System

```shell
Environment Info:

  System:
    OS: macOS 12.5.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 15.6.1
  npmPackages:
    @storybook/addon-controls: ^7.0.20 => 7.0.20 
    @storybook/addon-essentials: ^7.0.4 => 7.0.4 
    @storybook/addon-interactions: ^7.0.4 => 7.0.4 
    @storybook/addon-links: ^7.0.4 => 7.0.4 
    @storybook/blocks: ^7.0.4 => 7.0.20 
    @storybook/manager-api: ^7.0.20 => 7.0.20 
    @storybook/preset-create-react-app: ^7.0.4 => 7.0.4 
    @storybook/react: ^7.0.4 => 7.0.18 
    @storybook/react-webpack5: ^7.0.4 => 7.0.4 
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

_No response_
Repository: react-native
Issue: 0.72.2 Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
Labels: Needs: Triage :mag:

### Description

After update to 0.72.2 and connect to chrome debugger an error appears:

Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
Consider providing alternative methods to expose this method in debug mode, e.g. by exposing constants ahead-of-time.

### React Native Version

0.72.2

### Output of `npx react-native info`

System:
  OS: macOS 13.4.1
  CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 2.95 GB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 16.13.0
    path: /usr/local/bin/node
  Yarn:
    version: 3.2.1
    path: /usr/local/bin/yarn
  npm:
    version: 8.1.0
    path: /usr/local/bin/npm
  Watchman:
    version: 2022.10.24.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods: Not Found
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 21.4
      - iOS 16.0
      - macOS 12.3
      - tvOS 16.0
      - watchOS 9.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.2 AI-222.4459.24.2221.10121639
  Xcode:
    version: 14.0.1/14A400
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.11
    path: /usr/bin/javac
  Ruby:
    version: 2.6.5
    path: /Users/user/.rvm/rubies/ruby-2.6.5/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.2
    wanted: 0.72.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: false
  newArchEnabled: false

### Steps to reproduce

1) start project
2) connect to chrome debugger
<img width="1402" alt="screen" src="https://github.com/facebook/react-native/assets/75758285/36af83f7-40e5-4167-98ac-14c018e6e3ec">


### Snack, code example, screenshot, or link to a repository

-
Repository: pytorch
Issue: Multiple dimensions support for `torch.max`
Labels: feature,triaged,module: numpy,needs design,module: python frontend

### 🚀 The feature, motivation and pitch

Numpy's  `np.max` has support for multiple dimensions, but `torch.max` does not.
To keep both synced and avoid implementing custom function like #105045, it would be really helpful to have this.

### Alternatives

#105045

### Additional context
@davidradl

cc @mruberry @rgommers @albanD
Repository: godot
Issue: Editor C++ classes exposed to GDScript with empty documentation
Labels: bug,topic:core,topic:gdscript,topic:editor

### Godot version

4.1 Stable

### System information

MacBook Ventura 13.4

### Issue description

Some C++ editor specific classes are exposed to GDScript as keywords (the class name light up on the script editor), but they can't be edited/inherited/inspected (Godot throws an error when you do), and their documentation page is empty.

Two classes I noticed have this problem:
- `EditorTitleBar`
- `EditorRunBar`

There are probably more classes with this problem, those are the ones I easily found when creating an editor plugin.

### Steps to reproduce

Write one of the classes I gave as example in any script (`EditorTitleBar` or `EditorRunBar`). They can't be instanced in any way or form in any `tool` or `plugin` script, and their documentation page is empty.

### Minimal reproduction project

N/A.
Repository: vscode
Issue: Integration test failure: Redo of rename Java Class name has no effect
Labels: integration-test-failure

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=222817&view=logs&j=a5d99aad-4929-5289-bf4a-26b78032353d&t=e0994396-3691-5ef8-8c95-5b6e6eca2c08

```
  1) vscode API - workspace
       issue #107739 - Redo of rename Java Class name has no effect:

      AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: Expected values to be strictly equal:

false !== true

      + expected - actual

      -false
      +true
      
      at Context.<anonymous> (extensions/vscode-api-tests/src/singlefolder-tests/workspace.test.ts:1115:11)

```
Repository: vscode
Issue: Adopt `sort-imports` rule for our code base
Labels: debt,engineering

This is about adopting https://eslint.org/docs/latest/rules/sort-imports for VS Code. It goes just like other lint rules but we need to ensure TypeScript's import-on-complete co-exists in peace and that (optionally) folks use `source.removeUnusedImports` but not `source.organizeImports`
Repository: flutter
Issue: Integration test cache clean between test
Labels: c: new feature,tool,t: flutter driver,platform-web,c: proposal,f: integration_test,P2,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

Writing integration test on chrome I can't clear cache between test.

### Proposal

ability to clear cache using command during test
Repository: flutter
Issue: Enforce formatting of packages repo tooling
Labels: team,p: tooling,package,team-ecosystem,P2,triaged-ecosystem

Currently we're enforcing Dart format on all the packages in packages/, but not the script/tool/ directory; we should add a check of that as well.

We could do this as a one-off, like we do for unit tests, but maybe a better option would be a flag to include the tooling in the package list, and then we could add that to specific commands like format and unit tests.
Repository: storybook
Issue: [Bug]: Storybook 7: have variants in one Canvas block
Labels: question / support,block: other

### Describe the bug

Hello.

I'm using Storybook 7 with the new way to write stories. 

But, when i'm trying to document my component with MDX, i am not able to provide a Canvas block with components variants inside. For exemple, the different sizes of my component.

What is the solution to do that ?

Thanks

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: axios
Issue: FATAL undefined undefined Error: Network Error (Android)
Labels: priority::low

### Describe the bug

After updating react-native in the application to version 0.71.1 and targetSDK to version 33, a problem began to appear when loading pictures. Moreover, the loading is strange, the first picture does not go away, an error comes. Following it, I send the next one - the picture is sent without problems. I noticed that the bug is observed on Android versions below 12 (tested on this device)

The image is attached to formData and sent as a POST request to the server. Memo used, used the XMLHttpRequest class separately. Flipper is not used in the project, so many of the upgrade tips are out of date.
 It is not an issue with the API.

<img width="991" alt="Screenshot 2023-07-12 at 16 24 00" src="https://github.com/axios/axios/assets/56867708/7c350abb-60ff-42e9-951c-22f5d017d3cb">





### To Reproduce

_No response_

### Code snippet

```js
const xhrRequest = (data) => {
  const { accessToken, fileName, type, uri } = data
  const xhr = new XMLHttpRequest()
  const body = new FormData()

  xhr.open('POST', `${URL}${ENDPOINTS.ATTACH_FILE}`)
  xhr.setRequestHeader('Authorization', `Bearer ${accessToken}`)
  xhr.setRequestHeader('Content-type', 'multipart/form-data')
  body.append('file', { uri, name: fileName, type })

  xhr.send(body)
}

export const attachFile = ({ accessToken, fileName, type, uri }) => {
  const body = new FormData()
  body.append('file', {
    name: fileName,
    uri: Platform.OS === 'android' ? uri : uri.replace('file://', ''),
    type,
  })

  if (Platform.OS === 'android') {
    xhrRequest({accessToken, fileName, type, uri})
  }

  return api
    .post(ENDPOINTS.ATTACH_FILE, body, {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        'Content-type': 'multipart/form-data',
      },
      maxContentLength: Infinity,
    })
    .then(R.prop('data'))
}
```


### Expected behavior

_No response_

### Axios Version

0.24.0

### Adapter Version

_No response_

### Browser

_No response_

### Browser Version

_No response_

### Node.js Version

18.16.1

### OS

_No response_

### Additional Library Versions

```bash
react: 18.2.0,
react-native: 0.71.10
```


### Additional context/Screenshots

_No response_
Repository: create-react-app
Issue: `eslint-config-react-app` causing conflicts after updating `@typescript-eslint` to v6
Labels: needs triage,issue: bug report

### Describe the bug

I updated a project to the newly released version 6 of `@typescript-eslint`. After the update, I'm getting eslint conflicts with `eslint-plugin-imports` and `@typescript-eslint` plugins. I think the fix is to update the dependencies in `eslint-config-react-app` but I am not sure.

Here is the full error
```
Uncaught exception received.
Error: Plugin "import" was conflicted between ".eslintrc.cjs#overrides[0] » eslint-config-react-app" and ".eslintrc.cjs".
    at mergePlugins (/home/superkxt/repos/personal/client-management/node_modules/.pnpm/@eslint+eslintrc@2.1.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:598:19)
    at createConfig (/home/superkxt/repos/personal/client-management/node_modules/.pnpm/@eslint+eslintrc@2.1.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:701:9)
    at ConfigArray.extractConfig (/home/superkxt/repos/personal/client-management/node_modules/.pnpm/@eslint+eslintrc@2.1.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:877:33)
    at CLIEngine.getConfigForFile (/home/superkxt/repos/personal/client-management/node_modules/.pnpm/eslint@8.44.0/node_modules/eslint/lib/cli-engine/cli-engine.js:981:14)
    at ESLint.calculateConfigForFile (/home/superkxt/repos/personal/client-management/node_modules/.pnpm/eslint@8.44.0/node_modules/eslint/lib/eslint/eslint.js:667:26)
    at /home/superkxt/.vscode/extensions/dbaeumer.vscode-eslint-2.4.2/server/out/eslintServer.js:1:22644
    at Object.E [as withClass] (/home/superkxt/.vscode/extensions/dbaeumer.vscode-eslint-2.4.2/server/out/eslintServer.js:1:19218)
    at w.then.g.validate (/home/superkxt/.vscode/extensions/dbaeumer.vscode-eslint-2.4.2/server/out/eslintServer.js:1:22610)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
```

### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

None. 

### Expected behavior

ESLint should work

### Actual behavior

ESLint errors and lining stops working
Repository: deno
Issue: Feature Request: support DENO_V8_FLAGS for compiled standalone binary
Labels: suggestion,compile

Use case: change memory limit `--max-old-space-size` for compiled standalone binary via environment variable `DENO_V8_FLAGS` depending on the target systems hardware (RAM).

Todo: add `get_v8_flags_from_env()` [here](https://github.com/denoland/deno/blob/80331d1fe5b85b829ac009fdc201c128b3427e11/cli/standalone/mod.rs#L454C60-L454C66).
Repository: pytorch
Issue: Support Delay Loading of c10.dll in when using libtorch as a thirdparty library.
Labels: module: windows,module: abi,triaged

### 🚀 The feature, motivation and pitch

Hi PyTorch team,

I'm currently working on a project where I have added libtorch as a third-party dependency. Due to the size of libtorch, I wanted to make it an optional dependency using delay load hooks. However, I've encountered an issue with c10.dll, which is a dependency of libtorch. It seems that c10.dll exports a global variable, causing it to be unable to be delay loaded.

Here's the error message I encountered
![image](https://github.com/pytorch/pytorch/assets/7751507/0e15b927-c16f-411d-a399-72787387771e)

I'm wondering if it's possible to add support for delay loading c10.dll in libtorch. Having this feature would be really helpful for my project, as it will allow me to better manage the dependency loading and reduce the initial load time.

### Alternatives

_No response_

### Additional context

_No response_

cc @peterjc123 @mszhanyi @skyline75489 @nbcsm @vladimir-aubrecht @iremyux @Blackhex @cristianPanaite
Repository: deno
Issue: `deno compile -A npm:docker-meta@4.2.0` produces non working binary
Labels: bug,compile

Hello,

Following https://deno.com/blog/v1.34#deno-compile-supports-npm-packages I'm trying to to compile my own project to distribute it portably (https://github.com/felipecrs/docker-meta).

I know, it's a little old and I did not keep up with the dependency updates since some time, but I wonder if this actually uncovers a bug or some situation which would be nice for deno to cover.

```console
❯ node --version
v18.16.1
❯ npm --version
9.8.0
❯ npm install -g docker-meta@4.2.0

added 188 packages in 10s

20 packages are looking for funding
  run `npm fund` for details
❯ docker-meta --help
Generates docker meta information such as tags, labels and build-args.

USAGE
  $ docker-meta

OPTIONS
  -V                             show CLI version
  -c, --config=config            Path to the config file
  -h, --help                     show CLI help
  -o, --output=output            Path to the output file
  --branch=branch                The branch
  --build-date=build-date        The build date in ISO 8601
  --change-number=change-number  The change number
  --[no-]change-request          Change request mode
  --git-sha=git-sha              The git sha
  --[no-]latest                  Push as latest
  --[no-]tag-semver              Use semver strategy to generate tags
  --[no-]tag-version             Use `version` to generate tags
  --version=version              The version to publish

DESCRIPTION
  The config will be read from any valid config file in the current directory. The configuration file can be defined using all the extensions and
   names accepted by cosmiconfig, such as docker-meta.config.js

❯ deno --version
deno 1.35.0 (release, x86_64-unknown-linux-gnu)
v8 11.6.189.7
typescript 5.1.6

❯ deno compile -A npm:docker-meta@4.2.0
Compile npm:docker-meta@4 to docker-meta

❯ ./docker-meta --help
error: Reading /tmp/deno-compile-docker-meta/node_modules/localhost/@oclif/command/1.8.31

Caused by:
    No such file or directory (os error 2)
```
Repository: vscode
Issue: Ability to overtype angle brackets (similar to normal parentheses)
Labels: feature-request,snippets,editor-core

<!-- ⚠️⚠️ 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. -->

When using a language that auto-inserts angle brackets in code completions (such as Rust with `rust-analyzer` in generic type signatures) it would be very convenient if angle brackets could be "overtyped", similar to normal parentheses, as e.g. in method completions. A quick demo of the issue below:

https://github.com/microsoft/vscode/assets/30873659/7c134bf6-2e92-411a-8518-40e6b4a84147
Repository: PowerToys
Issue: Shortcuts for Window rescaling
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

I'd love to have the opportunity to assign shortcuts to resize windows and move them to certain zones. Also, It'd be great to have the ability to resize windows across multiple zones.

### Scenario when this would be used?

I often am in meetings where I'd like to resize the window across multiple zones, as my usual work zones are too small.

### Supporting information

_No response_
Repository: TypeScript
Issue: Add support for `willDeleteFiles`/`didDeleteFiles` to tsserver
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

`willDeleteFiles`/`didDeleteFiles`
update errors after deleting file
deleting file
removing file
renaming file

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [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 [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

Add support for `willDeleteFiles`/`didDeleteFiles` (https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_willDeleteFiles)
As for my current knowledge, `tsserver` right now watches filesystem on its own, as mentioned in [this article](https://www.typescriptlang.org/docs/handbook/configuring-watch.html). Unfortunately this method is not always correct and sometimes (specifically in larger repositories) after renaming files, or deleting them - `tsserver` does not know that the filesystem was changed resulting in out-of-sync error messages.
Adding support for such methods would allow editors to notify `tsserver` that something has changed and then `tsserver` could internally update it's state about the files.

## 📃 Motivating Example

https://github.com/microsoft/TypeScript/assets/35625949/1eec8678-8af6-43d0-bf2f-25eecbac0b96

In this example, when file is deleted by the user, the diagnostic about file not existing is not shown. It might be shown after some time in the future, but an editor can send this notification to the server immediately after user performs an action 

## 💻 Use Cases

For now the only way to deal with this is to restart `tsserver`. While this solution works it would be nicer user experience for this to happen automatically.
Repository: pytorch
Issue: [feature request] make the input k in rot90 a list of int to rotate tensors individually in a batch
Labels: feature,triaged,module: python frontend

### 🚀 The feature, motivation and pitch

I'm using torch.rot90(input, k=1, dims=[0, 1]) to rotate a batch sample. Since the k here should be an int, which means all the samples in a batch will be rotated with the same angle (because they share the same k). What I want to do is to rotate each sample of the batch separately because this will improve the accuracy of my task.

Is it possible to extend rot90 to make the input k a list of int, to make it possible to rotate tensors individually in a batch? 

### Alternatives

A simple alternative to achieve the function described above is to use the for loop: 

```python
import numpy as np
import torch

batch_sample = torch.randn(10, 1, 32, 32, 129)
for i in range(len(batch_sample)):
    k = np.random.choice(4, 1, replace=False)[0]
    batch_sample[i, :] = torch.rot90(batch_sample[i, :], k=k, dims=[1,2])
```

But it is slow using the for loop. So, I'm wondering if it is possible to extend rot90 to make the input k a list of int, making it faster to rotate tensors individually in a batch.


### Additional context

_No response_

cc @albanD
Repository: ant-design
Issue: Ability to render Date/Range Picker Panel separately
Labels: 💄 Design,💡 Feature Request,Inactive

### What problem does this feature solve?

I'd like to be able to render the panel as regular component. Not in a dropdown, not connected to an input.
<img width="598" alt="image" src="https://github.com/ant-design/ant-design/assets/1982853/fd803b96-0747-4206-a40b-36c27d135d02">

An example API:
```tsx
<PickerPanel.Range picker="year" value={...} onChange={...} />
```

#### Possible scenario:
- User opens a page with a "Select date range" button
- User clicks on the button
- A modal containing the picker panel opens up
- User makes his selection and clicks "ok" button
- The modal closes, the selection stores in an external storage (e.g. GET param)

#### In other words, input and picker panel are too tied to each other. I'd like to have a flexibility here:
- Render any component (not only an input) as element, which triggers the dropdown. Good example here is `<Tooltip>` or `<Dropdown>` (e.g. show picker panel by clicking on a `<Button>`)
- Render picker panel anywhere it needs to be rendered, not only in dropdown. An example here is `<Calendar>` or pretty much any other component

### What does the proposed API look like?

```tsx
<PickerPanel.Range picker="year" value={...} onChange={...} />
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: x/build/cmd/gerritbot: leave a CL comment on a freshly imported PR to help confirm the author has a Gerrit account
Labels: Builders,NeedsInvestigation

In #61182, Bryan has an excellent list of friction around the GitHub PR workflow, including:

> A significant fraction of GitHub PRs are abandoned when the author does not respond to Gerrit comments, but the existence of an open PR discourages other contributors from working on the corresponding issue.

One minor thing we could do to shave off some friction is leave a welcome comment in Gerrit after a PR is imported, wherein we:
 * ask the PR author to respond to the comment in Gerrit confirming the CL is ready for review, and
 * provide some context to the possibly new contributor, including a link to the Review section of the contributing guide

If they respond to the comment, a potential reviewer then knows that the author:
 * has a Gerrit account, and
 * knows how to reply in Gerrit

To make this suggestion more concrete, I will send a draft CL shortly.

### Possible extensions

A modest extension would be to have a reminder comment after a week or so if the author does not reply. This could include some hints around the reply mechanism, including to help with the problem of unpublished Gerrit draft responses.

Another extension would be to automatically abandon the CL and close the PR with an explanatory message if there is no reply after a month or so. This would help with the problem of an open PR discouraging other contributors.

Both of these possible extensions are left as TODOs in the code and possible future issues.