sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]:  text2img error 
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

when evaluating text2img in more than 1000x1000 type errors
rtx 3070 ti. 

while my friend renders quietly at 1500x1500 on rtx 3060


### Steps to reproduce the problem

1. Go to .... 
2. Press ....
3. ...


### What should have happened?

-

### Commit where the problem happens

-

### What platforms do you use to access the UI ?

_No response_

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
-
```


### List of extensions

-

### Console logs

```Shell
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 3.75 GiB (GPU 0; 8.00 GiB total capacity; 5.89 GiB already allocated; 0 bytes free; 6.00 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
```


### Additional information

_No response_
Repository: pytorch
Issue: Improve checkpoint thread-safety
Labels: module: autograd,triaged,module: multithreading,needs design

### 🐛 Describe the bug

Checkpoint's uses a dictionary to track whether a given checkpoint has already been recomputed, and this dictionary can be shared between multiple threads. As a result we might run into something like the following (note that the GIL doesn't protect you here!):

Possible race condition:
- perform forward on two devices to force backward to be performed on two threads, since they spawned from the same backward, the two threads share the same graph_task_id
- both threads simultaneously try to execute two separate nodes created under the same checkpoint
- the test `if not frame.is_recomputed[gid]:` passes for both threads
- both threads do recompute for the same checkpoint! (something bad happens, at the very least, we recompute checkpoint unnecessarily)

See https://github.com/pytorch/pytorch/pull/90105#discussion_r1135722492 



### Versions

main

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @Lezcano @Varal7
Repository: pytorch
Issue: Follow-ups to do after adding nested checkpoint
Labels: module: autograd,triaged,actionable

Tracking some follow ups to do after https://github.com/pytorch/pytorch/pull/90105 lands:
- [x] update docs to reflect ability to do backward within checkpointed region https://github.com/pytorch/pytorch/pull/96862
- [x] enable early-stopping by default, add an API to disable https://github.com/pytorch/pytorch/pull/96866
  - [x] update docs to mention the early stop feature https://github.com/pytorch/pytorch/pull/96866
- [ ] update docs/tutorial to feature nested use cases
- [ ] https://github.com/pytorch/pytorch/issues/96764

Missing anything?

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @Lezcano @Varal7
Repository: storybook
Issue: [Feature Request]: allow configure in raw source code in Code panel
Labels: feature request,web-components,block: source

### Allow configure the way display raw source code in Code panel 

I am currently working on a project using storybook which add Code panel and Controls panel. This is what I have in mdx file now:

```
export const Template = ({dark, width, height, theme}) => {
  return html`
    <my-button
      @click=${action('button clicked')}
      width="${width}"
      height="${height}"
      theme="${theme}"
      ?dark=${dark}>
    </my-button>
  `;
};
```

This is Code panel when the user set `dark` to true in Control panel: 

`<my-button  width="200" height="40" theme="dark"  dark="">
</my-button>`

**dark** is a boolean user can set in Control panel. 

We're supporting displaying raw source code in Code panel for each component. The value of the attribute for the html element will change based on different configuration of the component. But we found some
limitations of overriding the source code in Code panel.

What we have now:
- Dark mode on : `<my-button dark=""></my-button>`
- Dark mode off : `<my-button ></my-button>`

We want to update all of our components to the following:

- Dark mode on : `<my-button dark></my-button>`
- Dark mode off : `<my-button ></my-button>`

Setting `dark` without a value works as expected, but removing `=""` is not achievable. We can define what type of inputs to display, but we don't have control over how this particular playground tab displays them, and there doesn't seem to be a type option for **no-value** attributes. No matter what we passed as a value to the attribute, it will be parsed to `=""`. 



### Describe the solution you'd like

We need to update all of our components to the following:

- Dark mode on : `<my-button dark></my-button>`
- Dark mode off : `<my-button ></my-button>`

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: TypeScript
Issue: Parameters created from tuple are treated as mutable instead of immutable, unless written as "...args"
Labels: Bug,Rescheduled

# Bug Report


### 🔎 Search Terms


const array tuple parameter spread

### 🕗 Version & Regression Information

- This is the behavior in every version I tried,.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground Link](https://www.typescriptlang.org/play?ts=4.9.5#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXxCjAAsAeAFQIA8MRVgBneAJUODwgE8BBGGKTqSipOAPlEAKMFAYgGALhZsOPPgIqiAlIomJUOgHRHYAcwXxym+AF5R8YZyu34ANxxZgAbgBQ3sHgYMeGlZJmt4AG1veBjIgEYAGngAcjjkgF0E6NiIgCYk5NyMrPT7Jn9UQJ8-AKDCEhAYGwIiYikZOU0fAHpu2NiAPQB+X174AFE+HBh5bzHeE2QAWzognER4DE4ABwRkiShFOPgAH3h8+AAjRQAiOJvT+Bvcm6c7Nw9k+CwmVBwgmQMLAmVBQS4QBAYHDwbawKArWhNdabHZ7CRGAymcxwKDsVBceJJO43UpnHF4gl5IkvdJvewiZIGOZ9CyopjI2H8BGNJjJKBfYTAFJYgVwb7oHBLWHYcEgJljWLkVEpckqQlPe6k+Cq-GcSIXZ4kr4-eB-AEMIEgsEQzbQra7FIRQ7wY5nC7XDUPM6G9KM5n9GLkYiQ5XJHWUxKe33fXnhzgC+jBYRmq4IQHA1AgIVQzbB+BLZAYa0hh3JJ1HR7u273R4+xkSXIAZgALABWTSjPoAdWIetgkLzpmWqyYsjoZXzheLI289WDMAkBySlzpAG9sjEoD0WcMN1dtzFdwBfLq+WetRqLjFYtd7hX9Xf9CqBSJQZelcJYnz9Lf++CP2JLgPf8RhPHwgA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
declare function each<T extends ReadonlyArray<any>>(cases: ReadonlyArray<T>): (fn: (...args: T) => any) => void;

const cases = [
    [1, '1'],
    [2, '2'],
] as const;

const eacher = each(cases);

// Error.
eacher((a, b) => {
});

// No error?
eacher((...args) => {
    const [a, b] = args;
});

```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->

```
Argument of type '(a: 1 | 2, b: "1" | "2") => void' is not assignable to parameter of type '(...args: readonly [1, "1"] | readonly [2, "2"]) => any'.
  Types of parameters 'a' and 'args' are incompatible.
    Type 'readonly [1, "1"] | readonly [2, "2"]' is not assignable to type '[a: 1 | 2, b: "1" | "2"]'.
      The type 'readonly [1, "1"]' is 'readonly' and cannot be assigned to the mutable type '[a: 1 | 2, b: "1" | "2"]'.(2345)
```

Obviously they're not assignable, but why did we come up with `[a: 1 | 2, b: "1" | "2"]` and not `readonly [a: 1 | 2, b: "1" | "2"]`?

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

No error, as though it had been expanded separately.

See also: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/64739
Repository: stable-diffusion-webui
Issue: [Feature Request]: Add [filewords] option to prompts.
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 ?

There is currently no way to take the individual elements of a picture into account during img2img or batch processing, since it does not use caption files.

Feature request is to add the following options to img2img and batch processing:
 - Add the option to use [filewords] in prompts, so that the placement of captioned files can be placed anywhere and with any weight.
 - And/or automatically interrogate the image before processing, automatically adding it to the existing prompt.

### Proposed workflow

1. Go to batch processing. Type a prompt as such,
" a person sitting at a table, [filewords] "
2. When batch process runs, it adds the filewords of each image's caption file to the prompt of that image's processing.

Auto interrogate option would be:
1. Enable Deepboru or Clip auto-interrogate checkbox.
2. Type positive prompt as normal and hit generate.
3. image is interrogated before the generation begins, and the new prompt is added to the end of the regular one.

### Additional information

I couldn't find this anywhere, but if it already exists, let me know.
Repository: godot
Issue: [3.5.1 Stable Mono] Json.Print() reads 2D array as 1D and does not work for boolean array
Labels: topic:dotnet

### Godot version

3.5.1.stable.mono

### System information

Windows 10

### Issue description

`Json.Print();` has some strange behaviours, the two that I noticed so far:
- It does not converts 2D or any layered arrays correctly, but will treat them as 1D array. For example `[[1,2],[3,4]]` will be treated as something like `[-2110987704, -2110987712]`, which I can only assume are the memory addresses.
- It does not work for boolean array (any dimension) specifically, even though it can convert boolean just fine


### Steps to reproduce

Run the following script in Mono
```C#
//2D Array behaviour
GD.Print(JSON.Print( new int[][]{ new int[]{1,2}, new int[]{3,4} } )); //[-5446920,568]
GD.Print(JSON.Print( new string[][]{ new string[]{"ab","cd"}, new string[]{"ef"} } )); //["",""]

//Boolean Array beahviour
GD.Print(JSON.Print(true)); //true
GD.Print(JSON.Print(new bool[]{true, false})); //Errors with the following stacktrace
//E 0:00:00.862   mono_object_to_variant_impl: Attempted to convert a managed array of unmarshallable element type to Variant.
//   <C++ Error>   Method failed. Returning: Variant()
//   <C++ Source>  modules/mono/mono_gd/gd_mono_marshal.cpp:1032 @ mono_object_to_variant_impl()
//   <Stack Trace> :0 @ System.String Godot.NativeCalls.godot_icall_3_1207(IntPtr , IntPtr , System.Object , System.String , Boolean )()
//                 JSON.cs:77 @ System.String Godot.JSON.Print(System.Object , System.String , Boolean )()
//                 TestScene.cs:19 @ void TestScene._Ready()()
```

### Minimal reproduction project

N/A
Repository: godot
Issue: Callables do not work with Singletons.
Labels: bug,topic:core,topic:gdscript,needs testing

### Godot version

4.0

### System information

Windows 10

### Issue description

You cannot use `Callable` to call a function within a singleton, where previously it was possible to do in 3.5 using `funcref()`.

Unsure if this change is intentional or not but it is mildly annoying.
I am soon going to test if it can be worked around by creating a variable which is equal to `self` within the singleton to use as the first parameter of `Callable`. 

### Steps to reproduce


```
Callable(Global_Singleton,"func_name")
```
gives error:
```
No constructor of "Callable" matches the signature "Callable(, String)".
```

### Minimal reproduction project

N/A
Repository: kubernetes
Issue: Pod status updates take longer to propagate to the API than necessary
Labels: priority/backlog,sig/scalability,sig/node,kind/feature,triage/accepted

### What happened?

#107897 originally identified a number of inefficiencies in how pod status is reported back to the API:

1. Pods are queued in a channel and then processed one by one - this causes HoL blocking and writes every observed status change, but pod status is level driven (split into #116615 for inclusion into #115331)
2. Status is a GET then PATCH, but we now have server side apply and using it would reduce 2 RT to 1 RT and reduce QPS
3. We treat all status updates the same, when in reality certain transitions should be prioritized (unready -> ready, Running -> Succeeded|Failed)
4. Status is single threaded, and we could easily try multiple
5. It's hard to know when our status cache has been brought up to date (so that we can bypass a SSA attempt), we could use ResourceVersion tracking for that (apimachinery proposed allowing it to be parsed)

In general these contribute to #113606 and should be improved.

/sig node
/sig scalability

### What did you expect to happen?

Faster

### How can we reproduce it (as minimally and precisely as possible)?

See kubelet logs.  Several e2e tests stress this flow, but we need a test that shows the improvements.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</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: vscode
Issue: System Certificates: Support trusted intermediate CAs
Labels: feature-request,proxy

Type: <b>Bug</b>

1. Log into a company account in Windows
2. Click Account icon, choose "Sign in to sync settings"
3. In the pop-up window, choose the account you already logged in
4. It says "You are signed in now and can close this page."
5. Nothing changed, you are still not logged in.

VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<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)|undefined|
|Memory (System)|31.75GB (17.62GB free)|
|Process Argv|--crash-reporter-id ccb873f8-d593-4eb5-bc2f-906204f79c83|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (8)</summary>

Extension|Author (truncated)|Version
---|---|---
monokai-charcoal-high-contrast|74t|3.4.0
jsonviewer|cci|1.3.2
format-json|Cle|1.0.3
terraform|has|2.25.4
prettify-json|moh|0.0.3
vscode-docker|ms-|1.24.0
remote-containers|ms-|0.282.0
color-highlight|nau|2.5.0

(7 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
f6dab269:30613381
vscrp:30673768
pythonsymbol12:30671437
6233i204:30672705
vsccsb:30677849
funwalk2cf:30682975
pythonms35cf:30686773

```

</details>

<!-- generated by issue reporter -->
Repository: storybook
Issue: [Bug]: react-vite, Failed to fetch dynamically imported module
Labels: bug,help wanted,react,has workaround,builder-vite,sev:S3

### Describe the bug

If you:

- are using @storybook/react-vite@7.0.0-rc.3
- have your .storybook folder in your src folder
- have `public` in your storybook staticDirs
- import an asset from src with the same path as an existing asset in public

Then storybook will error with:

> Failed to fetch dynamically imported module: http://localhost:6006/stories/Button.stories.ts

If you look at the network activity, the asset is returned with `Content-Type: image/png`, but `Content-Type: application/javascript` is expected and an error is thrown:

> Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "image/png". Strict MIME type checking is enforced for module scripts per HTML spec


### To Reproduce

https://github.com/penx/storybook-issue-2023-03-14

### System

```shell
Environment Info:

  System:
    OS: macOS 13.2.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 16.19.1 - ~/.nvm/versions/node/v16.19.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.19.1/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.1/bin/npm
  Browsers:
    Edge: 101.0.1210.39
    Firefox: 109.0
  npmPackages:
    @storybook/addon-essentials: ^7.0.0-rc.3 => 7.0.0-rc.3 
    @storybook/addon-interactions: ^7.0.0-rc.3 => 7.0.0-rc.3 
    @storybook/addon-links: ^7.0.0-rc.3 => 7.0.0-rc.3 
    @storybook/blocks: ^7.0.0-rc.3 => 7.0.0-rc.3 
    @storybook/react: ^7.0.0-rc.3 => 7.0.0-rc.3 
    @storybook/react-vite: ^7.0.0-rc.3 => 7.0.0-rc.3 
    @storybook/testing-library: ^0.0.14-next.1 => 0.0.14-next.1
```


### Additional context

This took me far too long to debug 😂

We have our storybook config inside src so that we can import files from src without typescript + ts lint complaining that our storybook files aren't in our project.

We have `public` in our storybook staticDirs as we have fonts and other assets that are loaded e.g. by .storybook/preview-head.html. There are some places where we have the assets in the same location in our src folder (public/themes/some-asset and src/themes/some-asset).

Now that I can see the issue, I should be able to find a workaround, but the errors were cryptic and I expect others could be faced with the same issue.

Note this error doesn't occur if the storybook config is not in the src or when running the vite app directly using `vite dev`
Repository: next.js
Issue: Unable to test `async` components with Jest
Labels: bug,TypeScript

### 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 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000
Binaries:
  Node: 18.9.0
  npm: 8.19.1
  Yarn: N/A
  pnpm: N/A
Relevant packages:
  next: 13.2.5-canary.3
  eslint-config-next: 13.2.4
  react: 18.2.0
  react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Jest (next/jest), TypeScript

### Link to the code that reproduces this issue

https://github.com/felipemullen/async-jest-bug

### To Reproduce

```bash
git clone https://github.com/felipemullen/async-jest-bug
npm i
npm test
```

### Describe the Bug

in NextJs 13+ using the experimental App folder, async server components can be written as [described by the documentation](https://beta.nextjs.org/docs/data-fetching/fetching#asyncawait-in-server-components) and the [async RFC](https://github.com/acdlite/rfcs/blob/first-class-promises/text/0000-first-class-support-for-promises.md)

These components cannot be tested with `Jest` and `@testing-library/react`. The component does not render, but instead spits an infinite loop to the console with the following error:

> Error: Uncaught [Error: Objects are not valid as a React child (found: [object Promise]). If you meant to render a collection of children, use an array instead.]

### Expected Behavior

Jest should be able to run without error when rendering an `async` component when running a simple test such as

```typescript
it('should render without crashing', async () => {
    // @ts-expect-error Async Component
    const { container } = await waitFor(() => render(<Page />));
    expect(container).toBeTruthy();
});
```

### Which browser are you using? (if relevant)

None

### How are you deploying your application? (if relevant)

None
Repository: flutter
Issue: Resolve Text Input Code Divergence
Labels: a: text input,platform-ios,framework,f: material design,f: cupertino,team-design,triaged-design

I was looking to use `CupertinoTextField` on iOS and `TextField` on Android for my app. The API differences between the two widgets for seemingly similar concepts feel rather unnecessary. Here are some examples:

- To add a piece of hint text, I need to supply that through the `decoration` property on `TextField` but the `placeholder` property on `CupertinoTextField`. 
- The `decoration` property on `TextField` takes an `InputDecoration`, but the same property on `CupertinoTextField` takes a `BoxDecoration`.
- To add a prefix icon, I can use the `prefixIcon` property on `InputDecoration`, which I then pass to the `decoration` property on `TextField`. However, I need to use the `prefix` property on `CupertinoTextField` to achieve a similar result. 

Such differences make it difficult to 1) reason about how to use `CupertinoTextField` based on my knowledge about `TextField`, and 2) minimize platform-specific code when showing one of the two widgets based on the OS. 

It could be helpful if a base text field is provided and design language is applied through theming or decoration.
Repository: next.js
Issue: `build` method no longer accepts config object as argument
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: linux
      Arch: x64
      Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
    Binaries:
      Node: 16.13.0
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://codesandbox.io/s/late-thunder-sdff1t?file=/build.js

### To Reproduce

yarn custom:build

### Describe the Bug

I recently noticed a break in a library I'm developing.. debugging today, I noticed that for some reason the build function was no longer accepting the configuration object.

Looking at the change history I found this specific commit https://github.com/vercel/next.js/commit/85ec9c5d94b57b19c4dd058313a246d1ae998774, but I didn't see a plausible reason for it.

For developers, like me, who depend in some way on the nextjs api (build, startServer, etc), this change complicates things.

Could we reverse this?

### Expected Behavior

Passing a custom configuration object to the build.

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

_No response_

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

_No response_