sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking issue for release notes of #91399: Tracking Issue for `float_next_up_down`
Labels: T-libs-api,relnotes,A-floating-point,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #91399.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Tracking Issue for `float_next_up_down`](https://github.com/rust-lang/rust/issues/91399)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @yaahc -- origin issue/PR authors and assignees for starting to draft text
Repository: godot
Issue: iOS export fails with provisioning profile error
Labels: bug,platform:ios,topic:editor,topic:export

### Tested versions

4.4.beta1.mono

### System information

Godot v4.4.beta1.mono - macOS Sonoma (14.6.1) - Multi-window, 1 monitor - Metal (Mobile) - integrated Apple M2 (Apple8) - Apple M2 (8 threads)

### Issue description

iOS export was working in Godot 4.3 stable but fails to create the .ipa when using version 4.4 beta 1:

error: "rockhopper" requires a provisioning profile. Select a provisioning profile in the Signing & Capabilities editor.

I'm using the same export settings as the version that is currently live on the App Store:

Export Method Release: Development
Code Sign Identity Release: iPhone Developer
Provisioning Profile UUID Release: [EMPTY]

Previously, this would create the ipa file and Xcode project with "Automatically manage signing" set.

### Steps to reproduce

Reproducible with a minimal Godot project.
Export project to iOS (debug or release)

### Minimal reproduction project (MRP)

N/A
Repository: node
Issue: Excessive slowness during AES-GCM decryption
Labels: crypto

### Version

22.2.0

### Platform

```text
Darwin MBP.local 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64
```

### Subsystem

_No response_

### What steps will reproduce the bug?

Profile the following:

```js
import webcrypto from 'tiny-webcrypto';
import encryptor from 'tiny-encryptor';

const SECRET = 'P@ssword!';
const SAMPLE_1GB = new Uint8Array ( 1024 * 1024 * 1024 );
const enc = await encryptor.encrypt ( SAMPLE_1GB, SECRET );
const dec = await encryptor.decrypt ( enc, SECRET );
```

It should produce a trace like this:

<img width="1152" alt="Image" src="https://github.com/user-attachments/assets/778a4a5f-a214-4b0c-b299-302238da9b99" />

