sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]: Handle removed model files gracefully when returning from making X/Y plots
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?

If for some reason webui tries to load a checkpoint that doesn't exist on the disk any longer, it can lead to at least the generation of X/Y plots failing.

### Steps to reproduce the problem

I was doing an X/Y plot with Checkpoint name as the Y type, and after image generation was completed, the webui tried to go "back" to the checkpoint in the top bar which didn't exist any longer. The X/Y plot was never generated because of running into this error.

### What should have happened?

I get an X/Y plot on the screen instead of running into a total failure for that whole reason I'm running that script. Loading that top bar's checkpoint was kind of useless in this case since I was comparing checkpoints, but use cases when loading a model is a waste of time and resources has been already reported in another issue; this is just another one of those.

### Commit where the problem happens

fd4461d44c7256d56889f5b5ed9fb660a859172f

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

_No response_

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

_No response_

### Command Line Arguments

_No response_

### Additional information, context and logs

FileNotFoundError: [Errno 2] No such file or directory:

```
The file may be malicious, so the program is not going to read it.
You can skip this check with --disable-safe-unpickle commandline argument.


Error completing request

Traceback (most recent call last):
  File "modules/call_queue.py", line 45, in f
    res = list(func(*args, **kwargs))
  File "modules/call_queue.py", line 28, in f
    res = func(*args, **kwargs)
  File "modules/txt2img.py", line 46, in txt2img
    processed = modules.scripts.scripts_txt2img.run(p, *args)
  File "modules/scripts.py", line 328, in run
    processed = script.run(p, *script_args)
  File "scripts/xy_grid.py", line 415, in run
    with SharedSettingsStackHelper():
  File "scripts/xy_grid.py", line 274, in __exit__
    modules.sd_models.reload_model_weights(self.model)
  File "modules/sd_models.py", line 359, in reload_model_weights
    load_model_weights(sd_model, checkpoint_info)
  File "modules/sd_models.py", line 196, in load_model_weights
    sd = read_state_dict(checkpoint_file)
  File "modules/sd_models.py", line 178, in read_state_dict
    sd = get_state_dict_from_checkpoint(pl_sd)
  File "modules/sd_models.py", line 152, in get_state_dict_from_checkpoint
    pl_sd = pl_sd.pop("state_dict", pl_sd)
AttributeError: 'NoneType' object has no attribute 'pop'
```
Repository: stable-diffusion-webui
Issue: [Bug]: (Macos) The default name still shows up even if I use custom names.
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?

