sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: PowerRename: Possiblity for external/calculated $-inserts, not only time?
Labels: Product-PowerRename,Needs-Triage

### Description of the new feature / enhancement

Hi, I'm looking for a way to add external/calculated values during the rename process. Such options could be:
- mp3 tags (title, artist, ...)
- audio/video codecs (hevc, av1, ... / flac, ...)
- hashes (CRC-32, SHA-256, etc.)
- EXIF properties
- File properties

### Scenario when this would be used?

- Music / Video library management (ffmpeg/ffprobe)
- Photo library management (EXIF)
- Any place you would want external/calculated values in your file name

### Supporting information

A straightforward way to implement this and not have the need to bundle libraries like ffmpeg/ffprobe, could be to let users add commands that map to $-inserts like:

- `$videocodec` which is mapped to the command `ffprobe -v error -select_streams v:0 -show_entries stream=codec_name -of default=noprint_wrappers=1:nokey=1 [FILENAME]`
  - Could return string `flac`

- `$md5` which is mapped to the command `Get-FileHash '[FILENAME]' MD5 | Select -ExpandProperty Hash`
  - Could return string `b00d075c8cb231eae86c1c5bae12988b`

#### Mapping table example
| Insert | Command | Example Value|
|--------|--------|--------|
| $videocodec | `Get-FileHash '[FILENAME]' MD5 \| Select -ExpandProperty Hash` | flac |
| $md5 | `ffprobe -v error -select_streams v:0 -show_entries stream=codec_name -of default=noprint_wrappers=1:nokey=1 [FILENAME]` | b00d075c8cb231eae86c1c5bae12988b|

