sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: options: add 'patchmodeskip', 'patchmodedir'
Labels: enhancement,needs:vim-patch,options

### Problem

I want to set some filetypes to be backup-ed. And other filetypes to keep their original. But backupskip applies universaly to backup and patchmode. The same for backupdir. (it would be nice to have a folder with my backup files while patchmoded .orig stay in the original folder.)

Example:

I have two files: an `example1.conf  `and an `example2.text`

Setting backup will create an `example.conf.bak` and an `example.text.bak` (or `example1.conf~` and `example2.text~` as per the original behavior.)

Setting `patchmode` will create `example1.conf.orig` and `example2.text.orig` respectively.

Given my aim is to have `example1.conf.orig` and `example2.text.bak`,

I read the `:h` on `backupskip`.

But (if I understand :h correctly,) `backupskip` applies both to `vim.opt.backup` and `vim.opt.patchmode`.

Therefore, if I was to add the extension `*.conf` to `backupskip`, I would end up with no example1 backup or original, and example2.text.bak along with an exampl2.orig

### Expected behavior

Having a `patchmodeskip` and `patchmodedir` would make for a clean solution to this.

I believe a solution could be devised with autocommands, but I am (rightfully?) reluctant to apply hacky solutions to the save-your-ass functionality that is a backup. It is supposed to to work when everything else fails, after all. In my mind (maybe I am wrong,) autocommandds would compromise it.
Repository: kubernetes
Issue: Default values of Kubelet's EvictionHard
Labels: priority/backlog,sig/node,kind/feature,triage/accepted

### What happened?

As we know, the default values of kubelet hard eviction's parameters are:
```
memory.available: "100Mi"
nodefs.available: "10%"
nodefs.inodesFree: "5%"
imagefs.available: "15%
```
When we change one of the default values, then the other unchanged parameters are set to 0. As per the code, this is the expected case.

### What did you expect to happen?

 The unchanged parameters should inherit their default values or is there any good scenario by setting the other parameters to 0.

### How can we reproduce it (as minimally and precisely as possible)?

NA

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
v1.25
```

</details>


### Cloud provider

<details>
NA
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: next.js
Issue: vercel deploy --prebuilt causes system environment variables to disappear
Labels: bug

### 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.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 20.4.0
      npm: 9.7.2
      Yarn: 1.22.19
      pnpm: 8.6.0
    Relevant Packages:
      next: 13.4.17-canary.0
      eslint-config-next: 13.4.16
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/Justinfan827/testing-vercel-cli

### To Reproduce

compare the deployed site when running:

```
vercel build
vercel deploy --prebuilt
```

vs

```
vercel deploy
```

### Describe the Bug

When running `vercel deploy`, the environment variable `NEXT_PUBLIC_VERCEL_URL` is populated correctly. However, when running `vercel build` and `vercel deploy --prebuilt`, this env var disappears.

<img width="1087" alt="Screenshot 2023-08-16 at 3 09 51 PM" src="https://github.com/vercel/next.js/assets/22778148/c0e53bd1-3fd4-46be-afe4-aca4f02c5dd2">

<img width="1119" alt="Screenshot 2023-08-16 at 3 12 28 PM" src="https://github.com/vercel/next.js/assets/22778148/f44c6555-baa5-46c0-a9c9-ee21a1f0ddc4">

### Expected Behavior

`NEXT_PUBLIC_VERCEL_URL` should always get populated even if running `vercel build` and `vercel deploy --prebuilt`

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Vercel
Repository: flutter
Issue: Ensure there are no conflicts while the Flutter SDK unzips engine artifacts
Labels: tool,P2,team-tool,triaged-tool

This is a follow up to https://github.com/flutter/flutter/issues/132592, to ensure it doesn't happen again.

Before we extract the Dart SDK zip archive on windows, we move the existing output to a backup, and then extract zip to previous location of the old one. However, when a new file was added to this archive (`LICENSE.dart_sdk_archive.md`) but the powershell file to extract it wasn't updated, the 7zip sub-process that was spawned would prompt the user what they wanted to do about the conflict, but the powershell script would never surface this prompt to the user.

This was fixed by special-casing this file. However, we need a more robust solution to prevent this from happening again.
Repository: flutter
Issue: Document the pattern of having IsValid methods on objects in the engine.
Labels: P2,team-engine,triaged-engine

Engine objects generally follow a pattern of not attempting to repair broken things. If an object is invalid, it needs to be discarded and a new one recreated. If the owner of an invalid object cannot create a new valid instance of the object, it itself may become invalid and so on. Valid objects may become invalid but invalid object never become valid later. Factories also never return invalid objects by convention.

This convention needs to be documented and the cases where an object may become invalid enumerated in the headerdocs for that object.
Repository: next.js
Issue: intercepting routes: break when using middleware in dev mode
Labels: bug,Parallel & Intercepting Routes

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information
```
Provide environment information
 Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:19 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.4.0
      npm: 8.12.1
      Yarn: 1.22.17
      pnpm: 8.6.5
    Relevant Packages:
      next: 13.4.16
      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) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

