sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Network error when starting dev server leads to confusing "circular structure" error output
Labels: bug,sev:S2

### Describe the bug

It's possible for Storybook to encounter a network error when starting its dev server, and when it tries to stringify the error, it encounters a circular object, which then leads to _another_ error. The error output becomes concerned only with this second error, and the original issue is lost entirely.

Here's the full error output:

```
@storybook/core v8.3.3

info => Starting manager..
TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    --- property 'issuerCertificate' closes the circle
    at JSON.stringify (<anonymous>)
    at renderHTML (file:///.../common/temp/node_modules/.pnpm/@storybook+core@8.3.3/node_modules/@storybook/core/dist/builder-manager/index.js:2836:41)
    at async starterGeneratorFn (file:///.../common/temp/node_modules/.pnpm/@storybook+core@8.3.3/node_modules/@storybook/core/dist/builder-manager/index.js:3054:11)
    at async Module.start (file:///.../common/temp/node_modules/.pnpm/@storybook+core@8.3.3/node_modules/@storybook/core/dist/builder-manager/index.js:3146:9)
    at async storybookDevServer (...\common\temp\node_modules\.pnpm\@storybook+core@8.3.3\node_modules\@storybook\core\dist\core-server\index.cjs:47306:11)
    at async buildOrThrow (...\common\temp\node_modules\.pnpm\@storybook+core@8.3.3\node_modules\@storybook\core\dist\core-server\index.cjs:46581:12)
    at async buildDevStandalone (...\common\temp\node_modules\.pnpm\@storybook+core@8.3.3\node_modules\@storybook\core\dist\core-server\index.cjs:48518:78)
    at async withTelemetry (...\common\temp\node_modules\.pnpm\@storybook+core@8.3.3\node_modules\@storybook\core\dist\core-server\index.cjs:47080:12)
    at async dev (...\common\temp\node_modules\.pnpm\@storybook+core@8.3.3\node_modules\@storybook\core\dist\cli\bin\index.cjs:2877:3)
    at async r.<anonymous> (...\common\temp\node_modules\.pnpm\@storybook+core@8.3.3\node_modules\@storybook\core\dist\cli\bin\index.cjs:2929:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.
```

### Reproduction link

N/A

### Reproduction steps

We're not exactly sure what caused this, but it seemed to be a transient network issue, since the problem went away on its own after 5-10 minutes.

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 20.11.1 - C:\Program Files\Node.js\node.EXE
    npm: 10.8.2 - C:\Program Files\Node.js\npm.CMD
    pnpm: 9.7.1 - C:\Program Files\Node.js\pnpm.CMD <----- active
  Browsers:
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @storybook/react: link:apps/geiger/node_modules/@storybook/react => 8.3.3
    storybook: link:apps/geiger/node_modules/storybook => 8.3.3