Access to some properties that windows explorer can access for example could even be bundled without a third party library I imagine:
![image](https://github.com/microsoft/PowerToys/assets/13102251/9d692761-f57a-4124-b6a8-e1ba14050fd3)


#### Example

A find/replace statement with the mapping explained above could be:
- Find: `.mp4`
  - `Homemovie.mp4`
- Replace `[$videocodec] [$md5].mp4`
  - `Homemovie [flac] [b703123e7120].mp4`

The user would be expected that the commands are setup to be runnable on the system (PATH-variable etc.)

---

Just to make clear what I'm talking about. I image it being like the current way you can add time information (see image):
![image](https://github.com/microsoft/PowerToys/assets/13102251/2ccc617c-7344-4b32-8706-778b4296182c)
Repository: deno
Issue: Ability to log all runtime granted permissions, e.g. when running with `-A`
Labels: cli,permissions,suggestion

I'm imagining a use-case where I would like to run an untrusted third party script.

It would be nice to be able to run the script first in a sandboxed environment (e.g. in a Docker container with the `-A` flag or a broad `--allow-read` flag) but then being able to see a log of all the specific permissions that were requested/granted during runtime.

This permission requests log list would be **as specific as possible**, e.g. listing _which_ specific `env` vars were requested, _which_ specific subprocess were run, etc., _which_ files on the file system were read to and written from.

This list could then be used as a base point to create an explicit allowlist for permissions, which could then be used in a production context. It wouldn't be perfect, since runtime behavior could change which permissions are requested, but this would be a great starting point to "discover" the program's behavior.

## Example

Note the `--log-permissions` flag:

```
$ deno run -A untrusted.ts --log-permissions=log.json
```

which outputs a file using the [Permission Descriptor types](https://deno.land/api@v1.36.2?s=Deno.PermissionDescriptor):

```
$ cat log.json
[
  { name: "env", variable: "HOST" },
  { name: "env", variable: "PORT" },
  { name: "write", path: "logs.txt" },
  { name: "net", host: "127.0.0.1:8000" }
]
```
Repository: terminal
Issue: DSC Resource for Windows Terminal
Labels: Issue-Feature,Help Wanted,Area-Settings,Product-Terminal

# Description of the new feature/enhancement

I would like a DSC Resource so I can specify the way I want Windows Terminal configured. WinGet Configuration or the Dev Home experience could leverage a configuration file to set Windows Terminal up the way I want it.

# Proposed technical implementation details (optional)

Some notes from discussion: Paths in the json file will be **H**ard. If someone's got a relative path in their `settings.json`, well, that just won't work on another machine. 

The ideal case here is probably a dotfiles-like experience where we can DSC that folder of fonts, images, and settings.json. 

### Crawl
* We can install the Terminal. 

### Walk
* We can make some customizations to the settings.json. Maybe use a well-known URL to apply your settings. 

### Run
* We can also install fragment extensions the user already has.
* We can install distros, PWSH's etc. 

### Sprint
* We can export the current settings.json to a dotfiles-like folder, with images, fonts, etc, and re-write the settings.json to use that path
Repository: go
Issue: x/pkgsite/internal/poller: risk of starvation if the `Getter` starts taking too long
Labels: pkgsite

While looking into #61269, I noticed what looks like a dangerous pattern in the `poller` implementation.

The `poller` uses `context.WithTimeout` to add a timeout for the configured `Getter`. Unfortunately, it sets that timeout to be exactly equal to the configured period: if the `Getter` runs within that period everything is fine, but if it starts taking marginally longer than the period, it is likely that every call will fail with a `deadline exceeded` error and whatever the poller is supposed to be doing will fail to make progress:
https://cs.opensource.google/go/x/pkgsite/+/master:internal/poller/poller.go;l=49;drc=694b5d3c2a971c2a1dcdf7ab34e521b762bd326d

Instead, I would generally expect the `Getter` to be invoked with the same `Context` that controls the lifetime of the poller overall, so that it will only fail if the `Poller` is being shut down.

(However, it might make sense to _also_ invoke the `onError` callback as soon as the call overruns the period, so that it can trigger any monitoring that hooks into that callback.)
Repository: material-ui
Issue: [system] Remove custom behavior for sx={{ width: 1 }}
Labels: discussion,breaking change,package: system,v6.x

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

https://mui.com/system/sizing/

```jsx
<Box sx={{ width: 1 }} />
```

feels a bit like a foot gun. I would expect `1px`, not `100%`. This discussion started in https://github.com/mui/mui-x/pull/5177/files#r895041464.

### Examples 🌈

I would propose:

```diff
diff --git a/packages/mui-system/src/sizing.js b/packages/mui-system/src/sizing.js
index 0454dfb170..c6c8920e49 100644
--- a/packages/mui-system/src/sizing.js
+++ b/packages/mui-system/src/sizing.js
@@ -3,7 +3,7 @@ import compose from './compose';
 import { handleBreakpoints, values as breakpointsValues } from './breakpoints';

 export function sizingTransform(value) {
-  return value <= 1 && value !== 0 ? `${value * 100}%` : value;
+  return value < 1 && value > 1 ? `${value * 100}%` : value;
 }

 export const width = style({
```

### Motivation 🔦

_No response_
Repository: rust
Issue: Adding trait bound causes unrelated trait resolution to fail
Labels: A-trait-system,C-bug,T-types

_This example is minimized from [this code](https://github.com/google/zerocopy/commit/2a4cf85da0c27765251a8f5a8b799bdb28397b0a#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759R682-R698). Also [discussed on URLO](https://users.rust-lang.org/t/why-does-adding-an-already-satisfied-trait-bound-cause-my-code-to-break/98756)._

I have the following code:

```rust
pub trait HasAssocType {
    type Assoc;
}

pub trait Foo {}

impl<T: Foo> HasAssocType for T {
    type Assoc = ();
}

trait Bar {
    fn bar()
    where
        Self: Foo + Sized,
    {
        fn bar_inner<T: HasAssocType<Assoc = ()>>() {}

        bar_inner::<Self>();
    }
}
```

This code compiles fine. However, when I modify the definition of `Bar` to `trait Bar: HasAssocType`, it fails:

```text
error[E0271]: type mismatch resolving `<Self as HasAssocType>::Assoc == ()`
  --> src/lib.rs:18:21
   |
18 |         bar_inner::<Self>();
   |                     ^^^^ type mismatch resolving `<Self as HasAssocType>::Assoc == ()`
   |
note: expected this to be `()`
  --> src/lib.rs:8:18
   |
8  |     type Assoc = ();
   |                  ^^
   = note:    expected unit type `()`
           found associated type `<Self as HasAssocType>::Assoc`
   = help: consider constraining the associated type `<Self as HasAssocType>::Assoc` to `()`
   = note: for more information, visit https://doc.rust-lang.org/book/ch19-03-advanced-traits.html
note: required by a bound in `bar_inner`
  --> src/lib.rs:16:38
   |
16 |         fn bar_inner<T: HasAssocType<Assoc = ()>>() {}
   |                                      ^^^^^^^^^^ required by this bound in `bar_inner`

```

I'm surprised by this - the existing `Self: Foo` bound on `fn bar` was previously sufficient to constrain `<Self as HasAssocType>::Assoc == ()`, so I don't understand why further constraining `Self: HasAssocType` would somehow cause that to no longer hold.

cc @CAD97
Repository: flutter
Issue: (iOS 17) Text selection magnifier is out of date
Labels: a: text input,platform-ios,P2,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)

### Steps to reproduce

  1. Run any app with selectable text, such as the one below (after entering some text into the field).
  2. Long press and drag to move the cursor.

### Expected results

The latest, iOS 17-style magnifier appears:

![output](https://github.com/flutter/flutter/assets/389558/a87a70d2-56fe-4c88-bd35-11e0cba859e2)



### Actual results

An out-of-date magnifier appears:

![output](https://github.com/flutter/flutter/assets/389558/a63f39f2-6d7e-40a5-acc1-6ba176aa5ee7)


### 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(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: const <Widget>[
            TextField(),
          ],
        ),
      ),
    );
  }
}
```

</details>


### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
[!] Flutter (Channel master, 3.14.0-9.0.pre.12, on macOS 13.5 22G74 darwin-arm64, locale en)
    ! Unknown upstream repository.
      Reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[!] Android Studio (version unknown)
    ✗ Unable to determine Android Studio version.
[✓] Android Studio (version 2022.2)
[✓] Connected device (4 available)
[✓] Network resources
```

