sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Environment: Background Mode: Canvas causes Popup windows to become severely transparent (including default "ToolTip") regardless of `background_canvas_max_layer` property
Labels: bug,topic:rendering,topic:2d

### Tested versions

- Reproducible in Godot 4.3 (Renderer: Mobile)

### System information

Windows 11 - Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org Vulkan 1.3.278 - Forward Mobile - Using Device #0: NVIDIA - NVIDIA GeForce RTX 3050 Laptop GPU

### Issue description

When using World environment in a scene, and setting the background mode of an environment to `canvas`, every popup window (transparent = true) to become severely transparent (almost invisible) Even when the theme is custom set to be fully opaque have tried to change the CanvasLayer's `Layer` which is the parent of the GUI node to a higher value than the `background_canvas_max_layer` but it has no effect.

 ![Image](https://github.com/user-attachments/assets/f6c91df6-7d72-4cda-beda-ea8bcc039523)

EXPECTED OUTCOME (WorldEnvironment `Background Mode` set to: `Clear Color`):
![Image](https://github.com/user-attachments/assets/14a08f65-bd33-4500-9f4d-8c9c95525089)

If this is the intended behavior, please tell me how to turn the severe transparency off for the default tooltip since i am overriding it with my own using `_make_custom_tooltip()` (even though the issue still exists with the default ones). thank you.

### Steps to reproduce

1. Create a new projectin godot 4.3 (Mobile)
2. Make a 2D scene:
![Image](https://github.com/user-attachments/assets/f2d1eec2-98e2-4fb7-9837-528b61d1eaae)

3. Add a `WorldEnvironment`  Node as a child.
4. Add a new environment and in the "Background" subgroup in the editor, Change the mode to `Canvas` and set `Canvas Max Layer` to 1:
![Image](https://github.com/user-attachments/assets/3b23829e-8708-4e2c-9a58-3cedc3355472)

5. Add a `CanvasLayer` as the Child of Root `Node2D`. Set the `Layer` to anything greater than 1 (5 in my case):
![Image](https://github.com/user-attachments/assets/3bddc584-7f83-496e-93ea-283a0b620e88)

7. Add a `PanelContainer` as the child of `CanvasLayer`. Set the `TooltipText` to any text in the editor:
![Image](https://github.com/user-attachments/assets/ad855a16-b0e1-40f2-95ff-33080232173b)

8. Save and Run the Scene and Hover your mouse cursor over the `PanelContainer`. The (More) Transparent Tooltip Text will be displayed:
![Image](https://github.com/user-attachments/assets/46a1a1df-1981-42b3-b158-71e1a1077356)

9. Now Change the Background Mode of the `WorldEnvironment` to anything other than "Canvas".
![Image](https://github.com/user-attachments/assets/f16c76f6-3c65-4763-81fa-93b944fdfdbc)

10. Save and Run the Scene. Now the Popup (Tooltip) is being displayed as Intended:
![Image](https://github.com/user-attachments/assets/e22b30b1-0f34-43df-bb8d-1d7268f526c0)



### Minimal reproduction project (MRP)

[mrp-bg_canvas.zip](https://github.com/user-attachments/files/18221440/mrp-bg_canvas.zip)
Repository: go
Issue: go/parser: `goto;` is incorrectly valid
Labels: NeedsFix

While poking around the `go/types` internals, i noticed that nothing really "type-checks" `goto`s without labels.

First pass:
https://github.com/golang/go/blob/500675a7c8c72bd6b1054a7eb4daaf61970f5ad7/src/go/types/stmt.go#L578-L608

Second pass:
https://github.com/golang/go/blob/500675a7c8c72bd6b1054a7eb4daaf61970f5ad7/src/go/types/labels.go#L173-L176


Also it also turns out that:

```go
func test() {
    goto;
}
```

Is accepted by the `go/parser`. The spec disallows `goto`s without labels, so we should either return an appropriate error in `go/types` or `go/parser`. Currently  `go/types` returns an `InvalidSyntaxTree` error.

https://github.com/golang/go/blob/500675a7c8c72bd6b1054a7eb4daaf61970f5ad7/src/go/types/stmt.go#L605-L607

CC @griesemer @adonovan
Repository: vscode
Issue: В jupiter notebook создаются пустые ячейки с которыми нельяз взаимодействовать
Labels: info-needed,*english-please,translation-required-russian


Type: <b>Bug</b>

В какой-то момент после недавнего обновления появиласть проблема. Ячейка дя кода создаётся, но писать в неё нелья. Иногда помогает создать ещё одну ячейку и удалить сломанную. Иногда помогает только перезапуск

VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.19044
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 4600H with Radeon Graphics          (12 x 2994)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.36GB (25.67GB free)|
|Process Argv||
|Screen Reader|no|
|VM|50%|
</details><details><summary>Extensions (14)</summary>

Extension|Author (truncated)|Version
---|---|---
gc-excelviewer|Gra|4.2.62
plantuml|jeb|2.18.1
vscode-language-pack-ru|MS-|1.96.2024121109
debugpy|ms-|2024.14.0
isort|ms-|2023.10.1
python|ms-|2024.22.0
vscode-pylance|ms-|2024.12.1
datawrangler|ms-|1.14.0
jupyter|ms-|2024.11.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
pip-manager|sli|1.1.4


</details>
<!-- generated by issue reporter -->
Repository: flutter
Issue: [format] Set up line length & rules for Dart code when using VSCode
Labels: framework,c: proposal,P2,team-framework,triaged-framework

### Use case

Developers wanting to contribute to the framework (or engine), by writing Dart code, while having their VSCode `User` settings set to something that differs from the framework's settings.

Context:

In https://github.com/flutter/flutter/commit/5491c8c146441d3126aff91beaa3fb5df6d710d0 the settings for `formatOnSave` and `formatOnPaste` were removed, as those were explicitly set to `false`. This presumably restored VSCode's default settings to format by default.

I started work on fixing a bug in the framework, post the engine binaries outage from yesterday, having not worked on the framework since the auto format change landed. Since I was aware of the autoformatting change, I pulled from master at 11AM UTC+1 on 22/12/2024, to start without issues. However, when using the `Format Document` action in `carousel_test.dart` I had a formatting diff in a piece of code that I did not write.

However, I have the following in my `User` settings, which overrides the `Workspace` settings from VSCode, if it finds things that are not defined.

```
    "dart.lineLength": 120,
    "[dart]": {
        "editor.formatOnSave": true,
        "editor.formatOnType": true,
        "editor.rulers": [
            120
        ],
    },
```

Neither the `dart.lineLength` nor `editor.rulers` is defined by the framework's `settings.json`, so I think it will use my own (incorrect) settings?

### Proposal

Add 

```
    "dart.lineLength": frameworkLineLength,
    "[dart]": {
        "editor.formatOnSave": true,
        "editor.formatOnType": true,
        "editor.rulers": [
            frameworkLineLength
        ],
    },
```

to the framework's `.vscode/settings.json`, where `frameworkLineLength` is the desired value for formatting code in the framework. By making the line length & formatOnSave/Type explicit, we avoid this being overridden by user level settings.
Repository: PowerToys
Issue: Update fail, uninstall/reinstall fail
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.87.1 (version prior)

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Installer

### Steps to reproduce

Attempted to update from notice, just stopped with no notice. Tried 'modify' in Apps, it uninstalled, tried to install from Store - kept failing. Deleted references to Powertoys in C:, attempted install again, it did and got the message to bug report. Haven't run program yet.

### ✔️ Expected Behavior

see above

### ❌ Actual Behavior

see above

### Other Software

[PowerToysReport_2024-12-22-06-41-04.zip](https://github.com/user-attachments/files/18221709/PowerToysReport_2024-12-22-06-41-04.zip)
Repository: flutter
Issue: [proposal][wasm][ffi] AOT wasm interoperability
Labels: c: new feature,dependency: dart,will need additional triage,c: proposal,e: wasm

### Use case

wasm interoperability would offers great value to flutter's framework
I'm sure the team is aware of this [[1](https://github.com/dart-archive/wasm/issues/146#issuecomment-1578567050), [2](https://github.com/dart-archive/wasm/issues/146#issuecomment-1579495860)] given that there used to be a  [labs.dart.dev](https://pub.dev/publishers/labs.dart.dev/packages)'s package [wasm](https://pub.dev/packages/wasm) 
that was [discontinued](https://github.com/dart-archive/wasm/issues/146) in summer 2023;
according to this [comment](https://github.com/dart-archive/wasm/issues/146#issuecomment-1577707770) such decision was caused by 3 technical obstacles:
- lack of dart/flutter native assets feature
- lack of AOT mode of the wasm runtime of choice for ios
- need for a separated package for bindings

as of today there is visible momentum towards the clearing of the main obstacles

- dart has an [experimental native assets feature](https://github.com/dart-lang/native/tree/main/pkgs/native_assets_cli)
  - https://github.com/dart-lang/sdk/issues/50565
  - https://github.com/flutter/flutter/issues/129757
- [wasmedge](https://github.com/WasmEdge/WasmEdge) besides provide support for [several platforms](https://wasmedge.org/docs/category/supported-platforms) is working on wasm AOT fro android and ios
   - https://github.com/WasmEdge/WasmEdge/issues/2621

### Proposal

Track the clearing of technical blocker for a `wasm` implementation
and if/when these blockers are cleared resume/re-work the deprecated [package:wasm](https://pub.dev/packages/wasm)

#

cc @devoncarew @mit-mit @liamappelbe @hydai
Repository: godot
Issue: [3.x] Task.Delay throws NullReferenceException on HTML5 exports
Labels: bug,platform:web

### Tested versions

Reproducible in: v3.6.stable.mono.official [de2f0f147]
* Occurs both when "Export as Debug" is set and when it isn't.
* Does *not* occur on Windows exports


### System information

Windows 11 64-bit, Chrome 131.0.6778.205 

### Issue description

Awaiting `Task.Delay` works fine in editor builds, but crashes on HTML5 exports, showing the following message on the console (F12):

> Unhandled Exception:
> System.NullReferenceException: Object reference not set to an instance of an object.
>   at System.Threading.WasmRuntime.TimeoutCallback (System.Int32 id) <0x2f69080 + 0x0000a> in <filename unknown>:0 
> timeout callback threw a System.NullReferenceException

### Steps to reproduce

* Open the attached minimal reproduction project in Godot
* It contains a single script:
```csharp
public override void _Ready() {
    Task.Run(async () => {
        GD.Print("Waiting...");
        await Task.Delay(1000);
        GD.Print("Done");
    });
}
```
* Observe how it runs as expected in the editor
* Export to HTML5, then run `python -m http.server` when `cd`-d into the exported directory
* Browse `http://localhost:8000`, press F12 to keep the console window open
* Click `TaskDelayDemo.html` and observe the errors in the console, and that "Done" is never printed

### Minimal reproduction project (MRP)

[TaskDelayDemo.zip](https://github.com/user-attachments/files/18221915/TaskDelayDemo.zip)
Repository: flutter
Issue: [go_router] Add meta property to GoRoute for custom attributes
Labels: package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

### Use case

The meta property can be used to store additional metadata for routes, which can then be utilized for various purposes, such as generating navigation menus and managing permissions.

### Proposal

I would like to propose adding a meta property to the GoRoute class in the go_router package. This property would allow users to define custom attributes such as labels, icons, and permissions for routes.

Here is an example of how the GoRoute class could be extended with the meta property:

```dart
GoRoute({
  required this.path,
  this.name,
  this.builder,
  this.pageBuilder,
  super.parentNavigatorKey,
  super.redirect,
  this.onExit,
  super.routes = const <RouteBase>[],
  this.meta, // New meta property
});

// Usage example
GoRoute(
  path: '/home',
  name: 'home',
  builder: (context, state) => HomeScreen(),
  meta: {
    'label': 'Home',
    'icon': Icons.home,
    'permission': 'view_home',
  },
);
```
Repository: go
Issue: proposal: errors: In() to check Is against multiple errors
Labels: Proposal

### Proposal Details

**Problem**
The code looks redundant and cumbersome in cases when you need to check an error match several times. Example:
```go
func foo() {
  err := bar()
  if errors.Is(err, err1) || errors.Is(err, err2) || errors.Is(err, err3) {
    // some logic
  }
}
```

**Solution**
A new function that will allow you to check for errors like this:
```go
func foo() {
  err := bar()
  if errors.In(err, err1, err2, err3) {
    // some logic
  }
}
```

**Implementation**
```go
package errors

func In(err error, target ...error) bool {
  for _, v := range target {
    if errors.Is(err, v) {
      return true
    }
  }

  return false
}
```
Repository: go
Issue: proposal: x/crypto/ssh/knownhosts:  Add `LineWithMarker` function and `MarkerCert` and `MarkerRevoked` constants
Labels: Proposal,Proposal-Crypto

### Proposal Details

The [Line](https://cs.opensource.google/go/x/crypto/+/refs/tags/v0.31.0:ssh/knownhosts/knownhosts.go;l=455) function doesn't allow you to write known host lines with the optional `@cert-authority` and `@revoked` markers, I suggest we introduce a new function:


```go
const MarkerCert = "@cert-authority"
const MarkerRevoked = "@revoked"

func LineWithMarker(marker string, addresses []string, key ssh.PublicKey) string {
	if marker != "" {
		return marker + " " + Line(addresses, key)
	} else {
		return Line(addresses, key)
	}
}
```
Repository: svelte
Issue: Static support for `$state` in `.svelte.ts`
Labels: feature request,runes

### Describe the problem

I have a class that is entirely static (only static properties and methods). I cannot declare a `$state` property, either with a field initializer or in a static initialization block. In both cases, Svelte complains that:

>_Error: CompileError: state_invalid_placement: `$state(...)` can only be used as a variable declaration initializer or a class field

Of course, this is a class field, it's just that it's a static field, which seems to be unsupported for some reason.

### Describe the proposed solution

Support static class fields.

### Importance

would make my life easier
Repository: flutter
Issue: [pigeon] Kotlin code should be `internal`
Labels: package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

As noted in https://github.com/flutter/flutter/issues/160737, we are currently generating Kotlin code using public visibility, which isn't what we want. `internal` would be consistent with Swift and with our usage guidance.
Repository: pytorch
Issue: add "enabled=True" to DistributedDataParallel.no_sync()
Labels: oncall: distributed,module: ddp

### 🚀 The feature, motivation and pitch

Training a model with DDP and gradient accumulation is quite common.
To avoid unnecessary sync, the no_sync() operation is used.

Providing an `enabled=True` argument is already done in pytorch, and is very useful in pytorch in `torch.amp.autocast` and `torch.amp.GradScaler`.

```
if (step % grad_accum_steps + 1) == 0:
    # forward+ backward code
    loss = ddp_model(inputs)
    (loss / grad_accum_steps).backward()
else:
    with ddp_model.no_sync():
         # forward + backward code
         loss = ddp_model(inputs)
        (loss / grad_accum_steps).backward()
```
using the `enabled` argument this can be simplified, preventing bug-prone code duplications:
```
with ddp_model.no_sync(enabled=(step % grad_accum_steps + 1) != 0):
    loss = ddp_model(inputs)
    (loss / grad_accum_steps).backward()
```


The implementation doesn't seem hard, and it will be back-compatible.

### Alternatives

_No response_

### Additional context

DDP with grad accum:
https://discuss.pytorch.org/t/gradient-accumulation-with-ddp-no-sync-interface/169593/3

Current no_sync implementation:
https://github.com/pytorch/pytorch/blob/main/torch/nn/parallel/distributed.py#L1420

torch.amp.autocast enabled=True API:
https://github.com/pytorch/pytorch/blob/09c950cc872dfcee453307db47fa10553c3f5616/torch/amp/autocast_mode.py#L222 

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: TypeScript
Issue: Inconsistent types between Document scrollingElement and documentElement
Labels: Bug,Help Wanted,Domain: lib.d.ts

### 🔎 Search Terms

I think `document.scrollingElement` should be of type `Document["documentElement"] | null` instead of `Element | null`. The spec (e.g. [this](https://developer.mozilla.org/en-US/docs/Web/API/Document/scrollingElement) and [this](https://drafts.csswg.org/cssom-view/#dom-document-scrollingelement)) says that in standards mode `scrollingElement` returns the document root, which is `document.documentElement` and in quirks mode returns `document.body` or `null`.

`document.body` is always `HTMLElement` (right?) In principle, `document.documentElement` does not have to be `HTMLElement` (and there's an open issue about this, #29052, but currently `Document.documentElement` is still defined as `HTMLElement`, for some reason. So how come `document.scrollingElement` is not `HTMLElement | null`?

### 🕗 Version & Regression Information

N/A


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
// Your code here
```


### 🙁 Actual behavior

`document.scrollingElement` is of type `Element | null` whereas `document.documentElement` and `document.body` are both of type `HTMLElement`.

### 🙂 Expected behavior

The non-null part of `document.scrollingElement` should be the same type as `document.documentElement`, which technically should be `Element`, but if `document.documentElement` is left as `HTMLElement`, as is currently, then `document.scrollingElement` should also be this.

### Additional information about the issue

_No response_
Repository: angular
Issue: Forms documentation is out-of-date
Labels: area: forms,area: docs

### Describe the problem that you experienced

The documentation on Reactive Forms describes how ReactiveFormsModule must be imported into your NgModule.

https://angular.dev/guide/forms/reactive-forms#import-the-reactiveformsmodule

It doesn't describe how to use reactive forms with standalone components at all.

Is this another one of those areas (like [this](https://github.com/angular/angular/issues/58583) one) where we will be told that we shouldn't bother looking for answers in the official documentation?

Neither the Routing nor the Forms documentation is up-to-date for v19. These are key systems! 

You've clearly been working on the change from module-based to standalone components for a couple of years now, but the different parts of the documentation are variously described either from a standalone or module-based perspective, with no feature described in both scenarios.

And when this is pointed out the response is that we shouldn't expect to find useful information about this in the official docs. 

It's really bad.

### Enter the URL of the topic with the problem

https://angular.dev/guide/forms/reactive-forms#import-the-reactiveformsmodule

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: kubernetes
Issue: kubelet ignores updated `etcd.yaml` and monitors only `etcd.yaml.backup`
Labels: kind/documentation,kind/support,sig/node,triage/accepted

### What happened?

During the `kubeadm upgrade` process, `kubeadm` creates a backup of the existing etcd manifest (`etcd.yaml.backup`) and updates the `etcd.yaml` manifest to a newer version (e.g., from etcd 3.4.13-0 to 3.5.16-0). However, post-upgrade, the `kubelet` appears to ignore the updated `etcd.yaml` and continues to monitor and apply changes only to `etcd.yaml.backup`. This behavior prevents the etcd cluster from upgrading, causing the `kubeadm upgrade` process to fail.

### What did you expect to happen?

After initiating the kubeadm upgrade:

- kubeadm should update the etcd.yaml manifest to the new etcd version (3.5.16-0).
- kubelet should detect changes in etcd.yaml, apply the updated configuration, and successfully upgrade the etcd cluster to version 3.5.16-0.
- The etcd.yaml.backup should remain as a backup and kubelet should continue to monitor only the primary etcd.yaml manifest.

### How can we reproduce it (as minimally and precisely as possible)?

There are two methods to reproduce the issue: Automated Upgrade via kubeadm and Manual Updating of etcd.

**Automated Upgrade via kubeadm:**
   - Attempt to upgrade the cluster using kubeadm to upgrade etcd to version 3.5.16-0:

>    `kubeadm upgrade apply v1.32.0`

   - kubeadm creates `etcd.yaml.backup` and updates `etcd.yaml` to version 3.5.16-0.
   - `kubelet` ignores `etcd.yaml`(verison 3.5.16-0 ) and only monitors `etcd.yaml.backup` ( version 3.4.13-0), preventing the etcd upgrade.

**Manual :**
 
- Create a backup of the existing `etcd.yaml` file: 
`cp /etc/kubernetes/manifests/etcd.yaml /etc/kubernetes/manifests/etcd.yaml.backup`

- Open etcd.yaml in a text editor and update the etcd image version from `3.4.13-0` to `3.5.16-0`.
- Restart the kubelet service: 
`systemctl restart kubelet`

### Anything else we need to know?

_No response_

### Kubernetes version

<details>


```console
$ kubectl version
Client Version: v1.32.0
Kustomize Version: v5.5.0
Server Version: v1.31.4
```

</details>


### Cloud provider

<details>
On-premises bare-metal servers
</details>

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>
containerd
</details>

### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>