sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: Changing theme does not change background color when using CSS variables
Labels: docs,support: question,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Live example links

https://codesandbox.io/s/create-react-app-with-typescript-forked-46llm7?file=/src/index.tsx

https://nikhil1920.github.io/next-js-mui-pwa-starter/

### Current behavior 😯

Background color is not changing based on theme

### Expected behavior 🤔

Background color should change based on current theme

### Context 🔦

_No response_

### Your environment 🌎

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: ScuNet quality issue
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?

The ScuNet implementation recently added seems to be bugged as it produces worse quality images then the official demo here https://replicate.com/cszn/scunet.
Using their own example images, first is original, second using the online demo and third the one created by this app:
![Flowers](https://user-images.githubusercontent.com/599468/198354668-b024487e-a9cb-440e-ac31-cd65fbe8b899.png)
![output](https://user-images.githubusercontent.com/599468/198354972-d1f0d8c4-b0de-4847-92ad-4fa0bd0835d3.png)
![tmpooue_vzr](https://user-images.githubusercontent.com/599468/198355033-d5288be1-8a7b-4dc3-a72b-1479626ddedb.png)
![6](https://user-images.githubusercontent.com/599468/198355446-cb66bb32-2c70-40a4-90d9-1190a4f0b2a2.png)
![output](https://user-images.githubusercontent.com/599468/198355535-3e050369-6780-407a-b4f8-3b5cd1ca1cef.png)
![tmp7e9z4hlf](https://user-images.githubusercontent.com/599468/198355592-eaeba79d-dd76-41c0-a5c6-0cdb508b8691.png)

This implementation seems to lose a lot more details by smoothing out the image more and also changes the colors a lot.

Also as a side note the two different ScuNet models seems to create identical images, diffing an image from each of them with PIL returns identical image data.

### Steps to reproduce the problem

1. Go to Extras tab
2. Load an image with some noise and chose one of the ScuNet models
3. Generate the image
4. Go to https://replicate.com/cszn/scunet
5. Use the same image and make sure real image denoising is selected
6. Submit to generate the image
7. Compare the two results 

### What should have happened?

Quality of the generated image in this repo should be similar to the demo generated image

### Commit where the problem happens

737eb28faca8be2bb996ee0930ec77d1f7ebd939

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

Windows

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

Google Chrome

### Command Line Arguments

```Shell
No commands
```


### Additional information, context and logs

_No response_
Repository: create-react-app
Issue: Allow users to override roots in Jest config
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

#7480 set jest config key `roots` to be `<rootDir>/src`. However this locks users into putting all jest-related files under the `src` directory.

Jest is unable to locate my tests if they are not located in the `<rootDir>/src` folder.
Given the following override to `testMatch` files in `<rootDir>/features` will never match.
```json
"jest": {
  "testMatch": [
    "<rootDir>/src/**/*.{spec,test}.{js,jsx,ts,tsx}",
    "<rootDir>/features/**/*.steps.{js,ts}"
  ]
}
```

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

#### A) `react-scripts/scripts/utils/createJestConfig.js` could add `roots` to `supportedKeys` to allow users to override default.
This would be the simplest change and give users the most control. Exposing the remaining `*PathIgnorePatterns` config keys would give users complete control to avoid parsing `node_modules`.

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

#### B) `createJestConfig.js` could support non-standard key, `additionalRoots`, which gets appended to `config['roots']
This would help avoid users accidentally dropping `<rootDir>/src` from `config['roots']`, but may need additional documentation.

#### C) `createJestConfig.js` could examine `overrides['testMatch']` to determine additional folders required for `config['roots']`
This would involve extra logic in `createJestConfig.js` and is probably not desirable

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

#7480 was introduced with #7458 because `node_modules` was being parsed and reducing performance
Repository: go
Issue: proposal: x/exp/future: new package to implement futures
Labels: Proposal

Futures have been proposed previously in various forms, most notably in #17466 where it was turned down due to being too unimportant to be done as a language change. Since then, generics have been added to the language, making it quite simple to implement futures in a type-safe way without needing any language changes. So here's a proposal to do just that.

Conceptually, a future functions similarly to a one-time use channel that can yield the value that it's given more than once. The benefit over just a normal channel is that it simplifies a 1:M case where multiple receivers need to wait on the same piece of data from a single source. This covers some of the cases, for example, that #16620 is meant to handle.

Here's a possible implementation:

```go
package future

import (
	"fmt"
	"sync"
	"time"
)

type Future[T any] struct {
	done chan struct{}
	val  T
}

func New[T any]() (f *Future[T], complete func(T)) {
	var once sync.Once
	f = &Future[T]{
		done: make(chan struct{}),
	}

	return f, func(val T) {
		once.Do(func() {
			f.val = val
			close(f.done)
		})
	}
}

// Unsure on the name. Maybe Ready or something instead?
func (f *Future[T]) Done() <-chan struct{} {
	return f.done
}

// Maybe Value instead of Get? Blocking in Value feels weird to me, though.
func (f *Future[T]) Get() T {
	<-f.done
	return f.val
}
```

And an example of the usage:

```go
func example() *future.Future[string] {
  f, complete := future.New[string]()
  go func() {
    time.Sleep(3 * time.Second) // Long-running operation of some kind or something.
    complete("Voila.")
  }()
  return f
}

func main() {
  r := example()
  fmt.Println(r.Get())
}
```

This API is patterned after `context.Context`. The exposure of the `done` channel makes it simple to wait for a future in a `select` case, but it's not necessary to use it to get the value in a safe way.

If the package was deemed to be useful after sitting in `x/exp`, it could be promoted to either `x/sync` or directly into `sync`.
Repository: flutter
Issue: CupertinoPageRoute barrier and shadow paints offscreen unnecessarily for the bottom route
Labels: framework,f: cupertino,perf: memory,perf: speed,team-design,triaged-design

`CupertinoPageRoute` includes a partially-transparent `ModalBarrier` behind it, as well as a drop-shadow on its left edge. This is to match the native page transition while a new page slides over on top of the current one. But this occurs even on the bottom/first route in the `Navigator`, where both the shadow and the background fill should never be visible to the user. So this increases raster time and/or memory usage. 

## `CupertinoModalBarrier`

<img width="888" alt="image" src="https://user-images.githubusercontent.com/789275/198301500-86a38722-755c-4634-b3a3-cae432d636a1.png">

(rectangle of `0x00000018`)

## `CupertinoPageTransition`

<img width="887" alt="image" src="https://user-images.githubusercontent.com/789275/198301568-70d3bc96-2550-457f-ad79-a8b0c4df653a.png">

## Example code

```dart
import 'package:flutter/cupertino.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Padding(
      padding: EdgeInsets.all(64),
      child: CupertinoApp(
        home: CupertinoPageScaffold(
          child: Center(
            child: Text('content')
          )
        )
      )
    );
  }
}
```
Repository: stable-diffusion-webui
Issue: [Feature Request]: Settings Presets
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 ?

Save and load different options: When using Novel AI's model you have to tweak several options that other models don't require, if you change back into the Standard SD Model (or another different one) you have to manually disable those options to the other model to work properly.
Also, adjusting settings seeds, ddim steps or prompts, saving those and loading them for future use.

### Proposed workflow

1. Go to Settings
2. Adjusts the Settings and Options that you need
3. Click a new "Save Custom Settings" button
4. In main Menu you could "Save parameters" to save prompt, seeds, ddim, cfg scale, sampling method, etc
5. Load the Custom settings or your custom parameters anytime, allowing you to pick between previously saved configurations.


### Additional information

_No response_
Repository: flutter
Issue: Condense iOS and macOS into a single Xcode project
Labels: platform-ios,platform-mac,P3,team-ios,triaged-ios

## Use case
It seems that when you deploy a Flutter app to iOS and macOS, you would need to take some repetitive steps. For example, opening the 'ios' folder in Xcode to change build settings, and then later open the 'macos' folder in Xcode to change the build settings again. 

Steps are detailed here: https://docs.flutter.dev/deployment/macos#review-xcode-project-settings

## Proposal
When you use the Swift multi-platform you have one project, with one target for the app itself. The project settings specify two deployment targets, and the app target allows you control the specifics for macOS and iOS as shown below. If Flutter generated just a single project, it would make it easier to complete some of the duplicate steps and also may make it easier to manage common assets for the app store. 

<img width="871" alt="Screenshot 2022-10-27 at 4 25 17 PM" src="https://user-images.githubusercontent.com/21065911/198391245-07f6cb84-feb0-47e0-af08-4aaf8408f440.png">


Full disclosure, I'm not even sure this is a good idea. If most people are just developing for iOS and Android, then this might give unnecessary overhead (deleting the mac target information). Another alternative is adding documentation that walks through adding macOS as a supported destination for the iOS runner project, but not sure if that would just work, or if will be confusing if the macOS project still exists.
Repository: PowerToys
Issue: Map Caps Lock to Shift (Left) does not work when waking from screen saver
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Priority-2,Status-Reproducible

### Microsoft PowerToys version

0.63.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I've mapped `Caps Lock` to `Shift (Left)` so I never want the `Caps Lock` to get locked:
![image](https://user-images.githubusercontent.com/13519180/198391782-865fe7da-2e17-4a78-993f-c4cc78178801.png)

However when the screen saver is active and I wake the system using the `Caps Lock ` button, the `Caps Lock` is turned on, and because the system is awake again (and `Keyboard manager` is active again) I cannot turn `Caps Lock` off, which is (to say the least) very annoying. I have to _disable_ the `Keyboard Manager`, press `Caps Lock` to turn it off and then _enable_ `Keyboard Manager` again.

### ✔️ Expected Behavior

Mapping is _active_ when screen saver is active

### ❌ Actual Behavior

Mapping is _disabled_ (at least for the `Caps Lock` key) so the keys have their original (not mapped) function

### Other Software

_No response_
Repository: pytorch
Issue: Permute
Labels: module: docs,triaged

## 📚 Documentation

In documentation:

we are told to use permute like this
torch.permute(x, (2, 0, 1)).size()

Also usage:
x = x.permute(2,0,1)

cc @svekars @carljparker
Repository: go
Issue: x/build/internal/relui: allow scheduled workflows to optionally fail fast
Labels: Builders,NeedsFix

Currently, in relui, a scheduled workflow may fail and send a notification for user intervention. For some workflows, we'd like to be able to have them outright fail and be superseded by the next workflow run.

With the change in https://go.dev/cl/444695, it probably makes the most sense for the WorkflowStalled handler to try to find if a Schedule is configured to fail-fast.
Repository: godot
Issue: Improve BaseMaterial3D flowmap compression by using RGTC VRAM compression (like normal maps)
Labels: enhancement,discussion,topic:rendering,topic:3d

### Godot version

v4.0.beta3.official [01ae26d31]

### System information

Windows 10, Vulkan, GTX 960 522.25

### Issue description

The picture describes everything:
![screenshot](https://user-images.githubusercontent.com/48926464/198414681-fdb24469-abe8-4a4f-b0a3-71b60bc2eb86.png)


### Steps to reproduce

1.- Create a Standard material.
2.-Set the roughness about 0.5.
3.- Activate the anisotropy and set it to 1.
4.- Insert the flowmap and observe.

### Minimal reproduction project


You can try it with this flowmap or with any other:
![anisodir01kmozm](https://user-images.githubusercontent.com/48926464/198415545-1cbf4abf-8ad4-4ce8-a9b4-b4f328b10df9.png)
Repository: rust
Issue: &Box<[u8; 1000]> cannot be coerced to &[u8]
Labels: T-compiler,C-bug,A-coercions

Consider this code (it is minimal reproducible example):

```rust
fn f(_: &[u8]) {
}

fn main() {
    let b = Box::new([0u8; 1000]);
    f(&b);
}
```

It doesn't compile, and I don't like this.
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1a1a8a172c0e3c580c2faa261694ee6a

Now let me describe why I need this to compile. I. e. let me tell you my actual problem. I have a wrapper for `libc::read` called `read_repeatedly` with this signature: `pub fn read_repeatedly(fildes: c_int, buf: &mut [u8]) -> Result<&mut [u8], Errno>`. I tried to allocate a buffer so: `let mut buf = box [0u8; 10_000]`. I allocated it in heap, because I'm afraid of getting stack overflow. And I used `box` instead of `Box::new`, because I'm afraid that `Box::new([0u8; 10_000])` first allocates a buffer on stack and then moves it to box (I have read about this problem here: https://github.com/PoignardAzur/placement-by-return/blob/placement-by-return/text/0000-placement-by-return.md ). I used a box instead of vec, because I think one should always use box unless he really needs a vec.

Then I did this: `read_repeatedly(socket2, &mut buf)`. And it did not work. I was able to fix the code so: `read_repeatedly(socket2, buf.as_mut())`. Still I think original code should work.

Yes, this bug is probably not a bug. I. e. the compiler probably works as intended. But still current behavior is confusing. I see clear path how the value should be coerced: `&mut Box<[u8; 10_000]>` -> `&mut [u8; 10_000]` -> `&mut [u8]`
Repository: flutter
Issue: Documentation for debugging the engine with Visual Studio Code on Linux
Labels: engine,d: api docs,a: debugging,platform-linux,P3,team-engine,triaged-engine

Hi. I am trying to debug the flutter engine to locate an unexpected behavior happening on Ubuntu. After reading the [Debugging the engine](https://github.com/flutter/flutter/wiki/Debugging-the-engine), I have built the engine for Linux successfully. But I didn't find a way to debug the engine on VSCode. Am I missing some important documentation?

My expectation is to be able to open src/flutter with Vscode and set breakpoints.
Repository: pytorch
Issue: AttributeError: '_MultiProcessingDataLoaderIter' object has no attribute 'next'
Labels: module: dataloader,triaged

### 🐛 Describe the bug

the same code can run in pytorch11.3， but can’t in 11.7.。。
 inputs_x, targets_x, index_x = labeled_train_iter.next()
AttributeError: '_MultiProcessingDataLoaderIter' object has no attribute 'next'

### Versions

version
cuda11.8
cudnn8.6.0
python3.8
torch version：1.14.0


cc @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: rust
Issue: Improve suggestion for misused str::get
Labels: C-enhancement,A-diagnostics,T-compiler,D-papercut

Given the following code ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=3fdf018c55f29ccc3e59f02acb689c83)):

```rust
fn main() {
    let s = "Hello World";
    let lo = 0_usize;
    let hi = 5_usize;
    let t = s.get(lo, hi).unwrap();
    println!("{t}");
}
```

The current output is long and includes a suggestion that doesn't fix my code:

```
error[E0277]: the type `str` cannot be indexed by `usize`
 --> src/main.rs:5:19
  |
5 |     let t = s.get(lo, hi).unwrap();
  |               --- ^^ string indices are ranges of `usize`
  |               |
  |               required by a bound introduced by this call
  |
  = help: the trait `SliceIndex<str>` is not implemented for `usize`
  = help: the trait `SliceIndex<[T]>` is implemented for `usize`
note: required by a bound in `core::str::<impl str>::get`

error[E0061]: this function takes 1 argument but 2 arguments were supplied
 --> src/main.rs:5:15
  |
5 |     let t = s.get(lo, hi).unwrap();
  |               ^^^     -- argument of type `usize` unexpected
  |
note: associated function defined here
help: remove the extra argument
  |
5 |     let t = s.get(lo).unwrap();
  |                  ~~~~
```

Ideally the output would be shorter and suggest the correct fix:

```
Error: string indexes should be a range, not two separate arguments

help: construct a range:
  |
5 |     let t = s.get(lo .. hi).unwrap();
  |                   ~~~~~~~~
```
Repository: pytorch
Issue: Autograd doesn't stop executing backward graph early enough in situations involving set_
Labels: module: autograd,triaged,has workaround,actionable

### 🐛 Describe the bug

Before the bug, the reproducing program is a bit whacky, so I need to explain why it might be reasonable to expect it not to error.

Suppose I have a naughty custom autograd function, that returns gradients of the wrong size. If I use grad() to cut off autograd computation before I actually get to the naughty autograd function, I would expect to never actually hit the error case. And indeed, this program runs successfully:

```
import torch

class F(torch.autograd.Function):
    @staticmethod
    def forward(ctx, x):
        return x.clone()

    @staticmethod
    def backward(ctx, grad_output):
        return torch.zeros(6, requires_grad=True)

x = torch.zeros(4, requires_grad=True)
y = F.apply(x)
z = y.clone()

print(torch.autograd.grad((z,), (y,), grad_outputs=torch.ones_like(z)))
```

In general, I would expect that no matter how naughty the history of how x was created, so long as I grad with respect to it as an input, it should be "as if" I had detached it from the rest of the graph, all sins absolved.

Here is a program for which I am too naughty, and this invariant does not hold:

```
x = torch.zeros(0)
x.requires_grad = True
x2 = x.clone()
with torch.no_grad():
    x2.set_(torch.zeros(5).storage(), 0, (5,), (1,))
y = x2.clone()

print(torch.autograd.grad((y.sum(),), (x2,)))
```

Fails with:

```
  File "auto.py", line 26, in <module>
    print(torch.autograd.grad((y.sum(),), (x2,)))
  File "/raid/ezyang/pytorch-scratch2/torch/autograd/__init__.py", line 300, in grad
    return Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: Function CloneBackward0 returned an invalid gradient at index 0 - got [5] but expected shape compatible with [0]
```

This minimal repro is from real code extracted from MetaConverter (written by yours truly) which tries to synthesize variables which resemble input variables as much as possible in all properties. Note that if you ablate the `no_grad`, the program passes, but I am not allowed to do this as in some real programs x may be a leaf variable.

I have a workaround for this problem, which is to allocate an appropriately sized x from the get go, so this is not a blocker to fix. But it would be good to better understand what is going on here, in case there is a more serious bug.

cc @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 

### Versions

master
Repository: create-react-app
Issue: Eslint errors when migrating CRA4 to CRA5 
Labels: needs triage,issue: bug report

Recently migrated an existing application from CRA4 to CRA5. 
Though the eslint rules remain the same, there are multiple listing errors that we are facing.
FYI - The following package versions are also updated.
- eslint - 8.25.0
- typescript-eslint/eslint-plugin: 5.40.0.
<img width="525" alt="Screenshot 2022-10-28 at 9 10 35 AM" src="https://user-images.githubusercontent.com/87611157/198497233-895d5c81-27c5-435b-b60a-6b5c379834f9.png">
<img width="1324" alt="Screenshot 2022-10-28 at 9 10 44 AM" src="https://user-images.githubusercontent.com/87611157/198497239-9b402353-7efe-4fdf-9535-853b62d5c1c2.png">

Errors attached in the screenshot is not happening for CRA 4 version, Also eslint version was 7.32.0 and typescript-eslint/eslint-plugin was 4.33.0
Repository: rust
Issue: "error: module has missing stability attribute" is insufficiently explained
Labels: A-diagnostics,P-low,A-stability,T-compiler,D-confusing,D-terse,requires-internal-features,F-staged_api

Given the following code ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=85da69f8dd0b5507585ce5c0318bb195)):

```rust
#![feature(slice_from_ptr_range)]
#![feature(slice_ptr_get)]
#![feature(staged_api)]
#![feature(stmt_expr_attributes)]
#![feature(strict_provenance)]

fn foo() {}
fn bar() {}
```

The current output points to the _entire file_ and doesn't tell me what I did wrong:

```
error: module has missing stability attribute
 --> src/lib.rs:1:1
  |
1 | / #![feature(slice_from_ptr_range)]
2 | | #![feature(slice_ptr_get)]
3 | | #![feature(staged_api)]
4 | | #![feature(stmt_expr_attributes)]
... |
7 | | fn foo() {}
8 | | fn bar() {}
  | |___________^
```

If I understand the feature correctly, the output should be:

```
error: expected at least one pub item in this module to be marked as stable or unstable
note: expected because of `#![feature(staged_api)]` on line 3
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->