sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [List] ListItemText does not align according to the dir="ltr" value
Labels: component: list

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:
https://codesandbox.io/s/list-listitemtext-does-not-align-according-to-the-dir-ltr-value-22tqtl

### Current behavior 😯

Even though the app is configured with dir="ltr", the ListItemText element still aligns to the right (unlike other elements)

### Expected behavior 🤔

When app is configured with dir="ltr" the ListItemText component will be aligned to the left (similar to other components)

### Context 🔦

The error occurs whether the browser language is set to Hebrew (rtl) or English

### Your environment 🌎

I use the Chrome browser

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.22621
  Binaries:
    Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.3.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 116.0.5845.180
    Edge: Spartan (44.22621.2134.0), Chromium (116.0.1938.76)
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.14
    @mui/core-downloads-tracker:  5.14.8
    @mui/icons-material: ^5.14.1 => 5.14.1
    @mui/lab: ^5.0.0-alpha.138 => 5.0.0-alpha.143
    @mui/material: ^5.14.8 => 5.14.8
    @mui/private-theming:  5.14.8
    @mui/styled-engine:  5.14.8
    @mui/system:  5.14.8
    @mui/types:  7.2.4
    @mui/utils:  5.14.8
    @mui/x-data-grid: ^6.11.2 => 6.11.2
    @mui/x-date-pickers: ^6.10.1 => 6.10.1
    @mui/x-tree-view:  6.0.0-alpha.0
    @types/react: 18.2.14 => 18.2.14
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.1.6 => 5.1.6
```
</details>
Repository: rust
Issue: Unspecific error on Fn trait bounds
Labels: A-diagnostics,T-compiler

### Code

```Rust
pub trait MyFn: Fn() -> () {}

fn do_f(f: &dyn MyFn) {}

fn main() {
    let f = || {};
    do_f(&f);
}
```


### Current output

```Shell
Jamess-MacBook-Pro:benchground jlogan$ cargo build
   Compiling benchground v0.1.0 (/Users/jlogan/git/benchground/benchground)
error[E0277]: the trait bound `[closure@src/fn_bound_repro.rs:6:13: 6:15]: MyFn` is not satisfied
 --> src/fn_bound_repro.rs:7:10
  |
7 |     do_f(&f);
  |          ^^ the trait `MyFn` is not implemented for closure `[closure@src/fn_bound_repro.rs:6:13: 6:15]`
  |
  = note: required for the cast from `&[closure@src/fn_bound_repro.rs:6:13: 6:15]` to `&dyn MyFn<Output = ()>`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `benchground` (lib) due to previous error
Jamess-MacBook-Pro:benchground jlogan$
```


### Desired output

```Shell
Some explanation of what part doesn't match or how a person might implement their intent would be helpful
```


### Rationale and extra context

_No response_

### Other cases

```Rust
The error emitted is nearly the same regardless of the types of arguments in the trait and in the closure, but when the arguments are references, the error also lists separate lifetimes for each input, which makes it look like lifetimes are the issue - but it seems that they're not, since the issue persists even with no relevant lifetimes involved
```


### Anything else?

_No response_
Repository: godot
Issue: Grid-like artifacts when using feedback loop shaders
Labels: bug,platform:web,platform:ios,topic:rendering,confirmed,topic:shaders

### Godot version

v3.5.stable.official [991bb6ac7]

### System information

iOS 16.3.1, iPhone 14 Pro Max, GLES 3

### Issue description

I'm using a feedback loop to create particle effects. The setup looks like this

- ColorRect (for output, takes ViewportTexture)
- Viewport
- - ColorRect (for feedback, takes the same ViewportTexture)
- - Particles2D

It works on desktop (tested on Mac) but on iOS it creates grid-like artifacts. It's especially strong when using an average value of nearby pixels (top + bottom + left + right) * 0.25

The grid has 32px dimension on Y axis and 32 or 64 on X axis, it doesn't depend on kernel used in shader

[Link to video](https://youtube.com/shorts/0zojTTDo9WQ)

on Web export the concept doesn't seem to work at all, it behaves like never clearing viewport and shows this error in the console

WebGL-0x108009bf800] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture.

### Steps to reproduce

1. Download test project
2. Open in Godot 
3. Export as iOS project
4. Use controls to enable\disable effects (blur especially)

### Minimal reproduction project

[ios_bug_for_github.zip](https://github.com/godotengine/godot/files/12570933/ios_bug_for_github.zip)
Repository: next.js
Issue: [Pages Router] - Middleware breaks URL masking
Labels: bug,Navigation,Runtime

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/github/ValenCassa/bug-next/main?file=/middleware.ts:1,1
### To Reproduce

1. Start the application in development
2. Click on the link
3. Remove the middleware file
4. Try again

### Current vs. Expected behavior

**Current behavior**:
When using middleware, the link redirects you to whatever the `as` prop  has been set to instead of browsing to the `href` and masking the URL. 
**Expected behavior**:
The link should should browse to the `href` and mask the URL based on the `as` prop. 

### 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 22.5.0: Mon Apr 24 20:40:17 PDT 2023; root:xnu-8796.121.2~3/RELEASE_ARM64_T8112
    Binaries:
      Node: 20.5.0
      npm: 9.8.0
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.23
      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)

Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Additional context

I spent several hours trying to debug what was causing the issue and was going crazy. It seems the `nextUrl` from the request object is returning the pathname as `/test/1?id=1`, so it's actually appending both whatever you're using for the `as` prop and the `href`. I tried setting the pathname manually too with no success.
Repository: godot
Issue: FileAccess 'get_var' method will return a null Variant if the file encoding is UTF-8
Labels: topic:core,documentation

### Godot version

4.1.dev3.official [a67d37f]

### System information

Windows 11 [Vulkan (Forward+)]

### Issue description

**Note:** I'm not sure if this is a bug, or if the behavior is intentional.

Calling `FileAccess.get_var()` on a file with UTF-8 encoding will return a null Variant type, due to a buffer length mismatch.

https://github.com/godotengine/godot/blob/fc99492d3066098e938449b10e02f8e01d07e2d1/core/io/file_access.cpp#L295

Perhaps this is intended, however, I discovered it by accident after I inadvertently entered a non-hex character in the file and saved it, resulting in the file encoding reverting to UTF-8.  Naturally, I fixed the problem character, however, the file encoding remained changed - unbeknownst to me.  This resulted in subsequent calls to `get_var()` to fail (silently) due to the above error - resulting in `null` Variants getting returned.

If this behaviour is expected, it might be good to have it documented somewhere that `FileAccess.get_var()` will not read from UTF-8 or other non-hex file encodings. 

### Steps to reproduce

Simply call `FileAccess.get_var()` after opening a file with UTF-8 encoding.  The file should previously have been saved using `FileAccess.store_var(...)`.

### Minimal reproduction project

Reproduction is straightforward.
Repository: PowerToys
Issue: Request for a utility to automate Windows computer shutdown planning.
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

This utility would allow the user to schedule the shutdown, restart, suspension, logoff, user lock or automated Windows hibernation depending on the fulfillment of one or several conditions, which have to be fulfilled simultaneously or not, depending on how the user needs it.

The implemented features could be the same as the ones available at "AMP WinOFF" program, but in a much more updated and efficient way, made to run the newer and latest versions of Windows with better integration with the operating system, since this program has been out of date for over a decade, and some of its features do not work properly with more modern operating systems.

This utility could somehow be integrated with Awake characteristic already available at PowerToys.

More info and ideas of AMP WinOFF here: https://www.ampsoft.net/utilities/WinOFF.php

Some examples of screenshots of how this program works:

![1](https://github.com/microsoft/PowerToys/assets/41569987/c3e96a88-0849-4538-860b-ebe41790b398)
![2](https://github.com/microsoft/PowerToys/assets/41569987/d9bea68b-9847-45bf-9bb8-e8ad004f11b9)
![3](https://github.com/microsoft/PowerToys/assets/41569987/6f83266e-0391-42ee-9805-42673b0bdd42)

### Scenario when this would be used?

This feature could be used when Windows is running for a long period of time, and, after a while, the user wants it to shut down depending on one or more conditions. This could prevent the computer from constantly running for long periods of time.

Users could use this tool to turn off or lock the computer after putting on music or a movie before bedtime, and thus the computer would not be playing multimedia content constantly after it has been turned off after a while.

### Supporting information

_No response_
Repository: PowerToys
Issue: Feature: Custom context menu options
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

The proposed feature is expected to allow users to add a custom file or command call to the context menu. This means that users can customize their context menu by adding specific files or commands that can be executed directly from the menu. This could include scripts, applications, or any other command that can be run in the system.

### Scenario when this would be used?

The idea is to give users the ability to customize their context menu by adding specific files or commands that can be executed directly from the menu. This could include scripts, applications, or any other command that can be run in the system.

For example, adding or removing a folder in the PATH environment variable. This would simplify the process of modifying the PATH variable and reduce the risk of errors.
Another example, this feature could allow users to add specific commands to the context menu of certain file types. For instance, a user might want to add a “Extract audio” command to the context menu of .mp4 files.



### Supporting information

**Clarification:**

I would like to clarify that the feature I’m proposing is not about implementing specific commands like “adding to PATH” or “Extracting audio”. Rather, it’s about providing the ability to add any desired command or file call to the context menu. The specific commands mentioned are just examples of what users might choose to add, but the actual implementation of those commands is not part of this feature request.

**Current Situation:**

At present, in order to customize the context menu, users have to manually edit the registry or download various utilities from the internet. This is not only inconvenient but also poses a security risk as it exposes users to potential malware or other threats. This feature would provide a safer and more user-friendly alternative for customizing the context menu.
Repository: deno
Issue: `console.` and `window.` not available for tab completion in repl
Labels: bug,repl,deno jupyter

**Tooling affected**: repl, jupyter kernel (xref: https://github.com/denoland/deno/pull/20337)

**Versions affected**: 1.36.0-1.36.4, also on `main`

**Last known working version**: 1.35.x

From https://github.com/bartlomieju/deno/pull/3#issuecomment-1712968620:

Within the repl, `console.` does not tab complete. Other globals, such as `Deno` are tab-complete-able. If you create a _new_ global then that variable is available to tab complete:

```typescript
var con = console
```

`con`-tab:

![image](https://github.com/denoland/deno/assets/836375/c94299e6-9ff3-40dc-8624-7941f0c523e6)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Add Image Creation Elapsed Time to PNG Headers and Filename options
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 ?

Problem Solved:
-Easily see Time Taken to create an older image.  (Time Taken in Live Preview only shows current image)
-This is helpful for benchmarking:
---Time per sampling steps
---Time per upscale settings
---Time per sampler used
---Time per prompt/keywords
-Currently you can add date/time generated to the filename or see in Windows, but then you have to calculate time passed in your head by comparing it to nearby files. And that's only if they are all in the same directory and you haven't moved/sorted them.

How the feature would work:
1) Take the "Time Taken: 1min 30 seconds" value that already exists at the bottom of the Live Preview screen.
2) Add the Time Taken value to the end of the PNG headers that get saved to the final image file. 
---So you can see in PNG editor or reloading in PNG Info in Automatic1111
---This could be the exact text since it's a text header
3) Add the Time Taken to the filename options here https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Custom-Images-Filename-Name-and-Subdirectory
---Since it's a filename you could print it as "(filename)_N_min_N_secs" in the filename export
---the file option could be called [time_taken], [processing_time], [elapsed_time] or something like that.

I feel like this might be pretty easy to do and would be extremely useful to everybody, but computers are hard, so who knows.

Thanks

### Proposed workflow

See above

### Additional information

_No response_
Repository: flutter
Issue: [Impeller] Could not decompress image on intel macOS
Labels: engine,platform-mac,a: images,P2,e: impeller,team-engine,triaged-engine

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

Display an image from local or network.

### Expected results

Just display.

### Actual results

<img width="1204" alt="image" src="https://github.com/flutter/flutter/assets/11473691/12ce2f50-c123-4544-ba5b-7f93ad308fae">


### Code sample

<details><summary>Code sample</summary>

```dart

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: Scaffold(
        body: Center(
          child: Image.network('https://i.imgur.com/CzXTtJV.jpg'),
        ),
      ),
    );
  }
}


```

</details>


### Screenshots or Video

_No response_

### Logs

<details><summary>Logs</summary>

```console

══╡ EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE ╞════════════════════════════════════════════════════
The following _Exception was thrown resolving an image frame:
Exception: Could not decompress image.

When the exception was thrown, this was the stack

Image provider: NetworkImage("https://i.imgur.com/CzXTtJV.jpg", scale: 1.0)
Image key: NetworkImage("https://i.imgur.com/CzXTtJV.jpg", scale: 1.0)
════════════════════════════════════════════════════════════════════════════════════════════════════

```

</details>


### Flutter Doctor output

<details><summary>Doctor output</summary>

```console

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 3.14.0-14.0.pre.210, on macOS 13.5.2
    22G91 darwin-x64, locale zh-Hans-HK)
[!] Android toolchain - develop for Android devices (Android SDK
    version 33.0.2)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more
      details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK
      licenses.
      See
      https://flutter.dev/docs/get-started/install/macos#android-setup
      for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[!] Android Studio (version unknown)
    ✗ Unable to determine Android Studio version.
[✓] IntelliJ IDEA Community Edition (version 2023.2.1)
[✓] VS Code (version 1.82.0)
[✓] VS Code (version 1.82.0-insider)
[✓] Connected device (2 available)
[✓] Network resources

