sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]: img2img makes images darker
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?

Whenever using img2img, the output images always turn out darker (everywhere), but generally only when using a low denoise level. This is especially pronounced when using loopback in img2img, the darkness just compound!
 to make a very dark image 

Input image: 
![image](https://user-images.githubusercontent.com/46050679/212977745-3f3f6d00-9fa1-4384-880b-0fcebb31c0d8.png)

prompt: girl with eyes closed wearing red dress white sleeves
negative prompt: nsfw, lowres, bad anatomy, bad hands, text, error, missing fingers, extra digit, fewer digits, cropped, worst quality, low quality, normal quality, jpeg artifacts, signature, watermark, username, blurry,missing fingers,bad hands,missing arms, long neck, Humpbacked,shadow,long body, Abnormal fingers,

sampling steps: 20
width: 512
height: 768
cfg scale: 7
denoising strength: 0.05

img2img loopback, 32 loops, 1 denoising strength change

Output: 
![image](https://user-images.githubusercontent.com/46050679/212978143-8d057408-f84f-483d-bdde-8efb54fcb30e.png)
Final image:
![image](https://user-images.githubusercontent.com/46050679/212978206-68970183-7fd8-4acd-a23e-9280faa8b29b.png)

### Steps to reproduce the problem

1. Go to img2img
2. Enter input image
3. Set denoising strength to any low amount
4. Setup loopback script with high number of loops
5. Generate image


### What should have happened?

The images colors should have remained the mostly the same whilst the shape should have changed

### Commit where the problem happens

38b7186e6e3a4dffc93225308b822f0dae43a47d

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

Windows

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

Google Chrome

### Command Line Arguments

_No response_

### Additional information, context and logs

_No response_
Repository: flutter
Issue: Include assets from a directory recursively
Labels: tool,a: assets,c: proposal,P3,team-tool,triaged-tool

Greetings Flutter team & community,

I would like to re-open the discussion which started in #4890.

In particular, a mechanism to add asset files *recursively* would benefit my use case, and as evidenced by [this comment](https://github.com/flutter/flutter/issues/4890#issuecomment-407327749), I suspect would benefit use cases of others.

My present use case is that I would like to embed many files into the app, so that I do not have to stand up a back end to host the files. This seems like a fairly typical desire.

However, not being able to recursively add assets is a hindrance.

I understand that

- There are possible work-arounds, such as tools/scripts to generated the needed paths for the `assets` key
- The reason for not implementing recursive asset inclusion in #4890 relates to the handling of variants (see #16413 and [this](https://medium.com/flutter-community/contributing-to-flutter-part-3-4b96d924d8ba))

## Use case

Add many files as assets, for example, when you'd prefer to bundle files with the app package rather than download them separately.

## Proposal

I am mostly hoping to spark some conversation around this, although one possible way to do this given the legacy/constraints of variants would be to introduce a new pubspec.yaml key, analogous to `assets`, but which does not allow variants and will be capable of adding files recursively and/or by wildcard. Said new key could be named something like `nonvariant_assets`.

Thank you for your time.
Repository: godot
Issue: Capsule collisionShape3D losing properties if bezier animation is attempted
Labels: bug,topic:physics,topic:animation

### Godot version

beta12-1

### System information

Arch Linux (updated as of 17-jan-2023)

### Issue description

Capsules (and cylinders as I've tested, not sure about other collision shapes), after having one of their radius/height properties keyframed for animation, if Bezier or RESET track options are selected; the next time I move the timeline those height/radius properties get set automatically to 0.0001, making the capsule "collapse"

![Screenshot_20230117_192243](https://user-images.githubusercontent.com/36774104/212983526-0c9515e2-557b-4d2e-80a2-49522adf9368.png)
![Screenshot_20230117_192254](https://user-images.githubusercontent.com/36774104/212983529-585dacb2-275e-4ca4-bcc7-b024306afc82.png)

This seems something so basic I'm unsure if it's an actual bug, or complete failure on my end to understand what is happening; I've searched for other issues speaking about this but I've found nothing.

### Steps to reproduce

- Add CharacterBody3d to scene
- Add CollisionShape3d as a child, set the shape to capsule (default values)
- Add AnimationPlayer
- Create new animation on that player, whatever name
- Click the collisionShape3d, on the capsule shape properties, add a keyframe (key icon) on the Height of the capsule
- When prompted if you want bezier and/or reset, check bezier and/or reset  (leaving both blank doesnt make this fail)
  - _edit: the bug happens even if not one of those is set_
- Move the timeline forward
- The very moment you click it in order to perform the step above, you'll see the capsule has collapsed
- Note how not just the keyframed property (height) has turned 0, but also height which was not even touched at any point

### Minimal reproduction project

Unsure if it works as exported, to me it appears already collapsed when imported. Please follow the steps above
[Archive.zip](https://github.com/godotengine/godot/files/10438300/Archive.zip)
Repository: rust
Issue: Trait method signature mismatch could suggest changing the signature inline
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,D-terse

### Code

```Rust
use serde::Serialize;

trait Foo {
    fn bar(baz: i32, quux: String);
}

impl Foo for () {
    fn bar(baz: i32) {
        
    }
}

struct Bar;

impl Serialize for Bar {
    fn serialize<S>(&self) {
        
    }
}

fn main() {}
```


### Current output

```Shell
error[E0050]: method `bar` has 1 parameter but the declaration in trait `Foo::bar` has 2
 --> src/main.rs:8:17
  |
4 |     fn bar(baz: i32, quux: String);
  |                 ----------------- trait requires 2 parameters
...
8 |     fn bar(baz: i32) {
  |                 ^^^ expected 2 parameters, found 1

error[E0050]: method `serialize` has 1 parameter but the declaration in trait `serialize` has 2
  --> src/main.rs:16:21
   |
16 |     fn serialize<S>(&self) {
   |                     ^^^^^ expected 2 parameters, found 1
   |
   = note: `serialize` from trait: `fn(&Self, S) -> Result<<S as Serializer>::Ok, <S as Serializer>::Error>`

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


### Desired output

```Shell
error[E0050]: method `bar` has 1 parameter but the declaration in trait `Foo::bar` has 2
 --> src/main.rs:8:17
  |
4 |     fn bar(baz: i32, quux: String);
  |                 ----------------- trait requires 2 parameters
...
8 |     fn bar(baz: i32) {
  |                 ^^^ expected 2 parameters, found 1
help: modify the signature to match the trait definition
  |
8 |     fn bar(baz: i32, quux: String) {
  |                    ~~~~~~~~~~~~~~

error[E0050]: method `serialize` has 1 parameter but the declaration in trait `serialize` has 2
  --> src/main.rs:16:21
   |
16 |     fn serialize<S>(&self) {
   |                     ^^^^^ expected 2 parameters, found 1
   |
   = help: modify the signature to match the trait definition
   |
16 |     fn serialize(&self, serializer: S) -> Result<S::Ok, S::Error> {
   |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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


### Rationale and extra context

The current message is slightly different for local and external traits, but the idea is the same: instead of just writing out the signature, the message could instead suggest adding parameters to exactly match the trait definition.

This is similar to what we already do when a function call expression does not match the function parameters.

### Other cases

_No response_

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: Simplify module backward hooks to use multi-grad hooks instead
Labels: module: bc-breaking,module: autograd,module: nn,triaged,needs research,topic: bc breaking

Since modules can take in multiple inputs and return multiple outputs, currently we use a dummy custom autograd Function to ensure that there is a single grad_fn Node that we can attach our hook to. A multi-grad hook can be used to solve this issue in a less hacky way.

Note that this would be a bc-breaking change, as the hooks would be register to tensor instead of grad_fn, and the recorded backward graph would be different.

cc @ezyang @gchanan @albanD @zou3519 @gqchen @pearu @nikitaved @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @mikaylagawarecki @saketh-are
Repository: rust
Issue: rustc does not clear temporary files after `unconditional_panic` error
Labels: A-lints,T-compiler,C-bug,I-monomorphization,L-unconditional_panic

This is a simple code to check Rust's bound checking:
```rust
fn main() {
    let a = [1, 2, 3, 4, 5];
    let _x = a[9];
}
```


If we try to compile it with `rustc` (not `cargo`), `rustc` produces a bunch of object [files](https://i.stack.imgur.com/L90td.png)

If we fix the code and recompile it, rust clears the produced files.
Repository: pytorch
Issue: backward(inputs= does not need to execute grad_fn of the inputs
Labels: module: bc-breaking,module: autograd,triaged,actionable,topic: bc breaking

Per title, we currently execute grad_fn of the inputs when running `.backward()` with the `inputs=` argument. We should avoid unnecessarily doing this extra compute since it is not actually necessary for the computation of the gradients wrt the inputs. 

This is bc-breaking. This is mostly a bug-fix but a case where users may depend on this behavior is if they depend on hooks registered to Node to execute for the backward(inputs= case. Fixing this will require some changes to how we compute `needed` in the engine.

cc @ezyang @gchanan @albanD @zou3519 @gqchen @pearu @nikitaved @Lezcano @Varal7
Repository: PowerToys
Issue: Shortcut Guide specify numeric pad or standard keyboard key when using custom shortcut
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

If I use a custom shortcut as [Win] + [Shift] + [/]   it only works with one of the two slash keys in the keyboard, so it should be specified somehow that it is the regular one or the one in the numeric pad.
Repository: vscode
Issue: Disassembly view: context menus
Labels: feature-request,debug,debug-disassembly

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->

Please add a context menu for the disassembly view with at least (some of) the following options:

Go to source view

Show next instruction
Set next instruction
Run to cursor

Show Address
Show Code Bytes
Show Source Code
Show Symbol Names

And please make breakpoint menus work in disassembly view.
Repository: go
Issue: x/tools/gopls: `infertypeargs` diagnostic is missing `code`/`codeDescription` fields
Labels: gopls,Tools

```
[Trace - 5:11:20 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///Users/hakim/projects/tools/go/buildutil/allpackages.go","version":5,"diagnostics":[{"range":{"start":{"line":22,"character":9},"end":{"line":22,"character":17}},"severity":2,"source":"infertypeargs","message":"unnecessary type arguments","tags":[1]}]}
```

We expect it to be linked with detailed info about the analyzer e.g. https://github.com/golang/tools/blob/d958e854808e53978bb3f600901fcb7fa3f71163/gopls/doc/analyzers.md?plain=1#L201
Repository: rust
Issue: Tracking Issue for Async Functions in Dyn Traits
Labels: C-tracking-issue

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for async functions in dyn traits.
The feature gate for the issue will be `#![feature(async_fn_in_dyn_trait)]`.

See #91611 for the static version.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [ ] Write the RFC
- [ ] Implementation
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

- How do we convert between static async traits and dyn async traits?

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
Repository: node
Issue: TZ environment variable doesn't parse POSIX strings correctly
Labels: wrong repo,icu

### Version

v16.14.0

### Platform

Darwin XHFHLG2CJP.local 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 arm64

### Subsystem

_No response_

### What steps will reproduce the bug?

When the `TZ` environment variable is set and interpreted by Node, it should support any of the formats allowed by the TZ environment variable  (see [man tzset](https://man7.org/linux/man-pages/man3/tzset.3.html)).

It does appear to support IANA time zones (ex `America/Los_Angeles`) and POSIX time zones (ex `PST8PDT`), but it is not supporting POSIX time zones that include minutes or seconds in the offset, which is allowed by the `TZ` spec.

Example that works:

```bash
TZ=XXX+12 node -e 'console.log((new Date).getTimezoneOffset())'
# returns 720
```

Example that should work and does not:

```bash
TZ=XXX+12:00 node -e 'console.log((new Date).getTimezoneOffset())'
# should return 720, but returns whatever the local system's current time zone offset is
```


### How often does it reproduce? Is there a required condition?

always reproducible

### What is the expected behavior?

The `TZ` format should work in its entirety, as in the spec https://man7.org/linux/man-pages/man3/tzset.3.html

### What do you see instead?

Only IANA time zones, or POSIX time zones with simple whole-hour offsets are supported.

### Additional information

https://stackoverflow.com/questions/75150048/tz-utc0300-vs-tz-utc3-difference-for-nodejs
Repository: godot
Issue: Vulkan: LightmapGI is culled as soon as its origin is outside the camera frustum
Labels: bug,topic:rendering,topic:3d

### Godot version

4.0.beta13 (could be reproduced as early as 4.0.beta11, likely earlier)

### System information

Fedora 37, GeForce RTX 4090 (NVIDIA 525.60.11) / AMD Radeon RX 6900XT (Mesa RADV)

### Issue description

LightmapGI is culled as soon as its origin is outside the camera frustum (video courtesy of @adamscott):

[Capture vidéo du 2022-11-24 20:34:31.webm](https://user-images.githubusercontent.com/270928/203883178-b6f1bc59-a932-43a9-b5cd-f43767a8525a.webm)

This can be reproduced in the 3D global illumination demo as per https://github.com/godotengine/godot-demo-projects/pull/758, but also in https://github.com/Calinou/godot-sponza/tree/4.0-dev.

### Steps to reproduce

- Import a 3D scene with bake mode set to **Static Lightmaps**.
- Add a LightmapGI node, select it and click **Bake** at the top of the 3D editor viewport.
- Move around the camera. Notice how lightmaps disappear from the mesh once the camera moves/rotates in a way that puts the LightmapGI node's origin outside the camera frustum.

### Minimal reproduction project

- https://github.com/godotengine/godot-demo-projects/tree/4.0-dev/3d/global_illumination
- https://github.com/Calinou/godot-sponza/tree/4.0-dev

I can create a more minimal MRP if needed.
Repository: pytorch
Issue: TypeError: no implementation found for 'torch._ops.aten.max.default' on types that implement __torch_dispatch__: [<class 'torch.masked.maskedtensor.core.MaskedTensor'>]
Labels: triaged,module: masked operators

### 🐛 Describe the bug

My problem with MaskedTensor is that the stacktrace is extremely incorrect and vague, I am unable to debug the source of any error. It claims here that the "max" is not supported but there is no max in the code, and it doesn't even reference a relevant line, there is no way the for loop line is erroring as there is no pytorch code there.


```
/usr/local/lib/python3.8/dist-packages/torch/masked/maskedtensor/core.py:299: UserWarning: max is not implemented in __torch_dispatch__ for MaskedTensor.
If you would like this operator to be supported, please file an issue for a feature request at https://github.com/pytorch/maskedtensor/issues with a minimal reproducible code snippet.
In the case that the semantics for the operator are not trivial, it would be appreciated to also include a proposal for the semantics.
  warnings.warn(msg)
Traceback (most recent call last):
  File "adam_aug_lagrangian.py", line 90, in <module>
    for outermost_training_iter in range(num_training_iters):
  File "/usr/local/lib/python3.8/dist-packages/torch/masked/maskedtensor/core.py", line 274, in __torch_function__
    ret = func(*args, **kwargs)
TypeError: no implementation found for 'torch._ops.aten.max.default' on types that implement __torch_dispatch__: [<class 'torch.masked.maskedtensor.core.MaskedTensor'>]

```

### Versions

```
Collecting environment information...
PyTorch version: 1.13.1+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.5 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.8.10 (default, Nov 14 2022, 12:59:47)  [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.4.0-132-generic-x86_64-with-glibc2.29
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA RTX A5000
Nvidia driver version: 465.19.01
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.1
[pip3] pytorch-minimize==0.0.2
[pip3] torch==1.13.1
[conda] Could not collect

```
Repository: electron
Issue: [Feature Request]: Add a getContextMenu method for the system tray contextMenu
Labels: enhancement :sparkles:,component/tray

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Testing these programmatically is made difficult by their inaccessibility. See https://github.com/spaceagetv/electron-playwright-helpers/issues/16

### Proposed Solution

Add a `getContextMenu` method for use in testing cases

### Alternatives Considered

Users have to manually add ipc handlers for all such behaviors and duplicate them, leading to not testing exactly the code that the user will actually use.

### Additional Information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: XY Grid - control same parameter with two axes
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 ?

With additional_networks you can train a LoRA model through several epochs. Each training session gives a set of models placed in a folder with the epoch number in the name

So naturally it would be nice to have an "AddNet Epoch" axis for each model. The problem is the epoch number is inherit to the model file and isn't a separate slider you can change. Each file contains the epoch number in a directory structure like `model-A-epoch-00008.safetensors` So in essence that would require affecting a single parameter (the model filename) with two axes

The only thing preventing this is the `apply` function for axis options has no knowledge of the option in the opposing axis. With that information available you could notice that for example `model-filename-A` is set in the Y axis, so you could look up `model-filename-A-epoch00008` with axis value 8 or what have you

### Proposed workflow

The signature of `AxisOption.apply` is changed to `apply(p, x, xs, y, ys)` and all the `apply` variations are updated

### Additional information

_No response_
Repository: create-react-app
Issue: Is create-react-app no longer being maintained?
Labels: needs triage

I am curious if this project is simply dormant, or if it is no longer supported.

If it is no longer supported, it would be nice to include that verbiage, prominently, at the top of the README, so people don't take on tech debt just by using this package.
Repository: pytorch
Issue: operations failed in TorchScript interpreter
Labels: oncall: jit

### 🐛 Describe the bug

when I use  torch.jit._get_trace_graph to trace my model on GPU，it happens that
The PyTorch internal failed reason is:
The following operation failed in the TorchScript interpreter.
Traceback of TorchScript (most recent call last):
  File "/xxxx/python37/lib/python3.7/site-packages/torchvision/models/detection/roi_heads.py", line 466, in _onnx_paste_masks_in_image_loop
    res_append = torch.zeros(0, im_h, im_w)
    for i in range(masks.size(0)):
        mask_res = _onnx_paste_mask_in_image(masks[i][0], boxes[i], im_h, im_w)
                   ~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
        mask_res = mask_res.unsqueeze(0)
        res_append = torch.cat((res_append, mask_res))
  File "/xxx/site-packages/torchvision/models/detection/roi_heads.py", line 430, in _onnx_paste_mask_in_image
    zero = torch.zeros(1, dtype=torch.int64)

    w = box[2] - box[0] + one
        ~~~~~~~~~~~~~~~~~~~~~ <--- HERE
    h = box[3] - box[1] + one
    w = torch.max(torch.cat((w, one)))
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu!


### Versions

pytorch 1.12

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel