sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: fairseq distributed training dumps core with flash attention
Labels: triaged,module: sdpa

### 🐛 Describe the bug

When doing distributed training with Fairseq for an NMT model, flash attention core dumps. (Adding here for issue tracking, internal discussion for details).

The reported source location of the core dump is consistent across multiple repros:

```
Opening GPU coredump: /tmp/cudacoredump_6-gpu_A100.devgpu003.prn6.facebook.com.3918025.1686793663

CUDA Exception: Warp Illegal Address
The exception was triggered at PC 0x7f3279226060 (utils.h:819 in _ZN4fmha11Ldg_functorI5uint4Li1EE4loadEib inlined from utils.h:120)
[Current focus set to CUDA kernel 0, grid 200269, block (0,0,0), thread (0,0,0), device 0, sm 0, warp 1, lane 0]
#0  fmha_bwd_dot_do_o_kernel<FMHA_kernel_traits<256, 64, 16, 1, 8, 256u, __half> ><<<(2,16,3),(256,1,1)>>> ()
    at /re_cwd/./fbcode/third-party-buck/platform010/build/cuda/11.4.2/include/cuda_fp16.hpp:733 in _ZN54_INTERNAL_32_fmha_bwd_hdim64_cu_pic_o_cpp1_ii_a4e28c6c14__half22float2E7__half2 inlined from cuda_fp16.hpp:539
733 /re_cwd/./fbcode/third-party-buck/platform010/build/cuda/11.4.2/include/cuda_fp16.hpp: No such file or directory.
```

Repro internally by Wei Ho.
cc: @drisspg 

### Versions

fbcode trunk head

cc @jbschlosser @bhosmer @cpuhrsch @erichan1 @drisspg @mikaylagawarecki
Repository: PowerToys
Issue: [Mouse Without Borders] Sync Lock Key status
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Without Borders

### Description of the new feature / enhancement

I would like to see an option for the Lock Keys (Number, Capitals, Scroll, Function) to synced across machines.

### Scenario when this would be used?

While controlling a remote machine, the visual indicator for if a Lock key is toggled is not carried over.

### Supporting information

_No response_
Repository: flutter
Issue: [in_app_purchase_android] Replace use of deprecated BillingFlowParams.ProrationMode with new ReplacementMode enum
Labels: platform-android,p: in_app_purchase,package,P2,team-android,triaged-android

A dependabot upgrade to change the com.android.billingclient:billing version from 5.2.0 to 6.0.0 created deprecation warnings that needed to be suppressed. 

We should remove usages of the deprecated `BillingFlowParams.ProrationMode` and then remove the warning suppressions.

See the PR that introduced the suppressions https://github.com/flutter/packages/pull/3988, as well as the [documentation for the deprecated class](https://developer.android.com/reference/com/android/billingclient/api/BillingFlowParams.ProrationMode) (which includes a suggestion on what to replace with).
Repository: next.js
Issue: Abnormal filesystem activity 
Labels: Upstream,bug

### 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:44 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.6-canary.7
      eslint-config-next: 13.4.5
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
```


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

Operating System (Windows, MacOS, Linux)

### Link to the code that reproduces this issue or a replay of the bug

https://share.cleanshot.com/SYpRks7p

### To Reproduce

1. Create a new, blank Next.js project with `npx create-next-app@latest`. No TypeScript, just basic JavaScript (although the problem also exists for TypeScript enabled projects). 
2. Run `sudo fs_usage -w | grep 'Users/[username]/[projects-location]/' --line-buffered` to capture macOs' filesystem activity. 
3. Open the project in Visual Studio Code. Immediately after opening a few config files (although it's completely random), the filesystem usage will start an endless loop as you see in my screen capture. It's trying to access non-existent folders, such as `bower-components`.


### Describe the Bug

Endless loop of `fs_usage` activity, causing massive battery drain due to this abnormal behavior.

### Expected Behavior

This issue seems to be somewhat related to TypeScript. If I use a different code editor, such as Nova from Panic, and I disable TypeScript support for jsx files, the problem goes away. File system activity returns to normal. Immediately upon enabling TypeScript support for JavaScript, the loop starts yet again. 

Also tried with a clean installation of VSCodium without any extension installed. Same problem.

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

_No response_

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

_No response_
Repository: flutter
Issue: Picking from gallery in `image_picker` could be replaced by `file_selector`
Labels: p: image_picker,package,team-ecosystem,P2,p: file_selector,triaged-ecosystem

With `file_selector` now supporting every platform besides Android. (PR in progress: https://github.com/flutter/packages/pull/3814), the functionality of the two plugin now overlap. On most platforms the API to choose an image from the gallery is the same for any other file type and is already supported by `file_selector`. 

Replacing the functionality in `image_picker` with `file_selector` or removing it would reduce the maintenance burden of `image_picker`.
Repository: vscode
Issue: SCM - history provider proposed API
Labels: feature-request,api,scm,api-proposal

```ts
/*---------------------------------------------------------------------------------------------
 *  Copyright (c) Microsoft Corporation. All rights reserved.
 *  Licensed under the MIT License. See License.txt in the project root for license information.
 *--------------------------------------------------------------------------------------------*/