```


### Additional context

_No response_
Repository: rust
Issue: tests/debuginfo/macro-stepping.rs remains broken with SingleUseConsts
Labels: A-LLVM,A-testsuite,A-debuginfo,T-compiler,A-MIR,C-bug,WG-llvm,WG-debugging

This is the part of @saethlin's #128945 that survived #130329. Reordering the IR in the front end in the SingleUseConsts pass breaks the stepping order. This could be mitigated to some extent (but not completely, unclear if it would be sufficient for this test to pass) with better support in LLVM for front ends to express which IR instructions should be considered for breakpoints.

@rustbot label +A-debuginfo +A-testsuite +A-llvm +A-mir +C-bug +T-compiler +WG-debugging +WG-llvm
Repository: ui
Issue: [bug]: could not determine executable to run for package shadcn-ui
Labels: bug

### Describe the bug

Subject: Issue adding any component with ```shadcn-ui```

Hi team,

I'm encountering an issue while trying to add the card component using ```shadcn-ui```. I've attached screenshots for reference.

Steps to reproduce:

I run the following command: ```bunx --bun shadcn-ui@latest add card``` (OR) ```bun x shadcn-ui@latest add card```

**Expected behavior:**
The card component should be added to my project using ```shadcn-ui.```

![image](https://github.com/user-attachments/assets/9ccd303c-7972-4791-b962-ed345ce3b3f4)
![image](https://github.com/user-attachments/assets/309d9d2a-60a5-4c78-bf8c-44d1e325b34d)


### Affected component/components

All the components

### How to reproduce


**Actual behavior:**
I receive the following error message: "could not determine executable to run for package shadcn-ui"

Additional information:

I've attempted to add the component using both ```npm``` and ```bun```, with the same error occurring.
Operating System: Windows 11
Node.js version:  ```v18.18.1```
Bun version: ```v1.1.29```
npm version: ```v10.8.3```


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows 11
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: ollama
Issue: Way to stop all running models
Labels: feature request

`ollama stop all` or `ollama stop *` etc

would be handy
Repository: vscode
Issue: Consider to convert `src/vs/workbench/contrib/webview/browser/pre/service-worker.js` to TypeScript
Labels: debt,webview

Given we now run with ESM, there is no real reason anymore to have JS files in our sources.

https://github.com/microsoft/vscode/blob/9e23739d0b9f3381d99be9bde649709d4329daa5/src/vs/workbench/contrib/webview/browser/pre/service-worker.js#L1-L8
Repository: godot
Issue: print() Shows inaccurate data after ~15-ish seconds
Labels: topic:editor,needs testing

### Tested versions

- Reproducible in: Godot 4.3 Stable (Only one I tested).

### System information

Godot v4.3.stable - Windows 10.0.22631 (Windows 11, but it says 10 on Godot for some reason?) - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 Laptop GPU (NVIDIA; 32.0.15.6081) - 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 Threads)

### Issue description


https://github.com/user-attachments/assets/fd593951-a2f8-44f2-93dc-9861543c2c4a

Essentially, for the first 15 seconds i play the game, using print() to print the player's state, etc. works fine.

After 15 seconds, it just breaks and prints out incorrect values. The game itself continues to print correct values. No clue what the reason behind this might be, nor what causes it.

I don't think that this is a coding bug and rather an engine bug because the game itself works just fine, and also gives accurate data, but the editor's print() is very inaccurate.

### Steps to reproduce

- Run the project on the 'night' scene
- Wait 15 seconds
- Labels will work fine but the print() statements will not.

### Minimal reproduction project (MRP)

project is over 700mb large, can't attach it. I don't know how to reproduce it outside of this project.
Repository: svelte
Issue: Assigning to rvalue `svelte(js_parse_error)`
Labels: bug,blocked by upstream

### Describe the bug

With this code:
```ts
foo! += 1;
```
(which is [valid typescript](https://www.typescriptlang.org/play/?#code/DYUwLgBAZg9jBcEB2BXAtgIxAJwgH2RWGAgF4IAGAbgCgbYYBCCAanIEYqg))

Svelte throws `Assigning to rvalue svelte(js_parse_error)`


### Reproduction

[REPL](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAAyWMzQrCMBAGX2X9rhbUa_oDPofrodatBNJNSDaC1L67FI8zA7Ni9kEK3G2FjovA4ZoSGtgn7VDeEkzQoMSap910Zco-GYVRXz3DCmNgZQtiNMfoSOvykExf0hoC9XRuWWlPBzr2dGlZu9P_MbCiwRKffvbyhLNcZbtvP5myBrmUAAAA)

### Logs

_No response_

### System Info

```shell
svelte@5.0.0-next.259
```


### Severity

annoyance
Repository: ui
Issue: [feat]: Support for Vinxi applications
Labels: area: request

### Feature description

I would like Shadcn CLI to support Vinxi applications which under the hood uses ViteJS.

Currently on a Vinxi setup, shadcn's CLI complains that the framework is not supported, I'm assuming it does that because in Vinxi codebase, the vite.config.ts is usually named app.config.ts.

I was able to solve this by renaming app.config.ts -> vite.config.ts but I would like the CLI to understand that app.config.ts is a ViteJS app too.

### Affected component/components

_No response_

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: vscode
Issue: [Bug] OS-Level Launch Configuration Not Behaving As Expected
Labels: bug,debug

<!-- ⚠️⚠️ 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. -->

<!-- 🪓 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. -->

The OS Level Presentation settings do not seem to be working as expected.

In below screenshot, I expected the launch config within the dev container (Linux OS) to be hidden but it is still visible:

![image](https://github.com/user-attachments/assets/39897d0f-0fbf-425c-8772-26667462096c)

Steps to Reproduce:

1. Setup a project for [`Dev Containers`](https://containers.dev)
1. Create 2 launch configs, one for host and one for within dev container
1. Use `{"windows/osx/linux": {"presentation": {"hidden": true/false}}}` property combinations such that only one launch config is visible in either environment (host / dev container)

_____

Version: 1.93.1 (user setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Repository: flutter
Issue: Eliminate dependency on DeviceLab bot/account for Apple development signing certificate renewals
Labels: team-infra,P2,triaged-infra

The certificate renewal process is described in [How to renew the DeviceLab development certificate](https://g3doc.corp.google.com/company/teams/flutter/infrastructure/devicelab/apple_cert_renewal.md) (Google-internal). In the _Create the new signing certificate_ section, we rely on a DeviceLab bot to perform the renewal, this and the related Apple Developer account are single points of failure.

* [ ] Allow renewals to be performed using any Apple Developer account that is authorised to create a developer signing certificate.
* [ ] Allow the certificate creation process to be performed from any authorised user's machine.
Repository: material-ui
Issue: [material-ui][Autocomplete] onInputChange called with undefined event contrary to type definition
Labels: typescript,package: material-ui,component: autocomplete

### Steps to reproduce

Link to live example: (required) https://stackblitz.com/edit/react-ouzbqw?file=Demo.tsx

Steps:
1. Set the onInputChange prop
2. Check what is passed in for the event param

### Current behavior

Hello 👋 

I'm noticing that the `onInputChange` is [typed as](https://github.com/mui/material-ui/blob/7fd82d58b79cfc90cc0d8c904b7cd753f8020e32/packages/mui-base/src/useAutocomplete/useAutocomplete.d.ts#L262-L266):

```
onInputChange?: (
    event: React.SyntheticEvent,
    value: string,
    reason: AutocompleteInputChangeReason,
) => void;
```

with a non-null `event` param, but `null` seems to be coming through for the param on mount. [See demo](https://stackblitz.com/edit/react-ouzbqw?file=Demo.tsx):

![onInputChange-null-event](https://github.com/user-attachments/assets/1e83d6a1-094d-4d0b-8db2-88c965d15804)


### Expected behavior

I'm not sure if `onInputChange` is supposed to be called on mount or not, but if it is and it's expected that `null` is an option for `event`, would it be possible to update the typing of `onInputChange` to reflect that?

Thanks!

### Context

We are trying to use strict null safety



### Your environment

See https://stackblitz.com/edit/react-ouzbqw?file=Demo.tsx - also reproduce-able in [this docs demo](https://mui.com/material-ui/react-autocomplete/#controlled-states)

**Search keywords**: onInputChange undefined event
Repository: vscode
Issue: With `editor.experimentalEditContextEnabled`, switching to another application during composition leads to a weird state
Labels: bug,upstream-issue-linked,editor-edit-context

Version: 1.94.0-insider
Commit: c43f508b732d24b0c4732de9db2b38b4c5b88b8a
Date: 2024-09-26T05:04:07.935Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 22.6.0

Steps to Reproduce:

1. Set `"editor.experimentalEditContextEnabled": true`
4. Enable Google IME for Japanese.
5. Type `sennsei`
6. Type `Space`
7. Switching to another application with mouse click.
8. Back to VS Code
9. Type `Space`. 
10. We get an inexpected output. 

https://github.com/user-attachments/assets/ac535f45-c851-49df-8735-04aa6e793454
Repository: go
Issue: net/http: new protocol registration mechanism
Labels: NeedsInvestigation

The following is not quite a proposal. It is a declaration of an intent to commit shenanigans, and an apology (in the sense of "a reasoned argument or justification of something") for them.

The net/http package allows an external package (practically: golang.org/x/net/http2) to register an HTTP/2 server and client implementation with it. (This is Server.TLSNextProto and Transport.TLSNextProto, plus Transport.RegisterProtocol.)

The current registration mechanism is cumbersome and can't easily be extended to support some features we want to add to the package. For example, we want to add support for unencrypted HTTP/2 (#67816), but the current extension mechanism assumes all HTTP/2 connections are a *tls.Conn. We have no way to pass an unencrypted net.Conn from net/http to the HTTP/2 implementation.

We have a plan to move x/net/http2 into std (#67810), but this involves a complex sequence of steps in which adding unencrypted HTTP/2 support is supposed to occur before the package move.

Therefore, it would be very convenient in the short term to have a better connection between net/http and golang.org/x/net/http2.

Ideally, this connection would be extensible if/when we discover additional ways the two packages need to communicate. It should also add little to no exported API surface to net/http, since it will have few-to-no users.

I propose, therefore, to add the following two unexported functions to net/http, using //go:linkname to make them visible to x/net/http2 (and only x/net/http2):

```go
//go:linkname serverRegisterProtocolImplementation golang.org/x/net/http2.nethttp_serverRegisterProtocolImplementation
func serverRegisterProtocolImplementation(s *Server, proto string, impl any) error

