sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Timer (SceneTreeTimer) leaked when awaiting it while quitting.
Labels: bug,topic:gdscript

### Godot version

4.1.1.stable

### System information

Ubuntu 22.04

### Issue description

If a timer is awaited when `get_tree().quit()` is called, then it is not freed.

```
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:2047)
Leaked instance: SceneTreeTimer:-9222497925110692716
```

### Steps to reproduce

* create a scene `main.tscn` with this as the script for the root node:
```
extends Node

func _ready():
    async_stuff()
    get_tree().quit()

func async_stuff():
    await get_tree().create_timer(1.0).timeout
```
* Launch the scene `godot main.tscn --verbose`
* Output should warn about the leak:
```
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:2047)
Leaked instance: SceneTreeTimer:-9222495726087437163
```

### Minimal reproduction project

[await_timer_leaked.zip](https://github.com/godotengine/godot/files/12098518/await_timer_leaked.zip)
Repository: flutter
Issue: Support custom design tokens on ThemeData's TextTheme and ColorScheme
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Translating a custom app design in Figma to a Flutter app, the designer provides the foundations for a design system. Functionality, I get everything that I need from the Material library. However, I need to do more work on the widgets to get it looking like the original design. 

The design system has its own design tokens with specifications that the designer has come up with, for example with TextStyles in TextTheme: 
- Heading1
- Heading2
- Heading3
- Subheading1
- Subheading2
- Paragraph
- Label
- etc.

However, these design tokens don't match up with Material's default tokens:
- displayLarge
- displayMedium
- displaySmall
- headlineLarge
- headlineMedium
- headlineSmall
- etc.

Same concept applies for ColorScheme with:
primary, secondary, tertiary, scrim, background, etc. 

Problem: Custom design token names don't match 1:1 with Material's design tokens. 
Solution options:
1. Map custom design tokens to a pre-existing Material's tokens
2. Override the TextStyle or Color directly within the widget, without referencing Material. Likely, creating a standalone class which has the token values. 
3. Override _all_ of the text and colors within the app to one common look and then override individual components to stylize. 

These potential solutions require additional overhead from the developer, whether that be keeping track of two sets of tokens-  the original design tokens and material's, and how they translate -- or overriding all of the styles individually to get it to a good starting point before customizing. It adds friction to the the development flow. 

### Proposal

Allow TextTheme and ColorScheme to be extended with new token names in addition to Material's. Use default value for Material tokens. Perhaps something like... 

```
ColorScheme.custom(
  brand: Color(0xffA2E3F6),
  accent: Color(0xffFFABC7),
)
```

```
TextTheme.copyWithCustom(
  headline1: TextStyle(...),
  subtitle: TextStyle(...),
  label: TextStyle(...),
)
```
Repository: kubernetes
Issue: kubectl does not retry after TLS handshake timeout
Labels: kind/bug,sig/api-machinery,lifecycle/frozen,triage/accepted

<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->

**What happened**:

One of our three control plane IPs is unresponsive. On my local machine, what I observe is sporadically it will lag for about 10 seconds, but otherwise works fine. This is because the Go standard library divides the 30 second dial timeout over the 3 IPs, and when the first times out it falls back to the second one.

Further testing shows that if the entire TCP dial times out, then kubectl itself will retry.

However, our build server is behind a firewall. Because of this, what happens there is the TCP dial works but the TLS handshake times out after 10 seconds. When this happens, kubectl treats it as fatal and does not attempt to retry.

**What you expected to happen**:

kubectl should retry if the TLS handshake times out. (It should start over with a fresh TCP dial.)

**How to reproduce it (as minimally and precisely as possible)**:

I don't know how to force this issue to reproduce.

**Anything else we need to know?**:

**Environment**:
- Kubernetes client and server versions (use `kubectl version`): v1.21.13 (client), v1.22.12 (server)
- Cloud provider or hardware configuration: AWS EKS
- OS (e.g: `cat /etc/os-release`): macOS 12.5.1
Repository: flutter
Issue: Create charts to show recent release branch builds
Labels: team-infra,P2,triaged-infra

Release candidate branches share same try/prod pools as main/master. Random cherry picks happens on different release branches and compete resources as the Main CI. It usually cause queue time high, some builds timing out, and tree closure.

We should have some charts showing release build status, which will give infra gardener some insight when CI queue time increases.
Repository: pytorch
Issue: [easy] Add an option to force recompilation
Labels: triaged,enhancement,hackathon,oncall: pt2

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @wconstab
Repository: pytorch
Issue: aten._trilinear
Labels: triaged,oncall: pt2,module: inductor

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @amjames @desertfire @wconstab
Repository: pytorch
Issue: aten._cdist_backward
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: aten.multilabel_margin_loss_backward
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: Reflection_pad1d
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: replication_pad1d
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: Move Inductor-specific decompositions to general decomposition registrations.
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: Lowering topk to reductions and pointwise when k is small
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: Using scans
Labels: triaged,hackathon,oncall: pt2

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: pytorch
Issue: Add color-coding to fx graph readable printouts :)
Labels: triaged,enhancement,hackathon,oncall: pt2

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @wconstab
Repository: vscode
Issue: Test UI should surface continuous run on gutter test icon
Labels: feature-request,testing