declare module 'vscode' {
	// https://github.com/microsoft/vscode/issues/185269

	export interface SourceControl {
		historyProvider?: SourceControlHistoryProvider;
	}

	export interface SourceControlHistoryProvider {
		currentHistoryItemGroup?: SourceControlHistoryItemGroup;

		/**
		 * Fires when the current history item group changes after
		 * a user action (ex: commit, checkout, fetch, pull, push)
		 */
		onDidChangeCurrentHistoryItemGroup: Event<void>;

		/**
		 * Fires when the history item groups change (ex: commit, push, fetch)
		 */
		// onDidChangeHistoryItemGroups: Event<SourceControlHistoryChangeEvent>;

		provideHistoryItems(historyItemGroupId: string, options: SourceControlHistoryOptions, token: CancellationToken): ProviderResult<SourceControlHistoryItem[]>;
		provideHistoryItemChanges(historyItemId: string, token: CancellationToken): ProviderResult<SourceControlHistoryItemChange[]>;

		resolveHistoryItemGroupBase(historyItemGroupId: string, token: CancellationToken): ProviderResult<SourceControlHistoryItemGroup | undefined>;
		resolveHistoryItemGroupCommonAncestor(historyItemGroupId1: string, historyItemGroupId: string, token: CancellationToken): ProviderResult<{ id: string; ahead: number; behind: number }>;
	}

	export interface SourceControlHistoryOptions {
		readonly cursor?: string;
		readonly limit?: number | { id?: string };
	}

	export interface SourceControlHistoryItemGroup {
		readonly id: string;
		readonly label: string;
		readonly upstream?: SourceControlRemoteHistoryItemGroup;
	}

	export interface SourceControlRemoteHistoryItemGroup {
		readonly id: string;
		readonly label: string;
	}

	export interface SourceControlHistoryItemStatistics {
		readonly files: number;
		readonly insertions: number;
		readonly deletions: number;
	}

	export interface SourceControlHistoryItem {
		readonly id: string;
		readonly parentIds: string[];
		readonly label: string;
		readonly description?: string;
		readonly icon?: Uri | { light: Uri; dark: Uri } | ThemeIcon;
		readonly timestamp?: number;
		readonly statistics?: SourceControlHistoryItemStatistics;
	}

	export interface SourceControlHistoryItemChange {
		readonly uri: Uri;
		readonly originalUri: Uri | undefined;
		readonly modifiedUri: Uri | undefined;
		readonly renameUri: Uri | undefined;
	}

