sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: DLPack with Int32 tensor on the GPU: inconsistent eager mode / graph mode / XLA
Labels: stat:awaiting tensorflower,type:bug,comp:apis,comp:gpu

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

v1.12.1-117097-gecf05620570 2.19.0-dev20241016

### Custom code

No

### OS platform and distribution

Linux Ubuntu 22.04

### Mobile device

_No response_

### Python version

3.12

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Hello,

I realize that `int32` is a special dtype in TensorFlow for historical reasons. It seems that the handling of GPU int32-typed tensors has evolved over time.

Currently, the `device` field of a tensor created with:
```py
with tf.device('gpu'):
    x = tf.constant([0,1,2], tf.int32)
```
*does* indicate it's a GPU tensor: `/job:localhost/replica:0/task:0/device:GPU:0`.

However, when exporting and re-importing it via DLPack, it comes back as a CPU tensor.
There even seems to be a unit test validating this:
https://github.com/tensorflow/tensorflow/blob/d3de971a7348ecaefdbb920e580c37ebde10d780/tensorflow/python/dlpack/dlpack_test.py#L75-L78


However, @jhoydis found that this is *not* consistent between modes. In particular, if the tensor goes through an XLA-compiled function, it will correctly live on the GPU even after a round-trip through DLPack. (See reproducer below).

Would it please be possible to revisit this behavior, so that **exporting an int32 GPU tensor via DLPack does result in a GPU DLPack capsule in all modes, not just XLA?**

### Standalone code to reproduce the issue

```shell
import tensorflow as tf


def f_eager(x):
    return x
f_graph = tf.function()(f_eager)
f_xla = tf.function(jit_compile=True)(f_eager)


with tf.device('gpu'):
    x = tf.constant([0,1,2], tf.int32)
    print("Original tensor:", x.device)

    dlcapsule = tf.experimental.dlpack.to_dlpack(x)
    x_ = tf.experimental.dlpack.from_dlpack(dlcapsule)
    print("Default:", x_.device)

    dlcapsule = tf.experimental.dlpack.to_dlpack(f_eager(x))
    x_ = tf.experimental.dlpack.from_dlpack(dlcapsule)
    print("Eager:", x_.device)

    dlcapsule = tf.experimental.dlpack.to_dlpack(f_graph(x))
    x_ = tf.experimental.dlpack.from_dlpack(dlcapsule)
    print("Graph:", x_.device)

    dlcapsule = tf.experimental.dlpack.to_dlpack(f_xla(x))
    x_ = tf.experimental.dlpack.from_dlpack(dlcapsule)
    print("XLA:", x_.device)
```


### Relevant log output

```shell
Original tensor: /job:localhost/replica:0/task:0/device:GPU:0
Default: /job:localhost/replica:0/task:0/device:CPU:0
Eager: /job:localhost/replica:0/task:0/device:CPU:0
Graph: /job:localhost/replica:0/task:0/device:CPU:0
XLA: /job:localhost/replica:0/task:0/device:GPU:0
```
Repository: rust
Issue: `IntErrorKind` should derive `Copy` and `Hash`
Labels: T-libs-api,C-feature-request

When including std errors as part of custom types, I've noticed that [`IntErrorKind`](https://doc.rust-lang.org/std/num/enum.IntErrorKind.html) does not derive the `Copy` or the `Hash` traits, and I think it most probably should, since it would make it easier to propagate and embed it. For example [`IoErrorKind`](https://doc.rust-lang.org/std/io/enum.ErrorKind.html) does in fact derive them.
Repository: material-ui
Issue: After applying high contrast themes, there is no differentiation between selected and non-selected control in Windows.
Labels: bug 🐛,waiting for 👍,component: button,ready to take,platform: windows

### Steps to reproduce

Link to live example: (required)
https://mui.com/material-ui/react-button/

