sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: Can't build adev (bazel error)
Labels: area: docs-infra

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

I get this weird error from bazel when I try build adev

### Please provide a link to a minimal reproduction of the bug

I followed every step here https://github.com/angular/angular/blob/main/adev/README.md, also tried cleaning after error but did not help

### Please provide the exception or error you saw

```true
ERROR: C:/users/cros4/desktop/angular/packages/zone.js/BUILD.bazel:19:8: Executing genrule //packages/zone.js:LICENSE_wrapped failed: (Exit -1): bash.exe failed: error executing command c:\tools\msys64\usr\bin\bash.exe -c ... (remaining 1 argument skipped)
Action failed to execute: java.io.IOException: ERROR: src/main/native/windows/process.cc(202): CreateProcessW("c:\tools\msys64\usr\bin\bash.exe" -c "source external/bazel_tools/tools/genrule/genrule-setup.sh; (echo '/**
 @license' && cat LICENSE && echo '*/') > bazel-out/x64_windows-fastbuild/bin/packages/zone.js/LICENSE.wrapped"): Can't find specified file.
 (error: 2)
Target //adev:serve failed to build
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
OS: win32 x64
```

### Anything else?

_No response_
Repository: flutter
Issue: [Android] Dragging outside the text should not show the magnifier
Labels: platform-android,P2,team-text-input,triaged-text-input

### Steps to reproduce

 1. Run an app with a text field (such as given below) on an Android device.
 2. Enter some text.
 3. Perform a drag inside the field but not on any of the text.

### Expected results

The magnifier hides whenever the drag leaves the text.

### Actual results

The magnifier is shown during the whole drag.

### Code sample

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: const <Widget>[
            TextField(
            ),
          ],
        ),
      ),
    );
  }
}
```

</details>


### Screenshots or Video

<details open>
<summary>Video of native Android</summary>


https://github.com/user-attachments/assets/03f2f56a-25ec-47f7-be21-26b9037c4be1



</details>

<details open>
<summary>Video of Flutter</summary>



https://github.com/user-attachments/assets/a295f2ee-5978-400a-a09f-97fd4760ebc6

</details>

Discovered while working on https://github.com/flutter/flutter/pull/148784.

### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
flutter doctor
Building flutter tool...
Resolving dependencies... (1.0s)
Downloading packages... 
Got dependencies.
Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel [user-branch], 3.22.0-35.0.pre.2441, on Debian GNU/Linux rodete 6.9.10-1rodete5-amd64, locale en_US.UTF-8)
    ! Flutter version 3.22.0-35.0.pre.2441 on channel [user-branch] at /usr/local/google/home/jmccandless/Projects/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2023.3)
[✓] Connected device (3 available)
[✓] Network resources

! Doctor found issues in 1 category.

```

</details>
Repository: opencv
Issue: Assertion error when flipping arrays with more than 512 channels
Labels: bug,category: python bindings

### System Information

OpenCV python version: 4.10.0.84
Operating System / Platform: MacOS 15.1.1
Python version: 3.12.7

### Detailed description

Flipping arrays with more than 512 channels (third dimension) throws the following assertion error:
```
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
cv2.error: OpenCV(4.10.0) /Users/xperience/GHA-Actions-OpenCV/_work/opencv-python/opencv-python/opencv/modules/core/src/matrix_transform.cpp:784: error: (-215:Assertion failed) _src.dims() <= 2 in function 'flip'
```

### Steps to reproduce

```python
import cv2
import numpy as np

# Works
arr1 = np.zeros((256, 256, 512), dtype=np.uint8)
cv2.flip(arr1, 0)

# Throws error: (-215:Assertion failed)
arr2 = np.zeros((256, 256, 513), dtype=np.uint8)
cv2.flip(arr2, 0)
```

