sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: [4.0 beta 11] Focus next control by pressing Tab key not always working
Labels: bug,needs testing,topic:gui

### Godot version

v4.0.beta11.official [91713ced8]

### System information

Manjaro Linux 22.0.0

### Issue description

Stepping through control nodes that can receive user input (like SpinBox) does not work as soon as I call `grab_focus()` in `ready()` and change `focus_mode` from `None` (which is the default) to `All`.

Manually setting `focus_next` only makes things worse.

### Steps to reproduce

1. Add 2 SpinBoxes
2. Launch game, click any SpinBox, press TAB. Everything works as expected: focus will cycle through the two SpinBoxes.
3. Decide you want to put initial focus into the first SpinBox. Add a script to it:
```
extends SpinBox

func _ready():
	grab_focus()
```

4. Launch game, get a warning: `_ready: This control can't grab focus. Use set_focus_mode() to allow a control to get focus.` Notice that the SpinBox does not have initial focus. Click any SpinBox, press TAB, notice that cycling through them still works as before.
5. Change `focus_mode` of the SpinBoxes from `None` to `All` to get rid of the warning.
6. Launch game, notice that the warning is gone but the SpinBox still doesn't have initial focus. Pressing TAB once now enters the first SpinBox. Pressing TAB again does not enter the second SpinBox, however. Only when pressing TAB a third time, we enter the next SpinBox. From now on we have to press TAB twice to jump from one SpinBox to the next.
7. Try solving it by setting the `focus_next` property of SpinBox A to SpinBox B and vice versa.
8. Launch game, notice that TAB no longer has any effect. It is not possible anymore to jump from one SpinBox to the next using TAB.


### Minimal reproduction project

