sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_streams (__main__.TestCuda)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_streams&suite=TestCuda&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/29667386345).

Over the past 3 hours, it has been determined flaky in 6 workflow(s) with 18 failures and 6 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_streams`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 616, in test_streams
    tensor1 = torch.ByteTensor(5).pin_memory()
RuntimeError: Host and device pointer dont match with cudaHostRegister. Please dont use this feature by setting PYTORCH_CUDA_ALLOC_CONF=use_cuda_host_register:False (default)

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCuda.test_streams

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_cuda.py`

cc @ptrblck @msaroufim @clee2000
Repository: pytorch
Issue: DISABLED test_set_per_process_memory_fraction (__main__.TestCuda)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_set_per_process_memory_fraction&suite=TestCuda&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/29658230012).

Over the past 3 hours, it has been determined flaky in 3 workflow(s) with 9 failures and 3 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_set_per_process_memory_fraction`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 307, in test_set_per_process_memory_fraction
    self.assertTrue((tensor == 1).all())
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 685, in assertTrue
    if not expr:
RuntimeError: Host and device pointer dont match with cudaHostRegister. Please dont use this feature by setting PYTORCH_CUDA_ALLOC_CONF=use_cuda_host_register:False (default)

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_CUDA_MEM_LEAK_CHECK=1 python test/test_cuda.py TestCuda.test_set_per_process_memory_fraction

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_cuda.py`

cc @ptrblck @msaroufim @clee2000
Repository: PowerToys
Issue: PowerToys Run URI Handler without https /enhancement
Labels: Needs-Triage

### Description of the new feature / enhancement

The URI Handler plugin for PowerToys Run is great, except that I can use it to get to my local devices like my router, because it forces https. Would it be possible to add an option (a check box?) to allow for http instead. Maybe it could be an option when you input the URI, give two results, one with HTTPS, the second with HTTP.

### Scenario when this would be used?

When logging on to my router, local file server, etc...

### Supporting information

_No response_
Repository: PowerToys
Issue: RegistryPreview - Create backups of modified keys before writing to registry
Labels: Needs-Triage

### Description of the new feature / enhancement

Prompt the user to optionally create a backup of changed registry values prior to writing the changes, which can be used for a rollback.

### Scenario when this would be used?

When a registry modification causes issues and needs to be undone. Modifying the registry can be dangerous. This would mitigate much of the risk.

### Supporting information

Here is an example of a similar backup feature being used by CCleaner, which allows the user to easily revert registry modifications in case they cause issues.