Prerequisites:
Turn on High Contrast Aquatic/Desert Modes (Go to settings->Contrast Themes->High Contrast aquatic/Desert Themes).

Steps:
1. Open URL-https://mui.com/material-ui/react-button/
2. "React Material UI." page will get Open.
3. Press Tab key to navigate to left navigation section and select radio group option.
4. Press Tab key to "Customization" section.
5. Verify with tab key whether after applying high contrast themes, there is no differentiation between selected and non-selected radio button control.

### Current behavior

After applying high contrast themes, there is no differentiation between selected and non-selected radio buttons.

### Expected behavior

After applying high contrast themes, there should be differentiation, or border should be present on selected radio button.

### Context

_No response_

### Your environment

<a data-no-markdown-link="true" class="MuiTypography-root MuiTypography-inherit MuiLink-root MuiLink-underlineNone app-drawer-active css-1oy3mdg" style="--_depth:1;--_expandable:0" href="/base-ui/react-radio-group/">Radio Group<div class="MuiChip-root MuiChip-filled MuiChip-sizeMedium MuiChip-colorDefault MuiChip-filledDefault css-ey7mmr"><span class="MuiChip-label MuiChip-labelMedium css-s01idy">Planned</span></div></a>

**Search keywords**: contrast themes, Radio group
Repository: ant-design
Issue: ColorPicker with presets doesn't correctly recognizes screen boundaries
Labels: Inactive,unconfirmed

### Reproduction link

