sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: Styles not added to shadow DOM when wrapping MUI in a library
Labels: external dependency,package: system

### Steps to reproduce

Link to live example: https://6698f74d46bade9e76f1d058--guileless-sorbet-bf347d.netlify.app/

https://github.com/MartinJaskulla/reproduction-library
https://github.com/MartinJaskulla/reproduction-library-user

1. git clone https://github.com/MartinJaskulla/reproduction-library-user
2. npm i
3. npm run dev
4. See the bug: MUI `<Button>` is unstyled, because emotion style sheets are added to `<head>` instead of shadow DOM
5. Comment out `Button,` and comment in `// import {Button} from "@mui/material";` in main.jsx
6. Bug gone

### Current behavior

`<Button>` looks like a native html `<button>` inside shadow DOM.

### Expected behavior

`<Button>` should look like a MUI button inside shadow DOM.

### Context

I created a component library for my company that wraps MUI and makes some adjustments. Everything works flawlessly. 

For a new feature we have to use my library inside shadow DOM meaning the project that is installing my component library is creating a custom element and wants to use the wrapped MUI components from my library inside it. I followed the documentation (https://mui.com/material-ui/customization/shadow-dom/) to do that. Somehow the styles do get added to the `<head>` instead of the shadow DOM.

I created a new library for my reproduction, in which I just re-export MUI as is (that is the only thing the library is doing):
https://github.com/MartinJaskulla/reproduction-library/blob/main/src/main.jsx
```ts
export * from "@mui/material";
```

If I install this library in a new project (https://github.com/MartinJaskulla/reproduction-library-user), then `import { Button } from "@mui/material";` adds the styles correctly to the shadow DOM, but `import { Button } from "reproduction-library";`  adds the styles to the `<head>` although the code of both buttons should be identical.

To me it looks like MUI only works inside shadow DOM if imported from `"@mui/material";`.


### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
 System:
    OS: macOS 14.5
  Binaries:
    Node: 22.2.0 - /opt/homebrew/bin/node
    npm: 10.7.0 - /opt/homebrew/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 126.0.6478.182
    Edge: Not Found
    Safari: 17.5
```
</details>


**Search keywords**: shadowdom library styles emotion
Repository: rust
Issue: Tracking issue for future-incompatibility lint `pub_use_of_private_extern_crate`
Labels: A-lints,A-resolve,A-visibility,T-lang,T-compiler,C-future-incompatibility,C-tracking-issue,A-crates

The `pub_use_of_private_extern_crate` lint detects a specific situation of re-exporting a private `extern crate`:

```rust,compile_fail
extern crate core;
pub use core as reexported_core;
```


A public `use` declaration should not be used to publicly re-export a private `extern crate`. `pub extern crate` should be used instead.This was historically allowed, but is not the intended behavior according to the visibility rules.

This used to be tracked as part of https://github.com/rust-lang/rust/issues/34537, but is only tangentially related so it got a new dedicated tracking issue.

### Related PRs
- https://github.com/rust-lang/rust/pull/127656 tried to make this a hard error, but there were too [many regressions](https://crater-reports.s3.amazonaws.com/pr-127656/index.html), mostly because several ancient versions of `bitflags` are still in use.
Repository: rust
Issue: Degradation from rustc 1.71.0 -> 1.79.0 ("infinite space" compile error not recognized anymore)
Labels: I-crash,T-compiler,regression-from-stable-to-stable,A-inference,C-bug

# Behaviour in rust version 1.79.0 (the bug)

I found a program that does

* successfully finish `cargo check`
* but does never build (it takes up as much space as it can get, and then inevitably crash)

on rust version 1.79.0:
```
rustc 1.79.0 (129f3b996 2024-06-10)
binary: rustc
commit-hash: 129f3b9964af4d4a709d1383930ade12dfe7c081
commit-date: 2024-06-10
host: x86_64-unknown-linux-gnu
release: 1.79.0
LLVM version: 18.1.7
```

# Behaviour in rust version 1.71.0 (before the degradation)

On rust version 1.71.0 this program failed the cargo check and build, which is the expected behaviour imo.


# The minimum working example 

```
use std::io::{self, BufRead};

fn main() -> Result<(), io::Error> {
  let stdin = io::stdin(); // We get `Stdin` here.
  let mut iterate_in = stdin.lock().lines();

  // that's how to run a single request for a number alone in a line
  let count = iterate_in.next().unwrap().unwrap().to_string().parse::<usize>().unwrap();

  let mut rects = vec![];
  for _ in 0..count {
    let vecline = iterate_in.next()
      .unwrap()
      .unwrap()
      .split_whitespace()
      .map(|s| s.parse::<u32>().unwrap()-1)
      .collect();

    let el = (rects[0],rects[1],rects[2],rects[3]);
    rects.push(el);
  }

  if let Some(solution) = rects.to_string() {
    for s in solution {
      println!("{} {}", s.0+1, s.1+1);
    }
  }

  Ok(())
}
```
Repository: vscode
Issue: Terminal sticky scroll can show up for 1 frame when using page down in a pager
Labels: bug,terminal-sticky-scroll

Repro:

1. On Windows
2. Enable sticky scroll
3. Open pwsh
4. Run `git diff` with more than a page of changes
5. Page up+down, 🐛 sticky scroll will show up for 1 frame every time page down is used

It rarely shows up in the gif due to low recording framerate

![Recording 2024-07-18 at 04 46 30](https://github.com/user-attachments/assets/3a81398d-ced8-41e7-b7fe-ff276e592d35)
Repository: rust
Issue: type alias `Plus2` is never used
Labels: A-lints,T-compiler,C-bug,E-needs-mcve,L-dead_code

### Summary

Some type is flagged by Clippy as never used, though it is used in an internal trait implementation

### Lint Name

dead_code

### Reproducer

I tried this code:

clone https://github.com/zama-ai/concrete-fft/commit/aeb75d4b7c5cc6b3031bf5b9f4730961f3132fe5

run pre commit checks, runs a clippy check:
make pcc

faulty clippy invokation:
```
RUSTFLAGS="-C target-cpu=native" cargo "+nightly-2024-07-18" clippy --all-targets \
        --features=serde -- --no-deps -D warnings
```

I saw this happen:

```
error: type alias `Plus2` is never used
  --> src/nat.rs:26:10
   |
26 | pub type Plus2<N> = Successor<Plus1<N>>;
   |          ^^^^^
   |
   = note: `-D dead-code` implied by `-D warnings`
   = help: to override `-D warnings` add `#[allow(dead_code)]`

error: type alias `Plus3` is never used
  --> src/nat.rs:27:10
   |
27 | pub type Plus3<N> = Successor<Plus2<N>>;
   |          ^^^^^

error: type alias `Plus4` is never used
  --> src/nat.rs:28:10
   |
28 | pub type Plus4<N> = Successor<Plus3<N>>;
   |          ^^^^^

error: could not compile `concrete-fft` (lib) due to 3 previous errors
```

I expected to see this happen:

No warning/error for these types as they are used in e.g. https://github.com/zama-ai/concrete-fft/blob/aeb75d4b7c5cc6b3031bf5b9f4730961f3132fe5/src/dit16.rs#L823

### Version

```text
rustc 1.81.0-nightly (fcc325f1b 2024-07-17)
binary: rustc
commit-hash: fcc325f1bc477975e2ce5ba534fe4c77ff8a8536
commit-date: 2024-07-17
host: x86_64-unknown-linux-gnu
release: 1.81.0-nightly
LLVM version: 18.1.7
```


### Additional Labels

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: rust
Issue: The Android CI prints unrelated things to stdout, ruining check-run-results tests.
Labels: O-android,A-meta,A-CI

See https://github.com/rust-lang/rust/pull/127003#issuecomment-2236125625

```
uploaded "$TEST_BUILD_DIR/path/to/test/a", waiting for result
```
Repository: angular
Issue: Support configuration of attachShadow when Custom Elements are created
Labels: area: elements

### Which @angular/* package(s) are relevant/related to the feature request?

elements, platform-browser

### Description

When Custom Elements instances are created (using @angular/elements) deep in the stack DOM's `attachShadow` method of host element is called:
https://github.com/angular/angular/blob/main/packages/platform-browser/src/dom/dom_renderer.ts#L424

I would like to inject additional configuration (right now only the default `mode: open` is used), specifically the `serializable: true` property, but there might be more use-cases for other config properties:
https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow#serializable


### Proposed solution

Allow to pass this config through Injector or as createCustomElement configuration.

### Alternatives considered

Make it possible or simplify to extend and override class of ShadowDomRenderer used internally by DomRendererFactory2.
Repository: angular
Issue: Deprecate "waitForAsync" in @angular/core/testing 
Labels: area: testing

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

With the Angular ecosystem moving towards a "zoneless" architecture and recent updates to the Angular documentation, I propose that we consider deprecating the waitForAsync utility. 

As a reference we can have a look to this [PR](https://github.com/angular/angular/pull/56388).

### Proposed solution

IMO, we can deprecate it in one of the upcoming version to make sure that the adoption of `waitForASycn` will be lower / less. And at some point can be removed.

### Alternatives considered

Relocate it to a dedicated location outside the core, providing zoneless applications with a specific entry point for accessing these utilities.
Repository: flutter
Issue: Color Migration in 3.22.0
Labels: framework,f: material design,d: api docs,P2,team-design,triaged-design

In the recent update, the background and onBackground colors were replaced with surface and onSurface, respectively. also the old surface and onSurface properties were replaced by surfaceContainer with options like Highest, High, Low, and Lowest. However, I noticed that there is no documented replacement for onSurface.

Could you please provide documentation on what the new equivalent for onsurface should be?
Thank you!
Repository: transformers
Issue: Using `numpy==2.0.0`
Labels: WIP

`transformers`  now remove the pin of `numpy<2.0.0`. However, some issues (with 3rd libraries) are known, and the following gives some guide:

- In an environment with `TensorFlow` and/or `Flax` --> downgrade to `numpy<2.0.0`
- issue with soxr --> `pip install soxr==0.4.0b1`
- issue with `faiss`  --> downgrade to `numpy<2.0.0`
- If error out with a message `using np.array(obj, copy=False) replace it with `np.asarray(obj) to allow a copy`: 
   - downgrade to `numpy<2.0.0`
   - or, install `datasets` dev. version
Repository: godot
Issue: Godot hangs when using ".GetAwaiter().GetResult()" in overrided Godot's method (e.q. _Ready) 
Labels: bug,needs testing,topic:dotnet

### Tested versions

- Reproducible in:
  - v4.1.4.stable.mono.official [fe0e8e557]
  - v4.2.2.stable.mono.official [15073afe3]
  - v4.3.beta3.mono.official [82cedc83c]

### System information

Godot v4.3.beta3.mono - Fedora Linux 40 (Workstation Edition) - Wayland - Vulkan (Forward+) - integrated AMD Radeon Graphics (RADV REMBRANDT) - AMD Ryzen 7 7735U with Radeon Graphics (16 Threads)

### Issue description

Since Godot doesn't like very much to perform operations on separate threads, I wanted to do asynchronous work in a synchronous way.
Consequently, I wrote an asynchronous method and wanted to execute it in a synchronous way using `.GetAwaiter().GetResult()`, which caused Godot to freeze (these calls can be in any method coming from Godot like **_Ready**).
Interestingly, Godot will not freeze if the called method itself is synchronous, but inside it calls asynchronous actions, but using `.GetAwaiter().GetResult()`.
An example of both situations can be found in the attached MRP.


### Steps to reproduce

1. Create an asynchronous method.
2. Run it synchronously in **_Ready** (or any other method derived from Godot) using `.GetAwaiter().GetResult()`.


### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/16283827/mvp.zip)
Repository: flutter
Issue: Introducing @State Macro to Stateful Widgets in Flutter
Labels: c: new feature,framework,c: proposal,P2,team-framework,triaged-framework

### Use case

I would like to spark the discussion on a new feature inspired by SwiftUI’s @State property wrapper.  The main motivation of this proposal is to investigate the possibility of using Dart Macros to remove the need to wrap a state property inside a setState callback. I am fully aware that Macros are still under active development, so this might still be a long way to go before it is possible.


### Proposal
Currently, managing an internal state of a Stateful Widget in Flutter requires the use of setState to retrigger the build method and update the UI. It works rather fine as is, but given that Dart Macros are on the horizon I would like to discuss the possibilities where one could write a Stateful Widget as this: 

```dart
class NumberAndButton extends StatefulWidget {
  const NumberAndButton({super.key});

  @override
  State<NumberAndButton> createState() => _NumberAndButtonState();
}

class _NumberAndButtonState extends State<NumberAndButton> {
  // Flagging a state property with a @State Macro
  @State int diceNumber = 1;

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        Text(diceNumber.toString()),
        ElevatedButton(
          onPressed: () {
            // when the state is mutated the build method is notified
            diceNumber = Random().nextInt(6) + 1;
          },
          child: const Text('Random Number'),
        ),
      ],
    );
  }
}
```
Repository: godot
Issue: In code comments, single or double quote inside pair of brackets breaks bracket matching, showing brackets in red when near caret
Labels: bug,topic:gdscript,topic:editor

### Tested versions

- Reproducible in v4.2.1.stable.official [b09f793f5], v4.3.rc2.official [3978628c6]

### System information

Godot v4.2.1.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 860M (nvidia; 535.161.07) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)

### Issue description

If you write: `# (')`, or spanned on multiple lines:

```gd
# ('
# )
```

And you move the caret near the brackets, you'll see that they will appear highlighted in red, showing that they are no matching brackets, instead of underlining their match. This is because a closing quote is expected, as in code. In fact, closing the quote with a second quote of the same type will fix the issue.

However, this commonly happens in English and other languages using quotes:

```gd
# (We're unsure about this line)
```

and the quote themselves do not benefit from quote matching: placing the caret near them does not highlight any matching quote, e.g. in:

```gd
# (print 'hello')
```

so there is not much use is considering quotes as string delimiters in comments. We may just ignore them and focus on matching brackets instead.

This aslo applies to double quotes `"` and square brackets `[]`, as well as export tooltip comments `##`.

### Steps to reproduce

Write comment:

`# (')`

or multiline:

```gd
# ('
# )
```

then move caret near a bracket, on its external side (left or opening bracket, right or closing bracket): instead of underlining matching bracket, only that bracket highlighted in red.

Add a closing quote and see how it fixes the issue.

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: Web workers do not work when runtime is edge
Labels: bug,Webpack,Runtime

### Link to the code that reproduces this issue

https://github.com/jauniusmentimeter/reproduction-app

### To Reproduce

1. Start the application with next dev command
2. Open the page http://localhost:3000
3. The error "document is not defined is returned from the server"
4. Open `app/page.tsx` and change runtime to `nodejs` instead of `edge`. The error is not returned anymore.

### Current vs. Expected behavior

Web workers do not work when runtime is set to edge. They should work in the same way as on nodejs runtime, since they are running on the client.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.11.0
  npm: 9.5.1
  Yarn: 1.22.21
  pnpm: 9.5.0
Relevant Packages:
  next: 15.0.0-canary.72 // Latest available version is detected (15.0.0-canary.72).
  eslint-config-next: N/A
  react: 19.0.0-rc.0
  react-dom: 19.0.0-rc.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Runtime, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

For some reason document is trying to be accessed on server environment when web worker code exist:
<img width="1021" alt="image" src="https://github.com/user-attachments/assets/1f2f4d0d-b642-4308-a6ff-47c05894370f">
here is the place in `.next/server/edge-runtime-webpack.js` that is failing:
<img width="704" alt="image" src="https://github.com/user-attachments/assets/8312efc0-6373-48e6-af86-96d44c7b7921">
Repository: node
Issue: node:readline support reading non printable characters such as group separator
Labels: readline,feature request

### What is the problem this feature will solve?

When using a USB barcode reader on a TTY app that uses node:readline the group separator character `\x1d` is needed for GS1-128 barcodes. GS1-128 barcodes contain multiple elements defined by an Application Identifier (AI) that is a 2-4 digit code followed by value. Either a defined length is expected for the data or it looks for the group separator character for early termination of the value.

### What is the feature you are proposing to solve the problem?

accept some or all non printable characters as inputs to readline

One of the following
1. add a flag to turn on that by default is disable to preserve existing implementations
2. add an option to explicitly define allowable non printable characters, defaults to an empty list
3. both a global flag and a list

### What alternatives have you considered?

I've considered writing my own, seems like a bad idea for support and security. I may look into putting in a PR but I'm starting with a feature request.
I've considered rewriting the application into a non NodeJS application.
I've considered just replacing the TTY app with something more "modern" but there are external layers affecting this decision. This wouldn't allow copy/pasta of other characters which could be useful in some edge cases.
Repository: kubernetes
Issue: integration tests are painfully slow
Labels: kind/bug,sig/scheduling,sig/api-machinery,sig/auth,sig/apps,triage/accepted

This job is often taking well over an hour even with 8 cores and 20Gi assigned in prow. It used to be more like 30m or less.

(because these tests cases are mostly kubectl and apiserver)

A handful of specific tests seem to be large outliers

the CEL tests alone take 11+ minutes
> k8s.io/kubernetes/test/integration/apiserver: cel | 11m13s

/sig api-machinery

cc @jpbetz @cici37 

and OIDC
> k8s.io/kubernetes/test/integration/apiserver: oidc | 11m16s

/sig auth


> k8s.io/kubernetes/test/integration/controlplane: transformation | 14m33s

> k8s.io/kubernetes/test/integration: examples | 7m47s


api machinery again?


> k8s.io/kubernetes/test/integration: job | 14m16s

/sig apps

> k8s.io/kubernetes/test/integration: scheduler_perf | 9m34s

/sig scheduling

Most of the SIG CLI tests take a few seconds

NOTE: I only skimmed a few of the excessive results here, you can see all of the timings if you expand the "174/174 tests passed!" field

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/126191/pull-kubernetes-integration/1813929954224640000






can we do something about this folks?

/kind bug
Repository: PowerToys
Issue: [PowerRename] Replace syntax help window: Text cut off
Labels: Issue-Bug,Product-PowerRename,Status-In progress,Area-User Interface

### Microsoft PowerToys version

0.82.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

PowerRename

### Steps to reproduce

![image](https://github.com/user-attachments/assets/8bcda6c0-87e7-4bbe-8666-88081607e4e2)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: PowerToys
Issue: [PowerRename] Replace syntax help window is bigger than the PowerRename window
Labels: Issue-Bug,Product-PowerRename,Area-User Interface,Needs-Triage

### Microsoft PowerToys version

0.82.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

PowerRename

### Steps to reproduce

![image](https://github.com/user-attachments/assets/75279c56-7db9-4d9b-b093-663e4ca4cb5c)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: TypeScript
Issue: [proposal] Non widened string values should be valid enum values, like widened string values
Labels: Suggestion,Fix Available

### 🔍 Search Terms

enum, string

### ✅ Viability Checklist

- [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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

TypeScript accepts **widened** strings as **enum** values, but refuses to accept **non widened** strings as enum values. I propose to relax this constraint allowing _widened_ and _non widened_ strings as valid enum values.

### 📃 Motivating Example

At the moment TypeScript accepts **widened strings** as valid **enum values**. 

```ts
// FILE:./case1.ts
export const Case1_ImagePngType = 'image/png'

// Emitted in FILE:./case1.d.ts as
export declare const Case1_ImagePngType = "image/png"

// FILE:./test1.ts
import {Case1_ImagePngType} from './case1.js'

enum Case1 {
  // WORKS FINE
  Png = Case1_ImagePngType,
}
```

Trying to use a **non widened string** results in a **compiler error**.

```ts
// FILE:./case2.ts
export const Case2_ImageJpegType = 'image/jpeg' as const

// Emitted in FILE:./case2.d.ts as
export declare const Case2_ImageJpegType: "image/jpeg"

// FILE:./test2.ts
import {Case2_ImageJpegType} from './case2.js'

enum Case2 {
  // FAILS WITH: Type 'string' is not assignable to type 'number' as required for computed enum member values.
  Jpeg = Case2_ImageJpegType,
}
```


### 💻 Use Cases

Given a consumer project `P1` using exported _widened strings_ values from a consumed library `L1`, if `L1` annotates the exported strings values `as const`, `L1` breaks `P1`.

Given that a _widened string_ value is a valid enum value, a "stricter" _non widened string_ (a subset of the _widened_ one) should be a valid enum value too.

```ts
// FILE:./lib-1.ts
export const ImagePngType = 'image/png'

// FILE:./lib-2.ts
export const ImageJpegType = 'image/jpeg' as const

// FILE:./project.ts
enum MyEnum {
  Png = ImagePngType, // FINE.
  Jpeg = ImageJpegType, // SHOULD BE FINE, BUT ERROR AT THE MOMENT.
}
```