sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Editor.cursorSurroundingLines broken with update to 1.86
Labels: bug,editor-sticky-scroll

Type: <b>Bug</b>

After updating to 1.86, the editor always gives a minimum of 5 context lines above the cursor rather than the value set in editor.cursorSurroundingLines. I confirmed this by downgrading to 1.85.2, and the setting worked as expected. I upgraded again to 1.86 and disabled all extensions, and the problem still exists. Setting editor.cursorSurroundingLines to numbers higher than 5 works as expected, and numbers lower than 5 work below the cursor as expected, just not above it.

VS Code version: Code 1.86.0 (05047486b6df5eb8d44b2ecd70ea3bdf775fd937, 2024-01-31T10:27:46.147Z)
OS version: Linux x64 6.5.0-15-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i9-12950HX (16 x 2496)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: disabled_off|
|Load (avg)|2, 3, 2|
|Memory (System)|31.32GB (27.24GB free)|
|Process Argv|--unity-launch --crash-reporter-id 4b5216b9-19d9-4922-a351-34399b68482e|
|Screen Reader|no|
|VM|100%|
|DESKTOP_SESSION|ubuntu|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu|
|XDG_SESSION_TYPE|wayland|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627cf:30244335
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
0bi6i642:30951795
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019bcf:30953938
7j2b6412:30949929

```

</details>

<!-- generated by issue reporter -->
Repository: material-ui
Issue: [joy-ui][Card] Make orientation Responsive 
Labels: new feature,waiting for 👍,component: card,package: joy-ui

### Summary

I ended up in a situation where doing this:

```tsx
<Card orientation={{xs: "vertical", md: "horizontal"}}>
	<NarrowContent/>
	<Divider />
	<WideContent/>
</Card>
```

would achieve result I want, that's about it.

Whilst writing this I thought that I would do it like I used to with `useMediaQuery` but turns out it's not in joy - https://github.com/mui/material-ui/issues/35037, so I guess I'll copy-paste content and display-hide/block it for now.

update: tried to extract content into it's own `<MyCardContent/>`:
```tsx
<Card orientation="horizontal" sx={{ display: { xs: "none", md: "flex" } }}>
	<MyCardContent />
</Card>
<Card orientation="vertical" sx={{ display: { xs: "flex", md: "none" } }}>
	<MyCardContent />
</Card>
```

and that kinda failed because `<Divider/>` stopped behaving because it's no longer a direct child of Card, I'm kind of at a loss what to do.


### Examples

_No response_

### Motivation

_No response_

**Search keywords**: joy card orientation vertical horizontal responsive mobile desktop
Repository: kubernetes
Issue: Generated go clients do not warn about side-effects to arguments
Labels: kind/documentation,sig/api-machinery,triage/accepted

### What happened?

Bug #82497 is still with us. But the generated go client code does not warn the caller about this booby trap. This problem is NOT obvious to the reader of generated code, and the reader should be warned. See https://github.com/kubernetes/client-go/blob/v0.24.6/kubernetes/typed/apps/v1/deployment.go#L46 for an example.

### What did you expect to happen?

A method that logically takes an argument only as input would not side-effect it, at least not without clearly warning me.

### How can we reproduce it (as minimally and precisely as possible)?

See above

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

Current and many previous.

</details>


### Cloud provider

<details>
N/A
</details>


### OS version

<details>
N/A
</details>


### Install tools

<details>
N/A
</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: create-react-app
Issue: dependencies are borked; will matter when deprecation kicks in
Labels: needs triage,issue: bug report

One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.

babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.
Repository: pytorch
Issue: torch.bmm fails when multiplying a batch of sparse matrices by a dense tensor
Labels: module: sparse,triaged

### 🐛 Describe the bug

When I try to multiply a batch of sparse matrices of shape (B, N, N) by a dense tensor of shape (B, N, 1) using ```torch.bmm```, the following error is thrown:
```RuntimeError: CUDA error: misaligned address```

However, no error is thrown when multiplying the batch of sparse matrices by a dense tensor of shape (B, N, D), with D>1. 

Code to reproduce the first case: 

```
import torch

n_nodes = 10
n_edges = 20
batch_size = 2

sparse_list = []
for i in range(batch_size):
    indices = torch.randint(0, n_nodes, (2, n_edges))
    values = torch.randn(n_edges)
    size = (n_nodes, n_nodes)
    sparse_list.append(torch.sparse_coo_tensor(indices, values, size))

