sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [feat] Enhance Tauri Tray Menus: Support Icons for Submenus and Checkable Items
Labels: type: feature request

### Describe the problem

The tray menu system has limitations in supporting icons for menu items. Currently:

- Menu items cannot have icons if they include submenus.
- Submenu items themselves cannot have icons.
- Checked menu items cannot display icons.

These limitations restrict the ability to create visually rich and user-friendly tray menus. On macOS, applications like Klack demonstrate that all these features are possible, enhancing the overall user experience.

<img width="391" alt="image" src="https://github.com/user-attachments/assets/3bbb66a6-7f52-4ed2-b2a3-44a400cab615">

### Describe the solution you'd like

I’d like Tauri v2 to enhance its tray menu functionality by:

- Supporting icons for menu items that include submenus.
- Allowing submenu items to have icons.
- Enabling icons for checkable menu items.

This functionality would allow developers to build visually consistent and feature-complete tray menus, leveraging the design capabilities of macOS.


### Alternatives considered

1. Custom tray menu implementations using native bindings or platform-specific workarounds, which significantly increase development complexity.

2. Accepting the current limitations and avoiding icons in menus, which compromises design and usability.
Both alternatives are less than ideal compared to having first-class support directly in Tauri.

### Additional context

_No response_
Repository: kubernetes
Issue: internal convert cause patchMergeKey lost
Labels: kind/bug,needs-sig,needs-triage

### What happened?

I have a deployment, which have imagePullSecrets issue.
At revision 1:
```yaml
imagePullSecrets:
- name: test
```
At revision 2:
We update it to
```yaml
imagePullSecrets:
- name: test
- name: ""
```
And k8s accept it, and it become 
```yaml
imagePullSecrets:
- name: test
- {}
```
However, any update after it failed with `error: map: map[] does not contain declared merge key: name`
We want to delete it by `kubectl edit` to remove its `{}` line, but also failed with same error.

This seems to happen in k8s convert strategy rather than patchStrategy. Help wanted.

### What did you expect to happen?

Deployment should become
```yaml
imagePullSecrets:
- name: test
- name: ""
```
Also, any update after it should succees.

### How can we reproduce it (as minimally and precisely as possible)?

Edit any deployment so you can produce.

### Anything else we need to know?

_No response_

### Kubernetes version

Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.19.9-20
WARNING: version difference between client (1.28) and server (1.19) exceeds the supported minor version skew of +/-1

Its a forked version, but should produce in community version.

### Cloud provider

None, we build it in virtual machines.

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: ant-design
Issue: Menu does not auto-scroll when an item at the bottom is expanded
Labels: Inactive,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/inline-menu-antd-5-22-2-forked-yfydvh?file=%2Findex.html)

### Steps to reproduce

Create a Menu component with several items, ensuring that some items are positioned at the bottom of the screen.
Click on a main menu item that is located at the bottom of the screen to expand its submenu.
Observe that the submenu expands, but the screen does not scroll down to display the expanded submenu.

### What is expected?

When a main menu item at the bottom of the screen is clicked and its submenu expands, the screen should automatically scroll down to display the expanded submenu.

### What is actually happening?

The submenu expands, but the screen does not scroll down, making it appear as though the submenu has not opened.

| Environment | Info |
| --- | --- |
| antd | 5.22.2 |
| React | 18.2.0 |
| System | Windows 11 |
| Browser | Google Chrome 130.0.6723.70 |

---
I am experiencing an issue with the Ant Design (antd) Menu component. When I click on a main menu item that is located at the bottom of the screen, the submenu expands, but the screen does not automatically scroll down to show the expanded submenu. As a result, it appears as though the submenu has not opened, which can be confusing for users.This issue affects the user experience as it can be confusing for users who may not realize that the submenu has expanded. An automatic scroll to the expanded submenu would improve usability.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: tensorflow
Issue: When using `tf.math.log1p` and NumPy's `np.log1p` with the same complex input, the outputs are inconsistent.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

2.17.1

### Custom code

Yes

### OS platform and distribution

Ubuntu 22.04.3

### Mobile device

_No response_

### Python version

3.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

TensorFlow's `tf.math.log1p` produces inconsistent results with NumPy's `np.log1p` for complex inputs containing `inf`, such as `[inf+0.j, 0+inf.j, inf+inf.j]`. TensorFlow outputs `[inf+0.j, nan+nanj, nan+nanj]`, while NumPy returns `[inf+0.j, inf+1.57079633j, inf+0.78539816j]`.