### 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: pytorch
Issue: Dynamo graph break on RNN/LSTM doesn't resume the function correctly.
Labels: triaged,bug,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Dynamo purposely graph breaks on RNN, GRU, LSTMs. We expect the sub modules before and after the RNN/GRU/LSTM calls should be compiled as partial graphs, however, we found only the sub modules before the graph break got compiled, the one after doesn't.
Repro:
```
import torch
import torch.nn as nn
import torch.nn.functional as F

class MultiLayerModel(nn.Module):
    def __init__(self, input_dim, lstm_hidden_dim, conv_channels, linear_out_dim, num_classes):
        super(MultiLayerModel, self).__init__()
        
        # Convolutional layer
        self.conv = nn.Conv2d(in_channels=1, out_channels=conv_channels, kernel_size=3, stride=1, padding=1)
        
        # Layer normalization for convolution output
        self.conv_layer_norm = nn.LayerNorm([conv_channels, input_dim, input_dim])
        
        # LSTM layer
        self.lstm = nn.LSTM(input_dim, lstm_hidden_dim, batch_first=True, bidirectional=True)
        
        # Fully connected linear layers
        self.fc1 = nn.Linear(lstm_hidden_dim * 2, linear_out_dim)  # LSTM is bidirectional, so hidden_dim * 2
        self.fc2 = nn.Linear(linear_out_dim, num_classes)
        
        # Layer normalization for linear layers
        self.linear_layer_norm = nn.LayerNorm(linear_out_dim)
        
    def forward(self, x):
        # Convolutional layer expects 4D input: (batch_size, channels, height, width)
        x = self.conv(x)
        x = F.relu(x)
        x = self.conv_layer_norm(x)
        
        # Flatten spatial dimensions for the LSTM (assuming square input images)
        batch_size, channels, height, width = x.size()
        x = x.view(batch_size, channels * height, width)  # Prepare for LSTM: (batch, seq_len, features)
        
        # LSTM expects input: (batch_size, seq_len, input_dim)
        x, _ = self.lstm(x)
        
        # Fully connected layers
        x = F.relu(self.fc1(x[:, -1, :]))  # Use the output from the last time step
        x = self.linear_layer_norm(x)
        x = self.fc2(x)
        
        return x
    
input_dim = 28
lstm_hidden_dim = 128
conv_channels = 16
linear_out_dim = 64
num_classes = 10

model = MultiLayerModel(input_dim, lstm_hidden_dim, conv_channels, linear_out_dim, num_classes)
print(model)

model = torch.compile(model)
# Dummy input: Batch of grayscale images (batch_size, channels, height, width)
dummy_input = torch.randn(8, 1, 28, 28)
output = model(dummy_input)
print("Output shape:", output.shape)
```
Run this script with ```TORCH_LOGS=+dynamo```, you will find there is only one compiled graph which includes the sub module befroe line ```x = x.view(batch_size, channels * height, width)```.

### Versions

N/A

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: go
Issue: build: build failure on go1.23-linux-amd64_c3h88-perf_vs_release
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "go1.23-linux-amd64_c3h88-perf_vs_release" && repo == "go" && mode == "build"
```

Issue created automatically to collect these failures.

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

    go: downloading github.com/BurntSushi/toml v1.0.0
    go: downloading github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51
    2024/11/19 18:09:12 Load average: 0.67 0.20 0.07 1/1176 1834
    2024/11/19 18:09:12 Waiting for load average to drop below 0.20...
    2024/11/19 18:09:42 Load average: 0.47 0.19 0.07 1/1177 1834
    2024/11/19 18:09:42 Waiting for load average to drop below 0.20...
    2024/11/19 18:10:12 Load average: 0.28 0.17 0.07 2/1177 1834
    2024/11/19 18:10:12 Waiting for load average to drop below 0.20...
    2024/11/19 18:10:42 Load average: 0.23 0.17 0.07 3/1180 1834
    2024/11/19 18:10:42 Waiting for load average to drop below 0.20...
    ...
    [sweet] Running benchmark tile38 for experiment: run 8
    [sweet] Running benchmark tile38 for baseline: run 8
    [sweet] Running benchmark tile38 for experiment: run 9
    [sweet] Running benchmark tile38 for baseline: run 9
    [sweet] Running benchmark tile38 for experiment: run 10
    [sweet] Running benchmark tile38 for baseline: run 10
    [sweet] error: failed to execute benchmarks: gvisor
    2024/11/19 23:45:15 Error running sweet: error running sweet run: exit status 1
    2024/11/19 23:45:15 FAIL
    exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Problems with Taskbar and selecting with the Mouse
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

I've been using PowerToys in its various iterations in Windows for more than a decade.  I realize the recent incarnation is new and unrelated to versions that ran on earlier versions of Windows.  Kudos to all those who work on these wonderful toys.

I cannot give specifics, nor do I want to duplicate the steps that led to the problem, but coincidental to updating PowerToys last week, I've had problems with selecting items in the Taskbar (what we used to call the System Tray).  I attempted to disable various toys related to the mouse to correct the issue, but with no luck.  I ended up uninstalling PowerToys, rebooting, and then reinstalling directly from the Microsoft PowerToys site.  Co far, all looks good.

### ✔️ Expected Behavior

I expect to be able to select items in the System Tray and interact with them.

### ❌ Actual Behavior

The mouse worked everywhere except in the System Tray.

### Other Software

I uninstalled PowerToys, rebooted, and reinstalled.  I do not know the previous version, but I updated last week, so it too was likely 0.86.0.
Repository: go
Issue: proposal: testing: add additional data to testing.T.Context
Labels: Proposal

### Proposal Details

The accepted proposal https://github.com/golang/go/issues/36532 added a Context method to `testing.T`, which is great, but I can think of two straightforward ways to improve its usefulness further:

1. Expose `T.Deadline()` as the deadline for the context.  There are (hopefully rare) cases where something needs to propagate deadline information to something that isn't go, e.g. a subprocess, where simple cancelation may not be sufficient.  Even in cases where the final consumer of the context is go, it's helpful for e.g. logging to be able to distinguish between a context cancelled due to a timeout vs. cancelled for some other reason.  This should be as simple as swapping out `context.WithCancel` for `context.WithDeadline` where appropriate.
2. Create a `trace.Task` named for the test.  When running a trace or benchmark with `-trace`, it can be handy to be able to track back regions to specific tests.  This, too, is fairly low-cost given that the `testing` package already depends on `runtime/trace`.
Repository: deno
Issue: Wasm module importing specifier that can't be resolved is missing referrer in error message
Labels: bug,wasm,dx

```wat
;; toolkit.wat
(module
  (import "env" "get_time_in_seconds" (func $get_time (result i32)))

  (func (export "getValue") (result i32)
    call $get_time
  )
)
```

```js
// env.ts
function getTimeInSeconds() {
  return Date.now() / 1000;
}