	// export interface SourceControlHistoryChangeEvent {
	// 	readonly added: Iterable<SourceControlHistoryItemGroup>;
	// 	readonly removed: Iterable<SourceControlHistoryItemGroup>;
	// 	readonly modified: Iterable<SourceControlHistoryItemGroup>;
	// }

}
```
Repository: kubernetes
Issue: Kubectl Namespace defaulting logic is inconsistent
Labels: kind/documentation,sig/api-machinery,sig/cli,triage/accepted

This is effectively a re-open of https://github.com/kubernetes/kubernetes/issues/99884, but I think its slightly different. Basically my concern is the mixing of disparate kinds of clusters.  If you don't agree feel free to close - we have worked around it so this is more to avoid future users issues; it took us _3 years_ to figure it out (obviously not fully time :slightly_smiling_face: )

Kubectl has some namespace defaulting logic:

https://github.com/kubernetes/kubernetes/blob/cea1d4e20b4a7886d8ff65f34c6d4f95efcb4742/staging/src/k8s.io/client-go/tools/clientcmd/client_config.go#L593-L599 and https://github.com/kubernetes/kubernetes/blob/8bf42039e62d001f5d0331753bd99790b70d51eb/staging/src/k8s.io/client-go/tools/clientcmd/merged_client_builder.go#L120

This generally works fine. 

I get if we are "in cluster" we use in cluster config, and if KUBECONFIG is specified we use that. But we are currently mixing the two, which IMO is wrong.

For example, run a pod in namespace "A", then in the pod
```
$ gcloud cluster get-credentials ...
$ kubectl get pods
// Will use namespace "A" instead of default
```

My concern here is that we are mixing two disparate cluster configurations. The configuration for "in cluster" and for "external cluster" should not be mixed, they are configured two completely different things. To me, this is not so different from having a KUBECONFIG with 2 clusters and merging bits of the two together -- they should remain separate.

---

note for folks seeing this issue, the fix is to either set the namespace explicitly or `automountServiceAccountToken: false`

/sig cli
Repository: rust
Issue: bootstrap: Make `rust` options configurable per-stage
Labels: T-bootstrap,C-feature-request

There are several cases where it makes sense to have different configuration between different stages. A simple one is debuginfo - we enable `rust.debuginfo-level-std = 1` in dist builders, but only need it for stage 2, not stage 1. Another is optimization levels; for developing, it can make sense to build rustc with `optimize = true` but std with `optimize = false` (https://github.com/rust-lang/rust/issues/112678).

We should make it easier to configure this without using RUSTFLAGS_NOT_BOOTSTRAP, which is hard to discover and breaks caching if you get it wrong. I'm imagining something like `rust.stage1.debuginfo-level-std`, where *any* option under `rust` is allowed to be configured per-stage. This also implies that any option under `rust` should be applicable to a single stage; anything today that isn't should be moved to `build`.

Mentoring instructions:
1. Audit https://github.com/rust-lang/rust/blob/5dee431d87783cc9fff2e80613959594c20e3336/src/bootstrap/config.rs#L825-L876 for anything that doesn't make sense to set for only a single stage  (e.g. `channel`, `musl_root`, `rpath`).
2. Take the options from 1. and move them to `build`. I expect there to be a lot of these, so if possible add aliases from the old name to the new one - maybe add something like `struct MovedOptions { ... }` and then `#[serde(flatten)] renamed: MovedOptions` in both `Build` and `Rust`? Make an entry in src/bootstrap/changelog.md.
3. Add a new `struct PerStage<T> { stage0: T, stage1: T, stage2: T, default: T }` and use it everywhere in `Rust`; add it to the `define_config` macro if that makes it easier. This is based off of https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/def/struct.PerNS.html and should have similar apis.
4. Add tests for your change in `src/bootstrap/config/tests.rs`.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"onur-ozkan"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: storybook
Issue: [Bug]: @storybook/web-components-vite `RollupError: Unexpected token` in mdx
Labels: bug,help wanted,mdx,builder-vite

### Describe the bug

In an MDX file, I am writing documentation. Certain fenced code blocks with backticks result in a `RollupError` and as a result I am unable to build the storybook.

This bug appeared in my monorepo. I was able to reproduce in a fresh project using `npx storybook init`. 

Maybe there is something I'm missing in my `vite.config.js` or `package.json`?

### To Reproduce

`npx storybook init` and follow the prompts: 
- Select vite and web components

Then update `Introduction.mdx` to

~~~mdx
import { Meta } from '@storybook/blocks';

<Meta title="Example/Introduction" />

```js
/** @type { import('@storybook/web-components-vite').StorybookConfig } */
const config = {
  stories: ["../stories/**/*.mdx", "../stories/**/*.stories.@(js|jsx|ts|tsx)"],
  addons: ["@storybook/addon-links", "@storybook/addon-essentials"],
  framework: {
    name: "@storybook/web-components-vite",
    options: {}
  },
  refs: {
    example: {
      title: "example",
      url: process.env.NODE_ENV === "development" ? "http://localhost:6007/" : "example/"
    }
  },
  docs: {
    autodocs: "tag"
  }
};
export default config;
```
~~~




### System

```shell
System:
    OS: macOS 13.4
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 18.12.1 - /usr/local/bin/node
    Yarn: 3.5.0 - ~/.yarn/bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 114.0.5735.133
    Edge: 113.0.1774.57
    Firefox: 113.0.2
    Safari: 16.5
  npmPackages:
    @storybook/addon-essentials: ^7.0.21 => 7.0.21 
    @storybook/addon-links: ^7.0.21 => 7.0.21 
    @storybook/web-components: ^7.0.21 => 7.0.20 
    @storybook/web-components-vite: ^7.0.21 => 7.0.21
```