</details>
Repository: angular
Issue: Misleading change detection source. 
Labels: area: zones,area: devtools

### Is this a bug report or a feature request?

- [X] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

Suppose I have this demo code : 

```ts
this.zone.runOutsideAngular(() => {
  document.getElementsByTagName('button')[0].addEventListener('click', () => {
      this.zone.run(() =>   this.name += ' test');
  });
});
```
The devTools will report that the change detection source is `HTMLButtonElement.addEventListener:click`

or

```ts
this.zone.runOutsideAngular(() => {
  window.setTimeout(() => {
    this.zone.run(() => this.name += ' test');
  }, 3000);
})
```

Here the devTools report `setTimeout` as the source. 


I find this a bit misleading since `addEventListener`/`setTimeout` are called outside the angular zone and it's the `zone.run` that is responsible for calling the change detection. 

This thing happens with 


WDYT ?
Repository: godot
Issue: 2D-HDR may cause issues with texture alpha rendering
Labels: discussion,topic:rendering,documentation,topic:2d

### Godot version

v4.2.dev3.official

### System information

Windows 11 [Vulkan (Forward+)]

### Issue description

Enabling 2D-HDR support seems to mess up the alpha channel of imported textures (used in a Sprite2D in this example).  I don't know if this is an intended side-effect that needs to be worked around somehow, or if this is a bug.  See the image below for an example.

