sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: missing setup for devtools cypress tests (potentially dead code)
Labels: area: devtools

### Is this a bug report or a feature request?

- [X] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

There's a [whole directory for cypress tests](https://github.com/angular/angular/tree/main/devtools/cypress) along with [config files](https://github.com/angular/angular/blob/main/devtools/cypress.json) which might be dead code. My guess is that might become dead after moving from package.json to bazel, since - according to git blame - the [appropriate cypress commands used to be there in the repo](https://github.com/rangle/angular-devtools/pull/45/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R10-R11). And now in https://github.com/angular/angular/blob/main/devtools/BUILD.bazel#L8 only cypress.json is exported, but no commands seem to be run.

I was thinking of providing end-to-end (or at least wide scope integration tests) for devtools anyway.

PS This is an issue (not a PR) since I don't know which direction should we move forward.



### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

Either we make cypress executable or we remove the tests entirely.

### Please provide a screenshot if possible [Bug Report only]

_No response_

### Please provide the exception or error you saw [Bug Report only]

_No response_

### Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

_No response_

### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_
Repository: next.js
Issue: Error Generating Sitemap with "output: export" config
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/generate-sitemap-with-output-export-h5v4vg

### To Reproduce

1. Open the CodeSandbox [sample](https://codesandbox.io/p/devbox/generate-sitemap-with-output-export-h5v4vg)
2. Access url within the sandboxed environment by navigating to [https://h5v4vg-3000.csb.app/sitemap.xml](https://h5v4vg-3000.csb.app/sitemap.xml)

### Current vs. Expected behavior

### Description:
Attempting to generate a sitemap using the provided example from the [official Next.js documentation](https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap#generate-a-sitemap) results in an error when the output is set to "export". The code functions correctly with output set to "standalone".

### Code Used:
```
// app/sitemap.js
export default async function sitemap() {
    return [
        {
            url: 'localhost:3000/',
            lastModified: new Date(),
            changeFrequency: 'yearly',
            priority: 1,
        },
       // ...other URLs
    ]
}
```
Next.js Configuration:
```
/** @type {import('next').NextConfig} */
const nextConfig = {
  output: "export",
};

module.exports = nextConfig;
```

### Current Behavior:
Accessing the "/sitemap.xml" endpoint results in a Server Error:

> Error: Page "/sitemap.xml/[[...__metadata_id__]]/route" is missing exported function "generateStaticParams()", which is required with "output: export" config.

### Expected Behavior:
Accessing "/sitemap.xml" should display the generated sitemap page without errors.

### 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 11 Pro
Binaries:
  Node: 20.6.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4-canary.28
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5
Next.js Config:
  output: export
```


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

Metadata (metadata, generateMetadata, next/head), Static HTML Export (output: "export")

### Additional context

_No response_
Repository: godot
Issue: Setter not called when changing value within dictionary
Labels: discussion,topic:gdscript,documentation

### Godot version

4.2 stable

### System information

Windows 10

### Issue description

Changing a dictionary with a setter method calls the setter method.
e.g.
```
var d : Dictionary : set = _set_d

func _set_d( v ):
   v = d

func test():
d = { v = 1 } # this calls the setter method
d.v = 2 # this does not call the setter method
```
I've included an overly complicated example in this issue.

### Steps to reproduce

```
var d : Dictionary : set = _set_d

func _set_d( v ):
   v = d

func test():
d = { v = 1 } # this calls the setter method
d.v = 2 # this does not call the setter method
```

### Minimal reproduction project

[2023_12_Test_Setter.zip](https://github.com/godotengine/godot/files/13518736/2023_12_Test_Setter.zip)
Repository: flutter
Issue: Create a theme flag that turns on automated platform adaptations for all applicable Material widgets
Labels: 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

In the future, we should consider having a flag that controls all (or specific groups of) platform adaptations. So, instead of a developer using the adaptive constructors throughout their app, they can turn adaptations on or off for their entire app. 

We can consider other ways to implement or compliment this, like in component themes - where the developer might turn on adaptations for all Switch widgets. 


### Proposal

This requires a bit more thought around implementation. For example, we have adaptations that already happen automatically - so we should make it clear which adaptations any flags would actually control. This work also relies on migrating cupertino functionality to use the Material library.
Repository: three.js
Issue: SpotLight map affected by distance updates
Labels: Suggestion

### Description

I recently noticed that when updating the distance of a spotlight to 0, the texture shined on a mesh is affected by whether the distance to the mesh prior was larger or smaller than the previous spotlight.distance value. When the prior spotlight.distance value was smaller than the distance to the mesh, the map is not reflected on the object. If it was larger, the map is still there as expected. Please see the jsfiddle below for an example

jsfiddle: https://jsfiddle.net/3rj7u8n9/99/

I'm assuming this is not expected behavior and could be a bug? I've tested this on both my Macbook Pro with Chrome and on iOS Safari and the behavior is the same on both


### Reproduction steps

1. Create a spotlight with a map set and any mesh to shine the light on
2. Set the spotlight distance to some value less than the distance to the mesh
3. Set the spotlight distance to 0 (the map is no longer shown on the mesh


### Code

```js
// Please see jsfiddle for example
```


### Live example

https://jsfiddle.net/3rj7u8n9/99/

### Screenshots

_No response_

### Version

r159

### Device

Desktop, Mobile

### Browser

Chrome, Safari

### OS

MacOS, iOS
Repository: terminal
Issue: The CursorStyle in TerminalTheme does not seem to work
Labels: Help Wanted,Issue-Bug,Product-Terminal,Area-WPFControl

### Windows Terminal version

be9fc200c7b22c544103ec3304ca31c3b984031e

### Windows build number

10.0.22631.2715

### Other Software

_No response_

### Steps to reproduce

https://github.com/microsoft/terminal/blob/main/src/cascadia/WpfTerminalTestNetCore/MainWindow.xaml.cs#L101

Change `BlinkingBar` to `BlinkingBlock`

### Expected Behavior

_No response_

### Actual Behavior

![image](https://github.com/microsoft/terminal/assets/2220320/98a664b8-574f-4635-b914-797a97666cc4)

It's still `BlinkingBar`
Repository: vscode
Issue: Trying to populate a `DiagnosticCollection` progressively results in excessive calls to CodeAction provider.
Labels: feature-request,languages-diagnostics

Version: 1.84.2 (user setup)
Commit: https://github.com/microsoft/vscode/commit/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22631

I'm reworking how the C/C++ extension populates diagnostics (and inlay hints, semantic tokens, etc.), to progressively populate the document as additional results are available.

It looks like `DiagnosticCollection` does not currently provide an efficient way to add `Diagnostic`'s to an existing set.  It's necessary to get the array of `Diagnostic`s, make a change, then set it again.  I'm seeing that, with a large file, and several iterations of augmenting that list of diagnostics, that I get redundant (expensive) requests to provide `CodeAction`'s for `Diagnostic`s that are not 'new'.  Also, if the user clicks on that bit of code, they will see the `CodeAction` lightbulb disappear out from under them when unnecessarily regenerated.

Perhaps this could be addressed by adding an 'add' function to `DiagnosticCollection`, or maybe keeping a cached list of existing `Diagnostics` to avoid redundantly requesting `CodeAction`s for.
Repository: go
Issue: x/mobile:  cannot use generic type demo.GenericTestData[T any] without instantiation
Labels: NeedsInvestigation,mobile,generics

I have a piece of code：

func NewGenericTestData[T any](path string) *GenericTestData[T] {
	return &GenericTestData[T]{
		dataPath: strings.TrimRight(path, "/"),
	}
}

type GenericTestData[T any] struct {
	dataPath string
	*CBaseInfo
	Data T
}

When I run gomobile, I get an error: cannot use generic type demo.GenericTestData[T any] without instantiation
Repository: ant-design
Issue: 在Upload组件传入showUploadList中的showPreviewIcon:true时，预览图标未展示，而下载图标可正常展示
Labels: 💡 Feature Request,Inactive,unconfirmed

### Reproduction link

[https://github.com/zhangzhengyi0220/antd-demo](https://github.com/zhangzhengyi0220/antd-demo)

### Steps to reproduce

我在page.tsx中引入了Upload组件，传入属性：showUploadList={{ showPreviewIcon: true, showDownloadIcon: true }}，npm run dev:项目启动后，点击上传文件按钮，上传一个文件，上传成功后，鼠标移到文件上，查看图标展示情况。

### What is expected?

showUploadList对象中传入showPreviewIcon:true，预览图标可正常展示，否则无法触发预览回调函数。

### What is actually happening?

只有下载图标可以展示，预览图标没有展示，右键检查发现，预览图标没有在dom中

| Environment | Info |
| --- | --- |
| antd | 5.11.5 |
| React | 18 |
| System | Windows11 |
| Browser | edge 119.0.2151.93 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: Deno gfm vendoring issues
Labels: bug,design limitation,vendor

Version: Deno 1.38.4

I encountered a bug related to vendoring dependencies while using deno. The problem becomes apparent when attempting to vendor the [deno-gfm](https://github.com/denoland/deno-gfm) library. For detailed information on how to reproduce this issue, please refer to the repository:

https://github.com/mcandeia/deno-vendor-bug

To reproduce, fork the repository and try to run with `--no-remote` options poiting to vendor/import_map.json file
Repository: go
Issue: cmd/compile: pgo weighted merge support
Labels: NeedsInvestigation,compiler/runtime

Go PGO [documentation](https://go.dev/doc/pgo#merging-profiles) shows support for merging multiple PGO profiles. However, as far as I see, there is no support for adding a weight to each profile. I quickly [checked](https://github.com/google/pprof/blob/main/profile/merge.go) the `pprof` merge implementation and also didn't find a way to add weights to profiles for the merge operation.

In the current guideline already there is a note about merging multiple profiles into one:

> Merge profiles across workloads: take profiles from each workload (weighted by total footprint) and merge them into a single “fleet-wide” profile used to build a single common profile used to build. This likely provides modest performance improvements for all workloads.

But it also says nothing about adding weights to the profiles.

The use case for such functionality is the following. We gathered N profiles from different workloads. According to our needs, one workload is our primary workload, and others are secondaries. So we want to add some multiplier to optimize as much as possible for our main workload, and optimize for our secondary workloads too but with a lower priority.

`llvm-profdata` tool [supports](https://llvm.org/docs/CommandGuide/llvm-profdata.html#cmdoption-llvm-profdata-merge-weighted-input) weighted merge ([here](https://llvm.org/docs/CommandGuide/llvm-profdata.html#weighted-input) are some invocation examples).

Right now I see the following ways, how it can be mitigated:

* (an easy way) If we want to perform merging for profiles A and B with weights 2 and 1 correspondingly, we need to copy A profile, then merge 3 profiles: A, A_copy, B. In theory, it would be equal to the weight 2 near the A profile. However, not the best UX.
* (a hard way) Parse PGO profiles somehow and tweak internal counters with some weight multiplier. Doable but hard to implement.

If you think having such functionality is important for PGO users in Go, I kindly ask implement it. Before the weight implementation, we can put the temporal mitigations to the documentation (of course if they work - I didn't test them yet). Probably it will require some changes on the `pprof` side.
Repository: go
Issue: cmd/compile: pgo support for external Linux perf profiles and perf_data_converter
Labels: help wanted,NeedsInvestigation,compiler/runtime

Go PGO docs [mentions](https://go.dev/doc/pgo#alternative-sources) some support for the external profile tooling and has [a reference](https://github.com/golang/go/wiki/PGO-Tools) to the external page about supported PGO tools. Having support for the external profiling tooling is important since some organizations already have their profiling infrastructure (GWP in Google, Perforator in Yandex, sometimes even [Grafana Pyroscope](https://grafana.com/oss/pyroscope/) or similar in-house solutions).

The official documentation explicitly mentions widely used Linux' `perf` profiles for PGO purposes. Using these profiles are common thing in the C++ world due to sampling PGO support with [AutoFDO](https://github.com/google/autofdo) tooling.

`pprof` package has [a reference](https://github.com/google/pprof#using-pprof-with-linux-perf) to a converter from Linux `perf` profiles to `pprof` profiles - https://github.com/google/perf_data_converter . Did anyone try to test it with Go PGO? Is it possible with this tool to use `perf` profiles to enable PGO optimization with the current PGO infrastructure in the Go compiler?

If it works, I suggest adding a mention about `perf_data_converter` to the https://github.com/golang/go/wiki/PGO-Tools page. Having a possibility to use Linux' `perf` profiles can be important since it allows users to implement company-wide PGO optimization pipelines in the same way as it's done for C++ infrastructure (infrastructure and tooling reusage, you know).
Repository: TypeScript
Issue: Declaration emit fails to import symbol on function auto-property
Labels: Bug,Domain: Declaration Emit

### 🔎 Search Terms

mixin symbol not imported function property

### 🕗 Version & Regression Information

- This changed between version _3.7.7_ and _3.8.1_, it went from working to being an error.
- This changed between version _4.2.4_ and _4.3.2_, it went from being an error to invalid.

### ⏯ Playground Link

https://www.typescriptlang.org/dev/bug-workbench/?#code/PTAEAEBMFMGMBsCGAnRAXAlgewHYC5Q1kBXaAKBAgGcALLAdwFEBbDNCscWhlttaSADEM8aAQw4YADwB0kGWipkMzAA5ZkaUAG9QrKRNABfUADNkWZqABEM4MminrAbjJkEiKlVCCsWUNBS-JLe+hIAFB5eOkYAlDpkoEmgZEZugeqaOj5+xm6U4KYi0DiIzGKgDqYKSu64VFpUAJ5WALygAMotAEZY8OGxZKbEOLCYuHoYBjgAPAAqAUElkN440PSg4TLbKADmVASIOE0A2gC68a0AfKBY3QBWcGhX4d2eFXPx2onJiN0NqDGoCi3gAsotgitQG8qNAEskEaATmEcDJmswzqB2kRSD8kmkEQ40MRkDhQKDUmQUWiWljQOjXGQMhotLoUcYgA

### 💻 Code

```ts
import { mixin } from "./ref";

class Foo extends mixin(class {}) {
    
}

export { Foo }
```

```ts
// @filename: ref.ts

const sym = Symbol()
function mixin<T extends new (...args: any[]) => object>(base: T) {
    abstract class M extends base {
        [mixin.sym] = true
    }
    return M
}
mixin.sym = sym;

export { mixin }
```


### 🙁 Actual behavior

The symbol `sym` is not referenced properly in the emitted `.d.ts` it is an undefined name, nor is an error thrown:
```ts
import { mixin } from "./ref";
declare const Foo_base: (abstract new (...args: any[]) => {
    [sym]: boolean;
}) & {
    new (): {};
};
declare class Foo extends Foo_base {
}
export { Foo };
```

### 🙂 Expected behavior

The symbol `sym` should be referenced as it's used `mixin.sym`
```ts
import { mixin } from "./ref";
declare const Foo_base: (abstract new (...args: any[]) => {
    [mixin.sym]: boolean;
}) & {
    new (): {};
};
declare class Foo extends Foo_base {
}
export { Foo };
```
or an error should be thrown.

### Additional information about the issue

From v3.3.3 to v3.7.7 this technique worked as expected. From v3.8.1 to v4.2.4 this technique resulted in a compiler error. And from v4.3.2 onward this technique has emitted invalid code.

This bug surfaced trying to workaround the fact that `const sym` is not exported and is a private name.
Repository: flutter
Issue: [camera] Get FlashMode capabilities for camera
Labels: c: new feature,p: camera,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

### 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

I'd like a way determine which `FlashMode`'s are supported by a camera. Ideally I could determine for each camera, which presumably in most cases would be whether the flash is in same direction.

The package currently has the following flash modes and I'd like to know which modes are valid for each camera:
`enum FlashMode { off, auto, always, torch }`
It seems `off` should always be valid, but perhaps there are edge cases I'm not aware of.

### Proposal

Perhaps add a `List<FlashMode>` of supported flash modes called `flashModes` to `CameraDescription`.
Repository: pytorch
Issue: print statements used in torch/utils/cpp_extension.py
Labels: module: cpp-extensions,triaged,better-engineering,actionable

### 🐛 Describe the bug

There are a lot of `print()` statements in `torch/utils/cpp_extension.py` ([here](https://github.com/pytorch/pytorch/blob/4875e4d63fa3e64c4fcd88c079fc7699b3e89d74/torch/utils/cpp_extension.py#L2034) for example). I don't think this is good practice. Maybe we should consider the standard `logging` package instead?

### Versions

Irrelevent

cc @malfet @zou3519
Repository: godot
Issue: Changed Signal not emitting on certain Resources.
Labels: discussion,topic:core

### Godot version

v4.2.stable.official [46dc27791]

### System information

Godot v4.2.stable - Ubuntu 22.04.3 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (nvidia; 535.129.03) - Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 Threads)

### Issue description

I am finding some Resource types that are not emitting the "changed" signal. Not sure whether it's a me thing or a bug.

I did search the source for BoxMesh, which led me to `void PrimitiveMesh::_update()` which appears to have `const_cast<PrimitiveMesh *>(this)->emit_changed();` at the bottom, so it looks like it's emitting.

When I test that, the signal does not seem to arrive.

https://github.com/godotengine/godot/blob/d76c1d0e516fedc535a2e394ab780cac79203477/scene/resources/primitive_meshes.cpp#L129C2-L129C52

### Steps to reproduce

My small demo shows it, but here's the basic code:

```Python
@tool
extends Node2D

## Click the Tog to start the code
@export var tog:bool:
	set(b):
		test()

func _prim_changed():
	print("!! _prim_changed <-- This does not run automatically.")

func _noise_changed():
	print("!! _noise_changed <-- this one works!")

func _cust_sig_func():
	print("sigfunc1")

func test():
	print()
	print()

	## Custom Resource signal is ok.
	var R:Resource = Resource.new()
	R.changed.connect(_cust_sig_func)
	R.changed.emit() # works.

	## This "built-in" seems to emit changed signal ok...
	var noise:FastNoiseLite = FastNoiseLite.new()
	noise.changed.connect(_noise_changed) # changed? YES!
	noise.domain_warp_enabled = true

	## None of these seem to emit the changed signal...
	## Docs say: Emitted when the resource changes, usually when one of its properties is modified.
	var builtinBox : BoxMesh
	builtinBox = BoxMesh.new()
	builtinBox.changed.connect(_prim_changed)
	builtinBox.set("size", Vector3(10,10,10) ) # changed? Nope.
	builtinBox.subdivide_depth = 2 # changed? Nope.

	var builtinSphere : SphereMesh
	builtinSphere = SphereMesh.new()
	builtinSphere.changed.connect(_prim_changed)
	builtinSphere.height = 2.0 # changed? Nope

	var builtinPrim : PrimitiveMesh
	builtinPrim = PrimitiveMesh.new()
	builtinPrim.changed.connect(_prim_changed)
	builtinPrim.flip_faces = true # change? Nope

```

Same happening on at least 4.2 RC1 

### Minimal reproduction project

https://gitlab.com/dbat/godot-resource-emit-changed-issue
Repository: kubernetes
Issue: events: use contextal logging
Labels: kind/feature,sig/instrumentation,triage/accepted,wg/structured-logging

### What would you like to be added?

Whenever events get emitted, `WithLogger` should be added before the method call.

/sig instrumentation
/wg structured-logging


### Why is this needed?

From 27a68aee3a483:

     Both EventRecorder interfaces in tools/events and tools/record now have a
     WithLogger helper. Using that method is optional, but recommended to support
     contextual logging properly. Without it, errors that occur while emitting an
     event are not associated with the caller.
Repository: PowerToys
Issue: OneNote plugin to search sections too, not only notes
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

It would be invaluable to add the ability to search **sections** in OneNote. Please, please add it.  🙏 Thank you in advance 🙇‍♂️

### Scenario when this would be used?

For example, I am keeping all my meeting notes with Union Palenshus in a **section** "OZ-Palenshus", and I want to open that **section** to see the list of all my notes. Currently I can only search by a particular note name. 

### Supporting information

_No response_