sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: File Explorer display page count for docs
Labels: Needs-Triage

### Description of the new feature / enhancement

All files in the file explorer that are of type pdf, doc, or any form where it consists of pages could have an additional coloum for displaying the number of pages in the file.

### Scenario when this would be used?

When you are deciding on printing a folder you can quickly add all the pages together to get the total pages in the folder

### Supporting information

_No response_
Repository: go
Issue: x/net/proxy: document returned Dialers implement ContextDialer
Labels: Documentation,NeedsInvestigation

Currently, if one tries to instantiate a socks5 dialer, one receives a response with the proxy.Dialer interface.  This interface only exposes the Dial() (context free) method.  This method is deprecated in many cases (i.e. http client transports).  DialContext() is actually implemented for all the proxies, but is only visible within the internal package, so is not actually usable by end users.

Motivated by https://github.com/golang/net/pull/164 but the comment there is that since that PR changes the proxy.Dialer interface it breaks backwards compatibility (which I assume is if external users use the interface, and not just limited to the proxy package) and therefore should go through the proposal process to determine what API changes should be.
Repository: rust
Issue: Confusing diagnostic when `impl IntoFuture` is passed to a function expecting `impl Future`
Labels: A-diagnostics,T-compiler,D-confusing

### Code

```Rust
use core::future::{IntoFuture, Future};
fn expect_future(_: impl Future) {}
fn test(into: impl IntoFuture) {
    expect_future(into)
}
```

([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=7a9528ffea58937dd45911b6c7f45dd4))

### Current output

```text
error[E0277]: `impl IntoFuture` is not a future
 --> src/lib.rs:4:19
  |
4 |     expect_future(into)
  |     ------------- ^^^^ `impl IntoFuture` is not a future
  |     |
  |     required by a bound introduced by this call
  |
  = note: impl IntoFuture must be a future or must implement `IntoFuture` to be awaited
note: required by a bound in `expect_future`
 --> src/lib.rs:2:26
  |
2 | fn expect_future(_: impl Future) {}
  |                          ^^^^^^ required by this bound in `expect_future`
help: consider further restricting this bound
  |
3 | fn test(into: impl IntoFuture + std::future::Future) {
  |                               +++++++++++++++++++++
```


### Desired output

```text
error[E0277]: `impl IntoFuture` is not a future
 --> src/lib.rs:4:19
  |
4 |     expect_future(into)
  |     ------------- ^^^^ `impl IntoFuture` is not a future
  |     |
  |     required by a bound introduced by this call
  |
note: required by a bound in `expect_future`
 --> src/lib.rs:2:26
  |
2 | fn expect_future(_: impl Future) {}
  |                          ^^^^^^ required by this bound in `expect_future`
help: consider calling `.into_future()`
  |
4 |     expect_future(into.into_future()) {
  |                       ++++++++++++++
```


### Rationale and extra context

The note provided by the compiler is very confusing:
```text
  = note: impl IntoFuture must be a future or must implement `IntoFuture` to be awaited
```
1. `impl IntoFuture` implements `IntoFuture`, so it looks like the error shouldn't happen
2. There is no `.await` in the code

Additionally the correct solution here (more likely than not) is to call `IntoFuture::into_future`, and not to add a bound, `impl IntoFuture + Future` is quite weird (all `Future`s are already `IntoFuture`...)
Repository: material-ui
Issue: [Tooltip] Tooltip as a child takes `onClick` props from parent by default
Labels: component: tooltip

### What's the problem? 🤔

When using MUI Tooltip as a child of an interactive element, it takes onClick props from parent by default. Is this a bug, or intended behaviour? There is a workaround where you can set `e.stopPropagation` to `componentProps`, but it would be better if it takes it as default prop.

### What are the requirements? ❓

_No response_

### What are our options? 💡

_No response_

### Proposed solution 🟢

_No response_

### Resources and benchmarks 🔗

_No response_
Repository: react
Issue: Feature request: Improved warning "Functions are not valid as a React child..."
Labels: Type: Feature Request

