sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: GPU Precision drops significantly when kernel size is increased from 3 to 5 in Conv3D
Labels: module: performance,module: cudnn,module: cuda,triaged

### 🐛 Describe the bug

# Precision bug
`nn.Conv3d`  has a huge decrease in precision when the kernel size increases from 3 to 5 for input tensors with size >  16. This is true even if `torch.backends.cuda.matmul.allow_tf32`  is turned off.

The maximum discrepency between `cpu` and `cuda` version is increased 1000 times when the kernel size is changed from 3x3x3 to 5x5x5. 

![image](https://github.com/user-attachments/assets/4c8e2c32-9cbc-42c0-9e11-8b923007a39f)

here's the code to generate the above table.

```python
import torch
import torch.nn as nn
import pandas as pd

torch.backends.cuda.matmul.allow_tf32 = False

# Function to perform 3D convolution on a given device
def conv_3d_device(conv3d, input_tensor, device):
    x = input_tensor.to(device)
    conv3d = conv3d.to(device)
    
    with torch.no_grad():
        output_tensor = conv3d(x)
    
    return output_tensor.cpu()

# Parameters
n_channels = 1
sizes = [32, 64, 128]  # Different sizes to test
kernel_sizes = [3, 5, 7, 9, 11]  # Different kernel sizes to test

results = []

for k_sz in kernel_sizes:
    for sz in sizes:

        pad_sz = k_sz // 2
        x = torch.randn(1, n_channels, sz, sz, sz)
        conv3d = nn.Conv3d(in_channels=n_channels, out_channels=1, kernel_size=k_sz, stride=1, padding=pad_sz)

        cpu_device = 'cpu'
        y1 = conv_3d_device(conv3d, x, cpu_device)
        gpu_device = 'cuda' 
        y2 = conv_3d_device(conv3d, x, gpu_device)

        max_error = torch.max(torch.abs(y2 - y1)).item()
        sum_diff = torch.sum(torch.abs(y2 - y1)).item()
        n_diff = torch.sum((y2 != y1).int()).item()
        n_approx = torch.sum((torch.abs(y2 - y1) < 1e-5).int()).item()
        n_app_diff = y2.numel() - n_approx

        result = {
            'size': sz,
            'kernel size': k_sz,
            'max error': max_error,
            'sum diff': sum_diff,
            'num elements': y1.numel(),
            'num diff elements': n_diff,
            'num same elements': y1.numel() - n_diff,
            'num close elements': n_approx
        }
        print(result)

        results.append(result)

# Convert results to DataFrame and save to Excel
df = pd.DataFrame(results)
df.to_csv('conv3d_results_pytorch.csv', index=False)
```

### Versions

pytorch-ignite            0.3.0                    pypi_0    pypi
torch                     2.1.1+cu118              pypi_0    pypi
torchaudio                2.1.1+cu118              pypi_0    pypi
torchvision               0.16.1+cu118             pypi_0    pypi

cc @msaroufim @csarofeen @ptrblck @xwang233
Repository: deno
Issue:  listenQueue blocks main thread
Labels: bug,ext/kv

Version: Deno 1.46.1
> I think that under certain conditions the listenQueue method blocks the main thread:

**test-kv.ts**
```ts
export const kv = await Deno.openKv();
kv.listenQueue(async () => {}); // BLOCKER!!!!
```
**test.ts**
```ts
import { kv } from "./test-kv.ts";
kv.get([]);
Deno.serve(() => new Response()); // does not start =(
```

> But if we remove listenQueue or add some log behind it, everything will work:

**test-kv.ts**
```ts
export const kv = await Deno.openKv();
kv.listenQueue(async () => {});
console.log(); // working!
```
This same code works fine on 1.44
Repository: go
Issue: google.golang.org/protobuf/proto: TestHasExtensionNoAlloc/Lazy failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "google.golang.org/protobuf/proto" && test == "TestHasExtensionNoAlloc/Lazy"
```

Issue created automatically to collect these failures.

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

    === RUN   TestHasExtensionNoAlloc/Lazy
        extension_test.go:156: proto.HasExtension should not allocate, but allocated 1.00x per run
    --- FAIL: TestHasExtensionNoAlloc/Lazy (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: kubernetes
Issue: feature(kubelet): add goroutines metric in the kubelet component
Labels: sig/node,kind/feature,sig/instrumentation,triage/accepted

### What would you like to be added?

I want to add a new metric to track the number of goroutines in kubelet. There seems to be no metric defined in kubelet to track the number of goroutines.

### Why is this needed?

Although we often use metrics such as `go_goroutine` or `go_sched_goroutines_goroutines`(We can use `go_goroutines{job="kubelet"}` or `go_sched_goroutines_goroutines{job="kubelet"}` to query in prometheus) to view the active goroutines of kubelet. However, using this metrics, we cannot know the number of goroutines for which operations. Therefore, I want to add this indicator to the kubelet component.
For example: Currently, there are many operations in kubelet that may add many goroutines: 
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/pod_workers.go#L945
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/images/puller.go#L55
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/kuberuntime_container.go#L843

In addition, kube-scheduler has implemented similar features. issue tracked: https://github.com/kubernetes/kubernetes/pull/112003
Repository: bitcoin
Issue: test: WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock) (pid=32090)
Labels: Bug,Wallet,Tests


To reproduce, use something like:

```
rm -rf ./bld-cmake/ && cmake -B ./bld-cmake -DAPPEND_CXXFLAGS='-std=c++23' -DCMAKE_C_COMPILER='clang' -DCMAKE_CXX_COMPILER='clang++' -DBUILD_GUI=ON -DBUILD_FUZZ_BINARY=ON -DBUILD_BENCH=ON -DWITH_ZMQ=ON -DWITH_ZMQ=ON -DBUILD_UTIL_CHAINSTATE=ON -DBUILD_KERNEL_LIB=ON -DSANITIZERS=thread        && cmake --build ./bld-cmake --parallel $( nproc ) -- 
TSAN_OPTIONS="suppressions=$(pwd)/test/sanitizer_suppressions/tsan:halt_on_error=1:second_deadlock_stack=1" ./bld-cmake/src/test/test_bitcoin -t wallet_tests -l test_suite
Repository: pytorch
Issue: Should make the doc of `nn.CrossEntropyLoss()` more clear
Labels: module: docs,module: nn,module: loss,triaged

### 📚 The doc issue

[The doc](https://pytorch.org/docs/stable/generated/torch.nn.CrossEntropyLoss.html) of `nn.CrossEntropyLoss()` explains about `target` tensor in a complex way as shown below. *It's difficult to understand:

![Screenshot 2024-08-30 195003](https://github.com/user-attachments/assets/018b6938-14ba-4fab-858a-f99dab4583eb)

So from my understanding and experiments, these simple explanations below should be added to the doc above. *It's easy to understand:

  - The `target` tensor whose size is different from `input` tensor  is treated as class indices.
  - The `target` tensor whose size is same as `input` tensor is the class probabilities which should be between `[0, 1]`.
 
And from what the doc says below and my experiments, when `target` tensor is treated as **class indices**, `softmax()` is used both for `input` and `target` tensor internally:

> The target that this criterion expects should contain either:   
> - Class indices in the range ...     
> ...    
> Note that this case is equivalent to applying [LogSoftmax](https://pytorch.org/docs/stable/generated/torch.nn.LogSoftmax.html#torch.nn.LogSoftmax) on an input, followed by [NLLLoss](https://pytorch.org/docs/stable/generated/torch.nn.NLLLoss.html#torch.nn.NLLLoss).

But when `target` tensor is treated as **class probabilities**, `softmax()` is used only for `input` tensor internally, that's why the example of `target` tensor as **class indices** in the doc doesn't use `softmax()` externally while the example of `target` tensor as **class probabilities** in the doc uses `softmax()` externally as shown below:

![Screenshot 2024-08-30 201043](https://github.com/user-attachments/assets/0f2072f1-0749-45ff-8060-01688680f646)

So, the doc also should say something like as shown below. *You also use the words **class indices mode** and **class probabilities mode** :

- `softmax()` is used internally for `input` tensor, both when `target` tensor is treated as **class indices** and **class probabilities** so you don't need to use `softmax()` externally.
- `softmax()` is used internally for `target` tensor only when `target` tensor is treated as **class indices** so you should use `softmax()` externally for `target` tensor when `target` tensor is treated as **class probabilities**.


### Suggest a potential alternative/fix

_No response_

cc @svekars @brycebortree @tstatler @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: go
Issue: proposal: bufio: add Scanner.Reset(io.Reader)
Labels: Proposal

### Proposal Details

It seems like an oversight that both bufio.Writer and bufio.Reader both can reuse their memory with the Reset method while Scanner does not have same method.
Repository: vscode
Issue: Screen cheese on multi-file diff editor scrollbar
Labels: polish,multi-diff-editor



https://github.com/user-attachments/assets/a40310ac-7a44-42d8-abb7-29edcdc81aac
Repository: flutter
Issue: Adding font scaling based on system font size for accessibility on desktop
Labels: c: new feature,a: accessibility,a: typography,c: proposal,a: desktop,P2,team-accessibility,triaged-accessibility

### Use case

According to <https://docs.flutter.dev/ui/accessibility-and-internationalization/accessibility#large-fonts>, font scaling based on Android and iOS system-wide font settings works.

I tested this with GNOME on Linux, and changing the interface font size did not adjust the font size in Flutter. I suspect that the same applies to Windows and macOS devices.

Font scaling on desktop would be wonderful for high pixel-density screens, and for the sake of accessibility.

### Proposal

It would be great if font scaling based on system settings could also work for desktop. It seems better to have a single API for font scaling in Flutter apps than to depend on a combination of behavior for phone vs desktop platforms.

Thanks! 😀
Repository: vscode
Issue: Bad line move indentation adjustment
Labels: bug,editor-autoindent

Have the following TypeScript code:

```ts
function something() {
	const x = 3;
	// if (true) {
	// }
}
```

Move the line `const x = 3;` down two times. Observe the result:

```ts
function something() {
	// if (true) {
		// }
		const x = 3;
}
```



https://github.com/user-attachments/assets/84f6b38d-ca63-4852-8b17-070cedb4688e
Repository: opencv
Issue: C++ no includes on get-started page on OpenCV.org
Labels: category: documentation

### Describe the doc issue

The `#include` lines are not actually showing what to include.
![image](https://github.com/user-attachments/assets/d336e8d8-47d0-4a23-999c-f9c9b2546da3)
https://opencv.org/get-started/

### Fix suggestion

_No response_
Repository: bitcoin
Issue: CMake `CheckPIESupported` doesn't always work
Labels: Build system,Upstream

Seen as part of this thread: https://github.com/hebasto/bitcoin/issues/341#issuecomment-2321282757.

It looks like CMakes https://cmake.org/cmake/help/latest/module/CheckPIESupported.html check isn't quite the equivalent of what we used to do in Autotools (having `-pie` and `-fPIE` as part of our hardened flags), such that now, sometimes the user will need to manually pass flags like `-fPIE`. In this case, on a FreeBSD system.

It's not entirely clear if this is a bug in CMake, or something else, however, we should fix this, as users/developers should not need to manually pass `PIC`/`PIE` related flags for working compilation, aside from it being a missing hardening feature.
Repository: vscode
Issue: New version of vscode breaks git bash terminal integration in Windows 11
Labels: bug,confirmation-pending,terminal-shell-git-bash

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.92.2 (user setup)
- OS Version:  Microsoft Windows 11 Home Single Language 10.0.22631 compilation 22631

Git version : Git for Windows v2.43.0

Steps to Reproduce:

1.  Install the mentioned vscode version 
2. Install the Git Version
3. Open the git bash terminal in vscode 
4. The following error is shown 
![image](https://github.com/user-attachments/assets/58f74cce-20e1-45a6-b728-b4779a35cfc6)
This happens when I updated VScode to the current version in other version git bash was working correctly.
I even try to update git for windows but same error is shown.
If I echo 
$ echo $HOME
odrisers # outpu

But if I run inside the git bash app then it seems to behave normally
![image](https://github.com/user-attachments/assets/dace1155-c07c-4c77-a0c9-0a2fe19faafa)
Repository: deno
Issue: Inconsistencies of unrelated but nested workspaces
Labels: bug

Version: Deno 1.46.2

Repro repo: https://github.com/albnnc/deno-repro-20240830

Possibly related: https://github.com/denoland/deno/issues/25226

Should the following cases work, or do I have wrong understanding of workspaces in Deno?

## Possibly wrong warning of improper "patch" usage

```sh
cd internal
deno run ./mod.ts
```

![image](https://github.com/user-attachments/assets/b2408c1a-eb08-4b7c-aaa7-aa6e15190bfd)

Workspace "internal" is nested in terms of folder structure only (it's not referenced in "workspace" field of outer deno.jsonc), but it looks like Deno thinks that `internal/deno.jsonc` is a part of outer workspace, which is wrong. Looks like "warning" message is wrong.

## Module resolution differs between implicit and explicit Deno config cases

```sh
cd internal
deno info ./mod.ts
deno info ./mod.ts --config ./deno.jsonc
```

![image](https://github.com/user-attachments/assets/c879a611-3848-4485-a1b3-b84e687e1090)

As far as I can understand, explicit reference of deno.jsonc which is in CWD shouldn't change anything. This behaviour breaks [esbuild_deno_loader](https://github.com/lucacasonato/esbuild_deno_loader) in some cases.
Repository: godot
Issue: Animated TileMapLayer Tiles Won't Pause When The Tree Is Paused
Labels: enhancement,discussion,topic:2d

### Tested versions

Godot v.4.3.stable

### System information

Windows 10 - Godot v4.3.stable

### Issue description

As the title says, animated tiles created in a tileset resource won't stop animating when pausing the scene tree, unlike all other processes that are meant to be. example below.

![issue](https://github.com/user-attachments/assets/d52252a2-0e74-41d1-8f02-2b4893a319c2)


### Steps to reproduce

Create an animated tile in a tileset resource, assign it to a TileMapLayer, and via a script, toggle the tree's paused property.

### Minimal reproduction project (MRP)

[mrp_001.zip](https://github.com/user-attachments/files/16818656/mrp_001.zip)
Repository: flutter
Issue: [Conductor] Enable override of engine mirror location
Labels: c: new feature,P2,team-release

Came up as part of https://github.com/flutter/flutter/pull/154363. 
Framework has the ability to override and set a custom mirror. Engine does not and should.
Repository: vscode
Issue: When "comment" text box is focused and "Review Pull Request" panel is in a sidebar, `sideBarFocus` does not get set to `true`
Labels: bug,help wanted,webview-views

<!-- Please search existing issues to avoid creating duplicates. -->

I have my primary sidebar set to be on the right side. When the "comment" textbox supplied by this extension (screenshotted below) is focused, `sideBarFocus` is not set to `true`. I know this for a fact, because I have set up a keyboard shortcut with a `when` clause of _just_ `sideBarFocus`, and it doesn't work when I'm in that text box - if I'm in another text box in the sidebar (for example, the extension view) and I use the same shortcut, it works fine.

![CleanShot 2024-08-20 at 15 30 01](https://github.com/user-attachments/assets/7471923a-1613-44da-99b2-91793a1b1a4e)

<!-- Use Help > Report Issue to prefill some of these. -->

- Extension version: v0.94.0
- VSCode Version: 1.92.2
- Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
- Date: 2024-08-14T17:29:30.058Z
- Electron: 30.1.2
- ElectronBuildId: 9870757
- Chromium: 124.0.6367.243
- Node.js: 20.14.0
- V8: 12.4.254.20-electron.0
- OS: Darwin arm64 23.6.0
- Repository Clone Configuration (single repository/fork of an upstream repository): single repository
- Github Product (Github.com/Github Enterprise version x.x.x): Github.com

Steps to Reproduce:

1. Create a keyboard shortcut with a `when` clause set to `sideBarFocus`. For demo purposes, I'm using the command to show the command palette (it could be anything):

```
{
  "key": "cmd+ctrl+space",
  "command": "workbench.action.showCommands",
  "when": "sideBarFocus"
}
```

2. Go to the "Leave a comment" textbox and try invoking that shortcut. It does not do anything.
3. Go to another panel, for example, the extensions view, click on a text box, and try to invoke the command. It works.

If this extension is in the sidebar, and my cursor is in the extension, then `sideBarFocus` should be `true` - but it's not. It's not clear to me whether or not this is a VSCode problem or a problem with this extension, however, considering that it works in other sidebar views, I want to place the blame on the extension at this point.
Repository: awesome-mac
Issue: 🎉 Add Peakto
Labels: addition

### 🪩 Provide a link to the proposed addition

https://cyme.io/peakto-photo-organizer-software

### 😳 Explain why it should be added

Exclusively for Mac users, Peakto is an unique photo organizer compatible with various photo sources (such as Lightroom, Capture One, Pixelmator, or simply photo folders), offering AI-driven features for seamless media management.


### 📖 Additional context

Peakto is the universal photo manager that’s here to make photographers life easier.

**See Everything:**
- All-In-One View: Preview all your photos AND videos from various sources in one place.
- Easy Organization: No need to stay connected to your NAS or hard drives to organize your portfolio.
- New Video Player: Quickly browse videos with contact sheets for easy navigation.

**Organize Everything:**
- Central Hub: Annotate, delete, and manage photos and videos from one interface.
- Tag People: Use AI to identify and tag people across your photos effortlessly.
- Create Selections: Make selections from different sources and sync edits across all your software.

**Rediscover:**
- Smart Sorting: Enjoy automatic sorting by category and map views.
- Timeline View: Navigate photos by date with the new timeline feature.

**Automate:**
- AI Organization: Let AI handle keyword assignments and content recognition.
- Video Search: Find specific scenes in videos with simple descriptions.

Peakto 2.0 brings together your photos and videos from folders, hard drives, Apple Photos, Lightroom, Luminar, Capture One, and more into one powerful interface. It’s the perfect tool to manage your entire photo library and streamline your workflow.

![visuel presse peakto 2 0](https://github.com/user-attachments/assets/c6f01d27-f6d4-458c-8a3e-d237f4a1d49d)



### 🧨 Issue Checklist

- [X] I have checked for other similar issues
- [X] I have explained why this change is important
- [X] I have added necessary documentation (if appropriate)
Repository: ollama
Issue: Improve error reporting with old or missing AMD driver on windows (unable to load amdhip64_6.dll)
Labels: feature request,windows,amd

I was trying to solve this issue that prevented me from using AMD GPU

```
time=2024-08-30T09:43:00.852-05:00 level=DEBUG source=amd_windows.go:33 msg="unable to load amdhip64_6.dll, 
please make sure to upgrade to the latest amd driver: The specified module could not be found."
```

Compared with the message for searching Nvidia, the AMD message is really minimal, here is the Nvidia output

```
time=2024-08-30T09:43:00.768-05:00 level=DEBUG source=gpu.go:469 msg="Searching for GPU library" name=cudart64_*.dll
time=2024-08-30T09:43:00.768-05:00 level=DEBUG source=gpu.go:488 msg="gpu library search" globs="[C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v12.2\\bin\\cudart64_*.dll* ..........]"
```

As you can see, ollama does not tell where it tries to find `amdhip64_6`.  https://github.com/ROCm/ROCm/issues/3418#issuecomment-2253379050 said the DLL should be in ` C:\Windows\system32\amdhip64_6.dll`, which is not the case as my dll is in `C:\Program Files\AMD\ROCm\6.1\bin`. It turns out that ollama uses the environment variable `PATH` to search for the DLL, which is not very clear just by reading the console debug output. To help future users, I'd like to suggest the following improvements:

1. Print out the search path when searching for AMD GPU (like the Nvidia log above)
2. Suppress Nvidia message when `CUDA_VISIBLE_DEVICES=-1` and AMD message when  `HIP_VISIBLE_DEVICES=-1` to simplify the log (there is no need to print out the search path if one does not need Nvidia or AMD driver)
Repository: tensorflow
Issue: [TFLite] Could log level control be added to the TFLite C API?
Labels: stat:contribution welcome,awaiting review,type:feature,comp:lite

### Issue type

Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.17.0

### Custom code

No

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

[`tflite::LoggerOptions::SetMinimumLogSeverity()`](https://github.com/tensorflow/tensorflow/blob/daa9e4e0d0a04626fb97cf9b11c1ae6be46c6517/tensorflow/lite/logger.h#L37) provides a method for controlling the log level in C++.
This allows more detailed logging than INFO or limits logging to ERROR or higher in prod builds.

However, we cannot use this feature from the C API. 
I think this enhancement for the C API is useful and good for future additions on other platforms, such as Swift.
Is it possible to add bindings for the `tflite::LoggerOptions` class to the C API ?

I am sorry if I missed this features of the C API.
I will be happy to help you, for example, try to create a PR.

### Standalone code to reproduce the issue

```shell
n/a
```


### Relevant log output

_No response_
Repository: deno
Issue: Bug: No named export `gql` in `graphq-tag` found
Labels: bug,node compat,node resolution

Reported in Discord:  https://discord.com/channels/684898665143206084/1279102082452029520/1279102082452029520

## Steps to reproduce

Run this snippet:

```ts
import { gql } from "npm:graphql-tag@2.12.6";
console.log(gql);
```

Output:

```sh
error: Uncaught SyntaxError: The requested module 'npm:graphql-tag@2.12.6' does not provide an export named 'gql'
import { gql } from "npm:graphql-tag@2.12.6";
         ^
    at <anonymous> (file:///Users/marvinh/dev/test/deno-graphql-tag/main.ts:1:10)
```

The problem occurs because Deno picks the wrong entry point.

```jsonc
  "main": "./main.js", // <- deno picks this one
  "module": "./lib/index.js", // <- ...but it should have picked this
  "jsnext:main": "./lib/index.js",
```

Version: Deno 1.46.2+d71eebb