sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Language services formatting for `else` on newline
Labels: Suggestion,Awaiting More Feedback

## Search Terms

* format else
* formatted else
* fomatter newline
* formatting newline

## Suggestion

When the formatting option for the opening brace on newline for control blocks is true, it would make sense to have the `else` on it's online as well.

## Use Cases

Using typescript-formatter with VS Code, and from command line.

## Examples

My tsfmt.json is:
```
{
    "baseIndentSize": 0,
    "indentSize": 4,
    "tabSize": 4,
    "indentStyle": 2,
    "newLineCharacter": "\n",
    "convertTabsToSpaces": true,
    "insertSpaceAfterCommaDelimiter": true,
    "insertSpaceAfterSemicolonInForStatements": true,
    "insertSpaceBeforeAndAfterBinaryOperators": true,
    "insertSpaceAfterConstructor": false,
    "insertSpaceAfterKeywordsInControlFlowStatements": true,
    "insertSpaceAfterFunctionKeywordForAnonymousFunctions": false,
    "insertSpaceAfterOpeningAndBeforeClosingNonemptyParenthesis": false,
    "insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets": false,
    "insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": true,
    "insertSpaceAfterOpeningAndBeforeClosingTemplateStringBraces": false,
    "insertSpaceAfterOpeningAndBeforeClosingJsxExpressionBraces": false,
    "insertSpaceAfterTypeAssertion": false,
    "insertSpaceBeforeFunctionParenthesis": false,
    "insertSpaceBeforeTypeAnnotation": false,
    "placeOpenBraceOnNewLineForFunctions": true,
    "placeOpenBraceOnNewLineForControlBlocks": true
}
```

I get results like this:
```
if(condition)
{
     console.log('condition true');
} else if(otherCondition)
{
     console.log('other condition is true');
} else 
{
     console.log('condition not true');
}
```

For people using `"placeOpenBraceOnNewLineForControlBlocks": true`, the expected behaviour (IMHO) would be:
```
if(condition)
{
     console.log('condition true');
} 
else if(otherCondition)
{
     console.log('other condition is true');
} 
else 
{
     console.log('condition not true');
}
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: PowerToys
Issue: [Color Picker] Activation behavior "Picker and editor" allows to open picker and editor parallel
Labels: Idea-Enhancement,Area-User Interface,Product-Color Picker

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

## ℹ Computer information

- PowerToys version: 0.27.0
- PowerToy Utility: Color Picker
- Running PowerToys as Admin: no
- Windows build number: W10 20H2

## 📝 Provide detailed reproduction steps (if any)

1. Open settings and configure action behavior 1 (Open Picker with editor enabled).
2. Press shortcut and click left mouse button to open editor.
3. Press shortcut to open picker parallel to the open editor window.

### ✔️ Expected result

Nothing happens.

Or the picker is shown and the editor gets hidden like whe pressing the button in editor.

### ❌ Actual result

Picker and editor is shown.

## 📷 Screenshots

![cp_option1](https://user-images.githubusercontent.com/61519853/100899307-f9403800-34c1-11eb-91b9-82127e58d6a2.png)
Repository: storybook
Issue: Support compact ArgsTable option in DocBlocks
Labels: feature request,inactive,addon: docs,block: argstable

**Is your feature request related to a problem? Please describe**
I would like to be able to use the "compact" option for ArgsTable when using it in MDX like so:
```
import { ArgsTable } from '@storybook/addon-docs/blocks';

<Story name="Main" args={{variant: 'primary'}} parameters={{layout: 'centered'}}> 
    {(args) => <Button {...args}>I want to buy a home</Button>}
  </Story>

 <ArgsTable story="Main" compact={true} include={['variant']} /> 
```
Currently it has no effect when using the `story` prop

**Are you able to assist to bring the feature to reality?**
maybe :)
Repository: TypeScript
Issue: Generic type sometimes returns never instead of actual template parameter type
Labels: Bug,Help Wanted,Experimentation Needed

**TypeScript Version:**  3.6+

**Search Terms:** enum, extends, never, template parameters

**Code**

```ts
enum FL4 { Absurd, False, True, Unknown }

type Classify< Left, Right > = Left extends Right

	? Right extends Left
		? [ Left , '==', Right ]
		: [ Left , '<:', Right ]
	
	: Right extends Left
		? [ Left, ':>', Right ]
		: [ Left , '!=', Right ]