Good day. Every time when I bump into the following error
```
Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.
```
it takes me quite some time to locate the bad value in UI structure, even though there's a component trace in the console. What I think would improve by debugging experience if the error would also log the problematic value. This way I could know which value it is exactly in a single click in DevTools.
Repository: material-ui
Issue: Popper background color does not respect custom theme
Labels: discussion,component: Popper

### 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://github.com/cq-overlays/dashboard (I have a workaround in `overrides.css`)

Steps:

1. Create custom theme and overwrite the "grey" color with your own shades
```
export const theme = createTheme({
  palette: {
    mode: "dark",
    primary: {
      light: "#008585",
      main: "#00BEBE",
      dark: "#33cbcb",
      contrastText: "#fff",
    },
    secondary: {
      light: "#ab003c",
      main: "#f50057",
      dark: "#f73378",
      contrastText: "#fff",
    },
    grey: {
      50: "#626E84",
      100: "#232c3d",
      200: "#263042",
      300: "#293346",
      400: "#2c374b",
      500: "#2f3a4f",
      600: "#38445a",
      700: "#414d64",
      800: "#4a566e",
      900: "#525f78",
      A700: "#626E84",
      A400: "#707B8F",
      A200: "#7D8799",
      A100: "#8992A2",
      main: "#293346",
      dark: "#2c374b",
    },
  },
})
```

3. Create an Autocomplete component
4. Select the component so the popper appears


### Current behavior 😯

