sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Kubernetes upgrade - "api-resources" call fails
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

During **upgrade**, when some kube-apiservers were in 1.21 and others were in 1.20, api-resources call fails on older servers (1.20)

Example:
```
kubectl api-resources --api-group airbnb.com --context=test
NAME                           SHORTNAMES   APIVERSION      NAMESPACED   KIND
blah                                        airbnb.com/v1   true         Alert
blah                                        airbnb.com/v1   true         AlertStaging
...   
error: unable to retrieve the complete list of server APIs: discovery.k8s.io/v1: the server could not find the requested resource, policy/v1: the server could not find the requested resource
```

Regarding being an unsupported version, `staging/src/k8s.io/client-go/discovery/discovery_client.go` nothing related to this has changed since 1.20. So the problem probably still exists in 1.25.

### What did you expect to happen?

```
kubectl api-resources --api-group airbnb.com --context=test
```
to not error out when the control plane is in different versions during migration.

### How can we reproduce it (as minimally and precisely as possible)?

* Launch control-plane on one version. 
* Add one api-server on new version. Hopefully there are some new api differences between the two versions 
* Query `kubectl api-resources --api-group airbnb.com --context=test` on the old version. See the failure.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.14-airbnb0", GitCommit:"a9ec715b66c6198ce1ed415db5c65eeb4e6a760d", GitTreeState:"clean", BuildDate:"2022-09-19T20:14:11Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}```
</details>


### Cloud provider

<details>
Self hosted
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"

$ uname -a
Linux i-00a122bfd961601ac 5.10.144-127.601.amzn2.x86_64 #1 SMP Thu Sep 29 01:11:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>
cri-o
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: storybook
Issue: [Feature Request]: Write proper documentation for components exported by @storybook/addon-docs
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

I couldn't find any documentation on how to use Docs "blocks", i.e. components exported by @storybook/addon-docs.
As components like `Primary` seem to have a particular logic that cannot be inspected, it would be great to have proper documentation on how to use them.

### Describe the solution you'd like

Create documentation on how to implement a customized "DocsPage" using the components exported by the  `@storybook/addon-docs` package.

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

no

### Additional context

An example of the implementation of these components can be found in the [docs](https://storybook.js.org/docs/react/writing-docs/docs-page)
```
// Button.stories.js|jsx

import React from 'react';

import {
  Title,
  Subtitle,
  Description,
  Primary,
  ArgsTable,
  Stories,
  PRIMARY_STORY,
} from '@storybook/addon-docs';

import { Button } from './Button';