```

[**Actual at 3.6+**](https://www.typescriptlang.org/play?ts=3.6.3#code/KYOwrgtgBAYgMgFigbygQQEYGcwCcAmANLAIYA2WwxAKrmFVAKogDWIA9gO4hQC+AsACghAFwCeAB2DpsefAH0AllnkhgAN2C55nEQDMoAXnRZKuEQB4hUG1ADCZEqcV6xF2IgB0mHAWIAGKAA+QmtbAG0oNU1cYgByCwAuOICoAF0hIKFRSWkAeTUlFWitHX0jEzNLMJsHJywXNw8Eb1k-KABGYNDBWyhI+BafOXjEoJSojS10zOzBAHoAKmWV1bX1jc3N+bnxKUqtasEASDQAYxEwch7jgFEADykL4HwoYHuRUHwsIWOAHygtwAjlcyO5zpdroDHsBnq8sicAQBZZQiEgsYDuOIAcXYIigYDUMLhUD2wAmENBwUyFUp5F2uUBIPI7jgwD0ImIACVFABzAAW+KCFV+AApfscLAANIKigCUhmFoqgUreHy+WCgbI5UAA-J0oIkoAAmKBy35ytWfEDfKDik6SmXyxV2lVWjVQHkC-H6rpG03mk6W-WEthcHhGkq4OY2IT4WGOXDSM7sEBYfEo9Po4AAZTEEAw7DIhoJIEUIOkWHzhbIDP2mbRGKsJyRwFMJF50ne1tt6dwihAvJuAEkQHp2BUozTjK3252oAAyFD9KAN7N5gtF9JG0fjvh16R1ZyuVnszmevmC4IVbX47ser2CubHfWPu-qm2a28S-WRW9QeJDEMCY3xmB0jT-M8AKgBJkm5S98QyE5fiNUD70-LUzx-Fdb1GcZ4O9MDjmOCDMJ1eIAEJgIIq80iAA)

```ts
type Absurd_is_never_wtf = Assert<
    Classify< FL4.Absurd, 0 >,
    [ never, '<:', 0 ]
>

type One_is_never_wtf = Assert<
    Classify< FL4.Absurd, 1 >,
    [ FL4.Absurd, ':>', never ]
>
```

[**Expected and before 3.6**](https://www.typescriptlang.org/play?ts=3.5.1#code/KYOwrgtgBAYgMgFigbygQQEYGcwCcAmANLAIYA2WwxAKrmFVAKogDWIA9gO4hQC+AsACghAFwCeAB2DpsefAH0AllnmYcBKAF50WSrhEAeIVBNQAwmRK7FAMzEHYiAHRq5xAAxQAfIWOmA2o4ILrIExADkmprhHlAAukJeQqKS0gDyIMBKKhnS2mi6wPpGgqbmltZ2DvDBrmFQAIzevqUBQSHqRFDhAFxeMY3xicmCAPQAVJNT0zOzc-PzoyPiUjp6hkIAkGgAxiJg5C2bAKIAHlJ7wPhQwKcioPhYWwA+UMcAjgdkDrv7h2-nYCXa5JQSbV4AWWUIhILGADnCAHF2CIoGBMoDgVAVsABr8vt5Elp0HsvstUm9PuQHHBgDYRMQAEqKADmAAtUV5iVsABRbTYGAAaXh5AEpNFyeVBBTc7g8sFBafSoAB+QY9KAAJigoq2otl9xAjygfLBAuFYolJulBvlUGZ7NRaqaGu1urB+rV6LYXB4GsyADciiMTEJ8EDLLhpDt2CAsKiofHYcAAMpiCAYdhkKAa9GKT7SLDpzNkcmrRMwuElTYQ4C6Egs6S3Q3G+O4RQgFlHACSIBs7GJgeDgi52lr9cbUAAZCgoIEK8m0xms-ENb3+3wy9ILFYsLZ7Iq6Qz7ayOd5iUrUc27Q6OSNNmrb1e5UaFZf+WrApeoBEogMn0MZoal+R4-t0Bg9P+p6ogkYJbBqAHXq+h70h+c4ocevT9Ey0GAZsmzARhYHhAAhNEOGOvEQA)

````ts
type Absurd_is_Absurd = Assert<
    Classify< FL4.Absurd, 0 >,
    [ FL4.Absurd, '==', 0 ]
>

type One_is_One = Assert<
    Classify< FL4.Absurd, 1 >,
    [ FL4.Absurd, ':>', 1 ]
>
```
Repository: vscode
Issue: [html] handle HTML-escaped characters in JavaScript attribute properties
Labels: bug,html