![Screenshot 2023-01-02 at 4 55 19 PM](https://user-images.githubusercontent.com/121373688/210280517-86f5ce7e-799f-4d83-a21e-06890c361a99.jpg)
![Screenshot 2023-01-02 at 4 55 07 PM](https://user-images.githubusercontent.com/121373688/210280519-f4e203bc-4db7-4b55-8399-14b741dd5e61.jpg)

The default name is on a wrong time and it never disappear even if I use custom name. I used [seed]-[model_hash]-[sampler] and yet the time starts at the beginning which isn't even a right time. 

### Steps to reproduce the problem

1. go to setting.
2. check custom naming.

### What should have happened?

The default name which is time shouldn't show up and the default time is on a different date and hours.



### Commit where the problem happens

Setting

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

MacOS

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

Apple Safari

### Command Line Arguments

_No response_

### Additional information, context and logs

_No response_
Repository: ant-design
Issue: 建議讓 showToday 能自動適應 picker 類型
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

1. 建議讓 showToday 能自動適應 picker 類型

例如當 picker = month 時轉變為 本月

2. 或者新增 showToday={ day?: boolean, week?: boolean, month?: boolean, year?: boolean } 形式的設定值

### What does the proposed API look like?

showToday={ day?: boolean, week?: boolean, month?: boolean, year?: boolean }

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: material-ui
Issue: [docs] Please update autocomplete docs to give current workaround for suppressing autocomplete on Chrome browser
Labels: docs,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Related page

https://mui.com/material-ui/react-autocomplete/#autocomplete-autofill

### Kind of issue

Other

### Issue description

I was looking for a way to suppress chrome autofill in an autocomplete field  and it appears that as of January 2023 none of the recommendations documented work for my case.  

The only solution that worked for me is adding a zero width joiner character to the middle of the field label as described on this page:

https://stackoverflow.com/a/70031071/267332

Might save a dev some time if that's on the docs page.

### Context 🔦

_No response_
Repository: godot
Issue: Default `enum` value on exported variable is not written to scene file
Labels: discussion,topic:core

### Godot version

v3.5.1.stable.official [6fed1ffa3]

### System information

Windows 11, 22H2

### Issue description

When exporting variables in a scene from GDScript specifiying an `enum` type, the set values are stored to the scene file - all but if the default is set.

This is confusing, as I would like to explicitly write all the values to the scene file.
To make matters worse, if you manually add the value to the scene file, the Godot Editor will remove it once you open the scene the next time.

![image](https://user-images.githubusercontent.com/29922/210282469-03f20980-c144-4bc2-b181-8f7198abdeaf.png)


### Steps to reproduce

* Create a node
* Export a variable with an enum type hint
* set it to the default value in the scene
* The value **will not** be written to the scene file

* Create a node
* Export a variable with an enum type hint
* set it to a value **other* than the default in the scene
* The value **will** be written to the scene file

### Minimal reproduction project

[repro-default-enum-value-export.zip](https://github.com/godotengine/godot/files/10333656/repro-default-enum-value-export.zip)
Repository: deno
Issue: Support for SvelteKit
Labels: node compat

Prompted by discussion on Discord I tried to get SvelteKit working in Deno.

After an hour of debugging I found the main blocker: by default SvelteKit installed Node adapter, which does a bit of setup that is not needed in Deno and makes the project crash, namely:
https://github.com/sveltejs/kit/blob/e7bc0be2b25aff5ac151e3d83b771ad80cac1ab8/packages/kit/src/exports/node/polyfills.js#L6-L28
which installs polyfills from `undici` for various Web APIs like `fetch` or `Response`. These objects work slightly differently in Deno and arguably installing them in Deno is not needed. 

I think the way forward would be to get a Deno dedicated adapter that would essentially be a noop as there's no need to change anything to make SvelteKit work.

Of course it would be very nice if `deno run -A npm:create-svelte@latest` would set up a project in a way that requires no changes (namely making specifiers use `npm:` prefixes).
Repository: stable-diffusion-webui
Issue: [Bug]: In img2img inpaint, the width and height sliders automatically change
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?

In img2img inpaint, the width and height sliders automatically change when you click on "Send to Inpaint" from under the generated image (which is usually scaled x2.) Having to manually adjust it back every time is SO frustrating! In the settings, I cannot find any way to stop this.

### Steps to reproduce the problem

1. Import an image to img2img inpaint.
2. Set width and height, and check Hires. fix.
3. Set upscale x2.
4. Make some brush strokes and generate an image.
5. Under the generated image, click "Sent to inpaint."


### What should have happened?

The width and height sliders should not change, but they now change to match the newly generated, scaled image.

### Commit where the problem happens

251ecee6949c36e9df1d99a950b3e1af2b5fa2b6

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

Windows

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

Google Chrome

### Command Line Arguments

```Shell
set COMMANDLINE_ARGS= --deepdanbooru --xformers --autolaunch
```


### Additional information, context and logs

_No response_
Repository: next.js
Issue: assetPrefix does not apply to <Images /> 
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

My machine info: 

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.0.7
      eslint-config-next: 13.0.7
      react: 18.2.0
      react-dom: 18.2.0

I'm experiencing the same problem reported in issue numbers [29330](https://github.com/vercel/next.js/issues/29330) and [20968](https://github.com/vercel/next.js/issues/20968).

Any update on this?

### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue

https://github.com/MikeBarberry/marvel-characters-next/tree/build

### To Reproduce

Review the source code linked above and attempt to access my API Gateway https://ekkow2ojlk.execute-api.us-west-2.amazonaws.com/main/add. You'll see that while my other static imports have the /main stage name appended, image sources do not and result in the following that cannot be resolved: `https://ekkow2ojlk.execute-api.us-west-2.amazonaws.com/_next/image?url=https://ekkow2ojlk.execute-api.us-west-2.amazonaws.com/main/_next/static/media/marvelLogo.bd2d21ac.jpeg&w=1920&q=75`.

### Describe the Bug

Image sources do not have asset prefix.

### Expected Behavior

Image sources have asset prefix.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: pytorch
Issue: wrong assert message
Labels: oncall: quantization,low priority,triaged

https://github.com/pytorch/pytorch/blob/cce577b39154b501705f32ee0392c77eee43820b/torch/ao/quantization/utils.py#L357-L359

In the assert condition, `2**31` is used, which is `2**31 = 2147483648`

However, in the error message, `4294967296` is used, which is `2**32 = 4294967296`

I think the assert message is wrong.

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: opencv
Issue: No tutorials for  Hardware accelerated video codecs 
Labels: feature,category: documentation

### System Information

OpenCV version: 4.7.0

### Detailed description

Althrough the release note of 4.7.0 said that `CUDA 12.0 support. Hardware accelerated video codecs support on NVIDIA platforms with modern Video Codec SDK (NVCUVID and NVENCODEAPI).`, there is no document for how to build opencv which supports this feature and how to use it. There is no samples.

### Steps to reproduce

Just use the opencv 4.7.0

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Advanced full-res inpainting tools
Labels: enhancement

- Full page zoom in for mask drawing
- Visualizer for aspect ratio and padding area, either done with rectangular overlays or a separate magnifier window
- Semi-transparent masks
- Polygonal and shape selection tools

### Proposed workflow

Click a button on the inpainting page to zoom in on the image and enter advanced mode, with tool selection and aspect ratio visualizer toggles on the left.
Repository: godot
Issue: Unable to add tile animation frames
Labels: topic:editor,documentation,topic:2d

### Godot version

4.0 beta 10

### System information

Ubuntu 22.04

### Issue description


I'm unable to make any changes to the frames array in tile properties

[godot_4_tile_anim_bug.webm](https://user-images.githubusercontent.com/15659245/210297555-32a8da7c-30b1-4cb3-a128-1deb6c061ff3.webm)


### Steps to reproduce

Create a new tileset select tiles and then properties.  Attempt to add a frame through the "Add Element" Button, or by right-clicking the three bars next to frame 0 and selecting insert before or after.

### Minimal reproduction project

[Uploading animation_bug.zip…]()
Repository: storybook
Issue: [Bug]: Source code not working . After add source code addons it just displaying loading source...
Labels: bug,addon: storysource

### Describe the bug

Source code
![Screenshot 2023-01-03 111738](https://user-images.githubusercontent.com/30592051/210305662-7f51cbf3-ce4a-47e7-b11d-ba207c2e21bd.png)
 not working . After add source code addons it just displaying loading source...

### To Reproduce

_No response_

### System

_No response_

### Additional context

"addons": [
    "@storybook/addon-links",
    "@storybook/addon-essentials",
    "@storybook/addon-interactions",
    "@storybook/addon-storysource"
  ],
Repository: Python
Issue: `mypy` produces errors when run on its own
Labels: enhancement

### Feature description

Apologies if I'm misunderstanding about how `mypy` is set up with this repo. `mypy` currently produces a litany of errors when run on its own even though it passes when run as part of `pre-commit`:
```
> mypy --ignore-missing-imports --install-types --non-interactive .
dynamic_programming/fibonacci.py:37: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
dynamic_programming/fibonacci.py:42: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
searches/binary_tree_traversal.py:21: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
maths/sigmoid_linear_unit.py:20: error: Function "numpy.core.multiarray.array" is not valid as a type  [valid-type]
maths/sigmoid_linear_unit.py:20: note: Perhaps you need "Callable[...]" or a callback protocol?
maths/sigmoid_linear_unit.py:29: error: Unsupported operand type for unary - (np.array?)  [operator]
maths/sigmoid_linear_unit.py:32: error: Function "numpy.core.multiarray.array" is not valid as a type  [valid-type]
maths/sigmoid_linear_unit.py:32: note: Perhaps you need "Callable[...]" or a callback protocol?
maths/sigmoid_linear_unit.py:51: error: Unsupported left operand type for * (np.array?)  [operator]
maths/sigmoid.py:14: error: Function "numpy.core.multiarray.array" is not valid as a type  [valid-type]
...
Found 87 errors in 13 files (checked 1143 source files)
```

Is this expected behavior? Should we expect `mypy`, when run on its own, to agree with `pre-commit`?
Repository: flutter
Issue: [Proposal] add FragmentPluginBinding or FragmentAware
Labels: c: new feature,platform-android,c: proposal,P3,team-android,triaged-android

## Use case

Why don't we have FragmentPluginBinding or FragmentAware?

When we develop a plugin, we can get some engine information through various callback in XXXPlugin, such as the attached activity, but Fragment is also one of the hosts of the engine, why can't we get it?

## Proposal

Provide some way so that we can get the host of the current engine (activity/fragment/others) in the upper layer.
Repository: PowerToys
Issue: Remember window placement in FancyZones
Labels: Needs-Triage

### Description of the new feature / enhancement

In a work environment it is very common to un-dock and re-dock a laptop between offices, meeting rooms, home working; all of which have different external monitor setups. Currently, even if I have a FancyZones configuration for all the monitor configurations, when I disconnect a laptop all windows move to the laptop screen only; but when I reconnect a laptop to an external monitor, it doesn't revert the previous setup, so I need to manually rearrange all my windows to my preferred FancyZone.

A feature would be to store a monitor+FancyZone configuration, and remember where each window lives for that configuration. Then, when reconnecting to a particular monitor+FancyZone configuration, all the windows ping back to where they were.

As someone who disconnects from my desk multiple times per day to go to meetings, having to rearrange all my windows everytime I return to my desk is not ideal.


### Scenario when this would be used?

Every time I disconnect/reconnect my laptop to an external monitor(s).
Saves a few minutes and some frustration, each time I change monitor configuration (or even if for some reason the laptop thinks it's disconnected from the external monitor, even though it hasn't - this happens too)

### Supporting information

Only personal use. It happens every time I disconnect/reconnect from/to external monitors.
Repository: pytorch
Issue: There is no developer documentation about getting started with MPS native debugging
Labels: module: docs,triaged,module: mps

### 📚 The doc issue

per title - getting started with writing native MPS code, or even tracking down bugs, assumes a large amount of pre-existing knowledge, and requires a lot of trial and error, because there's no documentation.

### Suggest a potential alternative/fix

I have already [written an informal guide/devlog](https://medium.com/p/f094b7f4e8f0) about what I had to do to be able to break into an LLDB session inside ATen MPS native code. I'd be very happy to adapt it for inclusion here, but I'd like to get approval from whomever is responsible for docs on the PyTorch team before going ahead.

cc @svekars @carljparker @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: vscode
Issue: Trusted domain dialog in web doesn't return focus to previously clicked element when canceled.
Labels: bug,accessibility,web,accessibility-sla

This can be trivially reproduced with the GitHub Pull Requests and Issues extension:

1. Open a pull request on insiders.vscode.dev
2. In the pull request description, leave a comment with a link to an external domain.
3. If you've trusted the workspace, set `"workbench.trustedDomains.promptInTrustedWorkspace": true`
4. Tab to the link that you made in step 2.
5. Enter.
6. In the resulting trusted domain dialog, tab to cancel and cancel.
7. 🐛 Focus is not restored (this works property on desktop with the native dialog).
Repository: ant-design
Issue: Ant Design Popover and Dropdown is not working on rc-dock/rc-new-window
Labels: Inactive,🚌 External Dependency

### Reproduction link

[https://github.com/kiocjw/rc-new-window](https://github.com/kiocjw/rc-new-window)

### Steps to reproduce

git clone https://github.com/kiocjw/rc-new-window.git

cd rc-new-window

npm i 

npm start 

Navigate to simple and click on Open/Close Window and press any button

Sample video of failure: https://user-images.githubusercontent.com/6771358/210332451-ec14d4dd-bc76-4a0f-a648-ff7f2cefaf20.mp4

### What is expected?

Expected the popover to work properly on different browsers not only firefox

### What is actually happening?

Popover only works on firefox only

| Environment | Info |
| --- | --- |
| antd | 5.1.2 |
| React | ^16.8.3 |
| System | WindowsOS and MacOS |
| Browser | Chrome |

---
Others' component is working fine but ant design component seems not working

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Allow `--wait` flag to work with split editors
Labels: feature-request,workbench-editors,workbench-cli,keep

Type: <b>Bug</b>

This is a reopening of #150368, which was not interpreted as a bug. It is a bug.

The `--wait` or `-w` flag behavior is unexpected and probably broken in combination with split editors. The `--help` output says this:

> Wait for the files to be closed before returning.

This description is ambiguous in relation to split editors. In fact the implementation doesn't do the "common sense" thing, which is to wait for the user to be *done editing*, but instead waits for a "lowlevel" editor closure event, which isn't useful behavior. The only trustable signal that the user is done, is when they have closed *all* editor instaces of the file(s) supplied from the command line.

This unexpected behavior can lead to genuine problems, even data loss. Consider using VSCode as a git commit messag editor. [The official documentation](https://code.visualstudio.com/docs/sourcecontrol/overview#_vs-code-as-git-editor) states to use the `--wait` flag. Consider the following steps (reproducable):

1. Invoke `git commit`. VSCode opens with COMMIT_EDITMSG and Git says `hint: Waiting for your editor to close the file...`
2. Split the editor (horizontally or vertically).
3. Edit and save the commit message.
4. Close *one* of the editors.
5. Git's `code --wait` invocation completes and applies the commit. If our `git commit` terminal is behind our VSCode window, we have no idea that this happened.
6. We still have COMMIT_EDITMSG open and can edit it, oblivious to the fact that we have already committed.

Therefore: VSCode interprets editor closure, which naturally happens when rearranging the editor layout, as editing-completion.

This is just an example with git, where of course the commit message can be amended. However, other tools invoking VSCode with `--wait` can and do cause much more severe problems.

Interestingly, the documentation linked above describes different behavior, when it says (emphasis mine)

> When you launch VS Code from the command line, you can pass the `--wait` argument to make the launch command wait until you have closed the new VS Code **instance**.

which leads to further confusion.

What's also confusing is that VSCode behaves differently for unsaved editors. Repeating the above git example, but *not* saving in step 3, actually yields the expected behavior of `code --wait` not completing. A code editor must not make any assumptions about the user saving. The behavior for saved and unsaved split-editor-closure should be identical.

VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No


<!-- generated by issue reporter -->