Currently, the popper has a background color of the default "grey", rather than the grey set in your custom theme:
![image](https://user-images.githubusercontent.com/47790183/217221884-da297963-cd8f-4ba5-898d-61f52ee4d345.png)

My custom grey theme is a very blue shade, but as you can see the background color is far more neutral. The custom primary color from my theme is inherited correctly.

### Expected behavior 🤔

The background color of this popper should be derived from the custom theme the same way the primary color is.

### Context 🔦

I'm attempting to create an autocomplete component, and I have a custom theme.

I would like to add that this is my first time making an issue on this repo so I apologize if I have missed a step. 
My first assumption was that the popper must have been portal'd outside of the ThemeProvider context, but the dark mode and primary color are inherited fine, so that must not be it.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

  System:
    OS: Linux 5.10 Ubuntu 20.04.5 LTS (Focal Fossa)
    Browser: Firefox
  Binaries:
    Node: 19.2.0 - ~/.nvm/versions/node/v19.2.0/bin/node
    Yarn: Not Found
    npm: 8.19.3 - ~/.nvm/versions/node/v19.2.0/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5 
    @emotion/styled: ^11.10.5 => 11.10.5 
    @mui/base:  5.0.0-alpha.116 
    @mui/core-downloads-tracker:  5.11.7 
    @mui/material: ^5.11.7 => 5.11.7 
    @mui/private-theming:  5.11.7 
    @mui/styled-engine:  5.11.0 
    @mui/system:  5.11.7 
    @mui/types:  7.2.3 
    @mui/utils:  5.11.7 
    @types/react: ^18.0.27 => 18.0.27 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^4.9.5 => 4.9.5 

</details>
Repository: deno
Issue: npm packages don't support git depedencies
Labels: node compat

Not even if you want specific version.

Logs say this:

```log
Could not set npm package requirements. npm package: @adiwajshing/baileys@5.0.0: error parsing version requirement for dependency: libsignal@git+https://github.com/adiwajshing/libsignal-node.git: Invalid npm version requirement 'git+https://github.com/adiwajshing/libsignal-node.git'.: Unexpected character.
  git+https://github.com/adiwajshing/libsignal-node.git
```

Deno verisons:
- `deno 1.28.2 (release, x86_64-pc-windows-msvc)`
- `deno 1.30.3 (release, x86_64-pc-windows-msvc)`
Repository: godot
Issue: Custom Shader classes not recognized by Shader resource creation dialog
Labels: bug,topic:editor,usability

### Godot version

4.0.beta17.official

### System information

macOS 13.1, Apple M1

### Issue description

Godot 3.5.1 supports the creation of custom classes extending `Shader`:

```gdscript
@tool
class_name CustomShader
extends Shader
```

When creating a new shader resource, these custom classes are given as an option:

![image](https://user-images.githubusercontent.com/1061/217240241-bc42409f-5cb9-4514-830a-338ab1f614e7.png)

When trying this in the **current Godot 4.0 beta** like this:

```gdscript
@tool
class_name CustomShader
extends Shader
```

The new Create Shader dialog window does not offer this class as a shader type to be created:

![image](https://user-images.githubusercontent.com/1061/217240432-adf79790-96af-4ff0-b136-46649c8a37ae.png)


### Steps to reproduce

1. Create a custom shader class like above
2. Create a Shader Material
3. Try to create a Shader resource for the material

### Minimal reproduction project

[MRP-Custom-Shader-Class.zip](https://github.com/godotengine/godot/files/10674852/MRP-Custom-Shader-Class.zip)
Repository: vscode
Issue: Being able to multiselect files to fix them in one shot
Labels: feature-request,error-list

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
In my code base, I've got the same issue on different files, I'd like to be able to select them in `Problems` tab and click on `fix` to fix them all.

https://user-images.githubusercontent.com/655838/217244878-37bcf3c5-f396-4af8-96f9-b95964436686.mp4

For the moment it's possible to select them all but when you apply the fix, it does it only on one file.
Repository: godot
Issue: VisibleOnScreenNotifier2D calls screen_exited() after RigidBody2D position has moved back on screen
Labels: topic:core,topic:physics,needs testing

### Godot version

4.0 Beta 17

### System information

Windows 10

### Issue description

Hi,

What I want to do:

When a Rigidbody2D exits the screen, reset it to its start position.

What I did:
- Created a RigidBody2D node
- Bound Key 1 to set sleeping to false, key 2 to set sleeping to true
- Added a CollisionShape2D, Sprite and VisibleOnScreenNotifier2D 
- When the RB falls off the screen, it calls screen_exited() and a flag _reset_me is set to true.
- in _integrate_forces(), if the _reset_me flag is true, put the RB to sleep, change the position, set _reset_me to false

What happens:
- when the RB first exits the screen, the screen_exited() is called and the RB is reset, sleeping now true
- when deactivating sleep, the screen_exited() is immediately called, even though the RB is now on the screen

Here is the RB script:

```
extends RigidBody2D

@onready var visible_on_screen_notifier_2d = $VisibleOnScreenNotifier2D
@onready var label = $Label


var _start: Vector2 = Vector2.ZERO
var _reset_me = false


func _ready():
	_start = global_position


func _process(delta):
	if Input.is_physical_key_pressed(KEY_1):
		sleeping = false
	if Input.is_physical_key_pressed(KEY_2):
		sleeping = true
		
	label.text = str(sleeping)


func _integrate_forces(state):
	if _reset_me == true:
		global_position = _start
		sleeping = true
		_reset_me = false


func _on_visible_on_screen_notifier_2d_screen_exited():
	print("_on_visible_on_screen_notifier_2d_screen_exited")
	if _reset_me == false:
		_reset_me = true

```


I have also attached a minimal project.

Note: If I use freeze mode, the same happens.

### Steps to reproduce

- Run the attached project.
- The RB will fall and reset.
- Now press 1 to remove sleeping
- The screen_exited() is called immediately and the RB will reset


I hope I have not wasted anyone's time here.


### Minimal reproduction project

[Notifier.zip](https://github.com/godotengine/godot/files/10675064/Notifier.zip)
Repository: material-ui
Issue: Removing a css property from the theme (override) without impacting another
Labels: component: card,enhancement,customization: css

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: [codesandbox](https://codesandbox.io/s/mutable-surf-yxw3zu?file=/src/App.tsx)

Steps:

1. Use the `ThemeProvider` with the default theme
2. Try to remove the `MuiCardContent-root:last-child` style (`padding-bottom`)
3. It impacts the default `MuiCardContent-root` style (`padding`)

![image](https://user-images.githubusercontent.com/30229752/217248250-b2030e9e-85a5-40a2-a571-db162f4ccc80.png)



### Current behavior 😯

Currently, when I try to remove the `padding-bottom` from `MuiCardContent-root:last-child` it impacts the `padding` of `MuiCardContent-root`. I can't find out a way to remove this css property without overriding the default `padding` value.

### Expected behavior 🤔

We should be able to opt-out from a theme's css property, without impacting other css properties.

In this particular case I would expect the default `padding` to be kept intact:  

```css
.MuiCardContent-root {
    padding: 16px;
    padding-top: 16px;
    padding-right: 16px;
    padding-bottom: 16px; /* should be intact */
    padding-left: 16px;
}
```

### Context 🔦

I'm trying to remove the `padding-bottom: 24px` from the `CardContext` component (`&last-child`).

The problem is that it impacts the default `padding: 16px`. When trying to unset the `padding-bottom` it removes the default `padding`.

### Your environment 🌎

Latest.
Repository: excalidraw
Issue: changing color during text creation on mobile doesn't work
Labels: bug,mobile

Steps:

1. start creating text, do not confirm yet
2. click on color picker
3. it exits the wysiwyg

related https://github.com/excalidraw/excalidraw/issues/4464 https://github.com/excalidraw/excalidraw/issues/4863
Repository: PowerToys
Issue: Start or stop docker container from PT Run
Labels: Needs-Triage

### Description of the new feature / enhancement

Similar to other plugin for PT Run, there should be a plugin that starts or stops a container directly from the window. 

### Scenario when this would be used?

Docker is becoming more and more common during development and in the system administration, being able to quickly start, stop and restart a docker container would really help improve the productivity of both devs and sys admins. 

### Supporting information

_No response_
Repository: next.js
Issue: Using template.js in a route group does not override previous template.js
Labels: bug

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101
    Binaries:
      Node: 18.13.0
      npm: 8.19.3
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.1.6
      eslint-config-next: 13.1.6
      react: 18.2.0
      react-dom: 18.2.0

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

_No response_

### Link to the code that reproduces this issue

https://github.com/yelshall/turingame

### To Reproduce

Have a file structure that looks like this:
```
/app
│   layout.js
│   template.js
│
└───(routegroup)
│   │   layout.js
│   │   template.js
│   │
│   └───subfolder1
```

### Describe the Bug

When accessing a page within the route group, it uses the `layout.js` within that route group, as the docs explained how to create multiple root layouts. However, it renders both `/app/template.js` and `/app/(routegroup)/template.js`.

### Expected Behavior

I believe that using a `template.js` within a route group should only render that `template.js`.

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

_No response_

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

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Allow sending to img2img without 'settings' (steps, width, height)
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 ?

When sending to other sections, ie img2img/extras, some settings are carried over (notably, steps, height and weight).

Sometimes this is tedious when you have say SD upscale settings set up.

### Proposed workflow

Allow one to CTRL + click to NOT send these settings.

### Additional information

_No response_
Repository: PowerToys
Issue: "Hold Shift to activate zones while dragging" can be used to toggle enabled state on each drag window action
Labels: Needs-Triage

### Description of the new feature / enhancement

The version of FancyZones I had in my old, now defunct PC worked differently than the newer version I installed on my new one.
Zones didn't show by default when dragging a window, and only showed when I right clicked.

It took me an embarrasing amount of time to figure out that to get the old behaviour I had to toggle on the "Hold Shift to activate zones while dragging".

IMHO it would be much clearer to have this be a separate toggle, to let the user decide on which state the zones should be in on each drag window action?
Maybe even a third option to remember the state between drag window actions?

### Scenario when this would be used?

My workflow deals with many, many small windows on a daily basis.
I only need VS Code, Edge and Slack to live in the zones, and so I rarely need to have FancyZones on.

My desired behaviour can be set by toggling an option that (for me!) is not intuitive enough.
Having the proposed toggle could make FancyZones more user friendly.

### Supporting information

_No response_
Repository: next.js
Issue: [arm64][appDir] generateBuildId does't work properly; nextjs build doesn't generate same chunk hash for main-app-[hash].js
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information
MacBook Pro 2021 Apple M1 Max (macOS Ventura 13.2 (22D49))

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Thu Jan  5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.1.7-canary.6
      eslint-config-next: 13.1.6
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

this example works perfect in cloud (x64) but if download and run locally (arm64) works wrong (see video and screenshot)
example: https://stackblitz.com/edit/vercel-next-js-2m8zyx
video: https://drive.google.com/file/d/1g_np1lkYjezVHlHDiByGSiRKu5E8URNq/view?usp=sharing
<img src="https://i.ibb.co/LRmwDBL/Screenshot-2023-02-07-at-17-23-54.png">

### To Reproduce

1. setup nextjs app
`npx create-next-app@latest --experimental-app`
2. add generateBuildId
https://nextjs.org/docs/api-reference/next.config.js/configuring-the-build-id
3. build
`yarn build`
4. open .next/static/chunks/main-app-[hash1].js
5. remove .next folder
`rm -rf .next`
6. rebuild
`yarn build`
7. open .next/static/chunks/main-app-[hash2].js
8. ensure that hash1 not equal hash2


### Describe the Bug

generateBuildId does't work properly;
nextjs build doesn't generate same chunk hash for main-app-[hash].js on rebuilds if nothing changed.
reproduced only on arm64.

### Expected Behavior

hash for main-app-[hash].js chunk keep the same on rebuilds if nothing changed.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: material-ui
Issue: [CSP] Blocks data-emotion inline styles
Labels: external dependency,package: system

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. use create-react-app with mui v5
2. set the following csp header inside public/index.html
```html
<meta http-equiv="Content-Security-Policy" content="default-src 'self'">
```
3. set the .env as follows:
```
INLINE_RUNTIME_CHUNK=false
IMAGE_INLINE_SIZE_LIMIT=0
```
4. my app root looks like this:

```jsx
<ThemeProvider theme={theme}>
  <IntlProvider locale={currentLanguage} messages={messages[currentLanguage]}>
    <CssBaseline />
    <BrowserRouter>
      <Routes>
        <Route path="/" element={<Layout />}>
            {...}
        </Route>
      </Routes>
    </BrowserRouter>
  </IntlProvider>
</ThemeProvider>
``` 
5. build or start the app

### Current behavior 😯

I dont know why, but I keep getting these empty inline "data-emotion" style tags ..

![image](https://user-images.githubusercontent.com/48263634/217274836-eb5bb136-3cf1-4e47-b0a1-3c8fb75b378c.png)

![image](https://user-images.githubusercontent.com/48263634/217274862-a587fff5-8903-42b2-954a-39913fdc90ab.png)

setting the style-src directive as "style-src 'self' 'sha256-2NO5...' 'sha256-47DE...';" with the full hashes from the emotion library works. but i dont wanna bind the csp header to this settings. i reckon the hashes change with future mui versions.

### Expected behavior 🤔

no data-emotion inline style tags

### Context 🔦

I dont use server-side-rendering. 
I upload the build output files directly to my aws cloudfront instance.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: Windows 10 10.0.22621
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.18.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22621.1105.0), Chromium (108.0.1462.76)
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5 
    @emotion/styled: ^11.10.5 => 11.10.5 
    @mui/base:  5.0.0-alpha.109 
    @mui/core-downloads-tracker:  5.10.17 
    @mui/icons-material: ^5.11.0 => 5.11.0 
    @mui/material: ^5.10.17 => 5.10.17 
    @mui/private-theming:  5.10.16 
    @mui/styled-engine:  5.10.16 
    @mui/system:  5.10.17 
    @mui/types:  7.2.2 
    @mui/utils:  5.10.16 
    @types/react: ^18.0.24 => 18.0.26 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^4.6.4 => 4.9.4 
```
</details>

using chrome and edge