Issue Type: <b>Bug</b>

- Create an HTML attribute with JS in it, such as a button `onclick` event.

- Since attributes cannot use raw double quotes (Already used to open/close the attribute, HTML will give a syntax error), use `&quot;`.

- VSC will incorrectly mark it as an error

**Example**
```<button onclick="someFunction(&quot;string&quot;);">```

VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 x 2904)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>opengl: enabled_on<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.93GB (10.94GB free)|
|Process Argv|--crash-reporter-id 7653d454-ecf1-40e5-ad93-80b2e56cc4b5|
|Screen Reader|no|
|VM|67%|
</details><details><summary>Extensions (6)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|2.1.13
denizenscript|den|0.3.5
prettier-vscode|esb|5.8.0
discord-vscode|icr|4.0.0
python|ms-|2020.11.371526539
jupyter|ms-|2020.11.392013122


</details>
<!-- generated by issue reporter -->
Repository: terminal
Issue: Consolidate Scrolling actions
Labels: Issue-Feature,Area-Settings,Product-Terminal

# Description of the new feature/enhancement

After #8459, we'll have the following scroll actions:
- `scrollUp`
- `scrollDown`
- `scrollUpPage`
- `scrollDownPage`
- `scrollToTop`
- `scrollToBottom`

This seems to be a case of us introducing new _actions_ when we should be introducing new _arguments_ instead. I propose the following designs:

### Design 1: 3 args
- action: `scroll`
- arguments:
  - `direction: up|down`
  - `mode: system|page|buffer`
  - `rowsToScroll: <optional int>`

Personally dislike that `rowsToScroll` _only_ works if you're in "system" mode. But it avoids the override in Design 2.

### Design 2: Override mode
- action: `scroll`
- arguments:
  - `direction: up|down`
  - `mode: system|page|buffer|<int>`

This is basically Design 1, except `rowsToScroll` is embedded inside `mode`. If we go with this approach, maybe mode should be renamed to something like "amount"?

Open to discussion. _Go!_
Repository: godot
Issue: Godot crashes when using extended Translation class in script
Labels: bug,topic:gdscript,confirmed,crash

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
3.2.3

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Gentoo AMD64 Linux

**Issue description:**
<!-- What happened, and what was expected. -->

Godot crashes on finalization

```
[1] /lib64/libc.so.6(+0x38ac0) [0x7f42c9364ac0] (??:0)
[2] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x862a7b] (godot-3.2.3-stable/./core/string_name.h:100)
[3] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x2ce3697] (godot-3.2.3-stable/core/object.cpp:935)
[4] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x1491d99] (godot-3.2.3-stable/./core/os/memory.h:114)
[5] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x2d5000a] (godot-3.2.3-stable/./core/reference.h:279)
[6] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x2d50309] (godot-3.2.3-stable/./core/set.h:121)
[7] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x7e159a] (godot-3.2.3-stable/./core/os/memory.h:119)
[8] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x7d1a79] (godot-3.2.3-stable/main/main.cpp:2277)
[9] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x7a5323] (godot-3.2.3-stable/platform/x11/godot_x11.cpp:59)
[10] /lib64/libc.so.6(__libc_start_main+0xeb) [0x7f42c934fe8b] (??:0)
[11] godot-3.2.3-stable/bin/godot.x11.opt.tools.64() [0x7a7b7a] (??:?)
```

**Steps to reproduce:**
Run example as script with `-s script.gd`

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[godot-translation-extending.zip](https://github.com/godotengine/godot/files/5631221/godot-translation-extending.zip)
Repository: ant-design
Issue: Resizing Autocomplete with "width 100%" does not resize the dropdown 
Labels: help wanted,Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/non-case-sensitive-autocomplete-antd491-forked-6j09c?file=/index.js)

### Steps to reproduce
Resize the window in the reproduction; you will see that the dropdown does not resize its width in accordance with the Autocomplete input box

### What is expected?
The dropdown resizes to the same width of the input box as the window size changes

### What is actually happening?
The dropdown size stays stagnant to the size it was at on first render

| Environment | Info |
|---|---|
| antd | 4.9.1 |
| React | 16.14.0 |
| System | macOS |
| Browser | macOS |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Roll benchmark
Labels: a: tests,engine,P3,team-engine,triaged-engine

Our copy of google/benchmark is pretty old, and the docs don't match up anymore. 

We should be able to roll it using a combination of the changes from flutter/buildroot#415 and https://github.com/flutter/engine/pull/22804, but the metrics_center code needs to be updated for some new output that the newer version gives as well.