Basically we can see that decryption is way slower than encryption, but how come? There seems to be a useless (arguably) [copy of the data buffer](https://github.com/nodejs/node/blob/74717cb7fa21eb7d7c2abc579334f28c66d96fb0/lib/internal/crypto/aes.js#L187) when decrypting, but I think it would be totally reasonable to simply delete this copy and getting a subarray instead. It's obvious that you shouldn't be modifying something while its being processed by something else if you don't want problems.

Basically this copy has a tangible cost, obviously, but a very intangible benefit, especially since a "tag" is used, if the underlying buffer gets modified under our nose the decryption should fail, I think.

So basically I think we should switch to a subarray instead of a slice there and get rid of this unnecessary slowness.

### How often does it reproduce? Is there a required condition?

Always.

### What is the expected behavior? Why is that the expected behavior?

No slowness caused by operations of dubious utility at best.

### What do you see instead?

Slowness caused by operations of dubious utility at best.

### Additional information

_No response_
Repository: kubernetes
Issue: [Sig-Network] Networking Granular Checks: Pods should function for intra-pod communication: sctp [LinuxOnly] [Feature:SCTPConnectivity]
Labels: sig/network,kind/failing-test,needs-triage

### Which jobs are failing?

- https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-node-features
- https://testgrid.k8s.io/sig-node-containerd#node-e2e-features
- https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv1-containerd-node-features

### Which tests are failing?

[Sig-Network] Networking Granular Checks: Pods should function for intra-pod communication: sctp [LinuxOnly] [Feature:SCTPConnectivity]

### Since when has it been failing?

As of Jan 16th.

### Testgrid link

https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-node-features

### Reason for failure (if possible)

We dropped NodeFeature in all of our sig-node jobs. This test is being picked up but it isn't obvious to me why it is failing.

I can filter it out but I wanted to bring this up here to see if this is actually an issue.

### Anything else we need to know?

https://github.com/kubernetes/kubernetes/blob/master/test/e2e/common/network/networking.go#L135

The other test is skipped.

### Relevant SIG(s)

/sig networking
Repository: PowerToys
Issue: [Settings] ImageResizer settings files may be saved too often
Labels: Issue-Bug,Idea-Enhancement,Product-Settings,Area-Quality,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Settings

### Steps to reproduce

1. Open the Settings application and navigate to the ImageResizer page
2. Click on the Edit button for any one of the listed size presets

![Image](https://github.com/user-attachments/assets/63f17bdb-0102-4b1e-a54b-6e0af6c18b7b)

4. Click on either Width or Height in the flyout edit dialog
5. Click or hold down on either the up or down arrow

![Image](https://github.com/user-attachments/assets/fc264180-83e4-4801-8f30-68f4c3b02e44)

6. Observe that the "settings.json" and "sizes.json" files are saved after every change in the width or height value

### ✔️ Expected Behavior

The settings files are only saved after a short delay, to account for multiple edits in a short period of time.

### ❌ Actual Behavior

The settings files are saved immediately after every change, even rapid changes via the up/down arrows.

### Other Software

_No response_
Repository: PowerToys
Issue: Auto Text Expand or Auto Text
Labels: Needs-Triage

### Description of the new feature / enhancement

Integrate a "Auto Text " feature into Microsoft PowerToys, providing users with advanced text input tools. This feature would include capabilities such as auto-correction, text expansion, customizable shortcuts, predictive text, and multi-language support. The goal is to enhance typing efficiency and accuracy across all Windows applications.

### Scenario when this would be used?

The feature would be useful in the following scenarios:

Professional Writing: When users are drafting emails, reports, or documents, this feature can auto-correct typos, suggest better word choices, or complete frequently used phrases.
Code Writing: Developers can use customizable text expansions or shortcuts for repetitive code snippets, improving productivity.
Language Learning: Users working in a second language can benefit from real-time grammar suggestions and translation tools.
Accessibility Needs: Individuals with physical disabilities or typing difficulties can use predictive text to reduce effort and improve input speed.

### Supporting information

Customizability: Allow users to create custom dictionaries, phrase expansions, and configure features to fit their needs.
Machine Learning Models: Incorporate lightweight, on-device AI models to ensure privacy and enhance predictive accuracy.
Cross-App Functionality: Ensure that feature works seamlessly across all applications, including browsers, text editors, and command-line interfaces.
Existing Examples: Inspiration could be drawn from tools like TextExpander, Grammarly, or Apple's QuickType, but designed to align with PowerToys' open-source, modular approach.
This feature would empower users to work more efficiently and effectively, making it a valuable addition to the PowerToys suite.
Repository: vscode
Issue: Shell type should be undefined when running an unrecognized shell
Labels: feature-request,terminal-shell-integration

Repro:

1. Open pwsh on Windows
2. Open R shell
3. Try paste with ctrl+v, 🐛 doesn't work

Context: https://github.com/microsoft/vscode/issues/238126#issuecomment-2598624657
Repository: PowerToys
Issue: Automation for PowerToys
Labels: Needs-Triage

### Description of the new feature / enhancement

Integrate a "Microsoft Automation" feature into Microsoft PowerToys, enabling users to automate repetitive tasks and workflows directly within the PowerToys suite. This feature would provide tools for creating scripts, automating UI interactions, and streamlining processes such as file management, text manipulation, and application control.

### Scenario when this would be used?

The Microsoft Automation feature would be useful in the following scenarios:

Routine Task Automation: Users can automate repetitive actions like renaming files, copying data, or scheduling tasks, saving time and effort.
UI Interaction Automation: Automate mouse clicks, keyboard inputs, or menu navigation for tasks requiring repetitive user interface interactions.
Custom Workflow Creation: Build custom scripts to integrate various applications or services for complex workflows, such as exporting data from one app and formatting it for another.
Enhanced Productivity: Automate actions like launching a set of applications or performing batch operations, improving overall productivity.
Accessibility Needs: Help users with physical disabilities by automating actions they find difficult to perform manually.

### Supporting information

Integration with PowerToys Philosophy: Microsoft Automation would align with PowerToys' goal of empowering users with advanced, customizable tools to enhance their productivity.
Low-Code/No-Code Interface: Provide an intuitive drag-and-drop or low-code interface for users without programming experience. Advanced users could also utilize scripting for greater flexibility.
Cross-Application Compatibility: Ensure automation scripts work seamlessly across various Windows applications and environments.
Prebuilt Templates: Offer templates for common automation tasks (e.g., bulk renaming, text formatting, data processing) to simplify the user experience.
Existing Inspiration: Features could draw inspiration from tools like Power Automate Desktop, AutoHotkey, or macro recorders, tailored to PowerToys' modular and open-source framework.
Adding Microsoft Automation to PowerToys would make the suite a more comprehensive tool for power users, enabling them to automate tasks effortlessly and improve their daily workflows.
Repository: godot
Issue: SpringBoneSimulator3D raises Node3D asserts when exiting tree
Labels: bug,topic:animation,topic:3d

### Tested versions

- v4.4.beta1.official [d33da79d3]

### System information

Godot v4.4.beta1 - Windows 11 (build 22631) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 SUPER (NVIDIA; 32.0.15.6603) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 threads)

### Issue description

Whenever an active SpringBoneSimulator3D exits the scene tree, it raises this assert: https://github.com/godotengine/godot/blob/d33da79d3f8fe84be2521d25b9ba8e440cf25a88/scene/3d/node_3d.cpp#L466 

When the modifier is made inactive, the asserts no longer occur.

### Steps to reproduce

The MRP sets this up in a simple demo scene: press space to toggle remove/adding the tail armature to the scene tree.

### Minimal reproduction project (MRP)

[springbone_error_2025-01-17_11-29-16.zip](https://github.com/user-attachments/files/18457939/springbone_error_2025-01-17_11-29-16.zip)
Repository: ant-design
Issue: Table组件在设置了scroll后，切换路由头部会闪烁一下
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/84lz8y)

### Steps to reproduce

来回切换路由可以看见头部闪一下

### What is expected?

不要闪烁

### What is actually happening?

切换路由就会闪烁

| Environment | Info |
| --- | --- |
| antd | 5.23.1 |
| React | "react": "18.2.0", |
| System | mac |
| Browser | chrome版本 131.0.6778.205（正式版本） (x86_64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ui
Issue: [bug]:The list width is 2 pixels wider than the trigger width
Labels: bug

### Describe the bug

The list width is 2 pixels wider than the trigger width. I haven't tested the component in the project, I just noticed this imperfection in the documentation

<img width="886" alt="Image" src="https://github.com/user-attachments/assets/a67aee98-cd5e-4ced-bb59-4c0cd8dec9f9" />

### Affected component/components

Select

### How to reproduce

Just see it in docs

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
Win11
Chrome 131.0.6778.265
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: flutter
Issue: [go_router] Implement go_router devtool using DevTools extensions
Labels: team-go_router

### Use case

Sometimes developers need to navigate to a specific route for testing. This can be challenging if the route originates from an HTTP request or if you need to perform certain actions to invoke the routing action.

Another troublesome issue arises when your app has numerous complex redirects, and you need to debug potential problems.

### Proposal

The proposal is to create a [DevTools extension](https://docs.flutter.dev/tools/devtools/extensions) for go_router.

This `devtool` would have some capabilities like:

 - Displaying the registered routes in a tree-like structure, similar to Flutter's widget tree inspector. 
 - Allowing the invocation of navigation methods (go, push, pop, etc.) directly from within the devtool.
 - Holding the navigation history to allow better `redirect` debugging.
Repository: TypeScript
Issue: Branded string literals revert to `string` in some cases
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

If I create a branded string literal it seems to respect the string literal in the basic case of assigning to a property, however it loses this information and just reverts to string when assigning to a property or in a template string.

It makes sense that the brand object needs to be dropped in these cases, but rather than converting to string, it should convert to the narrower literal type.

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about branded string


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/C4TwDgpgBAsiAyBLYEBOBDANgHgMpQgA8UA7AEwGcoLhVESBzAPigF4p8AyKAbwH0ARhnIAuXgF9xAbgBQAYwD2JGlHRsoAcnQbVVOEhQYcWjU1nylKwmJPr0UqAHpHUAO4LUAawoBCC8uAoEBttdQADABIedHEwh2coADN0RExffxUALzFosRIAVwBbATRxdR4AbXQAXTEADjKE5NTfIA

### 💻 Code

```ts
type MyLiteral<S extends string> = S & {_brand: {}};
const a = 'a' as MyLiteral<'a'>;

const x: 'a' = a; // works!
const y: 'a' = `${a}`; // fails!
const z: {a: number} = {[a]: 8} // fails!
```


### 🙁 Actual behavior

For `y` and `z`, the types don't match because `a` is converted to `string` rather than `'a'`

### 🙂 Expected behavior

The types should match in all 3 cases, `x`, `y`, `z`

### Additional information about the issue

_No response_
Repository: pytorch
Issue: Tracking issue: Incorrect Meta Strides / Turn On PyDispatcher in FakeTensor Mode
Labels: triaged,oncall: pt2,module: fakeTensor,module: decompositions,module: pt2-dispatcher

### 🐛 Describe the bug

Incorrect Strides can manifest in errors within torch.compile. Potentially what makes them trickier is that they only sometimes cause errors. An incorrect stride can lay dormant for a while and then cause a problem. 

See, [this discussion](https://github.com/pytorch/pytorch/issues/144699#issuecomment-2591018702) with @ezyang, @bdhirsh and myself about incorrect strides.


There are a number of known issues that yet unfixed. Some of them have outstanding prs, please check with the pr author before taking it on.

- [ ] `full_like`: https://github.com/pytorch/pytorch/issues/144699
- [ ] `_unsafe_index` : https://github.com/pytorch/pytorch/issues/139312
- [ ] `_fft_r2c`: https://github.com/pytorch/pytorch/issues/135087
- [ ] `_constant_pad_nd`: https://github.com/pytorch/pytorch/issues/144187

Additionally, there are a number of stride & other issues that have been exposed by enabling PyDispatcher in FakeTensorMode. This causes us to potentially route through different decompositions and metas. It is what we use in torch.compile, which means we lack coverage of this mode in our other tests.
 
Tests exposed by this [turning this on](https://github.com/pytorch/pytorch/pull/138953#issuecomment-2438965279):
- [ ] dropout
- [ ] MultiLabelMarginLoss


Fft tests as well, but that might be related to `_fft_r2c` in the existing issue.




### Versions

master

cc @chauhang @penguinwu @SherlockNoMad @zou3519 @bdhirsh @yf225
Repository: PowerToys
Issue: [ImageResizer] Pick up settings changes automatically
Labels: Idea-Enhancement,Product-Image Resizer,Needs-Triage

### Description of the new feature / enhancement

This enhancement would automatically reload any changes made by the user to the Image Resizer options within the Settings application. Currently, making changes requires Image Resizer to be closed and reopened.

Ideally, there would be a brief notification in the Image Resizer UI to indicate that the updated settings had been loaded.


### Scenario when this would be used?

It would allow users to make changes to presets and options like "Filename format" while the application is open, streamlining situations where the existing properties are not quite right for the current operation.

### Supporting information

We rely on the user knowing (without this being documented) that they need to close and reopen the application when making changes in the Settings app. A novice user could easily assume that the changes they make in the Settings app (say to "Filename format" or the file modified option) would be immediately reflected in the open Image Resizer application.
Repository: rust
Issue: Tracking issue for release notes of #127292: Tracking Issue for PathBuf::add_extension and Path::with_added_extension
Labels: T-libs-api,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #127292.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Tracking Issue for PathBuf::add_extension and Path::with_added_extension](https://github.com/rust-lang/rust/issues/127292)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @tisonkun -- origin issue/PR authors and assignees for starting to draft text
Repository: PowerToys
Issue: [ImageResizer] Images may be saved to a new file but not resized
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Image Resizer

### Steps to reproduce

1. Create a new Image Resizer preset within the Settings application of 4000 by 4000 pixels with a Fit setting of "Fit"
2. In Explorer, right-click on any image smaller than 4000 x 4000 pixels
3. Select "Resize with Image Resizer" to open Image Resizer
4. Select the preset created in Step 2
5. Ensure "Make pictures smaller but not larger" is checked
6. Click the Resize button

### ✔️ Expected Behavior

Either:

1. No work is done because the image already fits within 4000 x 4000 pixels and does not need to be resized, or;
2. The original file is copied, following the filename format and file modified settings defined in the Settings application

### ❌ Actual Behavior

The image is 'resized' but with the same dimensions as it was originally. For lossy codecs like JPEG, this results in a generational degradation in quality.

### Other Software

_No response_
Repository: TypeScript
Issue: [isolatedDeclarations] Quick-fix for adding missing annotations can duplicate comments
Labels: Bug,Help Wanted

### 🔎 Search Terms

isolatedDeclarations, autofixer, quick fix, quickfixer, quick-fix, duplicate, redundant, comments

### 🕗 Version & Regression Information

TS5.5+

### ⏯ Playground Link

https://www.typescriptlang.org/play/?downlevelIteration=true&importHelpers=true&target=99&module=1&isolatedDeclarations=true&ts=5.7.3#code/KYDwDg9gTgLgBAMwK4DsDGMCWEWIBQCUcA3gFBwVxo4DO8EcAvHAPQBUbcARsAtMHDYsSrTphQAbcQMh0AtMUHCWw4CgAmcKShkR5ZSpRVx1ENEgC2a+AkxQ6cGAE8wwcodFxx2gTz5QBITgQT29pODAAuWoJHCU4AC5QyXDI4DlnV3iAVmSfCL0YDJdA4QAaVmEAQwQYYCgqCAsLKoBGd0NjU3MrFHgaYGoNRxKOow44ACZuXn54p0S4AHI6KCXRTmmauoahCpVt+sbmqsmximM06NiacQBzMYBfDbhD3ZYAbjGAmCQoXAgX0eQA

### 💻 Code

```ts
export function f() {
    const o = /** before */ { /* inline post-{ */ // end line post-{
      // document first type
      /* inline before */ x /* inline pre-colon */ : /* inline pre-type */ 5 /* inline post-type */ , // after comma1
      // document second type
      /** 2 before */ y : 'str' /** 2 after */, //after comma2
      // pre-closing
    } /** after */;
    return o;
}
```


### 🙁 Actual behavior

After running the autofixer, the result includes many of the inline code comments in the added type annotation. It looks like:
```ts
export function f(): { /* inline post-{ */ // end line post-{
// document first type
/* inline before */ x: number; /* inline post-type */ // after comma1
// document second type
/** 2 before */ y: string; /** 2 after */
} {
    const o = /** before */ { /* inline post-{ */ // end line post-{
      // document first type
      /* inline before */ x /* inline pre-colon */ : /* inline pre-type */ 5 /* inline post-type */ , // after comma1
      // document second type
      /** 2 before */ y : 'str' /** 2 after */, //after comma2
      // pre-closing
    } /** after */;
    return o;
}
```

### 🙂 Expected behavior

The actual behavior isn't technically broken, but I would generally expect/prefer the generated annotation to include only types with no comments.  Something like:

```ts
export function f(): {
    x: number;
    y: string;
} {
    const o = /** before */ { /* inline post-{ */ // end line post-{
      // document first type
      /* inline before */ x /* inline pre-colon */ : /* inline pre-type */ 5 /* inline post-type */ , // after comma1
      // document second type
      /** 2 before */ y : 'str' /** 2 after */, //after comma2
      // pre-closing
    } /** after */;
    return o;
}
```

### Additional information about the issue

_No response_