sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: There should be a way in the vscode API to resolve configuration variables
Labels: feature-request,variable-resolving

<!-- ⚠️⚠️ 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. -->
Maybe there is, but I have not been able to find it. There has been similar questions posted but no real solution given. Only workarounds for specific use cases.

When writing extensions it is often needed to read configuration settings (vscode.workspace.getConfiguation). 
Configuration settings could be making use of variable references like ${workspaceFolder}.
This references are not being resolved by the vscode.WorkspaceConfiguration class.
The developer is left to resolve those variable references, which can be error prompt and a hurdle in writing extensions.
Maybe ${workspaceFolder} is an easy one to code for ,but there is a number of variations and also references to environment variables ${env:<variable name>}, or even other configuration settings like ${config:<variable name>}

Looking at the vscode code itself it seems to be making use of a IConfigurationResolverService, but this service is not exposed through the vscode api. 
Exposing that service could be a way to provide the developer with a way to resolve variables.

Another implementation option would be to enhance the vscode.WorkspaceConfiguration with getResolved methods that would act exactly like the get methods excepts the values returned would be resolved.

If there is indeed a way to do this already please point me in the right direction.

Thanks.
Repository: godot
Issue: Async signal handler causes error "Attempted to convert an unmarshallable managed type to Variant. Name: 'Task`1'"
Labels: discussion,topic:dotnet

### Godot version

3.4.2 stable

### System information

macOS Monterey 12.1 on MacBook Air M1 (8 cores, 16GB RAM)

### Issue description

Error:

```
E 0:00:08.059   mono_object_to_variant_impl: Attempted to convert an unmarshallable managed type to Variant. Name: 'Task`1' Encoding: 21.
  <C++ Error>   Method failed. Returning: Variant()
  <C++ Source>  modules/mono/mono_gd/gd_mono_marshal.cpp:927 @ mono_object_to_variant_impl()
  <Stack Trace> :0 @ void Godot.NativeCalls.godot_icall_2_635(IntPtr , IntPtr , System.String , System.Object[] )()
                Object.cs:364 @ void Godot.Object.EmitSignal(System.String , System.Object[] )()
                Player.cs:96 @ void Player._PhysicsProcess(Single )()
```

The flow is essentially: 
- Player emits signal `EmitSignal(nameof(ArrivedAtDestination), Position);`
- In `_Ready()`, game connects to signal: `Player.Connect(nameof(Player.ArrivedAtDestination), this, nameof(HandlePlayerArrivedAtDestination));`

Making the signal handler async causes the error above:

```csharp
async Task HandlePlayerArrivedAtDestination(Vector2 localPos)
{
  await SomeAsyncMethod();
}
```

Changing the handler to `void` fixes the issue:

```csharp
void HandlePlayerArrivedAtDestination(Vector2 localPos)
{
  SomeAsyncMethod();
}
```

Problem: async calls cannot be awaited if the handler is `void`.

### Steps to reproduce

Emit a signal and make the connected handler `async Task`.

Interestingly, even with the error showing everything seems to work just fine. 

### Minimal reproduction project

_No response_
Repository: rust
Issue: rustdoc: cannot resolve links to associated items on more complex primitive types
Labels: T-rustdoc,A-associated-items,C-bug,A-intra-doc-links

As a continuation of https://github.com/rust-lang/rust/issues/90703

#92443 fixes this for "simple" primitives such as:
char, str, bool, never, usize, u{8, 16, 32, 64, 128}, isize, i{8, 16, 32, 64, 128} and f32, f64. However, for types that wrap around other types, such as Tuple, Array, Slice, RawPtr, etc. I was not able to make it work at first try. See the discussion here: https://github.com/rust-lang/rust/pull/92443#discussion_r776808181

Basically we want these comments to have links to the respective primitive type's implementation, e.g.:

``` rust
/// [`<&[u32]>::fmt()`] [`<(u32, u32)>::eq()`]
```

Should link to
- https://doc.rust-lang.org/std/primitive.slice.html#impl-Eq
- https://doc.rust-lang.org/std/primitive.tuple.html#impl-Debug-6

Note that for the tuple, we ideally want to link to the implementation for the specified size of the tuple.

Not sure if we also need to know whether the type inside the tuple actually has the necessary traits, e.g. in the case of `[(a, b)::fmt()]`, `a` and `b` should also have `Debug`. This is pretty complex and we might be able to get away without it.
Repository: rust
Issue: Inconsistency between Clippy and Rustdoc build stages
Labels: T-rustdoc,T-bootstrap,C-bug,A-clippy

If I run:

```
./x.py build src/tools/rustdoc --stage 1
```

Then I get a `rustdoc` built against my local `stage1` compiler

However, if I run:

```
./x.py build src/tools/clippy --stage 1
```

Then bootstrap will attempt to build a **stage2** compiler, and compile Clippy against it. In order to get the same result as with Rustdoc, I need to use  `./x.py build src/tools/clippy --stage 0`

As far as I know, both Clippy and Rustdoc are both the same 'kind' of tool (they are a frontend that runs some of the compiler's passes), so `--stage N` should give the same result with both of them.
Repository: rust
Issue: Error message improvement for a missing comma syntax error in `.fold()`
Labels: A-diagnostics,T-compiler

Given the following code ([play.rust-lang.org link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=eb1c2f0d199fae770683aa7a0d08a5ee)):

```rust
fn main() {
    let numbers = vec![1, 2, 3];

    // Note the missing comma ---------V
    let sum: u8 = numbers.iter().fold(0 |acc, x| acc + x);

    println!("Sum is: {}", sum);
}
```

The current output is (in both stable and nightly):

```
   Compiling playground v0.0.1 (/playground)