### Standalone code to reproduce the issue

```shell
python
import tensorflow as tf
import numpy as np

test_input = tf.constant([complex(float('inf'), 0), complex(0, float('inf')), complex(float('inf'), float('inf'))], dtype=tf.complex128)

# TensorFlow computation
with tf.device('/CPU:0'):
    cpu_out = tf.math.log1p(test_input)

# NumPy computation
numpy_out = np.log1p(test_input.numpy())

print(f"CPU Output: {cpu_out}")
print(f"NumPy Output: {numpy_out}")
```


### Relevant log output

```shell
CPU Output: [inf +0.j nan+nanj nan+nanj]
NumPy Output: [inf+0.j         inf+1.57079633j inf+0.78539816j]
```
Repository: rust
Issue: track whether a non-coherence `TypingMode`  has been used to reuse cache entries
Labels: C-feature-request,T-types

see the WIP branch https://github.com/lcnr/rust/tree/typing-mode-is-coherence.

It is now fairly straightforward to track whether evaluation relied on the exact typing mode. finishing this work should result in a reasonable perf improvement
Repository: react-native
Issue: ScrollView's scrollToEnd scrolls too far on android
Labels: Issue: Author Provided Repro,Resolution: PR Submitted,Platform: Android,Component: ScrollView

### Description

ScrollView's `scrollToEnd` method gives different results on iOs and Android.

Expected behaviour:
ScrollView's `scrollToEnd` method should function consistently across platforms. Ideally The view should scroll until the bottom of the content reaches the bottom of the view.

Actual behaviour:
On iOs the view tries to scroll until the bottom of the content reaches the bottom of the view.
On Android the view tries to scroll until the bottom of the content reaches the top of the view.

This is especially annoying if you add content while the view is scrolling, as it then scrolls too far, or if you have an animation of content being added to slide in from the bottom.

### Steps to reproduce

1. Open the provided snack on Android
2. Press the button labeled "Press me!"
3. The view scrolls until element "Test 50" reaches the top of the screen
4. Open the provided snack on iOs
5. Press the button labeled "Press me!"
6. The view scrolls until element "Test 49" reaches the bottom of the screen

### React Native Version

0.76.3

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.7
  CPU: (10) arm64 Apple M1 Pro
  Memory: 124.23 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.19
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman:
    version: 2024.09.16.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12550806
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 18.0.2.1
    path: /Users/chriscoerdes/.jenv/shims/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.1
    wanted: 15.0.1
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.3
    wanted: 0.76.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://github.com/coerdes-chris/react-native-scrollview

### Screenshots and Videos


https://github.com/user-attachments/assets/ad2a0bcd-4c59-4291-8891-9f2dfbd1d13f
Repository: kubernetes
Issue: DRA: mark devices as unhealthy in ResourceSlice
Labels: sig/node,kind/feature,needs-triage,wg/device-management

### What would you like to be added?

The current method of preventing allocation of an unhealthy device is to remove the device from the ResourceSlice. There's an inherent race here between that and the scheduler seeing the update, but that's unavoidable.

Some way of marking the device as unhealthy and/or unavailable would be nicer.

### Why is this needed?

Use cases:

- Users can see all devices which exist in the cluster, including those which are unhealthy. Ideally there's also some information about *why* they are unhealthy.
- A system admin may want to take a device offline for maintenance. The driver doesn't (and shouldn't) need to be aware of that.
- A monitoring solution separate from the driver detects that the device is unhealthy or not performing as expected.
Repository: bitcoin
Issue: RFC: support for writing UTXO set dump (`dumptxoutset` RPC) to a named pipe
Labels: Feature

### Please describe the feature you'd like to see added.

While the primary obvious use-case for the `dumptxoutset` RPC is to create AssumeUTXO snapshots (to be distributed and loaded on newly created nodes via the `loadtxoutset` RPC later), it can also be useful as input for external tooling like converters to other UTXO set formats, e.g. https://github.com/bitcoin/bitcoin/pull/27432. For those, the intermediate step of writing a >10GB file to disk and then reading it again is wasteful and annoying, as it consumes both more time and space than necessary. By supporting writing to a [named pipe](https://en.wikipedia.org/wiki/Named_pipe#In_Unix), the output data could be fed directly into another process instead. Thanks to the UNIX "everything is a file" philosophy, no logic changes in the tooling are even needed -- the reader only sees an input stream and doesn't notice or care if the input file represents an actual physical file on disk or if the data is generated on-the-fly from another process.