//go:linkname transportRegisterProtocolImplementation golang.org/x/net/http2.nethttp_transportRegisterProtocolImplementation
func transportRegisterProtocolImplementation(t *Transport, proto string, impl any) error
```

This is implemented in https://go.dev/cl/616097 (net/http) and https://go.dev/cl/616118 (x/net/http2).

The interface passed in the impl parameters is fiddly, low-level, contains no user-serviceable parts, and is subject to change to in the future. (We pass it as an "any" to make it easier to evolve if necessary.) See the above CLs for the details.

It is likely that we will want to expose a user-visible protocol registration mechanism in the future to support HTTP/3, since there exists at least one existing third-party HTTP/3 implementation. We could do this by converting the above unexported functions to exported methods and defining an appropriate interface for HTTP/3 server/client implementations:

```go
func (*Server) RegisterProtocolImplementation(proto string, impl any)
func (*Transport) RegisterProtocolImplementation(proto string, impl any)
```

That's a separate proposal, though.
Repository: flutter
Issue: Bot `mac-731-h526` is failing for various reasons
Labels: team-infra,P1,triaged-infra

This bot is failing to checkout `flutter/flutter` across multiple tests

`Mac_arm64 build_tests_2_4 `
https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64%20build_tests_2_4/15092/infra
https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64%20build_tests_2_4/15076/infra
https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64%20build_tests_2_4/15074/infra

`Mac_arm64 framework_tests_misc`
https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64%20framework_tests_misc/14302/overview

etc

Failure [log](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8735691188089322913/+/u/Checkout_flutter_flutter/git_fetch__2_/stdout) is:
```
fatal: unable to access 'https://github.com/flutter/flutter/': SSL: certificate verification failed (result: 5)
```

Noticed on https://github.com/flutter/flutter/pull/155794
Repository: rust
Issue: Better type inference with `impl_trait_in_assoc_type` (ITIAT)
Labels: requires-nightly,D-confusing,F-impl_trait_in_assoc_type

```rust
#![feature(impl_trait_in_assoc_type)]