![image](https://github.com/godotengine/godot/assets/8756569/b3db606a-a4db-4e6b-ab11-357b209096e5)

Texture import settings are defaulted, as follows:

![image](https://github.com/godotengine/godot/assets/8756569/6ef7a321-4731-4b90-adb6-d95b5fcaa8f7)



### Steps to reproduce

Here's the sample border image that contains alpha information.  Place it on a black (or very dark) background and enable/disable the 2D-HDR option and observe how the alpha transparency changes.

![BFSquare_Border](https://github.com/godotengine/godot/assets/8756569/f46b9f99-03bb-4547-b750-c5ec66f4b80e)


### Minimal reproduction project

All information to reproduce is included above.

Also tested with the #80651 PR changes and the issue still persists.
Repository: go
Issue: cmd/compile: dead code-elimination should work for sync.OnceValue
Labels: NeedsInvestigation,FeatureRequest,binary-size,compiler/runtime

This is special case of #14840, but identified as a potential source of special-cases if the general case is hard to solve.

Compiling the following program:
```go
package main

import "sync"

var initializeVariable = sync.OnceValue(func() string {
    return "THIS_IS_DEAD_CODE"
})

func main() {}
```

should not link in logic for `initializeVariable` since the variable is dead.
This also applies to `OnceFunc` and `OnceValues`.

At present, `OnceValue` is unfortunately not a drop-in replacement for for `sync.Once` for initializing global variables.
Repository: flutter
Issue: `focus_manager` should check for `debugPrintKeyboardEvents` for logging key events
Labels: a: text input,framework,c: proposal,f: focus,P3,team-framework,triaged-framework

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

In `focus_manager.dart`, key events are logged in `_focusDebug` checking if `debugFocusChanges` is `true`. This generates a lot of undesired output if I'm only interested in key events.

There is a `debugPrintKeyboardEvents` flag, but when set, there isn't output indicating whether the key event was handled. This output is generated when `debugFocusChanges` is true.

To confirm, run the following code and press any key: 

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  debugFocusChanges = true;
  runApp(MaterialApp(
    home: Scaffold(body: SizedBox()),
  ));
}
```

</details>



### Proposal

Check for `debugPrintKeyboardEvents` when logging key events instead of `debugFocusChanges`.
Repository: PowerToys
Issue: number calculation error in powertoys run
Labels: Issue-Bug,Area-Quality,External Dependency,Priority-1,Run-Plugin

### Microsoft PowerToys version

0.72.0

### Installation method

GitHub, PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. activate power toys run by key shortcut
2. enter `=2^50`

### ✔️ Expected Behavior

expected answer is 1125899906842624

### ❌ Actual Behavior

actual answer is 1125899906842620

actually, any answer of 2^x would not be multiply of 10.
under any x >= 50, answer from powertoys run will be a wrong answer.
I guess the floating-point number introduced errors. 
But if the error could not be avoided, users should be notified explicitly on the UI.

### Other Software

windows calculator(11.2210.0.0): 1,125,899,906,842,624

python 3.8.10: python -c "print(2**50)" shows 1125899906842624
Repository: flutter
Issue: Inconsistent a11y voice-over behavior for state toggling buttons on different platforms
Labels: platform-android,platform-ios,framework,f: material design,a: accessibility,platform-web,customer: google,a: desktop,has reproducible steps,P2,c: parity,team-design,triaged-design,found in release: 3.13,found in release: 3.15

Copied from Google bug b/296949014:

## Summary
I have FAB that, when pressed, changes the screen state and its own tooltip and icon. The a11y behavior of this button is different on iOS, Android and Web. It would be nice to make them consistent throughout.

On iOS:
- When voiceover is on, tapping the FAB will make it announce the resultant button tooltip after the toggle is complete. However, it only announces the button tooltip and not the ", button" after it.

on Android:
- When talkback is on, tapping the FAB will make no talkback announcements.

on Web:
- on Mac, the voiceover software sometimes announces the tooltip + button phrase correctly, sometimes announces just the tooltip. Additionally, if the state change requires some time to render (e.g. not the minimum app), it skips the announcement entirely.

Expected outcome:
Voice over a11y softwares on different platforms should announce the button tooltip and also the phrase to indicate that the user is on a button. In other words, the a11y voice over should announce the same thing as if the user changed focus to this button, after the state change.

Note on prioritization: This isn't strictly blocking anyone, but it could in the future.

## Repro project
<details>
<summary>Minimal repro app</summary>

```
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(useMaterial3: false),
      title: 'Flutter Demo',
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _onScreenA = true;

  void _toggleScreen() {
    setState(() {
      _onScreenA = !_onScreenA;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title, style: TextStyle(fontFamily: 'ProductSans')),
      ),
      body: Center(
        child: Text(
          _onScreenA ? 'Screen A' : 'Screen B',
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _toggleScreen,
        tooltip: _onScreenA ? 'Show Screen B' : 'Show Screen A',
        child: _onScreenA ? const Icon(Icons.add) : const Icon(Icons.delete),
      ),
    );
  }
}
</details>
```
Repository: material-ui
Issue: [joy-ui] Add `Backdrop` component
Labels: new feature,waiting for 👍,component: backdrop,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Material UI has the Backdrop component, but Joy UI does not.

### Examples 🌈

https://mui.com/material-ui/react-backdrop/


### Motivation 🔦

I had been using Backdrop in Material UI to overlay a spinner on the page. This isn't available with Joy UI. The docs show a backdrop prop for the Joy UI modal, but a modal isn't the right component for this case. Will this be added to Joy UI? If not, how should I replicate a spinner over the page?
Repository: flutter
Issue: Support selected `child` for tabs in `TabBar`.
Labels: c: new feature,framework,f: material design,c: proposal,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

`NavigationBar` has this nice API for navigation items where each item can specify its `icon` and `activeIcon` separately. This helps in cases where user wants different behavior for selected state.

This behavior however, is missing from `TabBar` widget. We can only specify `icon` or `child` which is used for both selected and unselected state with different icon themes. While this works great when you're using `Icon` or `ImageIcon` widgets that can hook into these inherited themes, it doesn't work for a custom requirement. 

e.g. Using an svg icon with `SvgPicture` widget from `flutter_svg` package. This doesn't hook into those inherited themes. The styling has to be specified manually. And since current implementation uses inherited widgets, there is no way to get those from context without using a `Builder` widget on the Tab `child` which is more boilerplate.

> AFAIK, I am pretty sure no workaround exists for this in the current API for `Tab`.

### Proposal

It would be nice to have `selectedChild` or `activeIcon` to be able to specify widgets for selected state.

```dart
TabBar(
  tabs: [
    Tab(
      icon: SvgPicture.asset('assets/ic_home.svg', color: Colors.grey),
      selectedIcon: SvgPicture.asset('assets/ic_home.svg', color: Theme.of(context).colorScheme.primary),
    ),
  ],
);
```

Since Tabs support either specifying `icon`, `label` or `child`, corresponding selected states are required: `selectedIcon`, `selectedLabel`, `selectedChild`. I am fine with only having `selectedChild` too if its too much trouble adding `selectedIcon` and `selectedLabel`.
Repository: godot
Issue: Godot colour discolouration in editor
Labels: discussion,topic:rendering,topic:editor,needs testing

### Godot version

4.1.1

### System information

Windows 7

### Issue description

From an existing project used Quit to Project List and editor was distorted with colour on loading new project.
![image](https://github.com/godotengine/godot/assets/25694861/96f2d4da-4740-4e41-ace4-5bbdfe785177)
The project itself ran fine as normal. Just in the Editor was it discoloured.


### Steps to reproduce

This has happened once before. Load Godot editor. Select project. Click on project to edit. editor loads with unusual colour gradients in each window.

### Minimal reproduction project

N/A
Repository: flutter
Issue: [Impeller] Move the skyline rect packer in typographer to core.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

https://github.com/flutter/engine/pull/44887#discussion_r1300472580