sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: [sig-cloud-provider] Hybrid cloud native support. 
Labels: kind/feature,sig/cloud-provider,triage/accepted

### What would you like to be added?

CLI global flag `--hybrid-cloud=true`

### Why is this needed?

It's possible to run multiple CCMs in one cluster, but it requires a deep understanding of how the cloud provider works. In some cases, we need to add a few checks or extra logic on the CCM side.

The `node-controller` functions properly; only one CCM can find and initialize the node, while others skip it with an error or log message.

With the node-lifecycle-controller, we need to incorporate more checks into each CCM because we cannot determine if an instance exists or not. For instance, Azure-CCM always responds that the instance exists and is not switched off if the ProviderID is not Azure. The CCM responsible for this cloud can make the correct decision. I believe these checks are better made on the cloud provider side.


When a CCM starts, it registers the name of the cloud using 'cloudprovider.RegisterCloudProvider'. This name usually exists in the ProviderID `cloud-provider-name://`. For example, we can add the CLI global flag `--hybrid-cloud=true`, which will use this name from `RegisterCloudProvider` to check the prefix in the ProviderID. If it does not match, the functions `InstanceExists` and `InstanceShutdown` will not be called.

/sig cloud-provider
Repository: next.js
Issue: Rsc header and query params always null on middleware
Labels: Middleware

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/nextjs-middleware-get-rsc-query-params-and-header-vfy9hk?file=%2Fmiddleware.ts%3A23%2C15

### To Reproduce

1. Go to https://codesandbox.io/p/devbox/nextjs-middleware-get-rsc-query-params-and-header-vfy9hk?file=%2Fmiddleware.ts%3A23%2C15
2. Open network tab on your browser
3. Clique on link "Page2?test=1"
4. You will a request to "https://vfy9hk-3000.csb.app/page2?test=1&_rsc=1dou9"


### Current vs. Expected behavior

Check console query params test is successfully log but _rsc params is null. rsc header is also null
![image](https://github.com/vercel/next.js/assets/18116930/997f2677-face-414a-817e-1e6226af994b)

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.3.0-canary.63 // Latest available version is detected (14.3.0-canary.63).
  eslint-config-next: N/A
  react: 19.0.0-beta-4508873393-20240430
  react-dom: 19.0.0-beta-4508873393-20240430
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed)

### Additional context

_No response_
Repository: material-ui
Issue: [@mui/joy] `components` is not in `Theme` type
Labels: on hold,typescript,package: joy-ui

### Steps to reproduce

Link to live example: (required)
https://codesandbox.io/p/sandbox/morning-brook-wjkmj4?file=%2Fsrc%2FDemo.tsx

Steps:
1. Try to use `components` from `useTheme` result
2. TS Error


### Current behavior

There is a TS error when trying to access `theme.components` even though it is definitely there.
<img width="856" alt="image" src="https://github.com/mui/material-ui/assets/9912830/28fbd4d0-2dda-42fa-81f2-8264a797b922">


### Expected behavior

I think `components` should be part of the `Theme` type by default, even if it's an optional type - I have to override `Theme` type for it to work as expected

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```

  System:
    OS: macOS 14.4.1
  Binaries:
    Node: 21.6.0 - /usr/local/bin/node
    npm: 10.2.4 - /usr/local/bin/npm
    pnpm: 9.0.6 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 124.0.6367.207
    Edge: 124.0.2478.105
    Safari: 17.4.1
  npmPackages:
    @mui/base: 5.0.0-beta.40 => 5.0.0-beta.40 
    @mui/private-theming:  5.15.14 
    @mui/styled-engine:  5.15.14 
    @mui/system: ^5.15.15 => 5.15.15 
    @mui/utils:  5.15.14 
```
</details>


**Search keywords**: mui, joy, theme, components, type
Repository: pytorch
Issue: torch script not support ModuleList/Sequential  ? 
Labels: oncall: jit

### 🐛 Describe the bug