Currently needed steps for external tools:
1. call `dumptxoutset` to create utxo.dump (>10GB on mainnet)
2. call external tool with utxo.dump as input (run only after step 1 is finished)
3. delete utxo.dump

Needed steps for external tools with named pipe support:
1. create a named pipe utxo.pipe (e.g. via https://linux.die.net/man/3/mkfifo)
2. call `dumptxoutset` to write to utxo.pipe
3. call external tool with utxo.pipe as input (run in *parallel* to step 2)
4. delete utxo.pipe

I've tried this yesterday and it works as expected with minimal changes (see proposed solution below). Will push the branch later with concrete instructions, if people feel that this is worthwhile to support.

### Is your feature related to a problem, if so please describe it.

_No response_

### Describe the solution you'd like

The `dumptxoutset` call only needs two minor behaviour modificiations. If the passed `path` is a named pipe (trivially detectable via C++ standard library routine [std::filesystem::is_fifo](https://en.cppreference.com/w/cpp/filesystem/is_fifo)), then:
* don't error if the file already exists
* don't create a temporary file with `.incomplete` suffix, but write directly into the specified path

### Describe any alternatives you've considered

_No response_

### Please leave any additional context

_No response_
Repository: next.js
Issue: [Windows] Server-side debugger doesn't stop in breakpoints after v15.0.3-canary.7
Labels: bug,Turbopack

### Link to the code that reproduces this issue

https://github.com/emilioestebanez/next-15-issues

### To Reproduce

1. Open in VSCode
2. Go to `Run and Debug` and execute the `Next.js: debug server-side`
3. Set a breakpoint in `src/app/page.tsx`
4. Visit http://localhost:3000

You'll see that the debugger doesn't stop in the breakpoint in Windows.

Now, if you go to `package.json` and remove `--turbopack` from the `dev` script and try the steps above again, you'll see that the debugger is able to stop in the breakpoint correctly.

This happens after next@15.0.3-canary.7

### Current vs. Expected behavior

I expect the breakpoint to stop with and without `--turbopack` enabled.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 65208
  Available CPU cores: 20
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I think this is the cause of the issue:
https://github.com/vercel/next.js/pull/71984
Repository: kubernetes
Issue: DRA: competition between schedulers + allocators
Labels: sig/scheduling,kind/feature,needs-triage,wg/device-management

### What would you like to be added?

At the moment, DRA uses the approach that one scheduler instance "owns" all resources on a node or available for a node (in the case of network-attached devices). This is the same approach that is used for other resources. It enables faster scheduling because allocation can happen without coordination with other entities.

This approach breaks down when there are multiple schedulers in the cluster such that each scheduler instance is responsible for its own subset of the nodes ("sharding") and there are network-attached devices that are available for more than one set of nodes.

Also, sometimes users run additional schedulers for the same nodes as the system scheduler. While that is already problematic regarding CPU and memory, with devices it might be even worse.

/sig scheduling
/wg device-management

### Why is this needed?

For more advanced cluster setups.
Repository: TypeScript
Issue: Bloomberg feedback for 5.7
Labels: Discussion

### Acknowledgement

- [x] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

We evaluated the 5.7 release and it seems to be a low impact release for us. We only found one issue, which we reported:

| # |                                 Change                                  |      Affects     | Release notes | Packages affected|  Reported As |
|---|-------------------------------------------------------------------------|------------------|---------------|------------------|--------------|
|  1|        Index signature added to classes that inherit an any typed class | Declaration Emit | Not Announced |              <1% | [#60383](https://github.com/microsoft/TypeScript/issues/60383) |
|  2|                                       Minor changes to declaration text | Declaration Emit | Not Announced |              <1% |              |

### Minor changes to declaration text

These seem to be related to isolated declaration emit alignment with external tools. The changes were in a limited number of places and did not impact the correctness of the declarations (some string delimiters changed, some types got preserved as `typeof x` instead being inlined, some recursive types got expanded one level deeper). 

Examples:

```diff
-  get sourceFn(): SourceFnArgs<TParams>['sourceFn'];
+  get sourceFn(): SourceFnArgs<TParams>["sourceFn"];

+ readonly Source: any;
- readonly Source: typeof LazySource.default;
```
Repository: kubernetes
Issue: DRA drivers: helper code for checking device allocations
Labels: sig/node,kind/feature,needs-triage,wg/device-management

### What would you like to be added?

A DRA driver has to check in NodePrepareResources whether the devices are a) already prepared for other claims and b) really currently available.

If so, it has to refuse to prepare them again. This is a sanity check that acts as last line of defense against unintended concurrent usage of a device (case a) or race conditions. DRA tries hard to avoid such situations, but at least the ["device became unhealthy"](https://github.com/kubernetes/kubernetes/issues/128979) is inherently racy. Allocating the same device for different claims could be the result of a bug or allocation by different schedulers without [coordination](https://github.com/kubernetes/kubernetes/issues/128980#issuecomment-2500948711).

DRA driver authors might forget to implement this check. Perhaps we can move it into [k8s.io/dynamic-resource-allocation/kubeletplugin](https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/dynamic-resource-allocation/kubeletplugin) with such an API change that the driver authors are forced to do something?


### Why is this needed?

Higher quality of DRA drivers.
Repository: PowerToys
Issue: Extend Quick Accent to space and dash
Labels: Needs-Triage

### Description of the new feature / enhancement

Use Quick Accent (PowerToys) to get the possibility to insert any kind of space or dash available (variable, fix, unbreakable, quadratin, half quadratin, quarter quadratin for the spaces, and all dashes used in typography).

### Scenario when this would be used?

Each time you compose a text with the need to insert a specific dash or space.

### Supporting information

the way Quick Accent is working for special accentuation seems to perfectly fit to this use. It just add a precious typographic ressource. Thank for this excellent set of utility!
Repository: PowerToys
Issue: New+ Folder "Bookmarks"
Labels: Needs-Triage

### Description of the new feature / enhancement

In the new+ context menu, it would be amazing to expand into subfolders, similar to the the way that you can expand folders on browser bookmarks.
Perhaps a specific set of characters at the start of a folder in the templates could indicate an expandable folder?
Thank you in advance for consideration of this feature!

### Scenario when this would be used?

This would allow you to better categorize template folders and or files, and have the ability to manage a large list of templates. 

### Supporting information

_No response_
Repository: vscode
Issue: Dynamically change run buttons to debug when breakpoints are placed
Labels: feature-request

In a recent user study, we observed a participant struggling to discover how to run in debug mode. After they placed breakpoints in their testing code, they would hit the run button next to their test expecting it to start the debugger and hit the breakpoint. It would be nice if when a user adds a breakpoint, the run button (whether it's for run file or for run test) would start the debugger 

cc/ @luabud 

<!-- ⚠️⚠️ 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. -->
Repository: vscode
Issue: Provide entry point to run and debug view in the debug console
Labels: feature-request,debug-console

In a recent user study, we observed participants clicking through the debug console hoping something would populate there on run. This might be a good entry point for the Run and Debug panel where they could configure the debugger for their use case rather than saying "Please start a debug session to evaluate expression" since we noticed this messaging wasn't helpful to get them setup with the debugger. Perhaps we could link to open the Run and Debug panel or provide similar buttons as the panel to create a config and run and debug. 

cc/ @luabud 

<!-- ⚠️⚠️ 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. -->
Repository: langchain
Issue: DOC: Broken API Reference Link for Google Vertex AI Embeddings
Labels: 🤖:docs

### URL

https://python.langchain.com/docs/integrations/text_embedding/google_vertex_ai_palm/#credentials

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

The API reference link for the Google Vertex AI Embeddings feature in LangChain's documentation is broken and leads to a "**Page Not Found**" error.

**Location of the broken link:**
The issue appears in the section that mentions:
For detailed documentation on Google Vertex AI Embeddings features and configuration options, please refer to the **API reference**.

The hyperlink here does not resolve to a valid page.

**![Screenshot 2024-11-26 214525](https://github.com/user-attachments/assets/1da3d4a8-a43f-48a5-8354-d94ed5745e6e)**
The link should direct users to the relevant API reference page that provides detailed documentation on the Google Vertex AI Embeddings feature.

**Current behavior:**

The link currently leads to a "Page Not Found" error, which hinders users from accessing detailed API reference material.

### Idea or request for content:

Please update the broken link to point to the correct API(https://python.langchain.com/api_reference/index.html) reference page or provide an explanation in the documentation if the reference is unavailable.