sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [bug] documentPictureInPicture window does not apply appropriate display-mode: picture-in-picture CSS media tag 
Labels: type: bug,status: needs triage

### Describe the bug

As the title says, it seems that Tauri on Windows does not render the appropriate `@media (display-mode: picture-in-picture)` CSS rules correctly for documentPictureInPicture pop-outs. It works on Windows both on Edge and Chrome [according to the spec](https://developer.mozilla.org/en-US/docs/Web/API/Document_Picture-in-Picture_API/Using#target_styles_when_in_picture-in-picture_mode), but for some reason Tauri does not load / render the CSS rules correctly.

### Reproduction

Run the example from MDN in a Tauri app on Windows: https://mdn.github.io/dom-examples/document-picture-in-picture/
A PiP window will open correctly, but it won't show the "mute" button according to the CSS rules. An even simpler way to reproduce would be opening a documentPiP window with the following CSS code:
```css
@media (display-mode: picture-in-picture) {
  body {
    background: red;
  }
}
```
Now opening any element in a window.documentPictureInPicture window should have a red background on Tauri, but does not.

### Expected behavior

The PiP window should render all `@media (display-mode: picture-in-picture)` rules, like it does on Chrome & Edge on Windows.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 x86_64 (X64)
    ✔ WebView2: 130.0.2849.56
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.15.0
    - npm: 10.7.0

[-] Packages
    - tauri 🦀: 2.0.1
    - tauri-build 🦀: 2.0.1
    - wry 🦀: 0.44.1
    - tao 🦀: 0.30.3
    - @tauri-apps/api : 2.0.3
    - @tauri-apps/cli : 2.0.5

[-] Plugins
    - tauri-plugin-os 🦀: 2.0.1
    - @tauri-apps/plugin-os : 2.0.0
    - tauri-plugin-shell 🦀: 2.0.1
    - @tauri-apps/plugin-shell : not installed!
    - tauri-plugin-process 🦀: 2.0.1
    - @tauri-apps/plugin-process : 2.0.0
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : 2.0.0
    - tauri-plugin-window-state 🦀: 2.0.1
    - @tauri-apps/plugin-window-state : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:8080/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: node debugger also connects to externally executed node scripts
Labels: feature-request,debug

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
When I'm running a VS Code node application in debug mode, it always also connects to every node script that I call via execSync.

There are cases when this is should not be the case - e.g. when I run "npm install" on a different project, it sometimes fails when in debug mode. It took me quite a while to figure this out, and from what I have found in google, no-one else has noticed that this might be the root cause of their errors.

For my own project I have a workaround by unsetting NODE_OPTIONS in the process.env variable before calling the external node script.

Could there be a switch in VS Code with which this could be generally turned on or off?

Thanks!
Repository: ollama
Issue: ollama runner process has terminated: exit status 127 
Labels: bug,linux,needs more info

### What is the issue?

Ollama will report this error when running any model. The ollama-linux-amd64.tgz file is directly upgraded to version 0.3.14.

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.0
Repository: ollama
Issue: Unable to load images from network fileshares on Windows
Labels: bug,windows

### What is the issue?

Using Ollama on Windows via the terminal, if you ask a question and reference an image on a network fileshare, it will give a response about it not been able to see the photo. If you copy the image locally and then reference the local image, it has no problem with analysing the image.

Paths starting with \\ will not load the image.

### OS

Windows

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.4.0
Repository: tailwindcss
Issue: Invalid css selector generated
Labels: v3

### Discussed in https://github.com/tailwindlabs/tailwindcss/discussions/14901

<div type='discussions-op-text'>

<sup>Originally posted by **kdy1** November  7, 2024</sup>
**What version of Tailwind CSS are you using?**

v3.4.14

**What build tool (or framework if it abstracts the build tool) are you using?**

Next.js + turbopack, but reproducible on playground.

**What version of Node.js are you using?**

Playground

**What browser are you using?**

Chrome

**What operating system are you using?**

macOS

**Reproduction URL**

https://play.tailwindcss.com/obgZakKyiO?file=css

**Describe your issue**

Generated CSS file is 

```css

p.my-4 {
  margin: 0px;
}
.\[\&_\:is\(p\)\]\:my-4 :is(p)p {
  margin: 0px;
}

```


where `:is(p)p` is invalid</div>


---

Originally opened here, but converted it too soon: https://github.com/tailwindlabs/tailwindcss/issues/14900
Repository: three.js
Issue: CSM Improvement: Calculate the best fit frustum for shadow map
Labels: Enhancement

### Description

So far, we use `OffsetCSMShadowNode` to get CSM effect in a scene. We can pass some parameters to this node when constructing.  In the file https://github.com/mrdoob/three.js/blob/dev/examples/jsm/csm/CSMShadowNode.js#L369 `OffsetCSMShadowNode` update transfrom of each internal light in each frame. but the frustum value(`.left`, `.top`, `far`...) of shadow map camera doesn't update, which clones from the main light at the begining.



### Solution

Because the frustum of each shadow camera may be bigger or smaller than the view frustum, It may cause a waste of shadow map or lost some shadow area. I think we should calculate the best fit frustum for shadow map automatically in `three.js`.

I've tested some way to get it. some code like this: https://github.com/ligaofeng0901/three.js/commit/2a00ba9ca5e7f327927afbdd360a27c14c7ef3f6
It can get a better tight box for shadow camera, get better quality of shadow. 
<img width="729" alt="490bc465ca3c3e5af64ab1af94ab1997" src="https://github.com/user-attachments/assets/2e0b3308-2b03-41ca-a0ac-f00bbe810e7c">


### Alternatives

But there are more sitiuation should be considered, the box should be a little bigger than the tight one,  but the margin of each box should not be a constant.  Also, if `.fade` is true, some blank area will appear.

### Additional context

_No response_
Repository: angular
Issue: feature: measure rendering time & notify users when they are rendering too much [using rendering budget]
Labels: area: core

Idea: Check when the last requestAnimationFrame has no more work to do and if it's more than the rendering budget just warn dev.
Repository: PowerToys
Issue: Github Style Markdown Rendering Support: Syntax Highlight, Mermaid Graphs, Latex
Labels: Needs-Triage

### Description of the new feature / enhancement

Would be great if any 1 of the following could be implemented
- Mermaid Graphs
- Latex
- Syntax Highlighting within Markdown

![Image](https://github.com/user-attachments/assets/387abd6c-bfa3-4d52-86d4-5df4fc0d210e)


### Scenario when this would be used?

It can be used for previewing presentation markdown files quickly as we scroll


### Supporting information

_No response_
Repository: next.js
Issue: Incremental Static Regeneration (ISR) Not Functioning as Expected in Next.js 15
Labels: bug

### Link to the code that reproduces this issue

https://github.com/samstr/isr-demo-nextjs15

### To Reproduce

NextJS 14 Demo: https://github.com/samstr/isr-demo-nextjs14
NextJS 15 Demo: https://github.com/samstr/isr-demo-nextjs15

1. Clone demo repo (isr-demo-nextjs14)
2. npm install
3. npm run build
4. Go to http://localhost:3000/ and click the example links

### Current vs. Expected behavior

The expected behavior is for pages that implement ISR should be cached for the time specified using the revalidate const.

In NextJS14 this works, but in NextJS 15 I can't seem to get the same behavior.

The `npm run build` output treats the route differently.

**NextJS 14**
![Screenshot 2024-11-07 at 10 51 33](https://github.com/user-attachments/assets/23d01ffc-b6b6-4461-aab1-6a969a1da5ed)

**NextJS 15**
![Screenshot 2024-11-07 at 10 59 05](https://github.com/user-attachments/assets/7da07629-a0f9-4783-a141-2b6709f9af2c)

I understand that NextJS 15 introduced a new 'uncached by default' concept for route handlers and fetch requests etc, but I didn't think that was related to server rendered pages that are using `revalidate`.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:04 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6020
  Available memory (MB): 98304
  Available CPU cores: 12
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: N/A
  pnpm: 7.22.0
Relevant Packages:
  next: 15.0.2 // Latest available version is detected (15.0.2).
  eslint-config-next: 15.0.2
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
  typescript: 5.6.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), next start (local), Vercel (Deployed)

### Additional context

_No response_
Repository: flutter
Issue: Navigator.canPop vs ModalRoute canPop different behavior
Labels: framework,f: routes,has reproducible steps,P2,team-framework,triaged-framework,found in release: 3.24,found in release: 3.27

### Steps to reproduce

Suppose following routes structure using GoRouter

```code
-- Home
   --- CreateProfile
```

On initial launch of app we launch CreateProfile using context.go() to CreateProfile. 

On Home page we have custom code to display back button (in some cases, users can be pushed to Home from different parts of App, omitted in example). 

When users goes back with AppBar's back button to Home, we decides if show back button with 

```dart
final canPop = context.canPop()

if(canPop) ... show button widget
```

However, canPop returns true even when there is only Home page on navigator's stack. 

If I do Hot-Reload on Home Page, **canPop returns false.**

Moreover

```dart

 final canPop = Navigator.of(context).canPop();
    final goRouterCanPop = context.canPop();
```
both returns `true` after POP from CreateProfile.

BUT if we ask for ` final modalRouteCanPop = ModalRoute.of(context)?.canPop;` , that is 

```dart
    final canPop = Navigator.of(context).canPop();
    final goRouterCanPop = context.canPop();
    final modalRouteCanPop = ModalRoute.of(context)?.canPop;
```

suddenly all calls returns `false` after pooping from CreateProfile. 

Why ModalRoute.of(context)?.canPop alters behaviors of canPop() methods? It seems that ModalRoute is InheritedWidget and it rebuilds HomePage. 

Why canPop() returns true for HomePage when there is CreateProfile on the navigator stack in first place?



GoRouter version:  go_router: ^14.1.3

### Expected results

CanPop() should return false for first page on navigator stack

### Actual results

CanPop returns true for first page navigator stack, after hot reload it returns false.

### Code sample

<details open><summary>Code sample</summary>

```dart
   final canPop = Navigator.of(context).canPop();
    final goRouterCanPop = context.canPop();
    final modalRouteCanPop = ModalRoute.of(context)?.canPop;
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

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


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[x] Flutter (Channel stable, 3.24.3, on Microsoft Windows [Version 10.0.22631.4317], locale en-US)
[x] Windows Version (Installed version of Windows is version 10 or higher)
[x] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[x] Chrome - develop for the web
[x] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.3)
[x] Android Studio (version 2021.3)
[x] Android Studio (version 2022.3)
[x] VS Code (version 1.94.2)
[x] Connected device (4 available)
[x] Network resources

No issues found!


```

</details>
Repository: flutter
Issue: The `event.buttons` of `Listener` `onPointerUp` callback returns 0 regardless of the mouse button pressed
Labels: c: new feature,framework,a: mouse,has reproducible steps,P3,team-framework,triaged-framework,found in release: 3.24,found in release: 3.27

### Steps to reproduce

Just click on amber rectanble and see the results. The `onPointerDown` shows 1 or 2, `onPointerUp` shows 0.

### Expected results

1 on left mouse pointer up
2 on right mouse pointer up

### Actual results

0 on left mouse pointer up
0 on right mouse pointer up

### Code sample

```dart
import 'package:flutter/material.dart';

void main() => runApp(const MaterialApp(home: Foo()));

class Foo extends StatelessWidget {
  const Foo({super.key});

  @override
  Widget build(BuildContext context) {
    String message = '';
    return Material(
      child: Center(
        child: Container(
          color: Colors.amber,
          width: 200,
          height: 200,
          child: StatefulBuilder(
            builder: (context, setState) {
              return Listener(
                onPointerDown: (event) {
                  setState(() {
                    message = 'down ${event.buttons}';
                  });
                },
                onPointerUp: (event) {
                  setState(() {
                    message = 'up ${event.buttons}';
                  });
                },
                child: Text(message),
              );
            },
          ),
        ),
      ),
    );
  }
}

```

</details>

### Flutter Doctor output

Windows 10
Google Chrome 130
Flutter 3.24.4 Stable
Repository: PowerToys
Issue: Fancy zones, limit activation to screens with the same resolution, limit templates to a max resolution, laptop changing between high res screens and low res screens
Labels: Needs-Triage

### Description of the new feature / enhancement

Right now when you are working with a laptop in a 4k screen, fancy zones is very useful as you can divide the screen as desired. The problem is that when you change between different resolutions, the template for the 4k doesn't fit well for 1080p screens. It would be nice to be able to set a maximum resolution where a template is applied, so when you change between screens you can apply automatically another template (or not apply any).

### Scenario when this would be used?

Laptops changing often between monitors with different resolutions, home / office.

### Supporting information

_No response_
Repository: node
Issue: Support `bufferSize` option with recursive mode in `fs.opendir`
Labels: confirmed-bug,fs,good first issue

Related to: #48820 and #55744

After the `recursive` option was added to `readdir` and `opendir`, it was noted that when specifying `bufferSize` alongside `recursive: true`, the result of `opendir` was incorrect. This is fixed in #55744 . However, the _fix_ is a naive solution, and doesn't properly respect the `bufferSize` option. Furthermore, it could result in a blocked event loop. This should be fixed.

I recommend reading the discussion in #48820 for more information. This should only involve changes to the `Dir` class in `lib/internal/fs/dir.js`.
Repository: rust
Issue: It is unclear how to reproduce "Testing stage2 error-index (x86_64-unknown-linux-gnu)"
Labels: A-diagnostics,T-bootstrap,C-bug,A-contributor-roadblock

In [this](https://github.com/rust-lang/rust/actions/runs/11721757438/job/32649886716) CI run, I got the following error:
```

Testing stage2 error-index (x86_64-unknown-linux-gnu)
STDOUT:

running 1106 tests
[...]

failures:
    /checkout/obj/build/x86_64-unknown-linux-gnu/test/error-index.md - Rust_Compiler_Error_Index::E0094 (line 1995)
    /checkout/obj/build/x86_64-unknown-linux-gnu/test/error-index.md - Rust_Compiler_Error_Index::E0211::_::Note__this_error_code_is_no_longer_emitted_by_the_compiler_ (line 3999)

test result: FAILED. 1043 passed; 2 failed; 61 ignored; 0 measured; 0 filtered out; finished in 8.56s


Command CFG_RELEASE_CHANNEL="nightly" RUSTC_BOOTSTRAP="1" RUSTC_STAGE="2" RUSTC_SYSROOT="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2" RUSTDOC_LIBDIR="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2/lib" RUSTDOC_REAL="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2/bin/rustdoc" RUST_TEST_THREADS="16" "/checkout/obj/build/bootstrap/debug/rustdoc" "-Wrustdoc::invalid_codeblock_attributes" "-Dwarnings" "-Znormalize-docs" "-Z" "unstable-options" "--test" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/error-index.md" "--test-args" "" (failure_mode=DelayFail) has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:41:18
```

I have no idea how to reproduce this locally. "Testing stage2 error-index" sounds like it should be `./x test error-index`, but that does not work. So right now I am making guesses and pushing that to the PR, leading to a 40min round-trip time for an edit-compile cycle...

In general, when an `x.py` job fails, it'd be really nice if it could, at the end of the error log, give some idea of how this can be reproduced -- for instance, it can also be non-trivial to find out which target the failing test ran on.

Cc @rust-lang/bootstrap
Repository: create-react-app
Issue: npx create-react-app is not working? why?
Labels: needs triage

For some reason when I tried to start a new project and run the npx  command, i had met this issue. I tried to google this reason but no avail. It says issues with git so I tried to log in on terminal but it is still giving me the same error. Any idea why this would happen? Thanks.

======================================================================
root@tabulaRasa:/mnt/c/Users/tabul/OneDrive/Desktop/DTC web/temp# npx create-react-app your-project

Creating a new React app in C:\Users\tabul\OneDrive\Desktop\DTC web\temp\your-project.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...


added 1312 packages in 13s

259 packages are looking for funding
  run `npm fund` for details
Git repo not initialized Error: Command failed: git --version
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at tryGitInit (C:\Users\tabul\OneDrive\Desktop\DTC web\temp\your-project\node_modules\react-scripts\scripts\init.js:46:5)
    at module.exports (C:\Users\tabul\OneDrive\Desktop\DTC web\temp\your-project\node_modules\react-scripts\scripts\init.js:276:7)
    at [eval]:3:14
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24 {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 9820,
  stdout: null,
  stderr: null
}

Installing template dependencies using npm...
Unknown command: "install$1$1"


Did you mean this?
  npm install # Install a package
To see a list of supported npm commands, run:
  npm help
`npm install --no-audit --save @testing-library/jest-dom@^5.14.1 @testing-library/react@^13.0.0 @testing-library/user-event@^13.2.1 web-vitals@^2.1.0` failed
Repository: react
Issue: [DevTools Bug]: Element selector mode not working with coarse pointer
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://react.dev/

### Repro steps



https://github.com/user-attachments/assets/159b1f24-dd54-4c8e-b726-1d37a131316e

Using the device emulation mode, switch to a mobile device and ensure the pointer is that used for touch devices (circular, rather than the regular fine pointer). 

Toggle on the element selector mode. 

Try to select an element on the page. 

No overlay when you hover the coarse pointer on the emulated device.




### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: transformers
Issue: Padding error when using Universal Assisted Generation with ASR pipeline
Labels: Core: Pipeline,bug,Audio

### System Info

Can not solve by supplying padding arg to pipeline (not accepted).

@gante 

transformers version: https://github.com/huggingface/transformers.git@refs/pull/34504/merge
Ubuntu
Python 3.10.15

### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

![image](https://github.com/user-attachments/assets/5818757b-25a6-471c-81a9-20679b43f73d)


### Expected behavior

Should complete pipeline execution as normal
Repository: PowerToys
Issue: Power Toys loses settings after computer is turned off
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Power toys starts automatically with start-up of my Windows 10 computer.  But often, not always, it reverts to the original four enabled modules instead of the 9 I use.  I have backed up my settings and can easily restore them every time but it's an annoyance.

### ✔️ Expected Behavior

I expected tyhat the program would remember the modules I have enabled every time. 

### ❌ Actual Behavior

When I open the program after the computer has been shut down, often, not always, it reverts to the original four enabled modules instead of the 9 I use.  I have backed up my settings and can easily restore them every time

### Other Software

_No response_
Repository: terminal
Issue: Mulitple levels of tabs
Labels: Issue-Feature,Area-UserInterface,Product-Terminal,External-Blocked-WinUI3

### Description of the new feature

instead of a single horizontal layer for tabs please allow multiple horizontal layers for tabs too

### Proposed technical implementation details

_No response_