export { getTimeInSeconds as get_time_in_seconds };
```

```js
// main.ts
import { getValue } from "./toolkit.wasm";

console.log(getValue());
```

Actual:


```shellsession
> wat2wasm toolkit.wat
> deno run main.ts
error: Relative import path "env" not prefixed with / or ./ or ../
```

Expected:

```shellsession
> wat2wasm toolkit.wat
> deno run main.ts
error: Relative import path "env" not prefixed with / or ./ or ../
    at file:///.../toolkit.wasm
```
Repository: deno
Issue: Import map unfurl Wasm module import specifiers on publish
Labels: bug,publish

Publishing a module to JSR should unfurl the import specifiers inside a Wasm module.
Repository: next.js
Issue: Catch-all route also intercepts and catches static assets and js chunks
Labels: bug,Navigation,Runtime

### Link to the code that reproduces this issue

https://github.com/r6203/next-catch-all-bug

### To Reproduce

1. Create a catch-all route
2. run `next dev`
3. go to any static route or js chunk or view server logs to see chunks intercepted


### Current vs. Expected behavior

Having a catch all route at the root of the app shouldn't intercept next generated assets or static assets.

Expect a working app where each non asset request resolves to the catch-all route but requests to next generated assets (_next/**/*) to resolve to the corresponding files.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
  Available memory (MB): 60075
  Available CPU cores: 16
Binaries:
  Node: 22.2.0
  npm: 10.7.0
  Yarn: N/A
  pnpm: 9.9.0
Relevant Packages:
  next: 14.2.12 // An outdated version detected (latest is 15.0.3), upgrade is highly recommended!
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Navigation, Runtime

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

next dev (local), next start (local)

### Additional context

For an in-production example of this issue with a workaround see https://github.com/session-foundation/websites/tree/main/apps/foundation

Note this is reopening this issue https://github.com/vercel/next.js/issues/67806
Repository: godot
Issue: [4.3] Using color picker in Project Settings doesn't stick
Labels: bug,topic:editor,needs testing

### Tested versions

Reproducible in 4.3.stable

Not reproducible in 4.2.2.stable, 4.4.dev3

### System information

Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org Vulkan 1.3.250 - Forward+ - Using Device #0: Intel - Intel(R) Iris(R) Xe Graphics

### Issue description

Changing the Default Clear Color from Project Settings by using the color picker outside of the Godot window fails to update when program is run.  The color preview for the Default Clear Color changes appropriately in Project Setting and even the editor preview changes, however when the program is run it uses the previous value Default Clear Color. If Project Settings is reopened it still shows the picked color. However, if the project is reloaded the Default Clear Color reverts to the previous value in Project setting, editor preview, and when running the program.

I confirmed the same behavior when changing the Debug Shape Color and I assume it is the same for all the others.

I tested for similar behavior on modulate in the inspector however it worked correctly.  

(Note: I am not using Single Window Mode - the color is picking fine just not sticking)

PS - First bug report, let me know if there is anything I missed!

### Steps to reproduce

1. Add a Node2D node and save the program.
2. Go to Project Settings
3. Change Default Clear Color using color picker outside of Godot window
4. Run program

### Minimal reproduction project (MRP)

N/A
Repository: kubernetes
Issue: Add support for environment variable resolution in `httpGet` probe paths
Labels: sig/node,kind/feature,needs-triage

Currently, Kubernetes does not support resolving environment variables in `httpGet` probe paths, which limits configuration flexibility.

Expected behavior:
- Allow environment variable interpolation like `path: "$(CONTEXT_PATH)/health/"`
- ~~Support standard shell-like variable substitution syntax~~

Sample configuration:
```yaml
       readinessProbe:
          httpGet:
            path: "$(CONTEXT_PATH)/actuator/health/readiness"
            port: 8080
            scheme: HTTP

```
Repository: pytorch
Issue: LoweringException: AttributeError: 'Constant' object has no attribute 'get_name'
Labels: oncall: export

### 🐛 Describe the bug

repros:
```
import torch
from torchvision.models.regnet import regnet_y_8gf

device = "cuda"

model = regnet_y_8gf(weights=None, progress=True, num_classes=256).to(device)
args = (torch.randn(1, 3, 224, 224, device=device),)

_ = model(*args)

ep = torch.export.export(model, args, strict=False)
_ = torch._inductor.aot_compile(ep.module(), args)
```

error:
```
/torch/_inductor/ir.py", line 3524, in realize_into
    V.graph.mark_buffer_mutated(dst.get_name())
torch._inductor.exc.LoweringException: AttributeError: 'Constant' object has no attribute 'get_name'
  target: aten.copy_.default
  args[0]: Constant(dtype=torch.int64, device=device(type='cuda', index=0), value=1)
  args[1]: TensorBox(StorageBox(
    Pointwise(
      'cuda',
      torch.int64,
      def inner_fn(index):
          tmp0 = ops.constant(2, torch.int64)
          return tmp0
      ,
      ranges=[],
      origin_node=full_default,
      origins=OrderedSet([full_default])
    )
  ))
```

### Versions

trunk

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: material-ui
Issue: [docs][TypeScript] Add examples of how to extend types from MUI components
Labels: typescript,support: docs-feedback

### Related page

https://mui.com/material-ui/

### Kind of issue

Other

### Issue description

Let me start by saying that I am using a translator and I hope my message will be understood.
I have always had problems with creating custom components based on MUI components. The problem is the typing of such components.
List of examples I would like to see:
1. Typing of components that have `component` props.
    - I don't understand how to take all the props of let's say `Box` component, add some of my own (mandatory and non-mandatory) props to them. And to add props from `component` when specifying `component`.
2. Typing of components that have `variant` in their generics (for example, if we take `TextFieldProps`).
3. Typing of more complex components such as `Button`.
4. How to type it all if we need to wrap everything in `forwardRef`.
   - How to define the element type for `ref` (HTMLDivElement, HTMLButtonElement, etc.).
   - It's also worth considering this type if a component is passed in `component`.
5. Also for all this I would like to see an example where we remove some props from the component and/or replace them with our own. For example in a `Chip` component I would like to be able to pass `children` and they would be placed in the props `label`, with the props `label` itself removed from the typing props (I don't know how to explain it).

(Important: The point is not to change the theme of some component, but to add your logic to it.)

If you could add a new page and/or to the component page examples of how to create a component based on that component - that would be awesome.

I realize it would take a lot of time to add this to the documentation, so I would like to see these examples under my Issue.

Thank you for your work and efforts!

### Context

_No response_

**Search keywords**: no
Repository: tauri
Issue: [bug] run android dev error On Win10
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug
not work

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
npm run tauri android init
npm run tauri android dev
```


### Stack trace
 Compiling quote v1.0.36
   Compiling libc v0.2.155
   Compiling cfg-if v1.0.0
   Compiling hashbrown v0.14.5
   Compiling rand_core v0.5.1
   Compiling rand v0.8.5
   Compiling windows-targets v0.52.5
   Compiling equivalent v1.0.1
error[E0463]: can't find crate for `core`
  |
  = note: the `x86_64-linux-android` target may not be installed
  = help: consider downloading the target with `rustup target add x86_64-linux-android`

For more information about this error, try `rustc --explain E0463`.
error: could not compile `cfg-if` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `libc` (lib) due to 1 previous error
error: script "dev" exited with code 255
`Failed to run `cargo build`: command ["cargo", "build", "--package", "mobile-rss", "--manifest-path", "E:\\test\\tauri-app\\src-tauri\\Cargo.toml", "--target", "x86_64-linux-android", "--lib"] exited with code 101
    Error `Failed to run `cargo build`: command ["cargo", "build", 

### Additional context

_No response_
Repository: PowerToys
Issue: Power-Toys automatically reported error when turn on my computer
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

[PowerToysReport_2024-11-21-06-06-27.zip](https://github.com/user-attachments/files/17839222/PowerToysReport_2024-11-21-06-06-27.zip)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: pytorch
Issue: DISABLED test_while_loop_schema_gen (__main__.TestHopSchema)
Labels: triaged,module: flaky-tests,skipped,module: functorch

Platforms: asan, linux, rocm, slow, mac, macos





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

Over the past 3 hours, it has been determined flaky in 128 workflow(s) with 256 failures and 128 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_while_loop_schema_gen`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `functorch/test_control_flow.py`

cc @clee2000 @zou3519 @Chillee @samdow @kshitij12345