sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_successful (jit.test_freezing.TestMKLDNNReinplacing)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_successful) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/10335682113).

Over the past 72 hours, it has flakily failed in 2 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_successful`


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: DISABLED test_requires_grad_loop (test_jit.TestScript)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_requires_grad_loop) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/10335682113).

Over the past 72 hours, it has flakily failed in 2 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_requires_grad_loop`


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: DISABLED test_prim_grad_undefined (test_jit.TestScript)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_prim_grad_undefined) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/10335682113).

Over the past 72 hours, it has flakily failed in 2 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_prim_grad_undefined`


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: DISABLED test_optional_tensor (test_jit.TestScript)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_optional_tensor) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/10335682113).

Over the past 72 hours, it has flakily failed in 2 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_optional_tensor`


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: DISABLED test_rand (test_jit.TestScript)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_rand) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/10335682113).

Over the past 72 hours, it has flakily failed in 2 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_rand`


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: DISABLED test_tensor_requires_grad (test_jit.TestScript)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_tensor_requires_grad) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/10335682113).

Over the past 72 hours, it has flakily failed in 2 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_tensor_requires_grad`


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: godot
Issue: Kinematicbody2D lose collision one frame when switch between collision shape
Labels: bug,topic:physics,topic:2d

### Godot version

3.x

### System information

Windows 10

### Issue description

If a Kinematicbody has 2 collision shape, one enabled and the other disabled ,when use shape_owner_set_disabled(idx, bool) to switch the collision shape, this KinematicBody will not been detect by Area2D in one frame. The Area2D detect that body exit then enter again. That means change collision shape's result update in 2 frames later.

I test it with the shape_owner_add_shape() and shape_owner_remove_shape(), and it still happens

This will be happen no matter which shape  you enable or disable first.
This wont happen when there is a third shape exist.

### Steps to reproduce

Use  shape_owner_set_disabled(idx, bool) to switch collisionshape, then use area2d to detect it.

### Minimal reproduction project

