sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Memory Allocation on VRAM when model size is bigger than the size of VRAM 
Labels: bug,windows,memory

### What is the issue?

when the num_gpu=22 ,the model will be loaded into VRAM and RAM correctly,but when i change num_gpu=24,just one small step(47layers in total),it is expected to use shared VRAM to contain about 1GB datas.But it doesn't work.It will load 12GB into shared VRAM,and then shutdown due to out of memory.Is it a bug,or is it a feature because CUDA dosenot support?

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 556.13                 Driver Version: 556.13         CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                  Driver-Model | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3080 ...  WDDM  |   00000000:01:00.0 Off |                  N/A |
| N/A   42C    P8             15W /  140W |      64MiB /  16384MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A     14768    C+G   D:\Program\QQNT\QQ.exe                      N/A      |
+-----------------------------------------------------------------------------------------+

server.log is submitted

![Screenshot 2024-09-19 100805](https://github.com/user-attachments/assets/cbe56a81-41db-4ca5-85cb-724d70c93f6b)
![Screenshot 2024-09-19 100817](https://github.com/user-attachments/assets/e4d516cb-be42-483e-b7ce-1f574a79487f)
![Screenshot 2024-09-19 100100](https://github.com/user-attachments/assets/df9447a5-500b-4b2d-9b56-bdabd90fcbb9)
[server.log](https://github.com/user-attachments/files/17052524/server.log)


### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.10
Repository: flutter
Issue: [Flutter GPU] Shaders across different shader libraries can name clash.
Labels: engine,P3,team-engine,triaged-engine,flutter-gpu

Under the hood, we currently register Flutter GPU shaders in a single Impeller shader library using their plaintext names as keys. A simple fix for this would be to generate unique prefixes during shader library instantiation.
Repository: rust
Issue: Tracking Issue for generic `Atomic`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(generic_atomic)]`

This is a tracking issue for replacing the distinct `Atomic*` types with a generic `Atomic<T>` type. This allows using `Atomic` with FFI type aliases and helps clean up some API surface. Only types with existing `AtomicT` are usable in `Atomic<T>`.

### Public API

```rust
// core::sync::atomic

pub struct Atomic<T: AtomicPrimitive>(/* private fields*/);

pub type AtomicI32 = Atomic<i32>; // etc
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] ACP: https://github.com/rust-lang/libs-team/issues/443
- [ ] Implement `Atomic<T>` as an alias to `AtomicT`: https://github.com/rust-lang/rust/pull/130543
- [ ] Flip alias so `AtomicT` is an alias to `Atomic<T>`
- [ ] Move generic functionality from `AtomicT` to `Atomic<_>`
- [ ] Pseudo-prerequisite: Stabilize 128-bit atomics: https://github.com/rust-lang/rust/issues/99069
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- `Atomic<T>` is soft-blocked on 128-bit atomics, because since trait implementations cannot be unstable, gating `Atomic<i128>` separately from `Atomic<i32>` isn't possible.
  - If necessary, `AtomicI128` could instead name `Atomic<Wrapper<i128>>` for some unstable name `Wrapper` until 128-bit atomics are stable, to prevent `Atomic<i128>` from being usable from stable earlier than intended.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: node
Issue: Support `net.BlockList` in `http.Agent` options
Labels: net,feature request

### What is the problem this feature will solve?

Enable users to allow or block requests when using `http.request`, `fetch`, etc.

### What is the feature you are proposing to solve the problem?

Node.js already supports `net.BlockList`, it'd be awesome if you could simply pass in an instance of `net.BlockList` when creating a custom `http.Agent` and then have it automatically enforce the IP checks for you.

### What alternatives have you considered?

I believe the only way to do this at the moment is a bit boilerplate-y, which would be using a custom `lookup` function that calls `dns.lookup(hostname)` manually, then calls `blocklist.check(address)` manually, and then if it flags, throw an error, else return the address.

Although that still isn't a complete solution because the `lookup` function isn't called for hostnames that are already IP addresses, so even more code to do the check fully :(
Repository: godot
Issue: [Physics Interpolation] Interpolated triggered from outside physics process when using multi-threaded rendering.
Labels: bug,documentation,topic:physics

### Tested versions

- Reproducible in: 3.6.stable, 3.5.3.stable.

Cannot reproduce in earlier versions, as in-built 3D physics interpolation was introduced in 3.5.

### System information

Linux Mint 22

### Issue description

Specifically when using the multi-threaded rendering model while physics interpolation is enabled, every so often this warning is generated while rigid bodies are in motion:

```
W 0:00:15.011   instance_set_transform: [Physics interpolation] Interpolated triggered from outside physics process: "/root/Scene/@Cube@2/CollisionShape/MeshInstance" (possibly benign).
  <C++ Source>  servers/visual/visual_server_scene.cpp:892 @ instance_set_transform()
```

The rigid body that generates the warning is random, and I'm pretty sure the warnings are actually rate-limited in 3.6, since in 3.5, the warnings are essentially spammed out.

I would like to keep using the multi-threaded rendering model for my project, as I need to instance meshes in a separate thread, but this warning is somewhat annoying. Is there a nice way to solve this issue, or is my only option to hide the warnings?

### Steps to reproduce

1. Open the reproduction project.
2. Run the scene, and let physics do its thing for about 30 seconds. Since by default Godot uses single-threaded rendering, there should be no warnings generated.
3. Stop running the scene, enter the project settings, and under Rendering > Threads > Thread Model, change to "Multi-Threaded".
4. Run the scene again, and wait about 30 seconds again. This time, the warning should appear at regular-ish intervals.

### Minimal reproduction project (MRP)

[InterpolationWarning.zip](https://github.com/user-attachments/files/17052605/InterpolationWarning.zip)
Repository: ollama
Issue: qwen2.5 context length
Labels: bug

### What is the issue?

<img width="674" alt="image" src="https://github.com/user-attachments/assets/03949cc7-07fd-45c4-a09a-4a971e0a3586">

According to the model card, the context length should be **128k**? 

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

0.3.10
Repository: vscode
Issue: Git - vscode does not respect GIT_AUTHOR_NAME/EMAIL in pre-commit hook failures, setting git.requireGitUserConfig=false has no effect 
Labels: bug,git

<!-- ⚠️⚠️ 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.92.1 (Universal)`
- OS Version: Mac OS Sonoma 14.6.1

Steps to Reproduce:

1. add a pre-commit hook that exits 1 (for whatever reason)
2. do not set git config for user.name or user.email
3. set configs using [GIT_AUTHOR_NAME / GIT_AUTHOR_EMAIL](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables)
4. Try to commit using the source control pane
5. See error about user.name/email despite being set

<img width="555" alt="image" src="https://github.com/user-attachments/assets/ee99c44b-972e-4e74-a4a7-184601c939b3">

Notes:

- This only fails if a pre-commit hook fails (which is valid!)
- If the configs are set directly using git config, you get the output of the pre-commit hook instead of the screenshot above
- `git.requireGitUserConfig` is set to false
- The issue is in these lines of code https://github.com/microsoft/vscode/blob/07e6c39831b3ac1cabc1c228502a48788c4244c8/extensions/git/src/git.ts#L1743-L1754 which make a false assumption about how these are set
- Similar yet separate issues:
   - https://github.com/microsoft/vscode/issues/128704
   - https://github.com/microsoft/vscode/issues/173442
Repository: go
Issue: runtime: TestGdbAutotmpTypes failures
Labels: help wanted,NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "runtime" && test == "TestGdbAutotmpTypes"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8736426478682440353)):

    === RUN   TestGdbAutotmpTypes
    === PAUSE TestGdbAutotmpTypes
    === CONT  TestGdbAutotmpTypes
        runtime-gdb_test.go:78: gdb version 15.0
        runtime-gdb_test.go:569: gdb output:
            Loading Go Runtime support.
            Target 'exec' cannot support this command.
            Breakpoint 1 at 0x6f720: file /home/swarming/.swarming/w/ir/x/t/TestGdbAutotmpTypes2165650426/001/main.go, line 9.
            [New LWP 1144577]
            [New LWP 1144578]
    ...
            File runtime:
            	[]main.astruct
            	bucket<string,main.astruct>
            	hash<string,main.astruct>
            	main.astruct
            	typedef hash<string,main.astruct> * map[string]main.astruct;
            	typedef noalg.[8]main.astruct noalg.[8]main.astruct;
            	noalg.map.bucket[string]main.astruct
        runtime-gdb_test.go:586: could not find []main.astruct; in 'info typrs astruct' output
    --- FAIL: TestGdbAutotmpTypes (53.89s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: kubernetes
Issue: topologySpreadConstraints for availability zone in aws is not working as expected 
Labels: kind/bug,sig/scheduling,lifecycle/rotten,needs-triage

### What happened?

Stateful set has 3az spread 
```
│       topologySpreadConstraints:                                                                                                                               │
│       - labelSelector:                                                                                                                                         │
│           matchLabels:                                                                                                                                         │
│             app: myApp                                                                                                                                           │
│             component: myComponent                                                                                                                                      │
│             id:  app-65                                                                                                                                         │
│             app-id: app-65                                                                                                                                     │
│         maxSkew: 1                                                                                                                                             │
│         topologyKey: topology.kubernetes.io/zone                                                                                                               │
│         whenUnsatisfiable: DoNotSchedule
```

### What did you expect to happen?

It supposed to have 3 replica with 1 in each az but it ended up all 3 replica in one az

### How can we reproduce it (as minimally and precisely as possible)?

Able to reproduce 2 times but not always 

### Anything else we need to know?

there were capacity issues in other azs but it should result it not scheduling pods there

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here

Server Version: v1.28.12-eks-2f46c53
WARNING: version difference between client (1.31) and server (1.28) exceeds the supported minor version skew of +/-1

```

</details>


### Cloud provider

<details>
AWS

</details>


### 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: Table组件，合并单元格，fixed两列之后，左右滑动合并的单元格不会固定。
Labels: 🐛 Bug,help wanted,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-bwlbbn?file=demo.tsx,package.json)

### Steps to reproduce

const columns: TableProps<DataType>['columns'] = [
  {
    title: 'Name',
    dataIndex: 'name',
    key: 'name',
    fixed: 'left',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 8 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: 'Age',
    dataIndex: 'age',
    key: 'age',
    fixed: 'left',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: 'Address',
    dataIndex: 'address',
    key: 'address',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: 'Tags',
    key: 'tags',
    dataIndex: 'tags',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: 'Action',
    key: 'action',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: '杀马特',
    dataIndex: '112',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: '杀马特',
    dataIndex: '1124',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: '杀马特',
    dataIndex: '11242',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
  {
    title: '杀马特',
    dataIndex: '11249',
    onCell: (o, i) => {
      if (i === 0) {
          return { colSpan: 0 };
      }
      return { colSpan: 1 };
  },
  },
];

### What is expected?

左右滑动，合并的一列，不会动

### What is actually happening?

左右滑动，合并的一列，会滑动


| Environment | Info |
| --- | --- |
| antd | 5.20.6 |
| React | 18.3.1 |
| System | mac os 14.6.1  |
| Browser | 版本 128.0.6613.138（正式版本） (arm64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Workspaces: Capture not translated
Labels: Issue-Bug,Area-Localization,Needs-Triage,Needs-Team-Response,Issue-Translation,Product-Workspaces

### Microsoft PowerToys version

0.84.0

### Utility with translation issue

Workspaces

### 🌐 Language affected

German

### ❌ Actual phrase(s)


Capture

### ✔️ Expected phrase(s)

Erfassen

### ℹ Why is the current translation wrong

Button still contains text "Capture", but should show "Erfassen", like in the text of the explaination.
![image](https://github.com/user-attachments/assets/6492387f-a331-4da4-bfd8-5250f7aa5971)
Repository: pytorch
Issue: Numpy related failure of gradient and sobolengine distribution testcases on POWER and x86
Labels: triaged,module: numpy,module: POWER

### 🐛 Describe the bug

I am seeing failures of testcases prsent in test/test_torch.py when run on either POWER or on x86 machine

Steps to reproduce:

- clone build and install pytorch
- `python test/test_torch.py`

o/p msg at end:
Ran 1021 tests in 47.036s

FAILED (failures=5, errors=2, skipped=53)

FAIL: test_sobolengine_distribution (__main__.TestTorch.test_sobolengine_distribution)
FAIL: test_sobolengine_distribution_scrambled (__main__.TestTorch.test_sobolengine_distribution_scrambled)
FAIL: test_gradient_all_cpu_complex64 (__main__.TestTorchDeviceTypeCPU.test_gradient_all_cpu_complex64)
FAIL: test_gradient_all_cpu_float32 (__main__.TestTorchDeviceTypeCPU.test_gradient_all_cpu_float32)
FAIL: test_gradient_all_cpu_int64 (__main__.TestTorchDeviceTypeCPU.test_gradient_all_cpu_int64)

Peculiar thing about these failures are, they are failing on POWER when the python version is 3.12 and numpy version is greater than 1.26, for numpy 1.26 and below above failures do not reproduce, moreover if we run pytorch on python version 3.10, then also  above failures do not reproduce (regardless of version of numpy)
For x86, version of python (3.10 or 3.12) is not of relevance, it passes if numpy version <=1.26 and fails if ver >1.26.4


### Versions

Collecting environment information...

NUMA node2 CPU(s):                  192-287
NUMA node3 CPU(s):                  288-383
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Not affected
Vulnerability Spectre v1:           Mitigation; __user pointer sanitization, ori31 speculation barrier enabled
Vulnerability Spectre v2:           Mitigation; Software count cache flush (hardware accelerated), Software link stack flush
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] numpy==2.1.1
[pip3] torch==2.5.0a0+gitc0d2f99
[conda] nomkl                     3.0                           0    https://ausgsa.ibm.com:7191/gsa/ausgsa/projects/o/open-ce/conda/Open-CE-r1.11/1.11.0/opence-p10
[conda] numpy                     2.1.1           py312h8c5cf51_0    conda-forge
[conda] torch                     2.5.0a0+gitc0d2f99          pypi_0    pypi

cc @mruberry @rgommers
Repository: ui
Issue: [bug]: Can't open DropdownMenu when using with AlertDialog together
Labels: bug

### Describe the bug

```tsx
export default function Test() {
  const [open, setOpen] = useState(false);

  return (
    <div className="p-20">
      <DropdownMenu>
        <DropdownMenuTrigger>Open</DropdownMenuTrigger>
        <DropdownMenuContent>
          <DropdownMenuLabel>My Account</DropdownMenuLabel>
          <DropdownMenuSeparator />
          <DropdownMenuItem>Profile</DropdownMenuItem>
          <DropdownMenuItem>Billing</DropdownMenuItem>
          <DropdownMenuItem>Team</DropdownMenuItem>
          <DropdownMenuItem>Subscription</DropdownMenuItem>
          <Button onClick={() => setOpen(true)}>open dialog</Button> // open dialog 
        </DropdownMenuContent>
      </DropdownMenu>

      <AlertDialog open={open}>
        <AlertDialogContent>
          <AlertDialogHeader>
            <AlertDialogTitle>Are you absolutely sure?</AlertDialogTitle>
            <AlertDialogDescription>
              This action cannot be undone. This will permanently delete your
              account and remove your data from our servers.
            </AlertDialogDescription>
          </AlertDialogHeader>
          <AlertDialogFooter>
            <AlertDialogCancel onClick={() => setOpen(false)}> // close dialog
              Cancel
            </AlertDialogCancel>
            <AlertDialogAction>Continue</AlertDialogAction>
          </AlertDialogFooter>
        </AlertDialogContent>
      </AlertDialog>
    </div>
  );
}
```

**Can't open DropdownMenu again after closing AlertDialog**

### Affected component/components

DropdownMenu, AlertDialog

### How to reproduce

---

### Codesandbox/StackBlitz link

https://codesandbox.io/p/sandbox/shadcnui-issue-44hxn3

### Logs

_No response_

### System Info

```bash
---
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues