sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: nvm
Issue: nvm install falls back immediately to source tarfile if binary tarfile fails for whatever reason
Labels: installing node,needs followup

installing with `nvm install --lts` on Bullseye ARM64 produces unexpected code compilation after the tarfile is downloaded

```
Computing checksum with sha256sum
Checksums matched!
$>./configure --prefix=/home/runner/.nvm/versions/node/v20.18.0 <
Node.js configure: Found Python 3.9.2...
INFO: configure completed successfully
/usr/bin/make -C out BUILDTYPE=Release V=0
  g++ -o /home/runner/.nvm/.cache/src/node-v20.18.0/files/out/Release/obj.target/simdutf/deps/simdutf/simdutf.o ../deps/simdutf/simdutf.cpp '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CONF_NAME=nodejs_conf' '-DNODE_OPENSSL_HAS_QUIC' '-DICU_NO_USER_DATA_OVERRIDE' '-D__STDC_FORMAT_MACROS' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' -I../deps/simdutf  -pthread -Wall -Wextra -Wno-unused-parameter -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++17 -MMD -MF /home/runner/.nvm/.cache/src/node-v20.18.0/files/out/Release/.deps//home/runner/.nvm/.cache/src/node-v20.18.0/files/out/Release/obj.target/simdutf/deps/simdutf/simdutf.o.d.raw   -c

...
```
 The compilation continues for hours (on a slow machine).

This issue does not occur on Bullseye ARMhf, Bookworm ARMhf, or Bookworm ARM64. There is no code compilation for those systems.
Repository: pytorch
Issue: [Runtime Error] Build PyTorch with cuda12.2 on Jetson AGX Orin with jetpack 5.1.4
Labels: module: cuda,triaged,module: arm,module: jetson

### 🐛 Describe the bug

### Environment

```bash
jetpack==5.1.4
cuda==12.2
PyTorch==2.3.0
```