![registry backup example](https://github.com/user-attachments/assets/575fb407-deba-480b-8baa-14eea67a9bc4)
Repository: ollama
Issue: Moondream2 needs an update
Labels: model request

moondream2 is an amazing tiny little VLM.  The owner (https://github.com/vikhyat) releases updates quite frequently.  I'm not sure which version ollama currently has, but there was a new release last week (2024-08-26) which is not in ollama.

https://huggingface.co/vikhyatk/moondream2
Repository: TypeScript
Issue: Error type on spreading array with additional props 
Labels: Bug,Help Wanted

### 🔎 Search Terms

array intersection spread any

### 🕗 Version & Regression Information

- This is the behavior in every version I tried


### ⏯ Playground Link

https://tsplay.dev/wOdoMN

### 💻 Code

```ts
type withExtraProps = extractArray<{ name: string } & string[]>;
//   ^? any[]

type extractArray<t extends readonly unknown[]> = [...{ [i in keyof t]: t[i] }];
```


### 🙁 Actual behavior

Inferred as `any[]` due to an internal error type

### 🙂 Expected behavior

Inferred as `string[]`

### Additional information about the issue

@Andarist mentioned this could be related to https://github.com/microsoft/TypeScript/issues/59260
Repository: pytorch
Issue: benchmarks/dynamo/timm_models.py starts installing binary distribution of PyTorch if torchvision is not installed
Labels: module: ci,triaged,oncall: pt2

### 🐛 Describe the bug

The reason is because we pip install timm_models, which has a dependency on torchvision, and if there's not a working install of torchvision it tries to get the binary distribution, which will in turn pull pytorch. Maybe we make the pip command say "do not install dependencies" or something.

### Versions

main

cc @seemethere @malfet @pytorch/pytorch-dev-infra @chauhang @penguinwu
Repository: ollama
Issue: cuda device unavailable error results in failed memory update leading to concurrent model load when no space actually available
Labels: bug,nvidia

### What is the issue?

```
ollama run llama3.1 (is ok)
```
switch to a different terminal
```
ollama run yi-coder
Error: llama runner process has terminated: CUDA error
ollama run llama3.1 (is ok)
```


### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.9
Repository: deno
Issue: Bug: patch feature silently fails on invalid `exports` map
Labels: bug,jsr,patch

Took me a couple of hours to narrow this down. When you use `patch` to point to a local JSR dependency, it will always ignore it when the `export` map contains an error. This is not obvious to the user as no error message is shown, not even in the internal logs.

## Steps to reproduce

1. Clone https://github.com/marvinhagemeister/deno-patch-bug-report
2. Run `cd bar`
3. Run `deno run -A mod.ts`

Output:

```sh
error: JSR package not found: @deno/i-dont-exist-yet
    at file:///Users/marvinh/dev/test/deno-patch-pre/bar/mod.ts:1:21
```

Reason it fails is because of an invalid entry key in the `exports` map in `foo/deno.json`:

```diff
  {
    "name": "@deno/i-dont-exist-yet",
    "version": "0.0.1",
    "exports": {
      ".": "./mod.ts",
-    "types": "./types.ts"
+    "./types": "./types.ts"
    }
  }
```

After this change it works as expected. We should show a big fat error when the exports mapping is wrong and abort, rather than silently falling back to fetching the package from the JSR registry.

Version: deno 2.0.0-rc.0+c58a628
Repository: flutter
Issue: Migrate flutter packages artifact hub usage to prevent using non google hosted dependencies. 
Labels: P2,infra: security,team-android,triaged-android

In https://github.com/flutter/flutter/issues/120119 we added a google provided repository. If artifacts are not found in this repo we fallback to maven or the public google repo. We should consider using maven profiles or limiting fallback so that if an artifact is not found in artifact hub (known internally as airlock) then the build fails. 

There is a availability risk to balance against a security risk where airlock removed a known dangerous dependency and we continued to build anyway. 
https://blog.gradle.org/maven-pom-profiles
Repository: react-native
Issue: (iOS) - NativeCommands fail in ref functions if batchRenderingUpdatesInEventLoop is active
Labels: Platform: iOS,Issue: Author Provided Repro,Newer Patch Available,Type: New Architecture

### Description

### Problem
Starting in version `0.74.1` and above, due to this [change](https://github.com/facebook/react-native/pull/43396/files), the `batchRenderingUpdatesInEventLoop` feature flag is turned ON. This causes NativeCommands called in `ref` functions to fail. 
```
<RTNCenteredText
  {...props}
  ref={element => {
    if (element) {
      Commands.trigger(element); // <-- trigger will not be called natively if batchRenderingUpdatesInEventLoop is turned ON
    }
  }}
/>
```

The corresponding NativeCommand:
```
// RTNCenteredText.mm
- (void)trigger {
    NSLog(@"*** Fabric component trigger method called directly");
}

- (void)handleCommand:(const NSString *)commandName args:(const NSArray *)args {
    NSString *TRIGGER = @"trigger";
    if([commandName isEqual:TRIGGER]) {
        [self trigger];
    }
}
```
### Diagnosis
The NativeCommand `trigger` fails because when [synchronouslyDispatchCommandOnUIThread](https://github.com/facebook/react-native/blob/2b11131247f09ab41c053625d70f65881d20f19b/packages/react-native/React/Fabric/Mounting/RCTMountingManager.mm#L323C9-L323C47) gets called, `findComponentViewWithTag` returns `nil` because the [_registry](https://github.com/facebook/react-native/blob/2b11131247f09ab41c053625d70f65881d20f19b/packages/react-native/React/Fabric/Mounting/RCTComponentViewRegistry.mm#L83) does not contain the element. 

When `batchRenderingUpdatesInEventLoop` is off, the `_registry` is correctly populated with all elements on the screen, and the NativeCommand `trigger` functions correctly.

If `Commands.trigger` is wrapped in a `setTimeout`, it gets called successfully.

```
<RTNCenteredText
  {...props}
  ref={element => {
    if (element) {
      setTimeout(() => {
        Commands.trigger(element); // <-- trigger gets called successfully
      }, 0);
    }
  }}
/>
```    

### Steps to reproduce

See the [reproducer](https://github.com/RyanCommits/RN74-issue-reproducer) provided.

1. Use `codegenNativeComponent` and `codegenNativeCommands` to create a `NativeCommand`
2. Call the created `NativeCommand` in a `ref` function 
3. See that the `NativeCommand` does NOT get called in versions `>=0.74.1`

### React Native Version

0.74.5

### Affected Platforms

Runtime - iOS

### Areas

JSI - Javascript Interface, Bridgeless - The New Initialization Flow

### Output of `npx react-native info`

```text
N/A
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://github.com/RyanCommits/RN74-issue-reproducer

### Screenshots and Videos

_No response_
Repository: go
Issue: x/telemetry: download the upload config lazily
Labels: telemetry

This is a follow up to #68946. To fix that issue for go 1.23.1, we did the absolutely narrowest fix to suppress the telemetry config download if the telemetry mode is not `"on"`.

However, we should also make the download lazy, so that we download the config once a week when there is actual work to upload, rather than once a day when the upload process runs.

We could also consider back-porting this fix to 1.23.2, as I think it will be a safe change.
Repository: flutter
Issue: ProcessException: Process exited abnormally with exit code -2:  Command: /usr/bin/arch -arm64e xcrun xcodebuild -list
Labels: c: crash,tool,P2,team-ios,triaged-ios

As of today (9/4), this crash affected 88 unique clients.

command: `flutter build ipa`

```
ProcessException: Process exited abnormally with exit code -2:  Command: /usr/bin/arch -arm64e xcrun xcodebuild -list
at RunResult.throwException(process.dart:122)
at _DefaultProcessUtils.run(process.dart:370)
at <asynchronous gap>(async)
at XcodeProjectInterpreter.getInfo(xcodeproj.dart:342)
at <asynchronous gap>(async)
at XcodeBasedProject.projectInfo(xcode_project.dart:155)
at <asynchronous gap>(async)
at IosProject.buildSettingsForBuildInfo(xcode_project.dart:442)
at <asynchronous gap>(async)
at IosProject._parseHostAppBundleName(xcode_project.dart:416)
at <asynchronous gap>(async)
at IosProject.hostAppBundleName(xcode_project.dart:405)
at <asynchronous gap>(async)
at BuildableIOSApp.fromProject(application_package.dart:116)
at <asynchronous gap>(async)
at FlutterApplicationPackageFactory.getPackageForPlatform(flutter_application_package.dart:82)
at <asynchronous gap>(async)
at _BuildIOSSubCommand.buildableIOSApp.<anonymous closure>(build_ios.dart:651)
at <asynchronous gap>(async)
at _BuildIOSSubCommand.runCommand(build_ios.dart:688)
at <asynchronous gap>(async)
at BuildIOSArchiveCommand.runCommand(build_ios.dart:427)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1408)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:212)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:420)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:364)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:130)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at main(executable.dart:93)
at <asynchronous gap>(async)
```
Repository: terminal
Issue: Disable Mica when window is out of focus
Labels: Issue-Feature,Product-Terminal,Area-Theming

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

PR #17858 Added MicaAlt support and it looks so good that Windows Terminal now looks like a more modern and beautiful PowerShell ISE if you use the default Windows dark theme. But if Windows Terminal loses focus, it becomes ugly again.

Maybe consider add an option to enable Mica only when Windows Terminal get focus, otherwise disable Mica to re-allow acrylic style.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: terminal
Issue: Make acrylic style work for “Settings” too
Labels: Product-Terminal,Issue-Task,Area-SettingsUI

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

The Mica style works on the whole window, so the “Settings” are prettier, but the Acrylic style doesn't look like that.
![image](https://github.com/user-attachments/assets/c4fc4ad3-6841-4bda-a830-f4c6d3754977)
![image](https://github.com/user-attachments/assets/611b7a11-d77c-4c37-afe9-35355c6d4472)

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: go
Issue: proposal: math: add Mean, Median, Mode, Variance, and StdDev
Labels: Proposal

**Description**:

This proposal aims to enhance the Go standard library’s `math` ( `math/stats.go` )package by introducing several essential statistical functions. The proposed functions are:

- **Mean**: Calculates the average value of a data set.
- **Median**: Determines the middle value when the data set is sorted.
- **Mode**: Identifies the most frequently occurring value in a data set.
- **Variance**: Measures the spread of the data set from the mean.
- **StdDev**: Computes the standard deviation, providing a measure of data dispersion.
and many more....

**Motivation**:

The inclusion of these statistical functions directly in the `math` package will offer Go developers robust tools for data analysis and statistical computation, enhancing the language's utility in scientific and financial applications. Currently, developers often rely on external libraries for these calculations, which adds dependencies and potential inconsistencies. Integrating these functions into the standard library will:

- **Provide Comprehensive Statistical Analysis**: These functions will facilitate fundamental statistical measures, aiding in more thorough data analysis and better understanding of data distributions.
- **Ensure Reliable Behavior**: Functions are designed to handle edge cases, such as empty slices, to maintain predictable and accurate results.
- **Optimize Performance and Accuracy**: Implemented with efficient algorithms to balance performance with calculation accuracy.
- **Increase Utility**: Reduces the need for third-party libraries, making statistical computation more accessible and consistent within the Go ecosystem.

**Design**:

The functions will be added to the existing `math` package, ensuring they are easy to use and integrate seamlessly with other mathematical operations. Detailed documentation and examples will be provided to illustrate their usage and edge case handling.

**Examples**:

- **Mean**:
  ```go
  mean := math.Mean([]float64{1, 2, 3, 4, 5})
  ```
- **Median**:
  ```go
  median := math.Median([]float64{1, 3, 3, 6, 7, 8, 9})
  ```
- **Mode**:
  ```go
  mode := math.Mode([]float64{1, 2, 2, 3, 4})
  ```
- **Variance**:
  ```go
  variance := math.Variance([]float64{1, 2, 3, 4, 5})
  ```
- **StdDev**:
  ```go
  stddev := math.StdDev([]float64{1, 2, 3, 4, 5})
  ```
---
<!-- Generated by Oscar. DO NOT EDIT. {"bot":"gabyhelp","kind":"overview"} -->
@gabyhelp's overview of this issue: https://github.com/golang/go/issues/69264#issuecomment-2593973713
<!-- oscar-end -->
Repository: flutter
Issue: [google_maps_flutter_ios] Failing native tests
Labels: c: regression,team,platform-ios,p: maps,package,P2,c: disabled test,team-ios,triaged-ios

The native tests in [GoogleMapsUITests.m](https://github.com/flutter/packages/blob/main/packages/google_maps_flutter/google_maps_flutter_ios/example/ios14/ios/RunnerUITests/GoogleMapsUITests.m) are consistently failing locally and on CI for Flutter main branch. I've also noticed this has been failing for over a week.

```
/Volumes/Work/s/w/ir/x/w/packages/packages/google_maps_flutter/google_maps_flutter_ios/example/ios14/ios/RunnerUITests/GoogleMapsUITests.m:53: error: -[GoogleMapsUITests testUserInterface] : failed - Failed due to not able to find User interface
    t =    63.39s Tear Down
