sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/pkgsite: broken link to internal type
Labels: pkgsite

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jbettis/.cache/go-build"
GOENV="/home/jbettis/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/jbettis/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/jbettis/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.5"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="x86_64-pc-linux-gnu-clang"
CXX="x86_64-pc-linux-gnu-clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2698240387=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

Read the documentation at https://pkg.go.dev/chromium.googlesource.com/chromiumos/platform/tast.git/src/go.chromium.org/tast/core/testing#Test

That package exports a type named Test, which is an alias of a Test struct that is in an internal package.

### What did you expect to see?

I expected to see the documentation for testing.Test

### What did you see instead?

A broken link to the internal type. There is no way to see the docs for the funcs or Public members of the Test struct.

Source code for public package: https://chromium.googlesource.com/chromiumos/platform/tast/+/15a9a0c3c67a/src/go.chromium.org/tast/core/testing/test.go#21
Source code for internal package: https://chromium.googlesource.com/chromiumos/platform/tast/+/15a9a0c3c67a/src/go.chromium.org/tast/core/internal/testing/test.go#41
Generated doc: https://pkg.go.dev/chromium.googlesource.com/chromiumos/platform/tast.git/src/go.chromium.org/tast/core/testing#Test
Repository: godot
Issue: VisualShader Varyings Appearing Incorrectly In Inspector
Labels: bug,topic:editor,topic:shaders

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Windows 10

### Issue description

When a varying is created in a VisualShader, it seems to always appear as a Vector2, and is unable to be changed.

### Steps to reproduce

Create a visual shader and assign it to a material/mesh. Click "Manage Varyings" and create a new varying. Go to the shader's inspector window and try to change the value of the varying.

### Minimal reproduction project