error[E0425]: cannot find value `acc` in this scope
 --> src/main.rs:5:42
  |
5 |     let sum: u8 = numbers.iter().fold(0 |acc, x| acc + x);
  |                                          ^^^ not found in this scope

error[E0425]: cannot find value `x` in this scope
 --> src/main.rs:5:47
  |
5 |     let sum: u8 = numbers.iter().fold(0 |acc, x| acc + x);
  |                                               ^ not found in this scope

error[E0425]: cannot find value `acc` in this scope
 --> src/main.rs:5:50
  |
5 |     let sum: u8 = numbers.iter().fold(0 |acc, x| acc + x);
  |                                                  ^^^ not found in this scope

error[E0425]: cannot find value `x` in this scope
 --> src/main.rs:5:56
  |
5 |     let sum: u8 = numbers.iter().fold(0 |acc, x| acc + x);
  |                                                        ^ not found in this scope

For more information about this error, try `rustc --explain E0425`.
error: could not compile `playground` due to 4 previous errors
```

Ideally the output should look like:

```
   Compiling playground v0.0.1 (/playground)
error[E0425]: cannot find value `acc` in this scope
 --> src/main.rs:5:42
  |
5 |     let sum: u8 = numbers.iter().fold(0 |acc, x| acc + x);
   |                                      ^ help: Consider adding a comma after `0`.
```

Just a small suggestion to help point out an easy syntax mistake that (hopefully) isn't too hard to detect!

This could also apply to other functions who take two arguments, (x, func), especially other methods of Iter such as `map()`, `filter()`, etc.
Repository: PowerToys
Issue: Update the Localization Dev Doc to explain the new process
Labels: Area-Localization,Issue-Docs

### Provide a description of requested docs changes

We don't use `LocProject.json` or `lcl` files any longer, and we don't use the `build-*.cmd` scripts that it mentions either.
Repository: material-ui
Issue: MUI5 override does not work as expected - duplications of code
Labels: new feature,status: expected behavior

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

In MUI4 I was able to override initial style code.
But now in 5 version I can't get the same behavior. 

```ts
const theme = createTheme({
  components: {
    // Name of the component
    MuiButton: {
      styleOverrides: {
        // Name of the slot
        root: {
          // Some CSS
          fontSize: '1rem',
        },
      },
    },
  },
});
```

I am getting result with redundant CSS output code

```
font-size: 0.875rem; // initial Button value
font-size: 1rem; // my override
```

 


### Expected behavior 🤔

It must be merged to **override** but not adds under the bottom

```
...
font-size: 1rem;
```

_Few weeks ago - I checked your demo page (https://mui.com/customization/theme-components/#global-style-overrides)
I noticed (in devtools) that it works as I wanted - but now it has changed behavior_

--- 

Also, now `undefined` hack is not working and I do not know how to remove unwanted styles

e.g

```ts
const theme = createTheme({
  components: {
    MuiButton: {
      styleOverrides: {
        root: {
          fontSize: '1rem',
          borderRadius: undefined // removes the `border-radius` in output CSS. works in MUI4
        },
      },
    },
  },
});
```

### Steps to reproduce 🕹

Steps to reproduce

1. Go to the one of yours "overriding" demo - https://codesandbox.io/s/gc1lb?file=/demo.js 
2. Check Button styles in devtools

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
System:
    OS: macOS 12.0.1
Binaries:
    Node: 16.13.0 - /usr/local/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
Browsers:
    Chrome: 96.0.4664.110
    Edge: Not Found
    Firefox: 94.0.2
    Safari: 15.1
npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.63 
    @mui/icons-material: ^5.2.5 => 5.2.5 
    @mui/material: ^5.2.7 => 5.2.7 
    @mui/private-theming:  5.2.3 
    @mui/styled-engine:  5.2.6 
    @mui/styles: ^5.2.3 => 5.2.3 
    @mui/system:  5.2.6 
    @mui/types:  7.1.0 
    @mui/utils:  5.2.3 
    @types/react: ^17.0.34 => 17.0.34 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    typescript: ^4.4.4 => 4.4.4 
```
</details>
Repository: storybook
Issue: ArgsTable View Mode for Docs iFrame Embed
Labels: feature request