Test Case '-[GoogleMapsUITests testUserInterface]' failed (63.614 seconds).
Test Suite 'GoogleMapsUITests' failed at 2024-09-03 11:59:47.863.
	 Executed 4 tests, with 4 failures (0 unexpected) in 256.426 (256.427) seconds
Test Suite 'RunnerUITests.xctest' failed at 2024-09-03 11:59:47.863.
	 Executed 4 tests, with 4 failures (0 unexpected) in 256.426 (256.428) seconds
Test Suite 'All tests' failed at 2024-09-03 11:59:47.864.
	 Executed 4 tests, with 4 failures (0 unexpected) in 256.426 (256.429) seconds
2024-09-03 12:00:13.009 xcodebuild[50120:308772] [MT] IDETestOperationsObserverDebug: 291.207 elapsed -- Testing started completed.
2024-09-03 12:00:13.009 xcodebuild[50120:308772] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2024-09-03 12:00:13.009 xcodebuild[50120:308772] [MT] IDETestOperationsObserverDebug: 291.207 sec, +291.207 sec -- end

Test session results, code coverage, and logs:
	/Users/chrome-bot/Library/Developer/Xcode/DerivedData/Runner-bynswbqjzzfjuuheqrjysabjmvyt/Logs/Test/Run-Runner-2024.09.03_11-54-50--0700.xcresult