[https://ant.design/components/color-picker#color-picker-demo-presets](https://ant.design/components/color-picker#color-picker-demo-presets)

### Steps to reproduce

- Open the documentation page
- Scroll to the position shown on the screenshot
- Open color picker
<img width="681" alt="image" src="https://github.com/user-attachments/assets/a85efbcc-5409-478f-81cf-b9ed05f45848">



### What is expected?

The color pickers understands some of presets go beyond the screen and changes the placement of the popup.

### What is actually happening?

Some presets are hidden

| Environment | Info |
| --- | --- |
| antd | 5.21.4 |
| React | 18 |
| System | Mac OS |
| Browser | Chrome |

---
In this particular case of documentation page, it's possible to scroll the page a little. However, in some other cases the scroll might not be available

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: electron
Issue: "second-instance" is not triggered with Deep Links when running with admin privileges
Labels: platform/windows,bug :beetle:,has-repro-gist,33-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

33.0.0

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 11

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

When using standard [Deep Links](https://www.electronjs.org/docs/latest/tutorial/launch-app-from-url-in-another-app) with elevated permission on the app, whether it's with an administrator terminal when using a development local server or when running the app as administrator, the `app.on("second-instance")` should be triggered when using the specified protocol url.

### Actual Behavior

`app.on("second-instance")` is not being triggered when running a [Deep Link](https://www.electronjs.org/docs/latest/tutorial/launch-app-from-url-in-another-app) url protocol when having administrator privileges. This behaviour is occurring when using a development local server with an elevated terminal and also when building into production and running the app as administrator (tested with electron-forge makers: Wix and Squirrel).

You can test it by just adding a standard Deep Link following the official documentation [here](https://www.electronjs.org/docs/latest/tutorial/launch-app-from-url-in-another-app)



### Testcase Gist URL

https://gist.github.com/gabriel-demoura-IMTF/9d0b4805ba0a5d26b1dded119d0557bb

### Additional Information

An issue as been created 2 years ago, but it has been closed and asked to create a new one if still occurring in newer versions: https://github.com/electron/electron/issues/35681
Repository: terminal
Issue: Broadcast Exit to multiple panes crash
Labels: Needs-Repro,Issue-Bug,Area-UserInterface,Severity-Crash,Product-Terminal

### Windows Terminal version

1.22.2702.0_x64

### Windows build number

10.0.22631.4317

### Other Software

_No response_

### Steps to reproduce

1. Open the Windows Terminal Preview
2. Create a second pane.
3. Toggle broadcast input to all panes (you should now be able to type in all panes)
4. Press Ctrl + D or type "exit"
5. the terminal crashes, even if you have other tabs open.

### Expected Behavior

I'd expect it to exit out of the tab, so that if you have other tabs you can return to using them.


### Actual Behavior

Upon exiting with multiple panes at the same time, it crashes and the program shuts down.
Repository: pytorch
Issue: Crash on Apple MPS (M2) when inverting large matrix
Labels: high priority,module: crash,triaged,module: third_party,module: linear algebra,module: mps

### 🐛 Describe the bug

Matrix inversion on MPS fails for matrices larger than 1024. Below is a minimal example that includes a working and non-working situation. The non-working situation throws error: ```/AppleInternal/Library/BuildRoots/5a8a3fcc-55cb-11ef-848e-8a553ba56670/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShaders/MPSCore/Types/MPSNDArray.mm:118: failed assertion `[MPSNDArrayDescriptor sliceDimension:withSubrange:] error: dimension index (2) not within number of dimensions (2)```.

```python
import torch

device = torch.device("mps")

###########################################
############# WORKING #####################
###########################################
n = 1024
# generate random positive semi-definite matrix
A = torch.rand(n, n, device=device)
A = torch.mm(A, A.t())
# invert
print("Before matrix inversion with n=1024")
V_pi = torch.linalg.inv(A)
print("After matrix inversion with n=1024")

###########################################
######### NOT WORKING #####################
###########################################
n = 1025
# generate random positive semi-definite matrix
A = torch.rand(n, n, device=device)
A = torch.mm(A, A.t())
# invert
print("Before matrix inversion with n=1025")
V_pi = torch.linalg.inv(A)                  # THIS FAILS
print("After matrix inversion with n=1025") # THIS IS NEVER REACHED
```


### Versions

Collecting environment information...
PyTorch version: 2.4.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 15.0.1 (arm64)
GCC version: (Homebrew GCC 11.5.0) 11.5.0
Clang version: 16.0.0 (clang-1600.0.26.3)
CMake version: Could not collect
Libc version: N/A

Python version: 3.9.20 (main, Oct  3 2024, 02:24:59)  [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-15.0.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M2

Versions of relevant libraries:
[pip3] numpy==2.0.2
[pip3] torch==2.4.1
[conda] numpy                     2.0.2                    pypi_0    pypi
[conda] torch                     2.4.1                    pypi_0    pypi

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: kubernetes
Issue: Support for expanded 'operators' (e.g. In) in field selectors
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Support for selecting objects using 'set operations' (notably 'In') with field selectors, bringing parity with labelSelectors.

More specifically, I'd like to be able to select over the `metadata.namespace` field, so I can establish multi-namespace watches with consistent RV semantics.

### Why is this needed?

To perform a multi-namespace list/watch today, a user must fetch objects at the cluster-scope and then filter down the response client-side. This is expensive and doesn't scale well as the size of the cluster grows (and various permissions/authZ boundaries are put in place).

Forcing the apiserver to perform this sort of filtering has typically been avoided in the past, as etcd does not natively support something like this, meaning apiservers have to establish a cluster-scoped watch for each client and perform filtering in memory, leading to high amounts of decoding objects from etcd (only to throw them away again after).

Recent work within the apiserver I believe enables us to reduce the impact of these kinds of requests, namely:

* https://github.com/kubernetes/enhancements/issues/2340 (consistent reads from cache)
* https://github.com/kubernetes/enhancements/issues/4568 (resilient watch cache initialization)

Combined, these allow us to ensure we serve list/field selectors from the watch cache, allowing us to optimise and index (similar to how we index certain field selectors and label selectors today).

I believe this feature would complement https://github.com/kubernetes/enhancements/issues/4601 (authorise with selectors) well, as it'd allow end-users to authorise field selector usage as well.

---

For this feature, I think it'll be important to ensure we also index watches and probably also list operations that utilise fieldSelectors, at the very least for `metadata.namespace`. For watches, this is relatively simple as we can add the `cacheWatcher` for the request to the `indexedWatchers` structure multiple times (by generating multiple namespaceName/scope entries): https://github.com/kubernetes/kubernetes/blob/06a15c5cf96131faaf44f93f1be228a013ae5c0d/staging/src/k8s.io/apiserver/pkg/storage/cacher/cacher.go#L135-L163. I've hacked together a quick PoC of the sort of change needed for watches here: https://github.com/munnerz/kubernetes/commit/ae075a0d30906a7218fdc123dd11cc96748bc20d - please do note that this relies on stuffing a `kubernetes.io/metadata.namespace` label into GetAttr funcs to emulate fieldSelector 'In' support, but it demonstrates the performance optimisation technique somewhat :)

Optimising LIST operations is a bit more complex today (as far as I can tell!) due the underlying Store/Indexer implementations in `k8s.io/client-go/tools/cache` not supporting indexed 'set operations' natively.
Repository: node
Issue: `Buffer.concat` and `Buffer.copy` silently produce invalid results when the operation involves indices equal or greater than 2^32
Labels: confirmed-bug,help wanted,buffer,regression

### Version

v22.9.0, v23.0.0

### Platform

```text
Windows 11 x64

Microsoft Windows NT 10.0.22631.0 x64
```


### Subsystem

Buffer

### What steps will reproduce the bug?

```js
const largeBuffer = Buffer.alloc(2 ** 32 + 5)
largeBuffer.fill(111)

const result = Buffer.concat([largeBuffer])
console.log(result)
```

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

Consistent in `v22.9.0` and `v23.0.0`

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

All bytes of the return buffer produced by `Buffer.concat([largeBuffer])` should be identical to the source:

In this example:
```
111, 111, 111, 111, 111, 111, 111, 111, 111, 111, 111, ....
```


### What do you see instead?

In the returned buffer, first 5 bytes are `111`, and all following ones are 0.

```
111, 111, 111, 111, 111, 0, 0, 0, 0, 0, 0, ....
```

The `console.log(result)` output looks like:
```
<Buffer 6f 6f 6f 6f 6f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... 4294967251
 more bytes>
```

### Additional information

_No response_
Repository: next.js
Issue: Cookies cannot be read in middleware while defined in server actions (since 14 at least)
Labels: bug,Middleware,Runtime

### Link to the code that reproduces this issue

https://github.com/ScreamZ/reproduction-app-cookies-middleware

### To Reproduce

1. Start application
2. Clic "click me" button

### Current vs. Expected behavior

Cookies are set in Server action and middleware is not able to catch it!
![image](https://github.com/user-attachments/assets/590e1236-0045-43f0-a634-e0587120a057)


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:39:07 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 9.12.1
Relevant Packages:
  next: 15.0.0-canary.196
  eslint-config-next: N/A
  react: 19.0.0-rc-77b637d6-20241016
  react-dom: 19.0.0-rc-77b637d6-20241016
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Middleware, Runtime

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

next dev (local), next start (local)

### Additional context

_No response_
Repository: vscode
Issue: 【BUG】After opening the ipynb file, maximize the command terminal panel, and there will be a line of "space" at the top of the terminal panel.
Labels: bug,notebook-layout

<!-- ⚠️⚠️ 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: 
```
Version: 1.85.2 (user setup)
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:10.514Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045
```
- OS Version: Windows 10 Pro 22H2 19045.5011

Steps to Reproduce:

1. Open a *.ipynb file
2. click Maximize Panel Size
After opening the ipynb file, maximize the command terminal panel, and there will be a line of "space" at the top of the terminal panel.

1. Open a Jupyter file and pay attention to the position marked by the red line at the top.
![Image](https://github.com/user-attachments/assets/cbfcc3c7-fdf4-40bb-9f05-c9083e1a28eb)

2. Then maximize the terminal panel. A gap appears here.
![Image](https://github.com/user-attachments/assets/878570ed-8585-48a8-97e9-b8432bf5352f)

Even if I disable all extensions, it's still the same when opening an ipynb file locally.
Repository: Python
Issue: Add binary search
Labels: awaiting triage

### What would you like to share?

In this i want to add binary search ques answer  please add the label of gssoc ext and hacktober fest

### Additional information

_No response_
Repository: next.js
Issue: Including exclamation mark(" ! ")  in assetPrefix compilation will result in an error
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/xenodochial-easley-ddh8vq?workspaceId=6bdce0be-af7a-405b-adec-ac633e9ed70d

### To Reproduce

Add the following config to "next.config.mjs":
```js
output: "export",
assetPrefix: "https://mycdn.com/!mark",
```
if the assetPrefix incude "!" will trigger error
if change the "!" to "21%" will be ok (but not my need)


### Current vs. Expected behavior

Current:
```sh
➜  workspace git:(master) ✗ yarn build
yarn run v1.22.19
$ next build
  ▲ Next.js 15.0.0-canary.196

   Creating an optimized production build ...
Failed to compile.

Module not found: Error: Can't resolve 'mark&nextConfigOutput=export&flyingShuttle=false&nextConfigExperimentalUseEarlyImport=&preferredRegion=&middlewareConfig=e30%3D' in '/project/workspace'

Module not found: Error: Can't resolve 'mark&nextConfigOutput=export&flyingShuttle=false&nextConfigExperimentalUseEarlyImport=&preferredRegion=&middlewareConfig=e30%3D' in '/project/workspace'

Module not found: Error: Can't resolve 'mark&nextConfigOutput=export&flyingShuttle=false&nextConfigExperimentalUseEarlyImport=&preferredRegion=&middlewareConfig=e30%3D' in '/project/workspace'


> Build failed because of webpack errors
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```



### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.0-canary.196 // Latest available version is detected (15.0.0-canary.196).
  eslint-config-next: N/A
  react: 19.0.0-rc-77b637d6-20241016
  react-dom: 19.0.0-rc-77b637d6-20241016
  typescript: 5.3.3
Next.js Config:
  output: export
```


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

create-next-app

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

next build (local)

### Additional context

Both 15.0 and 14.x is not ok
Repository: PowerToys
Issue: Add Ḱ ḱ
Labels: Idea-Enhancement,Good first issue,Resolution-Fix Committed,Product-Quick Accent

### Description of the new feature / enhancement

Being able to select 

- **ḱ** on [**K**]
- **Ḱ** on [**Shift**] +[**K**]

### Scenario when this would be used?

Transcription of the Proto-Indo-European language.

### Supporting information

https://en.wikipedia.org/wiki/%E1%B8%B0
Repository: ant-design
Issue: Table组件，设置了sticky和        summary属性，  scroll: { x: 'max-content' }不生效
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox][(https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/ji-ben-yong-fa-antd-5-21-4-forked-tnc9fy?file=%2Fdemo.tsx%3A79%2C9&workspaceId=73767ffe-8e59-46a5-8f0d-9959add1714c)](https://codesandbox.io/p/sandbox/ji-ben-yong-fa-antd-5-21-4-forked-znmjgj?workspaceId=73767ffe-8e59-46a5-8f0d-9959add1714c)

### Steps to reproduce

进入链接codesandbox点击  <Button type="primary" onClick={addColumn}>
        Add Column
      </Button>

### What is expected?

当我设置sticky，summary属性后，期望在动态向表格中添加列能够表格自适应，能够滚动内容

### What is actually happening?

在动态添加内容时，表格不会自适应，添加的column，

| Environment | Info |
| --- | --- |
| antd | 5.21.4 |
| React | 18 |
| System | mac |
| Browser | chorme |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->