```

</details>
Repository: storybook
Issue: [Bug]: Addon with type Tab works only on MDX page
Labels: bug,ui,sev:S3

### Describe the bug

Addon with type **tab** does not work on js strories, but works on MDX.
I try to use code from documentation
```
import React from 'react';

import { addons, types } from '@storybook/manager-api';

addons.register('my/tab', () => {
  addons.add('my-panel-addon/tab', {
    type: types.TAB,
    title: 'Example Storybook tab',
    //👇 Checks the current route for the story
    route: ({ storyId, refId }) => (refId ? `/mytab/${refId}_${storyId}` : `/mytab/${storyId}`),
    //👇 Shows the Tab UI element in mytab view mode
    match: ({ viewMode }) => viewMode === 'mytab',
    render: () => (
      <div>
        <h2>I'm a tabbed addon in Storybook</h2>
      </div>
    ),
  });
});
```

If you change type to panel - it will work correctly)). I am trying on fresh install Stroybook (react type) with webpack5

https://github.com/storybookjs/storybook/assets/57175740/24a932b2-e161-494b-b475-befd76ab5b58

`package.json`
```
{
  "name": "2new-st",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "storybook dev -p 6006",
    "build-storybook": "storybook build"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@babel/preset-env": "^7.22.15",
    "@storybook/addon-essentials": "^7.4.0",
    "@storybook/addon-interactions": "^7.4.0",
    "@storybook/addon-links": "^7.4.0",
    "@storybook/blocks": "^7.4.0",
    "@storybook/html": "^7.4.0",
    "@storybook/html-webpack5": "^7.4.0",
    "@storybook/testing-library": "^0.2.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "storybook": "^7.4.0"
  }
}
```

`main.js`
```
/** @type { import('@storybook/html-webpack5').StorybookConfig } */
const config = {
  stories: [
    "../stories/**/*.mdx",
    "../stories/**/*.stories.@(js|jsx|mjs|ts|tsx)",
  ],
  addons: [
    "@storybook/addon-links",
    "@storybook/addon-essentials",
    "@storybook/addon-interactions",
    "../addons/events/manager.js",
  ],
  framework: {
    name: "@storybook/html-webpack5",
    options: {},
  },
  docs: {
    autodocs: "tag",
  },
};
export default config;
```

PS.
On strorybook 6.5 addons work perfect (my own and from docs)
### To Reproduce

1. Init npm project `npm init`
2. Install stroybook `npx storybook@latest init` (type react or web components, build system - webpack5)
3. Add addon (for example `addons/events/manager.js`)
4. Connect addon in `.storybook/main.js` - `../addons/events/manager.js`
5. Try to open tab addon

### System

_No response_

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: While navigating to “Controls, Actions, Interactions, Accessibility, Performance” tab items narrator announce twice announcement for tab items.
Labels: bug,good first issue,help wanted,ui,accessibility,sev:S4

### Describe the bug

While navigating to “Controls, Actions, Interactions, Accessibility, Performance” tab items narrator announce twice announcement for tab items.

Actual Result:
While navigating to “Controls, Actions, Interactions, Accessibility, Performance” tab items narrator announce twice announcement for tab items.

Expected Result:
While navigating to “Controls, Actions, Interactions, Accessibility, Performance” tab items narrator should announce only once.


### To Reproduce

1. Open URL: [Common Navigation - Scrolling Panel ⋅ Storybook (windows.net)](https://vivacommonstorybooktest.blob.core.windows.net/$web/index.html?path=/story/common-navigation--scrolling-panel&globals=backgrounds.grid:!false;backgrounds.value:transparent)
2. Navigate to “App bar” button at right side of the pane invoke it and navigate to “Default” link invoke it. 
3. Now navigate to “Controls, Actions, Interactions, Accessibility, Performance” tab items and observe the narrator announcement           


Attachments:

https://github.com/storybookjs/storybook/assets/93735775/930a7a65-3586-4439-848e-99ed81204bf5

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     

### System

```bash
OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)
```


### Additional context

_No response_