sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]: "Expecting value: line 1 column 1 (char 0)" thrown
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?

I'm using the python launch.py command but I can not utilise the function normally.
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/65069663/a9eee2e8-f129-4a48-b880-037cb0531c25)


### Steps to reproduce the problem

1. Download the package.
2. Download other packages it needs.
3. Run the webui.

### What should have happened?

Normal function.

### Sysinfo

I'm using windows system equipped with Python3.10.6.

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

_No response_

### Console logs

```Shell
D:\1Workshop\4Downhill\stable-diffusion-webui-master>python launch.py
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: No names found, cannot describe anything.
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: 1.6.1
Commit hash: <none>
Launching Web UI with arguments:
no module 'xformers'. Processing without...
no module 'xformers'. Processing without...
No module 'xformers'. Proceeding without it.
Loading weights [6ce0161689] from D:\1Workshop\4Downhill\stable-diffusion-webui-master\models\Stable-diffusion\v1-5-pruned-emaonly.safetensors
Running on local URL:  http://127.0.0.1:7860
```


### Additional information


I've pip downloaded xformers before. Any help is appreciated.
Repository: angular
Issue: Add ability to pass onlySelf option when updating FormArray
Labels: area: forms

### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

Here is my use case.  I have a form group with form control and a form array of form groups.  I have validation rules that need access to both form control and form array to validate.  I also have server side code that may add an item into an array.  When server request completes, I want to patch the entire form, then trigger business rules (validation rules).  This is currently not possible if number of items in an array that comes from the server is larger than the number of items in the corresponding form array.  PatchValue fired on the root form will throw an error if number of items in json array and FormArray is not the same.  Hence, I have to adjust the number of items.  However, both push and removeAt methods on FormArray do no support onlySelf option, like patchValue does.  Neither does setControl on FormGroup, which I could use to replace entire FormArray.  

### Proposed solution

Add onlySelf option to:
FormGroup's methods
  * setControl
  * removeControl

FormArray's methods
  * push
  * removeAt
  * insert
  * setControl

All of them already have options: {emitEvent?: boolean}, I am proposing to change that to options: {emitEvent?: boolean, onySelf? boolean}  When onlySelf is true, do not trigger validation for the parent just like in patchValue
Thank you!

### Alternatives considered

Replacing entire control, but that will trigger parent validation.  Disabling the control, but that seems ugly.
Thank you!
Repository: rust
Issue: Misleading error info where it should require explicit type annotations in nightly
Labels: A-diagnostics,T-compiler

### Code

```Rust
use std::io::Read;

struct Wrapper<In> {
    i: In,
}

impl<In: Read> Read for Wrapper<In> {
    fn read(&mut self, buf: &mut [u8]) -> std::io::Result<usize> {
        self.i.read(buf)
    }
}

impl<In> Read for &Wrapper<In>
where
    for<'a> &'a In: Read,
{
    fn read(&mut self, buf: &mut [u8]) -> std::io::Result<usize> {
        (&self.i).read(buf)
    }
}

trait FromReadable<S: Read>: Default {
    fn get(s: S) -> Self {
        Self::default()
    }
}

#[derive(Default)]
struct Got;

impl<S: Read> FromReadable<S> for Got {}
fn from_readable<S: Read, G: FromReadable<S>>(g: G) {}

impl<In> Wrapper<In>
where
    for<'a> &'a In: Read,
{
    fn foo(&self) {
        let got = Got::get(self);
        //from_readable::<&In, _>(got)
        from_readable(got)
    }
}
```


### Current output

```Shell
error[E0275]: overflow evaluating the requirement `for<'a> &'a Wrapper<_>: std::io::Read`
   |
   = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`playground`)
note: required for `&'a Wrapper<Wrapper<_>>` to implement `for<'a> std::io::Read`
  --> src/lib.rs:15:10
   |
15 | impl<In> Read for &Wrapper<In> 
   |          ^^^^     ^^^^^^^^^^^^
16 | where for <'a> &'a In :Read
   |                        ---- unsatisfied trait bound introduced here
   = note: 126 redundant requirements hidden
   = note: required for `&Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<Wrapper<...>>>>>>>>>>>` to implement `for<'a> std::io::Read`
   = note: the full type name has been written to '/playground/target/debug/deps/playground-a9202c2be828afe8.long-type-989942384064675355.txt'

For more information about this error, try `rustc --explain E0275`.
```


### Desired output

```Shell
error[E0282]: type annotations needed
  --> src/lib.rs:38:9
   |
38 |         from_readable(got)
   |         ^^^^^^^^^^^^^ cannot infer type of the type parameter `S` declared on the function `from_readable`
   |