fn coca(_: String) {}

trait Foo<T> {}
impl Foo<()> for String {}

trait Bar {
    type T;
    type I: Foo<Self::T>;
    type F: FnOnce(Self::I);

    const M: Self::F;
}

impl Bar for () {
    type T = impl Sized; // The compiler could infer this associated type as `()`.
    type I = impl Foo<Self::T>;
    type F = impl FnOnce(Self::I);

    const M: Self::F = coca;
}
```

[playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=ba5e2718db00ff48f015aafe9f511aab)

Errors with:

```rust
error[E0277]: the trait bound `String: Foo<<() as Bar>::T>` is not satisfied
  --> src/lib.rs:21:24
   |
21 |     const M: Self::F = coca;
   |                        ^^^^ the trait `Foo<<() as Bar>::T>` is not implemented for `String`
   |
   = help: the trait `Foo<()>` is implemented for `String`
```
Repository: godot
Issue: Can't preview FPS on the animation panel when editor language is set to ko (Korean)
Labels: bug,topic:editor

### Tested versions

- Reproducible in 4.3.stable, latest master [506d6e4]

### System information

* Godot v4.4.dev (506d6e427) - Windows 10.0.22631 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 (NVIDIA; 31.0.15.3623) - Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 threads)
* Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 (NVIDIA; 31.0.15.3623) - Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 Threads)

### Issue description

If the language of the editor is set to "ko" (Korean), you can't preview the FPS value (프레임) on the animation panel when it's not active.
You can only see it when you click it.

#### latest master [506d6e4]
https://github.com/user-attachments/assets/f48df47b-6179-4125-b103-bbb860270a50

#### v4.3.stable
https://github.com/user-attachments/assets/852b005c-4355-4b2f-992f-192aab2aaa44



### Steps to reproduce

Open the animation panel.

### Minimal reproduction project (MRP)

N/A
Repository: pytorch
Issue: Thread safety issue with torch.compile()
Labels: high priority,triaged,months,oncall: pt2,module: inductor,module: dynamo,module: pt2-dispatcher

See https://dev-discuss.pytorch.org/t/impact-of-multithreading-and-local-caching-on-torch-compile/2498 for a crash when two threads call torch.compile().

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @muchulee8 @ColinPeppler @amjames @desertfire @rec @bdhirsh
Repository: kubernetes
Issue: CronJob executed twice: once before and once at the scheduled time
Labels: kind/bug,sig/apps,lifecycle/rotten,needs-triage

### What happened?

While using Kubernetes CronJob for scheduling tasks, we encountered an issue where a specific CronJob was executed earlier than its scheduled time. The CronJob ran approximately 6 hours before the intended schedule and then executed again at the correct scheduled time, resulting in the job running twice. This issue was observed in a Kubernetes 1.25.5 environment.



### What did you expect to happen?

We expected the CronJob to execute exactly once at the scheduled time. All CronJobs should run according to their defined schedules without any duplication.



### How can we reproduce it (as minimally and precisely as possible)?

The issue occurred unexpectedly in a CronJob that was previously functioning correctly, and we haven't identified a way to reliably reproduce it. The problem has only happened once so far and has not occurred again since, indicating it may be an intermittent issue. The environment details are as follows:

The affected CronJob is scheduled to run daily.
There are a total of 26 CronJobs running in the cluster, with 12 of them in the affected namespace.
Some of these CronJobs in the same namespace are scheduled to run every minute or hourly.


### Anything else we need to know?

We attempted to identify the issue by checking the kube-controller-manager logs but did not find any anomalies.

### Kubernetes version

<details>

```console
Client Version: v1.31.0
Kustomize Version: v5.4.2
Server Version: v1.25.5
WARNING: version difference between client (1.31) and server (1.25) exceeds the supported minor version skew of +/-1
```

</details>


### Cloud provider

<details>
on-prem
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
```

</details>


### Install tools

<details>
cluster-api
</details>


### Container runtime (CRI) and version (if applicable)

<details>
containerd 1.6.8
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>
calico v3.24.1
</details>