sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Proposal: add tagged template literal support for `vscode.l10n`
Labels: feature-request,l10n-platform,api-proposal

## Motivation

Currently, string localization is done by calling a method

```ts
vscode.l10n.t('Hello {0}!' name);
```

This mirrors what we do in core, however, this is a little error-prone. There's no validation in that string to ensure that replacement are done correctly, that all replacement arguments are used, or that enough replacement arguments are provided to satisfy the string. This is what initially [inspired me](https://github.com/microsoft/vscode-js-debug/pull/1693/files) 🙈 

## Proposal

We propose adding an overload to `vscode.l10n.t` that allows it to be used with [tagged template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#tagged_templates). With tagged literalls, developers use a template literal as they "normally would", but prepend it with the method call

```ts
vscode.l10n.t`Hello ${name}!`
```

The associated definition for `t()` would gain an overload:

```ts
	export namespace l10n {
		/**
		 * Marks a string for localization. If a localized bundle is available for the language specified by
		 * {@link env.language} and the bundle has a localized value for this message, then that localized
		 * value will be returned (with injected {@link args} values for any templated values).
		 *
		 * This signature is for use with tagged template literals. The more verbose object-based
		 * call should be used if comments are required.
		 *
		 * @example
		 * ```
		 * vscode.l10n.t`Hello ${name}!`
		 * ```
		 *
		 * @param message - String message components.
		 * @param args - Replacement components in the string.
		 * @returns localized string with injected arguments.
		 * @see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#tagged_templates
		 */
		export function t(parts: TemplateStringsArray, ...args: Array<string | number | boolean>): string;
```

Tagged template literals are an ES5 feature, and we already use ES6 features (such as `Symbol.iterator`), so this does not introduce any new `lib`/`target` constraints.

Previously we haven't been big fans of adding "convenience" APIs such as this to the extension host API, but I think this might warrant some deviation since we force that this specific method is used (and not wrapped) in the localization extraction pipeline.

## Alternatives

An alternative way to gain the same level of safety would be to use TS' [template literal types](https://www.typescriptlang.org/docs/handbook/2/template-literal-types.html) to enforce argument placement. However, this lacks the ergonomic benefits of template literals, and would introduce previously unseen levels of type acrobatics to vscode.d.ts. Our extension host api is not a venue for Cirque du TypeScript.
Repository: vscode
Issue: Some quickpick item button icons not centered
Labels: bug,quick-pick



![image](https://user-images.githubusercontent.com/30305945/236280940-94cfc6b9-6379-4a18-b2fe-4e1c9d1e6163.png)
Repository: tensorflow
Issue: TensorFlow Refuses to See my GPU All The Time
Labels: stat:awaiting tensorflower,type:build/install,type:support,subtype: ubuntu/linux

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

Support

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

No

### Source

source

### Tensorflow Version

2.25.1

### Custom Code

Yes

### OS Platform and Distribution

Linux, Ubuntu 22.04.6

### Mobile device

_No response_

### Python version

Python 3.11

### Bazel version

N/A*

### GCC/Compiler version

11.2

### CUDA/cuDNN version

12

### GPU model and memory

Nvidia GT 1030 2gb

### Current Behaviour?

<pre>``2023-05-05 02:37:58.234754: I tensorflow/tsl/cuda/cudart_stub.cc:28] Could not find cuda drivers on your machine, GPU will not be used.
2023-05-05 02:37:58.270803: I tensorflow/tsl/cuda/cudart_stub.cc:28] Could not find cuda drivers on your machine, GPU will not be used.
2023-05-05 02:37:58.271133: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-05-05 02:37:58.944800: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2023-05-05 02:37:59.878527: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:996] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-05-05 02:37:59.878936: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1956] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...``<pre>

### Standalone code to reproduce the issue

```shell
The above is the response every time even though the GPU exists in the PC.

The GT 1030 might not be the most powerful GPU out there, but it does have 344 Cuda Cores.

I also have the Cuda Toolkit installed, along with the latest drivers available (I'm surprised this card is still getting support).

To reproduce,run the following command in the terminal: ``python3 insert script name here.py (replace with the name of your .py script).

The output will tell you what has happened.

Just FYI, this also affects AMD Radeon Pro WX 5, 6 and 7000 series GPU's and their gaming variants i.e., my RX 6700 XT in this case running in WSL 1.

Godspeed.
```


### Relevant log output

_No response_</details>
Repository: pytorch
Issue: Optimal Batch Size Selection in Torchdynamo Benchmarks for Different GPU Memory Sizes
Labels: triaged,enhancement,oncall: pt2

### 🚀 The feature, motivation and pitch

