sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: [Flaking Test] [sig-apps] Kubernetes e2e suite.[It] [sig-apps] ReplicaSet Replace and Patch tests [Conformance]
Labels: kind/flake,sig/apps,needs-triage

### Which jobs are flaking?

master-blocking
- gce-cos-master-default

### Which tests are flaking?

Kubernetes e2e suite.[It] [sig-apps] ReplicaSet Replace and Patch tests [Conformance]
[Prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/1882170659614756864)
[Triage](https://storage.googleapis.com/k8s-triage/index.html?test=ReplicaSet%20Replace%20and%20Patch%20tests%20&xjob=e2e-kops)

### Since when has it been flaking?

[1/10/2025, 5:10:10 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-kind-conformance-parallel/1877628702888562688)
[1/10/2025, 11:40:02 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce-alpha-enabled-default/1877727102057320448)
[1/19/2025, 6:47:20 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/e2e-ci-kubernetes-e2e-al2023-aws-conformance-canary/1880914873404100608)
[1/20/2025, 7:25:30 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-containerd/1881467771536019456)
[1/22/2025, 5:57:09 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/1882170659614756864)

### Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-default

### Reason for failure (if possible)

```
{ failed [FAILED] failed to see replicas of test-rs in namespace replicaset-5368 scale to requested amount of 3: watch closed before UntilWithoutRetry timeout
In [It] at: k8s.io/kubernetes/test/e2e/apps/replica_set.go:552 @ 01/22/25 21:08:36.337
}
```

### Anything else we need to know?

N/A

### Relevant SIG(s)

/sig apps
cc: @kubernetes/release-team-release-signal
Repository: PowerToys
Issue: Your message on my computer: A problem has occurred - Report the error in the GitHub repository for PowerToys - 2025-01-23
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1.0

### Installation method

WinGet

### Running as admin

None

### Area(s) with issue?

Settings

### Steps to reproduce

Date: 23.01.2025 11:34:34
Exception:
System.Windows.Markup.XamlParseException: Set property

[2025-01-23.txt](https://github.com/user-attachments/files/18519964/2025-01-23.txt)

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

?

### Other Software

_No response_
Repository: godot
Issue: ColorPicker load/save swatches button issues
Labels: bug,topic:gui

### Tested versions

v4.4.beta1.official [d33da79d3]

### System information

Fedora Linux 40 (KDE Plasma) on Wayland - Wayland display driver, Single-window

### Issue description

ColorPicker load/save swatches button moves when clicked:

https://github.com/user-attachments/assets/e16bfa09-8fb9-492f-acb0-44ae6a18f443

The PopupMenu is also not behaving the same as other Popupmenus in the ColorPicker in RtL:

https://github.com/user-attachments/assets/b9a7b0cf-89d0-454a-955f-0d5997194274

There is also an issue in single window mode, where you can't close the menu by clicking on the button again:

https://github.com/user-attachments/assets/73ee9d81-e902-4d8a-9c38-975f2da58e21



### Steps to reproduce

Try any ColorPicker in the editor

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: revert deprecating Color withOpacity / opacity
Labels: engine,customer: crowd,c: proposal,P3,team-engine,triaged-engine

Read through the [code](https://github.com/flutter/flutter/blob/master/engine/src/flutter/lib/ui/painting.dart#L328-L332) and [migration guide](https://docs.flutter.dev/release/breaking-changes/wide-gamut-framework) but still having trouble supporting the end result here.

### Axioms

1. the vast majority of production codebases use .withOpacity(x), where x is 0.0–1.0 [1](https://github.com/search?type=code&q=.withOpacity%28)
1. the internal implementation is now .withOpacity(x) => .withAlpha((255.0*x).round());  [2](https://github.com/flutter/flutter/blob/master/engine/src/flutter/lib/ui/painting.dart#L328-L332)
1. the migration docs say to migrate .withOpacity(x) => .withValues(alpha: x); [3](https://docs.flutter.dev/release/breaking-changes/wide-gamut-framework#migrate-withopacity)
1. .withValues(alpha: x) is more verbose and less obvious than .withOpacity(x) [4](https://x.com/spiffyeehaw/status/1882459279564886111?s=46)
1. **designers communicate opacity as a percentage** from 0%–100% not an integer from 0–255 [5](https://help.figma.com/hc/en-us/articles/360041098433-Adjust-the-properties-of-an-image#:~:text=Click%20the%20thumbnail%20to%20open,by%20clicking%20the%20eye%20icon.)


### Questions

1. why doesn't the internal implementation match the migration docs
1. why does withAlpha(x) take an int 0–255 and withValues(alpha: x) take a double 0–1.0 
1. why does .withOpacity need to be deprecated at all


### Recommendations

1. unify alpha to a double or an int across all color methods
1. **undeprecate withOpacity** method
1. **undeprecate opacity** getter
Repository: material-ui
Issue: [Chip] Clickable area expands with `line-height`
Labels: bug 🐛,component: chip,ready to take

### Steps to reproduce

Steps:
1. Open this link to live example: https://stackblitz.com/edit/react-ryuspuxm?file=Demo.tsx
2. Click anywhere inside the black border box



### Current behavior

The chip is clicked even though the pointer is outside the Chip.

### Expected behavior

The chip should only be clicked when the pointer is inside the Chip.

### Context

Found in https://github.com/mui/mui-x/issues/16304

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 14.5
  Binaries:
    Node: 22.2.0 - ~/.nvm/versions/node/v22.2.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v22.2.0/bin/npm
    pnpm: 9.15.4 - ~/.nvm/versions/node/v22.2.0/bin/pnpm
  Browsers:
    Chrome: 131.0.6778.265
    Edge: 132.0.2957.115
    Safari: 17.5
  npmPackages:
    @mui/material: 6.4.1
```
</details>


**Search keywords**: Chip line-height
Repository: flutter
Issue: iOS Zoom is very sensitive
Labels: waiting for customer response,in triage

### Steps to reproduce

1. Open the camera on an iOS device
2. Pinch zoom

### Expected results

Zooming in using the pinch gesture functions the same as the native camera.

### Actual results

Zooming in using the pinch gesture is extremely sensitive & zooms in a lot, very quickly.

### Code sample

<details open><summary>Code sample</summary>

```dart
class CameraZoom {
  final double minimunCameraZoom;
  final double maximumCameraZoom;
  final double currentCameraZoom;
  final double zoomScale;
 
  CameraZoom({
    required this.minimunCameraZoom,
    required this.maximumCameraZoom,
    required this.currentCameraZoom,
    required this.zoomScale,
  });
 
  bool isZoomOut() {
    return zoomScale < 1.0;
  }
 
  double calculateZoomOut() {
    final zoomToApply = zoomScale < 1.0
        ? currentCameraZoom - (maximumCameraZoom / 200)
        : currentCameraZoom;
 
    return zoomToApply;
  }
 
  double calculateZoomIn() {
    final zoomToApply = zoomScale > 1.0
        ? currentCameraZoom + (maximumCameraZoom / 200)
        : currentCameraZoom;
 
    return zoomToApply;
  }
 
  double calculateZoomToApply() {
    double scale = isZoomOut() ? calculateZoomOut() : calculateZoomIn();
 
    if (scale <= minimunCameraZoom) {
      scale = minimunCameraZoom;
    } else if (scale >= maximumCameraZoom) {
      scale = maximumCameraZoom;
    }
 
    return scale;
  }
}
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

https://github.com/user-attachments/assets/4c0f94de-2daf-45be-9b89-95abf9f86b36

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: flutter
Issue: [iOS][PlatformView] Conflict between Flutter ListView scrolling and PlatformView
Labels: platform-ios,framework,f: scrolling,a: platform-views,has reproducible steps,team-ios,found in release: 3.27,found in release: 3.29

### Steps to reproduce

This example highlights a conflict between Flutter's scrolling and the native platform view's `TextView` scrolling and text selection. Specifically, text selection in the TextView only works when `ListView` scrolling is disabled using physics: NeverScrollableScrollPhysics(). This limitation affects the usability of TextView and could also impact other types of platform views.
**Note:** This issue occurs only on iOS.

### Expected results

Users should be able to select text even when the TextView is inside a scrollable widget.

### Actual results

User cannot select text when TextView is inside a scrollable Widget and scrolling is enabled.

### Code sample

[flutter_native_text_view_sample_main.zip](https://github.com/user-attachments/files/18545585/flutter_native_text_view_sample_main.zip)


<details open><summary>Code sample</summary>

**Run this ready code:** 
Screen has 3 Texts elements:
- the first one is flutter widget 
- the other two are platform views. 
Try to select text, it works with flutter widget but doesn't work with platform views. If scrolling is disable, text selection works also with platform views. After testing we think there is a conflict at low level.
Sample here:


</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

-  Flutter's SelectableText: Text selection works as expected.
- Native Platform View: Text selection is hindered by scrolling functionality.


https://github.com/user-attachments/assets/f7abf303-97b7-4d74-89cc-5ce17426dcae


</details>



### Flutter Doctor output

<details open><summary>Doctor output</summary>

```Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel [user-branch], 3.24.5, on macOS 14.2.1 23C71 darwin-arm64, locale en-IT)
    ! Flutter version 3.24.5 on channel [user-branch] at /Users/delfme/Development/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] Connected device (4 available)
    ! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area
      network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources


```

</details>
Repository: node
Issue: [v20.x] `parallel/test-buffer-tostring-range` fails on SmartOS
Labels: smartos,flaky-test,v20.x

### Test

parallel/test-buffer-tostring-range

### Platform

SmartOS

### Console output

```console
03:13:42 not ok 177 parallel/test-buffer-tostring-range
03:13:42   ---
03:13:43   duration_ms: 5550.52900
03:13:43   severity: fail
03:13:43   exitcode: 1
03:13:43   stack: |-
03:13:43     node:internal/buffer:961
03:13:43         super(bufferOrLength, byteOffset, length);
03:13:43         ^
03:13:43     
03:13:43     RangeError: Array buffer allocation failed
03:13:43         at new ArrayBuffer (<anonymous>)
03:13:43         at new Uint8Array (<anonymous>)
03:13:43         at new FastBuffer (node:internal/buffer:961:5)
03:13:43         at Function.alloc (node:buffer:395:10)
03:13:43         at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos23-x64/test/parallel/test-buffer-tostring-range.js:107:28)
03:13:43         at Module._compile (node:internal/modules/cjs/loader:1468:14)
03:13:43         at Module._extensions..js (node:internal/modules/cjs/loader:1547:10)
03:13:43         at Module.load (node:internal/modules/cjs/loader:1287:32)
03:13:43         at Module._load (node:internal/modules/cjs/loader:1103:12)
03:13:43         at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:180:12)
03:13:43     
03:13:43     Node.js v20.18.3
03:13:43   ...
```

### Build links

- https://ci.nodejs.org/job/node-test-commit-smartos/58746/console

### Additional information

It's blocking v20 release https://github.com/nodejs/node/pull/56699

@nodejs/platform-smartos
Repository: vscode
Issue: Braces colouring is off inside Dart multiline strings
Labels: triage-needed

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.96.4
- OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:

1. Open an empty folder with nothing inside
2. Disable all extensions
3. Add a new `file.dart` file
4. Write the following to it:

```dart
var myString = '''
Here is a string with ()
and some other examples {like (this)}.
''';
```

5. See the braces colouring (possibly, more on that later)

![Image](https://github.com/user-attachments/assets/87fbf68b-4dbb-43b0-bbba-f070e35ceab5)

6. Change the string to be raw by adding `r` before the opening `'''`:

![Image](https://github.com/user-attachments/assets/b70b8bbc-ad07-43a8-8eee-a2216a434a4f)

I've asked @DanTup to verify this but with the same VS Code version he could not see this behaviour on his machine. 

If I close the editor (file opened) and reopen it (even removing `r` now) I see the braces colouring flash and go back to string colour.

His guess is that there may be some other racing here as https://github.com/microsoft/vscode/issues/230498. Same machine, a Samsung Galaxy Book Pro. To note we had problems with this colouring previously at https://github.com/microsoft/vscode/issues/209435 for Dart and we still have this opened for Python https://github.com/microsoft/vscode/issues/225179.

I can't reliably reproduce this (besides flashing) again on this _exact_ folder/file (unfortunatelly). But I saw this behaviour previously on Dart projects and this is an empty folder with only that file inside.
Repository: pytorch
Issue: [custom ops] [2.7 nightly] custom ops with typing.List breaks when importing annotations from future
Labels: high priority,triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

### 🐛 Describe the bug

The latest nightly version does not support `typing.List` in combination with `from __future__ import annotations`, but requires the use of `list`. While I agree that using `list` is better and more modern, this introduces a breaking change that makes it difficult to keep the custom ops working both on older and newer pytorch versions.

This change was introduced 5 days ago with this commit: https://github.com/pytorch/pytorch/commit/a79100ab11e09473d7456bc02de36de629d9db62#diff-09dd038b7467c407d31c7feb905906037d68d4a419a714bb1f56cee93976de39

My problem with that is: Using List[T] as annotation now gives me the following error:
```
Traceback (most recent call last):
  File "/weka/mathias/kuma/.venv/lib/python3.12/site-packages/torch/_library/infer_schema.py", line 65, in convert_type_string
    return eval(annotation_type)
           ^^^^^^^^^^^^^^^^^^^^^
  File "<string>", line 1, in <module>
NameError: name 'List' is not defined. Did you mean: 'list'?
```

I could simply change all annotations for `list`, but then it doesn't work anymore with older pytorch versions, requring to create a complete clone of the custom op module.
I already tried using typing Aliases: use `type List = list if version... else type List = typing.List`, but that doesn't work either, because the types are evaluated as a raw string - using capital L in the beginning doesn't work.

**Turns out that typing.List only fails when importing future annotations.** 
So, not sure if you want to fix, but since it did work before and would only require reverting one line of code, I wanted to open this issue to discuss if you want to support this case or not.
My workaround now was to remove the `from __future__ import annotations` from these files and change some types.

The line that need to be changed
https://github.com/pytorch/pytorch/blob/a79100ab11e09473d7456bc02de36de629d9db62/torch/_library/infer_schema.py#L6

to the state before this commit:
https://github.com/pytorch/pytorch/commit/a79100ab11e09473d7456bc02de36de629d9db62#diff-09dd038b7467c407d31c7feb905906037d68d4a419a714bb1f56cee93976de39

Use this script to reproduce the error:

```
from __future__ import annotations

import torch
from typing import List

@torch.library.custom_op("test::custom_op_list", mutates_args=())
def my_custom_op(
    x: torch.Tensor,
) -> List[torch.Tensor]:
    return [torch.randn_like(x)]
```



### Versions

Pytorch 2.7.0.dev20250122+cu124
Python 3.12.6
Ubuntu 20.04

(collect_env.py crashes when using uv)

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @bdhirsh @yf225
Repository: vscode
Issue: We were unable to automatically build your code. Please replace the call to the autobuild action with your custom build steps. We were unable to automatically build your code. Please change the build mode for this language to manual and specify build steps for your project. See https://docs.github.com/en/code-security/code-scanning/troubleshooting-code-scanning/automatic-build-failed for more information. Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.20.1/x64/codeql/codeql database trace-command --use-build-mode --working-dir /home/runner/work/todo/todo -O=cpp.trap.cache.dir=/home/runner/work/_temp/trapCaches/cpp -O=cpp.trap.cache.bound=1024 -O=cpp.trap.cache.write=true /home/runner/work/_temp/codeql_databases/cpp". Exit code was 2 and error was: A fatal error occurred: Exit status 1 from command: [/opt/hostedtoolcache/CodeQL/2.20.1/x64/codeql/cpp/tools/autobuild.sh]. See the logs for more details.
Labels: info-needed,triage-needed

https://github.com/latamexiovas10/todo/actions/runs/12929318719/job/36058459946#step:7:161
Repository: react
Issue: CSP violation
Labels: Status: Unconfirmed

As per guidelines from security team, framework team wants to enable Content Security Policy (CSP ) at the gateway layer to enforce good web-security practice. In 2412, framework team evaluated the impact of enabling lenient CSP at the gateway layer.  As part of this exercise, we enabled CSP in the gateway layer in Report only mode and collected all CSP violations. we found that 

node_modules/react-dom/cjs/react-dom-server-legacy.browser.development.js
node_modules/react-dom/cjs/react-dom-server-legacy.browser.production.min.js
node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js
node_modules/react-dom/cjs/react-dom-server.browser.development.js
node_modules/react-dom/cjs/react-dom-server.node.development.js
node_modules/react-dom/umd/react-dom-server-legacy.browser.development.js
node_modules/react-dom/umd/react-dom-server-legacy.browser.production.min.js
node_modules/react-dom/umd/react-dom-server.browser.development.js


is using eval/dynamic function which is flagged as CSP violation. To fix this, we need to replace usage of eval/dynamic function with something safe.
Repository: vscode
Issue: Allow multiple lines per StickyScroll entry
Labels: feature-request,editor-sticky-scroll

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Some coding conventions mandate opening/closing braces to be on a separate line. For example here's a piece of `PostgreSQL` code:
<details>
  <summary>Wall of C code</summary>

```C
RelFileNumber
GetNewRelFileNumber(Oid reltablespace, Relation pg_class, char relpersistence)
{
	RelFileLocatorBackend rlocator;
	char	   *rpath;
	bool		collides;
	ProcNumber	procNumber;

	/*
	 * If we ever get here during pg_upgrade, there's something wrong; all
	 * relfilenumber assignments during a binary-upgrade run should be
	 * determined by commands in the dump script.
	 */
	Assert(!IsBinaryUpgrade);

	switch (relpersistence)
	{
		case RELPERSISTENCE_TEMP:
			procNumber = ProcNumberForTempRelations();
			break;
		case RELPERSISTENCE_UNLOGGED:
		case RELPERSISTENCE_PERMANENT:
			procNumber = INVALID_PROC_NUMBER;
			break;
		default:
			elog(ERROR, "invalid relpersistence: %c", relpersistence);
			return InvalidRelFileNumber;	/* placate compiler */
	}
....
}
```
</details>

The StickyScroll makes reading this kind of code really nice, but sometimes there are extremely long `if` statements and having those Stick is really nice. However the `outlineModel` doesn't really care about the `if` statements. The next best alternative would be the `foldingProviderModel`, but that doesn't work well with this coding convention. The Sticky looks like this:

```C
{
    {
        {
             /* some code here */
...
```

And surely if one were to fold the opening braces to the same line, it'd look way more useful:
```C
GetNewRelFileNumber(Oid reltablespace, Relation pg_class, char relpersistence){
	switch (relpersistence){
            /* you are here */
```

## Feature:
Allow including "lines before" and "lines after" into the sticky scroll, or a hack to "collapse braces" or something, although that is too language specific, unfortunately.
Repository: react
Issue: [React 19] Without extra Generic Type to useActionState hook
Labels: React 19

## Summary

Hi everyone!

I have a question about the types from the new hook 'useActionState'.

Actually, I'm working on a project and I need some extra types for my action function

![A snippet of types from React 19v](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bxewm33ed1v9kqmgceq8.png)

Why don't we have an extra Generic Type to return from the action? Does the return really need to be equal to the initial state?

In a real use case, the return from the action can be different from the entry data, such as an error object like:


```js

// INPUT DATA
{
  email: 'user@email.com'  
}

// OUTPUT DATA
{
  email: {
    value: 'user@email.com'  
    state: {
      error: {
         message: null
      }
    }
  }
}
```

**Reference**

- https://react.dev/reference/react/useActionState
- https://react.dev/blog/2024/12/05/react-19#whats-new-in-react-19

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->