export default {
  /* 👇 The title prop is optional.
  * See https://storybook.js.org/docs/react/configure/overview#configure-story-loading
  * to learn how to generate automatic titles
  */
  title: 'Button',
  component: Button,
  parameters: {
    docs: {
      page: () => (
        <>
          <Title />
          <Subtitle />
          <Description />
          <Primary />
          <ArgsTable story={PRIMARY_STORY} />
          <Stories />
        </>
      ),
    },
  },
};
```

But the use of each component is not described and the way components like <Primary/> actually work is kind of blurry to me.
Repository: stable-diffusion-webui
Issue: [Feature Request]:  colossalai integration
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Integrate ColossalAI improvements : https://github.com/hpcaitech/ColossalAI/tree/main/examples/images/diffusion


### Proposed workflow

User is able to toggle improvements by colossal AI

### Additional information

_No response_
Repository: pytorch
Issue: MPS test_numpy_ref_mps_nn_functional_group_norm_mps_float32 is flaky?
Labels: triaged,module: flaky-tests,module: mps

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/actions/runs/3446932166/jobs/5752655448

### Versions

master

cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: flutter
Issue: [pigeon] Reorganize test pigeons
Labels: team,package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

The Pigeon API definitions used for tests are defined in a bunch of files in the `pigeons/` directory. There are several problems with this:
- They grew haphapzardly:
  - It's not always clear what any given file is intended to test (e.g., the original file is just called "message.dart" rather than having a usage-based name, and there are ambiguous cases like "enum.dart" vs "enum_args.dart")
  - Some have multiple APIs, some only one.
  - It's not clear when to make a new file vs. editing an existing one.
- Each file is generated in its own `pigeon` invocation in the test script, and each invocation is *slow*. It takes quite a while, especially on Windows, to generate all of the output, because there are so many files, and each new file slows things down more.

We should consolidate this to a small number of files—very possibly that number being one—and clearly group things (with comments) within that file. E.g., Maybe we have one API that tests all permutations of arguments, or one that tests all permutations of enums (return value, direct arg, class field), even though they are in the same file. But we definitely don't need to have a lot of single-entry APIs like we currently have across the files.

Currently the native unit test files are mostly broken down matching the pigeons/ files; we would need to figure out how we want to groups those files instead. But we can certainly have multiple source files for the native unit tests even if we consolidate the API definition, if keeping file division is useful.

(This has been discussed in the past, but I didn't see an issue where we captured it. /cc @tarrinneal )
Repository: next.js
Issue: Multizones with i18n causes proxied path HMR to stop working (WebSocket connection to 'ws:<URL>/app/_next/webpack-hmr' failed: WebSocket is closed before the connection is established.)
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: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.16.0
      npm: 8.11.0
      Yarn: 1.22.19
      pnpm: 7.13.5
    Relevant packages:
      next: 13.0.3-canary.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### What browser are you using? (if relevant)

Chrome Version 107.0.5304.110 (Official Build) (arm64)

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

In the "with-zones" example, If you add any i18n configuration to the home app and navigate to /blog will case the repeating warning to be displayed:

```
WebSocket connection to 'ws://localhost:3000/blog/_next/webpack-hmr' failed: WebSocket is closed before the connection is established.
```
Also because of this HMR is not working when editing files in the blog Next.js app.

### Expected Behavior

The HMR client should probably reconnect to the proxied apps HMR server automatically, even if you have a i18n configuration?

### Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

just add an i18n configuration to the with-zones example home app next.config.js

### To Reproduce

Clone https://github.com/vercel/next.js/tree/canary/examples/with-zones, add any i18n configuration to the home app next.config.js and follow the instructions to start both Next.js apps in dev mode (next dev). Open http://localhost:3000 in a browser and navigate to blog. Wait on the WebSocket connection fail warning to display in the console.
Repository: yt-dlp
Issue: Add support for Adobe Pass Auth TV Provider Cox Communications
Labels: account-needed,site-enhancement

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a site-specific feature
- [X] I've verified that I'm running yt-dlp version **2022.11.11** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [ ] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

US

### Example URLs

https://abc.com/shows/greys-anatomy/episode-guide/season-19/06-thunderstruck

### Provide a description that is worded well enough to be understood

Add support for Adobe Pass Auth TV Provider Cox Communications

### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
[debug] Command-line config: ['https://abc.com/shows/greys-anatomy/episode-guide/season-19/06-thunderstruck', '--ap-mso', 'Cox', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', '-verbose']

Usage: yt-dlp.exe [OPTIONS] URL [URL...]

yt-dlp.exe: error: Unsupported TV Provider "Cox", use --ap-list-mso to get a list of supported TV Providers
```
Repository: node
Issue: Native zip support
Labels: zlib,feature request,never-stale

### What is the problem this feature will solve?

This issue is to test the water a little bit.

Node supports zlib natively, which takes care of the compression / decompression aspect of sharing files, but it doesn’t include any primitive allowing to manipulate file archives of any kind. It can be implemented in userland (and in a project of mine we’re doing this by compiling the [libzip](https://github.com/nih-at/libzip) to wasm), but it’s significantly slower (both in runtime, boot time, and size).

Being able to read file archives is especially useful when coupled with the ESM loaders, since it then becomes possible to implement loading modules straight from packaged vendors - a more performant alternative to bundled packages which doesn’t require to precompile the code and allows distributing it along with non-JS files.

### What is the feature you are proposing to solve the problem?

I’d like to investigate whether it’d make sense to implement a **basic** archive manipulation library in Node.js. This isn’t unheard of, multiple interpreters having similar capabilities, sometimes even supporting multiple formats:

- PHP - https://www.php.net/manual/en/zip.examples.php
- Python - https://docs.python.org/3/library/zipfile.html
- Python (tar) - https://docs.python.org/3/library/tarfile.html
- Perl - https://perldoc.perl.org/IO::Compress::Zip
- Perl (tar) - https://perldoc.perl.org/Archive::Tar
- Go - https://pkg.go.dev/archive/zip@go1.19.3
- Go (tar) - https://pkg.go.dev/archive/tar@go1.19.3
- Java - https://docs.oracle.com/javase/7/docs/api/java/util/zip/package-summary.html
- C# - https://learn.microsoft.com/en-us/dotnet/standard/io/how-to-compress-and-extract-files

The API of this **basic** archive library would be to define, but generally we can assume some simple requirements:

- Read an archive’s directory listing
- Stat files from within an archive
- Read a buffer from an archive
- Add a file to an archive

I’d be interested to explore an implementation myself.

### What alternatives have you considered?

_No response_

@nodejs/zlib
Repository: vscode
Issue: Change undo/redo to time based, AKA allow undo without erasing redo
Labels: feature-request,editor-core,undo-redo

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Imagine you are programming something.
After some time you aren't sure of something, so you check an earlier version of it.
After some Ctrl-Zs you accidentally press a key, and that's it all of your unsaved code is gone.

If we treat the undo button as a rewind button, we can prevent this!
A) ----> Original changes
B) <---- Undoing them
C) --->  New changes
becomes linearly:

A) ----> B) ----> C) --->

Currently, whenever a key is pressed (changes to a webview are made) a new entry is pushed into the 'undo stack' and the 'redo stack' is emptied.
Instead, we can add the 'redo stack' to the  'undo stack' to keep 'alternate futures' of the webview.
Specifically, we will want the following whenever the 'undo stack' is populated:
'undo stack' = 'undo stack' + inverted 'redo stack' + 'redo stack' + new 'undo stack' entry (change)

Further reading:
https://github.com/zaboople/klonk/blob/master/TheGURQ.md
Repository: storybook
Issue: [Bug]: certain glob patterns in stories dramatically slows down launch time
Labels: bug,performance issue,builder-webpack5,builder-vite

### Describe the bug

Before the webpack build even starts, the build gets stuck after logging "Using default webpack5 setup" for over a minute - doubling the time it takes to launch storybook.

Changing our `stories` config value from `../../../my-lib/react-[box|stack]/index.stories.tsx` or ``../../../my-lib/*/index.stories.tsx`` to `["../../../my-lib/react-box/index.stories.tsx", "../../../my-lib/react-stack/index.stories.tsx"]` causes the build to not pause after the "webpack5 setup" step at all.  Removing `storyStoreV7` also stops the delay from happening.

This is a very large monorepo with hundreds of libraries, but the issue happens even when there are only 2 libraries that match the pattern, like the example above. In this example, react-box and react-stack are not very complicated components/folders, but there are over 100 "siblings" in the `my-lib` folder.

Similar to [this comment](https://github.com/storybookjs/storybook/issues/19446#issuecomment-1276067149), I'm able to work around this issue by generating the full paths to each story using a glob library.

### To Reproduce

Unfortunately, I have only been able to reproduce this in a very large, private repository. I would be happy to do debugging on my end if anyone can point me in the right direction (I've tried adding logs at various places in the SB libraries, and haven't found the long-running task yet).


### System

```shell
Environment Info:

  System:
    OS: macOS 12.6.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v16.14.0/bin/yarn
    npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Firefox: 106.0.3
    Safari: 16.1
```


### Additional context

Possibly related to #19446 and maybe https://github.com/webpack/webpack/issues/13636
Repository: godot
Issue: Godot aborts with stack trace on editing scene file marked as tool with a timer that frees the node
Labels: bug,topic:editor,needs testing,crash

### Godot version

v3.4.4.stable.official (419e713a29f20bd3351a54d1e6c4c5af7ef4b253)

### System information

Linux PopOS

### Issue description
Opening a scene file (in attached project) causes the following hard quit of Godot:

```
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v3.4.4.stable.official (419e713a29f20bd3351a54d1e6c4c5af7ef4b253)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f6627442520] (??:0)
[2] /opt/godot/Godot() [0x2ae4157] (??:0)
[3] /opt/godot/Godot() [0x2b1cd5c] (??:0)
[4] /opt/godot/Godot() [0x1708a90] (??:0)
[5] /opt/godot/Godot() [0x170ce14] (??:0)
[6] /opt/godot/Godot() [0xb50a45] (??:0)
[7] /opt/godot/Godot() [0x2b77c39] (??:0)
[8] /opt/godot/Godot() [0x2ff86d8] (??:0)
[9] /opt/godot/Godot() [0x2b81bec] (??:0)
[10] /opt/godot/Godot() [0x9d8c5e] (??:0)
[11] /opt/godot/Godot() [0x9471ad] (??:0)
[12] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f6627429d90] (??:0)
[13] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f6627429e40] (??:0)
[14] /opt/godot/Godot() [0x95ae1e] (??:0)
-- END OF BACKTRACE --
```


The actual line at fault is this:
```
func _on_Timer_timeout() -> void:
queue_free()
```

My code is marked with tool.

If I remove tool or the queue_free() then it doesn't crash.
Repository: flutter
Issue: Use a more generic name for drones
Labels: team-infra,P3,triaged-infra

With the previous implementation of the sharding utility we required a drone for every repo, platform, environment combination. The new implementation remove the need for the repo combination and we need to remove non needed drones and update the needed ones with a more generic name.
Repository: create-react-app
Issue: How to exclude/override plugins included by babel-preset-react-app
Labels: needs triage

I want to use propTypes even in production mode (not recommended but my React app needs it). As you may know propTypes are removed by `babel-plugin-transform-react-remove-prop-types plugin`. this plugin is added by `babel-preset-react-app` in this file: `node_modules/babel-preset-react-app/create.js line 199`. In my React application i tried everything to exclude the plugin, but nothing works, any ideas?

```
react => 18.2.0

For overriding CRA config i use : 
react-app-rewired => 2.2.1
customize-cra => 1.0.0
```
Here is what i tried:

```js
// .babelrc

{
  "presets": [
    [
      "react-app", {
      "exclude": [
        "babel-plugin-transform-react-remove-prop-types",
        "transform-react-remove-prop-types",
        "react-remove-prop-types"
      ]
    }]
  ]
}

// And i tried this : 
{
  "overrides": [
    {
      "presets": [
        [
          "react-app", {
          "exclude": [
            "babel-plugin-transform-react-remove-prop-types",
            "transform-react-remove-prop-types",
            "react-remove-prop-types"
          ]
        }]
      ]
    }
  ]
}

// and also tried to change plugin params
{
  "presets": ["react-app"],
  "plugins": [
    [
      "babel-plugin-transform-react-remove-prop-types",
      {
        "removeImport": false,
        "ignoreFilenames": [".*"]
      }
    ]
  ]
}
```
```js
// config-overrides.js

const { override, removeInternalBabelPlugin, useBabelRc} = require("customize-cra");

module.exports = override(
    useBabelRc(),
    removeInternalBabelPlugin('babel-plugin-transform-react-remove-prop-types'),
    removeInternalBabelPlugin('transform-react-remove-prop-types'),
);
```
Repository: vscode
Issue: Issue with "reopen editor with" -> Jupyter notebook
Labels: bug,notebook

@Tyriar pointed out these steps

- ctrl+n
- "Reopen Editor With" -> "Jupyter Notebook"
- Start RBL in a cell
- A plain text editor opens, instead of pausing in the notebook cell

In this case, the notebook cell has a URI like 

`vscode-notebook-cell:Untitled-1#W0sdW50aXRsZWQ%3D`

If I create a notebook directly, eg via "Create New File", the cell URI looks like


`vscode-notebook-cell:Untitled-1.ipynb?jupyter-notebook#W0sdW50aXRsZWQ%3D`

Another difference is the tab icons 

<img width="296" alt="image" src="https://user-images.githubusercontent.com/323878/201447168-3e397941-0e57-45c2-a931-932b1b6ed75f.png">

Do you know where the problem lies here @lramos15? I get that we created a plain file first with a default URI and don't change the URI when opening it in a notebook editor. I think the problem is just that when the debugger tries to open the document that was paused with that cell URI, it isn't opened in the notebook - does the missing query string `?jupyter-notebook` cause that?
Repository: tauri
Issue: [bug] window.print() empty preview with pdf.js
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

printview error
<img width="1320" alt="image" src="https://user-images.githubusercontent.com/40415260/201448169-40116944-ee3e-4d6d-ae49-398cbe2f5060.png">


### Reproduction

this is pdf viewer,
https://hub.nuaa.cf/mozilla/pdf.js

this is demo
https://mozilla.github.io/pdf.js/web/viewer.html

print views error

### Expected behavior

printviewer
<img width="1232" alt="image" src="https://user-images.githubusercontent.com/40415260/201448085-d3e4bcea-9f52-4fdc-adaf-d3f6f7d02092.png">


### Platform and versions

  › OS: Mac OS 12.5.1 X64
  › Node.js: 16.14.0
  › npm: 8.3.1
  › pnpm: 6.32.3
  › yarn: 1.22.17
  › rustup: 1.25.1
  › rustc: 1.65.0
  › cargo: 1.65.0
  › Rust toolchain: stable-aarch64-apple-darwin 


### Stack trace

_No response_

### Additional context

_No response_
Repository: create-react-app
Issue: Remove `self` from confusing-browser-globals
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Yes.

When writing code for a service worker, the global variable `self` is used the same way `window` is used in web pages; however, eslint will report errors when writing worker code since `self` is banned via https://github.com/facebook/create-react-app/blob/main/packages/confusing-browser-globals/index.js.

### Describe the solution you'd like

I believe we should remove `self` from the confusing-browser-globals list.

### Describe alternatives you've considered

The workbox CRA template simply places:
```
/* eslint-disable no-restricted-globals */
```
at the top of the `service-worker.ts` file. This has the downside of removing all restricted global protections from your service worker code. Additionally, it is impractical for larger service worker codebases with many source files.

One can also use `this` and `globalThis` as an alternative to using `self`. However, I still believe that `self` should not be included in this list for the following reason:
- `self` in a worker is the equivalent of `window` in a web page
- `window` is not included in the list, so neither should `self`

### Additional context