sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Child resource class initialized before parent resource class
Labels: bug,topic:core,confirmed

### Godot version

v4.0.beta2.official [f8745f2f7]

### System information

Linux (Pop OS), NVIDIA GeForce RTX 2060, Video Drive v 470.141.03

### Issue description

If you have a base class that extends Resource with some exports, and a Child class that extends that base class, the order of initialization on loading the resource seems backwards.

If the child class attempts to reference any values in the parent class during it's initialization, it will find that the parent class hasn't been set up yet.

The class init appears to be called with all default parameters (if the export values were passed here, I could pass it along to the parent constructor).  Then a second step sets the exported values from the resource file.  The second step appears to be called on the child class values before the parent class values.

I would expect that the parent class would have it's exported values set before the child class.

### Steps to reproduce

- Set up a Base class that extends Resource, that has at least one export
- Set up a child class that extends the Base class, with it's own export
- Have the child class try to reference one of the exported values on the Base class when setting the export value
- Load a saved version of that child class
- The base class value hasn't been set when you get to the point where the child class value is being set.

In the minimal reproduction product, I have an assert set up that will fail due to the parent class not being set up yet, so you should be able to just run it.

### Minimal reproduction project

[ResourceInheritBugTest.zip](https://github.com/godotengine/godot/files/9769514/ResourceInheritBugTest.zip)
Repository: rust
Issue: rustdoc: inconsistent number of blank lines rendered top/bottom
Labels: T-rustdoc,C-bug

I tried this code:

```rust
/// ```
/// # use c::f;
///
///
/// f()?;
///
///
/// # Ok::<(), i32>(())
/// ```
```

I expected to see this happen: the same number of blank lines rendered on the top and bottom (0, 1 or 2 depending on what rule is followed).

Instead, this happened: currently it renders 2 on top, but 1 at the bottom, which is confusing.

I assume the idea is that the user does not add any blank line at all. However, since leaving 1 line in the bottom renders fine (even if the generated HTML does contain an extra newline), users may assume that it also works for the top, especially in projects that e.g. group hidden/not hidden `use`s at the top. For instance, the following appears to work fine:

```rust
/// ```
/// # use c::very_common_thing;
/// use c::f;
///
/// f(very_common_thing)?;
///
/// # Ok::<(), i32>(())
/// ```
```

### Meta

Seems to have happened since a while ago, see https://github.com/rust-lang/rust/issues/78695 for a related feature request that would fix this bug by leaving 0 lines on both top and bottom (which would be consistent).
Repository: rust
Issue: Niche optimisation with disjoint tags
Labels: T-compiler,A-layout,C-discussion

These two types *could* be laid out the same. However, the second type makes it explicit that the tag is logically split across different bytes. Is this something we'd be okay with the compiler doing on its own? Inspecting the next part of the tag might require an extra load.

```rust
enum ShortSlice<T> {
    Empty,
    Single(T),
    Multi(Box<[T]>),
}
dbg!(size_of::<ShortSlice<NonZeroUsize>>()); // 24

enum ShortSlice2<T> {
    ZeroOne(Option<T>),
    Multi(Box<[T]>),
}

dbg!(size_of::<ShortSlice2<NonZeroUsize>>()); // 16
```
https://play.rust-lang.org/?version=nightly&mode=release&edition=2021&gist=a15d6b9d5389d781c5d778b250a02627
Repository: vscode
Issue: Pin in "File: Open Recent..." and in "Command palette..." - as in Tasks from VSCode version 1.72
Labels: feature-request,quick-open

VSCode 1.72 added Pinning in Tasks.
![obraz](https://user-images.githubusercontent.com/16800535/195976698-dd6ee7d5-6896-4f75-b67a-54226512e4f1.png)


I would like identical pinning in "File: Open Recent..." and in "Command palette...".

I could dispense with the Project Manager extension if I added pinning in "File: Open Recent...".
And it would be more convenient than Project Manager, because it would be recent open along with pinned. In Project Manager, I have pinning in a completely separate panel.

If I had Pinning in the "Command palette...", I could dispense with extensions that create special custom menus.

As you can see, this would be very useful, and it would be at little cost, a solution identical to the one already in place for Tasks.
Repository: vscode
Issue: Add static preloads notebook contribution 
Labels: feature-request,api,api-proposal

For #160965

This tracks a new contribution point that lets extensions contribute static preload scripts to a notebook of a specific type. Notebooks can use this to load global scripts before any notebook renderers have been loaded
Repository: stable-diffusion-webui
Issue: RTX 4090 performance
Labels: asking-for-help-with-local-system-issues

Is the 4090 fully supported in SD?

I am getting the same performance with the 4090 that my 3070 was getting.
Repository: pytorch
Issue: compile torch from source
Labels: needs reproduction,module: build,triaged

### 🐛 Describe the bug

Cuda version in my local machine or system env is 11.7 but 11.3 in my conda env. I set **_CUDA_HOME=/usr/lcoal/cuda_** when I compiled torch but failed ... And It finished with success when I downgraded cuda-version in local machine or upgraded cuda-version in my conda env. In other words, I have to keep cuda version in local machine consistent with that inside conda env, which is extremely inconvenient  for me... 
What can I do to solve it? THANKS

### Versions

torch 1.12.0

cc @malfet @seemethere
Repository: rust
Issue: Methods are not shown for pub type that is imported from other crate
Labels: T-rustdoc,E-needs-test,C-bug,A-cross-crate-reexports

### Location
I searched for `FatalError` in the rustc docs: https://doc.rust-lang.org/nightly/nightly-rustc/?search=fatalerror
The first two results are the interesting ones: [`rustc_errors::FatalError`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_errors/struct.FatalError.html) and [`rustc_span::fatal_error::FatalError`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_span/fatal_error/struct.FatalError.html)

When opening the `rustc_span::fatal_error::FatalError` page, the associated method `raise` is shown:
![grafik](https://user-images.githubusercontent.com/921462/195511178-49e22ff3-7363-426e-a999-98d6fea5fb45.png)

When opening the `rustc_errors::FatalError`, the method won't show up:
![grafik](https://user-images.githubusercontent.com/921462/195511240-96589998-99aa-4114-bd25-605c1ec2399c.png)

This looks like a bug to me, because you can call the public method through the public export, so that method should either be documented or a page forward should happen to the original struct.
Repository: PowerToys
Issue: RDP Desktop Power Toy Integration to Start bar desktops
Labels: Idea-Enhancement,Needs-Triage

### Description of the new feature / enhancement

Would it be possible to somehow link the RDP desktop to Start bar Desktops? Also WSL2 desktop could be nice to exist in Desktop pane.

### Scenario when this would be used?

When using remote or local WSL2 desktop.

### Supporting information

See: https://drive.google.com/file/d/1LYTZah8xWnFCaL-vmjolHUf9oiqdSia3/view?usp=sharing
Repository: ant-design
Issue: Table shouldCellUpdate
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/ji-ben-yong-fa-antd-4-22-4-forked-47ticj)

### Steps to reproduce

click Click button

### What is expected?

When shouldUpdateCell return true, Cell render should re-excuted

### What is actually happening?

doesn't excuted

| Environment | Info |
| --- | --- |
| antd | 4.23.5 |
| React | 17 |
| System | Window |
| Browser | 106.0.5249.103 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: DISABLED test_variant_consistency_jit_linalg_lu_factor_ex_cuda_complex64 (__main__.TestJitCUDA)
Labels: triaged,module: flaky-tests,skipped,module: unknown

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_variant_consistency_jit_linalg_lu_factor_ex_cuda_complex64&suite=TestJitCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8859723172).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_variant_consistency_jit_linalg_lu_factor_ex_cuda_complex64`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Repository: PowerToys
Issue: FancyZones idea: minimize/maximize window
Labels: Idea-Enhancement,Needs-Triage

### Description of the new feature / enhancement

Currently, I could not find a possible configuration, where Win+UP would maximize the window to use whole screen, and Win+DOWN to minimize. I like the window snapping functionality of FancyZones, and I am overriding the native windows keys to snapping, and loosing this feature. 


### Scenario when this would be used?

1. Every time you want to maximize the window to the whole screen
2. Every time you want to minimize the window to the tray

### Supporting information

_No response_
Repository: next.js
Issue: <style jsx> cannot render in next/head
Labels: Upstream,bug,Metadata

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.3.2-canary.26
      eslint-config-next: 12.1.0
      react: 17.0.2
      react-dom: 17.0.2


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

_No response_

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

_No response_

### Describe the Bug

<style jsx>{...}</style> cannot render in next/head

```
<Head>
  ...
  <style jsx>{`
    body {
      margin: 0;
      background: #ccc;
    }
  `}</style>
</Head>
```

### Expected Behavior

<style jsx>{...}</style> render in next/head successfully

### Link to reproduction

https://github.com/Capricair/next-dynamic-issue

### To Reproduce

1. npm run install
2. npm run dev
3. open homepage
Repository: pytorch
Issue: Broadcasting add for nested_tensor
Labels: triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

It would be useful when multiple a cutoff based ordinal regression heads of the CORAL variety https://github.com/Raschka-research-group/coral-pytorch to be able to do broadcasting addition, like so:

```
>>> import torch
>>> import torch.nested
>>> torch.nested.as_nested_tensor([torch.tensor([3.4, 2.3, 4.5])]) + torch.nested.nested_tensor([torch.tensor([-2.3, 0.4, 5.3]), torch.tensor([-2.3, 0.4, 5.3])])
/home/frankier/edu/doc/bert_ordinal/nestedplay/.venv/lib/python3.10/site-packages/torch/nested/__init__.py:84: UserWarning: The PyTorch API of nested tensors is in prototype stage and will change in the near future. (Triggered internally at ../aten/src/ATen/NestedTensorImpl.cpp:175.)
  return torch._nested_tensor_from_tensor_list(tensor_list, dtype, None, device, None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: add does not support broadcasting when given a NestedTensor
```

### Alternatives

Copy stuff like so (current workaround):

```
>>> torch.nested.as_nested_tensor([torch.tensor([3.4, 2.3, 4.5]),torch.tensor([3.4, 2.3, 4.5])]) + torch.nested.nested_tensor([torch.tensor([-2.3, 0.4, 5.3]), torch.tensor([-2.3,
 0.4, 5.3])])
nested_tensor([
  tensor([1.1000, 2.7000, 9.8000]),
  tensor([1.1000, 2.7000, 9.8000])
])
```

### Additional context

_No response_

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @mikaylagawarecki
Repository: godot
Issue: Got freeze for 1-2 seconds each time I press cmd+q (quit application) on macOS. 
Labels: platform:macos,performance

### Godot version

4.0 Beta2

### System information

macOS v12.6

### Issue description

This issue happens for Godot editor and exported application for macOS, in other words, all applications made by Godot.

The application will freeze for 1-2 seconds each time before the quit.

I noticed this issue occurred for applications made by Godot 3.5 also.

This laggy will makes me feel annoying, not sure what others might feel, maybe just me.

Expected experience is the application could be quitted quick and clean immediately after cmd+q is pressed.

### Steps to reproduce

1. Open any application made by Godot on macOS.
2. Press `cmd+q`.

### Minimal reproduction project

_No response_
Repository: stable-diffusion-webui
Issue: stop current generation if change from step to step is practically zero
Labels: enhancement

**Is your feature request related to a problem? Please describe.**
sometimes, the image will no more evolve from step to step. sometimes as soon as the 20th step (personal experience). But it still goes all the way to the last step unless click on stop button.

**Describe the solution you'd like**
It would be time and ressources saving if generation was automagically stopped when there is no longer discernable changes from one gen to the other. a threshold could be set in the settings by the user.


**Describe alternatives you've considered**
click the stop button. But sometimes i am not in front of the screen, expecially if batch generation, and some other time i am unsure about the rate of change from step to step so letting the process complete. But that is not satisfying.

**Additional context**
Add any other context or screenshots about the feature request here.
Repository: stable-diffusion-webui
Issue: Option to save source images when doing img2img and Extra
Labels: enhancement

In the process of making https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/2473 I generated a lot images in img2img, then using one of them each time, sending it to img2img again directly from GUI.

Then I have all generations with their parameters saved in folders, but no indication of what exact images did I use!

An option to always store a copy of input image will solve this. Even if it won't contain previous generation metadata, but the very image will be good enough. (Combining this with metadata can be left to future improvements).

You can argue that it will take x2 storage space, but firstly: it's an option, and user may enable or disable it at will; and secondly, you can implement an optimization which stores the input image only once per **invocation** – for example in "img2img-grids" subfolder, where the final result it stored only once even for batches/grids.

Related issues that effectively asked for this: 
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/2335
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/2333
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/2140
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/1784
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/1315
Repository: stable-diffusion-webui
Issue: DDP multi-GPU training with PyTorch Lightning 
Labels: enhancement,extension-request

Is there a way to add training for Dreambooth / TI / Hypernetwork training with PyTorch Lightning's trainer class using DDP strategy as featured in @XavierXiao's repo. It allows for a very pain-free experience when using multi-GPU training compared to native PyTorch's solutions. Correct me if I'm wrong but from what I've gathered there isn't a clean way to do this type of training with the code that's available now. If anyone has more information about how to do proper multi-GPU training please feel free to chime in.

[Code Here by XavierXiao](https://github.com/XavierXiao/Dreambooth-Stable-Diffusion/blob/main/main.py#L604-L611)
Repository: pytorch
Issue: View-based advanced indexing (Integer array/LongTensor indexing) of nested_tensor
Labels: feature,triaged,module: advanced indexing

### 🚀 The feature, motivation and pitch

Integer array/LongTensor indexing is a type of advanced indexing and as such typically returns a copy of a tensor. This feature request is proposing that something along these lines or index_select are implemented for nested_tensor, and made to return a view.

This feature has been requested a few times for normal tensors e.g. here https://discuss.pytorch.org/t/index-select-same-storage-as-the-original-tensor/4368/4 and here https://discuss.pytorch.org/t/tensor-slice-views/24694/5 -- both times it was noted that this does not fit with the normal strided tensor layout. However, it does seem that this should be possible for nested_tensor. One area where it is relevant is in multi-task learning e.g. different classification heads with a different number of labels. In this context, mutliple heads could be being stored in a nested_tensor. We may recieve a batch with task_ids corresponding to inputs and want to do something along the lines of `inputs ⊕ weights[task_ids]`.  At a cursory glance, it appears such a view is possible with nested_tensor. In fact, it looks like this is what `_nested_view_from_buffer` in the C++ API allows.

### Alternatives

The current workaround would be to use a list comprehension on the index array and reconstruct a nested_tensor with copies of the data.

### Additional context

_No response_
Repository: pytorch
Issue: DISABLED test_vmapvjp_linalg_lu_cuda_float32 (__main__.TestOperatorsCUDA)
Labels: triaged,module: flaky-tests,skipped,module: functorch

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_vmapvjp_linalg_lu_cuda_float32&suite=TestOperatorsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8862096317).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_vmapvjp_linalg_lu_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


cc @zou3519 @Chillee @samdow @soumith
Repository: PowerToys
Issue: "Quake" is translated to Dutch, which is not supposed to happen
Labels: Issue-Bug,Product-Settings,Area-Localization,Needs-Triage,Needs-Team-Response,Loc-Sent To Team,Issue-Translation

### Microsoft PowerToys version

0.63

### Utility with translation issue

PowerToys Run

### 🌐 Language affected

Dutch

### ❌ Actual phrase(s)

![afbeelding](https://user-images.githubusercontent.com/1918658/195574713-936fc360-4c3a-4f4f-8275-7784c1835cd6.png)



### ✔️ Expected phrase(s)

Something like "Profielen in het Quake-venster openen", and "Windows Terminal ondersteunt een "quake" functie waarbij ...."

### ℹ Why is the current translation wrong

"Quake" is translated, despite the [instruction](https://github.com/microsoft/PowerToys/pull/19960/files#diff-307e6095bbce676a874cfef8cb1f5d40b8b695841106e2345ce06c40da8dfc7dR125) not to do so in the resources file.
Repository: neovim
Issue: Accessors for nvim_win and nvim_buf api functions
Labels: enhancement,lua

### Feature description

What would you think of adding `vim.win` and `vim.buf`?

A bit similar to how you can do `vim.b[buf].comment`

```lua
vim.api.nvim_win_get_option(win, "winhighlight")
vim.api.nvim_buf_line_count(buf)

vim.buf[buf]:line_count()
vim.win[win]:get_option("winhighlight")

local buf = vim.buf[1]
buf:line_count()
buf:set_name("foobar")
```

Instead of `[]`, we could also use `()`.

Just an idea. Makes code shorter and easier to read.

If enough interest and if this is something that would be accepted, I'm willing to create a PR.

## With array access
```lua
local meta = {
  __index = function(_, key)
    return function(self, ...)
      return vim.api[("nvim_%s_%s"):format(self.type, key)](self[self.type], ...)
    end
  end,
}

vim.buf = setmetatable({}, {
  __index = function(_, buf)
    buf = buf == 0 and vim.api.nvim_get_current_buf()
    return setmetatable({ type = "buf", buf = buf }, meta)
  end,
})

vim.win = setmetatable({}, {
  __index = function(_, win)
    win = win == 0 and vim.api.nvim_get_current_win()
    return setmetatable({ type = "win", win = win }, meta)
  end,
})

local buf = vim.buf[0]

print(buf:line_count())

buf:set_name("foobar")

print(buf:get_name())
```

## As functions

```lua
local meta = {
  __index = function(_, key)
    return function(self, ...)
      return vim.api[("nvim_%s_%s"):format(self.type, key)](self[self.type], ...)
    end
  end,
}

---@param buf? number Buffer or 0 for the current buffer
function vim.buf(buf)
  buf = buf and buf ~= 0 and buf or vim.api.nvim_get_current_buf()
  return setmetatable({ type = "buf", buf = buf }, meta)
end

---@param win? number Window or 0 for the current window
function vim.win(win)
  win = win and win ~= 0 and win or vim.api.nvim_get_current_win()
  return setmetatable({ type = "win", win = win }, meta)
end

local buf = vim.buf()

print(buf:line_count())

buf:set_name("foobar")

print(buf:get_name())
```
Repository: opencv
Issue: A newSelf-Calibrated Illumination (SCI) learning framework
Labels: feature

### Descripe the feature and motivation

We develop a newSelf-Calibrated Illumination (SCI) learning framework for fast, flexible, androbust brightening images in real-world low-light scenarios. To be specific, weestablish a cascaded illumination learning process with weight sharing tohandle this task. Considering the computational burden of the cascaded pattern,we construct the self-calibrated module which realizes the convergence betweenresults of each stage, producing the gains that only use the single basic blockfor inference (yet has not been exploited in previous works), which drasticallydiminishes computation cost. We then define the unsupervised training loss toelevate the model capability that can adapt to general scenes. We think this method can be well introduced into OpenCV because of its lightweight.

### Additional context

The source code is available at https://github.com/vis-opt-group/SCI.