sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: File Touch command
Labels: Idea-New PowerToy,Product-File Explorer,Product-File Actions Menu

### Description of the new feature / enhancement

Add a "touch" file feature to update the file date to current date or to a date specified by the user.

### Scenario when this would be used?

To inform the user or recipient of a file is "up to date" even though it physically was not modified.  Comes in handy to when backing up files after a certain date.

### Supporting information

See this IBM documentation: https://www.ibm.com/docs/pl/aix/7.1?topic=t-touch-command
Repository: flutter
Issue: [flutter_tools] the tool should have a way to share validation checks between the doctor and flutter build
Labels: tool,c: proposal,P3,team-tool,triaged-tool

We have many validations that run as part of the `flutter doctor` command that would detect either a failing build or an invalid one (inspired by https://github.com/flutter/flutter/issues/125653). We should refactor the tool such that validators can register themselves as something that should run before a build for that platform.
Repository: flutter
Issue: Remove preconstructed context objects from LayerTestBase
Labels: engine,P2,team-engine,triaged-engine

The layer tests all use member variables for PrerollContext and PaintContext objects held in the LayerTestBase class that they inherit from. Since they have different needs for what variants of data they want stored in those contexts, the base class has to construct a number of different variations of those contexts ready to be used by the appropriate tests. Further, some of the tests will "customize" the contexts before they use them. While the objects are local to a given test, it feels like modifications for persistent objects is not a good design. Additionally, some tests go through multiple "virtual frames" of testing, reusing those objects over and over between tests. That reuse is not against any design criteria of the context objects, but it seem fragile, especially when those reuses are also combined with customizing some of the context fields.

The objects contain many values most of which are defaulted for any given test so directly constructing them in each test would be quite verbose and create a potential widespread maintenance hassle every time the fields of these context objects are added/removed/modified.

Instead of these pre-allocated context objects, LayerTestBase should provide a factory to create the objects using various arguments that specify the customizations being used. This would avoid:

- creating pre-allocated contexts for variants that will not be used in the tests
- make it easier to introduce new context data into the system by providing a single place to modify the setups of the context for all tests
- allow tests to customize the generated contexts without any concerns about potential reuse for additional testing frames
Repository: PowerToys
Issue: Option to Auto-Activate Find My Mouse On Wake
Labels: Needs-Triage

### Description of the new feature / enhancement

Add an option to have Find My Mouse automatically activate for a configurable amount of time after waking the monitors or system from sleep. Turning off after the designated period of time.

### Scenario when this would be used?

Anywhere people may have difficulty finding their mouse cursor on multiple large monitors after waking the monitors or computer from a sleep state. 

### Supporting information

_No response_
Repository: PowerToys
Issue: Peek should have the option to close itself when releasing the shortcut keys
Labels: Idea-Enhancement,Help Wanted,Product-Peek

### Description of the new feature / enhancement

Right now after you Ctrl+Space to peek, you need to manually close the peek window.

It would be useful if the window would close itself once you release control;.

The way I think this should be implemented is via a separate shortcut option. The current shortcut opens the current window with the additional options such as resizing the preview or opening the file in its associated application. The new shortcut will open a popup window with minimal UI (just the preview) that will close itself once the modifier keys for the shortcut are released. It would not be possible to bind a shortcut without a modifier key.

Not sure if you can detect the release of keys for global hotkeys; you may need to just have the preview window poll for it. It will be in focus if that helps. If it loses focus you can just close it at that point too.

### Scenario when this would be used?

Allows for quicker use of Peek.

### Supporting information

When I heard of Peek this is what I thought it would be, for whatever that's worth.
Repository: flutter
Issue: Option to specify checkout levels in engine_v2 drones
Labels: c: new feature,team-infra,P2,triaged-infra

The engine v2 drones right now do a full gclient checkout in every test shard. In order to reduce this overhead, we can adjust some of our builder configurations to not be reliant on gclient checkout, and eventually not require a source checkout at all. In order to do this, we'd need to be able to specify what type of checkout we need in the engine_v2 builder json. I'd like to suggest three levels:
* Full gclient checkout
* Source checkout only (no `gclient`)
* No checkout
This should allow us to make the web test shards much lighter weight and quicker to execute.

Note: I also noticed that `tester.py` always checks out the flutter framework, which I think is required by the monorepo test shards. It might also be a good idea to make this customizable so that we can avoid that checkout as well, as a large majority of the engine tests do not require the framework at all.
Repository: rust
Issue: Tracking Issue for `riscv-interrupt-{m,s}` ABIs
Labels: T-compiler,C-tracking-issue,O-riscv,A-ABI,A-hardware-interrupts

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for the RFC "XXX" (rust-lang/rfcs#NNN).
The feature gate for the issue is `#![feature(FFF)]`.

Similar to https://github.com/rust-lang/rust/issues/38487,  https://github.com/rust-lang/rust/issues/69664 , and https://github.com/rust-lang/rust/issues/40180 the intent is to plumb the existing riscv interrupt handler support in LLVM through the front-end. It would enable writing e.g.

```rust
extern "riscv-interrupt-m" fn machine_mode_handler() {
    ...
}
```

to produce a function with a prologue/epilogue suitable for being the target of a hardware interrupt.


### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement the RFC 
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

XXX --- list all the "unresolved questions" found in the RFC to ensure they are
not forgotten

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
https://github.com/rust-lang/rust/pull/111891
Repository: godot
Issue: Editor Translate Snap Shifted Decimals
Labels: bug,topic:editor,topic:3d

### Godot version

v4.0.stable.official [92bee43ad]

### System information

Windows 10, AMD Ryzen 7 3700X 8-Core Processor

### Issue description

Editing the grid translate snap number, leaving that scene in the editor, then coming back the number will shift by a small amount.
This is in the 3D tab.

Ex:
I set it as 0.0005, which shifted to 0.00050000002375
or 0.01 became 0.00999999977648

### Steps to reproduce

-Be in the 3D view.
-Edit the _translate snap_ in a scene to a specific number (it has to be a floating point number).
-Switch scene, then come back.
-Open the _configure snap_ menu and see it has slightly shifted (as shown in the examples in Issue desc.).

### Minimal reproduction project

N/A
Repository: godot
Issue: AnimatedTexture does not automatically animate in the inspector preview
Labels: bug,topic:editor,usability

### Godot version

4.1 dev2

### System information

Windows 10 x64

### Issue description


https://github.com/godotengine/godot/assets/2223172/69923393-14d0-41e9-9d7b-c271fa79a0f6

We could probably detect if the displayed texture is AnimatedTexture and call `queue_redraw()` in `_process()`.

Relevant file is `texture_editor_plugin.cpp`.

### Steps to reproduce

1. Create AnimatedTexture
2. Inspect it

### Minimal reproduction project

https://github.com/godotengine/godot/files/10528262/AnimatedTexture.zip
Repository: bitcoin
Issue: Creating too many wallets exhausts file descriptor limit and leads to crash
Labels: Wallet,macOS

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

This behavior was first noted by @EthanHeilman here: https://github.com/bitcoin/bitcoin/issues/11368#issuecomment-751574945 but it was conflated with the RPC issue there while I now think this is a separate issue.

When a lot of wallets are created in quick succession, sqlite will exhaust all the available file descriptors and the node crashes the next time it tries to create file for unrelated reasons (blk, rev etc.).

### Expected behaviour

The node shouldn't crash.

### Steps to reproduce

```
for i in $(seq 1 100); do src/bitcoin-cli createwallet "fd-wallet$i"; done
```

### Relevant log output

https://0bin.net/paste/swIJVCaU#CuCCWv7cC4ZscxjCEiauqEhB1icPiMHkYo+D5dC8mSr

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

master

### Operating system and version

macOS

### Machine specifications

_No response_
Repository: flutter
Issue: CanvasKit's canvas.drawPoints is broken in dart2wasm
Labels: engine,P2,e: wasm,team-web,triaged-web

Golden tests added in https://github.com/eyebrowsoffire/engine/pull/51 show that CanvasKit's `drawPoints` fails to render properly in dart2wasm. I believe this has something to do with the type handling we do between `Float32List`, `SkFloat32List`, and `JSFloat32Array`.
Repository: flutter
Issue: Disabled MaterialButton ignores disabledTextColor when textColor is set
Labels: framework,f: material design,has reproducible steps,P3,found in release: 3.10,found in release: 3.11,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

### disabledTextColor gets ignored when textColor is set and MaterialButton is disabled

`MaterialButton` can be disabled if the onPressed method isn't set or set to null.
I noticed that when disabled, `textColor` is being used instead of `disabledTextColor`

I know its a design choice but it seems weird that a disabled button with both `textColor` and `disabledTextColor` properties set, it will still use the `textColor`.

### Steps to reproduce
```dart
MaterialButton(
  onPressed: null,
  textColor: Colors.blue,
  disabledTextColor: Colors.red,
  child: Text("Button"),
);
```
### Expected results
Button text color **Red**.
### Actual results
Button text color **Blue**.

<br />

This seems even more weird when considering that the properties `color` and `disabledColor` behave differently.
For example:
```dart
MaterialButton(
  onPressed: null,
  color: Colors.blue,
  disabledColor: Colors.red,
  child: Text("Button"),
);
```

This will be filled **Red**.

### Proposal

I think that if `disabledTextColor` is set, it shouldn't be ignored to `textColor` when the button is disabled.

I think that will make more sense and make the widget more concise with its properties.
Repository: PowerToys
Issue: Fancy Zones Editor
Labels: Idea-Enhancement,FancyZones-Editor,Needs-Triage

### Description of the new feature / enhancement

Fancy Zones Editor should have the ability to flip layouts horizontally and vertically

### Scenario when this would be used?

allows consideration of symmetrical fancy zones being used in multi monitor setups. 
![image](https://github.com/microsoft/PowerToys/assets/83685156/1877cab0-28f8-4608-a685-7017bda689eb)
^ these layouts are completely symmetrical and the second one could be easily created with the ability to just mirror the first layout vertically. Instead of having to manually make it like I ended up having to do.

### Supporting information

_No response_
Repository: flutter
Issue: HTML renderer crashes when trying to render vertices with indexes
Labels: c: crash,platform-web,e: web_html,P3,team-web,triaged-web

When the HTML renderer tries to draw hairlines for vertices, it simply iterates over the vertices directly and attempts to render them as triangles, even if there is a set of indexes. This is wrong, and causes crashes when the number of vertices is not divisible by 3. See the unit test in `flutter/lib/web_ui/test/ui/vertices_test.dart` for an example of this issue in action.
Repository: angular
Issue: Sync `Observable` in Async validators in `FormGroup` with a `FormControl` inside `*ngIf` causes "ExpressionChangedAfterItHasBeenCheckedError"
Labels: area: forms

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

Hello,

Seems like a fairly common case but haven't been able to find a similar post.
(except for the following link but no docu link or explanation: https://stackoverflow.com/questions/42465003/async-validators-causing-expression-has-changed-error)
If it exists, kindly point me to it. Thanks. 

I have an async validator for a `FormGroup` that returns an sync `Observable` in some cases and async on another.
In same `FormGroup`, there are controls inside `*ngIf` that will show up depending on another control's value inside the same `FromGroup`.
When a control shows up because of a change in another control's value and async validator for `FormGroup` returns a sync `Observable`, the error shows up

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-bd4p4z?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
ExpressionChangedAfterItHasBeenCheckedError
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Also exists on v16 it seems as it happens on the stackblitz reproduction

Angular CLI: 14.2.10
Node: 16.18.1
Package Manager: npm 8.19.2 
OS: darwin x64

Angular: 14.2.12
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, platform-server, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1402.10
@angular-devkit/build-angular   14.2.10
@angular-devkit/core            14.2.10
@angular-devkit/schematics      14.2.10
@angular/cdk                    14.2.7
@angular/cli                    14.2.10
@schematics/angular             14.2.10
rxjs                            7.5.7
typescript                      4.6.4
```


### Anything else?

_No response_
Repository: electron
Issue: [Bug]: Non-modal window with parent does not minimize properly
Labels: platform/windows,bug :beetle:,has-repro-gist,24-x-y,25-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

24.3.1

### What operating system are you using?

Windows

### Operating System Version

Windows 10 Pro 21H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Window should not be visible on screen after minimizing, both via the native minimize button or via the `.minimize()` api call in the `BrowserWindow` object

### Actual Behavior

A small rectangle of the screen stays on the screen after minimizing
![image](https://github.com/electron/electron/assets/16294244/f9e41c80-e047-4368-8134-077beffce1be)


### Testcase Gist URL

https://gist.github.com/Levyks/217008d0b1335cb54b0d28101daa69ff

### Additional Information

The problem is the same as mentioned in issue #27327 , that is closed.

I've noticed that the problem only appears if I do not put `modal: true` in my window.

I was able to reproduce it in versions 24, 23, 22 and 9
Repository: create-react-app
Issue: Getting unexpected app after create create app
Labels: needs triage,issue: bug report


    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.

### Describe the bug

I installed a react app using create-react-app. I've tried .

After creating the app, I start the react app using 'npm start'. An app appears at localhost:3000, as expected. However, the app contents are different from what I expected compared to my project.

insteat of loading the project after start react it started "color-changer@0.1.0, and with a bottum. When I inspect the src/App.js files and a CustumButtom, which that is not in my project 



Here is the package.json file, it shows some dependencies.

### Did you try recovering your dependencies?
{
  "name": "fix",
  "description": "A simple fix for a bug in react-scripts",
  "type": "module",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@testing-library/jest-dom": "^5.16.5",
    "@testing-library/react": "^13.4.0",
    "@testing-library/user-event": "^13.5.0",
    "axios": "^1.4.0",
    "bootstrap": "^5.2.3",
    "jwt-decode": "^3.1.2",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-router-dom": "^6.11.1",
    "react-scripts": "^5.0.1",
    "reactstrap": "^9.1.10",
    "web-vitals": "^2.1.4"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}
![Screenshot 2023-05-23 231156](https://github.com/facebook/create-react-app/assets/67286010/37564128-591c-46ef-aa05-97667f2b4384)
![Screenshot 2023-05-23 231300](https://github.com/facebook/create-react-app/assets/67286010/ead2470f-d9d1-4181-9d9b-344003ffd7e4)

![Screenshot 2023-05-23 230639](https://github.com/facebook/create-react-app/assets/67286010/5fc13e74-e728-41b5-951f-8b4209e82902)
Repository: PowerToys
Issue: Peek should support .odt, .ods, and .odg files
Labels: Idea-Enhancement,Needs-Triage,Product-Peek

### Description of the new feature / enhancement

Peek should provide a preview of .odt, .ods, and .odg files (which are LibreOffice/OpenOffice "write", "spreadsheet", and "draw" documents).

### Scenario when this would be used?

Why is this important? Who wouldn't like to have a quick preview of the contents of such files? Isn't that the whole purpose of Peek??

### Supporting information

_No response_
Repository: rust
Issue: Allow specifying stack size of threads spawned by the test runner
Labels: C-feature-request,A-libtest

On platforms where concurrency is available, the test runner will always spawn threads with their default stack size: https://github.com/rust-lang/rust/blob/edbd5c5a78853d11f66b7581b6b90109b4853b7b/library/test/src/lib.rs#L596

There appears to be no way to control this stack size without altering the default stack size of the code running _within_ the test, via `RUST_MIN_STACK`.

The default rustc stack size for main thread is currently 8MiB: https://github.com/rust-lang/rust/blob/edbd5c5a78853d11f66b7581b6b90109b4853b7b/compiler/rustc_interface/src/util.rs#L124

I think for spawned threads it's whatever the platform default is: I think on my Linux box this is 2MiB.

Consider that I have two pieces of code: one using 1MiB of stack size, usually running on a thread. Another piece of code using 6MiB usually running on main thread, possibly spawning the 1MiB one.

I now have a `#[test]`. When I run it, I get a stack overflow because we've spawned a thread with 2MiB to run the 6MiB stack code.

What are my options? It seems `RUST_MIN_STACK` is my only option, so I set it to, say, 8MiB to match the main thread stack.

This makes the test pass.

However now  originally-1MiB stack code changes and stack usage to 3MiB! The test is still passing but the code is going to crash outside of tests: we've changed the behaviour of the code we are trying to verify is working because we're trying to work-around the test runner.

`RUST_MIN_STACK` is too big of a hammer: we should _either_ have a way to specify the stack size for the _test_ threads or pick a better default. It seems that the sanest default is the value of `fn get_stack_size()`. Changing the behaviour of code under testing just to control test runner seems very undesirable.

For people using `RUST_MIN_STACK` today, the behaviour remains the same. For people not using it, the memory usage of each test thread goes from their system default to the main-thread default. I think this is probably not a big deal for _test runner_. Indeed, if the program spawns any real number of threads, it might actually bring overall memory usage _down_.

PS: setting `--test-threads 1` doesn't help: it still spawns a single thread with the same problem. It seems that platforms that don't support concurrency are the only way to run tests truly "sequentially".