Java good first issues

This issue proposes improving automated emails sent to mentors and mentees by clearly indicating that the sender address is a no-reply and providing the correct contact email for the mentorship team. The goal is to reduce confusion and ensure users know where to direct their inquiries.

This issue outlines the comprehensive checklist for the HugeGraph 1.8.0 release, focusing on functionality, compatibility, documentation, and cross-repository integration. It details specific tasks for HugeGraph Server, Toolchain, AI, website, and documentation, including Kubernetes/Helm support, various deployment configurations, and authentication mechanisms.

A user has successfully adapted a Metal implementation for Minecraft 26.3, building upon the Voxy M-Series Metal project. They are seeking permission to share their experimental build or contribute their changes back to the original repository, while also acknowledging the use of AI for development.

When configuring identity provider mappers, a misconfiguration can lead to users being created with a null username. These users are unmanageable through the GUI or API, requiring direct database intervention for cleanup. The expected behavior is for an error to be thrown during user creation if the username would be null, and for a database NOT NULL constraint to prevent this.

The current IVP (Installation Verification Procedure) is too strict regarding version number formats, requiring exactly seven characters and a specific file structure. The issue proposes a more flexible approach to version handling and component detection, suggesting the need for defined requirements and potentially allowing suffixes for intermediate releases.

This issue requests the creation of a demonstration for a Java 12 feature (JEP 346) that allows the G1 garbage collector to promptly return unused committed memory. The goal is to showcase how this feature improves memory management by releasing memory back to the operating system more efficiently.

This issue requests the creation of a demonstration for the Java 12 feature JEP 344, which introduces abortable mixed collections for the G1 garbage collector. The goal is to showcase how this feature works and its potential benefits.

This issue requests the creation of a demonstration for the Java 12 feature JEP 341, which introduces default Class Data Sharing (CDS) archives. The goal is to showcase how this feature works and its benefits.

This issue requests the creation of a demo for Java 12's JEP 340, which consolidates the AArch64 ports. The goal is to showcase this feature through a practical example, following the project's contribution guidelines.

This issue requests the creation of a demo project to showcase the Java 12 Microbenchmark Suite feature (JEP 230). The goal is to provide a practical example of how to use this new feature for performance testing within Java.

This issue is a tracker for implementing demonstration code for all new features introduced in Java 12, as defined by their respective Java Enhancement Proposals (JEPs). It's a broad task requiring individual implementation for each JEP.

This issue is a tracker for implementing demonstration code for all new features introduced in JDK 27, as outlined by relevant JEPs. It's an enhancement request labeled as 'help wanted', indicating community contribution is encouraged.

This issue requests the creation of a demonstration for Java 13's JEP 353, which reimplements the legacy socket API. The goal is to showcase this new feature through a practical example, following the project's contribution guidelines.

The issue proposes moving a validation check from `IndexValidator` to `MetaDataValidator`. This check ensures that the `addedVersion` of an index is less than or equal to its `lastModifiedVersion`, which is a logical place for metadata-level validations.

The Kestra flow code editor fails to highlight duplicate task IDs when they are nested within conditional blocks like 'If', 'Switch', 'Dag', or 'afterExecution'. While the backend correctly identifies these duplicates upon saving, the frontend lacks the visual indication, making it difficult for users to pinpoint the source of the error.

This issue requires replacing Bootstrap utility classes within the `Gantt.vue` component with custom CSS using design system tokens. The goal is to remove all Bootstrap dependencies from the component, ensuring visual consistency across light and dark modes and passing all relevant UI checks.

A visual bug exists in the breadcrumb navigation where a space is missing between the word 'Deleted' and the flow name when navigating back to a deleted flow from the execution page. This issue is reproducible by creating, executing, and then deleting a flow in a separate tab.

This issue involves removing a dead Bootstrap class, `img-fluid`, from the `NoExecutions.vue` component. The class is no longer used by Kestra's CSS, so its removal will not affect the component's appearance. The task requires verifying the removal and ensuring the component's visual consistency through screenshots.

This issue requests the removal of a dead Bootstrap class (`text-truncate`) from the `Header.vue` component. The class is no longer supported by Kestra's CSS and should be replaced with the `<KsText truncated>` component. The fix involves updating the template and ensuring all checks pass.

This issue requires replacing 19 Bootstrap utility classes within the `KeyShortcuts.vue` component with custom CSS using `--ks-*` design tokens. The goal is to remove Bootstrap entirely from the project, ensuring the component's appearance remains identical in both light and dark modes after the changes. The task involves mapping Bootstrap's spacing utilities to the correct design token values.

This issue proposes integrating SpotBugs and FindSecBugs static analysis security testing (SAST) scanners into the VulnerableApp benchmark. The goal is to analyze the Java code, collect findings, and convert them into the benchmark's existing JSON format, ensuring compatibility with the current comparator and documentation.

This issue requires replacing 14 Bootstrap utility classes within the `ValidationError.vue` component with custom CSS using design system tokens. The goal is to remove all Bootstrap dependencies from this specific component, ensuring visual consistency across light and dark modes and passing all relevant checks.

This issue requires replacing ten Bootstrap utility classes within the `KsTopNavBar.vue` component with custom CSS using `--ks-*` design tokens. The goal is to remove Bootstrap dependency and ensure visual consistency across light and dark modes, verified by screenshots and passing automated checks.

This issue requires replacing seven Bootstrap utility classes within the `Toc.vue` component with custom CSS using the `--ks-*` design tokens. The goal is to remove Bootstrap from the project's design system and ensure the component's styling remains consistent, particularly with spacing and color, across light and dark modes. The replacement should be done within the component's existing scoped SCSS block.

This issue requires replacing four Bootstrap utility classes within the `InputText.vue` component with custom CSS using design system tokens. The goal is to remove all Bootstrap dependencies from the component and ensure the styling remains consistent across light and dark modes. The task involves modifying the component's template and scoped styles, followed by verification through screenshots and automated checks.

This issue requires replacing four Bootstrap utility classes within the `ContextDocsMenu.vue` component with custom CSS using Kestra's design system tokens. The goal is to eliminate Bootstrap dependencies and ensure the component's styling is maintained across light and dark modes. The task includes removing unused Bootstrap classes and verifying the changes with screenshots and automated checks.

This issue requires replacing six Bootstrap utility classes within the `KsEditor.vue` component with custom CSS using design system tokens. The goal is to eliminate Bootstrap dependency and ensure visual consistency across light and dark modes, verified by screenshots and passing automated checks.

This issue requires replacing three Bootstrap utility classes in the `FlowRootTopBar.vue` component with custom CSS using design system tokens. The goal is to remove Bootstrap dependencies and ensure the styling is consistent with the new design system. The task involves adding a scoped SCSS style block and verifying the changes with screenshots and automated checks.

This issue proposes a feature to reduce the speed of asteroids in the 'Easy' game mode. The goal is to balance the game by making asteroids less challenging compared to other enemies, with a hint to modify the `GameMode` file to introduce a new field for asteroid speed.