batch_sparse_tensor = torch.stack(sparse_list).coalesce()

device = torch.device('cuda:1')

batch_sparse_tensor = batch_sparse_tensor.to(device)

f_random = torch.randn(batch_size, n_nodes, 1).to(device)

torch.bmm(batch_sparse_tensor, f_random)
```

Code to reproduce the second case:

```
import torch

n_nodes = 10
n_edges = 20
batch_size = 2
D=100

sparse_list = []
for i in range(batch_size):
    indices = torch.randint(0, n_nodes, (2, n_edges))
    values = torch.randn(n_edges)
    size = (n_nodes, n_nodes)
    sparse_list.append(torch.sparse_coo_tensor(indices, values, size))

batch_sparse_tensor = torch.stack(sparse_list).coalesce()

device = torch.device('cuda:1')

batch_sparse_tensor = batch_sparse_tensor.to(device)

h_random = torch.randn(batch_size, n_nodes, D).to(device)

torch.bmm(batch_sparse_tensor, h_random)
```

### Versions

PyTorch version: 2.1.2+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: AlmaLinux 8.8 (Sapphire Caracal) (x86_64)
GCC version: (GCC) 8.5.0 20210514 (Red Hat 8.5.0-18)
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.28

Python version: 3.9.18 (main, Sep 11 2023, 13:41:44)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-4.18.0-477.21.1.el8_8.x86_64-x86_64-with-glibc2.28
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: 
GPU 0: NVIDIA GeForce RTX 3090
GPU 1: NVIDIA GeForce RTX 3090
GPU 2: NVIDIA GeForce RTX 3090
GPU 3: NVIDIA GeForce RTX 3090

Nvidia driver version: 535.104.05
cuDNN version: Could not collect

Versions of relevant libraries:
[pip3] numpy==1.26.3
[pip3] torch==2.1.2
[pip3] torch_geometric==2.4.0
[pip3] torchvision==0.16.2
[pip3] triton==2.1.0
[conda] numpy                     1.26.3                   pypi_0    pypi
[conda] torch                     2.1.2                    pypi_0    pypi
[conda] torch-geometric           2.4.0                    pypi_0    pypi
[conda] torchvision               0.16.2                   pypi_0    pypi
[conda] triton

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: go
Issue: x/tools/gopls: unusedparams analyzer reports false positive due to build tags
Labels: gopls,Tools,Analysis,gopls/analysis

```
xtools$ go run ./gopls/internal/analysis/unusedparams/cmd/main.go -c 3 ./gopls/internal/test/integration/fake
/Users/adonovan/w/xtools/gopls/internal/test/integration/fake/workdir.go:75:38: unused parameter: err
72	
73	// isWindowsErrLockViolation reports whether err is ERROR_LOCK_VIOLATION
74	// on Windows.
75	var isWindowsErrLockViolation = func(err error) bool { return false }
76	
```

The analysis believes that this function is assigned to a variable that is only ever used in call position--because it is never used at all. In fact it is used in non-call position, for an assignment to the variable, though only in a file tagged for GOOS=windows, which of course the analysis cannot see. Consequently it falsely reports  that the parameter can be safely removed.

One possibility would be to observe that pass.IgnoredGoFiles contains one or more files, in particular files with build tags, and to conservatively assume that these extra files contain assignments to all variables such as isWindowsErrLockViolation.

This is really a representative for a whole class of built-tag-related analyzer problems.
Repository: vscode
Issue: [folding] Add Code Folding Actions to the Undo Stack
Labels: feature-request,editor-folding

<!-- ⚠️⚠️ 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. -->
As a developer, I would like to be able to revert code folding actions quickly and intuitively using the standard "Undo" command (<kbd>⌘</kbd> <kbd>Z</kbd> on macOS).  A user or workspace setting to enable this would be greatly appreciated.

## Steps to Reproduce
1. Click the disclosure triangle in the gutter (or press <kbd>⌥</kbd> <kbd>⌘</kbd> <kbd>[</kbd>) to collapse a block of code.
2. Press <kbd>⌘</kbd> <kbd>Z</kbd>.

## Expected Results
The folded block of code should be unfolded.

## Actual Results
The folded block remained folded, and the most recent code edit is reverted.

## VSCode Version
```
% code --version
1.85.2
c8a36a69377856369f139f39ee56dd3838130fbf
x64
```

## System Version
```
% sw_vers
ProductName:		macOS
ProductVersion:		13.6.3
BuildVersion:		22G436
```
Repository: storybook
Issue: [Bug]: "async/await is not yet supported in Client Components, only Server Components." - since 8.0.0--alpha.13
Labels: bug,react,nextjs,sev:S3,rsc

### Describe the bug

Since 8.0.0--alpha.13 there is an error in console.
The problem still exists in the latest 8.0.0--beta.0 version.

Error message:
> Warning: async/await is not yet supported in Client Components, only Server Components. This error is often caused by accidentally adding `'use client'` to a module that was originally written for the server.

![image](https://github.com/storybookjs/storybook/assets/14075940/bd43deb1-153d-4462-a1fa-69dbb0744b48)


### To Reproduce

Try to update storybook version for [repo](https://github.com/shilman/next-react-server-components) from storybook's official [article](https://storybook.js.org/blog/build-a-nextjs-app-with-rsc-msw-storybook/)



### System

```bash
System:
    OS: macOS 14.1.1
    CPU: (8) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm
    pnpm: 8.5.0 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Chrome: 121.0.6167.139
    Safari: 17.1
  npmPackages:
    @storybook/addon-essentials: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/addon-interactions: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/addon-links: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/blocks: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/nextjs: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/react: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    @storybook/test: 8.0.0-alpha.13 => 8.0.0-alpha.13 
    msw-storybook-addon: 2.0.0--canary.122.06f0c92.0 => 2.0.0--canary.122.06f0c92.0 
    storybook: 8.0.0-alpha.13 => 8.0.0-alpha.13