[focus_test.zip](https://github.com/godotengine/godot/files/10407227/focus_test.zip)
Repository: deno
Issue: Speed up npm integration tests
Labels: chore

They are too slow. Maybe some of them should be moved to unit tests.

```
166.08s | tests/npm_tests.rs (target/debug/deps/npm_tests-fe5cac7b378a2336)
```
Repository: TypeScript
Issue: Type hint incorrect if type alias is exported
Labels: Bug,Help Wanted,Domain: Completion Lists

# Bug Report

### 🔎 Search Terms

export type alias

### 🕗 Version & Regression Information

No clue, seems older but I can't find any reference to it

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about exported types

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.9.4#code/KYDwDg9gTgLgBDAnmYcBiEJwLxwOSgCMecAPvqAEx4DcAsAFCMDGEAdgM7wgBc6mQA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
export type Foo = 'ex1' | 'ex2';

const x: Foo
```

### 🙁 Actual behavior

When annotating with an exported type alias, the type hint in an editor (noticed with NeoVim using [`coc-tsserver`](https://github.com/neoclide/coc-tsserver) and can reproduce in TS Playground) is shown as `any`. Removing the `export` ensures the correct type is shown.

This is limited to the hints, however. Attempting to assign an incorrect value (like `'ex3'`, in the example above) will still show a type error. 

### 🙂 Expected behavior

I should see the correct type, even if the alias is exported.

Image comparison to help illustrate:

🙁 w/ `export`             |  🙂 w/out `export`
:-------------------------:|:-------------------------:
![w/ `export`](https://user-images.githubusercontent.com/33403762/212218343-184694a1-7bef-435b-a67e-0551a1e07541.png) | ![w/out `export`](https://user-images.githubusercontent.com/33403762/212218418-4403ece9-4830-4db1-975a-a3102f22a9a3.png)
Repository: godot
Issue: When I try to get_var from this file the engine crashes with no error
Labels: bug,topic:core,crash

### Godot version

3.5.1

### System information

Windows 11

### Issue description

I was trying to save an array with resources in it, but when i try to load it, it crashes.

### Steps to reproduce

run the repro project

### Minimal reproduction project

[test.zip](https://github.com/godotengine/godot/files/10407858/test.zip)
Repository: rust
Issue: Rustdoc compressed doc
Labels: T-rustdoc

From https://github.com/rust-lang/docs.rs/issues/360

> The local docs are not compressed, it took up 635 MB for the current stable, half the size of the whole toolchain (1.2 GB). I think we can reopen this, but one issue is browser does not work with locally compressed files.

> If the web browsers can still work with local compressed files, then I'm totally going to add it. @GuillaumeGomez 

Currently local docs are stored uncompressed, one way is to start a server but that would requires user to have a step to start documentation server which makes the user experience worse. Maybe a more feasible way is to be able to compressed part of the local docs and store it in a better way?

Or we just have to wait until browsers support opening locally compressed docs.
Repository: pytorch
Issue: DISABLED test_cuda_variable_sharing (__main__.TestMultiprocessing)
Labels: triaged,module: flaky-tests,skipped,module: unknown

Platforms: rocm

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

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 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_cuda_variable_sharing`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Repository: pytorch
Issue: Torchrun seems to have problem with virtual environment
Labels: oncall: distributed,triaged,oncall: r2p

## Issue description

Use torchrun (inside a virtual environment) to launch a Python script. The script can not import modules installed in that virtual environment. Changing to use torch.distributed.launch to launch works well but that method has been depreciated.

## Code example

* Create a venv, activate the venv
* Install a module, say "pip install datasets"
* Write a python script (test.py) to load datasets
```
# This is test.py
import datasets
```
* Do the following
```
torchrun \
    --nnodes=1 \
    --nproc_per_node=8 \
    --max_restarts=0 \
    --rdzv_id=123456 \
    --rdzv_backend=c10d \
    --rdzv_endpoint=localhost \
    test.py
```
You will get "ModuleNotFoundError: No module named 'datasets'"
* Changing from 'torchrun' to 'python3 -m torch.distributed.launch', then it all works.
```
python3 -m torch.distributed.launch \
    --standalone \
    --nnodes=1 \
    --nproc_per_node=8 \
    test.py
```

## System Info

Python 3.10.6
PyTorch 1.12.0
Linux (CentOS 7)

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: godot
Issue: When click Delete Type in the Theme Editor Management Theme Items menu, you not only delete the selected type, but delete all unused types
Labels: bug,topic:editor,usability,topic:gui

### Godot version

3.5.1mono

### System information

windows10

### Issue description

See this video
[2023-01-13 13-43-42.zip](https://github.com/godotengine/godot/files/10408528/2023-01-13.13-43-42.zip)


### Steps to reproduce

1.Create a project
2.Create a theme
3.Open theme editor
4.Open management theme items menu
5.Create more than 2 type
6.Delete one of them
7.Found all the types that don't be used are deleted

### Minimal reproduction project

An empty project
Repository: pytorch
Issue: [Bug][Dataloader] unable to mmap 2048 bytes from file <filename not specified>: Cannot allocate memory (12)
Labels: module: multiprocessing,module: dataloader,triaged

### 🐛 Describe the bug

Hi,

Here is the results i observed when i was running my workload with PyTorch 1.13 on Ubuntu 20.04 to train RN50 with imageNet:
When i run 25 epochs, the error is thrown as below:

```
Epoch: [25][3096/5005]	Time  0.551 ( 0.548)	Data  0.000 ( 0.001)	Loss 1.9055e+00 (2.1268e+00)	Acc@1  57.81 ( 51.79)	Acc@5  79.69 ( 76.05)
Epoch: [25][3097/5005]	Time  0.547 ( 0.548)	Data  0.000 ( 0.001)	Loss 1.9593e+00 (2.1268e+00)	Acc@1  55.08 ( 51.80)	Acc@5  81.25 ( 76.06)
Exception in thread Thread-52:
Traceback (most recent call last):
  File "/home/gta/miniconda3/envs/zejun/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/home/gta/miniconda3/envs/zejun/lib/python3.9/threading.py", line 910, in run
    self._target(*self._args, **self._kwargs)
  File "/home/gta/miniconda3/envs/zejun/lib/python3.9/site-packages/torch/utils/data/_utils/pin_memory.py", line 52, in _pin_memory_loop
    do_one_step()
  File "/home/gta/miniconda3/envs/zejun/lib/python3.9/site-packages/torch/utils/data/_utils/pin_memory.py", line 29, in do_one_step
    r = in_queue.get(timeout=MP_STATUS_CHECK_INTERVAL)
  File "/home/gta/miniconda3/envs/zejun/lib/python3.9/multiprocessing/queues.py", line 122, in get
    return _ForkingPickler.loads(res)
  File "/home/gta/miniconda3/envs/zejun/lib/python3.9/site-packages/torch/multiprocessing/reductions.py", line 294, in rebuild_storage_fd
    storage = cls._new_shared_fd(fd, size)
RuntimeError: falseINTERNAL ASSERT FAILED at "/home/gta/zejun/pytorch/aten/src/ATen/MapAllocator.cpp":323, please report a bug to PyTorch. unable to mmap 2048 bytes from file <filename not specified>: Cannot allocate memory (12)
```

This Runtime Error is thrown from torch dataloader. I found the community has had this issue: https://discuss.pytorch.org/t/pytorch-cannot-allocate-memory/134754.

I set the dataloader workers to be 0 and the error is missing, but the training time increases too much when using the single process to fetch and decode the dataset. I also check the host memory usage and no oom happen. The fd limitation of one process is also not exceeded. Thus we wonder if the issue can be fixed, otherwise it may block the model training with PyTorch.

### Versions

PyTorch 1.13
Python 3.9
Torchvision 1.14
Running BS: 256
Model: ResNet50
Dataset: ImageNet

Ubuntu 20.04
Host Mem 128G
CPU: Intel Xeon Gold 6342

cc @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: create-react-app
Issue: Why doesn't webpack hot update work when webpack module federation is applied?
Labels: needs triage

## Summarize
`webpack hot update` **does not work** when `module federation` is applied to CRA using CRACO (Create React App Configuration Override).

<hr />

### Screenshot
![image](https://user-images.githubusercontent.com/11847732/212248231-5d209403-2b85-4100-a2fa-96ba18573dea.png)

<hr />

### Project configuration
![image](https://user-images.githubusercontent.com/11847732/212248387-c41b37e6-fb17-439b-8923-ddaa61a48401.png)

<hr />

### Webpack setting (craco.config.js)
```javascript
const { ModuleFederationPlugin } = require('webpack').container;
const { dependencies } = require('./package.json');

const isDev = process.env.NODE_ENV === 'development';

module.exports = {
  devServer: {
    port: 4000,
    historyApiFallback: true,
    headers: {
      'Access-Control-Allow-Origin': '*',
    },
  },
  webpack: {
    plugins: {
      add: [
        new ModuleFederationPlugin({
          name: 'dashboard',
          filename: 'remoteEntry.js',
          exposes: {
            './Main': './src/bootstrap',
            './Btn': './src/components/Button.jsx',
          },
          shared: dependencies,
        }),
      ],
    },
    configure: (webpackConfig) => ({
      ...webpackConfig,
      output: {
        ...webpackConfig.output,
        publicPath: isDev ? 'auto' : 'http://localhost:4001/',
      },
    }),
  },
};
```
<br />
<hr />

## Description
i am trying to create MF(micro frontend) using webpack5 module federation.


I'm still not good at custom setting webpack, so I'm trying to use CRA.

override webpack configuration via CRA,
when I edit the code, an error occurs as shown in the screenshot.

could it be due to chunk related issues?
please any advice? 😥
Repository: stable-diffusion-webui
Issue: [Bug]: Generating an image, then reusing its seed will ignore any new image generated
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?

When you generate any image in txt2img (I didn't test img2img or inpaint), if you want to reuse the seed of an already generated image in the webui, it will refuse to show the end result of a new image if the seed is the same, even if you change parameters (for example resolution). Instead it shows the first generated image with the seed.
It also doesn't save the new image anywhere.

### Steps to reproduce the problem

1- Generate any image, for example "chair" at 256x256
2- Then reuse the seed and change the resolution to 512x256 (you can change anything outside of the seed).
3- The resulting image is still the one generated before at step 1 instead of being the new one at the 512x256. If you check if any image was saved, nothing was saved anywhere.



### What should have happened?

It should generate a new image with the new parameters, even if the seed is the same.

### Commit where the problem happens

d930020044875fa780c95f7bc1881c7077d4fa59

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

Windows

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

Brave

### Command Line Arguments

```Shell
--xformers --no-half-vae --deepdanbooru
```


### Additional information, context and logs

_No response_
Repository: next.js
Issue: Server side Error.getInitialProps result cannot be hydrated into client error page
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 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 19.4.0
      npm: 9.2.0
      Yarn: 1.22.19
      pnpm: 7.24.3
    Relevant packages:
      next: 13.1.2
      eslint-config-next: 13.1.1
      react: 18.2.0
      react-dom: 18.2.0

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

Data fetching (gS(S)P, getInitialProps)

### Link to the code that reproduces this issue

https://github.com/tangye1234/next.js/tree/fix/render-error-on-page-error/test/integration/render-error-on-page-error/pages

### To Reproduce

We need to reproduce it on production build, not dev phase.

```shell
next build
next start
```

browser the localhost, the error page cannot be hydrated properly.
the console prints a hydration error(react minify error)

### Describe the Bug

The bug is firstly introduced by the bugfix: #21240
That bugfix is to solve the top module error in client render/hydration.

In fact, the `renderErrorProps.props?.err` can never be existed, which breaks the original intents.

### Expected Behavior

1. do not break the original design, that will use the error.getInitialProps server side result as the hydration props.
2. if error comes from client not server side, it must call error.getInitialProps in the client side.

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

Chrome 108

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

next start in nodejs
Repository: go
Issue: proposal: net/http/httputil: ReverseProxy add a API to get the length of proxy had sent data 
Labels: Proposal

<!--
Our proposal process is documented here:
https://go.dev/s/proposal-process
-->
demo code:
``` go
revProxy := httputil.NewSingleHostReverseProxy(url)
  modifyFunc := func(res *http.Response) error {
		body, err := io.ReadAll(res.Body)
		res.Body = io.NopCloser(bytes.NewReader(body))
		if err != nil {
			return err
		}
		count := len(body)
		return nil
	}
	revProxy.ModifyResponse = modifyFunc
```

goal：get the length of proxy had sent data, it is successful, but it is block when response is live streaming, because io.ReadAll() can not read EOF or error from streaming。The stream has always existed and has no end。

Design:
```go
type ReverseProxy struct {
    SendBodySize atomic.Int64
}
```

```go
// copyBuffer returns any write errors or non-EOF read errors, and the amount
// of bytes written.
func (p *ReverseProxy) copyBuffer(dst io.Writer, src io.Reader, buf []byte) (int64, error) {
	if len(buf) == 0 {
		buf = make([]byte, 32*1024)
	}
	var written int64
	for {
		nr, rerr := src.Read(buf)
		if rerr != nil && rerr != io.EOF && rerr != context.Canceled {
			p.logf("httputil: ReverseProxy read error during body copy: %v", rerr)
		}
		if nr > 0 {
			nw, werr := dst.Write(buf[:nr])
			if nw > 0 {
				written += int64(nw)
                                 p.SendBodySize.Add(int64(nw))  // add code
			}
			if werr != nil {
				return written, werr
			}
			if nr != nw {
				return written, io.ErrShortWrite
			}
		}
		if rerr != nil {
			if rerr == io.EOF {
				rerr = nil
			}
			return written, rerr
		}
	}
}

func (p *ReverseProxy) ResetSendSize() {
    p.SendBodySize.Store(0)
}
```
Repository: PowerToys
Issue: [PT Run > System plugin] Enable / Disable network adapter buttons
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

In PT Run you can search for network interfaces. The possibility to enable/disable the adapters would be great.

Additional an option to open `ncpa.cpl` or the adapter properties would be great.

### Scenario when this would be used?

If you have network problems or switch the environment and have to disable/enable adapters fast.

### Supporting information

_No response_
Repository: godot
Issue: get_node() does not accept StringName variables as a valid argument
Labels: topic:gdscript

### Godot version

4.0 Beta 11

### System information

Win 10, Forward+, 1080ti, 516.94 driver

### Issue description

Simply put if you try to get a node by using a StringName as an argument you'll get the error

`Parser Error: Invalid argument for "get_node()" function: argument 1 should be "NodePath" but is "StringName".`

which is likely an oversight because doing `get_name()` on a node gives a StringName.

I came across this when I was trying to loop through some nodes, checking names of nodes in an array vs the children of a node, but was able to easily work around it by making the array a string typed array

### Steps to reproduce


I uploaded an mrp, but the code is as simple as

```
var nodeString = StringName("Node")
var test = get_node(nodeString)
```

### Minimal reproduction project

[bug.zip](https://github.com/godotengine/godot/files/10409307/bug.zip)
Repository: next.js
Issue: Failed to execute 'replaceState' on 'History': A history state object with URL on google web cache
Labels: bug,stale

### Verify canary release

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

### Provide environment information

Version next 12.3.1


![image](https://user-images.githubusercontent.com/45229473/212283596-52bcbba3-20e2-4bf0-afbe-16390c3e46a1.png)


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

_No response_

### Link to the code that reproduces this issue

-

### To Reproduce

when viewing a page in google cache, this error appears Failed to execute 'replaceState' on 'History': A history state object with URL on google web cache Can I somehow get rid of this error? 

### Describe the Bug

when viewing a page in google cache, this error appears Failed to execute 'replaceState' on 'History': A history state object with URL on google web cache Can I somehow get rid of this error? 

### Expected Behavior

.

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

_No response_

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

_No response_
Repository: vscode
Issue: Regression: debugger cannot attach to a child process
Labels: bug,debug

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No (but read the description)

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.74.0 and newer
- OS Version: MacOS Ventura 13.1 

Installed extensions: 
* ms-python.python

**Summary:** Python debugger can't attach to a child process and fails with a "Failed to launch debugger for child process" message. This issue is submitted here and not in the Python extension repository, because it's a regression after https://github.com/microsoft/vscode/pull/166137.

**Longer explanation:** When using a debug server like debugpy and attaching to it from VSCode (an ordinary remote attach launch configuration), the debugger is disconnected after an `os.execv()` call (and similar methods I suppose). This started happening in VSCode 1.74.0, it was working perfectly fine in 1.73.1. At first I thought it was an issue with the Python extension, however even after downgrading the extension, the issue persisted. Then I sat with `git bisect`, started compiling VSCode from sources, and found the PR after which the issue happens: https://github.com/microsoft/vscode/pull/166137. I'm not yet sure why that breaks the debugging. I've made a MCVE and a screen recording that shows the reproduction:


https://user-images.githubusercontent.com/9080183/212286574-a6c83ce3-7cc2-47a5-be48-0be9674f24af.mov

[python-debugger-reproduction.zip](https://github.com/microsoft/vscode/files/10410169/python-debugger-reproduction.zip)