help: consider specifying the generic arguments
   |
38 |         from_readable::<S, Got>(got)
   |                      ++++++++++

For more information about this error, try `rustc --explain E0282`.
error: could not compile `playground` (lib) due to previous error
```


### Rationale and extra context

Current stable channel version 1.74 gives the desired output, but nightly channel version 1.76 gives the misleading infos.

### Other cases

_No response_

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"mu001999"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: tauri
Issue: [bug] Updater fails for macOS-sandboxed apps
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

Sandboxed macOS apps do not have permissions to write to the installation folder, so updates fail. Sparkle gets around this by running the updater outside the app sandbox. https://sparkle-project.org/documentation/sandboxing/

### Reproduction

Build a sandboxed app and try running the updater.

My entitlements file is as follows:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>

    <key>com.apple.security.files.user-selected.read-write</key>
    <true/>

    <key>com.apple.security.network.client</key>
    <true/>
</dict>
</plist>
```

### Expected behavior

There should be a way to auto-update with sandbox enabled.

### Platform and versions

```text
[✔] Environment
    - OS: Mac OS 14.1.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.73.0 (cc66ad468 2023-10-03)
    ✔ cargo: 1.73.0 (9c4383fb5 2023-08-26)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.6.1
    - pnpm: 8.6.3
    - yarn: 3.4.1
    - npm: 9.8.1
    - bun: 1.0.0

[-] Packages
    - tauri [RUST]: 1.5.2
    - tauri-build [RUST]: 1.5.0
    - wry [RUST]: 0.24.4
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.5.1
    - @tauri-apps/cli [NPM]: 1.5.6

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite
```
```


### Stack trace

```text
The following is the error event emitted by the updater:


Tauri API error: Operation not permitted (os error 1)
```
```


### Additional context

_No response_
Repository: go
Issue: proposal: x/tools/cmd/goimports: add flag to remove blank lines in import for regrouping during formatting
Labels: Proposal

# current

The goimports will retain blank lines and multiple groups will exist after formatting.

testdata in.go:
```go
import (
	"fmt"


	"github.com/foo/a"
	"github.com/foo/b"

	"go.pkg.com/bar/x"
	"go.pkg.com/bar/y"
	"context"


	"github.com/foo/c"
	"go.pkg.com/bar/z"
)
```

`goimports -local go.pkg.com in.go` output:

```go
package foo

import (
        "fmt"

        "github.com/foo/a"
        "github.com/foo/b"

        "context"

        "go.pkg.com/bar/x"
        "go.pkg.com/bar/y"

        "github.com/foo/c"

        "go.pkg.com/bar/z"
)
```
# expect

Would like a tool to automate the removal of blank lines and regrouping.

Add a  `-r` flag, `goimports -r -local go.pkg.com in.go` output:
```go
package foo

import (
        "context"
        "fmt"

        "github.com/foo/a"
        "github.com/foo/b"
        "github.com/foo/c"

        "go.pkg.com/bar/x"
        "go.pkg.com/bar/y"
        "go.pkg.com/bar/z"
)

```

# implement

It's easy to implement, here's the pseudo-code:

```go
// add flag
regroup = flag.Bool("r", false, "remove blank line and regroup imports")


func processFile() {
    if *regroup {
        src = removeBlankLineInImport(src)
    }

    // origin imports.Process
    res, err := imports.Process(target, src, opt)
}

func removeBlankLineInImport(src []byte) []byte {
    // 1. parset AST
    // 2. find first import block start and end line
    // 3. rewrite src, remove blank line in import block
}
```

No breaking changes, and even regrouping keeps compatibility with the original goimports rules.

We forked goimports in our internal project and added this feature so that if the proposal is accepted, I can submit a PR.
Repository: godot
Issue: Additive blend mode causes shimmering with FSR 2.
Labels: bug,topic:rendering,topic:3d

### Godot version

4.2 rc1

### System information

Windows 11, RTX 2070 Super

### Issue description

Additive materials don't seem to play nicely with FSR 2, as you can see in the below video (the lens flares from the lamps are additive billboards).

https://github.com/godotengine/godot/assets/20043270/7e87e6d3-ae29-4aed-9779-5fe9ba259fad

However the effect works correctly with TAA, suggesting this is an FSR specific issue and not a general one with temporal reconstruction.

https://github.com/godotengine/godot/assets/20043270/08b006e5-b436-4bc1-b9d9-869c31ea41cf




### Steps to reproduce

- Download the MRP and upgrade it to 4.2 rc1.
- Toggle FSR 2 on in the Scaling 3D settings.
- Compare with TAA, FSR 1 and FXAA results.

### Minimal reproduction project

