sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: docs: add docs on RouteReuseStrategy 
Labels: P3,area: docs

### Describe the problem that you experienced

There are no docs on how this feature works.

https://github.com/angular/angular/issues/55207

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

_No response_

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

_No response_

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

_No response_

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

_No response_
Repository: ollama
Issue: Add enhancement to allow RAG functionnality
Labels: feature request

### What are you trying to do?

I want use a custom script on ollama server (windows) to execute Retrieval Augmented Generation (RAG) process. How can I do ?
(I have an example which is working with a python script, langchain and ollama but I can't do it behing the ollama server using api restful).

### How should we solve this?

Allow Retrieval Augmented Generation (RAG)  or add an example

### What is the impact of not solving this?

_No response_

### Anything else?

_No response_
Repository: electron
Issue: [Feature Request]: expose process.crashReporter.adExtraParameter to utility processes
Labels: enhancement :sparkles:,component/crash-reporter

### 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 feature request that matches the one I want to file, without success.

### Problem Description

There is no way to set crash reporter parameters [`crashReporter.addExtraParameter`](https://www.electronjs.org/docs/latest/api/crash-reporter#crashreporteraddextraparameterkey-value) from a [utility process](https://www.electronjs.org/docs/latest/api/utility-process).

### Proposed Solution

expose `process.crashReporter[.addExtraParameter]` to utility processes.

### Alternatives Considered

Not aware of any. You can't send messages to the main/browser process to do this since the API is per-process, and calling it in main will not set the metadata for crashes that occur in the utility process that wanted it. 

### Additional Information

There was a [previous issue](https://github.com/electron/electron/issues/41445) filed, which was closed for "being a question" when this is most definitely a feature request.

If the team will consider this, would love to contribute it.
Repository: vscode
Issue: Git - beyond a symbolic link error
Labels: bug,git

I see this error in dev console with this [repo](https://github.com/tree-sitter/tree-sitter-typescript) checked out:

```
[Extension Host] rejected promise not handled within 1 second: Git error {
  "exitCode": 128,
  "stdout": ".gitignore\u00009\u0000package-lock.json\u0000/Users/ulugbekna/code/tree-sitter-typescript/package-lock.json\u0000.gitignore\u00008\u0000Cargo.lock\u0000/Users/ulugbekna/code/tree-sitter-typescript/Cargo.lock\u0000",
  "stderr": "fatal: pathspec '/Users/ulugbekna/code/tree-sitter-typescript/typescript/corpus/common/types.txt' is beyond a symbolic link\n"
} (at console.<anonymous> (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:142:60451))
```

<img width="1395" alt="image" src="https://github.com/microsoft/vscode/assets/16353531/4e3287a2-9ce1-4ca2-b713-21fb91c9c803">


git version 2.44.0

Version: 1.88.0-insider
Commit: 57028e3d274ebde851c7cc02123def372ca619a6
Date: 2024-04-03T04:44:44.440Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
Repository: flutter
Issue: Gradle Plugin Error When Creating New Flutter Project in Android Studio
Labels: platform-android,tool,t: gradle,P3,team-android,triaged-android

### Description

When creating a new Flutter project in Android Studio from scratch, I encounter an unexpected Gradle plugin error. Normally, such errors might be expected in existing, older projects, where a manual migration could resolve the issues. However, when starting a new project from scratch, I anticipate that the project setup should correctly handle such configurations without encountering these errors. My Flutter version is up-to-date. Below are the details of the error message encountered:

> You are applying Flutter's app_plugin_loader Gradle plugin imperatively using the apply script method, which is deprecated and will be removed in a future release. Migrate to applying Gradle plugins with the declarative plugins block: https://flutter.dev/go/flutter-gradle-plugin-apply
> 
> 
> FAILURE: Build failed with an exception.
> 
> * Where:
> Build file 'C:\Users\dev\StudioProjects\untitled99\android\app\build.gradle' line: 2
> 
> * What went wrong:
> Plugin [id: 'com.android.application'] was not found in any of the following sources:
> 
> - Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
> - Plugin Repositories (plugin dependency must include a version number for this source)
> 
> * Try:
> > Run with --stacktrace option to get the stack trace.
> > Run with --info or --debug option to get more log output.
> > Run with --scan to get full insights.
> 
> * Get more help at https://help.gradle.org
> 
> BU�LD FAILED in 11s
> Error: Gradle task assembleDebug failed with exit code 1

I am seeking advice from other developers who have encountered and resolved this issue, or directly from the Flutter team. Detailed information on the cause of this problem and how to solve it would be greatly appreciated.
Repository: kubernetes
Issue: Allow "level" key in the JSON logger
Labels: sig/instrumentation,triage/accepted

Greetings maintainers,

_(This is issue has been inherited from https://github.com/kubernetes-sigs/metrics-server/issues/1426)_

Currently, there's no way to define LoggingConfiguration of a JSONLogger from component-base in such a way that it ends up exposing JSON logs with a "level" field (values: "info", "warn", "error", etc.) which can be a very informative attribute of logs in terms of observability and translating telemetry out of them (while having low cardinality).

This is because of component-base:
- being programmed to omit LevelKey as its default zapcore EncoderConfig ([Ref](https://github.com/kubernetes/component-base/blob/master/logs/json/json.go#L66-L74))
- being hardcoded to follow the code-path always leading to using this default EncoderConfig ([Ref](https://github.com/kubernetes/component-base/blob/master/logs/json/json.go#L142-L145))



If you note in the last comment of the aforementioned issue (https://github.com/kubernetes-sigs/metrics-server/issues/1426#issuecomment-2017236912), 
I just a fix well which I have paraphrased below as well

> What could be the fix then?
> 
> Smallest one, yet not so clean one: Modify the component-base's NewJSONLogger to include LevelKey as well in its default EncoderConfig i.e. the following two lines of code to be added [here](https://github.com/kubernetes/component-base/blob/master/logs/json/json.go#L66-L74)
> 		LevelKey:       "level",
> 		EncodeLevel:    zapcore.LowercaseLevelEncoder,
> [Working example](https://go.dev/play/p/EEd5uKffO3x)
> 
> Larger but cleaner and extensible one: Modify component-base to allow clients like metrics-server to provide more granular options like providing EncoderConfig for the underlying JSON logger to use instead of blatantly using nil (causing it to forcefully use the default encoderconfig)


If you find this issue worthy of being addressed, I would love to work on it considering I have already navigated the codebase of component-base fairly enought the understand the places which would require any potential changes.

Thank you for your time, patience and efforts maintaining this useful codebase  <3
Repository: godot
Issue: MouseButton Keys do not get cleared when debugging in VisualStudio (C#)
Labels: bug,topic:dotnet,topic:input

### Tested versions

Reproducible in Godot v4.2.1-stable-mono-win64 & Visual Studio 17.8.1

### System information

Godot v4.2.1.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; 31.0.15.3758) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

### Issue description

When debugging a C# Script in the Visual Studio IDE and stopping at a brakepoint, while listening for Mouse Inputs, the Button Status does not reset between calls. This only occours when starting the program diredtly via the VisualStudio debugger. When executed in the Godot Enginge directly the state gets cleared as expected.

### Steps to reproduce

1. Create new Project
2. Configure VisualStudio debugging
3. Add C# Script with the following code to a Node
```csharp
public override void _Input(InputEvent e)
{
    switch (e)
    {
        case InputEventMouseButton:
            if (Input.IsMouseButtonPressed(MouseButton.Left))
            {
                MouseButtonMask x = Input.GetMouseButtonMask();
                GD.Print(x);
            }
            break;
    }
}
```
4. Add breakpoint
5. Execute program in VisualStudio (F5) and click left mouse button
6. Resume program after breakpoint is reached
7. Click any other mouse button

### Minimal reproduction project (MRP)

[BugTest.zip](https://github.com/godotengine/godot/files/14874864/BugTest.zip)
Repository: go
Issue: proposal: net: allow ParseMAC to handle pure base-16 numerical representation without hyphens
Labels: Proposal

### Proposal Details

The `ParseMac` function in https://github.com/golang/go/blob/master/src/net/mac.go says:

```
// ParseMAC parses s as an IEEE 802 MAC-48, EUI-48, EUI-64, or a 20-octet
// IP over InfiniBand link-layer address using one of the following formats:
//
//	00:00:5e:00:53:01
//	02:00:5e:10:00:00:00:01
//	00:00:00:00:fe:80:00:00:00:00:00:00:02:00:5e:10:00:00:00:01
//	00-00-5e-00-53-01
//	02-00-5e-10-00-00-00-01
//	00-00-00-00-fe-80-00-00-00-00-00-00-02-00-5e-10-00-00-00-01
//	0000.5e00.5301
//	0200.5e10.0000.0001
//	0000.0000.fe80.0000.0000.0000.0200.5e10.0000.0001
```

When reading the [EUI guidelines](https://standards.ieee.org/wp-content/uploads/import/documents/tutorials/eui.pdf) however, it states in section "EUI Structure and Representation":

> ...[EUI-48/EUI-64] can be represented in the IEEE RA hexadecimal (hex) form with the octets separated by hyphens, or as a pure base-16 numerical representation without hyphens. It may also be represented as a binary number or sequence, as illustrated.

And on [Wikipedia](https://en.wikipedia.org/wiki/MAC_address):
> As typically represented, MAC addresses are recognizable as six groups of two [hexadecimal](https://en.wikipedia.org/wiki/Hexadecimal) digits, separated by hyphens, colons, or without a separator.

I haven't come across binary representations as the guidelines say are allowed, but it does happen (frequently enough) that the octets don't have a separator. In those cases I had to resort to a custom implementation of `HardwareAddr` just to deal with that case. I was not sure if this would be considered a bug (since the docs do state it should support EUI-48/EUI-64, but there does not seem to be an official required representation). However, this would slightly change the behaviour of `ParseMAC` in that it would accept a format without separators where it previously would return an error. So I filed this proposal instead of a bug report.

I think that extending `ParseMAC` to allow for a format without separators (only for the shorter formats EUI-48 and EUI-64) would at least (1) match what's stated in the documentation and (2) resolve the need for custom implementation at least for a use case that is frequent enough for me personally to care about (but of course I have no idea how common this is in general).

This would then allow the following formats in addition to those already mentioned:
```
//      00005e005301
//      02005e1000000001
```
Repository: ant-design
Issue: TimePicker.RangePicker disabledTime "now" does not always contain the current time.
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-xggjxq?file=%2Findex.js%3A11%2C30)

### Steps to reproduce

- Let's assume the current time is 12:00

- Click on the input

- Click on the time. For example, 14

### What is expected?

- In the console, 12 will always be displayed.

- In the dropdown list, 12 will always be hidden.

### What is actually happening?

- In the browser console, 14 will be displayed first, and only then 12.

- The hidden hour will always be the selected hour (14), not the current one (12).



| Environment | Info |
| --- | --- |
| antd | 5.16.0 |
| React | 18.2.0 |
| System | MacOS 14.4.1  |
| Browser | Chrome 123 |

---
We are validating fields based on the current time, and this behavior disrupts its functioning.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Godot claims broken dependencies, files are still where they're supposed to be, can't fix them
Labels: bug,topic:editor,needs testing

### Tested versions

Reproducible in 4.2.stable

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - integrated AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 31.0.12029.10015) - AMD Athlon Silver 3050U with Radeon Graphics (2 Threads)

### Issue description

As a result of a Git desync, my Godot editor refuses to load the default scene, claiming broken dependencies. No files outside of the .godot folder are missing or changed, as that was the folder that got desynced, and clicking on "Fix Dependencies" shows every file in the correct location, with no option to apply the fixes. Deleting the .godot folder does not fix the issue.

### Steps to reproduce

These are the steps I followed that resulted in the desync
- Add /.godot to gitignore
- Delete .godot folder from repository and commit changes
- Pull repository on local device

### Minimal reproduction project (MRP)

Attached is a stripped down version of the project I was working on.
[MRP.zip](https://github.com/godotengine/godot/files/14875790/MRP.zip)
Repository: flutter
Issue: `flutter doctor` should warn if the Android (emulator) AVD version is "old"
Labels: platform-android,tool,P2,e: impeller,team-tool,triaged-tool

`flutter doctor` currently outputs (something) like this:

```sh
% flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.0, on macOS 14.4 23E214 darwin-arm64, locale
    en)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.87.2)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!
```

We'd like to add a _warning_ in the Android emulator (AVD) version is lower than an expected "newer" version.

We discovered this can be queried via:

```sh
% $ANDROID_HOME/emulator/emulator --version
33.1.17.0 (build_id 10594030)
```

Steps:

- [ ] Add a warning for the emulator version
- [ ] Work with the Impeller team to verify what that version should be

## Context

As we get closer to releasing Impeller on Android, we've discovered that Vulkan and Vulkan Validation Errors were not fully supported, and even worked with the Android team to get bug fixes to avoid emulator crashes.

Emulators are a primary way many developers work on their Flutter application, especially if they are developing for Android, so it will become surprising that (older) emulator binaries crash when we switch the default to `--enable-impeller`.

/cc @reidbaker @christopherfujino 

As I mentioned in the engine weekly, this up for grabs.
Repository: vscode
Issue: Option to disable cell collapsing region (on favor of group splitter focus)
Labels: feature-request,notebook

<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->

When you are working with a vertically split workspace the group splitter can be grabbed to modify the width of each editor group.

For jupyter editors the splitter becomes quite hard to grab as the cell border is also a clickable region.
I consider grabbing the group splitter quite more important and often used, so I think it should be given more room.

Note that you can already collapse cells by double clicking the grabbable region used for sorting/moving cells, so this feature is partially redundant:

![2024-04-04_(134227)_Code](https://github.com/microsoft/vscode-jupyter/assets/26868611/a970afdf-5730-4eb3-b723-e7944f8eca51)

Probably the best would be a new simple option to disable being able to collapse cells when clicking this region (so no padding or visual changes).
> Note that the border of the cell should also not be grabbable (could display focus state anyway), otherwise grabbing the cell would produce the same issue.

Regards!
Repository: go
Issue: go/parser: StructType.End() can underflow the File
Labels: NeedsInvestigation,gopls/parsing,Refactoring

A struct type with a missing close brace has an StructType.End pos of zero. That means the enclosing nodes such as ReturnStmt may also have a computed End that is zero, or perhaps slightly larger:

![Screenshot 2024-04-04 at 2 43 08 PM](https://github.com/golang/go/assets/5658175/84636a95-1527-4cfd-ab90-e03f1fb1b860)

I believe this is the root cause of at least some of the many gopls crashes recorded in https://github.com/golang/go/issues/64547.

Ultimately this is a problem of parser error recovery. We need to establish the invariants that:
- all tree nodes have valid Pos/End positions; and 
- all tree nodes have nested Pos/End subranges (with a possible exception for the func keyword in FuncDecl/FuncType).

See also:
- https://github.com/golang/go/issues/48300 ;-)
Repository: TypeScript
Issue: Import ellision emit bug: usage of imports only in keys of interfaces does not result in those imports being elided as type-only
Labels: Bug,Help Wanted

### 🔎 Search Terms

import ellision emit

### 🕗 Version & Regression Information

- This is the behavior in every version I tried - I saw it in typescript 4.9 and in the playground in typescript 5.4.3.

### ⏯ Playground Link

https://www.typescriptlang.org/play?importHelpers=true&target=99&module=2#code/JYWwDg9gTgLgBAbwEIEEBKBfOAzKERwDkARgIZSEDcAsAFCiSxwBUcpAzjhBDngYdm5U6dAKYAPRvGAA7GKKjZSAY1Fw03GAGUYpeYjpw4AbVRoAugC447GFFkBzGrSPHBEAHRkoVm3cfOGHRAA

### 💻 Code

```ts
import {BAR} from 'bar';
import * as foo from 'foo';

export interface RootState {
  [BAR]: string;
  [foo.bar]: string;
}
```


### 🙁 Actual behavior

When compiled to ESNext module:
```
import { BAR } from 'bar';
import * as foo from 'foo';
```

when compiled to AMD with importHelpers it's interesting that __importStar appears
```
define(["require", "exports", "tslib", "bar", "foo"], function (require, exports, tslib_1, bar_1, foo) {
    "use strict";
    Object.defineProperty(exports, "__esModule", { value: true });
    foo = tslib_1.__importStar(foo);
});
```

### 🙂 Expected behavior

output should be an entirely empty module, e.g. AMD should be
```
define(["require", "exports"], function (require, exports) {
    "use strict";
    Object.defineProperty(exports, "__esModule", { value: true });
});
```

ESNext should be
```
export {}
```

### Additional information about the issue

_No response_
Repository: deno
Issue: Consider asynchronously caching statically analyzable dynamic imports in the background for `deno run` instead of up front
Labels: perf,cli,suggestion

When doing `deno run` without `--check`, perhaps it should load statically analyzable dynamic imports in the background in order to start faster instead of doing that upfront. This adds a lot of complexity to deno_graph though. For `deno cache` the current behaviour should be maintained.

See https://github.com/denoland/deno/issues/23149#issuecomment-2035893106
Repository: PowerToys
Issue: [Power Toys- General]: The links present at the bottom of the page are not associated with its visible label.
Labels: Issue-Bug,Product-Settings,Status-In progress,Area-Accessibility,Needs-Triage,A11yE+D,A11ySev3,A11yWCAG

### Microsoft PowerToys version

v0.79.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

**Test environment:**
OS Build: Windows 11 Enterprise insider preview 23H2 (22631.3296)
Power toys version: v0.79.0
Screen reader: Narrator

**Repro Steps:**

1. Open the Power Toys app in the desktop.
2. Select the general option from left navigation pane.
3. Turn on narrator using Ctrl + Win +Enter.
4. Now navigate to the links present at the bottom of the page.
5. Observe the issue.

**User Experience:**
Users who depend on screen readers may encounter difficulties in understanding the purpose or destination of the links at the bottom of the page. Without proper association between the visible labels and the links, users may be unable to navigate to the desired content or perform specific actions effectively. 

**Note:**
This issue is repro at every pane for the links.


**Guideline reference:**
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships

**Attachments:**

https://github.com/microsoft/PowerToys/assets/117908911/de1b487b-9886-49c5-a2d7-3f8def3621cd




### ✔️ Expected Behavior

Links present at the bottom of the page should be associated with their visible labels using proper HTML markup, such as the <a> tag with an appropriate 'href' attribute. Screen readers should announce the visible labels when navigating through the links, providing users with accurate information about the destination or action associated with each link.

### ❌ Actual Behavior

Currently, links present at the bottom of the page are not associated with their visible labels. Screen readers may announce generic or misleading information when navigating through these links, as they are not properly linked to their visible labels. 

### Other Software

_No response_