Failing tests:
	-[GoogleMapsUITests testMapClickPage]
	-[GoogleMapsUITests testMapCoordinatesPage]
	-[GoogleMapsUITests testMarkerDraggingCallbacks]
	-[GoogleMapsUITests testUserInterface]

** TEST FAILED **

Testing started

[packages/google_maps_flutter/google_maps_flutter_ios completed in 6m 23s]
```

See https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8737792882371508001/+/u/Run_package_tests/native_test/stdout?format=raw for full logs.

The problem seems to be that `XCUIElement` is failing to find the Flutter element in the example app:

<img width="948" alt="Screenshot 2024-09-04 at 3 36 08 PM" src="https://github.com/user-attachments/assets/c2031a2c-f6f3-43fc-9448-6e32cd8eb184">
Repository: pytorch
Issue: TORCH_CPP_LOG_LEVEL cannot enable VLOG
Labels: module: logging,triaged

### 🐛 Describe the bug

When not using GLOG, the `VLOG` macro is implemented as a negative severity: 
https://github.com/pytorch/pytorch/blob/eb0fd17bc451b604b7d7ed7981c4197666f4dd6e/c10/util/logging_is_not_google_glog.h#L95-L97

The severity is then compared with `FLAGS_caffe2_log_level`:
https://github.com/pytorch/pytorch/blob/eb0fd17bc451b604b7d7ed7981c4197666f4dd6e/c10/util/Logging.cpp#L415-L418

However, the flag at runtime comes from the `TORCH_CPP_LOG_LEVEL` envvar, which only supports 4 pre-defined severity levels:
https://github.com/pytorch/pytorch/blob/eb0fd17bc451b604b7d7ed7981c4197666f4dd6e/c10/util/Logging.cpp#L506-L539

As a result, when GLOG is not built, there is no way to control whether to print VLOG messages or not. 

One potential fix could be to allow a negative `TORCH_CPP_LOG_LEVEL`.

### Versions

github main