**Is your feature request related to a problem? Please describe**
Hi, I'm working on design system docs. We plan to use the ArgsTable from our Storybook docs for our design system docs site.  We are following the advice given here https://storybook.js.org/docs/react/sharing/embed

**Describe the solution you'd like**
a new viewMode `viewMode=controls`?

**Describe alternatives you've considered**
We are currently rendering using the docs page mode documented in the link above.

**Are you able to assist to bring the feature to reality?**
yes!

**Additional context**
Repository: rust
Issue: VecDeque missing operations for "front" handling.
Labels: C-feature-request

From the docs of VecDeque:

"""
A double-ended queue implemented with a growable ring buffer.

The “default” usage of this type as a queue is to use push_back to add to the queue, and pop_front to remove from the queue. extend and append push onto the back in this manner, and iterating over VecDeque goes front to back.
"""

From this, we can assume the default way to use VecDeque when visualised is:

```
 front [ a, b, c, d, e ] back
 # push_back(f)
 front [ a, b, c, d, e, f ] back
```

VecDeque has a number of operations to reduce the size of the content in the VecDeque such as truncate or split_off, but these assume you want to truncate or split from the back.

```
 front [ a, b, c, d, e, f ] back
 # truncate(4)
 front [ a, b, c, d ] back
```

```
 front [ a, b, c, d, e, f ] back
 # split_off(4)
 front [ a, b, c, d ] back  ->  front [ e, f ] back
```

However, what is missing is equivalents for operating on the *front* of the VecDeque

```
 front [ a, b, c, d, e, f ] back
 # truncate_front(4)
 front [ c, d, e, f ] back
```

This created confusion for me wanting to use VecDeque as an *ordered* ringbuffer since VecDeque will iterate front to back, and recommends you push_back, but trying to maintain a fixed capacity requires you to either manually pop_front to len, OR you need to actually store your VecDeque in reverse, and rely on iter().rev() allowing you to use truncate.

Since VecDeque intends to be "double ended" it would be useful and convenient to have a number of the methods given front variants. My non-exhaustive list is:

* truncate
* split_off
Repository: transformers
Issue: [Benchmark] HF Trainer on A100
Labels: Benchmarks,WIP

# 🖥 Benchmarking `transformers` w/ HF Trainer on a single A100 40GB

We are going to use a special benchmarking tool that will do all the work for us. https://github.com/huggingface/transformers/pull/14934

This is the index post and specific benchmarks are in their own posts below:

1. [fp16 vs bf16 vs tf32 vs fp32](https://github.com/huggingface/transformers/issues/15026#issuecomment-1004543189)
2. [gradient accumulation steps](https://github.com/huggingface/transformers/issues/15026#issuecomment-1004592231)
3. [batch size](https://github.com/huggingface/transformers/issues/15026#issuecomment-1005033957)
4. [gradient checkpointing](https://github.com/huggingface/transformers/issues/15026#issuecomment-1005034578)
5. [optimizers](https://github.com/huggingface/transformers/issues/15026#issuecomment-1005220263)
6. [combining winning strategies](https://github.com/huggingface/transformers/issues/15026#issuecomment-1005227577) **~3x speed improvement!**
7. [RTX-3090 vs A100](https://github.com/huggingface/transformers/issues/15026#issuecomment-1005235845)

Note that each benchmark was run only once, so multiple runs and averaging is probably going to give slightly different results. The purpose here though is to see relative differences roughly and not try to give an exact number.

See also the [same benchmarks for RTX-3090](https://github.com/huggingface/transformers/issues/14608)
Repository: go
Issue: spec: allow string(t) conversion in generics where t []T, T byte|rune
Labels: LanguageChange,Proposal,generics,LanguageChangeReview

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18beta1 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes (1.18 beta)

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\tamir.bahar\AppData\Local\go-build
set GOENV=C:\Users\tamir.bahar\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\tamir.bahar\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\tamir.bahar\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.18beta1
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\TAMIR~1.BAH\AppData\Local\Temp\go-build3924345009=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

Compile the following code: 
```
func toString[T byte|rune](slice []T) string {
   return string(slice)
}
```


### What did you expect to see?

Since `string(...)` can take either a `[]byte` or a `[]rune`, I expected the code to compile successfully.

### What did you see instead?

Compilation fails with:
```
cannot convert slice (variable of type []T) to type string
```

See https://gotipplay.golang.org/p/ZgvdU6Xv9jB
Repository: godot
Issue: Godot reports error that does not exist
Labels: bug,topic:gdscript

### Godot version

v3.4.2.stable.official [45eaa2daf]

### System information

w10 64

### Issue description
With autosave after 1 second option activated
When the code is changed while the editor is running an instance, when it is run again godot reports an error that does not exist.

Watch this video (I use two monitors, in the video you will only see godot).
The first run reports an error.
I change the code.
The next run reports an error that does not exist.

https://user-images.githubusercontent.com/19652075/148040362-19f57b35-24e0-4f31-b39c-c2a2d3ee9bb5.mp4




### Steps to reproduce

See the video

### Minimal reproduction project

...
Repository: flutter
Issue: [TextField]`backgroundColor` covers/hides cursor and text selection
Labels: a: text input,framework,f: material design,has reproducible steps,found in release: 2.8,found in release: 2.9,team-design,triaged-design

Setting `backgroundColor` on `TextField` appears to mask cursor and text selection. That is when you type some text in a text box and move cursor back it disappears. Selecting text doesn't show any visual indicator of a selection either.

Below is a code to reproduce this.

I observe this behavior at least on linux and android.

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: TextField(
          style: new TextStyle(backgroundColor: Colors.yellow),
        ),
      ),
    );
  }
}
```
https://dartpad.dev/?id=c76c8bd3543de7eeea64cd6d0b225835 <== you can test it here
Repository: electron
Issue: [Bug]: Window shows white screen when frame rate limit is disabled, window is maximised and intense webpage is loaded
Labels: bug :beetle:

### 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 bug report that matches the one I want to file, without success.

### Electron Version

16.0.6, 17.1.0, 18.0.0-alpha.5, 19.0.0-nightly.20220209, 21.1.0

### What operating system are you using?

Windows

### Operating System Version

Windows 10 version 20H2, Windows 11 version 21H2

### What arch are you using?

x64

### Last Known Working Electron version

11.5.0

### Expected Behavior

Web page displays its content

### Actual Behavior

Web page only shows up as a white-screen. Links and buttons are still interactable but the window does not render anything until the gpu process is restarted.

### Testcase Gist URL

https://gist.github.com/jf908/860590047b274f8ff6c6e0db731cc52b

### Additional Information

I suppose there is some kind of race condition going on with the GPU process.

This problem only seems to occur when loading certain websites but I haven't identified what in the website is required to cause this. I have also reproduced this by loading https://github.com/home for example but a lot less reliably.

A "workaround" to solve this problem while the app is still running is to restart the gpu process in task manager.
Repository: create-react-app
Issue: CRA 5.0 fails to hot-reload in a docker container built
Labels: needs triage,issue: bug report

Apolgozies for being super inexperience, there many layers and dont know which part of the problem I should debug like is it docker, is npm package manager, is it react-scripts@5.0.0 itself? 

### Describe the bug

CRA 5.0 fails to hot-reload in a docker container with using CHOKIDAR_USEPOLLING

Yes its mounted correctly. I checked many many times.

### Environment
OS:Windows 10 
VScode 
WSL 
Docker 4.2.0

### Steps to reproduce
Lets say you 

```npx create-react-app my-app```

you start the server it works normally, however your workflow at a company uses docker containers with react for development 

you use the newer version of react-scripts@5.0.0 

dockerfile created

```FROM node:14
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
ENV PORT=3000
EXPOSE 3000
CMD ["npm", "run", "start"]
```

```docker build -t react-test-2 ./ ```

```docker run -e CHOKIDAR_USEPOLLING=true -v D:\test-react-app\my-app:/app -it --name react-test-app2 -p 3000:3000 react-test-2```

you triple check that bind mount is working. Try different directories, check docker, check Chokidar library, 

So I went back to the version that worked with in react-scripts@4.0.3 it somehow works, try again different techniques 

I see when I ran react-script@5.0.0 

I get (node:31) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP MIDDLEWARE] DeprecationWarning: 'AfterStep Middleware' option is deprecated. Please use the 'setupMiddlewares' option.

Or the webpack log displays on start up don't know if its a issue or bug yet related 
https://github.com/facebook/create-react-app/issues/11871 

Or maybe it's 
# npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

### Expected behavior

React to hot-reload as it did in react-scripts@4.0.3 inside a mounted volume docker container

### Actual behavior
React-scripts@5.0.0 fails to hot-reload inside a mounted volume docker container

### Reproducible demo
https://github.com/Gresliebear/Reproducible-demo

### Solution 

Downgrade react-scripts@5.0.0 to react-scripts@4.0.3 

However your will expose to vulerabilites which 2 are critical 

![image](https://user-images.githubusercontent.com/13157730/148066228-6324c4bb-6cee-4699-a16f-de53868a5bef.png)