[vercel](https://vercel.live/link/nextgram-git-middleware-cryptickoan.vercel.app?via=deployment-domains-list-branch)

https://github.com/cryptickoan/nextgram/tree/middleware

### To Reproduce

Code can be found in the middleware branch of the nextgram fork i provided. 

1. Run the project locally 
2. Click a picture, modal will be shown
3. Dismiss modal
4. Click another picture, modal will not be shown

### Describe the Bug

When running locally middleware rewrites break intercepting routes

### Expected Behavior

When running locally middleware rewrites should work fine.
 Its a bit confusing I actually realized it was a development environment problem till I deployed this to Vercel to create an issue. It works fine in Vercel.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

locally
Repository: vscode
Issue: vscode terminal sends ctrl+<arrow key> instead of alt+<arrow key>
Labels: bug,help wanted,under-discussion,terminal-input

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.80.0
- OS Version: Windows 10

Steps to Reproduce:

1. Enable terminal.integrated.sendKeybindingsToShell
2. Focus terminal and press alt and any arrow key

I used `fish_key_reader` to see what the terminal is sending:

- vscode terminal
  - alt+left: `\e\[1\;5D`
  - ctrl+left: `\e\[1\;5D`
- windows terminal, gnome terminal, etc
  - alt+left: `\e\[1\;3D`
  - ctrl+left: `\e\[1\;5D`

Tried searching through the options and old issues, but couldn't find anything to resolve it
Repository: puppeteer
Issue: [Bug]: Scrolled to bottom element screenshot shifts scroll position and clips bottom
Labels: bug,screenshot,confirmed,P3

### Minimal, reproducible example

```TypeScript
// code sample possibly not perfect. everything inside the try was tested inside our test env (jest-puppeteer), and it reproduced the bug.
import puppeteer from 'puppeteer'; // TS/ESM are all supported.

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  try {
    await page.evaluate(
    ({ dataURL }) => {
        const container = document.createElement("div");
        container.setAttribute("id", "container");
        container.setAttribute(
        "style",
        "height: 200px; width: 328px; overflow: auto;"
        );

        // inner contents containing image
        const child = document.createElement("div");
        child.setAttribute("id", "child");
        child.setAttribute(
        "style",
        "height: 370px; width: 328px; background-image: url(" + dataURL + ");"
        );
        container.appendChild(child);

        document.body.appendChild(container);
    },
    // bambi and skunks cartoon and irl
    { dataURL: 'https://i.imgur.com/XOeC8im.png' }
    );

    const containerSelector = "#container";
    const containerElement = await page.$(containerSelector);
    if (containerElement) {
    const [scrollHeight] = await page.evaluate(
        (el) => [el.scrollHeight],
        containerElement
    );

    await page.evaluate(
        ({ containerSelector, y }) => {
        document.querySelector(containerSelector)?.scrollBy(0, y);
        },
        {
        containerSelector,
        scrollHeight,
        }
    );
    const im = await containerElement.screenshot({
        type: "png",
        encoding: "binary",
        path: "screenshot.png",
    });
    }
    
  } catch {
    throw new Error('Something went wrong');
  }
  await browser.close();
})();
```


### Error string

no error

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

Been trying to make a utility to capture a single screenshot of the scrollable contents of a container. It stitches several screenshots together in the end. The last one is always off because of this.
Using this via jest-puppeteer. The screenshot command comes from this library.

### Expectation

Expected the last screenshot to be the element scrolled to the very bottom.

### Reality

Before screenshot, the scroll position is correct. During screenshot and after, the scroll position is altered.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

21.4.1

### Node version

18.16.0

### Package manager

npm

### Package manager version

9.5.1

### Operating system

Windows
Repository: material-ui
Issue: [CssBaseline] Consider rework
Labels: breaking change,package: system,component: CssBaseline

This issue is extracted from #30660 to have a space to discuss the improvements we can make to this component.

CssBaseline was introduced around 2019, today browsers are different, time to consider how to best evolve it.

Ideas:

1. https://moderncss.dev/modern-css-for-dynamic-component-based-architecture/
2. add html { overflow-y: scroll; } to avoid layout shift when changing pages or maybe https://twitter.com/stackblitz/status/1518924375721873408 but it doesn't seem to work with position absolute elements.
3. separate CSS resets and theme application https://github.com/mui/material-ui/pull/38135#issuecomment-1660941951
4. Remove `enableColorScheme` altogether, see: https://github.com/mui/material-ui/issues/42695 or make `enableColorScheme: true` the default https://github.com/mui/material-ui/pull/29611#issuecomment-966391839 
5. button margin should be reset? I shouldn't have to spend time to do this #34861.
6. `min-width: 0` everywhere: https://www.youtube.com/watch?v=cH8VbLM1958


### Benchmark

- https://tailwindcss.com/docs/preflight 
- https://twitter.com/souporserious/status/1746311121949356469
- https://www.youtube.com/watch?v=cCAtD_BAHNw
Repository: flutter
Issue: ExpansionPanelList should have a `builder` option, just like `ListView`
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### 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

`ExpansionPanelList` are lists after all, but right now we can't make them lazy.

### Proposal

Give `ExpansionPanelList` a `builder` constructor, just like other widgets, like `ListView` has.
Repository: react-native
Issue: There is no way to manage focus for external keyboard from one element to another
Labels: Issue: Author Provided Repro,API: Keyboard,Needs: Triage :mag:

### Description

Sometimes we need to set external keyboard focus from one place to another, for instance from one `Pressable` to another `Pressable`, or from a `Pressable` to a `View`. 

For Screen Reader users we can use `AccessibilityInfo.setAccessibilityFocus(tag)` to manage focus, but this technique does not work for the external keyboard when a screen reader is not switched on. 

The standard React method of `ref.current.focus()` also does not work for external keyboard users on mobile (only web).

### React Native Version

0.71.3

### Output of `npx react-native info`

I don't have access to this.

### Steps to reproduce

On Android or iOS physical device:

1. Connect a hardware keyboard to the device using bluetooth.
2. Open https://snack.expo.dev/@nedgip/external-keyboard-focus-example-1 in Expo Go
3. Navigate to the Send focus button using arrow keys
4. Press Space 

### Expected
Focus should move to the Receive focus button

### Actual
Focus remains on the Send focus button


### Snack, screenshot, or link to a repository

1. https://snack.expo.dev/@nedgip/external-keyboard-focus-example-1
2. https://snack.expo.dev/@nedgip/external-keyboard-focus-example-2
Repository: flutter
Issue: ExpansionPanelList should have zero padding surrounding header and gap size between ExpansionPanel child by default
Labels: framework,f: material design,c: proposal,P2,team-design,triaged-design

The `ExpansionPanelList` header is changing it's height while it expands/contracts.

MD3 doesn't provide specs for it, but it's possible to see that the header doesn't change height while expanded.
https://m3.material.io/components/lists/guidelines#f6fe9c4e-7498-420a-b820-d12a2b59fc99

But MD2 does provide specs for Collapsed & Expanded:
https://m2.material.io/components/lists#specs

I can't share my current code, but I bet the example at `examples/api/lib/material/expansion_panel/expansion_panel_list.0.dart` should be enough to reproduce it.
Repository: flutter
Issue: Add "scaleSlop" in DeviceGestureSettings and GestureDetector respect it.
Labels: c: new feature,framework,f: gestures,c: proposal,P3,team-framework,triaged-framework

### 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

I want to make the Scale in GestureDetector more responsive like native.
I found out that we can improve panning by adjust panSlop in DeviceGestureSettings .
But it seems no way to adjust scaleSlop.
[`https://github.com/flutter/flutter/blob/fe9c7f4fa7bfadaff4d4110313e0750eacc5d0e7/packages/flutter/lib/src/gestures/events.dart#L2467`](https://github.com/flutter/flutter/blob/fe9c7f4fa7bfadaff4d4110313e0750eacc5d0e7/packages/flutter/lib/src/gestures/events.dart#L2467)

### Proposal

Add scaleSlop in DeviceGestureSettings and respect in computeScaleSlop
Repository: pytorch
Issue: dist.scatter is incompatible with transpose/permute operation
Labels: oncall: distributed,triaged

### 🐛 Describe the bug

I found that when using dist.scatter() (torch 2.0.1, backend=nccl) and the tensors in scatter tensor list have been modified by operations such as transpose, permute, etc., (so that it is not contiguous), the results are abnormal. Here is the demo.

```import os
 
import torch
import torch.distributed as dist
import torch.multiprocessing as mp
 
 
def main(rank):
    dist.init_process_group(backend="nccl", world_size=2, rank=rank)
    device = f"cuda:{rank}"
 
    a = torch.arange(0, 4).reshape((2, 2)).to(torch.float).to(device)
    b = torch.arange(4, 8).reshape((2, 2)).to(torch.float).to(device)
    a = a.transpose(0, 1) # [[0,2],[1,3]]
    b = b.transpose(0, 1) # [[4,6],[5,7]]
    src = [a, b] if rank == 0 else None
    dst = torch.zeros((2, 2)).to(device)
    dist.scatter(dst, src, 0)
    """
    Expected result of dst:   rank0 [[0,2],[1,3]] rank1 [[4,6],[5,7]]
    Real result of dst:   rank0 [[0,2],[1,3]] rank1 [[4,5],[6,7]]
    """
    print(rank, dst)
 
 
if __name__ == "__main__":
    os.environ["MASTER_ADDR"] = "127.0.0.1"
    os.environ["MASTER_PORT"] = "6666"
    mp.spawn(main, nprocs=2)
```

I guess the scatter() directly copy the corresponding memory (without consider the stride variation caused by tranpose/permute) to the dest. However, this is not what the users expect. A simple way to solve this issue is to add a check script at the beginning of the scatter operation like:

```
if not a.is_contiguous():
    a = a.contiguous()
```

Also, I'm not sure if the bug will appear for other DDP operations like gather, reduce, etc.



### Versions

PyTorch version: 2.0.1+cu117


cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu
Repository: TypeScript
Issue: Cannot await Thenable
Labels: Needs Investigation

### 🔎 Search Terms

"Type of 'await' operand must either be a valid promise or must not contain a callable 'then' member.", "TS1320"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about async

### ⏯ Playground Link

https://www.typescriptlang.org/play?target=9#code/PTAEAEBcEMCcHMCmkBcoCiBlATABm9gFCEDGA9gHYDOkoAtgJ4AqAFohdAEYA2ioAvKADehUKEhsKACkoAxAK7cAZgEtuvACYAaUJQBKiAFaISkRBoCUQ0LGTzYFXRQXK1mgPwA6KQEYLoAF9CIMJoKgYKElAleUjIFUpQaDpoFWl-ETFQcmpaWAEkgHdU2kZWdi5eAG5RMRyqMl5PbjJ4KQByADdobnlEdp1YHXaUAfEGAAdEMiUbCxqs20h7R1gakLLJSr4qaHiqVUQqUAAFWDI6FSpEABkVAGtEAB4KeTpORFgAPmJryCYVHRpvJIFJkqkKDpcBYgA

### 💻 Code

```ts repro
// @target: ES2022

const myThenable = {
  then(onFulfilled, onRejected){ return onFulfilled?.(1) }
}

async function amain() {
   const r = await myThenable;
   console.log('value', r, ':', typeof r);
   return r;
}

myThenable satisfies PromiseLike<number>

setTimeout(amain, 0)
```

[Workbench Repro](https://www.typescriptlang.org/dev/bug-workbench/?target=9#code/PTAEAEBcEMCcHMCmkBcoCiBlATABm9gFCEDGA9gHYDOkoAtgJ4AqAFohdAEYA2ioAvKADehUKEhsKACkoAxAK7cAZgEtuvACYAaUJQBKiAFaISkRBoCUQ0LGTzYFXRQXK1mgPwA6KQEYLoAF9CIMJoKgYKElAleUjIFUpQaDpoFWl-ETFQcmpaWAEkgHdU2kZWdi5eAG5RMRyqMl5PbjJ4KQByADdobnlEdp1YHXaUAfEGAAdEMiUbCxqs20h7R1gakLLJSr4qaHiqVUQqUAAFWDI6FSpEABkVAGtEAB4KeTpORFgAPmJryCYVHRpvJIFJkqkKDpcBYgA)

### 🙁 Actual behavior

An error is shown:
> Type of 'await' operand must either be a valid promise or must not contain a callable 'then' member.

### 🙂 Expected behavior

I expect no error or a suppressible warning. I also expect some explanation of "why" or a suggestion like "wrap the thenable in a `Promise.resolve()`"

### Additional information about the issue

This is valid JavaScript, and executes in Deno, Node, Chrome, and Firefox.

Note that `await` doesn't even require its argument to be a `PromiseLike` - `then` may have return type `void` or even `never`!
Repository: godot
Issue: MultiplayerSpawner doesn't track nodes that are already in the scene file.
Labels: bug,topic:multiplayer

### Godot version

v4.1.1.stable.mono.official.bd6af8e0e

### System information

Godot v4.1.1.stable.mono - EndeavourOS

### Issue description

The MultiplayerSpawner doesn't track nodes that are already in the scene file.

This makes it very difficult to build the map on a server, and have it be sent to the client. (Separate projects)

It also has the side effect of not being able to despawn nodes that were already built into the scene file.

### Steps to reproduce

Add a spawnable scene, as a child of the spawn path. It will not be tracked, (it won't be sent to the client, and if it already exists it won't be despawned when the server requests it)

---

For the project, make sure you have run multiple instances, set to at least 2.
Choose one instance to be the client, and the other to be the server.

You can see that the instances that are added with add_child spawn and despawn just fine.
But the ones that were built into the scene file don't work. 
 - One of them doesn't replicate to the client.
 - The other doesn't get despawn on the client when the server requests it.


### Minimal reproduction project

[project.zip](https://github.com/godotengine/godot/files/12365752/project.zip)