[VaryingsIssue.zip](https://github.com/godotengine/godot/files/12717778/VaryingsIssue.zip)
Repository: vscode
Issue: Better synonym support in TF-IDF similar commands
Labels: feature-request,quick-open

We can support this better by tacking on a list of known synonyms to a user's query. This will improve results quite a bit.
Repository: vscode
Issue: git diff on untracked new file shows erroneous removal of non-existant first line
Labels: feature-request,diff-editor

Type: <b>Bug</b>

- create a file with some contents in an existing git working dir
- go to git tab, select file

the diff viewer shows that line #1 is being replaced. this is wrong: there _is_ no prior version containing line #1.

![image](https://github.com/microsoft/vscode/assets/1088194/63a11479-5879-4023-a6db-bdd079391b3f)

also repos on github.dev 1.18.2

VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 4.4.0-19041-Microsoft
Connection to 'wsl+centos7' could not be established

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (6 x 2904)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|47.85GB (16.33GB free)|
|Process Argv|C:\\Users\\PiersH\\AppData\\Roaming\\com.bostrot\\WSL Distro Manager\\wslmanager_01.log|
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|WSL: Ubuntu-22.04|
|OS|Linux x64 4.4.0-19041-Microsoft|
|CPUs|Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (6 x 2901)|
|Memory (System)|47.85GB (16.31GB free)|
|VM|0%|

Connection to 'wsl+centos7' could not be established
</details><details><summary>Extensions (12)</summary>

Extension|Author (truncated)|Version
---|---|---
autoconf|mae|0.2.0
remote-containers|ms-|0.309.0
remote-ssh|ms-|0.106.4
remote-ssh-edit|ms-|0.86.0
remote-wsl|ms-|0.81.4
vscode-remote-extensionpack|ms-|0.24.0
remote-explorer|ms-|0.4.1
remote-server|ms-|1.4.3
gitlens|eam|14.3.0
cpptools|ms-|1.17.5
cpptools-extension-pack|ms-|1.3.0
markdown-all-in-one|yzh|3.5.1

(2 theme extensions excluded)

</details>
<!-- generated by issue reporter -->
Repository: PowerToys
Issue: Remap alt and ctrl keys, fail when need write @
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Repro,Priority-2

### Microsoft PowerToys version

0.73.0

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Remap this keys
![image](https://github.com/microsoft/PowerToys/assets/35842929/19b8900a-f58f-46b4-a610-f87dfbac17b3)

Try to write @

### ✔️ Expected Behavior

Write @

### ❌ Actual Behavior

Write 2

### Other Software

_No response_
Repository: godot
Issue: Scaled SubViewportContainers break contained TileMap grids
Labels: bug,topic:gui

### Godot version

Godot v4.2.dev5 - Fedora Linux 38 (Workstation Edition) - Wayland - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i7-1280P (20 Threads)

### System information

Godot v4.2.dev5 - Fedora Linux 38 (Workstation Edition) - Wayland - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i7-1280P (20 Threads)

### Issue description

Expected behavior: Tilemaps show grids aligned to their actual tile content, regardless of whether or not they're within a SubViewport.

Actual behavior: Tilemaps within SubViewports render grids that are out-of-alignment with the SubViewportContainer's scale and the actual tile content.

Given this node & scene structure:
![Screenshot from 2023-09-25 14-10-50](https://github.com/godotengine/godot/assets/364501/89712485-9271-4c4b-98cf-bc9cb8a0dfd0)

... a 16x16px tilemap scene that is rendered like this:
![Screenshot from 2023-09-25 14-10-06](https://github.com/godotengine/godot/assets/364501/1d84bf41-14e9-4b50-9b6b-a057206bd5f2)

... will be rendered like this when nested inside of a subviewport with a scale of (8, 8):
![Screenshot from 2023-09-25 14-15-25](https://github.com/godotengine/godot/assets/364501/dcd9bf81-8ec0-466d-8e18-f6d401b07c65)

The tilemap grid no longer aligns to the actual tiles as rendered.

Further, whatever is driving the incorrect grid scale also impacts Cameras, since I first noticed this when a Camera2D was no longer accurately assigning its viewport's visible rect - instead, assigning one to the upper-left, as if the camera's coordinate system had been scaled down.

### Steps to reproduce

1. Create a scene (A) with a Tilemap, draw a few tiles, and save it.
2. Create a new scene (B) with a SubViewport in a SubViewportContainer.
3. Scale the SubViewportContainer to (8, 8)
4.  Drag and drop scene A into the SubViewport of scene B
5. Enable "editable children" on the nested scene A so you can select the TileMap
6. Select the TileMap; note that its grid no longer aligns with its rendered tiles


### Minimal reproduction project

[bug-tilemap-subviewport.zip](https://github.com/godotengine/godot/files/12718303/bug-tilemap-subviewport.zip)
Repository: material-ui
Issue: [material-ui][Stack] Not accepting a React Fragment when using it with a divider
Labels: waiting for 👍,package: material-ui,component: Stack,status: expected behavior

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. Use the Stack component
2. Wrap the children elements inside a React Fragment. (in my particular scenario I am sending this as a prop that is why I send it wrapped in a fragment)
3. Add a prop to the Stack component to add "dividers" (`divider={<div>xxx</div>}`)
4. The component generates the spacing between each element but it doesn't add the dividers

Sandbox example:
https://codesandbox.io/s/stack-divider-fragment-bug-lnypq9

### Current behavior 😯

There is no divider between each children element.

```
<Stack>
  <div>one</div>
  // space
  <div>two</div>
  // space
  <div>three</div>
</Stack>
```

### Expected behavior 🤔

Should add between each children element a divider

```
<Stack>
  <div>one</div>
  // space
  <divider/>
  // space
  <div>two</div>
  // space
  <divider/>
  // space
  <div>three</div>
</Stack>
```

### Context 🔦

I created an extended version of the Stack component. It's almost the same but with some additions. If you send the children elements as a React Fragment is where you get the bug. I need to accept those because it's a valid JSX code and also because my component accepts the children prop.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: vscode
Issue: Search Editor: Add keybinding for double-click action, e.g. to open to the side
Labels: help wanted,feature-request,search

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

In the Search Editor, there are currently keybindings / keyboard shortcuts for opening results in the current editor group, and double-clicking can be configured to open to the side, but there are currently no keybindings for opening to the side:

- https://code.visualstudio.com/docs/editor/codebasics#_search-editor
> In the Search Editor, results can be navigated to using Go to Definition actions, such as F12 to open the source location in the current editor group, or ⌘K F12 to open the location in an editor to the side. Additionally, double-clicking can optionally open the source location, configurable with the search.searchEditor.doubleClickBehaviour setting.

- https://code.visualstudio.com/docs/getstarted/settings
```js
  // Configure effect of double-clicking a result in a search editor.
  //  - selectWord: Double-clicking selects the word under the cursor.
  //  - goToLocation: Double-clicking opens the result in the active editor group.
  //  - openLocationToSide: Double-clicking opens the result in the editor group to the side, creating one if it does not yet exist.
  "search.searchEditor.doubleClickBehaviour": "goToLocation",
```

It'd be great to add a keybinding to do the same action as double-click, which users can already configure to `openLocationToSide`. (Looks like `enter` / `cmd+enter` are currently available.)
Repository: fastapi
Issue: Get the StringConstraints directly from the Identifier type
Labels: feature,confirmed

**Problem:**
FastAPI does not validate custom string build using `Annotated[str, StringConstraints(...)]`

**Temporary solution**
_My solution is to annotate the constrained type with Path again, then it seems to work:_

```python
from typing import Annotated

from fastapi import FastAPI, Path
from pydantic import StringConstraints

# In my case this is imported from a lib with pydantic but without fastapi,
# so it can't be changed to Annotated[str, Path(pattern=r"^[a-fA-F0-9]+$")]
Identifier = Annotated[str, StringConstraints(pattern=r"^[a-fA-F0-9]+$")]


app = FastAPI()


@app.get("/{some_id}")
async def get_something(some_id: Annotated[Identifier, Path()]):
    return some_id

```

**Feature request**
Would be nice if fastapi would be able to get the constraint directly from the `Identifier` type without being required to add `Annotated[Identifier, Path()]`.

_Originally posted by @JasperJuergensen in https://github.com/tiangolo/fastapi/discussions/10105#discussioncomment-6901418_
Repository: pytorch
Issue: Dataloader resetting with num_workers=1 and persistent_workers=True
Labels: module: dataloader,triaged

### 🐛 Describe the bug

I hit the following bug when initializing a pytorch Dataloader with `num_workers=1` and `persistent_workers=True`. It seems the Dataloader gets reset:

`UserWarning: Length of IterableDataset <ConstantLengthDataset object at 0x7f4f3d028790> was reported to be 55936 (when accessing len(dataloader)), but 69087 samples have been fetched. For multiprocessing data-loading, this could be caused by not properly configuring the IterableDataset replica at each worker.`

I also tried using the `worker_init_fn` as suggested, where `dataset.start` and `.end` are the start and end indices. It still hits the above warning: 

```
def worker_init_fn(worker_id):
    worker_info = torch.utils.data.get_worker_info()
    dataset = worker_info.dataset  # the dataset copy in this worker process
    overall_start = dataset.start
    overall_end = dataset.end
    # configure the dataset to only process the split workload
    per_worker = int(math.ceil((overall_end - overall_start) / float(worker_info.num_workers)))
    worker_id = worker_info.id
    dataset.start = overall_start + worker_id * per_worker
    dataset.end = min(dataset.start + per_worker, overall_end)
    logger.info(f"Initializing worker with split of data from {dataset.start} to {dataset.end}")

```

From the training perspective, I hit this error about every 2.46 epochs and the epochs get reset to 1 and then it continues training from there, but I have a suspicion it's skipping part of the data. I worry this might have affected training. 

### Versions

PyTorch version: 2.0.1+cu118
Is debug build: False
CUDA used to build PyTorch: 11.8
ROCM used to build PyTorch: N/A

Versions of relevant libraries:
[pip3] numpy==1.24.4
[pip3] pytorch-lightning==2.0.8
[pip3] pytorch-ranger==0.1.1
[pip3] torch==2.0.1+cu118
[pip3] torch-optimizer==0.3.0
[pip3] torchdata==0.6.1
[pip3] torchmetrics==0.11.4
[pip3] torchtext==0.15.2+cpu
[pip3] torchvision==0.15.2+cu118
[pip3] triton==2.0.0
[pip3] triton-pre-mlir==2.0.0
[conda] Could not collect

cc @SsnL @VitalyFedyunin @ejguan @dzhulgakov
Repository: vscode
Issue: SCM - Visually distinguishing Staged Changes from Changes in Tree View
Labels: ux,scm,under-discussion

<!-- ⚠️⚠️ 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?: Yes

<!-- 🪓 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.82.2
- OS Version: macOS 13.5.2

It's difficult to distinguish Staged Changes from Changes in Source Control sidebar in Tree view. This has been raised several times before; most relevant was https://github.com/microsoft/vscode/issues/102473 but that was swept into an existing discussion about a larger change that was only partially relevant.

Simplest proposal:

```css
[role="treeitem"][aria-level="1"] {
    font-weight: bold;
}
```

The difference is subtle; other tweaks could improve it. e.g., add a line (or even half-line) of vertical space before it. Or, removing the 8px padding-left on the .monaco-tl-twistie also pulls it visually farther from the tree. The old all-caps CHANGES feels a bit too strong to me, but it would fix the issue.

Other approaches include https://github.com/microsoft/vscode/issues/140343 suggested adding themeable elements.
Repository: flutter
Issue: Separate beta and stable release builders into their own configurations
Labels: P1,team-release,infra: security
Repository: next.js
Issue: Scripts using `beforeInteractive` do not run at all if a client component references "window"
Labels: bug

### Link to the code that reproduces this issue

https://github.com/jdgarcia/nextjs-script-beforeinteractive-bug

### To Reproduce

1. Start the application in development (next dev)
2. Open the Dev Tools -> Console
3. notice that `console.log('beforeInteractive script');` never gets run
4. remove reference to `window` in Test.tsx and refresh the page
5. notice that `console.log('beforeInteractive script');` now does get run

### Current vs. Expected behavior

I expected my `Script` element that uses `beforeInteractive` to be run. Instead, it did not run.

### 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.5.0: Mon Apr 24 20:53:19 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6020
Binaries:
  Node: 18.16.1
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 13.5.3-canary.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Script optimization (next/script)

### Additional context

_No response_
Repository: godot
Issue: Vulkan: Non-power-of-2 PointLight2D texture renders wrong
Labels: bug,topic:rendering,topic:2d

### Godot version

4.1.1.stable.official

### System information

Windows 10, GeForce RTX 2080, driver 31.0.15.2849, "forward_plus"

### Issue description

I'm very new to Godot, so please forgive me if I misunderstood or messed up something.

When setting textures for PointLight2D "sometimes" it renders weird if the texture dimensions are not power of two.
"Sometimes" - because I'm not always able to reproduce this. But once it happens it happens always.
Also, sometimes it shows up in the editor as well, sometimes only in run mode.

![capture1](https://github.com/godotengine/godot/assets/70334968/d706f2b5-4fc0-47c3-b8de-4291e5e06226)


### Steps to reproduce

- create new project, create new 2D scene
- add Polygon2D, draw a large polygon, adjust color so that it's somewhat darker than full white
- add PointLight2D, set texture to GradientTexture2D
- create radial falloff texture: white at center to black at sides
- set texture dimensions to 30x30 pixels
- move light into the polygon
- run project, be amazed
- set gradient light texture dimensions to 32x32 pixels
- run project, no it's fine

### Minimal reproduction project

[New Game Project.zip](https://github.com/godotengine/godot/files/12719619/New.Game.Project.zip)
Repository: stable-diffusion-webui
Issue: [Bug]: Installation crashes due to insufficient disk space
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?

Calling ./webui.sh crashes with this message:

```
  Downloading https://download.pytorch.org/whl/cu118/torch-2.0.1%2Bcu118-cp310-cp310-linux_x86_64.whl (2267.3 MB)
     ━━━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━ 0.8/2.3 GB 32.7 MB/s eta 0:00:45ERROR: Could not install packages due to an OSError: [Errno 28] Auf dem Gerät ist kein Speicherplatz mehr verfügbar

     ━━━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━ 0.8/2.3 GB 32.6 MB/s eta 0:00:45
```

Which is impossible: there is more than 300GB free disk space at this point. The only disk space that is limited is `/tmp/` (2GB RAM-Disk). Therefore, I believe the setup routine tries to download the necessary files to that directory. 



### Steps to reproduce the problem

Just start webui.sh on a system with /tmp limited to 2GB.

### What should have happened?

The setup routine should check the available space for downloading, and ask for some other temporary space to save the download if /tmp/ is too small.

### Sysinfo

System info file has not been created, because the set up crashes.

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

Mozilla Firefox

### Console logs

```Shell
Downloading https://download.pytorch.org/whl/cu118/torch-2.0.1%2Bcu118-cp310-cp310-linux_x86_64.whl (2267.3 MB)
     ━━━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━ 0.8/2.3 GB 32.7 MB/s eta 0:00:45ERROR: Could not install packages due to an OSError: [Errno 28] Auf dem Gerät ist kein Speicherplatz mehr verfügbar

     ━━━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━ 0.8/2.3 GB 32.6 MB/s eta 0:00:45
```


### Additional information

_No response_
Repository: svelte
Issue: a11y-no-redundant-roles warning misidentifies an implicit role
Labels: a11y

### Describe the bug

The a11y-no-redundant-roles warning correctly identifies that < a href="http://somelink.com" role="link"></a > has a redundant role because an anchor tag with an href has an implicit role (link) in HTML5. However, the redundant role warning should not appear when < a role="link"></a > html is used, because HTML5 does not implicitly assign the link role to anchor tags without hrefs. 

### Reproduction

"< a role="link"></ a>"

A11y: Redundant role 'link' svelte(a11y-no-redundant-roles)

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 13.5.2
    CPU: (8) arm64 Apple M1
    Memory: 1.55 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.1 - /usr/local/bin/node
    npm: 9.6.7 - /usr/local/bin/npm
  Browsers:
    Chrome: 117.0.5938.92
    Safari: 16.6
  npmPackages:
    svelte: ^3.46.0 => 3.57.0
```


### Severity

annoyance