```


### Additional context

_No response_
Repository: transformers
Issue: TextStreamer: An option to print / put every single token instead of whole words
Labels: Feature request,Generation

### Feature request

https://github.com/huggingface/transformers/blob/v4.37.2/src/transformers/generation/streamers.py#L108-L114

The current implementation forces us to visualize decoding on a per word basis. Add an option to print the string as soon as it's generated.

### Motivation

I use TextStreamer to visualize several things in my terminal:
1. How words are split
2. Actual token-per-second performance
3. Understand how it generates very long words like URLs

### Your contribution

I'm a Python noob
Repository: go
Issue: x/build: LUCI builders fail to fetch dependencies for subrepos
Labels: Unfortunate,Builders,NeedsInvestigation

```
#!watchflakes
post <- mode == "build" && log ~ `Failed to run "fetch .*" dependencies`
```

(placeholder for watchflakes)
Repository: vscode
Issue: Adopt `ensureNoDisposablesAreLeakedInTestSuite` in `quickAccess.test.ts`
Labels: debt,quick-open

Original issue: https://github.com/microsoft/vscode/issues/200091

`src/vs/workbench/test/browser/quickAccess.test.ts` is a beast. It's gonna take me a some time to work through... mostly because a lot of the stuff was assumed to live on for the entire window, which makes sense given the area...

Opening this as a separate issue since it will take a fair amount of time.
Repository: godot
Issue: Vulkan error in console as pop-up boxes become blank due to ASUS GPUTweak
Labels: bug,platform:windows,topic:rendering,topic:thirdparty

### Tested versions

Reproduced in 4.2.1 and 4.2
Not reproducible in 3.5.3

### System information

Godot v4.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; 31.0.15.5123) - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

Whenever I open the new node dialog, after at most just a few seconds the dialog box freezes and I get a spam of Vulkan errors in the console which is the below three errors repeating endlessly. After this happens, the editor still seems to run but all the toolbar menus and any popups appear blank. (see attached pics)

ERROR: Vulkan: Cannot submit graphics queue. Error code: VK_ERROR_DEVICE_LOST
   at: (drivers/vulkan/vulkan_context.cpp:2536)
ERROR: Vulkan: Did not create swapchain successfully. Error code: VK_NOT_READY
   at: (drivers/vulkan/vulkan_context.cpp:2459)
ERROR: Vulkan: Did not create swapchain successfully. Error code: VK_NOT_READY
   at: (drivers/vulkan/vulkan_context.cpp:2459)

![Godotbug](https://github.com/godotengine/godot/assets/38431774/b73088ad-3d0b-4a65-a402-d7ab6226b90a)
![GodotBug2](https://github.com/godotengine/godot/assets/38431774/548f155f-3187-44c4-8172-7b6c6895d308)

### Steps to reproduce

Create a blank project.
Add any type of root node
Open 'new node' dialog

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: request.nextUrl received in middleware after server action redirect is wrong
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/redirect-aciton-error-t4mkg5?file=%2Fapp%2Fpage.tsx%3A17%2C37

### To Reproduce

1 - start application
2 - navigate to /
3 - click on the submit button

### Current vs. Expected behavior

current:
the url printed on the page stays https://localhost:3000/

expexted
the url on the page should change to https://localhost:3000/?hello=world

### Provide environment information

```bash
multiple envs. its possible to se on codesandbox
```


### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

After redirecting from an action, it seems that middleware is not receiving the correct href.

working on 14.1.1-canary.16
Repository: pytorch
Issue: [MPS] Tracking issue for ModuleInfo failures when enabling testing for `torch.float16`
Labels: triaged,module: mps

### 🐛 Describe the bug

Issue accompanying #119039. The following tests fail when I enable `torch.float16` ModuleInfo testing for MPS

#### Not specific to MPS (also fail on CPU and CUDA)
- [ ] `test_check_inplace_nn_CELU_mps_float16`
- [ ] `test_check_inplace_nn_ELU_mps_float16`

#### Errors with "error: input types 'tensor<f32>' and 'tensor<...f16>' are not broadcast compatible"
- [ ] `test_forward_nn_AvgPool2d_mps_float16`
- [ ] `test_forward_nn_BCELoss_mps_float16`
- [ ] `test_if_train_and_eval_modes_differ_nn_AvgPool2d_mps_float16`
- [ ] `test_if_train_and_eval_modes_differ_nn_BCELoss_mps_float16`
- [ ] `test_memory_format_nn_AvgPool2d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_AvgPool2d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_BCELoss_mps_float16`
- [ ] `test_pickle_nn_AvgPool2d_mps_float16`
- [ ] `test_pickle_nn_BCELoss_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_MSELoss_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_SmoothL1Loss_mps_float16`

#### Errors with "MPSNDArrayConvolutionA14.mm:3976: failed assertion `destination datatype must be fp32'"
- [ ] `test_memory_format_nn_Conv1d_mps_float16`
- [ ] `test_memory_format_nn_Conv2d_mps_float16`
- [ ] `test_memory_format_nn_ConvTranspose1d_mps_float16`
- [ ] `test_memory_format_nn_ConvTranspose2d_mps_float16`
- [ ] `test_memory_format_nn_LazyConv1d_mps_float16`
- [ ] `test_memory_format_nn_LazyConv2d_mps_float16`
- [ ] `test_memory_format_nn_LazyConvTranspose1d_mps_float16`
- [ ] `test_memory_format_nn_LazyConvTranspose2d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_Conv1d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_Conv2d_mps_float16 `
- [ ] `test_non_contiguous_tensors_nn_ConvTranspose1d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_ConvTranspose2d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_LazyConv1d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_LazyConv2d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_LazyConvTranspose1d_mps_float16`
- [ ] `test_non_contiguous_tensors_nn_LazyConvTranspose2d_mps_float16`

