sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Autocomplete]  The onHighlightChange event is triggered by child elements of the list item
Labels: bug 🐛,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Children of the list item are triggering `onHighlightChange` unexpectedly.

In the code below the `span` will trigger `onHighlightChange`

```js
      renderOption={(p, { label }) => {
        return (
          <div {...p}>
            <span>{label}</span>
          </div>
        );
      }}
```
![Animation](https://user-images.githubusercontent.com/4041334/157394061-0b648964-af49-4372-948e-2acb16b39e37.gif)


### Expected behavior 🤔

The children of the list item should not trigger `onHighlightChange ` event.

### Steps to reproduce 🕹

Steps:

1. open [this codesandbox](https://codesandbox.io/s/onhighlightchange-issue-7xgbcv?file=/demo.tsx:440-589)
2. open console
3. open Autocomplete
4. mouse over an item label as shown in picture 
5. look at the console message count


### Context 🔦

By applying `pointerEvents: none` to the child elements, this problem can be solved, however I don't believe this is a viable solution since use may need to use child events. and I believe it should be handled internally.

### Your environment 🌎

<details>
```
  System:
    OS: Windows 10
  Browsers:
    Chrome:  Version 99.0.4844.51
```
</details>
Repository: vscode
Issue: [html] allow to turn off closing tags when not needed
Labels: feature-request,html

<!-- ⚠️⚠️ 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. -->

Ref: https://www.youtube.com/watch?v=lOWcwgt4dLQ
Eg. PHP, all HTML tags etc.
Repository: create-react-app
Issue: Upgrading dotenv for multiline support
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?
React apps do not support .env files with multiline variables
dotenv got proper multiline support for .env-files in version **15.0.1** and is currently on version **16.0.0**
create-react-app is still on dotenv **10.0.0**

### Describe the solution you'd like
Upgrading the dotenv version to **15.0.1** or higher
Repository: material-ui
Issue: Configure timezone for date and time picker components
Labels: new feature,component: date time picker

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Currently there does not seem to be a way to specify what timezone the value should be in, which means the output date is in the system's timezone. The best workaround I cant think of is to convert the system datetime to a string, and then parse that string using some timezone-configurable function. Maybe a dateAdapter with `string` as a `DateIOType` would remove some of the conversion complexity, and allow to easily implement other `DateIOType`s component on top.

The only problem I can think of which may interfere with this approach is DST, which gives double meaning, or no meaning, to certain datetime values depending on the configured timezone. So maybe it's not a good idea to split timezone configuration away from pickers, and it would be better if either the `LocalizationProvider` or the picker component accepted a `timezone` prop. Or both.

### Examples 🌈

_No response_

### Motivation 🔦

It may make sense to have a picker that returns date in a timezone different than that of the system in the case of event scheduling, since events may be happening in a different timezone than that of the system.
Repository: svelte
Issue: Support optional transitions
Labels: transition/animation

### Describe the problem

It is possible to set transitions via props when creating Svelte components:

```svelte
<script>
export let transition;
</script>

<p transition:transition|local>Hi!</p>
```

However, they cannot be optional:
```svelte
<script>
export let transition = undefined;
</script>

<p transition:transition|local>Hi!</p>
```

Error thrown if transition is undefined:
![Screenshot 2022-03-09 at 11 41 32](https://user-images.githubusercontent.com/48158184/157425729-eff22f22-d987-467f-ae5b-280b42b9a617.png)


### Describe the proposed solution

Check if transition is a function before running it. 

The current implementation does not check if fn is of type `"function"`
![Screenshot 2022-03-09 at 11 42 50](https://user-images.githubusercontent.com/48158184/157425967-bf88ecea-dc6d-4779-b194-6b69919c5498.png)

### Alternatives considered

Setting a default empty empty function:

```svelte
<script>
export let transition = () => {};
</script>

<p transition:transition|local>Hi!</p>
```

However, this is a potential memory leak until [this pr](https://github.com/sveltejs/svelte/pull/7260) is merged.

### Importance

would make my life easier
Repository: node
Issue: don't use `TextDecoder` + `arrayBuffer()` in `blob.text()`
Labels: buffer

...Use TextDecoderStream Instead. ( or stream-consumers.text() )
Here is the problem: https://github.com/nodejs/node/blob/6b004f1bb14a1f06066a087f1e1c12c577dc7568/lib/internal/blob.js#L312-L313

### Version

17.5

### Platform

mac

### Subsystem

_No response_

### What steps will reproduce the bug?

```js
const { Blob } = require('buffer')
const header = 24;
const bytes = new Uint8Array( (512 * 1024 * 1024) + header );
const blob = new Blob([bytes])
const text = await blob.text()
const length = text.length
```

### How often does it reproduce? Is there a required condition?

every single time

### What is the expected behavior?

to read a 500mb + blob using `blob.text()`

A solution i'm using in fetch-blob is using the [streaming](https://github.com/node-fetch/fetch-blob/blob/dc295883669fbc41d39d502ffbae36f1c12f580a/index.js#L118-L127) approach 

```js
const { Blob } = require('buffer')
const header = 24;
const bytes = new Uint8Array( (512 * 1024 * 1024) + header );
const blob = new Blob([bytes])

let res = ''

const iterable = blob.stream().pipeThrough(new TextDecoderStream())
for await (chunk of iterable) res += chunk
```

### What do you see instead?
```
Uncaught:
TypeError [ERR_ENCODING_INVALID_ENCODED_DATA]: The encoded data was not valid for encoding utf-8
    at __node_internal_captureLargerStackTrace (node:internal/errors:464:5)
    at new NodeError (node:internal/errors:371:5)
    at TextDecoder.decode (node:internal/encoding:429:15)
    at Blob.text (node:internal/blob:314:16)
    at async REPL5:1:39 {
  errno: 1,
  code: 'ERR_ENCODING_INVALID_ENCODED_DATA'
}
```
### Additional information

it's a disadvantage to use ArrayBuffer/TextEncoder in your [.text()](https://github.com/nodejs/node/blob/6b004f1bb14a1f06066a087f1e1c12c577dc7568/lib/internal/blob.js#L312-L313) method to read it as a string.

At the time when you read the blob as a text it will use 3x memory (the size of the blob, the size of the arrayBuffer and the size of the string) quite a large memory spike at this point, there is no chance for v8 to do a GC

there is also a problem in v8 that you can't create strings with more than 500 MiB
however it's fine to concat the strings using `str += 'foo'` to avoid this problem. (as strings can just be references point to other multiple strings with a size & offset)

See more info here: https://stackoverflow.com/questions/61271613/chrome-filereader-api-event-target-result
Repository: rust
Issue: `$val.$i` should suggest using a `tt` metavariable for `$i`
Labels: A-diagnostics,A-macros,T-compiler

~~1. Matching literals with constants:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=2e60491da5cd43301b9b64b26dc1e320~~
In nightly suggests to use `:tt`.

2. Indexing of tuples:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=571e5a9d34cee2250d1a716c6ae7c86d
Repository: node
Issue: Blob's type should not be all lowercased
Labels: buffer

(only parts of it should be lowercased)

### Version

17.5

### Platform

mac

### Subsystem

_No response_

### What steps will reproduce the bug?

A meta value can contain uppercase letters that are important to be kept as is
there is an ongoing [issue](https://github.com/w3c/FileAPI/issues/43) about this in the spec too about this.

```js
const type = 'multipart/form-data; boundary=----WebKitFormBoundaryDUbbET022Y1HGX5x'
new Blob(payload, { type }).type === type // false
```

The only thing that should be lowercased is the mimetype (multipart/form-data) and the keys (boundary) the value is important to keep it as is.
otherwise you would not be able to parse the payload correctly as you lose valuable information.

fetch-blob is more relaxed and don't cast anything to lowercase (as we are a bit lazy and don't have a proper mime type parser like [whatwg-mimetype](https://www.npmjs.com/package/whatwg-mimetype)) so we only keep the type string as is...

### How often does it reproduce? Is there a required condition?

every time

### What is the expected behavior?

to not lowercase the boundary value and instead keep it as is (and yield true instead.

```js
const type = 'multipart/form-data; boundary=----WebKitFormBoundaryDUbbET022Y1HGX5x'
new Blob(payload, { type }).type === type // true
```


```js
const type = 'mUltiPart/foRm-dAta; boundary=----WebKitFormBoundaryDUbbET022Y1HGX5x'
new Blob(payload, { type }).type === 'multipart/form-data; boundary=----WebKitFormBoundaryDUbbET022Y1HGX5x'
```

### What do you see instead?

every char in type is lowercased

### Additional information

https://github.com/w3c/FileAPI/issues/43
Repository: deno
Issue: Move webcrypto key store to Rust
Labels: chore,ext/crypto

To avoid passing the serialized key to every op.

It lives in JS atm:
https://github.com/denoland/deno/blob/8b2989c417db9090913f1cb6074ae961f4c14d5e/ext/crypto/00_crypto.js#L362
Repository: rust
Issue: A confusing compile error about lifetime of mutable reference after reborrowed
Labels: A-diagnostics,A-borrow-checker,T-compiler

## Code
```rust
let mut s = "s".to_string();

let mref = &mut s;
let ref1 = &*mref; // <- reborrow occurs here

// ^ the end of lifetime of `mref` I've thought

let ref2 = &s;
println!("{}, {}", ref1, ref2); 
```
The mutable reference `mref` were not used anymore after reborrowed. But It seems that it's lifetime were not over when I used `ref1`.

## Result
```
error[E0502]: cannot borrow `s` as immutable because it is also borrowed as mutable
   --> tests/borrow.rs:272:16
    |
267 |     let mref = &mut s;
    |                ------ mutable borrow occurs here
...
272 |     let ref2 = &s;
    |                ^^ immutable borrow occurs here
273 |     println!("{}, {}", ref1, ref2);
    |                        ---- mutable borrow later used here
```

##  Other case
```rust
        let mut s = "s".to_string();
        let mref = &mut s;
        let ref1: &String = mref as &String;
        let ref2 = &s;
        println!("{}, {}", ref1, ref2); 
```
Repository: create-react-app
Issue: Bug: Stuck on "Starting the development server" when parent folder contains '#'
Labels: Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 17.0.2

## Steps To Reproduce

1. Create folder with '#' in name ie: mkdir myfolder/#trash/
2. Create react app in folder: npx create-react-app myApp
3. Start app: npm start

## The current behavior
Gets stuck on "Starting the development server..." forever

## The expected behavior
It should start and run the app as expected when creating a new app or warn you about invalid parent directory name
Repository: flutter
Issue: `ui.FlutterView.render` should pass the window id to the engine
Labels: engine,P2,c: tech-debt,team-engine,triaged-engine

Currently, the parameter it passes is the `FlutterView` object itself instead of the `id`, and the engine side cannot find the corresponding window or window id based on this `FlutterView` object.
So we need to change 
```
void _render(Scene scene, FlutterView view) native 'PlatformConfiguration_render';
```
to 
```
void _render(Scene scene, Object id) native 'PlatformConfiguration_render';
```
Repository: go
Issue: cmd/go: "go test" seems to cache test build output when GODEBUG changes
Labels: NeedsInvestigation,GoCommand

I was using `GODEBUG=inittrace=1` to get some quick stats on the init cost of some packages via `go test`, and I noticed that even after I unset the variable, its output was still around - presumably via Go's cache.

As a repro:

```
$ go version
go version devel go1.19-c6d9b38dd8 Wed Mar 9 06:51:37 2022 +0000 linux/amd64
$ cd $(go env GOROOT)/src/encoding/json
$ GODEBUG=inittrace=1 go test -c -vet=off 2>&1 | wc -l
625
$ go test -c -vet=off 2>&1 | wc -l
488
```

It's unclear why the number of lines diminishes, but they're all still inittrace output.

`go build` does not show this bug, so presumably the bug is with the test cache:

```
$ GODEBUG=inittrace=1 go build 2>&1 | wc -l
137
$ go build 2>&1 | wc -l
0
```

Perhaps Go's cache should be taught to include `GODEBUG` as part of cache key hashes.
Repository: rust
Issue: Allow multiple #[unstable] attributes on one item
Labels: A-stability,T-compiler,E-help-wanted,E-medium,C-feature-request,F-staged_api

We sometimes have things that should be gated by multiple features. E.g. `ScopedJoinHandle::is_running` is part of `scoped_threads`, but also of `thread_is_running`. In these cases we now just apply only one of the `#[unstable]` attributes, and because of that sometimes accidentally stabilize something when only one of the features gets stabilized.

It'd be great if we could add multiple `#[unstable]` attributes to a single item. Allowing multiple `#[stable]` tags isn't a necessity. We could just remove the `#[unstable]` tag if the feature gets stabilized and there are other `#[unstable]` tags left. The most important part is that we don't forget about the other unstable tags and don't stabilize something by accident.

Another option would be multiple `feature =` arguments to `#[unstable]`.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: [Proposal]Support for rectangular icons
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Use case
Currently, flutter only supports square icons. `Icon` creates a `SizedBox` with equal width and height.
Packages like font_awesome_flutter, which contain rectangular icons, have to reimplement the `Icon` class and change the line where flutter defines the `SizedBox`.
This leads to a lot of duplicate code, unnecessary maintenance costs, unexpected behavior for developers, and slow adaptation of new features added to `Icon`.

Related issues:  fluttercommunity/font_awesome_flutter#132, fluttercommunity/font_awesome_flutter#204, fluttercommunity/font_awesome_flutter#201, fluttercommunity/font_awesome_flutter#198

## Proposal
There are multiple possible solutions:
- Add an aspectRatio attribute to `IconData` which is then used to scale the `Icon` width accordingly
- Allow overriding a method in `Icon` which sets the icon dimensions (would keep `FaIcon` in font_awesome_flutter)
- ~Automatically obtain icon dimensions using `IntrinsicWidth`/`IntrinsicHeight` (costly)~
Repository: create-react-app
Issue: Typescript version 4.6.2 is not supported by @typescript-eslint/typescript-estree which is a dependency of eslint-config-react-app
Labels: needs triage,issue: bug report

### Describe the bug
I am using [eslint-config-react-app](https://www.npmjs.com/package/eslint-config-react-app) which uses [@typescript-eslint/parser](https://www.npmjs.com/package/@typescript-eslint/parser) which then uses [@typescript-eslint/typescript-estree](https://www.npmjs.com/package/@typescript-eslint/typescript-estree) under the hood.

eslint-config-react-app is using version `5.5.0` of `@typescript-eslint/parser` which supports the following TS versions

```
>=3.3.1 <4.6.0
```

If I use the latest TS version, it throws this warning

```
=============

WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <4.6.0

YOUR TYPESCRIPT VERSION: 4.6.2

Please only submit bug reports when using the officially supported version.

=============
```

### Steps to reproduce

Using eslint-config-react-app outside of create-react-app

### Suggested Solution
@typescript-eslint/typescript-estree already fixed this issue in [this PR](https://github.com/typescript-eslint/typescript-eslint/pull/4615) with version `5.14.0` 

Updating `@typescript-eslint/parser` in `eslint-config-react-app` to the latest version will fix this.
Repository: go
Issue: x/pkgsite: large module pages are very slow to render
Labels: NeedsInvestigation,pkgsite,UX

The datadog-api-client-go packagesite page is... enormous. The raw HTML over the wire from the server is over 21MB, and rendering performance is abysmal. It can take up to 25 seconds for the page to become fully responsive to input. Obviously, this is an outlier package, but even given that, there seems like plenty of room here for performance work.

I fired up the Chrome performance tooling to see if there was something obvious:

<img width="1792" alt="Screen Shot 2022-03-09 at 10 15 49 AM" src="https://user-images.githubusercontent.com/2105458/157470995-a08ca38a-7d00-438c-910e-fede32042ea8.png">

Nearly all the time is spent in "Recalculate Style", presumably because the browser is constantly re-flowing the page as more and more HTML gets thrown at it?

### What is the URL of the page with the issue?

https://pkg.go.dev/github.com/DataDog/datadog-api-client-go@v1.10.0/api/v1/datadog

### What is your user agent?

`Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36`

### Screenshot

No rendering error, so screenshot isn't useful.

### What did you do?

Load the page.

### What did you expect to see?

Reasonable page-load times

### What did you see instead?

An extremely-long rendering block.
Repository: vscode
Issue: [scss] variables in @media parsing
Labels: bug,css-less-scss

Issue Type: <b>Bug</b>

I have the following line of code in my SCSS file:

    @media screen and  (max-width : 735px) and #{breakpoint(medium)}  {
        line-height: 120%;
    }

I get the error:

`
( expectedscss(css-lparentexpected)
`

The error occurs on the # of the #{breakpoint( part of the query.

The expected behavior is no parsing errors.

VS Code version: Code 1.65.1 (8908a9ca0f221f36507231afb39d2d8d1e182702, 2022-03-08T02:20:11.670Z)
OS version: Darwin x64 21.3.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz (6 x 3000)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|1, 2, 2|
|Memory (System)|32.00GB (3.64GB free)|
|Process Argv|--crash-reporter-id 4a82aa03-c351-4e29-9734-e795784ce9b9|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (9)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|2.2.2
phptools-vscode|DEV|1.7.8766
vscode-test-explorer|hbe|2.21.1
test-adapter-converter|ms-|0.1.5
format-html-in-php|rif|1.7.0
vscode-scss-formatter|sib|2.3.3
vscode-hexdump|sle|1.8.1
code-spell-checker|str|2.1.7
vscode-counter|uct|3.0.3


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
testflightcf:30433671
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30448491
dsvsc008:30440022
pythonvsnew555:30450167
vsbas813:30436447
vscscmwlcmc:30438804
vscgsvid1:30447480
helix:30440343
pynewfile477cf:30450039

```

</details>

<!-- generated by issue reporter -->
Repository: react
Issue: [DevTools Bug]: Out of Memory randomly on pages
Labels: Type: Bug,Status: Unconfirmed,Resolution: Needs More Information,Component: Developer Tools

### Website or app

https://bestellen-a.cito.nl

### Repro steps

Goto the site with the React DevTools extension installed.

After installing this plugin pages I noticed that chrome started giving "Out of Memory" error pages while visiting pages with react. Not all of the times but some times. After uninstalling the plugin the error message didn't show up anymore. Am I the first to experience this?

Is there anything I can supply to help figure out what is going wrong?

### How often does this bug happen?

Often

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: kubernetes
Issue: volumebinding unit tests run slowly
Labels: kind/cleanup,sig/scheduling,help wanted,lifecycle/stale,needs-triage

The unit tests in pkg pkg/scheduler/framework/plugins/volumebinding cost ~30 seconds on my m1max machine:

```
⇒  go test ./pkg/scheduler/framework/plugins/volumebinding -count 1
ok  	k8s.io/kubernetes/pkg/scheduler/framework/plugins/volumebinding	28.960s
```

Among the tests, a single test even costs ~5 seconds:

```
⇒  go test ./pkg/scheduler/framework/plugins/volumebinding -run TestCheckBindingsWithCSIMigration -count 1
ok  	k8s.io/kubernetes/pkg/scheduler/framework/plugins/volumebinding	5.077s
```

It doesn't look like a good signal. It may be worth taking a close look to polish the tests a bit.

/sig scheduling
/kind cleanup
/help