sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [LoadingButton] Loading component should be inline when positioned left or right
Labels: package: lab,component: LoadingButton

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Currently, the loading spinner/component is position:absolute for all positions. If I have a button stretching the full length of its container, as opposed to exactly fitting its content, this means with position "start" or "end" the spinner appears at the very beginning or end of the button, with the text label in the middle, which doesn't look good.

It would be far neater (and consistent) if for these two positions, the spinner was simply inlined in the same way as the button's startIcon / endIcon.

Note that the button icon is currently faded out when transitioning to loading state, so this may need a rethink, unless the loading spinner is faded in to match.

### Examples 🌈

How it looks when not loading:
![image](https://github.com/mui/material-ui/assets/15246391/4be430ad-4799-49f4-896c-bf07c11e06ba)

How it looks when loading:
![image](https://github.com/mui/material-ui/assets/15246391/4ddb1694-bb05-4d3c-a017-d79ca29c66e1)

How I want it to look:
![image](https://github.com/mui/material-ui/assets/15246391/b2b88d17-ecee-4e48-b85d-2f410bb1cf5f)

https://m3.material.io/components/buttons/guidelines#9ecffdb3-ef29-47e7-8d5d-f78b404fcafe
https://m3.material.io/components/buttons/guidelines#89ba49e3-31b5-47ae-9665-3e7f33452d0f

### Motivation 🔦

We could remove a fair bit of boilerplate code by using LoadingButton instead of Button. But currently, we cannot use LoadingButton because of this issue, and centrally positioning the loading component is not an option for us because the button text then disappears.
Repository: PowerToys
Issue: Windows Snap won't work properly after enabled "Restore the original size of windows when unsnapping" 
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.71.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

1.use fancy zone to resize a window
2.drag that window to the edge of screen to trigger windows snap
3.the window won't be snapped to a half screen size but the original size



https://github.com/microsoft/PowerToys/assets/44182970/7449609d-46e2-4106-9b0d-0efd9bc76df7



### ✔️ Expected Behavior

window that resized by fancy zone should be snapped to half screen size

### ❌ Actual Behavior

window restored to the original size and triggered windows snap

### Other Software

Windows 11 Build 22621.1992
Repository: go
Issue: net/http: reuse gzip reader from pool for transport
Labels: Performance,help wanted,NeedsInvestigation

https://github.com/golang/go/blob/089e37a931d30d4055c7468facb602c4cfa9b537/src/net/http/transport.go#L2858
Is it possible to reuse this gzip reader from a `sync.Pool` to reduce the memory allocation cause by `flate.NewReader`
Repository: ant-design
Issue: issue occurs in only windows chrome browser  => if there is scroll in menu then space coming in between menu and submenu when using popupOffset to render submenu in left
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antdmenu-with-custom-submenu-forked-pw4xrd?file=/src/App.tsx:754-759)

### Steps to reproduce

just hover over menu items

### What is expected?

no space between submenu and menu should be there is we have max-height with scroll

### What is actually happening?

submenu will open in left side, there will be space between menu and submenu, if you remove height and scroll then there is no space coming

| Environment | Info |
| --- | --- |
| antd | 4.18.4 |
| React | 17 |
| System | windows |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: storybook
Issue: [Documentation]: Story book for vue 3 - How can change control type globally for auto generated slot args?
Labels: documentation

### Describe the problem

I have auto generated slot args, without overwrite in target story I always get `control: object` for my slots, but I want to get `control: text`. Is it possible?   
e.g.  
I have this:  
![image](https://github.com/storybookjs/storybook/assets/32958181/766bf927-78cf-4ec7-a688-dd2703bd6a3f)  
I want to get this (without overwrite on every story) for all slots:  
![image](https://github.com/storybookjs/storybook/assets/32958181/03ac5d74-9695-4023-800e-a39bcfb6a78e)  



### Additional context

_No response_
Repository: node
Issue: test-net-autoselectfamily.js failed
Labels: test

### Version

v20.4.0

### Platform

Darwin MacBook-Pro.local 21.6.0 Darwin Kernel Version 21.6.0: Thu Jun  8 23:57:12 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_X86_64 x86_64

### Subsystem

net

### What steps will reproduce the bug?

Download the latest node from the offical site. https://nodejs.org/dist/v20.4.0/node-v20.4.0-darwin-x64.tar.gz

```sh
roger@MacBook-Pro node-contribute % ~/Downloads/node-v20.4.0-darwin-x64/bin/node ~/Work/node-contribute/test/parallel/test-net-autoselectfamily.js
```

The test-net-autoselectfamily.js I run is from the latest node source.
```sh
roger@MacBook-Pro node-contribute % git log
commit f9737b1b8c96e43cedfff764634524df62cf3109 (HEAD -> origin/main, origin/HEAD)
Author: Node.js GitHub Bot <github-bot@iojs.org>
Date:   Fri Jul 14 10:37:47 2023 +0100
```


### How often does it reproduce? Is there a required condition?

Consistently reproducable

### What is the expected behavior? Why is that the expected behavior?

no complaint, of course

### What do you see instead?

node:assert:125
  throw new AssertionError(obj);
  ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

  [
    '2606:4700::6810:85e5:56228',
    '104.20.22.46:56228',
-   '2606:4700::6810:84e5:56228',
-   '104.20.23.46:56228',
-   '::1:56228',
-   '127.0.0.1:56228'
  ]
    at Socket.<anonymous> (/Users/roger/Work/node-contribute/test/parallel/test-net-autoselectfamily.js:145:18)
    at Socket.<anonymous> (/Users/roger/Work/node-contribute/test/common/index.js:466:15)
    at Socket.emit (node:events:512:28)
    at afterConnect (node:net:1578:10)
    at afterConnectMultiple (node:net:1675:3) {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: [ '2606:4700::6810:85e5:56228', '104.20.22.46:56228' ],
  expected: [
    '2606:4700::6810:85e5:56228',
    '104.20.22.46:56228',
    '2606:4700::6810:84e5:56228',
    '104.20.23.46:56228',
    '::1:56228',
    '127.0.0.1:56228'
  ],
  operator: 'deepStrictEqual'
}

Node.js v20.4.0

### Additional information

_No response_
Repository: PowerToys
Issue: Mouse without Boarders key invalidated by security patching
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.71.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Start with 2 working PC and Mouse without Boarders is working. Apply July monthly security patches on W11 on both systems. After reboot, Mouse without Boarders isn't able to access the "other" PC. Only generating a new key on the primary and installing on the secondary restores functionality.

### ✔️ Expected Behavior

Monthly security and feature patches should not impact the validity of the Mouse without Boarders key.

### ❌ Actual Behavior

After applying monthly security patches and  reboot, Mouse without Boarders isn't able to access the "other" PC. Only generating a new key on the primary and installing on the secondary restores functionality.

### Other Software

_No response_
Repository: rust
Issue: Missed optimization on short known length iterator
Labels: A-LLVM,I-slow,A-iterators

[Compiler Explorer](https://godbolt.org/z/6Pv4bxs1b)

Consider these equivalent ways of checking whether an array of 5 booleans are all true.

```rust
pub fn iter_all(a: [bool; 5]) -> bool {
    a.iter().all(|s| *s)
}

pub fn iter_fold(a: [bool; 5]) -> bool {
    a.iter().fold(true, |acc, a| acc & a)
}

pub fn manual_loop(a: [bool; 5]) -> bool {
    let mut b = true;
    for a in a {
        b &= a;
    }
    b
}

pub fn comparison(a: [bool; 5]) -> bool {
    a == [true; 5]
}

pub fn and(a: [bool; 5]) -> bool {
    a[0] & a[1] & a[2] & a[3] & a[4]
}
```

This is the generated assembly.

```asm
# same for `iter_all`, `iter_fold`, `manual_loop`
example::iter_all:
        movabs  rax, 1099511627775
        and     rax, rdi
        test    dil, dil
        setne   cl
        test    edi, 65280
        setne   dl
        and     dl, cl
        test    edi, 16711680
        setne   cl
        test    edi, -16777216
        setne   sil
        and     sil, cl
        and     sil, dl
        mov     ecx, 4278190080
        or      rcx, 16777215
        cmp     rax, rcx
        seta    al
        and     al, sil
        ret

example::comparison:
        movabs  rax, 1099511627775
        and     rax, rdi
        movabs  rcx, 4311810305
        cmp     rax, rcx
        sete    al
        ret

example::and:
        not     rdi
        movabs  rax, 4311810305
        test    rdi, rax
        sete    al
        ret
```

One thing of note is that usually when functions would result in the same assembly, they get merged together. This hasn't happened here, which might indicate that the compiler did not understand that all of them do the same thing.

The assembly of `and` is the best one. The other versions should compile to it. It is unfortunate that you need to manually unroll the iterator to get the better version.
Repository: rust
Issue: Standardize what the `'a` thingies are called in compiler errors
Labels: A-diagnostics,A-lifetimes,T-compiler,D-inconsistent

There are some error messages that refer to `'a` (colloquially called "lifetimes" but the compiler should be more specific) as a "lifetime annotation", a "lifetime parameter", or a "lifetime specifier".

Are these interchangeable, or is there a nuance I'm not appreciating?

If they are interchangeable, the compiler errors should probably pick one and stick with it.

Quick GitHub searches of the repo show "lifetime parameter" seems most common:

- [Lifetime parameter](https://github.com/search?q=repo%3Arust-lang%2Frust+%22lifetime+parameter%22&type=code): 372 results
- [Lifetime specifier](https://github.com/search?q=repo%3Arust-lang%2Frust+%22lifetime+specifier%22&type=code): 88 results
- [Lifetime annotation](https://github.com/search?q=repo%3Arust-lang%2Frust%20%22lifetime%20annotation%22&type=code): 10 results
- [Lifetime name](https://github.com/search?q=repo%3Arust-lang%2Frust%20%22lifetime%20name%22&type=code): 112 results

TRPL is inconsistent too 😅 it uses "lifetime parameter" and "lifetime annotation", but not "lifetime specifier", I don't think.
Repository: PowerToys
Issue: [Feature request] Screen capture Gyazo style
Labels: Needs-Triage

### Description of the new feature / enhancement

I would love to have  a sceen capture with the option to make a rectangle and that the "app" directly generates the image in png (or jpg) and opens it on the browser (for example), which then you can just drag it put to where you want it (telegram, whatssap, desktop...) Instead of the classic "prt-scn" then open paint/ps, Ctrl+V, then save as, put name...

### Scenario when this would be used?

In many daily uses i am capturing parts of the desktop to send for many conversations, corrections...

### Supporting information

There are some few programs that do this for free like Gyazo, but since i love Powertoys i'd love to have it integrated.
Repository: node
Issue: Conditional unhandled 'error' event when http.request with `.lookup`
Labels: confirmed-bug,http,net,good first issue

### Version

20.4.0

### Platform

Docker ArchLinux 6.1.35-1-lts

### Subsystem

_No response_

### What steps will reproduce the bug?

https://github.com/loynoir/reproduce-node-48771

### How often does it reproduce? Is there a required condition?

- ip blackhole like behavior

### What is the expected behavior? Why is that the expected behavior?

Make it possible to catch error, and exit with 0.

### What do you see instead?

Error is not caught, and exit with 1.

### Additional information

_No response_
Repository: TypeScript
Issue: Module resolution using nodenext and a wildcard in package.json exports
Labels: Needs Investigation,Rescheduled

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

Nodenext wildcard, type cannot be named

### 🕗 Version & Regression Information
The bug only appears when using nodenext for module resolution

### ⏯ Playground Link

Cloneable repo: https://github.com/geoffreytools/effect-test-tsc

### 💻 Code

```ts
import { TaggedClass } from '@effect/data/Data';
// import '@effect/data/Equal';

export class Foo extends TaggedClass('Foo')<{}> {}
```

### 🙁 Actual behavior

```
The inferred type of 'Foo' cannot be named without a reference to '../node_modules/@effect/data/Equal'. This is likely not portable. A type annotation is necessary.
```

### 🙂 Expected behavior

To compile correctly, without using nodenext it works fine and the same issue doesn't apply to other transitive imports such as Hash that are identically exported. All goes away the very moment there is either an explicit import of `Equal` or when adding to the library package.json the following:

```ts
{
  "exports": {
    "./Equal": {
      "import": {
        "types": "./Equal.d.ts",
        "default": "./mjs/Equal.mjs"
      }
    }
  }
}
```

Note that the library uses a wildcard `./*` as each import map to a file and this is perfectly resolvable by node
Repository: flutter
Issue: shared_preferences does not store preferences inside XDG_CONFIG_HOME
Labels: platform-linux,p: shared_preferences,package,a: desktop,P2,team-linux,triaged-linux

### 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)

### Steps to reproduce

1. Make a project utilizing shared_preferences
2. Run it while setting a preference

### Expected results

The file to be saved under `~/`**`.config`**`/com.example/shared_preferences.json`.

### Actual results

`shared_preferences` has saved the preferences as `~/`**`.local/share`**`/com.example/shared_preferences.json`

The [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) states:

> $XDG_DATA_HOME defines the base directory relative to which user-specific data files should be stored. If $XDG_DATA_HOME is either not set or empty, a default equal to $HOME/.local/share should be used.

While "shared preferences" are a kind of user-specific data files, the line below specifies:

> $XDG_CONFIG_HOME defines the base directory relative to which user-specific configuration files should be stored. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used. 

My use case utilizes shared_preferences primarily for configuration, and a look inside `.config` reveals a bunch of applications using this directory, one which of is Chromium.

The ultimate problem arises from `path_provider` not supporting a configuration path property<sup><a href="https://github.com/flutter/packages/blob/main/packages/path_provider/path_provider_linux/lib/src/path_provider_linux.dart">[source]</a></sup>.

A mitigation or workaround does not seem to be possible since the classes of implementations of `shared_preferences` seem very well protected.

### Code sample

```dart
import 'dart:io';

import 'package:flutter/widgets.dart';
import 'package:shared_preferences/shared_preferences.dart';

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  final preferences = await SharedPreferences.getInstance();
  preferences.setString('hello', 'world');
  exit(0);
}
```

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

N/A
Repository: pytorch
Issue: Significant time difference of calculating Jacobian matrix using jacrev and oracle functions
Labels: module: autograd,triaged,module: functorch

### 🚀 The feature, motivation and pitch

Sorry I'm not sure if this is a new feature, but I'd be very grateful if you guys would like to improve this part.

Specifically, I found that using `jacrev` would be much slower than using the oracle Jacobian function:
```python
from torch.func import vmap, jacrev
import torch
import time

a = torch.rand(10000, 10000)

def f(x):
    return (x ** 2).sum(-1)

def df(x):
    return 2 * x


t0 = time.time()
b = df(a)
t1 = time.time()
c = vmap(jacrev(f))(a)
t2= time.time()

assert torch.allclose(b, c)
print(t1 - t0, t2 - t1)
```
result: 0.10568618774414062 0.9206998348236084

Given that oracle's Jacobian is readily available in neural networks, I wonder why using `jacrev` is so much slower? Is there something wrong with me?

Of course, I can actually rewrite each layer of the neural network to obtain the value and Jacobian at the same time, but calculating the Hessian matrix is too troublesome. It would be great if `jacrev` could be faster!



### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @Chillee @samdow @kshitij12345 @janeyx99
Repository: create-react-app
Issue: Will Create React App be updated in the future?
Labels: needs triage

I noticed that this project has not been updated for almost a year, and the official React documentation no longer mentions using Create React App to create React projects. I'm wondering if Create React App will still receive updates in the future?

If it will no longer receive updates in the future, or enters a so-called "maintenance mode", then I will use other frameworks to develop my React projects.
Repository: PowerToys
Issue: Mouse without borders: Inconsistent pointer speed across devices
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.71.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

* Use the mouse attached to a PC with a single display, 1920/1200px, 100%
* Connect to a laptop with a builtin display, 2560/1600px, 150% and an external display, 1920/1200px, 100%, set up as extended desktop (not mirroring), horizontal alignment
* Move the mouse pointer on the PC as you would always do
* Move the mouse pointer over to the laptop and its two displays (internal and external)

### ✔️ Expected Behavior

The mouse pointer moves at the same speed and acceleration everywhere.

### ❌ Actual Behavior

The speed and acceleration on the PC is as always.

* Without the setting "Move relatively": The speed on both laptop displays is *too quick only horizontally* (vertical speed is normal, acceleration is good)
* With the setting "Move relatively": The speed on both laptop displays is a bit slow and the acceleration on both laptop displays is *extreme*. The mouse pointer would jump across the display at moderate mouse movement speed.

It's hard to work on the remote machine (laptop) with either setting from the host (PC).

### Other Software

_No response_
Repository: godot
Issue: Visibility range mixes origin and AABB
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.1.stable.official [970459615]

### System information

Godot v4.1.stable - Pop!_OS 22.04 LTS - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) () - AMD Ryzen 5 5600G with Radeon Graphics (12 Threads)

### Issue description

When using a multimeshinstance3d with visibility range it seems that the visibility and fading are calculated differently. Visibility is calculated from the camera's distance to the origin, while fading is calculated based on the distance from the AABB. I assume this because the fading depends on the viewing direction.

I assume it happens too when the mesh in a meshinstance is not centered at the origin, but I have not tested this yet.



### Steps to reproduce

Create a MeshInstance3D
Add a plane to it
Offset the MeshInstance3D eg +1m in the x direction 
Create a MeshInstance3D as target mesh.
Add arbitrary mesh, eg small capsule
Create a MultiMeshInstance3D
Populate it with the small capsule on the plane surface.
Set 10m as visibility_range_end
set 5m as visibility_range_end_margin
set self fade mode

Observe as you pan around the center the mmi sometimes fades nicely and sometimes pops out of existence.

https://github.com/godotengine/godot/assets/36245389/51859cb4-e2ef-45de-b1c3-18767365ac5b



### Minimal reproduction project

[mmiproblem.zip](https://github.com/godotengine/godot/files/12052308/mmiproblem.zip)
Repository: create-react-app
Issue: create-react-app connection error ???
Labels: needs triage
Repository: flutter
Issue: Benchmark regressions on Material 3 change
Labels: c: performance,perf: speed,P2,team-design,triaged-design

https://github.com/flutter/flutter/pull/129724 Resulted in regressions in a number of benchmarks. So far just collecting the links from SkiaPerf. Haven't analyzed any of these yet. cc @HansMuller 

https://flutter-flutter-perf.skia.org/e/?begin=1689270076&end=1689287463&keys=X84a0007b39fb2fa1be1fc8a84f115bd1&num_commits=50&request_type=1&xbaroffset=35722

https://flutter-flutter-perf.skia.org/e/?begin=1689270405&end=1689288118&keys=X314f5d9b52383aeefee0e2606c5219f5&num_commits=50&request_type=1&xbaroffset=35723

https://flutter-flutter-perf.skia.org/e/?begin=1689270405&end=1689288118&keys=Xb03dce35138f5bbcdacbfd6f357798e2&num_commits=50&request_type=1&xbaroffset=35723

https://flutter-flutter-perf.skia.org/e/?begin=1689270624&end=1689288832&keys=X6ce9d4f274857c24ba40556b08093ab7&num_commits=50&request_type=1&xbaroffset=35724

https://flutter-flutter-perf.skia.org/e/?begin=1689270624&end=1689288832&keys=Xd49f2344577562b7a6b46f3c9d1cbcf0&num_commits=50&request_type=1&xbaroffset=35724
Repository: next.js
Issue: Next 13.4.3 breaks custom server in express
Labels: bug

### 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 21.6.0: Thu Jun  8 23:57:38 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_ARM64_T8110
    Binaries:
      Node: 18.6.0
      npm: 9.6.2
      Yarn: 1.22.19
      pnpm: 8.6.5
    Relevant packages:
      next: 13.4.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/jeremyruppel/next-custom-server

### To Reproduce

1. install next@13.4.2
2. `npm start`
3. `sh test.sh`, see the request 200s
5. install next@13.4.3
3. `sh test.sh`, see the request 404s

### Describe the Bug

When using the custom server in dev mode inside an express app, next's static assets will 404 starting in 13.4.3

### Expected Behavior

Static assets are served in dev mode

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

_No response_

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

_No response_