/cc @liyuqian fyi

There's no urgent need for this, but it's a nice to have thing for the next person trying to add a benchmark and looking at the docs.
Repository: flutter
Issue: CupertinoNavigationBar incorrect dark mode theming with MaterialApp
Labels: framework,f: material design,f: cupertino,has reproducible steps,found in release: 3.3,found in release: 3.7,team-design,triaged-design

`CupertinoNavigationBar` background and text styling not respecting theme, even when using a `cupertinoOverrideTheme` workaround, as seen in the simplified code sample below. The background of the app is also different.

Expected (same code sample, with `CupertinoApp` instead):
<img width="736" alt="Screenshot 2020-12-02 at 20 00 25" src="https://user-images.githubusercontent.com/6655696/100918654-12081800-34d9-11eb-865a-021f68d33a17.png">

Actual:
<img width="745" alt="Screenshot 2020-12-02 at 19 59 27" src="https://user-images.githubusercontent.com/6655696/100918556-ed13a500-34d8-11eb-9cb9-528a9bb38bd5.png">

```dart
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        theme: ThemeData(
          brightness: Brightness.dark,
        ).copyWith(
            cupertinoOverrideTheme:
                CupertinoThemeData(brightness: Brightness.dark)),
        
        routes: {
          '/': (_) => MyCupertinoScaffold(),
        });
  }
}

class MyCupertinoScaffold extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoPageScaffold(
      navigationBar: CupertinoNavigationBar(
        middle: Text('Title'),
      ),
      child: Container(),
    );
  }
}
```
Repository: flutter
Issue: The Material color API is not well suited for null safety
Labels: framework,f: material design,a: null-safety,P3,team-design,triaged-design

The material color palette has a set of named colors with pre-set saturations of 50,100,200,300,400,500,600,700,800, and 900: https://material.io/resources/color/#!/?view.left=0&view.right=0

In the current Flutter API, this is encoded as a static named getters (e.g. `green`) on `Color` with an `[]` operator for getting the Color representing a given saturation (expressed as an `int`), e.g.: `Colors.green[400]` returns a `Color` that is Green with a saturation of 400.

After migrating Flutter to null safety, this causes issues when using these to set a non-null color, e.g.:

```dart
class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
      decoration: const BoxDecoration(
        border: Border(
          top: BorderSide(width: 1.0, color: Colors.green[400]),
        ),
      ),
      child: const Text('Hello'),
    );
  }
}
```

=>

```
The argument type 'Color?' can't be assigned to the parameter type 'Color'.
```

It would be nice if this API could be redesigned so it returns something of type `Color`, not `Color?` for the known saturations.
Repository: flutter
Issue: "The relevant error-causing widget" misleads when the exception is thrown from user code
Labels: c: crash,framework,a: first hour,a: quality,a: error message,has reproducible steps,P2,found in release: 3.7,found in release: 3.9,team-framework,triaged-framework

Steps to reproduce:
1. `flutter create dummy`
2. `cd dummy`
3. `nano lib/main.dart`
4. add a `throw 'hello';` statement on line 64, the first line of the `_MyHomePageState.build` method.
5. save and quit the editor
6. `flutter test`

Expected results:
Exception is reported, pointing clearly to line 64.

Actual results:
Exception is reported, but before the stack trace it first points you to line 25, where the MyHomePage widget is instantiated.
Repository: opencv
Issue: OpenCV 5.0
Labels: evolution

Discussion thread for https://github.com/opencv/opencv/wiki/OE-5.-OpenCV-5.

Please note that some topics, such as 3D module, are discussed in the corresponding threads.