```python  
import torch
import torch.nn as nn
from typing import List

class ResNetFusion(nn.Module):
    def __init__(self, out_channels=256, inter_channels=256):
        super(ResNetFusion, self).__init__()

        self.inter_channels = inter_channels
        self.layers = nn.Sequential(nn.Linear(inter_channels, out_channels), nn.LayerNorm(out_channels))
        self.layer_norm = nn.Sequential(nn.Linear(inter_channels, out_channels), nn.LayerNorm(out_channels))

    @torch.jit.script
    def forward(self, x:List[torch.Tensor]):
        x = torch.cat(x, 1).contiguous() # [1, 256, 200, 200]

        for _, layer in enumerate(self.layers):
            x = layer(x)
        x = x.reshape(x.shape[0], x.shape[1], -1).permute(0, 2, 1)  
        x = self.layer_norm(x)
        return x
    
res = ResNetFusion()

traced_model = torch.jit.trace(res, torch.randn(1,128,200,200), torch.randn(1,128,200,200))
print(traced_model)    
```

error arise   
```
RuntimeError:
'Tensor (inferred)' object has no attribute or method 'layers'.:
  File "./export_fusion_script.py", line 132
        x = torch.cat(x, 1).contiguous() # [1, 256, 200, 200]

        for _, layer in enumerate(self.layers):
                                  ~~~~~~~~~~~ <--- HERE
            x = layer(x)
        x = x.reshape(x.shape[0], x.shape[1], -1).permute(0, 2, 1)
```
How to slove it ?

### Versions

torch                     1.10.0+cu113      
torchaudio                0.10.0+cu113    
torchvision               0.11.0+cu113    

### OTH-similar case     
https://github.com/pytorch/pytorch/issues/38034    
https://github.com/pytorch/pytorch/issues/34302    
https://github.com/pytorch/pytorch/pull/29236     
https://discuss.pytorch.org/t/torchscript-does-not-support-assigning-output-of-module-to-element-of-tensor/108371   

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: PowerToys
Issue: Modifier key (CTRL) remains stuck
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I have a Lenovo ThinkBook 16p. This one has 2 parenthesis (open/close) keys over the numeric keypad. Having that in mind (perhaps it matters), i have assigned CTRL+ ) (which was translated to CTRL+SHIFT + 0) to Media->Next track.

Whenever i press this combination with the key in the numeric keypad [ Right CTRL + ) ], after i release them the CTRL key seems to remain pressed, so whenever i click any other key, (p for instance), the laptop acts as if i had pressed CTRL + the key (CTRL+p in this case, which usually opens the Print dialog).

Pressing the two CTRL keys simultaneously causes CTRL to unstuck.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: go
Issue: proposal: slices: add functions MinNFunc and MaxNFunc
Labels: Proposal

### Proposal Details

I propose the addition of a function

    func MinNFunc[S ~[]E, E any](n int, x S, cmp func(a, b E) int) S

which returns the `n` smallest elements of `x` in increasing order.  If `len(x) < n`, then `MinNFunc` returns `x` sorted.

`MinNFunc(n, x, cmp)` is equivalent to
```
    y := SortFunc(x, cmp)
    if len(y) < n {
        return y
    }
    return y[:n]
```
but it avoids an allocation of size O(`len(x)`).

For symmetry, there could be a function `MaxNFunc` which returns the `n` largest elements of `x` in decreasing order.  `MaxNFunc(n, x, cmp)` is equivalent to
```
MinNFunc(n, x, func(a, b E) int {
    return -cmp(a, b)
})
```
Repository: go
Issue: proposal: maps: add function to check existence of a key
Labels: Proposal

### Proposal Details