<!-- ⚠️⚠️ 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. -->
CC @connor4312 

The `Turn On Continuous Run` option should also be surfaced in the right click menu for the gutter icons

![image](https://github.com/microsoft/vscode/assets/15258962/73e7ee8c-d0de-4186-b55f-5c6979cb9edf)

![image](https://github.com/microsoft/vscode/assets/15258962/1c8220c1-5a4f-43be-9903-5209509af4fa)
Repository: go
Issue: all: test failures with `_assert(): stream.sputn` on ios-arm64-corellium
Labels: Builders,NeedsInvestigation,compiler/runtime,OS-iOS

```
#!watchflakes
post <- log ~ `_assert\(\): stream\.sputn`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/3e6b9566193557cd6b848a65be4020d8d799f35e)):

    --- FAIL: TestLargeReloc (6.78s)
        link_test.go:1094: build failed: exit status 1. output:
            # command-line-arguments
            /tmp/workdir-host-ios-arm64-corellium-ios/go/pkg/tool/ios_arm64/link: running /var/root/bin/clangwrap failed: exit status 1
            ../ldid.cpp(534): _assert(): stream.sputn(static_cast<const char *>(data) + total, writ) == writ
            clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
    
        link_test.go:1101: build failed: exit status 1. output:
            # command-line-arguments
            /tmp/workdir-host-ios-arm64-corellium-ios/go/pkg/tool/ios_arm64/link: running /var/root/bin/clangwrap failed: exit status 1
            ../ldid.cpp(534): _assert(): stream.sputn(static_cast<const char *>(data) + total, writ) == writ
            clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Terminal tab home CWD is not handled correctly in remote workspaces
Labels: bug,terminal-tabs

Repro:

1. Open a remote window with a folder
2. Open a terminal, 🐛 you should _not_ see the folder name

![image](https://github.com/microsoft/vscode/assets/2193314/a6ce4a4f-37b8-4b53-ae4f-f030060b0e9d)
Repository: flutter
Issue: Simplify syntax for a non-MaterialState-dependent border
Labels: c: new feature,framework,c: proposal,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Stylizing a [SegmentedButton](https://api.flutter.dev/flutter/material/SegmentedButton-class.html) as part of translating a custom app design in Figma to a Flutter app.

Requirements for the example use case:
- Add a static border that doesn't depend on Material State
- Uniform border all around, no special sides 

Example code implemented:
```
ButtonStyle(
  side: MaterialStateProperty.all(
    BorderSide(
      color: Marketplace.theme.colorScheme.onSecondary,
      width: 2,
    ),
  )
)
```

semi-related to https://github.com/flutter/flutter/issues/99983 
cc @leighajarett 

### Proposal

This is very rough idea, but in essence abstract away MaterialStateProperty and BorderSide. Ideally, makes it faster to write, easier to customize a border worrying about MaterialState and it's less verbose/easier to read at a glance. 

So instead of...
```
MaterialStateProperty.all(
   BorderSide(
     color: Marketplace.theme.colorScheme.onSecondary,
     width: 2,
   ),
)
```

It looks a little simpler, like:
```
StaticMaterialBorder(
  color: Marketplace.theme.colorScheme.onSecondary,
  width: 2,
)
```
Repository: godot
Issue: Rotation of a 3D node saves wrong when using 180/-180 degrees
Labels: bug,topic:editor

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Godot v4.1.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 31.0.15.3667) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

### Issue description

When changing the rotation of a 3D node to 180 degrees in the editor, saving the scene and reopening it, the rotation will have changed to -180 degrees. When setting the rotation to -180 degrees, it will change to 180 degrees. This happens to the x, y and z properties but not with any other rotation than 180 or -180 degrees.

### Steps to reproduce

- create a new scene
- create a new 3D node
- change the rotation.x of the node to 180 degrees
- save and close the scene
- after opening the scene again the rotation.x will be -180 degrees

### Minimal reproduction project

N/A
Repository: flutter
Issue: Provide more explicit warnings when using Material 2 widgets with Material 3 Theme
Labels: framework,f: material design,c: proposal,P2,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Adding a bottomNavigationBar to an app with `useMaterial3: true` specified in the ThemeData. 

When specifying the bottomNavigationBar property in Scaffold, you can provide either a [BottomNavigationBar](https://api.flutter.dev/flutter/material/BottomNavigationBar-class.html) or a [NavigationBar](https://api.flutter.dev/flutter/material/NavigationBar-class.html). 

If a BottomNavigationBar (Material 2) is provided, no warnings are given that I might want to use the NavigationBar instead because I've enabled Material 3. 

Additionally, API docs for [BottomNavigationBar](https://api.flutter.dev/flutter/material/BottomNavigationBar-class.html) doesn't give any acknowledgement to NavigationBar which is it's new replacement. BottomNavigationBar also comes up first when you Google ["navigation bar flutter"](https://www.google.com/search?q=navigation+bar+flutter&rlz=1C5CHFA_enUS870US870&oq=navigat&aqs=chrome.0.69i59j0i20i263i433i512j69i64j69i57j69i60l3j69i65.1954j0j7&sourceid=chrome&ie=UTF-8) so developers who are looking this up will go for the older Material 2 version instead of the new Material 3 Navigation Bar.

### Proposal

If useMaterial3 is specified in a ThemeData, it can be assumed that developers want to use Material 3 version of widgets. Provide an explicit warning when flutter code specifies an older Material 2 version of widgets that have a Material 3 counterpart available, such as BottomNavigationBar vs NavigationBar. 

Additionally, Material 2 widget documentation should highlight newer Material 3 counterparts, if available.
Repository: deno
Issue: Add `retry` option to `Deno.test`
Labels: suggestion,testing

In the Fresh project we're running into more flaky tests on windows. Our tests are all based on `Deno.test` and it would be nice if we could retry failing tests automatically.

Something like:

```js
Deno.test({
  name: "foobar",
  retry: 3, // <-- Specifier number of times this test is allowed to fail.
  fn() {
     //...
  }
});
```
Repository: next.js
Issue: Slots (@ routes) that start with the same first two letters render incorrectly
Labels: bug,Navigation

### 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 22.5.0: Mon Apr 24 20:52:43 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T8112
    Binaries:
      Node: 16.20.0
      npm: 8.19.4
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.11-canary.0
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A


✨  Done in 2.33s.
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/franzwarning/nextjs-slots-bug

https://github.com/vercel/next.js/assets/1596816/7d0bedf8-e356-4307-8ddc-72b74bcce9f0

### To Reproduce

Click "Tree", the tree slot will be rendered
Click "Dismiss", the home page is rendered
Click "toad", the toad slot is rendered
Click "Dismiss", the tree slot is rendered again incorrectly

### Describe the Bug

If you have multiple slots that start with the same first two letters (in my example @tree and @troad), clicking on one, dismissing, then clicking on the other and dismissing will bring back up the first one.

See the video in my git repo: https://github.com/franzwarning/nextjs-slots-bug

If you rename the slots to begin with different letters, the bug does not exist

The last version that was working for us was 13.4.6, so I will try to investigate the commit that broke this behaviour.

### Expected Behavior

You should not have the original slot rendered again

### Which browser are you using? (if relevant)

Chrome, Safari

### How are you deploying your application? (if relevant)

Vercel
Repository: flutter
Issue: Show a warning that uses-material-design: true needs to be specified in pubspec.yaml when setting useMaterial3: true for users Migrating a Cupertino app to Material 
Labels: c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Migrating a Cupertino app to Material and decided that I wanted to use [Material's icons](https://api.flutter.dev/flutter/material/Icons-class.html). Started adding icons into the bottom navigation bar, but only questions marks in a square (BottomNavigationBar) or weird emojis (NavigationBar) appeared. There's no indicator that I need to specify `uses-material-design: true` in my pubspec.yaml.

BottomNavigation:
<img width="447" alt="Screenshot 2023-07-19 at 12 56 53 PM" src="https://github.com/flutter/flutter/assets/12416400/f2c8e898-2385-40c2-94bd-00b1efbdfdb6">

NavigationBar:
<img width="450" alt="Screenshot 2023-07-19 at 12 56 34 PM" src="https://github.com/flutter/flutter/assets/12416400/0b1ed4eb-486e-4b25-a311-5f13ca4afe75">


### Proposal

Show a warning that `uses-material-design: true` needs to be specified in pubspec.yaml when using Material icons.
Repository: godot
Issue: Godot freezes when create a new animation on node AnimatedSprite2D
Labels: bug,platform:linuxbsd,topic:porting

### Godot version

4.1

### System information

Arch Linux\Linux

### Issue description

Every time that I create an animation on node AnimatedSprite2D and try to rename godot freezes and I need to kill the process on terminal.

### Steps to reproduce

create a new animation and rename.

### Minimal reproduction project

none
Repository: PowerToys
Issue: Peek: Have Pin Window Setting Persist When Peek App is Closed
Labels: Needs-Triage

### Description of the new feature / enhancement

The setting to pin the window to the current location should persist when the Peek app is closed. When Peek is closed and restarted (usually when the computer is restarted), the setting reverts to the default unpinned state.

### Scenario when this would be used?

This would be useful for those who always want the Peek window pinned. When Peek restarts (usually when the computer is restarted), the window would use the same setting (pinned or unpinned) it had before when Peek shutdown. As it stands now, each time I restart my computer, I must manually pin the window in the desired location. I want it to simply open in the location I last used before Peek shutdown.

### Supporting information

_No response_
Repository: flutter
Issue: [google_maps_flutter] Evaluate `google_maps` package dependency on web
Labels: team,p: maps,platform-web,package,P2,team-web,triaged-web

See https://github.com/flutter/flutter/issues/122713 for context.

The `google_maps` package is very heavily used in the web implementation of `google_maps_flutter`, but it's outside the policy we've now established for dependencies. E.g., it looks like it may have a bus factor of one person currently, which is definitely not ideal.

@ditman @a14n Any thoughts on what we could do here? Is there a plausible path for this becoming part of flutter/packages, for instance?
Repository: go
Issue: net: TestInterfaceArrivalAndDepartureZoneCache failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestInterfaceArrivalAndDepartureZoneCache"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/9842658765ea7d1e02c7ee707e556a7a1bdf9c57)):

    --- FAIL: TestInterfaceArrivalAndDepartureZoneCache (0.00s)
        interface_unix_test.go:196: args=[ip address add fe80::1 dev gotest0] out="RTNETLINK answers: Permission denied\n" err=exit status 2


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Peek: Cannot Use Arrow Keys to Cycle Through and Preview Multiple Files in a Folder
Labels: Issue-Bug,Needs-Triage,Product-Peek

### Microsoft PowerToys version

0.71.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Peek

### Steps to reproduce

1. Create a folder with multiple PDF files in it. Each pdf file should have at least two pages in it (this will best illustrate the problem).
2. Use ctrl+space to preview the first pdf file in the folder.
3. Use the mouse cursor to click on the page of the previewed pdf file in Peek (just click somewhere on the previewed pdf file).
4. Press the down arrow key.

### ✔️ Expected Behavior

Pressing the down arrow key should cause Peek to show a preview of the next pdf file in the folder. Also, the arrow keys should work to cycle through and preview the pdf files in the folder

### ❌ Actual Behavior

Pressing the down arrow key scrolls the pdf file downward in the Peek window. Also, the arrow keys no longer cycle through and preview the pdf files in the folder. Instead, they only scroll the pdf file displayed in the Peek window.

Note: this may be related to this issue: https://github.com/microsoft/PowerToys/issues/27017

### Other Software

_No response_
Repository: deno
Issue: `deno vendor` tries to fetch `declare module` specifiers
Labels: bug

The `deno vendor` command aborts with an error when it encounters a type definition file that imports a locally declared module.

## Steps to reproduce

1. Create a file `foo.js` with the following content:
  ```js
  import * as highlight from "https://esm.sh/highlight.js";

  console.log(
    highlight.HighlightJS !== undefined ? "it works" : "it doesn't work"
  );
  ```
2. Run `deno vendor foo.js` -> Error

Error:

```sh
$ deno vendor foo.js
error: Module not found "https://esm.sh/v128/highlight.js@11.8.0/private~.d.ts".
    at https://esm.sh/v128/highlight.js@11.8.0/types/index.d.ts:18:33
```

The definition file looks like this:

```ts
// Locally declared module
declare module 'https://esm.sh/v128/highlight.js@11.6.0/private~.d.ts' {
    // ...
    type KeywordDict = Record<string, KeywordData>
}

declare module 'https://esm.sh/v128/highlight.js@11.6.0/types/index.d.ts' {
    // This line causes the error, Deno tries to fetch this, but it's a locally declared module
    import { KeywordDict } from "https://esm.sh/v128/highlight.js@11.6.0/private~.d.ts";
    // ...
}
```