The torchdynamo benchmarking scripts come with default batch size for each model based on A100 40GB GPU tests. When adapting these scripts for training on smaller sized GPUs, we see OOM errors. The performance and accuracy tests will fail for most models and the benchmarking results becomes less informative. Thus it makes more sense to assign an optimal batch size according to the actual GPU memory size for each model, where the optimal batch size map will be kept as a list in the directory `benchmarks/dynamo`. By adding this batch size selection feature in the benchmarking scripts for all model suites, the benchmarking can be adapted by wider communities and suits their needs for testing and comparison among different GPU types.



### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @soumith @wconstab @ngimel
Repository: flutter
Issue: infra: bot didn't ask for missing tests in a PR
Labels: team-infra,P2,triaged-infra

<!--  Thank you for contributing to Flutter!

      If you are filing a bug, please add the steps to reproduce, expected and actual results.

      If you are filing a feature request, please describe the use case and a proposal.

      If you are requesting a small infra task with P0 or P1 priority, please add it to the
      "Infra Ticket Queue" project with "New" column, explain why the task is needed and what
      actions need to perform (if you happen to know). No need to set an assignee; the infra oncall
      will triage and process the infra ticket queue.
-->

#125855 PR doesn't have tests but bot didn't complaint about it.
Repository: terminal
Issue: Color schemes can get "stuck" when the Theme is Light
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-SettingsUI

### Windows Terminal version

Commit 97a617a909f1dd3664daf3a1764c9a7e8996a1b8

### Windows build number

10.0.19045.2728

### Other Software

_No response_

### Steps to reproduce

1. In Windows Terminal open the _Settings_ page.
2. Set the _Theme_ to _Light_.
3. Go to any profile and change the color scheme to something obviously different from the default, e.g. _One Half Light_.
4. Go to the default profile and also change that color scheme to _One Half Light_.
5. Go back to the profile from step 3 and reset the color scheme to the inherited value.
6. Go to the default profile and reset the color scheme there too.
7. Save the settings.
8. Go back to the profile from step 3 and view the appearance.


### Expected Behavior

Everything should now have been reset to the default color scheme, i.e. _Campbell_.

### Actual Behavior

The color scheme is listed as being _Campbell_, but what is displayed in the preview window is still _One Half Light_, and that's also what gets used if you try and start that profile.