https://github.com/perfoon/Abandoned-Spaceship-Godot-Demo
Repository: ant-design
Issue: 在 next 中 使用 Table 的 sticky中的offsetHeader有问题
Labels: Inactive,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-f6kmdr?file=/index.js)

### Steps to reproduce

刷新表格title 先空白在展示

### What is expected?

直接展示title 不要空白

### What is actually happening?

先空白在展示文案

| Environment | Info |
| --- | --- |
| antd | 5.11.0 |
| React | react |
| System | window |
| Browser | Google Chrome 19.0.6045.159 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: [RFC] Support for Redundant Hosts in TorchElastic
Labels: oncall: distributed,triaged,module: elastic

### 🚀 The feature, motivation and pitch

# Summary

Allow TorchElastic to manage more nodes than a maximum `nnodes` specifed in a job. It will be used as a spare capacity/warm nodes for schedulers that support elasticity. 

# Motivation
Non-application failures that require host replacement will need to provision new hosts. This delays overall job recovery since healthy nodes will need to rendezvous with newly provisioned hosts. 

- Failures could include: hardware faults, scheduled maintenance and emergency security maintenance events. 
- Provisioning may include host allocation by a scheduler, booting and application package deployment.


To reduce the time to recover in those cases, users may simply opt-in into **overprovisioning** if a user job support elasticity. This will provide additional trade-off between recovery time and hardware underutilization. The failure needs to satisfy  `N_hosts_replaced <= (N_hosts - N_max_nnodes)` requirement in order to address potential delay.

# Proposed implementation: allow registering redundant nodes in rendezvous handler 

Update rendezvous handler implementations to allow:

- Maintain existing contract between agent and rendezvous handler that uses non-zero `num_nodes_waiting()` value to signal start of re-rendezvous process ([ref](https://github.com/pytorch/pytorch/blob/main/torch/distributed/elastic/agent/server/api.py#L900C49-L900C67)): 
- Each rendezvous handler implementation will permit registration of agents that more that `max_nodes` value:
   - On redundant nodes, agent will block on `next_rendezvous()` call and could potentially join the next rendezvous. It have no impact on `num_nodes_waiting()` value till next round of rendezvous.
   - Any membership changes when current node count is <= `max_nodes`, we will maintain existing behavior.

Pros:
- Simple non-intrusive implementation and easier POC validation
Cons:
- Implementation must eventually be replicated in each rendezvous handler.


### Alternatives

We could introduce explicit *capacity* construct, with possible `min:max` range, that the rendezvous process would expect at first hand-shake. Capacity will be required to be >= `max_nodes`.

Pros:
- Earlier potential host issues detection since we would expect all of them to attempt to hand-shake.
- Explicit contract that will be “visible” at launcher (e.g TorchX) layer. For example above proposal will require additional logic in scheduling code. 

Cons:
- More complex implementation + additional user facing contract.


### Additional context

_No response_

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @dzhulgakov @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @penguinwu
Repository: go
Issue: cmd/compile: missing BCE optimization cases
Labels: Performance,NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.21.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

https://github.com/golang/go/blob/go1.21.4/src/slices/slices.go#L346-L385

```go
func Compact[S ~[]E, E comparable](s S) S {
	if len(s) < 2 {
		return s
	}
	i := 1
	for k := 1; k < len(s); k++ {
		if s[k] != s[k-1] {
			if i != k {
				s[i] = s[k] // Found IsInBounds
			}
			i++
		}
	}
	clear(s[i:]) // Found IsSliceInBounds
	return s[:i]
}

func CompactFunc[S ~[]E, E any](s S, eq func(E, E) bool) S {
	if len(s) < 2 {
		return s
	}
	i := 1
	for k := 1; k < len(s); k++ {
		if !eq(s[k], s[k-1]) {
			if i != k {
				s[i] = s[k] // Found IsInBounds
			}
			i++
		}
	}
	clear(s[i:]) // Found IsSliceInBounds
	return s[:i]
}
```

And 

```go
func DeleteFunc[S ~[]E, E any](s S, del func(E) bool) S {
	i := IndexFunc(s, del)
	if i == -1 {
		return s
	}
	// Don't start copying elements until we find one to delete.
	for j := i + 1; j < len(s); j++ {
		if v := s[j]; !del(v) { // Found IsInBounds
			s[i] = v // Found IsInBounds
			i++
		}
	}
	clear(s[i:]) // Found IsSliceInBounds
	return s[:i]
}
```

### What did you expect to see?

No bound checks.

### What did you see instead?

Many bound checks.

This problem might have been reported before, but I couldn't find it now.
Repository: next.js
Issue: PerformanceNavigationTiming "navigate" event does not fire for app-router to app-router navigations
Labels: bug

### Link to the code that reproduces this issue

https://github.com/tavvy/nextjs-navigate-event-reproduction

### To Reproduce

1. https://nextjs-navigate-event-reproduction.vercel.app/
2. navigate from app rotuer -> app router
3. check console log for CWV logs
4. No PerformanceNavigationTiming "navigate" events fired, so no TTFB, FCP etc

### Current vs. Expected behavior

App router -> App router page navigations should fire PerformanceNavigationTiming "navigate" events so that web vital metrics are collected.

### 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.6.0: Fri Sep 15 13:41:28 PDT 2023; root:xnu-8796.141.3.700.8~1/RELEASE_ARM64_T6000
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.9.2
Relevant Packages:
  next: 14.0.4-canary.5
  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) are affected? (Select all that apply)

App Router

### Additional context

App router -> App router navigations do not fire the ["navigate" PerformanceNavigationTiming event](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming/type).

Pages -> App router and App router -> pages are not impacted.

Please see the reproduction deployment: https://nextjs-navigate-event-reproduction.vercel.app/ Click around and view console logs

I used the vanilla web vitals script https://github.com/GoogleChrome/web-vitals as I want to demonstrate the problem is "outside" of the vercel web vital hook implementations. The same issue is present in the custom vercel / next web vital hook implementations.

I've used `next/link` but the same issue is present with `router.push()` (my main use case).

The main issue is this **drastically** reduces the number of CWV data points that will be collected for a project. We went from 10,000s per/hour to just 10s! I understand these metrics just wrap browser apis. My concern is this will reflect how the Google CrUX data is collected and site page scores are going to be impacted as the sample size is so small and thus variance in the data is far greater .
Repository: next.js
Issue: Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime
Labels: bug

### Link to the code that reproduces this issue

https://github.com/azr-arch/realtime-chat-app

### To Reproduce

try building the app with `npm run build`

### Current vs. Expected behavior

**Current Behavior:**
When I attempt to build my Next.js application for deployment, the build process fails. The error message indicates that dynamic code evaluation (e.g., 'eval', 'new Function', 'WebAssembly.compile') is not allowed in Edge Runtime. The error seems to originate from the `@babel/runtime/regenerator` and `next-auth/react` modules.

Here's the error message I received:

```
Failed to compile.

./node_modules/@babel/runtime/regenerator/index.js
Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime 
Learn More: https://nextjs.org/docs/messages/edge-dynamic-code-evaluation

Import trace for requested module:
./node_modules/@babel/runtime/regenerator/index.js
./node_modules/next-auth/react/index.js

> Build failed because of webpack errors
```

**Expected Behavior:**
I expected the build process to complete without errors, allowing me to deploy my Next.js application.

**Steps to Reproduce:**
1. Run the build command for the Next.js application.
2. Observe the error message related to dynamic code evaluation in Edge Runtime.

---

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
Binaries:
  Node: 21.1.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.1
  eslint-config-next: 14.0.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

also, any help regarding this 

```
(node:7360) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
```

would be appreciated.

Note: this warning only shows during `npm run dev`
Repository: react
Issue: [DevTools Bug] Cannot add node "1590" because a node with that id is already in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://editor.wix.com/html/editor/web/renderer/edit/1e14587f-a72d-4b5f-866d-f00b1ede1959?metaSiteId=e0eb6e2b-eb02-4e61-8c27-b28c38ce72f9

### Repro steps

Just open web and error show

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

4.28.5-ef8a840bd

### Error message (automated)

Cannot add node "1590" because a node with that id is already in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1125187
    at A.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1095954)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1097642
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1495532)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: material-ui
Issue: [material-ui][Tabs] Focus not moving correctly on the scrollable variant
Labels: component: tabs,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:https://mui.com/material-ui/react-tabs/#scrollable-tabs

Steps:

1. Select tab 6 or 7 in portrait mode
2. Switch to landscape mode after moving the tab foucs
3. Switch back to portrait mode and see if the screen stays visible


### Current behavior 😯

Focus does not move to the previously selected tab.

### Expected behavior 🤔

The focus should move to the previously selected tab.

### Context 🔦

Hello bro,
There was a problem coding the scrollable tab.

If you have multiple tabs and are on a mobile phone,
Scroll to select a tab and
When switching from horizontal to vertical, you will not be able to move to the previously selected tab.

Check the example below : 
https://mui.com/material-ui/react-tabs/#scrollable-tabs

It works normally in v4, but a problem occurs with the update to v5.

Check the example below : 
https://v4.mui.com/components/tabs/#scrollable-tabs

Thank you 4 ur hard work. :)

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>