**Upd. We now have a [dedicated OpenCV 5.0 project](https://github.com/orgs/opencv/projects/1) to finally make it!**
Repository: vscode
Issue: Git - Add a command palette option for git rm
Labels: help wanted,feature-request,git

<!-- ⚠️⚠️ 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. -->
I'd like to be able to open the command palette and choose "Git: Delete Current File" which would do the equivalent of `git rm path` where `path` is the path to the current file.

A `git rm` will fail when the file is not currently committed. If it has uncommitted changes, or is not tracked by git, then it will fail. In this way, it's a "safer" form of delete, while avoiding the system trash folder.
Repository: rust
Issue: Add support for branch coverage in source-based coverage
Labels: C-enhancement,A-code-coverage

Similarly to what is being done in LLVM and Clang: https://reviews.llvm.org/D84467.
Repository: pytorch
Issue: [bug][libtorch] torch::load seeks to the start of the input stream before reading
Labels: module: serialization,triaged,needs design

## 🐛 Bug

The behavior of torch::load makes it impossible to read multiple tensors from a stream, as it will seek to the beginning of the stream before reading the tensor. The corresponding writing function torch::save does not seek to the beginning of the stream.

## To Reproduce
```cpp
torch::Tensor x = torch::ones({2, 2});
torch::Tensor y = torch::ones({2, 2}) * 2;

std::cout << x << "\n" <<  y << std::endl;

std::ofstream os("my_tensors", std::ios::binary);
if (os.is_open())
{
    std::cout << "\nostream position before writing:  " << os.tellp() << std::endl;
    torch::save(x, os);
    std::cout << "\nostream position after writing x: " << os.tellp() << std::endl;
    torch::save(y, os);
    std::cout << "\nostream position after writing y: " << os.tellp() << std::endl;
}
os.close();

std::ifstream is("my_tensors", std::ios::binary);
if (is.is_open())
{
    std::cout << "\nistream position before reading:  " << is.tellg() << std::endl;
    torch::load(x, is);
    std::cout << "\nistream position after reading x: " << is.tellg() << std::endl;
    torch::load(y, is);
    std::cout << "\nistream position after reading y: " << is.tellg() << std::endl;
}
is.close();

std::cout << x << "\n" <<  y << std::endl;
```

Output:

```
 1  1
 1  1
[ CPUFloatType{2,2} ]
 2  2
 2  2
[ CPUFloatType{2,2} ]

ostream position before writing:  0

ostream position after writing x: 1478

ostream position after writing y: 2956

istream position before reading:  0

istream position after reading x: 80

istream position after reading y: 80
 1  1
 1  1
[ CPUFloatType{2,2} ]
 1  1
 1  1
[ CPUFloatType{2,2} ]
```

## Expected behavior

Tensors x and y read from the input stream match the tensors written to the corresponding output stream.

## Environment

libtorch-win-shared-with-deps-1.7.0+cpu


cc @mruberry
Repository: flutter
Issue: [MacOS] Add headless engine support for platform views / FlutterGLCompositor
Labels: engine,platform-mac,a: desktop,P2,team-macos,triaged-macos

Currently, FlutterGLCompositor will not be created if _viewController is nil which is the case for headless engines.

As a result, platform views will not work without the compositor.

We need to find a solution to creating a FlutterGLCompositor with a nil FlutterViewController for headless engines.

cc @cyanglaz
Repository: flutter
Issue: [google_sign_in] Add future that completes when the plugin is (really) ready.
Labels: c: new feature,p: google_sign_in,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case

Google Sign In (web) is some times slow to start up and silently sign in the current user; however there's no way for app developers to let users know about this delay.

There's currently a future in the plugin side that can be used to compute the initialization status of the plugin, without having to touch platform-dependent code:

https://github.com/flutter/plugins/blob/master/packages/google_sign_in/google_sign_in/lib/google_sign_in.dart#L227-L228

(However, it can become null if the initialization fails)

## Proposal

> As proposed by @SwissCheese5 [here](https://github.com/flutter/flutter/issues/52338#issuecomment-737185938):
> 
> A Future in the Google Sign In package that completes as soon as the javascript script finishes loading. That way we can show a loading indicator on sites and act accordingly. This will not break anything and only provides an extra feature people can use to make sure google sign in finishes loading.
Repository: deno
Issue: Allow to set process title
Labels: cli,suggestion

`deno install --name <name>`  allow to specify the name of executable file.

Unfortunately, the name of running process is still `deno` eg Activity Monitor on Mac.

How can I change the process name, equivalent of `process.title` in Node.js ?
Repository: kubernetes
Issue: Migrate private registry e2e tests away from gcr.io/k8s-authenticated-test
Labels: priority/important-soon,kind/cleanup,sig/node,area/release-eng,sig/apps,sig/testing,sig/release,lifecycle/frozen,needs-triage,sig/k8s-infra

Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: https://github.com/kubernetes/k8s.io/issues/1458

Followup to https://github.com/kubernetes/kubernetes/issues/97002

The registry is used by the following kubernetes e2e tests:
- [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
- [sig-apps] ReplicationController should serve a basic image on each replica with a private image

https://github.com/kubernetes/k8s.io/issues/1459 covers setting up a community-owned alternative

This issue covers updating the tests.  Fixes may need to be cherry-picked back to previous release branches.