sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [material-next][Switch] Add `Switch` component
Labels: on hold,component: switch,design: material you

This issue is to track the work for adding the `Switch` component to @mui/material-next, moving forward the Material You effort (https://github.com/mui/material-ui/issues/29345)

Material You Swicth specification: https://m3.material.io/components/switch/overview

Migration Guide steps

- [x] Copy component files from material (v5) to material-next: https://github.com/mui/material-ui/pull/39887 
- [x] ~Remove deprecated components and componentsProps props:~ Skipped, no props to remove
- [ ]  Drop support for ThemeProvider in favor of CssVarsProvider: https://github.com/mui/material-ui/pull/40442
- [x]  Migrate component to Typescript: https://github.com/mui/material-ui/pull/39894
- [ ]  Refactor component to use Base UI hooks: `useSwitch` & `useSlotProps`: https://github.com/mui/material-ui/pull/40442
- [ ]  Implement Material You design specs: https://github.com/mui/material-ui/pull/40442
- [ ]  Add component playground to v5 docs: https://github.com/mui/material-ui/pull/40442

Note: This comment will be updated to show the progress and list possible issues.

@DiegoAndai
Repository: go
Issue: cmd/compile: panic due to undocumented `gotypesalias` GODEBUG in types2
Labels: NeedsInvestigation

```
#!watchflakes
post <- log ~ `Value of name not listed in godebugs.All: gotypesalias`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/99d94711b63f3f866740804be450809211f01797)):

    <unknown line number>: internal compiler error: panic: godebug: Value of name not listed in godebugs.All: gotypesalias
    
    goroutine 1 [running]:
    runtime/debug.Stack()
    	/tmp/workdir-host-freebsd-riscv64-unmatched/go/src/runtime/debug/stack.go:24 +0x6c
    bootstrap/cmd/compile/internal/base.FatalfAt({0x1ea74?, 0x0?}, {0x72baa9, 0x9}, {0x881d0db8, 0x1, 0x1})
    	/tmp/workdir-host-freebsd-riscv64-unmatched/go/src/cmd/compile/internal/base/print.go:225 +0x23c
    bootstrap/cmd/compile/internal/base.Fatalf(...)
    	/tmp/workdir-host-freebsd-riscv64-unmatched/go/src/cmd/compile/internal/base/print.go:194
    bootstrap/cmd/compile/internal/gc.handlePanic()
    ...
    <unknown line number>: internal compiler error: panic: godebug: Value of name not listed in godebugs.All: gotypesalias
    
    goroutine 1 [running]:
    runtime/debug.Stack()
    	/tmp/workdir-host-freebsd-riscv64-unmatched/go/src/runtime/debug/stack.go:24 +0x6c
    bootstrap/cmd/compile/internal/base.FatalfAt({0x1ea74?, 0x0?}, {0x72baa9, 0x9}, {0x882f6db8, 0x1, 0x1})
    	/tmp/workdir-host-freebsd-riscv64-unmatched/go/src/cmd/compile/internal/base/print.go:225 +0x23c
    bootstrap/cmd/compile/internal/base.Fatalf(...)
    	/tmp/workdir-host-freebsd-riscv64-unmatched/go/src/cmd/compile/internal/base/print.go:194
    bootstrap/cmd/compile/internal/gc.handlePanic()
    ...
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory
    go tool dist: open /tmp/workdir-host-freebsd-riscv64-unmatched/go/pkg/freebsd_riscv64: no such file or directory


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Cleaner Upscaler Console Output
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

When running the upscaler in the Extras tab, the console currently prints out the current tile step for every image.

It would be much nicer if instead the console could use `tqdm` or something similar to print out the progress of the current image so that it doesn't spam the console. This would be especially helpful when upscaling using `Batch from directory` since there is currently no way of knowing how many images remain during that process.

I understand that `tqdm` can be a bit weird when it comes to multiprocessing applications so if that doesn't work then something simple like just printing out of the current image and number of remaining images and nothing else would be fine.

Currently the console logs look like the following:

```bash
Tile 1/100
Tile 2/100
...
Tile 100/100
Tile 1/50
Tile 2/50
...
Tile 50/50
```

...and that is just for two images so you can imagine how noisy the console is when running on a large directory.

### Proposed workflow

1. Go to `Extras` tab.
2. Upscale using `Batch from Directory` mode.
3. Console prints something similar to the following:
    
    ```bash
    [upscaler]: Processing image 1/100
    [upscaler]: Processing image 2/100
    ...
    [upscaler]: Processing image 100/100
    [upscaler]: Batch from Directory completed.
    ```

Of course the implementation of the logs is up to you. This is just an example.

### Additional information

I tried to make this change on my end but I struggled to understand how these messages are being printed to the console. I tried searching through the code but ultimately couldn't find any way to modify these logs.
Repository: next.js
Issue: `suppressHydrationWarning` not working as expected for app router
Labels: bug

### Link to the code that reproduces this issue

https://github.com/aronwoost/nextjs-suppress-warning-issue

### To Reproduce

1. `npm install`
2. `npm run dev`
3. Open http://localhost:3000/ in browser


### Current vs. Expected behavior

Actual result: "Hello Server" is displayed  
Expected result: "Hello Client" is displayed


### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 20.6.0: Thu Jul  6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_ARM64_T8101
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: 1.22.5
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

This is the code in question:

```jsx
"use client";

import styles from "./page.module.css";

export default function Home() {
  let helloLabel = "";

  if (typeof window !== "undefined") {
    helloLabel = "Client";
  } else {
    helloLabel = "Server";
  }

  return (
    <main className={styles.main}>
      <h1 suppressHydrationWarning>Hello {helloLabel}</h1>
    </main>
  );
}
```

`suppressHydrationWarning` does suppress the warning, but it does also prevents re-rendering. Without the `suppressHydrationWarning` prop, the text is correctly displayed but (of course) the warning is printed in the devtools console.
Repository: godot
Issue: Autocomplete triggers inside shader comments
Labels: bug,topic:editor,confirmed

### Godot version

v4.2.beta.custom_build [c851a4606]

### System information

N/A

### Issue description

In the shader text editor, typing code elements such as `=` inside commented lines will still trigger the autocomplete widget:

![image](https://github.com/godotengine/godot/assets/30739239/5b58ef99-4bcc-4ca3-bb7b-39d1fe87e44d)

### Steps to reproduce

- Create a text shader.
- Start a commented line (`//`).
- Type a character such as `=`, the autocomplete widget will trigger.

### Minimal reproduction project

N/A, trivially reproducible.
Repository: flutter
Issue: Activate InkSparkle on Canvaskit (Android only)
Labels: c: proposal,e: web_canvaskit,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Since https://github.com/flutter/flutter/pull/99882, `InkSparkle` is the default splash animation for M3 apps, only on Android and when the platform is not web, see:
https://github.com/flutter/flutter/blob/6e9d4ccc250dd56ad967de221258d2b8eeffe8e3/packages/flutter/lib/src/material/theme_data.dart#L418




### Proposal

Because shaders are now supported on the Canvaskit renderer, it would be possible to make `InkSparkle` the default animation for Flutter web when isCanvasKit is true.

Here is a video showing the `InkSparkle` shader running on Chrome (Android emulator) : 
- `ThemeData` implementation was updated to change the default splash factory resolution.
- The application was launched using: `flutter run -d web-server --web-renderer=canvaskit --web-port 8080 --web-hostname 0.0.0.0`.
- `adb reverse tcp:8080 tcp:8080` was runned before accesing the application from the emulator.

https://github.com/flutter/flutter/assets/840911/7f5f4d35-5b79-426c-8fc7-62f2277323a3



<details><summary>Example app used to make the screenshot</summary>

```dart
import 'package:flutter/material.dart';
import 'package:flutter/scheduler.dart';

void main() {
  timeDilation = 10.0;
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: Scaffold(
        body: Padding(
          padding: const EdgeInsets.all(8.0),
          child: Material(
            child: InkWell(
              onTap: () {},
              child: Container(
                width: 400,
                height: 100,
                decoration: BoxDecoration(
                  border: Border.all(color: Colors.white),
                ),
              ),
            ),
          ),
        ),
      ),
    );
  }
}

``` 

</details>
Repository: next.js
Issue: ISR or SSR returns null on remote
Labels: examples

### Verify canary release

- [ ] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Nextjs 13.5.4 website deployed on AWS Amplify
```


### Which example does this report relate to?

No example

### What browser are you using? (if relevant)

Chrome

### How are you deploying your application? (if relevant)

AWS Amplify

### Describe the Bug

I tried a page with ISR, which does not work on the remote.

```
export async function getStaticPaths() {
    return {
      paths: [],
      fallback: "blocking"
    };
  };

  export const getStaticProps = async (context: { params: { slug?: string } }) => {
    const eventSlug = context.params?.slug as string;

    const eventProps = await getEventProps(eventSlug)
    const globalData = await fetchGlobalData()

    return {
      props: {
        ...eventProps,
        ...globalData,
      }
    }
  }
```

If I try it locally it works great. But when I try it on the published site, the data it retrieves from `_next/data/.../example.json` brings null and then I end up fetching the API with CSR.

The problem is that it makes the request to the API because the statically generated data is null.

I replaced ISR with SSR, and I have the same problem. The data arrives in null and ends up making a request to the API that it shouldn't.

### Expected Behavior

It should bring data from server side and the data is null.


### To Reproduce

According to the URL and opening the network tab, you will see the API request.
Repository: rust
Issue: `rustc` successfully compiles PIE for target without support for PIE
Labels: A-linkage,A-diagnostics,T-compiler

### Code

With the following target spec:
```json
{
  "arch": "x86_64",
  "data-layout": "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128",
  "linker": "rust-lld",
  "linker-flavor": "ld.lld",
  "llvm-target": "x86_64-unknown-none-elf",
  "panic-strategy": "abort",
  "target-pointer-width": "64"
}
```
(note that `position-independent-executables` is implicitly set to false)

The following command successfully compiles:
```
RUSTFLAGS="-Crelocation-model=pie" cargo b --target x86_64-unknown-custom.json -Zbuild-std=core
```

### Current output

`rustc` successfully compiles, but the output executable is not position-independent:

```Shell
$ file target/x86_64-unknown-custom/debug/pie
target/x86_64-unknown-custom/debug/pie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, with debug_info, not stripped
```

### Desired output

A similar error to when a crate type isn't supported e.g.

```Shell
error: cannot produce position-independent executable for `pie v0.1.0 (/path/to/pie)` as the target `x86_64-unknown-custom` does not support them
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Anything else?

_No response_
Repository: next.js
Issue: Using template literals in JSX className adds extra whitespace when rendered
Labels: bug

### Link to the code that reproduces this issue

https://github.com/ben-aggus-gateway/cssbug.git

### To Reproduce

1. Start the application and view the default page.
2. View source of rendered page

### Current vs. Expected behavior

Current behavior is that line returns or spaces added by prettier (or manually) to a template literal className causes them to be rendered with extra spaces and line returns in HTML.

In my example, I omitted any variables or ternaries, but typically this is why we would need template literals for classnames.

Example:
This JSX:
```
<div
        className={`text-white 
py-6 place-items-center 
grid md:grid-cols-12 
md:gap-7 grid-cols-8 
gap-2 bg-blue-500`}
      >
```
renders this output
```
<div class="text-white
  | py-6 place-items-center
  | grid md:grid-cols-12
  | md:gap-7 grid-cols-8
  | gap-2 bg-blue-500">


```
Expected behavior is that line returns are ignored in template literal output when rendering JSX className attribute (these are often added by prettier)

I would expect this output:
`<div class="text-white py-6 place-items-center grid md:grid-cols-12 md:gap-7 grid-cols-8 gap-2 bg-blue-500">`

I expect this due to previous output w/ Next 13.5.2. 

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Enterprise
Binaries:
  Node: 18.18.2
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.3-canary.9
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Static HTML Export (output: "export")

### Additional context

This issue did not occur in Next 13.5.2 and below. I noticed it after upgrading to 14.0.2
Repository: PowerToys
Issue: FancyZones relative position but left and right only
Labels: FancyZones-Hotkeys,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

The FancyZones Override Windows Snap feature has a "Move windows based on" dropdown where you can select Zone index or Relative position. This feature would exclude the up/down arrows in the Relative option.

### Scenario when this would be used?

Zone index always seemed odd to use, since you're going from an undefined position in the index, then Win+Left would go to 2, and Win+Right would go to 1. Presumably as though the undefined is a 0 and it's looping back around in either direction.

I started using Relative, since it seemed more intuitive, however, I only have my zones split left/right (specific ultrawide layouts as I imagine are quite common). I'm also a hotkey fiend, so at some point I needed to maximize a window. This is typically Win+Up, but the relative Option hijacks Win+Up and Win+Down (normally minimize) for its functionality.

I just want to be able to use the relative option, but only for left/right, so I can still minimize and maximize application with my hotkeys.

### Supporting information

In the meantime, I wanted to use the FancyZone editor, but it doesn't seem I can define with zone is which number. If I could set the left Zone to 2, and the right to 1, then use the "Zone index" option, then it would also more or less address my use cases. I think a third option for Relative position with only left/right is the best solution, however:
![image](https://github.com/microsoft/PowerToys/assets/68610227/d6a7d625-bb8b-44d8-b556-6ffa56f56fa8)
Repository: flutter
Issue: DeviceLab test runner should not try to upload performance metrics if the test failed
Labels: a: tests,team-infra,P2,triaged-infra

Errors uploading the metrics file adds noise complicating the find the root cause of the test failure:

```[2023-11-15 05:37:03.308678] [STDERR] Task failed: PathNotFoundException: Cannot open file, path = '/opt/s/w/ir/x/w/recipe_cleanup/flutter_logs_dir/platform_views_scroll_perf.timeline_summary.json' (OS Error: No such file or directory, errno = 2)
[2023-11-15 05:37:03.308756] [STDERR] 
[2023-11-15 05:37:03.308763] [STDERR] Stack trace:
[2023-11-15 05:37:03.322433] [STDERR] dart:io                                                    _File.readAsStringSync
[2023-11-15 05:37:03.322465] [STDERR] package:flutter_devicelab/tasks/perf_tests.dart 1365:77    PerfTest.internalRun.<fn>```

Example: 
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8764356584207497729/+/u/run_platform_views_scroll_perf_impeller__timeline_summary/test_stderr
Repository: node
Issue: Missing documentation in `fs.StatFs`
Labels: doc,fs,good first issue

### Affected URL(s)

https://nodejs.org/api/fs.html#class-fsstatfs

### Description of the problem

* `statfs.bsize` fails to mention if the size is reported in bits or bytes
* While `statfs.bavail` and `statfs.bfree` can be used to calculate available and free space, it would be appropriate to put an example on how to use them
  Example:
  ```ts
  import { statfs } from "fs/promises"
  const statsfs = await statfs("/tmp")
  const available_bits_or_bytes_not_documented = statsfs.bsize * statsfs.bavail
  ```
* Similarly, `statfs.blocks` and `statfs.files` would strongly benefit from an example
* What's `statfs.type` and why is it a number?
Repository: flutter
Issue: Recipe KMS module pulls crypto keys from staging project
Labels: team-infra,P2,c: tech-debt,triaged-infra

I would expect this be using the prod project (flutter-infra) which has much more restrictions in place. Another option would be to change the project based on the current builder realm it's being run on (staging -> flutter-infra-staging, prod -> flutter-infra)

https://cs.opensource.google/flutter/recipes/+/master:recipe_modules/kms/api.py;l=32;drc=a85607bb7c1d8f29ba9300e7e2d35526993c5fb9

```py
    self.m.step(
        'cloudkms get key', [
            cloudkms, 'decrypt', '-input', encrypt_file, '-output', secret_path,
            'projects/flutter-infra-staging/locations/global'
            '/keyRings/luci/cryptoKeys/flutter-infra'
        ]
    )
```
Repository: next.js
Issue: ISR not working on application root with i18n when deployed to Vercel
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/theirc/refugee.info-greece

### To Reproduce

1. Go to the current deployment
2. Check on the terminal the request headers

### Current vs. Expected behavior

I set up a revalidation time on getStaticProps for index.tsx expecting the ISR to work every 60 minutes but currently that's not happening and you can see that the request header comes as STALE.
All of the others dynamic routes ISR are working but not for index.tsx
This is happening only on PRODUCTION and not locally.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: macOS
  Arch: arm64
  Version: Sonoma 14.0
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: 1.22.17
  pnpm: N/A
Relevant Packages:
  next: 12.3.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.8.3
Next.js Config:
  output: N/A
```


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

Data fetching (gS(S)P, getInitialProps), Internationalization (i18n)

### Additional context

I tested this both locally and deployed to Vercel. 
Locally works fine but when deployed to Vercel the ISR it's not working at all.
![Screenshot 2023-11-15 at 17 04 19](https://github.com/vercel/next.js/assets/14352552/ff729536-b28d-4397-be67-0793e157461a)
Repository: pytorch
Issue: InternalTorchDynamoError rewrapping loses exception chaining
Labels: module: logging,triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Self explanatory. I'm not sure how to fix it, maybe we should manually re-chain the InternalTorchDynamoError too.

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @wconstab @aakhundov
Repository: flutter
Issue: [cocoon] Throttle swarming presubmit tasks during peak hours of users consuming a large amount of infra quota
Labels: c: new feature,team-infra,P3,triaged-infra

Occasionally, someone will send a large number of cleanup PRs which consumes a large chunk of presubmit capacity. To protect overall SLOs for the community, we should deprioritize this user for the day.

Peak hours would be around 10 AM - 3 PM PST on US workdays.

This could be some metric based on the number of builds being scheduled. For example, we could batch it in groups of 50 targets. These numbers can be tweaked to better match our infra capacity:

0 - 150: No impact
150 - 250: Slight reduction
250+: Lowest priority

Cocoon can leave a comment on the PR as an FYI that the user is being throttled for using too much capacity.