#### Tolerance errors
- [ ] `test_forward_nn_Bilinear_mps_float16`
- [ ] `test_forward_nn_BCEWithLogitsLoss_mps_float16`
- [ ] `test_forward_nn_GELU_mps_float16`
- [ ] `test_forward_nn_LogSigmoid_mps_float16`
- [ ] `test_forward_nn_MSELoss_mps_float16`
- [ ] `test_forward_nn_NLLLoss_mps_float16`
- [ ] `test_forward_nn_SoftMarginLoss_mps_float16`
- [ ] `test_forward_nn_Softmax2d_mps_float16`

#### inf nan error
- [ ] `test_forward_nn_LogSoftmax_mps_float16`

#### Incorrect output dtype? values for attribute 'dtype' do not match: torch.float16 != torch.float32.
- [ ] `test_forward_nn_HuberLoss_mps_float16`




### Versions

main

cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr
Repository: go
Issue: build: make.bash fail on LUCI darwin builders due to unexpected stale targets
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder ~ `(gotip|go1\.\d\d)-darwin-amd64` && mode == "build" && `go tool dist: unexpected stale targets`
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/ui/b/8759787751839774129)):

    HASH[moduleIndex]
    HASH[moduleIndex]: "devel 5c38c04957dd93db2f6f1d4a507031631976a122"
    HASH[moduleIndex]: "modroot /Volumes/Work/s/w/ir/x/w/goroot/src/cmd\n"
    HASH[moduleIndex]: "package devel 5c38c04957dd93db2f6f1d4a507031631976a122 go index v1 /Volumes/Work/s/w/ir/x/w/goroot/src/cmd/dist\n"
    HASH[moduleIndex]: "file README 2024-01-04 18:20:55.871835001 -0800 PST 1341\n"
    HASH[moduleIndex]: "file build.go 2024-01-04 18:20:55.871980374 -0800 PST 50355\n"
    HASH[moduleIndex]: "file buildgo.go 2024-01-04 18:20:55.872087275 -0800 PST 3495\n"
    HASH[moduleIndex]: "file buildruntime.go 2024-01-04 18:20:55.872180521 -0800 PST 2630\n"
    HASH[moduleIndex]: "file buildtag.go 2024-01-04 18:20:55.872265534 -0800 PST 3077\n"
    HASH[moduleIndex]: "file buildtag_test.go 2024-01-04 18:20:55.872409862 -0800 PST 1257\n"
    ...
    	STALE cmd/go: not installed but available in build cache
    	STALE cmd/gofmt: not installed but available in build cache
    	STALE cmd/link: not installed but available in build cache
    	STALE cmd/nm: not installed but available in build cache
    	STALE cmd/objdump: not installed but available in build cache
    	STALE cmd/pack: not installed but available in build cache
    	STALE cmd/pprof: not installed but available in build cache
    	STALE cmd/test2json: not installed but available in build cache
    	STALE cmd/trace: not installed but available in build cache
    	STALE cmd/vet: not installed but available in build cache


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: build: make.bash fail on LUCI solaris builder due to unexpected stale targets
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder ~ `(gotip|go1\.\d\d)-solaris-amd64` && mode == "build" && `go tool dist: unexpected stale targets`
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/ui/b/8757810555682226033)):

    Building Go cmd/dist using /opt/golang/swarm/.swarming/w/ir/cache/tools/go_bootstrap. (go1.21.0 solaris/amd64)
    Building Go toolchain1 using /opt/golang/swarm/.swarming/w/ir/cache/tools/go_bootstrap.
    Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
    Building Go toolchain2 using go_bootstrap and Go toolchain1.
    Building Go toolchain3 using go_bootstrap and Go toolchain2.
    Building packages and commands for solaris/amd64.
    HASH[moduleIndex]
    HASH[moduleIndex]: "devel b6d1eb750f274d5637e5eb63f6e03706798f0444"
    HASH[moduleIndex]: "modroot /opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/cmd\n"
    HASH[moduleIndex]: "package devel b6d1eb750f274d5637e5eb63f6e03706798f0444 X:nocoverageredesign,noallocheaders,noexectracer2 go index v2 /opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/cmd/link\n"
    ...
    HASH[moduleIndex]: "file testing_other.go 2024-01-26 21:16:34.049243738 +0100 CET 386\n"
    HASH[moduleIndex]: "file testing_test.go 2024-01-26 21:16:36.881132734 +0100 CET 19697\n"
    HASH[moduleIndex]: "file testing_windows.go 2024-01-26 21:16:34.049459512 +0100 CET 751\n"
    HASH[moduleIndex]: d48f350ed50fd9bad4c27d6d42a9f305cba82a8e3132ca8349ae076c2d006701
    cmd/link true
    go tool dist: unexpected stale targets reported by /opt/golang/swarm/.swarming/w/ir/x/w/goroot/pkg/tool/solaris_amd64/go_bootstrap list -gcflags="" -ldflags="" for [cmd/asm cmd/cgo cmd/compile cmd/link] (consider rerunning with GOMAXPROCS=1 GODEBUG=gocachehash=1):
    	STALE cmd/asm: stale dependency: internal/cpu
    	STALE cmd/cgo: stale dependency: internal/cpu
    	STALE cmd/compile: stale dependency: internal/cpu
    	STALE cmd/link: stale dependency: internal/cpu


— [watchflakes](https://go.dev/wiki/Watchflakes)