sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: [Feature Request]: protocol.handle for Websocket
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

protocol.handle() works for http but not WebSocket. so we can do protocol.handle('someProto') and then we can fetch('someProto://example/file.txt'), but we can not `new WebSocket('someProto://example/path')`

### Proposed Solution

having protocol.handle() work with both fetch and `new WebSocket()` or an option for protocol.handle() that enables it to handle WebSocket

### Alternatives Considered

having a separate function to register protocol handlers for WebSocket

### Additional Information

_No response_
Repository: rust
Issue: 32-bit ARM NEON intrinsics are unsound due to subnormal flushing
Labels: O-Arm,P-medium,T-compiler,I-unsound,T-libs,A-floating-point,I-miscompile

This is the ARM NEON version of https://github.com/rust-lang/rust/issues/114479. Example by @beetrees, to be compiled with `--target armv7-unknown-linux-gnueabihf -O -Ctarget-feature=+neon`:
```rust
#![feature(stdarch_arm_neon_intrinsics)]

use std::arch::arm::{float32x2_t, vadd_f32};
use std::mem::transmute;

#[inline(never)]
fn print_vals(x: float32x2_t, i: usize, vals_i: u32) {
    println!("x={x:?} i={i} vals[i]={vals_i}");
}

const ZERO: float32x2_t = unsafe { transmute([0, 0]) };
const INC: float32x2_t = unsafe { transmute([f32::MIN_POSITIVE / 128.0, f32::MIN_POSITIVE / 128.0]) };
const TARGET: [u32; 2] = unsafe { transmute([f32::MIN_POSITIVE, f32::MIN_POSITIVE]) };

#[inline(never)]
pub fn evil(vals: &[u32; 300]) {
    let mut x: float32x2_t = ZERO;
    let mut i: usize = 0;
    while unsafe { transmute::<float32x2_t, [u32; 2]>(x) } != TARGET {
        print_vals(x, i, vals[i]);
        x = unsafe { vadd_f32(x, INC) };
        x = unsafe { vadd_f32(x, INC) };
        i += 2;
    }
}

pub fn main() {
    let mut vals: [u32; 300] = [0; 300];
    for i in 0..300 { vals[i as usize] = i; }
    evil(&vals);
}

#[cfg(not(target_feature = "neon"))]
compile_error!("-Ctarget-feature=+neon required");
```

LLVM's optimizations assume they can calculate what that loop does, and that it follows IEEE semantics. But LLVM's codegen produces code that does not have IEEE semantics, and instead flushes subnormals to zero. :boom: 

This almost surely also affects the unstable `std::simd` on ARM.
Repository: godot
Issue: Tiny mouse pointer under wayland
Labels: bug,platform:linuxbsd

### Tested versions

Godot v4.3.stable

### System information

Godot v4.3.stable - Manjaro Linux #1 SMP PREEMPT_DYNAMIC Mon Aug 19 09:51:26 UTC 2024 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (nvidia; 550.107.02) - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

[Screencast_20240902_080033.webm](https://github.com/user-attachments/assets/006f0853-1956-44bc-b082-e6356b43b242)

As seen in the video, the mouse is tiny compared with the OS one (the size changes when hovering the system titlebar)

### Steps to reproduce

Just start godot with wayland support (--display-driver wayland) under linux

### Minimal reproduction project (MRP)

Not applicable
Repository: pytorch
Issue: DISABLED test_random_no_reused_random_states_float32 (__main__.TestCuda)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 3 workflow(s) with 9 failures and 3 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_random_no_reused_random_states_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 1047, in test_random_no_reused_random_states
    run(func, torch.device("cuda"), dtype)
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 1042, in run
    return torch.stack([t1, t2]).unique().shape[0]
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_tensor.py", line 991, in unique
    return torch.unique(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_jit_internal.py", line 624, in fn
    return if_false(*args, **kwargs)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_jit_internal.py", line 624, in fn
    return if_false(*args, **kwargs)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/functional.py", line 1075, in _return_output
    output, _, _ = _unique_impl(input, sorted, return_inverse, return_counts, dim)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/functional.py", line 968, in _unique_impl
    output, inverse_indices, counts = torch._unique2(
RuntimeError: Host and device pointer dont match with cudaHostRegister. Please dont use this feature by setting PYTORCH_CUDA_ALLOC_CONF=use_cuda_host_register:False (default)

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCuda.test_random_no_reused_random_states_float32

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_cuda_expandable_segments.py`

cc @ptrblck @msaroufim @clee2000
Repository: puppeteer
Issue: [Bug]: Scale parameter in page.pdf() has no effect when using Firefox as browser engine/backend
Labels: bug,upstream,confirmed,bidi,P3,firefox

### Minimal, reproducible example

```TypeScript
const puppeteer = require('puppeteer') 

const firefoxOptions = {
  browser: 'firefox',
  executablePath: '/opt/firefox/129.0.2/firefox',
  headless: true 
};

function delay(time) {
  return new Promise(function(resolve) {
    setTimeout(resolve, time)
  });
}

async function printPDF() {

  console.log('printPDF() called');
 
  const browser = await puppeteer.launch(firefoxOptions);
  const page = await browser.newPage();

  /* await page.setViewport({
    width: 1600,
    height: 1131,
    deviceScaleFactor: 1.0,
  }); */

  await page.goto('http://foo.bar/site', {waitUntil: 'networkidle0'});

  console.log('Waiting for 20s');
  await delay(20000);

  console.log('Generating PDF...');

  await page.pdf({path: 'page.pdf',
                  format: 'A4',
                  scale: 0.4,
                  timeout: 900000,
                  margin: { left: '0.5cm', top: '1.5cm', right: '0.5cm', bottom: '0.5' }});

  await browser.close();

  console.log('Finished');

};

printPDF();
```


### Background

I used to have Puppeteer v19.x and Firefox version nightly 2023-11-27 where PDF printing with scale option worked just fine.

Now I updated Puppeteer to 23.2.1 (NodeJS 20.x LTS) and Firefox to 129.0.2 (which is mentioned here: https://github.com/puppeteer/puppeteer/blob/main/packages/puppeteer-core/src/revisions.ts), and the scale option does not have effect. I tried multiple values, and it does not work (it defaults to value 1 always).

Firefox was downloaded from here: https://download-installer.cdn.mozilla.net/pub/firefox/releases/129.0.2/linux-x86_64/en-US/

### Expectation

https://pptr.dev/api/puppeteer.pdfoptions has the "scale" option listed, and it has worked with Firefox earier, but it's not working anymore. I would like to have this option, because by using that, I'm able to get more information/page view in one PDF sheet ("zoom out" effect).

### Reality

Scale option does not have any effect. PDF prints are defaulting to scale parameter "1", even I put 0.4 or 0.6 as its value.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

23.2.1

### Node version

20.8.1

### Package manager

npm

### Package manager version

10.1.0

### Operating system

Linux
Repository: react
Issue: [React 19] Need suggestion on upgrade.
Labels: React 19

## Summary

We are upgrading the react in our project and we see in the documentation the support for the defaultprops and proptypes is removed.

We are using the jsx and migrating to typescript is not possible at the moment as our project is fairly big. Any suggestion on how to do defaultprop and proptype check.
Repository: pytorch
Issue: Broadcasting Parameter destroys hooks in PyTorch 2.4
Labels: oncall: distributed,triaged

### 🐛 Describe the bug

### 
Following code runs successful in PyTorch 2.1.1
However in PyTorch 2.4, the hook will not be called
```
import os

import torch
import torch.nn as nn
import torch.distributed as dist

os.environ["MASTER_ADDR"] = "127.0.0.1"
os.environ["MASTER_PORT"] = "8881"
os.environ["WORLD_SIZE"] = "1"
os.environ["RANK"] = "0"
dist.init_process_group(backend='gloo', init_method='env://')
weight = nn.Parameter(torch.ones(1))
hook_fired = False

def grad_hook(_):
    global hook_fired
    hook_fired = True

weight.register_hook(grad_hook)

dist.broadcast(weight, src=0)

weight.backward()
dist.destroy_process_group()
assert hook_fired # AssertionError for pytorch 2.4
```

Further, hooks that are registered after `dist.broadcast` are also not called 


### Versions

Collecting environment information...
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 24.04 LTS (x86_64)
GCC version: (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.39

Python version: 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.8.0-36-generic-x86_64-with-glibc2.39
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 4090
GPU 1: NVIDIA GeForce RTX 4090

Nvidia driver version: 550.90.07
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        43 bits physical, 48 bits virtual
Byte Order:                           Little Endian
CPU(s):                               16
On-line CPU(s) list:                  0-15
Vendor ID:                            AuthenticAMD
Model name:                           AMD EPYC 7232P 8-Core Processor
CPU family:                           23
Model:                                49
Thread(s) per core:                   2
Core(s) per socket:                   8
Socket(s):                            1
Stepping:                             0
Frequency boost:                      enabled
CPU(s) scaling MHz:                   90%
CPU max MHz:                          3100.0000
CPU min MHz:                          1500.0000
BogoMIPS:                             6200.10


cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: react-native
Issue: StyleSheet.flatten with a falsy value returns undefined
Labels: Issue: Author Provided Repro,API: StyleSheet

### Description

On iOS and Android (not web), calling `StyleSheet.flatten` with null/undefined/false returns `undefined`.

The TypeScript signature of `flatten` is `flatten<T>(style?: StyleProp<T>): T`. null/undefined/false are valid `StyleProp`s, so passing them to flatten should be valid, but flatten is supposed to return `T` (some style object), and undefined is usually not a valid `T`.

Widening the return type of `flatten` to `T | undefined` is an option, but would be a public API change. I think changing the function to return `{}` for falsy values is more correct, since you probably want to get a final computed, flattened style object, and don't care what the input was or if it was falsy.

### Steps to reproduce

On iOS or Android:
```
console.log(typeof StyleSheet.flatten(false)) // => 'undefined'
```

### React Native Version

0.75.2

### Affected Platforms

Runtime - Android, Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.2
  CPU: (8) arm64 Apple M2
  Memory: 339.17 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.3.0
    path: ~/.volta/tools/image/node/22.3.0/bin/node
  Yarn:
    version: 3.6.4
    path: ~/.volta/tools/image/yarn/4.3.1/bin/yarn
  npm:
    version: 10.8.1
    path: ~/.volta/tools/image/node/22.3.0/bin/npm
  Watchman:
    version: 2024.07.01.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/hazel/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java: Not Found
  Ruby:
    version: 2.7.4
    path: /Users/hazel/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.2
    wanted: 0.75.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: fals
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://snack.expo.dev/@catboyfan/stylesheet-flatten-undefined

### Screenshots and Videos

_No response_
Repository: vscode
Issue: Merge Editor Code lens renders incorrectly
Labels: bug,merge-editor

Possibly caused by @jrieken changes as it uses the same type of code lens

I opened the merge editor and the code lenses were rendered twice or at the wrong location after scrolling.

<img width="566" alt="image" src="https://github.com/user-attachments/assets/4c8a8da4-4b1f-409a-8718-9af237c66f16">
Repository: pytorch
Issue: torch.hub.load will raise RuntimeError: operator torchvision::nms does not exist
Labels: triaged,module: hub

### 🐛 Describe the bug

When loading models from the torch hub, it will raise `RuntimeError: operator torchvision::nms does not exist`. I tested on both Linux and Mac.

```python
import torch
torch.hub.load('pytorch/vision', 'resnet18')
```

### Versions

PyTorch version: 2.4.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.6 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.3.9.4)
CMake version: version 3.29.0
Libc version: N/A

Python version: 3.11.0 | packaged by conda-forge | (main, Jan 14 2023, 12:26:40) [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-14.6-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M3 Max

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.4.0
[pip3] torchvision==0.19.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] torch                     2.4.0                    pypi_0    pypi
[conda] torchvision               0.19.0                   pypi_0    pypi

cc @nairbv @NicolasHug @vmoens @jdsgomes
Repository: kubernetes
Issue: [Pod Auto Scaler] Why use Pod Request Resource As Base?
Labels: sig/autoscaling,kind/feature,lifecycle/rotten,needs-triage

### What would you like to be added?

Why do we decide to use Pod's request as the basis for calculating indicators? Usually our scenario is to use limit to set the threshold.

https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/podautoscaler/replica_calculator.go#L437

### Why is this needed?

support limit as base resource
Repository: deno
Issue: Support `import foo from "./bar.txt" with { as: "bytes" }`
Labels: suggestion

Would import the relevant file as a byte buffer (`Uint8Array`). Maybe also `import foo from "./bar.txt" with { as: "text" }`?
Repository: flutter
Issue: [flutter_markdown] Screenreader: Ignore Bullet Points and Icons
Labels: a: accessibility,package,c: proposal,team-ecosystem,P2,p: flutter_markdown,triaged-ecosystem

### Use case

We use the `MarkdownBody` Widget to show some intros for our App. The intro texts are stored in a .json file.

We carried out a professional accessibility test and one of the findings we noticed was that the intro text is read out in an unusual way. 
Specifically, it was noted that icons are read aloud and that the bullet point is read aloud each time a list is given.
It would be desirable if the `MarkdownBody` widget offered a configuration option to influence the behavior of the screen reader.

In my opinion, an option to not read out icons when the screen reader is switched on would be useful.
In addition, not to explicitly read out the bullet points for enumerations.
Currently, the behavior of the screen reader cannot be influenced here

### Proposal

Example Text:
```
🚀 **Improvements**
* Feature A
* Feature B
```
--> The Screenreader read the following:
_Rocket_, Improvments
_Dot_, Feature A
_Dot_ Feature B

The accessibility testers noted that reading out the term “rocket” does not offer any added value here, as it is only a visual element. These are not usually read aloud.

The same applies to reading out “dot”. It is implicitly clear that this is an enumeration and reading this out again is confusing.
Repository: go
Issue: net/http: IdleConnTimeout is invalid for HTTP/2
Labels: NeedsInvestigation

### Go version

go version go1.22.2 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/data/home/sakiluzhang/.cache/go-build'
GOENV='/data/home/sakiluzhang/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/data/home/sakiluzhang/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/data/home/sakiluzhang/go'
GOPRIVATE=''
GOPROXY='https://sakiluzhang:lFEajkXQ@goproxy.woa.com'
GOROOT='/data/home/sakiluzhang/go'
GOSUMDB='sum.woa.com+643d7a06+Ac5f5VOC4N8NUXdmhbm8pZSXIWfhek5JSmWdWrq7pLX4'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/data/home/sakiluzhang/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.2'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/data/home/sakiluzhang/DServer/go.mod'
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 -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build929430334=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

```
func (t *Transport) tryPutIdleConn(pconn *persistConn) error {

	if t.DisableKeepAlives || t.MaxIdleConnsPerHost < 0 {
		return errKeepAlivesDisabled
	}
	if pconn.isBroken() {
		return errConnBroken
	}
	pconn.markReused()

	t.idleMu.Lock()
	defer t.idleMu.Unlock()

	// HTTP/2 (pconn.alt != nil) connections do not come out of the idle list,
	// because multiple goroutines can use them simultaneously.
	// If this is an HTTP/2 connection being “returned,” we're done.
	if pconn.alt != nil && t.idleLRU.m[pconn] != nil {
             **here pconn.idleAt has not been updated and returned.**
		return nil
	}
       ......
```



### What did you see happen?

I hope one connection is checked IdleConnTimeout  should start at the latest time I used it  rather than the first time
      
I hope *http.Transport.idleLRU list should remove connection  not only by MaxIdleConns (in many cases, you can't estimate proper num for in China there maybe Tens of millions users use our product simultaneously and more http requests will be produced) but also by IdleConnTimeout

### What did you expect to see?

read above
Repository: next.js
Issue: BeforeInteractive script not firing after calling notFound() function
Labels: bug,Script (next/script),linear: next

### Link to the code that reproduces this issue

https://github.com/kacyee/before-interactive-2

### To Reproduce

1. Start the application in production mode (npm build -> npm start)
2. Go to http://localhost:3000
3. Look into browser console, there should logged messages:
First -> "I should be beforeInteractive"
Second -> "Im in root layout!"
4. Go to http://localhost:3000/not-existing-route, console should log as in point 3.
5. Go to http://localhost:3000/pl/newsite, console log only "Im in root layout!", but not "I should be beforeInteractive" - 
_**which is the problem I am describing**_


### Current vs. Expected behavior

Currently when firing notFound function, for some reason script injected with strategy "beforeInteractive" are not fired.
In that case - CMP (Consent Management Platform) cookie consent is not being initialized and some cookies are already generated.
To avoid that - all scripts with strategy "beforeInteractive" should be fired on every single page, even on notFound.
On other pages it works fine, but not when we call notFound function.

Expected behavior:
scripts with strategy "beforeInteractive" are fired on every single page, even after calling notFound() function.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:19:22 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.5.0
  npm: 9.8.0
  Yarn: 3.6.1
  pnpm: 8.6.6
Relevant Packages:
  next: 14.2.7 // Latest available version is detected (14.2.7).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Script (next/script)

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

I tested few version from 14.2.3 to "15.0.0-canary.135", error occurs on all of them.
Repository: vscode
Issue: Issue Reporter should include warning if VSCode is not pure
Labels: feature-request,issue-reporter

Some extensions modify our source code. When users with these extensions report a bug, it would be very helpful to know that the users build is corrupted/modified, as they often cause these issues.

You could use the integrity service to check if the installation is pure or not: [isPure](https://github.com/microsoft/vscode/blob/d09064eb4f816690d8ae9199f2d128b5053a54d2/src/vs/workbench/services/integrity/electron-sandbox/integrityService.ts#L65)

Here’s an example of an issue where a user had an extension that caused a bug. It was difficult to identify that the user had a corrupted build. https://github.com/microsoft/vscode/issues/227023