sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Skeleton2D and Bone2D throwing error "core/math/transform_2d.cpp:51 - Condition "det == 0" is true."
Labels: bug,topic:animation,topic:2d

### Godot version

4.1.2 Stable

### System information

macOS 14.0 Sonoma, Intel Core I9, AMD 550M,  Forward+

### Issue description

I am having a problem with Skeliton2d and bone 2D where while I am trying to rig a 2D character in the latest version of Godot, I keep getting some errors and it wont let me set a rest position. I am not sure if I am doing this right, so I followed a few tutorial videos on youtube, but with no luck. I keep getting the error " core/math/transform_2d.cpp:51 - Condition "det == 0" is true." anyone know how to fix this?
![Screenshot 2023-10-18 at 10 21 57 AM](https://github.com/godotengine/godot/assets/25351216/953d0135-b43c-49cf-9ad8-99ff8de5f6d1)
![Screenshot 2023-10-18 at 10 23 20 AM](https://github.com/godotengine/godot/assets/25351216/1c136f4e-88f6-4b65-a1c6-e85242394ff9)


### Steps to reproduce

While attaching Skeliton2D and Bone2D to the Scene, I started getting the above errors, starting with one for each bone that was added. then finally when all of the bones were in place, I selected to set the rest position and the errors were firing off constantly.

### Minimal reproduction project

[Project.zip](https://github.com/godotengine/godot/files/13030150/Project.zip)
Repository: node
Issue: `test-fs-watch-recursive-add-file-with-url` is flaky
Labels: s390,flaky-test

### Test

`parallel/test-fs-watch-recursive-add-file-with-url`

### Platform

Linux s390x

### Console output

```console
not ok 1368 parallel/test-fs-watch-recursive-add-file-with-url
  ---
  duration_ms: 120048.27600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
```


### Build links

- https://ci.nodejs.org/job/node-test-commit-linuxone/40398/

### Additional information

_No response_
Repository: godot
Issue: Class names suddenly seen as invalid
Labels: topic:gdscript,topic:editor,needs testing

### Godot version

4.1.1 stable

### System information

Godot v4.1.1.stable - Windows 10.0.22635 - Vulkan (Forward+) - integrated AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 31.0.22013.1002) - AMD Ryzen 7 7735U with Radeon Graphics (16 Threads)

### Issue description

Suddenly all custom class names in my project (declared using `class_name` in scripts) produce this error:
`Parser Error: Could not parse global class "(the name of the class)" from "res://(path to the script the class comes from)".` and prevent the game from running.

This is fixed by going to the script, erasing one letter from the class name, typing it again and saving, but I would have to do that for every single one, which doesn't sound like a fun way to spend my day.


### Steps to reproduce

I am unable to reproduce this. Before it happened, I was trying to export my game before I noticed these errors but I'm not sure what caused it. I reverted to an older version that wasn't affected and retraced my steps, but I couldn't reproduce it. 
An attempt to reproduce it is happening though.

### Minimal reproduction project

_Production edit:_ [83561.zip](https://github.com/user-attachments/files/15749188/83561.zip)
Repository: next.js
Issue: Sass not working for new project - Cannot read properties of undefined (reading 'pop')
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/FreedCapybara/nextjs-sass-error

### To Reproduce

1. Create a new Next.js app
```
npx create-next-app@latest
√ What is your project named? ... nextjs-sass-error
√ Would you like to use TypeScript? ... Yes
√ Would you like to use ESLint? ... Yes
√ Would you like to use Tailwind CSS? ... No
√ Would you like to use `src/` directory? ... Yes
√ Would you like to use App Router? (recommended) ... Yes
√ Would you like to customize the default import alias (@/*)? ... No
```
2. Add Sass, per the documentation https://nextjs.org/docs/pages/building-your-application/styling/sass
```
npm install --save-dev sass
```
3. Rename `src/app/page.module.css` to `src/app/page.module.scss` and update the import in `src/app/page.tsx`
4. Run the app
```
npm run dev
```
5. Error page with
```
./src/app/page.module.scss
Cannot read properties of undefined (reading 'pop')
```

### Current vs. Expected behavior

I expect the app to build and render the page, but the app crashes with `Cannot read properties of undefined (reading 'pop')`.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 21.0.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.6-canary.6
  eslint-config-next: 13.5.5
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, CLI (create-next-app)

### Additional context

Occurs as far back as 12.3.2-canary.43, had trouble installing older versions.
Repository: flutter
Issue: [video_player] Integration tests fail on API 22 emulator in CI
Labels: a: tests,team,platform-android,p: video_player,package,P2,c: disabled test,team-android,triaged-android

Trying to bring up API 22 emulators to replace the disable legacy API FTL tests (https://github.com/flutter/flutter/issues/130010), `video_player` and `video_player_android` are failing several tests with:

```
PlatformException(VideoError, Video player had error
com.google.android.exoplayer2.ExoPlaybackException: MediaCodecVideoRenderer error, index=0,
format=Format(1, null, null, video/avc, avc1.64001F, -1, null, [1280, 720, 29.973475], [-1, -1]),
format_supported=NO_EXCEEDS_CAPABILITIES, null, null)
```

([example run](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8766883897941974577/+/u/Run_package_tests/drive_examples/stdout))

It looks like that emulator isn't capable of playing at least some videos. I'm not sure if this is something that could be avoided with a different emulator configuration (or maybe different test videos); for now I'm going to disable `video_player` in the legacy tests (via a new `script/config/exclude_integration_android_legacy_emulator.yaml` file I'm adding in the PR; the entry in that file will reference this issue) to unblocking bringing up the rest of the suite.
Repository: flutter
Issue: [webview_flutter] Integration tests hang on API 22 emulator in CI
Labels: a: tests,team,platform-android,p: webview,package,P2,c: disabled test,team-android,triaged-android

Trying to bring up API 22 emulators to replace the disable legacy API FTL tests (https://github.com/flutter/flutter/issues/130010), `webview_flutter` hangs forever in `integration_test/webview_flutter_test.dart: Video playback policy Video plays inline`.

It's interesting that the problem is related to video given https://github.com/flutter/flutter/issues/136823 is the other issue that was specific to this legacy emulator test.

I haven't tried to repro locally (I had issues getting a working 22 emulator locally) so I don't have any more information about what exactly is going wrong. For now I'm going to disable `webview_flutter` (and `webview_flutter_android`) in the legacy tests (via a new `script/config/exclude_integration_android_legacy_emulator.yaml` file I'm adding in the PR; the entry in that file will reference this issue) to unblocking bringing up the rest of the suite.
Repository: next.js
Issue: `import x = y` syntax stopped working from next@13.5.4
Labels: bug

### Link to the code that reproduces this issue

https://github.com/steebchen/nextjs-import-bug-13.5.4

### To Reproduce

Use this import syntax:

```ts
import X = Components.Schemas.MeUserDto
```

build fails:

```
> next build

 ✓ Linting and checking validity of types    
Failed to compile.

./src/pages/test.tsx
Module not found: Can't resolve '@/src/generated/api'

https://nextjs.org/docs/messages/module-not-found

```

Still happens in latest and canary.

### Current vs. Expected behavior

This import syntax should work, or be officially unsupported and return a more appropriate error.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 8.6.3
Relevant Packages:
  next: 13.5.6-canary.6
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


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

Not sure

### Additional context

_No response_
Repository: vscode
Issue: Long/multiline test failure messages are not all readable when using actual/expected diff
Labels: feature-request,testing

If I fail my test with a multiline `TestMessage` it looks like this:

![image](https://github.com/microsoft/vscode/assets/1078012/78ef3cde-6b7c-4fa1-ae60-8500abdd918e)

But if I use `TestMessage.diff` like this:

```ts
const testMessage = vs.TestMessage.diff("this is a more detailed description of the issue\nit is long and multiline", "aaaaaaaaaa", "aaaaaaaaaaaaaaa");
```

I can't see the full multiline text in the Test Results pane (it does appear in the editor but unwrapped, and in the peek title it's truncated to the first line):

![image](https://github.com/microsoft/vscode/assets/1078012/63214efe-3e8a-411e-b7f4-9d789242618c)

Dart's test package generates quite descriptive errors which we currently show. I'd like to use `.diff` but it looks like we'd lose some info here (while we could write an additional output entry, it wouldn't be the final failure state for the test).

It would be nice if the message could be shown in full (inc. multiple lines) in the peek title, and also in a section above the diff in the Test Results pane.
Repository: godot
Issue: Commenting code with `Ctrl+K` now inserts the `#` in front of the first keyword rather than at the start of the line
Labels: discussion,topic:gdscript,topic:editor

### Godot version

v4.2.beta.custom_build [7f884b4e0]

### System information

linux

### Issue description

Commenting a line using <kbd>Ctrl+K</kbd> inserts a `#` in front of the first keyword.
This:
 - is ugly imo, it makes it hard to detect what was mass-commented
 - when commenting a code block, it turns comments inside into doc comments (`##`) which are coloured differently.


https://github.com/godotengine/godot/assets/71937306/517d58e0-10c7-467a-b31f-db26df206427



### Steps to reproduce

- Use <kbd>Ctrl + K</kbd>

### Minimal reproduction project

any script
Repository: electron
Issue: [Bug]: ChromeDriver hangs when requesting WindowHandles after opening new window
Labels: platform/windows,bug :beetle:,component/BrowserView,blocked/upstream ❌,26-x-y,component/WebContentsView,stale-exempt

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

v26.0.0

### What operating system are you using?

Windows

### Operating System Version

Windows 10 Version 22H2

### What arch are you using?

x64

### Last Known Working Electron version

v25.9.1

### Expected Behavior

We automate testing against one of our Electron applications by using ChromeDriver (via Selenium) to interact with webpages. In particular, one test looks for newly-opened windows by asking the driver to provide it with a set of handles to all open windows for that driver (what I assume is [this](https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/WebDriver.html#getWindowHandles()), although the actual call is done by a C# wrapper). After opening a new window in our Electron application, we would expect a call to get the window handles to return all available window handles, including a handle to the newly created window.

### Actual Behavior

The call to get all window handles hangs for a while before eventually timing out. This only seems to occur after a window has been newly-opened, and only for certain windows.

### Testcase Gist URL

_No response_

### Additional Information

To be blunt, this isn't an issue with Electron's code itself - we've sourced this to a specific [Chromium change](https://chromium-review.googlesource.com/c/chromium/src/+/4546274) made sometime between Chromium v115.0.5786.0 and Chromium v115.0.5790.0 (confirmed by testing with Electron v26.0.0-nightly.20230524, where the issue does not occur, and Electron v26.0.0-nightly.2023.0525, where it does). We've written up a [Chromium issue](https://bugs.chromium.org/p/chromium/issues/detail?id=1493733) to track this, but wanted to open an issue here as well in the event that this might be something Electron could fix with a Chromium patch if Chromium doesn't fix it.
Repository: PowerToys
Issue: [Peek] Cursor doesn't change when autoscrolling a PDF
Labels: Issue-Bug,Area-Quality,Priority-2,Product-Peek

### Microsoft PowerToys version

0.74.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Peek

### Steps to reproduce

1. Preview a PDF with Peek
2. Press the scroll wheel
3. Move your cursor up or down
4. The PDF starts autoscrolling as expected, but the cursor doesn't change

### ✔️ Expected Behavior

The cursor should change to the autoscroll cursor
<img src="https://github.com/microsoft/PowerToys/assets/127593627/666092ff-6e58-4b39-afae-c91b5e3ff783" alt="Autoscroll cursor alternative 1" width="116"/>
or
![Autoscroll cursor alternative 2](https://github.com/microsoft/PowerToys/assets/127593627/588decb6-3607-4afe-8179-a36283734d86)


### ❌ Actual Behavior

The cursor doesn't change, which can lead to some very confusing situations, especially when you press the scroll wheel by accident.

### Other Software

_No response_
Repository: flutter
Issue: Confusing output from flutter tool when I run "flutter build web lib/a.dart"
Labels: tool,platform-web,a: build,has reproducible steps,team-tool,found in release: 3.13,found in release: 3.16

It says that it is compiling "lib/main.dart"

@eyebrowsoffire says this is because there is a "lib/main.dart" wrapper that is compiled
Repository: flutter
Issue: Add local baseline comparison for engine gold testing
Labels: c: new feature,engine,P2,team-engine,triaged-engine

The framework does this via a `LocalFileComparator` - we should be able to do the same in the engine once we're actually populating more goldens.
Repository: flutter
Issue: [two_dimensional_scrollables] TableView pinned rows and columns should warn if pinned spans exceed viewport dimensions
Labels: framework,f: scrolling,package,P2,team-framework,triaged-framework,p: two_dimensional_scrollables

Since pinned rows and columns do not scroll, we should assert they are all contained within the viewport.
Edge case to also consider: If there are pinned rows/columns that consume the full extent of the viewport, and there are additional unpinned children we should probably also assert, since the additional children will never be visible to the user.

---

Update: Rather than asserting here, we should probably just surface a non-fatal warning of some kind. A good example of this is in Google sheets. If you freeze rows/columns beyond the window size, it is allowed, but a small dialog pops up to inform the user they cannot scroll anything in to view in that configuration.
Repository: terminal
Issue: About dialog changes tooltip theme from Light to Dark
Labels: Issue-Bug,Product-Terminal,Area-Theming

### Windows Terminal version

1.18.2822.0

### Windows build number

10.0.19045.0

### Other Software

_No response_

### Steps to reproduce

Use a Dark application theme. Open a new Terminal window and take note of the tooltip theming. Open the About dialog and close it and then recheck tooltip theming.

### Expected Behavior

_No response_

### Actual Behavior

 I noticed this behaviour today, and I can consistently reproduce it. When I open a new Terminal window, the tooltips for that window are Light themed up until I open the About dialog, and then they become Dark themed (but only for that window). You can see what I mean in the following video:
 
https://github.com/microsoft/terminal/assets/11712728/cf716feb-d02a-4017-8e56-d35d7b51d2d8

In my `settings.json`, I'm using this custom Dark theme (the purpose is just to allow me to hide the close buttons on the tabs):

    "theme": "dark_no-close-button",
    "themes": 
    [
        {
            "name": "dark_no-close-button",
            "tab": 
            {
                "background": "terminalBackground",
                "showCloseButton": "never",
                "unfocusedBackground": "#00000000"
            },
            "tabRow": 
            {
                "background": "#2E2E2EFF",
                "unfocusedBackground": "#333333FF"
            },
            "window": 
            {
                "applicationTheme": "dark",
                "useMica": false
            }
        }
    ]

It happens when I just use `"theme": "dark"` or `"theme": "legacyDark"` as well though.

Here are my Windows colour settings:

![WindowsColour](https://github.com/microsoft/terminal/assets/11712728/2bd75f1f-56de-4155-acf6-cc5cb4907904)
Repository: kubernetes
Issue: [StructuredAuthnConfig] Make username required
Labels: sig/auth,triage/accepted

              I think we want to go ahead and start failing if username is the empty string.

_Originally posted by @enj in https://github.com/kubernetes/kubernetes/pull/121078#discussion_r1362658684_
Repository: PowerToys
Issue: [Issue]: PowerToys Run: Deleted Entries
Labels: Issue-Bug,Product-PowerToys Run,Run-Results (Programs),Status-Reproducible

### Microsoft PowerToys version

0.74.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. Delete Shortcut in Startmenu folder
2. search for the shortcut
3. deleted shortcut is shown (sometimes even after restart)

### ✔️ Expected Behavior

Deleted Shortcut shouldn't be shown in (program) search

### ❌ Actual Behavior

deleted shortcut is shown

### Other Software

_No response_
Repository: rust
Issue: `unreachable_code` lint on `match`ing empty enum result of `Into::into`
Labels: A-lints,A-diagnostics,T-compiler,C-bug,L-unreachable_code,L-false-positive

### Code

```Rust
trait ResultExt<T> { fn into_ok(self) -> T; }
impl<T, E> ResultExt<T> for Result<T, E>
where
    E: Into<core::convert::Infallible>,
{
    /// Infallibly unwraps `self` into it's value
    fn into_ok(self) -> T {
        match self {
            Ok(val) => val,
            Err(e) => match Into::into(e) {},
        }
    }
}
```


### Current output

```Shell
warning: unreachable expression
  --> src/main.rs:11:23
   |
11 |             Err(e) => match Into::into(e) {},
   |                       ^^^^^^-------------^^^
   |                       |     |
   |                       |     any code following this expression is unreachable
   |                       unreachable expression
   |
note: this expression has type `std::convert::Infallible`, which is uninhabited
  --> src/main.rs:11:29
   |
11 |             Err(e) => match Into::into(e) {},
   |                             ^^^^^^^^^^^^^
   = note: `#[warn(unreachable_code)]` on by default

warning: `playground` (bin "playground") generated 1 warning
```


### Desired output

```Shell
No diagnostic.
```


### Rationale and extra context

The `match` in that code, which is linted against, as well as the `Into` is added for type checking. Without either, the above code fails to compile, as can be demonstrated here:
```rust
trait ResultExt<T> { fn into_ok(self) -> T; }
impl<T, E> ResultExt<T> for Result<T, E>
where
    E: Into<core::convert::Infallible>,
{
    /// Infallibly unwraps `self` into it's value
    fn into_ok(self) -> T {
        match self {
            Ok(val) => val,
            Err(e) => Into::into(e),
        }
    }
}
```

which yields

```
error[E0308]: `match` arms have incompatible types
  --> src/main.rs:11:23
   |
3  |   impl<T, E> ResultExt<T> for Result<T, E>
   |        - this type parameter
...
9  | /         match self {
10 | |             Ok(val) => val,
   | |                        --- this is found to be of type `T`
11 | |             Err(e) => Into::into(e),
   | |                       ^^^^^^^^^^^^^ expected type parameter `T`, found `Infallible`
12 | |         }
   | |_________- `match` arms have incompatible types
   |
   = note: expected type parameter `T`
                        found enum `std::convert::Infallible`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` (bin "playground") due to previous error
```

(cases without the `Into::into(e)` are trivial, and left as exercise to reader)

### Other cases

_No response_

### Anything else?

Actual code that found this lint is <https://github.com/lccc-project/lccc/blob/main/xlang/xlang_abi/src/result.rs#L182-L194>
Repository: PowerToys
Issue: [FR]: PowerToys Run: Hide blue background behind UWP apps
Labels: Help Wanted,Product-PowerToys Run,Run-Results (Programs)

### Description of the new feature / enhancement

the blue background of UWP oder PWAs should be hidden as in windows search.
Currently app icons are smaller und it doesn't fit well with the modern Windows 11 System.

![image](https://github.com/microsoft/PowerToys/assets/97352673/5202b740-fc4a-4333-96c8-a474237eeeca)

![image](https://github.com/microsoft/PowerToys/assets/97352673/8c6bbb65-9c58-450f-b871-3776a78dbb9f)

![image](https://github.com/microsoft/PowerToys/assets/97352673/dfe42429-21cb-431c-8534-6edc678e73fb)


### Scenario when this would be used?

better design and consistence 

### Supporting information

_No response_