![image](https://user-images.githubusercontent.com/4181424/236286427-de654633-1b16-40c0-9484-4498c2b7cded.png)
Repository: go
Issue: go/analysis/passes/critsec: a new checker for control flow in critical sections
Labels: Tools,Analysis

A common programming mistake in Go is to add an early return statement in a critical section and then to forget to release the mutex. Usually the unlock operation can be deferred so that it runs automatically, but there are times when the critical section does not extend to the end of the function so defer cannot be used. It would be interesting to see how many mistakes a checker in the analysis framework might catch. (A quick experiment in x/tools caught only the one instance that I was training it on.)

The notion of "critical section" could be generalized to other control flow problems. For example, some long functions ([example](https://github.com/google/starlark-go/blob/master/starlark/interp.go#L79)) are structured to have a single return statement and a comment saying "don't return before the end!". This region can be thought of as a "critical section of no return" that is "unlocked" immediately before the final return statement. Similarly, a function that opens a file and then closes it before returning should probably close it on all paths, making a "critical section of an open file". Ideally a checker would allow the user to define pairs of lock/unlock operation using some kind of annotation mechanism.
Repository: vscode
Issue: 'Switch Output' dropdown closes when a new item is added
Labels: bug,dropdown,confirmed,papercut :drop_of_blood:

Type: <b>Bug</b>

I want to switch the Output window between sources, but I have to wait for all active extensions to finish loading or else the dropdown will keep closing.

To reproduce:

1. Open VSCode on a file which will cause some heavy extensions to load, e.g. C# or Apex
2. Open 'Switch Output' dropdown

VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:02.548Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8 x 3000)|
|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>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.90GB (19.42GB free)|
|Process Argv|--crash-reporter-id fdb18783-4de2-4006-84bc-43b55050e930|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (18)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|2.4.0
prettier-vscode|esb|9.12.0
csharp|ms-|1.25.7
data-workspace-vscode|ms-|0.4.0
mssql|ms-|1.18.0
sql-bindings-vscode|ms-|0.3.0
sql-database-projects-vscode|ms-|0.21.0
salesforce-vscode-slds|sal|1.4.8
salesforcedx-vscode|sal|57.10.2
salesforcedx-vscode-apex|sal|57.10.2
salesforcedx-vscode-apex-debugger|sal|57.10.2
salesforcedx-vscode-apex-replay-debugger|sal|57.10.2
salesforcedx-vscode-core|sal|57.10.2
salesforcedx-vscode-lightning|sal|57.10.2
salesforcedx-vscode-lwc|sal|57.10.2
salesforcedx-vscode-soql|sal|57.10.2
salesforcedx-vscode-visualforce|sal|57.10.2
</details><details>


<!-- generated by issue reporter -->
Repository: go
Issue: cmd/go/internal/envcmd: double check plan 9 behavior in PrintEnv when null byte present in value
Labels: ExpertNeeded,OS-Plan9,NeedsInvestigation

We'd like a plan 9 expert to double check this: In PrintEnv in cmd/go/internal/envcmd/env.go, plan9's handling behavior is different based on whether there's a null byte. If there's not a null byte present it quotes the string, and if there isn't it puts them in a parenthesized list, but doesn't quote each of the listed strings. We want to make sure that not quoting each of the strings in the list is the intended behavior.
Repository: go
Issue: x/tools/gopls: clarify supported operating systems
Labels: gopls,Tools

We have experienced a fair amount of friction with gopls tests on e.g. plan9, android, illumos, and solaris.  While test failures on these operating systems _occasionally_ turn up real gopls bugs, in my experience failures are more often due to builder problems, resource constraints, and/or bugs in the toolchain. Given that (I assume) few if any of our users are on some of these operating systems, it is almost certain that our resources devoted to these builders results in a net loss for our users.

Unlike other projects on the Go team, gopls is designed for a relatively narrow use-case: development environments. We should not expend resources on ports that are unlikely to serve this use-case for a large number of users. However, we do not specify supported operating systems in our [README](https://github.com/golang/tools/blob/master/gopls/README.md).

We should specify precisely which operating systems we aim to support, and disable builders for others.  At the very least, we will support linux, windows, darwin, and other BSD-like operating systems. I am open to others, but do not want to commit to support if there is no demand.

CC @bcmills @adonovan
Repository: vscode
Issue: Improved visual image diffing in source control
Labels: feature-request,diff-editor

Right now for diffing two images (e.g. .png files), VSCode's source control tab supports side-by-side. This is fine for very obvious diffs, but not possible to tell what changed with subtle diffs. Some workflows require image diffing for validating graphics or UI changes, and it would be helpful to be able to visualize subtle image diffs for this as well. Dedicated diff tools often support other image diffing views like an overlap view that highlights the areas that are different, and it would be helpful if VSCode's source control diff had functionality like that.
Repository: flutter
Issue: Migrate engine C++ TUs to C++20.
Labels: engine,c: proposal,P3,c: tech-debt,team-engine,triaged-engine

The Flutter Engine assumes C++17 for all its translation units today. The toolchains and standard libraries have been capable of C++20 for a while. This issue tracks updating the the version to 20, modernizing code where it makes sense and allowing newer code to use modern features.
Repository: flutter
Issue: Investigate libgrapheme
Labels: engine,dependency: skia,a: typography,platform-web,e: web_canvaskit,P2,team-web,triaged-web

[Libgrapheme](https://libs.suckless.org/libgrapheme/) is an interesting project providing a new smaller and more efficient implementation of ICU. We would like to investigate it and see if it will work for us.

Initial CLs:
- https://skia-review.googlesource.com/c/skia/+/615217
- https://skia-review.googlesource.com/c/skia/+/674676
- https://skia-review.googlesource.com/c/skia/+/694699
Repository: flutter
Issue: Devicelab capacity for running host-side benchmarks that don't need a device
Labels: team-infra,P3,triaged-infra

We have some benchmarks like `analyzer_benchmark` that would like to run on a single non-VM Linux configuration in order to get consistent results.

When we moved `analyzer_benchmark` to a VM for https://github.com/flutter/flutter/issues/124065, the results became very unstable. See https://flutter-flutter-perf.skia.org/e/?begin=1414088239&dots=false&end=1683225253&queries=sub_result%3Dflutter_repo_watch_maximum&requestType=0.

It would be nice to have some machines to run benchmarks on in the devicelab that don't have phones attached. Does this already exist?

cc @yusuf-goog @keyonghan
Repository: PowerToys
Issue: CRON for anything (executables, reminders, etc.)
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be interesting to have a CRON that allows to schedule periodic program executions, create pop-ups with reminders, even trigger web services and display their result in a pop-up, just to name a few examples.

A simple syntax could be used, with the possibility of a more advanced syntax, inherited from *NIX operating systems.
           30 7 20 11 *  /home/user/scripts/update.sh
           0 0 9-18 * MON-FRI  /home/user/scripts/backup.sh
           
           (Like JIRA)
           
           
![image](https://user-images.githubusercontent.com/61297862/236306634-c4880b14-1059-4b5f-928c-962ae42c8ae2.png)
![image](https://user-images.githubusercontent.com/61297862/236306675-6c4e4e80-0a6e-4971-a4d7-13520998e9f9.png)
![image](https://user-images.githubusercontent.com/61297862/236306712-f003c82f-ea27-477d-95a1-aa894ffdc23b.png)
![image](https://user-images.githubusercontent.com/61297862/236306763-6df38acd-797d-49e1-bb78-5ee267eb41cf.png)


### Scenario when this would be used?

It could be used to automate tasks, such as an executable that runs through a directory, processes files and then sends an email documenting what has been done, or to send a periodic reminder, such as taking a medication, etc.

### Supporting information

It would be interesting to have a CRON that allows to schedule periodic program executions, create pop-ups with reminders, even trigger web services and display their result in a pop-up, just to name a few examples.

A simple syntax could be used, with the possibility of a more advanced syntax, inherited from *NIX operating systems.
           30 7 20 11 *  /home/usuario/scripts/actualizar.sh
           0 0 9-18 * MON-FRI
Repository: TypeScript
Issue: Support import of jsonc file to infer type
Labels: Suggestion,In Discussion

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms
typescript
jsonc

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

json jsonc

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
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, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion
Enable supporting import of jsonc file to provide typing information.

<!-- A summary of what you'd like to see added or changed -->

```
import * as data from './test.jsonc';

type myType = typeof data;
```

The import statement for jsonc is not supported today.

## 📃 Motivating Example

<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->
```
import * as data from './test.jsonc';

type myType = typeof data;
```
## 💻 Use Cases

<!--
  What do you want to use this for?
  What shortcomings exist with current approaches?
  What workarounds are you using in the meantime?
-->

Our scenario auto generates UX based on declarative jsonc file. 
We have a requirement to load and infer the type specified in the jsonc file to invoke some component in the UX. 
There is no typing support currently and workaround is to manually construct the data.
Repository: go
Issue: x/tools/go/packages: TestConfigDir failures
Labels: Testing,help wanted,NeedsInvestigation,Tools

```
#!watchflakes
post <- pkg == "golang.org/x/tools/go/packages" && test == "TestConfigDir"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/55a17607834dcc641b6b2f30861f460bdb032be1)):

    --- FAIL: TestConfigDir (0.00s)
        --- FAIL: TestConfigDir/Modules (134.14s)
            packages_test.go:481: dir "/opt/golang/tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/TestConfigDir_Modules2691312952/fake", pattern "./b": got , want "b"
            packages_test.go:490: dir "/opt/golang/tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/TestConfigDir_Modules2691312952/fake", pattern "./b": error true, want false


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: go/types: TestImplicitsInfo failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "go/types" && test == "TestImplicitsInfo"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/31efb83127190acd8517165a6b5fe44d93b2b002)):

    --- FAIL: TestImplicitsInfo (0.64s)
    panic: p2:1:22: could not import fmt (can't find import: "fmt") [recovered]
    	panic: p2:1:22: could not import fmt (can't find import: "fmt")
    
    goroutine 78 [running]:
    panic({0x1476cc0?, 0xc000418000?})
    	/tmp/buildlet/go/src/runtime/panic.go:1017 +0x3ac fp=0xc0001436a8 sp=0xc0001435f8 pc=0x1086e8c
    testing.tRunner.func1.2({0x1476cc0, 0xc000418000})
    	/tmp/buildlet/go/src/testing/testing.go:1545 +0x366 fp=0xc000143780 sp=0xc0001436a8 pc=0x11619e6
    testing.tRunner.func1()
    	/tmp/buildlet/go/src/testing/testing.go:1548 +0x650 fp=0xc000143970 sp=0xc000143780 pc=0x1161290
    panic({0x1476cc0?, 0xc000418000?})
    	/tmp/buildlet/go/src/runtime/panic.go:920 +0x270 fp=0xc000143a20 sp=0xc000143970 pc=0x1086d50
    go/types_test.mustTypecheck(...)
    	/tmp/buildlet/go/src/go/types/api_test.go:50
    go/types_test.TestImplicitsInfo(0xc0003a6820)
    	/tmp/buildlet/go/src/go/types/api_test.go:867 +0x6bd fp=0xc000143e98 sp=0xc000143a20 pc=0x13d043d
    testing.tRunner(0xc0003a6820, 0x14b6260)
    	/tmp/buildlet/go/src/testing/testing.go:1595 +0x239 fp=0xc000143fb0 sp=0xc000143e98 pc=0x1160b39
    testing.(*T).Run.func1()
    	/tmp/buildlet/go/src/testing/testing.go:1648 +0x45 fp=0xc000143fe0 sp=0xc000143fb0 pc=0x1162645
    runtime.goexit()
    	/tmp/buildlet/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc000143fe8 sp=0xc000143fe0 pc=0x10bcde1
    created by testing.(*T).Run in goroutine 1
    	/tmp/buildlet/go/src/testing/testing.go:1648 +0x836


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