[A lot of code](https://github.com/search?q=language%3AGo+%2Fif+_%2C+ok+%3A%3D+.*%3F%5C%5B.*%3F%5C%5D%3B+ok%2F&type=code) uses pattern like this:

```go
if _, ok := somemap[somekey]; ok {
    ...
}
```

just to check if key exists in a map.

And, with `*Func` functions from `strings`, `slices`, etc packages it makes code look unnecessary ugly.
For example, to filter out elements of a slice that exist in a map you need to do this:

```go
type Buzz struct {
    ID string
}

var fizzies map[string]int
var buzzies []Buzz

...

buzzies = slices.DeleteFunc(buzzies, func (buzz Buzz) bool {
    _, ok := fizzies[buzz.ID]
    return ok
})
```

Instead of, let's say, this:

```go
buzzies = slices.DeleteFunc(buzzies, func (buzz Buzz) bool {
    return maps.Contains(fizzies, buzz.ID)
})
```

That might be subjective, but one-line return statement looks less clunky.

I deliberately used this example because simple one, with `var buzzies []string` might raise unnecessary questions like "why not add something like `HasKeyFunc(map[K]V) func(K) bool`" which will make this example look like this:

```go
buzzies = slices.DeleteFunc(buzzies, maps.HasKeyFunc(fizzies))
```

Which looks pretty, but doesn't make other cases any more readable than first example.

### Bike-shedding section

I don't care about naming, but already implied `maps.Contains` because it's common across std.  

One might argue that semantics of e.g. `slices.Contains` differ from `maps.Contains` because `slices.Contains` uses slice values instead of indices.  
But there is an opposite argument of `delete(map, key)` that follows this pattern for maps while `slices.Delete` uses indices instead of values.
Repository: pytorch
Issue: Erroneous Conda Windows MKL dependency
Labels: module: binaries,module: windows,triaged,module: mkl,module: intel

https://github.com/pytorch/pytorch/blob/a0aaf561143d265c246631e4f57a716994965406/setup.py#L1112

This line adds a dependency to the python package on `mkl >=2021.1.1,<=2021.4.0` on windows. However, the built conda packages do not align with this requirement. 

For instance take the conda package `win-64_pytorch-2.3.0-py3.12_cuda11.8_cudnn8_0`:

The PKG_INFO inside the package lists:

```
Requires-Dist: mkl<=2021.4.0,>=2021.1.1; platform_system == "Windows"
```

However the `index.json` has:

```json
  "depends": [
    ...
    "mkl 2023.1.*",
    ...
  ],
```

Running pip-check will fail.

However, the conda package `win-64_pytorch-2.3.0-py3.9_cuda11.8_cudnn8_0` (note the `py3.9`) does specify:

```json
  "depends": [
    ...
    "mkl 2021.4.*",
    ...
  ],
```

I think its because of these lines in the `meta.yaml`:

https://github.com/pytorch/builder/blob/a4b440ec0f687c84d089310d68ae3345d6eca7fc/conda/pytorch-nightly/meta.yaml#L26-27

Regardless, I think this dependency should depend on the BLAS implementation chosen, if BLAS is not set to mkl I think this dependency shouldn't be there in the first place.

cc @seemethere @malfet @osalpekar @atalman @peterjc123 @mszhanyi @skyline75489 @nbcsm @vladimir-aubrecht @iremyux @Blackhex @cristianPanaite @frank-wei @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10
Repository: godot
Issue: Editor Viewport Settings is Forgetful! (Not saved in any manner)
Labels: enhancement,discussion,topic:editor,needs testing,topic:3d

### Tested versions

Reproduced in Godot v4.2.2.stable

### System information

Godot v4.2.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Ti (NVIDIA; 31.0.15.3623) - 12th Gen Intel(R) Core(TM) i9-12900K (24 Threads)

### Issue description

Change the view settings to have a View Z-Near of 0.01 and a View Z-Far of 500.
Open another scene and it will reset to the defaults.

### Steps to reproduce

1. Open "scene a" and change the view settings to have a View Z-Near of 0.01 and a View Z-Far of 500.
2. Open "scene b" and look at the view settings, it will reset to the defaults.

### Minimal reproduction project (MRP)

N/A
Repository: go
Issue: x/build/internal/installer/{darwinpkg,windowsmsi}: report if GOTOOLCHAIN in environment is set to an older version than one being installed
Labels: Builders,NeedsInvestigation,FeatureRequest

When an installer for a certain Go version runs, it can check if the environment is configured such that `go version` would select select an older toolchain than the one being installed, and potentially highlight that to the user. (Another option may be to modify `GOTOOLCHAIN` in environment, either automatically or after prompting, but this might be trickier to get right.)

For example, suppose someone installs Go 1.22.0 with an installer, then later upgrades to Go 1.22.1 by setting `go env -w GOTOOLCHAIN=go1.22.1+auto`, then later on uses the installer once again to install a Go 1.22.2 local toolchain. Unless they change the `GOTOOLCHAIN` value in the environment, the installer would be a no-op, so it might be a good thing to report to the user, in case it was unintentional on their part.

(The macOS installer already has a few checks at https://cs.opensource.google/go/x/build/+/master:internal/installer/darwinpkg/_data/dist.xml;l=17-28;drc=0ce25ffd88baa2eb34517f5c0528e4a79d5e924f.)

Thanks to @hyangah for suggesting this.
Repository: material-ui
Issue: [material-ui] possibility to override defaultProps of custom styled components 
Labels: new feature,waiting for 👍,package: system,package: material-ui

### Summary

following this i am creating themed components: https://mui.com/material-ui/customization/theme-components/#creating-new-component-variants

styled overrides work fine, but now i would like to override defaultProps from the theme as well, this is not possible currently.

would it be possible at least to override defaultProps from inside the styled()({ .... }) declaration ?

### Examples

_No response_

### Motivation

_No response_

**Search keywords**: theme components
Repository: vscode
Issue: VSCode started with `--extensionDevelopmentPath` crashes after the computer enters in sleep mode
Labels: bug,extension-host,remote

<!-- ⚠️⚠️ 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.89.1

Steps to Reproduce:

1. Generate a new web extension using `yo code` (named `test-vscode-web-extension`)
2. Run `code --extensionDevelopmentPath=C:\Users\poweruser\Desktop\test-vscode-web-extension` .
3. Open a folder from WSL:
![image](https://github.com/microsoft/vscode/assets/4996054/55114fb1-2d28-4653-862d-a2d4a2be90ff)
4. Enter the computer in `sleep` mode
5.  When the computer is opened again, the vscode is not running anymore

When entering the sleep mode the logs looks like this :
![image](https://github.com/microsoft/vscode/assets/4996054/66eb4679-a95a-43ea-9a8a-d7d8205a5fc9)

![image](https://github.com/microsoft/vscode/assets/4996054/8b313402-7182-465d-816b-603003013149)

I checked the logs also when the vs code is recovering ok from the sleep mode (when started without the  `test-vscode-web-extension` extension i.e. without the `--extensionDevelopmentPath` as an argument). And the following entries are appearing in the logs in this case (and are missing from the logs when the vscode crashes):
![image](https://github.com/microsoft/vscode/assets/4996054/b25599e9-c723-4059-9061-69c4cf922863)

The problem doesn't appear if no folder is open or the folders are opened from Windows (not from WSL).

Does anybody know about this problem and maybe a possible fix for it?
Repository: next.js
Issue: Next.js v14.2 creates source map issues with various components in VS Code debugger
Labels: bug,linear: next

### Link to the code that reproduces this issue

https://github.com/andyvanosdale/nextjs-vscode-debug-read-source-map-issue

### To Reproduce

1. run `npx create-next-app`
2. Start the VS Code debugger running the npm script `dev`
3. Navigate to the Debug Console tab in VS Code
4. Load the home page in a browser

### Current vs. Expected behavior

Current behavior: VS Code's Debug Console shows this error:

> Could not read source map for file:///Users/oz/src/github.com/andyvanosdale/nextjs-vscode-debug-read-source-map-issue/.next/server/vendor-chunks/next.js: ENOENT: no such file or directory, open '/Users/oz/src/github.com/andyvanosdale/nextjs-vscode-debug-read-source-map-issue/.next/server/vendor-chunks/render-from-template-context.js.map'

This also occurs with:
* `link.js.map`
* `image-component.map`

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
  Available memory (MB): 65536
  Available CPU cores: 12
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.3.0-canary.63 // Latest available version is detected (14.3.0-canary.63).
  eslint-config-next: N/A
  react: 19.0.0-beta-4508873393-20240430
  react-dom: 19.0.0-beta-4508873393-20240430
  typescript: 5.1.3
Next.js Config:
  output: N/A

VS Code:
Version: 1.89.1 (Universal)
Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07T05:14:24.611Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.5.0
```


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

Developer Experience

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

next dev (local)

### Additional context

_No response_
Repository: pytorch
Issue: Adopt inductor-perf-test-nightly.yml to be used for release testing
Labels: module: binaries,triaged

### 🐛 Describe the bug

After running the release/2.2 and release/2.3 inductor testing and receiving the results:
https://hud.pytorch.org/benchmark/compilers?startTime=Fri%2C%2003%20May%202024%2001%3A00%3A54%20GMT&stopTime=Fri%2C%2010%20May%202024%2001%3A00%3A54%20GMT&granularity=hour&suite=torchbench&mode=training&dtype=amp&lBranch=release%2F2.3&lCommit=97ff6cfd9c86c5c09d7ce775ab64ec5c99230f5d&rBranch=release%2F2.2&rCommit=39901f229520a5256505ec24782f716ee7ddc843

Looks like the build: https://github.com/pytorch/pytorch/blob/main/.github/workflows/inductor-perf-test-nightly.yml
Being tested during this workflow is missing correct cuda/triton dependencies.
This is what i see in Metadata:
```
Requires-Dist: filelock
Requires-Dist: typing-extensions >=4.8.0
Requires-Dist: sympy
Requires-Dist: networkx
Requires-Dist: jinja2
Requires-Dist: fsspec
Requires-Dist: mkl <=2021.4.0,>=2021.1.1 ; platform_system == "Windows"
Provides-Extra: opt-einsum
Requires-Dist: opt-einsum >=3.3 ; extra == 'opt-einsum'
Provides-Extra: optree
Requires-Dist: optree >=0.9.1 ; extra == 'optree'
```
Also do not see triton version in the install script: https://github.com/pytorch/pytorch/actions/runs/8992882383/job/24709147395#step:18:133

The trtion and cuda versions are built into the docker image here: https://github.com/pytorch/pytorch/actions/workflows/docker-builds.yml

Hence we are testing pytorch build with the same pinned triton version.

We want to test exact wheel being compiled similar to the release.

### Versions

2.4.0

cc @seemethere @malfet @osalpekar
Repository: next.js
Issue: Using export dynamic = 'auto' opts you into dynamic rendering
Labels: bug,Performance,Runtime

### Link to the code that reproduces this issue

https://github.com/MangoMarcus/nextjs-dynamic-auto

### To Reproduce

1. Clone the repository. There's a seperate route for each of the options for [dynamic](https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#dynamic), plus one for none.
2. Deploy to Vercel
3. Check the "Deployment summary" under the deployment.
4. The `/none` route is an ISR function, but `/auto` isn't

### Current vs. Expected behavior

I expected the default for [dynamic](https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#dynamic) to be 'auto', but using that actually opts you in to dynamic rendering - which is not the same behavior as omitting the export altogether.

### Provide environment information

```bash
Operating System:
  Platform: macOS
  Chip: Apple M1 Pro
  Version: macOS 14.4
Binaries:
  Node: 20.2.0
  npm: 9.6.6
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.3
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Performance, Runtime

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

Vercel (Deployed)

### Additional context

<img width="1261" alt="Screenshot 2024-05-15 at 15 45 55" src="https://github.com/vercel/next.js/assets/72021142/4811c554-440d-45ae-b717-0c13dfabc2c8">
Repository: go
Issue: net/http: TestCmdGoNoHTTPServer failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestCmdGoNoHTTPServer"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8747924545551249681)):

    === RUN   TestCmdGoNoHTTPServer
    === PAUSE TestCmdGoNoHTTPServer


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: runtime:cpu4: TestUsingVDSO failures
Labels: help wanted,NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "runtime:cpu4" && test == "TestUsingVDSO"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8747866791326770913)):

    === RUN   TestUsingVDSO
    === PAUSE TestUsingVDSO
    === CONT  TestUsingVDSO
        vdso_test.go:51: GO_WANT_HELPER_PROCESS=1 /bin/strace -f -e clock_gettime /home/swarming/.swarming/w/ir/x/t/go-build3885972143/b001/runtime.test -test.run=^TestUsingVDSO$
        vdso_test.go:57: /bin/strace: Process 140051 attached
            /bin/strace: Process 140052 attached
            /bin/strace: Process 140050 attached
            /bin/strace: Process 140053 attached
            [pid 140050] ???( <unfinished ...>
            [pid 140049] --- stopped by SIGURG ---
            /bin/strace: ptrace(PTRACE_LISTEN,pid:140049,sig:0): Input/output error
            /bin/strace: Process 140049 detached
            /bin/strace: Process 140051 detached
            /bin/strace: Process 140052 detached
            /bin/strace: Process 140050 detached
            /bin/strace: Process 140053 detached
        vdso_test.go:70: exit status 1
    --- FAIL: TestUsingVDSO (0.14s)


— [watchflakes](https://go.dev/wiki/Watchflakes)