[CollisionShapeSwitch.zip](https://github.com/godotengine/godot/files/10317664/CollisionShapeSwitch.zip)
Repository: rust
Issue: Bounds checks on non-contiguous accesses are not eliminated in rustc 1.29 through at least 1.66
Labels: A-LLVM,I-slow,P-medium,T-compiler,regression-from-stable-to-stable,C-bug

### Code

I tried this code:

```rust
pub fn fibonacci_vec(fib:&mut [u8])  {
    
        if fib.len() > 2 {
            // The compiler now knows that `fib` is fixed-size
            // and we are iterating exactly up to its length
            for i in 2..fib.len() {

                // bounds check present on 1.29 and later
                fib[i] = fib[i-2]; 

                // no bounds check in any recent version
                //fib[i] = fib[i-2]+fib[i-1]; 

            }
        }

}
```

In rustc 1.28, bounds checks are eliminated in both of these lines. However, 1.29 through 1.66 fail to eliminate the bounds check on ` fib[i] = fib[i-2]`, even though they always remove the bounds check on the `fib[i] = fib[i-2]+fib[i-1]` line (if you uncomment it and comment the other).

**Godbolt: https://godbolt.org/z/3K3WaGjEY**

Thanks to @etemesi254 for discovering the issue and providing a minimal example.

### Version it worked on

It most recently worked on: rustc 1.28 in Godbolt

### Version with regression

Tested 1.66 locally, other versions in Godbolt:

`rustc --version --verbose`:
```
rustc 1.66.0 (69f9c33d7 2022-12-12)
binary: rustc
commit-hash: 69f9c33d71c871fc16ac445211281c6e7a340943
commit-date: 2022-12-12
host: x86_64-unknown-linux-gnu
release: 1.66.0
LLVM version: 15.0.2
```

@rustbot modify labels: +regression-from-stable-to-stable -regression-untriaged +I-slow
Repository: neovim
Issue: Incorrect JavaScript syntax highlighting
Labels: runtime,bug-vim,syntax,needs:vim-patch

### Neovim version (nvim -v)

0.8.1

### Vim (not Nvim) behaves the same?

yes, 9.0.1046

### Operating system/version

Arch Linux

### Terminal name/version

Konsole 22.12.0

### $TERM environment variable

xterm-256color

### Installation

pacman

### How to reproduce the issue

- `nvim --clean`
- `:set syntax=javascript`
- Enter `/^\//.test("/")`

### Expected behavior

Correct syntax highlighting.
Symbol `/` after `^\` is escaped, and represents a literal `/` in this case. Second `/` signals the end of regex.
Example:
![img](https://user-images.githubusercontent.com/5338332/209909264-fb246e16-31cc-47a2-87ea-0cf1f9a97bb0.png)


### Actual behavior

`//` is interpreted as the start of a comment.
![img](https://user-images.githubusercontent.com/5338332/209909093-22a07ef4-15c9-40e3-9e08-fee042aa57a7.png)
Repository: flutter
Issue: TextInputConnection should let objects listen for IME connection closure
Labels: a: text input,c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

An IME connection is established with these pieces: `TextInput`, a `TextInputConnection`, and a `TextInputClient`.

```dart
final myConnection = TextInput.attach(myInputClient, myConfig);
```

`TextInputConnection` has a `bool` that reports `isAttached`, but there's no way to listen for a change to this attachment.

The `TextInputClient` has a method called `connectionClosed`, which, I assume, represents a notification that the IME connection has closed. However, policies about when to open and close a connection are usually independent from the policies that apply text input messages from the platform. Therefore, the use of `TextInputConnection` should be able to exist independently from the code that implements `TextInputClient`, and this requires that `TextInputConnection` receive a notification when its connection is closed.

```
Flutter 3.7.0-1.2.pre • channel beta • https://github.com/flutter/flutter.git
Framework • revision c29b09b878 (9 days ago) • 2022-12-19 18:30:12 -0600
Engine • revision 8c99b0feaf
Tools • Dart 2.19.0 (build 2.19.0-444.2.beta) • DevTools 2.20.0
```
Repository: create-react-app
Issue: nth-check  <2.0.1 Severity: high &&  json5  <2.2.2 Severity: high
Labels: needs triage,issue: bug report

json5  <2.2.2
Severity: high
Prototype Pollution in JSON5 via Parse Method - https://github.com/advisories/GHSA-9c47-m6qq-7p4h
fix available via `npm audit fix --force`
Will install react-scripts@4.0.3, which is a breaking change
node_modules/tsconfig-paths/node_modules/json5
  tsconfig-paths  3.5.0 - 3.9.0 || 3.11.0 - 3.14.1
  Depends on vulnerable versions of json5
  node_modules/tsconfig-paths
    eslint-plugin-import  >=2.24.2
    Depends on vulnerable versions of tsconfig-paths
    node_modules/eslint-plugin-import
      eslint-config-react-app  >=7.0.0-next.75
      Depends on vulnerable versions of eslint-plugin-import
      node_modules/eslint-config-react-app
        react-scripts  >=2.1.4
        Depends on vulnerable versions of @svgr/webpack
        Depends on vulnerable versions of eslint-config-react-app
        node_modules/react-scripts

nth-check  <2.0.1
Severity: high
Inefficient Regular Expression Complexity in nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr
fix available via `npm audit fix --force`
Will install react-scripts@4.0.3, which is a breaking change
node_modules/svgo/node_modules/nth-check
  css-select  <=3.1.0
  Depends on vulnerable versions of nth-check
  node_modules/svgo/node_modules/css-select
    svgo  1.0.0 - 1.3.2
    Depends on vulnerable versions of css-select
    node_modules/svgo
      @svgr/plugin-svgo  <=5.5.0
      Depends on vulnerable versions of svgo
      node_modules/@svgr/plugin-svgo
        @svgr/webpack  4.0.0 - 5.5.0
        Depends on vulnerable versions of @svgr/plugin-svgo
        node_modules/@svgr/webpack
          react-scripts  >=2.1.4
          Depends on vulnerable versions of @svgr/webpack
          Depends on vulnerable versions of eslint-config-react-app
Repository: neovim
Issue: `<Esc>` from mapping executes cmdline in command mode
Labels: needs:discussion,complexity:low,mappings

### Neovim version (nvim -v)

NVIM v0.9.0-dev-1763+g9be24110f-dirty (Build type: Release)

### Vim (not Nvim) behaves the same?

unsure (probably?)

### Operating system/version

macOS 11.7.3

### Terminal name/version

kitty 0.26.5

### $TERM environment variable

xterm-kitty

### Installation

`brew install --HEAD neovim`

### How to reproduce the issue

Within an interactive terminal/shell, do:

```vim
nvim --clean -c "cnoremap <expr> <Esc> '<Esc>'"
```

Now, type `:cq` followed by the escape key on your keyboard.

### Expected behavior

I expect the behavior to be identical to what occurs when escape is pressed while not mapped. That is:

1. whatever was typed on the cmdline is saved in the command history
2. the cmdline itself should clear/become blank (no text)
3. command mode is exited without any commands being executed (unless there are `CmdlineLeave` autocmds defined, of course)

TLDR: the cmdline is "aborted"

### Actual behavior

The difference in actual vs expected behavior occurs when escape is pressed, wherein the current contents of the cmdline are executed causing Neovim to exit with exit-code `1` (due to the `cq` command being executed). Generally speaking, Neovim behaves as if `<Esc>` was mapped to `<CR>`, making it very difficult, if not impossible, to have a useful command mode mapping for the escape key (e.g. a conditional mapping such as: _close the completion window if it is visible, otherwise abort the cmdline with `<Esc>` as if it had never been mapped in the first place_).

In other words, Neovim essentially behaves as if the `x` option/flag of `&cpo` (aka `cpoptions`) is set, even though this is definitely not the case (as `x` is off by default, plus I continue to experience this bug even after explicitly running `set cpo-=x`). Neovim does **not** behave this way when escape is pressed while not mapped however, so I don't quite understand why the behavior differs here (receiving escape naturally vs via <expr> map). I am unsure if this is a bug, user error, or expected behavior, etc.
Repository: material-ui
Issue: [Chip] it should accept a custom color
Labels: component: chip

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

The `Chip` component accepts a `color` attribute, but it can only refer to a color from the theme:

```
<Chip label="primary" color="primary" />
```

A custom color can be provided by a wrapping `ThemeProvider`, e.g.:

```
export const ColorChip: React.FunctionComponent<ColorChipProps> = (props) => {
  return (
    <ThemeProvider
      theme={(theme: Theme) =>
        createTheme({
          ...theme,
          palette: {
            ...theme.palette,
            primary: {
              main: props.color.color,
            },
          },
        })
      }
    >
      <Chip
        color="primary"
        label={props.color.name}
        onClick={() => props.onSelectedChange(!props.isSelected)}
        variant={props.isSelected ? 'filled' : 'outlined'}
        sx={{
          border: props.isSelected ? `1px solid ${props.color.color}` : undefined,
        }}
      />
    </ThemeProvider>
  )
}
```

This works fine, until multiple of those chips get changed at once - re-inserting the `ThemeProvider` components is really slow (38 chips takes over 5 seconds, with the UI freezing in the meantime).

Another approach would be to override the background color, e.g.:

```
export const ColorChip: React.FunctionComponent<ColorChipProps> = (props) => {
  const styleOverride = props.isSelected ? {backgroundColor: props.color.color} : {}
  return (
    <Chip
      color="primary"
      label={props.color.name}
      onClick={() => props.onSelectedChange(!props.isSelected)}
      variant={props.isSelected ? 'filled' : 'outlined'}
      sx={{
        border: props.isSelected ? `1px solid ${props.color.color}` : undefined,
      }}
      style={styleOverride}
    />
  )
}
```

The problem with this option is that it requires some knowledge about the implementation of the component - e.g. not overriding the primary color means MUI is unable to determine whether it should use a dark or light text color, the hover effect breaks...

Allowing to use a custom color directly would likely not be a complex change in the component itself, but would solve both of those problems.

### Examples 🌈

This could be used like this:

```
<Chip
  color="#123abc"
  label='label'
/>
```

### Motivation 🔦

As outlined above, this is to make the component more flexible.
Repository: excalidraw
Issue: typescript backwards compatibility
Labels: discussion

Would love to use the [`satisfies`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-9.html#the-satisfies-operator) operator, but it'll break types for host apps running on TS < 4.9.

Post 1.0 we should be way more mindful of breaking like this, but right now, IMO I'd do it.

For most projects, upgrading to 4.9 should require none to very few changes to the codebase.
Repository: material-ui
Issue: [NumberInput] Automatic currency formatting
Labels: new feature,waiting for 👍,component: number field

### Summary 💡

A Textfield which will get an number (amount in cents) and the input will format it in dollars or euros or whatever currency, according to the currency or the local given to the Input threw a prop

### Examples 🌈

It will do something like this. An npm package do already this but it is no longer maintained. Here is the github repository (https://github.com/unicef/material-ui-currency-textfield)
![material-ui-currency-field](https://user-images.githubusercontent.com/114908589/209938694-714a078f-f01f-418c-911d-047bb7431092.gif)


### Motivation 🔦

Currently I am building a admin interface in which i have to edit prices. As usual the API i'm using return to me currecy in cents and i would like to edit the amount in dollars/euro and sumbmit it again in cents to the API
Repository: vscode
Issue: Navigate back ( ^ - ) not working on notebooks
Labels: bug,notebook


Type: <b>Bug</b>

Create any notebook.
Navigate to another cell
Press ^ - and nothing happens.

VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:26:09.430Z)
OS version: Darwin x64 20.6.0
Modes:
Sandboxed: No
Connection to 'dev-container+2f55736572732f7961726f6e2f636f64652f656c656374696f6e735f7472656e64' could not be established

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|4, 4, 3|
|Memory (System)|16.00GB (0.13GB free)|
|Process Argv|--crash-reporter-id 5d72c8c8-e28b-4dee-893b-5ce4470d0146|
|Screen Reader|no|
|VM|0%|

Connection to 'dev-container+2f55736572732f7961726f6e2f636f64652f656c656374696f6e735f7472656e64' could not be established
</details><details><summary>Extensions (24)</summary>

Extension|Author (truncated)|Version
---|---|---
better-toml|bun|0.3.2
regex|chr|0.4.0
vscode-clock|Com|0.0.1
xml|Dot|2.5.1
gitlens|eam|13.2.0
code-runner|for|0.11.8
copilot|Git|1.65.7705
todo-tree|Gru|0.0.220
vsc-python-indent|Kev|1.18.0
vscode-docker|ms-|1.23.3
isort|ms-|2022.8.0
python|ms-|2022.20.1
vscode-pylance|ms-|2022.12.20
jupyter|ms-|2022.11.1003412109
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.12
vscode-jupyter-cell-tags|ms-|0.1.6
vscode-jupyter-slideshow|ms-|0.1.5
remote-containers|ms-|0.266.1
autodocstring|njp|0.6.1
vscode-yaml|red|1.10.1
jinjahtml|sam|0.19.0
sourcery|sou|1.0.2
vscode-icons|vsc|12.0.1


</details>
<!-- generated by issue reporter -->
Repository: ant-design
Issue: Bundle size optimization for v5
Labels: help wanted,📦 Bundlesize

We did it in https://github.com/ant-design/ant-design/issues/38720 before, and continue it recently.

- [x] https://github.com/ant-design/ant-design/issues/39594
- [x] https://github.com/ant-design/ant-design/pull/39662

Here is the current bundle size: https://github.com/ant-design/ant-design/pull/39898#issuecomment-1367204418

| Path                              | Size      |
| --------------------------------- | --------- |
| `./dist/antd.min.js`              | 367.29 KB |
| `./dist/antd-with-locales.min.js` | 422.41 KB |

[report.html.zip](https://github.com/ant-design/ant-design/files/10319114/report.html.zip)
---

Since we drop legacy browsers support, there are still something we can optimize.

- [ ] Like [antd-tools](https://github.com/ant-design/antd-tools/pull/269), we could remove IE and legacy browsers transform for react-component too. By setting [targets](https://github.com/umijs/father/blob/master/docs/config.md#targets) in https://github.com/react-component/tour/blob/master/.fatherrc.js
- [ ] @ant-design/icons unnecessary internal component, we could reduce it.
   - https://unpkg.com/browse/@ant-design/icons@4.8.0/AccountBookFilled.js
   - https://unpkg.com/browse/@ant-design/icons@4.8.0/es/icons/AccountBookFilled.js
   - https://unpkg.com/browse/@ant-design/icons-svg@4.2.1/es/asn/AccountBookFilled.js
- [ ] Remove [resize-observer-polyfill](https://bundlephobia.com/package/resize-observer-polyfill@1.5.1)
- [x] Refactor to function component for Transfer/Affix/Input/Collapse
  - [x] https://github.com/ant-design/ant-design/issues/39893
  - [x] https://github.com/ant-design/ant-design/issues/39892
  - [x] Collapse https://github.com/react-component/collapse/pull/287#issuecomment-1367245979
  - [x] Input/TextArea https://github.com/react-component/textarea/pull/19
  - [x] rc-pagination https://github.com/react-component/pagination/pull/514
- [ ] Use ES classes, remove these babel plugins: https://github.com/ant-design/antd-tools/blob/3b3447eb106a80ebc64e634ca60ce1cd55e8a351/lib/getBabelCommonConfig.js#L20-L22
- [x] remove displayName in production mode https://github.com/ant-design/ant-design-icons/pull/570
Repository: rust
Issue: Iterator::max_by_key twice as slow than manual implementation
Labels: C-enhancement,T-libs

Here's the reproduction repo:

  * https://github.com/fasterthanlime/slow-max-by-key
 
The README has repro instructions (essentially `cargo bench`, via criterion). I tried to golf it down a little, but it still has a bunch of dependencies. Sorry!

---

Essentially, this is fast (mvs is an iterator):

```rust
        // find best move
        {
            let mut best_state: Option<State<'net>> = None;

            for mv in mvs {
                let mut next: State<'net> = state.clone();
                let actor = &mut next.actors[0];
                actor.in_progress_move = Some(mv);
                actor.step(next.net, &mut next.inner);

                let end_state: State<'net> = next.run_manual();
                if end_state.pressure > best_state.as_ref().map(|s| s.pressure).unwrap_or_default()
                {
                    best_state = Some(end_state);
                }
            }

            match best_state {
                Some(state) => {
                    // we reached the end
                    state
                }
                None => {
                    // no moves possible, just wait it out
                    state.run_manual()
                }
            }
        }
```

But this is slow:

```rust
        mvs.map(|mv| {
            let mut next: State<'net> = state.clone();
            let actor = &mut next.actors[0];
            actor.in_progress_move = Some(mv);
            actor.step(next.net, &mut next.inner);
            next.run_max_by_key()
        })
        .max_by_key(|state| state.pressure)
        .unwrap_or_else(|| state.run_max_by_key())
```

Which is a shame, since I like the latter a lot more!

Reproduced with:

```shell
$ rustc -vV
rustc 1.68.0-nightly (270c94e48 2022-12-28)
binary: rustc
commit-hash: 270c94e484e19764a2832ef918c95224eb3f17c7
commit-date: 2022-12-28
host: x86_64-unknown-linux-gnu
release: 1.68.0-nightly
LLVM version: 15.0.
```

Prior art: #52543 (which I couldn't reproduce)
Repository: pytorch
Issue: Update map_nt to take into account size and strides
Labels: triaged,module: nestedtensor,bug

# Summary

Since map_nt doesn't check that the input is contiguous but only that the numels of the input match that of the buffer. This is in order to allow for the unary ops to be run on transposed inputs. We should also update the  map_nt to construct the output tensor with the same stride and offset information.

cc @cpuhrsch @jbschlosser @bhosmer @mikaylagawarecki