sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: CONTENT_SCALE_MODE_DISABLED?
Labels: discussion,topic:rendering,needs testing

### Godot version

v4.0.stable.official [92bee43ad]

### System information

window10 64bit

### Issue description

1. I Config my ProjectSettings like this:
![image](https://user-images.githubusercontent.com/35988767/224999583-a85c0cb0-4102-4d24-ae8d-b9ab910fd2f4.png)

2. I Create a Cotrol Scene and coding like this:
![111](https://user-images.githubusercontent.com/35988767/225001041-687506f2-83d9-44ff-9812-f23702792162.gif)
All work OK !

3. Then I Create a ConfirmDialog Scene and coding like this:
![2222](https://user-images.githubusercontent.com/35988767/225001437-d9220697-821f-493e-b0de-7ebd2b211549.gif)

And it not work.

### Steps to reproduce

/

### Minimal reproduction project
[ScaleTest.zip](https://github.com/godotengine/godot/files/10968565/ScaleTest.zip)
Repository: ant-design
Issue: The autoFocus property doesn't work for the Input component inside the Modal 
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/gracious-ully-x3b7y1)

### Steps to reproduce

Open the modal and you see the input field is not focused 

### What is expected?

The input field should be focused

### What is actually happening?

The input field is not focused

| Environment | Info |
| --- | --- |
| antd | 4.24.0 |
| React | react |
| System | N/A |
| Browser | Google Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Many padding Module fail memory_format tests
Labels: module: nn,triaged,module: memory format,actionable,module: intel

See https://github.com/pytorch/pytorch/pull/96641 that added these skips.
We should investigate why this happens and most likely fix them.

cc @ezyang @gchanan @zou3519 @mruberry @jbschlosser @walterddr @mikaylagawarecki @jamesr66a @frank-wei @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @saketh-are
Repository: rust
Issue: add bootstrap tests for detecting src and out
Labels: T-bootstrap

I was thinking about the following cases when I wrote the comment in #109055

1. Running bootstrap from the source root.
2. Running from a subdirectory of the source root.
3. Running from outside the source root.
4. Running on a different machine from where bootstrap was compiled (which will be important for #107812). You can mostly replicate this by renaming the source root so it no longer exists on disk.
5. Running with `--build-dir`.
6. Running with `$RUST_BOOTSTRAP_CONFIG` set in the environment and `build-dir` set in the file.

_Originally posted by @jyn514 in https://github.com/rust-lang/rust/issues/109055#issuecomment-1467088488_
Repository: rust
Issue: rustdoc: Add option to hide imports from rendered examples
Labels: T-rustdoc,C-feature-request

### Problem

Adding imports to code examples are necessary to make them compile however it makes code examples more hard to read. That's why many developers choose to hide them from the generated output. This leads to the problem that when copying code examples users have to manually choose the correct imports which can be error-prone.

### Proposed Solution

Add an UI option to each Rust code block that allows to dynamically hide and show the imports.

### Notes

This may raise the question if we also want an option to show/hide all hidden code fragments.
Repository: go
Issue: x/net/ipv4: TestPacketConnReadWriteMulticastICMP failures with `destination unreachable`
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/net/ipv4" && test == "TestPacketConnReadWriteMulticastICMP" && `got type=destination unreachable`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/831f306aeab5ed74bc18ca5497dad15bd7669758)):

    --- FAIL: TestPacketConnReadWriteMulticastICMP (2.19s)
        --- FAIL: TestPacketConnReadWriteMulticastICMP/grp=224.0.0.254/src=<nil> (0.00s)
            multicast_test.go:247: got type=destination unreachable, code=3; want type=echo reply, code=0


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: storybook
Issue: [Bug]: Inconsistent margins on headings
Labels: bug,ui

### Describe the bug

The `margin-top` and `padding-top` are set to `0` on headings using the pseudo-class `:first-of-type`

This causes inconsistent spacing between elements:

![image](https://user-images.githubusercontent.com/6906782/225036711-256ab03d-2aad-4999-8fea-ce4695a95f03.png)


### To Reproduce

Make an MDX file containing the following

```
# H1

## H2

### H3

#### H4

### H3

#### H4
```

### System

```shell
System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz
  Binaries:
    Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.3.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1023.0), Chromium (110.0.1587.69)
  npmPackages:
    @storybook/addon-a11y: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/addon-docs: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/addon-essentials: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/addon-links: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/cli: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/client-api: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/preview-web: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/react: ^7.0.0-rc.3 => 7.0.0-rc.3
    @storybook/react-vite: ^7.0.0-rc.3 => 7.0.0-rc.3
```


### Additional context

_No response_
Repository: deno
Issue: Supporting transitive mappings for npm: specifiers
Labels: suggestion,node compat

I was just running some tests to see if I can map transitive dependencies with Deno `npm:` specifiers along the lines of:

```json
{
  "imports": {
    "react": "npm:react@18.2.0"
  },
  "scopes": {
    "npm:react@18.2.0": {
      "loose-envify": "npm:loose-envify@1.2.3"
    }
  }
}
```

Where there is an import of `import 'react'` against the above import map in Deno.

Supporting the scoped `npm:react@18.2.0` in the above would be great for extending import maps support to npm specifiers without treating the version resolution as a fully opaque process. It would also make it easier to switch from Deno npm packages to eg JSPM versions of packages for moving from a browser to server workflow.

Has this been discussed at all, or are there any particular hurdles to achieving this kind of support, would be really interested to hear opinions!

//cc @dsherret
Repository: stable-diffusion-webui
Issue: [Bug]: Update made Realesrgan 4x slower?
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 not sure exactly what's wrong, I nuked my venv, pulled the latest and tried to upscale with Realesrgan as I usually do, only now the tile progress is like 10x slower

Did anyone experience this?

### Steps to reproduce the problem

Upscale anything with RealEsrgan 4X


### What should have happened?

Work as expected

### Commit where the problem happens

latest

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

Windows

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

Microsoft Edge

### Command Line Arguments

```Shell
xformers api
```


### List of extensions

controlnet

### Console logs

```Shell
Tile 52/240
        Tile 53/240
        Tile 54/240
        Tile 55/240
        Tile 56/240
        Tile 57/240
        Tile 58/240
        Tile 59/240
        Tile 60/240
        Tile 61/240
        Tile 62/240
        Tile 63/240
        Tile 64/240
        Tile 65/240
        Tile 66/240
        Tile 67/240
        Tile 68/240
        Tile 69/240
        Tile 70/240
        Tile 71/240
```


### Additional information

_No response_
Repository: rust
Issue: Broken link to incoherent impl
Labels: T-rustdoc,E-hard,C-bug

On this page https://doc.rust-lang.org/nightly/core/primitive.slice.html#method.binary_search_by_key (core, not std) there is a broken link [`sort_by_key`] -> `slice::sort_by_key` (interpreted as protocol "slice"). This seems to happen because `sort_by_key` is defined as an incoherent impl in alloc.

![screenshot of link](https://user-images.githubusercontent.com/26522220/225052644-9687db28-62a3-47e9-9af0-634f00475316.png)

I found this when running a link checker for a no-std project with a type with `Deref<Target = [T]>`.
Repository: godot
Issue: Exporting a tscn to gltf fails gltf validation
Labels: bug,topic:3d,topic:export

### Godot version

4.0.1 preview, doubles?

### System information

Windows 11, Nvidia 3000

### Issue description

Export this packed scene as a gltf. The gltf fails blender import.



### Steps to reproduce

1. Open PackedScene
2. Export as gltf 
3. Fails gltf validation

[cat_fire_floof_dance.zip](https://github.com/godotengine/godot/files/10970945/cat_fire_floof_dance.zip)

[glTF Validator.zip](https://github.com/godotengine/godot/files/10970957/glTF.Validator.zip)

### Minimal reproduction project

[v-sekai-game.zip](https://github.com/godotengine/godot/files/10971008/v-sekai-game.zip)
Repository: vscode
Issue: Toggle cell toolbar position does nothing if toolbar is currently hidden
Labels: bug,notebook-celltoolbar

1. Have notebook cell toolbar hidden
1. Right click on a notebook cell
2. Select Toggle cell toolbar position
3. :bug: nothing happens

I'd expect a quickpick to show the 3 possible settings (left/right/hidden) similar to the global workbench configure layout action.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Clip adjusting all appropriate settings 
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 ?

A handful of models require clip 2 set to get them to work properly when you set clip 2 the following changes occur: 

22 settings changed: ldsr_steps, ldsr_cached, SWIN_tile, SWIN_tile_overlap, CLIP_stop_at_last_layers, sd_lora, lora_apply_to_outputs, control_net_model_config, control_net_model_adapter_config, control_net_detectedmap_dir, control_net_models_path, control_net_max_models_num, control_net_model_cache_size, control_net_control_transfer, control_net_no_detectmap, control_net_detectmap_autosaving, control_net_only_midctrl_hires, control_net_allow_script_control, control_net_skip_img2img_processing, control_net_monocular_depth_optim, control_net_only_mid_control, control_net_cfg_based_guidance.


When you change the settings back to clip 1 the following changes occur: 

1 settings changed: CLIP_stop_at_last_layers.


This results in a DRASTICALLY lower quality of generations once you switch back to clip 1. Possibly even a worse quality at clip 2 due to the initial 22 settings being changed.  

### Proposed workflow

1. Cache the settings as a default for clip 1 
2. When switching to clip 2 change everything the same way it does
3. When switching back to clip 1 restore the default settings cached 


### Additional information

_No response_
Repository: go
Issue: net/http: TestTransportDialTLSContext flakes in local testing
Labels: NeedsFix

```
% go test -c net/http
% stress ./http.test -test.count=10 -test.run=TestTransportDialTLSContext
254 runs so far, 0 failures
572 runs so far, 0 failures
860 runs so far, 0 failures
1163 runs so far, 0 failures
1460 runs so far, 0 failures
1737 runs so far, 0 failures

/var/folders/pm/qx0jkz117r1cvc05kf31fhh8000n9d/T/go-stress173291610
--- FAIL: TestTransportDialTLSContext (25.91s)
    --- FAIL: TestTransportDialTLSContext/h2 (25.91s)
        transport_test.go:3821: Get "https://127.0.0.1:59866": dial tcp 127.0.0.1:59866: connect: operation timed out
FAIL


ERROR: exit status 1

2026 runs so far, 1 failures
2320 runs so far, 1 failures
2615 runs so far, 1 failures
2915 runs so far, 1 failures
3212 runs so far, 1 failures

/var/folders/pm/qx0jkz117r1cvc05kf31fhh8000n9d/T/go-stress896441329
--- FAIL: TestTransportDialTLSContext (25.92s)
    --- FAIL: TestTransportDialTLSContext/https1 (25.91s)
        transport_test.go:3821: Get "https://127.0.0.1:59866": dial tcp 127.0.0.1:59866: connect: operation timed out
FAIL


ERROR: exit status 1

3512 runs so far, 2 failures
3804 runs so far, 2 failures
```

I see a similar failure during all.bash from time to time, but stress is an easier way to reproduce it.

/cc @neild
Repository: next.js
Issue: `next/image` cannot use edge API routes
Labels: bug

### 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.3.0: Thu Jan  5 20:49:43 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.17
      pnpm: 7.5.2
    Relevant packages:
      next: 13.2.5-canary.3
      eslint-config-next: 13.0.6
      react: 18.2.0
      react-dom: 18.2.0
```


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

Image optimization (next/image, next/legacy/image), Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/edge-image-api-route-qtxuv9?welcome=true&file=%2Fpages%2Findex.tsx

### To Reproduce

1. Create an API route using the edge runtime, that returns an image.
2. Use that API route in the `next/image` component.

### Describe the Bug

The `next/image` component is unable to use the image with the default loader. The error produced is this:
`upstream image response failed for /api/image?url=https://picsum.photos/3000/2000 TypeError: str.split is not a function or its return value is not iterable`

As far as I can tell, the headers being passed into [`parseCacheControl`](https://github.com/vercel/next.js/blob/canary/packages/next/src/server/image-optimizer.ts#L367) are a `string[]` rather than `string`, which is causing the issue.

### Expected Behavior

The loader parses the `cache-control` header correctly, and loads the image.

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

_No response_

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

_No response_
Repository: next.js
Issue: [NEXT-856] Error Overlay does not display the current version of Next.js
Labels: good first issue,bug,linear: next,resolved

### 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 10 Pro
    Binaries:
      Node: 16.19.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.5-canary.3
      eslint-config-next: 13.2.4
      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/osulli/nextjs-error-overylay-repro

### To Reproduce

- Run `npm run dev`
- Click the `throw error` button

### Describe the Bug

I do not seemingly benefit from any of the latest features e.g. the Next.js version being displayed

<img width="727" alt="image" src="https://user-images.githubusercontent.com/46930728/225087218-9c55ad08-1238-429c-ba76-55135a104f90.png">


### Expected Behavior

I see the latest features on the error-overlay e.g. the Next.js version being displayed

![image](https://user-images.githubusercontent.com/46930728/225087531-db6d59c7-a388-4d90-b30a-dd68d201b8d0.png)
https://nextjs.org/blog/next-13-2#improved-error-overlay

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

Chrome Version 111.0.5563.65 (Official Build) (64-bit)

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

npm run dev

<sub>[NEXT-856](https://linear.app/vercel/issue/NEXT-856/error-overlay-does-not-display-the-current-version-of-nextjs)</sub>
Repository: scrcpy
Issue: Automatically stop recording when the screen auto-locks?
Labels: feature request

Is there a feature where the screen recording stop automatically when the phone gets locked due to the auto-lock setting? If not then I would really appreciate such feature. 

Maybe keep the stop as default and add a flag like `--turnoff-autolock` or something similar where it doesn't stop recording even when it gets locked? Either would do really.

I am on Arch Linux and I have OnePlus Nord 2 5G which uses stock android 11.

Btw the new 2.0 release has been really amazing with the audio especially. Love this app a lot and I use it daily.
Repository: go
Issue: net/http: idle timeout added in CL 121419 is undocumented and surprising
Labels: NeedsInvestigation

[CL 121419](https://go.dev/cl/121419) changed `net/http.Server` to treat new connections as idle after 5 seconds, in order to unblock `Shutdown` with stalled connections (see #22682). That behavior has a regression test, but I find it surprising and I don't see it mentioned in the `net/http` documentation _at all_.

I would intuitively expect one of two other behaviors:
1. `closeIdleConns` could use the configured `ReadHeaderTimeout` for this purpose, as suggested in https://github.com/golang/go/issues/22682#issuecomment-346208009.
2. A call to `Shutdown` could instead cause `closeIdleConns` to close *all* connections in `StateNew`, regardless of how long they have been in that state.

(attn @neild; CC @bradfitz @tombergan)
Repository: godot
Issue: [Editor] [Linux] Some subwindows do not auto-focus
Labels: bug,topic:editor,usability

### Godot version

4.0-mono

### System information

Linux 6.2.2, Gnome 43 (Wayland), Radeon RX 6700 (Mesa: 22.3.6), Vulkan

### Issue description

When some subwindows appear, they do not properly grab focus resulting which results in user having to move mouse to the window to be able to type with a keyboard. 

Affected subwindows:
* Everything under context menu in FileSystem (**New Folder**, **New Scene**, etc.)
* "**Add New Node**" under context menu Scene

There are also subwindows which **do** properly grab focus:
* Create New Project window in Project Manager
* "Add Metadata" under Inspector > Node

### Steps to reproduce

1. Start godot **without** _--single-window_ argument
1. Create a new project, _notice that you don't have to move your mouse to start typing the project name_
1. Move mouse under File System panel
1. Right click and select "New Folder"
1. Notice that you have to move mouse cursor to the new window to start typing

### Minimal reproduction project

N/A
Repository: rust
Issue: run-make with target wasm32-unknown-unknown has hard-to-diagnose errors
Labels: A-testsuite,C-enhancement,T-bootstrap

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```toml
# config.toml

[build]
target = ["x86_64-unknown-linux-gnu","wasm32-unknown-unknown"]
```

Bootstrap invocation:
```shell
% python x.py build    --stage 1   library/std  && python x.py test    --stage 1    tests/run-make
```

I expected to see this happen: the test suite runs and gives me successes or failures relevant to my Rust project source, or gives me diagnostics that tell me about unsatisified dependencies.

Instead, this happened: Mysterious run-make test failures like "rust-lld not found" or "foo.js not found"

----

Each of the failures are easy to work around.

E.g. rust-lld can be satisfied by adding:

```
[rust]
lld = true
```

to the `config.toml`.

And the `foo.js not found` problem is addressed by setting:

```toml
[build]
nodejs = "node"
```

(and ensuring that node is indeed installed).

(The latter is hard to understand without looking at the `Makefile`s in question; it originates because the `Makefile` is blindly using `$(NODE)` as the first element in a shell command, and if `$(NODE)` expands to an empty string or whitespace, then the *next* argument is interpreted as the program for the shell to execute. Thus, `foo.js not found` (as a program to run).)

----

So, workarounds exists, but the overall experience is pretty bad in terms of running the `run-make` tests. This is perhaps to be expected given that [wasm is a tier-2 target](https://doc.rust-lang.org/nightly/rustc/platform-support.html#tier-2). It might be worth considering adding a prerequisite to the relevant wasm run-make tests that does a trivial dummy run of the basics, and if it fails, spits out an error telling the developer what changes they should make if they want to do `run-make` tests with this target enabled.
Repository: godot
Issue: `Resource.duplicate(true)` doesn't duplicate subresources stored in Array or Dictionary properties
Labels: bug,discussion,topic:core,confirmed,documentation

___

***Bugsquad note:** This issue has been confirmed several times already. No need to confirm it further.*

___

### Godot version

4.0.stable

### System information

Manjaro Linux

### Issue description

This behavior is poorly documented, and it breaks expectations. It is mentioned in the docs only under `Array.duplicate()`, but not `Dictionary` class, or `Resource.duplicate()`.

This affects also "Make Unique" and "Make Unique (Recursive)" for custom resources.

Here's the problematic code:
https://github.com/godotengine/godot/blob/fc7adaab7b3856a7831d402ea2bbb27efe7b7d8a/core/variant/variant_setget.cpp#L1889-L1900

The "breaks stuff :(" comment in the code was left in 2018 (d280b14e6e7b686d4e1d873e6b1ac14754404075).


### Steps to reproduce

For simple code see reproduction project.

To reproduce on your own:
1) Have a resource with a property of type Array[SomeOtherResource]
2) One of the following:
2a) "Make Unique" on parent resource in inspector.
2b) Or duplicate(true) from code.
3) Check if SomeOtherResource items inside array are unique.


### Minimal reproduction project

[res_bug_reproduction.zip](https://github.com/godotengine/godot/files/10972464/res_bug_reproduction.zip)
Repository: go
Issue: net/http: HTTP/2 server sometimes accepts a new request after OnShutdown hook is called
Labels: NeedsInvestigation

When I modified `net/http.TestServerShutdown` to make a call to `Get` in the handler after the hook passed to `RegisterOnShutdown` was called, it passed reliably on my workstation but failed on the `windows-amd64-2016` builder:

https://storage.googleapis.com/go-build-log/8141c27e/windows-amd64-2016_0b21b774.log:
```
--- FAIL: TestServerShutdown (0.00s)
    --- FAIL: TestServerShutdown/h2 (1.12s)
        serve_test.go:5478: https://127.0.0.1:51794: unexpected success. Listener should be closed before OnShutdown is called.
FAIL
FAIL	net/http	4.111s
```

That suggests that an HTTP/2 server (at least on Windows) may accept a completely new request after it has already called the `OnShutdown` hook. Even given HTTP/2's stream multiplexing, that behavior is surprising.

See previously #39776, 

(attn @neild)