I found that the cuda-12.2 is compatible with jetpack5.x: [CUDA Upgradable Package for Jetson](https://docs.nvidia.com/cuda/cuda-for-tegra-appnote/index.html#cuda-upgradable-package-for-jetson)

I've built PyTorch from source with cuda-12.2. When I typed:

```python
import torch
torch.cuda.get_device_capability()
```

It went:

```bash
 File "/home/orin/tools/anaconda3/envs/llmserving_py/lib/python3.10/site-packages/torch/cuda/__init__.py", line 430, in get_device_capability
    prop = get_device_properties(device)
  File "/home/orin/tools/anaconda3/envs/llmserving_py/lib/python3.10/site-packages/torch/cuda/__init__.py", line 444, in get_device_properties
    _lazy_init()  # will define _get_device_properties
  File "/home/orin/tools/anaconda3/envs/llmserving_py/lib/python3.10/site-packages/torch/cuda/__init__.py", line 293, in _lazy_init
    torch._C._cuda_init()
RuntimeError: The NVIDIA driver on your system is too old (found version 11040). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver.
```

But what confused me is that the cuda-12.2 seems compatible with jetpack-5.1.4, I really want to know why because I don't want to reflash my jetson env and rebuild the PyTorch anymore, it really kills me. >_<

### Error logs

_No response_

### Minified repro

_No response_

### Versions

I'm using PyTorch v2.3.0 which was built from source.

cc @ptrblck @msaroufim @malfet @snadampal @milpuz01 @puririshi98 @ezyang @chauhang @penguinwu
Repository: go
Issue: x/tools/go/packages: Load is inefficient due to heavy contention
Labels: NeedsInvestigation

See https://github.com/golang/go/issues/70078#issuecomment-2442266268: for the same workload, the go list command sometimes runs very quickly (70ms) and other times waits for a conspicuously round number (1.0s) of elapsed time before it exits. I vaguely recall that this was intentional behavior to prevent file system time quantization problems. Is it always necessary? If so, when and why? Are there ways to avoid it?

@matloob @samthanawalla
Repository: deno
Issue: Using NPM-prefixed Import Syntax Breaks Lock File
Labels: bug,node compat,install

## Deno Info
Version: Deno 2.0.3

## Steps to reproduce

File Tree:
```tree
- .vscode
  - settings.json
- app.ts
- deno.json
```

Deno.json:
```json
{
    "imports": {
        "@aws-sdk/client-s3": "npm:@aws-sdk/client-s3@^3.679.0"
    }
}
```

1. Add the following to `app.ts`:
   ```ts
   import { S3Client } from '@aws-sdk/client-s3';
   console.log(S3Client);
   ```
2. Run `deno run -A app.ts`:
   Console Output: `[class S3Client extends Client]`
3. Update `app.ts`:
   ```ts
   import { S3Client } from 'npm:@aws-sdk/client-s3';
   console.log(S3Client);
   ```
4. Run `deno run -A app.ts`:
   Console Output: `error: Could not resolve 'npm:@aws-sdk/client-s3@3.679.0'.`
5. Update `app.ts` to original:
   ```ts
   import { S3Client } from '@aws-sdk/client-s3';
   console.log(S3Client);
   ```
6. Run `deno run -A app.ts`:
   Console Output: `error: Could not resolve 'npm:@aws-sdk/client-s3@3.679.0'.`

## Expected Behavior

Both import syntaxes should work.
```
import { S3Client } from '@aws-sdk/client-s3';
import { S3Client } from 'npm:@aws-sdk/client-s3';
```

## Notes

The lock file seems to become “corrupted” once the command in step 4 is run.
Repository: go
Issue: runtime: TestLockOSThreadExit failures
Labels: NeedsInvestigation,arch-riscv,compiler/runtime

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

Issue created automatically to collect these failures.

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

    === RUN   TestLockOSThreadExit
        proc_test.go:983: /home/swarming/.swarming/w/ir/x/t/go-build3157675313/testprog.exe LockOSThreadMain (36.043549ms): ok
        proc_test.go:989: /home/swarming/.swarming/w/ir/x/t/go-build3157675313/testprog.exe LockOSThreadAlt (31.099939ms): ok
        proc_test.go:991: want "OK\n", got "error: read /proc/self/task/3378684/status: no such process\n"
    --- FAIL: TestLockOSThreadExit (0.07s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: google.golang.org/protobuf: TestIntegration/Go1.23.0/ProtoLegacy failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "google.golang.org/protobuf" && test == "TestIntegration/Go1.23.0/ProtoLegacy"
```

Issue created automatically to collect these failures.

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

    === RUN   TestIntegration/Go1.23.0/ProtoLegacy
        integration_test.go:137: executing (go1.23.0 test -tags protolegacy ./...): exit status 1
            ?   	google.golang.org/protobuf/cmd/protoc-gen-go/internal_gengo	[no test files]
            ok  	google.golang.org/protobuf	0.097s
            ok  	google.golang.org/protobuf/cmd/protoc-gen-go	0.109s
            ok  	google.golang.org/protobuf/compiler/protogen	0.096s
            ok  	google.golang.org/protobuf/encoding	0.117s [no tests to run]
            ok  	google.golang.org/protobuf/encoding/protodelim	0.116s
            ok  	google.golang.org/protobuf/encoding/protojson	0.186s
            ok  	google.golang.org/protobuf/encoding/prototext	0.194s
    ...
            --- FAIL: TestHasExtensionNoAlloc (0.02s)
                --- FAIL: TestHasExtensionNoAlloc/Eager (0.00s)
                    extension_test.go:156: proto.HasExtension should not allocate, but allocated 1.00x per run
            FAIL
            FAIL	google.golang.org/protobuf/proto	0.353s
            ok  	google.golang.org/protobuf/reflect/protodesc	0.141s
            ok  	google.golang.org/protobuf/reflect/protorange	0.226s
            ok  	google.golang.org/protobuf/reflect/protoreflect	0.071s
            ok  	google.golang.org/protobuf/reflect/protoregistry	0.122s
            ok  	google.golang.org/protobuf/testing/protocmp	0.185s
            ok  	google.golang.org/protobuf/testing/protopack	0.049s
            ok  	google.golang.org/protobuf/testing/prototest	1.064s
            ok  	google.golang.org/protobuf/types/dynamicpb	0.121s
            ok  	google.golang.org/protobuf/types/known/anypb	0.057s
            ok  	google.golang.org/protobuf/types/known/durationpb	0.011s
            ok  	google.golang.org/protobuf/types/known/fieldmaskpb	0.024s
            ok  	google.golang.org/protobuf/types/known/structpb	0.021s
            ok  	google.golang.org/protobuf/types/known/timestamppb	0.029s
            FAIL
    --- FAIL: TestIntegration/Go1.23.0/ProtoLegacy (66.75s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: log/syslog: TestConcurrentReconnect failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "log/syslog" && test == "TestConcurrentReconnect"
```

Issue created automatically to collect these failures.

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

    === RUN   TestConcurrentReconnect
        syslog_test.go:430: timeout in concurrent reconnect
    --- FAIL: TestConcurrentReconnect (0.29s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: archive/tar: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "archive/tar" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	archive/tar [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/compile/internal/abt: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/compile/internal/abt" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	cmd/compile/internal/abt [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/tools/cmd/gonew: Test/quote.txt failures [consistent failure]
Labels: NeedsInvestigation,Tools

```
#!watchflakes
default <- pkg == "golang.org/x/tools/cmd/gonew" && test == "Test/quote.txt"
```

Issue created automatically to collect these failures.

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

    === RUN   Test/quote.txt
        main_test.go:98: unexpected failure exit
        main_test.go:118: wrong stderr: diff want have
            --- want
            +++ have
            @@ -1,1 +1,10 @@
            -gonew: initialized my.com/test in ./test
            +gonew: go mod download -json example.com/quote@latest: exit status 1
            +{
            +	"Path": "example.com/quote",
            +	"Version": "v1.5.2",
            +	"Query": "latest",
            +	"Error": "example.com/quote@v1.5.2: read /"file:///opt/golang/swarm/.swarming/w/ir/x/t/Testquote.txt188249249/001/proxy/example.com/quote/@v/v1.5.2.zip/": write /opt/golang/swarm/.swarming/w/ir/x/w/gopath/pkg/mod/cache/download/example.com/quote/@v/v1.5.2.zip291328757.tmp: sendfile: invalid argument",
            +	"Info": "/opt/golang/swarm/.swarming/w/ir/x/w/gopath/pkg/mod/cache/download/example.com/quote/@v/v1.5.2.info",
            +	"GoMod": "/opt/golang/swarm/.swarming/w/ir/x/w/gopath/pkg/mod/cache/download/example.com/quote/@v/v1.5.2.mod",
            +	"GoModSum": "h1:fBZUP3qzh2hlMC+KYCP3wzEFXKFiObko2TCwsxUizdw="
            +}
        main_test.go:151: missing file out/test/go.mod
        main_test.go:151: missing file out/test/quote.go
        main_test.go:151: missing file out/test/quote/another.go
    --- FAIL: Test/quote.txt (0.05s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/compile: unrecognized failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "cmd/compile" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	cmd/compile [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/compile/internal/amd64: unrecognized failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "cmd/compile/internal/amd64" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	cmd/compile/internal/amd64 [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: svelte
Issue: Effect tracks entire store instead of properties used
Labels: documentation

### Describe the bug

If a property of a store is used in an effect, the entire store becomes a dependency. 

This is especially an issue when using something like superforms that stores formdata in a single store. Changing one field will cause all effects referencing any field to run.

### Reproduction

https://svelte.dev/playground/ca42f41442a549d1a37ec9c4073cb061?version=5.1.4

### Logs

_No response_

### System Info

```shell
System:
  OS: Linux 5.15 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
  CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400F
  Memory: 8.01 GB / 15.54 GB
  Container: Yes
  Shell: 5.8.1 - /usr/bin/zsh
Binaries:
  Node: 20.18.0 - ~/.nvm/versions/node/v20.18.0/bin/node
  Yarn: 1.22.22 - /mnt/c/Users/bayles/AppData/Local/pnpm/yarn
  npm: 10.8.2 - ~/.nvm/versions/node/v20.18.0/bin/npm
  pnpm: 9.12.3 - /mnt/c/Users/bayles/AppData/Local/pnpm/pnpm
npmPackages:
  svelte: ^5.1.4 => 5.1.2
```


### Severity

blocking an upgrade
Repository: PowerToys
Issue: [Peek] Images open blurry
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Peek

### Steps to reproduce

I open an image in Peek.

### ✔️ Expected Behavior

The image should look accurate.


### ❌ Actual Behavior

The image is not in focus. In this case, the text is blurred.

### Other Software

I am attaching a comparison between Peek and FastStone Image Viewer. As well as the original test image.

![Image](https://github.com/user-attachments/assets/8aee100f-7199-42a2-b43b-2a6ae28a0569)
![Image](https://github.com/user-attachments/assets/8c08df26-4f31-4063-afd7-c8f8d88d040d)
Repository: next.js
Issue: `cloneElement` in client component with async server component as children not working
Labels: bug

### Link to the code that reproduces this issue

https://github.com/darthmaim-reproductions/vercel-next.js-72034

### To Reproduce

1. Clone the reproduction
2. `npm i`
3. `npm run dev`
4. Open http://localhost:3000/ and observe error

### Current vs. Expected behavior

#### Current

When using `cloneElement` in a client component, and the children is an async server component, this error is thrown:
> Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
> Check the render method of `ClientComponent`.

When the server component is not `async` (or a client component), this just works.

Additionally, adding this line to the client component also makes this work:

```ts
if(children.$$typeof === Symbol.for('react.lazy')) { children = use(children._payload); }
```

#### Expected

Since `cloneElement` works for client components and non-async server components, I expected this to work async server components as well.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.6.0: Mon Jun 24 00:56:10 PDT 2024; root:xnu-8020.240.18.709.2~1/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 4
Binaries:
  Node: 22.8.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.2-canary.11 // Latest available version is detected (15.0.2-canary.11).
  eslint-config-next: N/A
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

This might be a bug in react and not in Next.js.

In earlier versions the children was reported as `<Lazy/>` in react-dev-tools and `cloneElement` was working, now it is shown as `{ $$typeof: Symbol(react.lazy) }` (when not using cloneElement to avoid the error).
Repository: opencv
Issue: Remove cuBLAS dependency with cuDNN >= 9.0.0
Labels: bug,category: gpu/cuda (contrib),category: dnn

### System Information

OpenCV version: 4.10
OS: Windows
Compiler: MSVC
CUDA version: 12.6
cuDNN version: 9.5.1

### Detailed description

Since version 9.0.0 cuDNN no longer depends on the cuBLAS library but on cuBLASLt instead.
https://docs.nvidia.com/deeplearning/cudnn/latest/release-notes.html#cudnn-9-0-0

Hoping to reduce the weight of dll that have to be shipped to perform inference using Cuda I tried to remove `cublas64_12.dll` from the distributed files, but it then fails to execute.
I then tried to get rid of cuBLAS dependancy when compiling OpenCV but enabling `WITH_CUBLAS=OFF` will result in
`> DNN: CUDA backend requires cuBLAS.  Please resolve dependency or disable`

Is there a way to get rid of that library with the right compilation flags?

### Steps to reproduce

Compile OpenCV

### Issue submission checklist

- [x] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: flutter
Issue: [a11y][iOS] TabBar does not work with iOS Voice Control
Labels: platform-ios,f: material design,a: accessibility,customer: money (g3),has reproducible steps,P1,found in release: 3.24,team-accessibility,triaged-accessibility,found in release: 3.27

### Steps to reproduce

1. Activate Voice Control from the settings app.
2. Open the sample code which uses TabBar.
3. Observe that you cannot navigate between tabs using Voice Control because there is no label for non-selected tabs.

b/345133676

### Expected results

You should be able to navigate between tabs using Voice Control.

### Actual results

There is only a single label for the tab bar, rather than individual labels for each tab.

### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

/// Flutter code sample for [TabBar].

void main() => runApp(const TabBarApp());

class TabBarApp extends StatelessWidget {
  const TabBarApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(useMaterial3: true),
      home: const TabBarExample(),
    );
  }
}

class TabBarExample extends StatelessWidget {
  const TabBarExample({super.key});

  @override
  Widget build(BuildContext context) {
    return DefaultTabController(
      initialIndex: 1,
      length: 3,
      child: Scaffold(
        appBar: AppBar(
          title: const Text('TabBar Sample'),
          bottom: const TabBar(
            tabs: <Widget>[
              Tab(
                icon: Icon(Icons.cloud_outlined),
              ),
              Tab(
                icon: Icon(Icons.beach_access_sharp),
              ),
              Tab(
                icon: Icon(Icons.brightness_5_sharp),
              ),
            ],
          ),
        ),
        body: const TabBarView(
          children: <Widget>[
            Center(
              child: Text("It's cloudy here"),
            ),
            Center(
              child: Text("It's rainy here"),
            ),
            Center(
              child: Text("It's sunny here"),
            ),
          ],
        ),
      ),
    );
  }
}
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

![Screenshot 2024-10-29 at 3 34 23 PM](https://github.com/user-attachments/assets/5e64e6f2-587e-4715-b277-66e952bdffd8)

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel google3, on macOS 14.7
    • Framework revision 2de487308a (0 days ago), 2024-10-29T00:00:00.000
    • Engine revision 0c8f0bf4d7
    • Dart version 6e55dfe774
```

</details>
Repository: go
Issue: archive/zip: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "archive/zip" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	archive/zip [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/compile/internal/compare: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/compile/internal/compare" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	cmd/compile/internal/compare [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: encoding/json: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "encoding/json" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	encoding/json [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/compile/internal/base: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/compile/internal/base" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	cmd/compile/internal/base [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Terminal profiles smoke test caused timeout
Labels: debt,smoke-test-failure,terminal-profiles

Build: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=301927
Changes: https://github.com/Microsoft/vscode/compare/22b0035...f992298

Terminal tests in this build were all very slow:

```
       ✔ should create a terminal in the editor area by default (117047ms)
      Terminal Input
        Auto replies
          ✔ should automatically reply to a custom entry (47570ms)
      Terminal Persistence
        detach/attach
          ✔ should support basic reconnection (48150ms)
          - should persist buffer content
      Terminal Profiles
        ✔ should launch the default profile
        ✔ should set the default profile to a contributed one
        ✔ should use the default contributed profile on panel open and for splitting (31984ms)
        ✔ should set the default profile (23498ms)
        ✔ should use the default profile on panel open and for splitting (24980ms)
        ✔ createWithProfile command should create a terminal with a profile
        ✔ createWithProfile command should create a terminal with a contributed profile
        ✔ createWithProfile command should create a split terminal with a profile (29530ms)
        ✔ createWithProfile command should create a split terminal with a contributed profile (48906ms)
```