### Additional context

Error message:

```
Unexpected token (Note that you need plugins to import files that are not JavaScript)
file: /Users/name/Documents/project/packages/temp/stories/Introduction.mdx:21:481
19:     }
20:   },
21:   docs: {
             ^
22:     autodocs: "tag"
23:   }
ERR! RollupError: Unexpected token (Note that you need plugins to import files that are not JavaScript)
ERR!     at error (file:///Users/name/Documents/project/node_modules/vite/node_modules/rollup/dist/es/shared/node-entry.js:2213:30)
```
Repository: material-ui
Issue: [material-next] Add documentation on how to provide a custom theme for the Material You components
Labels: docs,component: button,ready to take,customization: theme

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:
https://codesandbox.io/s/pedantic-architecture-yjt5x5?file=/src/App.js
Steps:

1. Wrap app with ThemeProvider
2. use material-next button
3. app breaks


### Current behavior 😯

`Cannot read properties of undefined (reading 'color')`
But it works fine without the ThemeProvider.
I want to change the theme of the buttons and get the above error

### Expected behavior 🤔

It should work fine as the `@mui/material` button and should also work fine as it does without the ThemeProvider

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
 System:
    OS: macOS 13.3.1
  Binaries:
    Node: 20.2.0 - ~/.nvm/versions/node/v20.2.0/bin/node
    Yarn: Not Found
    npm: 9.6.6 - ~/.nvm/versions/node/v20.2.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.106
    Edge: Not Found
    Firefox: Not Found
    Safari: 16.4
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.4
    @mui/core-downloads-tracker:  5.13.4
    @mui/material: ^5.13.5 => 5.13.5
    @mui/material-next: ^6.0.0-alpha.89 => 6.0.0-alpha.89
    @mui/private-theming:  5.13.1
    @mui/styled-engine:  5.13.2
    @mui/system:  5.13.5
    @mui/types:  7.2.4
    @mui/utils:  5.13.1
    @types/react: ^17.0.0 => 17.0.59
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    typescript: ^4.9.5 => 4.9.5
```
</details>
Repository: flutter
Issue: Allow resetting the WebViewPlatform instance to initial state
Labels: c: new feature,p: webview,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

If we set the WebViewPlatform instance in one test, we cannot set it back to null after the instance is no longer needed.
```
  /// Platform-specific plugins should set this with their own platform-specific
  /// class that extends [WebViewPlatform] when they register themselves.
  static set instance(WebViewPlatform? instance) {
    if (instance == null) {
      throw AssertionError(
          'Platform interfaces can only be set to a non-null instance');
    }
    PlatformInterface.verify(instance, _token);
    _instance = instance;
  }
```

So if we mock the WebViewPlatform in one test, the other test would deal with the side effect of setting the mock.

```
class MockWebViewPlatform extends Mock
    with MockPlatformInterfaceMixin
    implements WebViewPlatform {}

main(){
  group('web view platforms do not have side effects', () {
    late final bool testWebViewPlatformWasCalled;

    test('Set instance in first test', () {
      testWebViewPlatformWasCalled = true;
      WebViewPlatform.instance = MockWebViewPlatform();
    });

    test('check if the WebViewPlatform instance is null', () {
      expect(
        testWebViewPlatformWasCalled,
        true,
        reason: 'We have to verify that the testWebViewPlatformWasCalled'
            ' is once executed so we can see if this affect this test',
      );
      expect(WebViewPlatform.instance, null);
    });
  });
}
```
The result of the second test would be as follows.
```
This test Fails with: 
Expected: <null>
Actual: MockWebViewPlatform:<MockWebViewPlatform>
```

This may cause undesired behaviour because the mock is still present. 

One solution would be to simply generate a new mock and set it, but we could not go back to the 'initial' state. 


### Proposal

 I would suggest something like the `debugNetworkImageHttpClientProvider`.
 
 flutter/packages/flutter/lib/src/painting/debug.dart

Somewhere there is a debugWebViewPlatformProvider field:
```
WebViewPlatform Function()? debugWebViewPlatformProvider;
```
And when we try to get the instance, we use it like this:
```
  /// The instance of [WebViewPlatform] to use.
  static WebViewPlatform? get instance {
    WebViewPlatform? result = _instance;
    assert(() {
      if (debugWebViewPlatformProvider != null) {
        final WebViewPlatform platform = debugWebViewPlatformProvider!();
        PlatformInterface.verify(platform, _token);
        result = platform;
      }
      return true;
    }());
    return result;
  }
```
Repository: tensorflow
Issue: Spurious(?) type inference failed warning for flattened tf.data.Dataset with a RaggedTensor
Labels: stat:awaiting tensorflower,type:bug,comp:data,TF 2.12

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Have you reproduced the bug with TF nightly?

Yes

### Source

binary

### Tensorflow Version

2.12.0

### Custom Code

Yes

### OS Platform and Distribution

Mac OS

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

As far as I can tell the code still runs as expected, but a seemly spurious warning is still issued.

The issue is pretty niche, removing the `_merge` function or the `vals` part to the initial dataset will make the error go away.

This occurs on 2.11, 2.12, and nightly on mac.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

labels = tf.ragged.constant([["a", "b"], ["a"]])
vals = tf.constant([0.1, 0.2])
ds = tf.data.Dataset.from_tensors(dict(labels=labels, vals=vals, other=vals))

parts = ["labels", "vals"]

def _flatten(ex):
  flat_ds = tf.data.Dataset.from_tensor_slices({k: ex[k] for k in parts})

  def _merge(_flat_ex):
    _flat_ex["other"] = tf.constant([0.1, 0.2])
    return _flat_ex

  return flat_ds.map(_merge)
ds = ds.flat_map(_flatten)

for ex in ds.as_numpy_iterator():
  print(ex)
```


### Relevant log output

```shell
2023-06-15 13:44:43.909272: W tensorflow/core/common_runtime/type_inference.cc:339] Type inference failed. This indicates an invalid graph that escaped type checking. Error message: INVALID_ARGUMENT: type mismatch for node 'TensorSliceDataset': expected a subtype of:
type_id: TFT_PRODUCT
args {
  type_id: TFT_DATASET
  args {
    type_id: TFT_PRODUCT
    args {
      type_id: TFT_TENSOR
      args {
        type_id: TFT_LEGACY_VARIANT
      }
    }
    args {
      type_id: TFT_TENSOR
      args {
        type_id: TFT_FLOAT
      }
    }
  }
}

  got:
type_id: TFT_PRODUCT
args {
  type_id: TFT_DATASET
  args {
    type_id: TFT_PRODUCT
    args {
      type_id: TFT_RAGGED
      args {
        type_id: TFT_STRING
      }
    }
    args {
    }
  }
}

  
	while updating its output type.
{'labels': array([b'a', b'b'], dtype=object), 'vals': 0.1, 'other': array([0.1, 0.2], dtype=float32)}
{'labels': array([b'a'], dtype=object), 'vals': 0.2, 'other': array([0.1, 0.2], dtype=float32)}
```
</details>
Repository: vscode
Issue: [linked editing] JSX tags: does not work when the whole tag is changed
Labels: bug,editor-synced-region

Type: <b>Bug</b>

1. Started editing the linked tag
eg: `<div> ....</div>`
2. Remove the complete tag
eg: `<>....</div>`

3. (Bug) Changing the original tag now does not affect the matching tag.
eg: `<section>....</>`       <-  did not change`


VS Code version: Code 1.79.2 (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:57:04.379Z)
OS version: Windows_NT x64 10.0.22621
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i5-12500H (16 x 3110)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<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)|15.63GB (8.48GB free)|
|Process Argv|--folder-uri file:///d%3A/Projects/agenda-builder|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (21)</summary>

Extension|Author (truncated)|Version
---|---|---
TabOut|alb|0.2.2
easy-npm|ani|0.3.0
tailwind-docs|aus|2.0.0
vscode-tailwindcss|bra|0.9.11
vscode-markdownlint|Dav|0.51.0
es7-react-js-snippets|dsz|4.4.3
gitlens|eam|14.0.0
prettier-vscode|esb|9.13.0
code-runner|for|0.12.0
copilot|Git|1.89.156
hungry-delete|jas|1.7.0
symbols|mig|0.0.12
vsliveshare|ms-|1.0.5873
cssvar|pho|2.6.2
vscode-thunder-client|ran|2.7.7
reflow|Ref|0.0.15
LiveServer|rit|5.7.9
svg-preview|Sim|2.8.3
errorlens|use|3.11.1
vscode-conventional-commits|viv|1.25.0
vscode-wakatime|Wak|24.0.14

(2 theme extensions excluded)

</details>
<!-- generated by issue reporter -->