Find meaningful ways to contribute

This issue highlights dependencies in the Pulsar-Native repository that Renovatebot has identified as potentially abandoned due to a lack of recent updates. It provides a list of 19 such dependencies, along with links to their respective repositories and last updated dates, and suggests consulting Renovatebot's documentation for more information.

A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.

The Azure Monitor receiver is experiencing highly variable and undocumented delays in publishing storage capacity metrics (BlobCapacity/UsedCapacity). This delay can cause older data points to be rejected by backends like Grafana Mimir, which have limited out-of-order sample windows.

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

The `notifyUser` function in Socket.IO broadcasts notifications to all connected clients instead of targeting specific users. This is because sockets are not associated with authenticated users upon connection, leading to a potential data leak where one user might receive notifications intended for another. The fix involves associating sockets with user IDs and modifying the emission logic to target specific users.

This issue requests the creation of a tool, either a Claude Code skill or a bash script, to automatically generate a structured CHANGELOG.md file from git history. The tool should fetch commits since the last tag, categorize them into 'Added', 'Fixed', 'Changed', and 'Removed', and produce a well-formatted changelog. It needs to be tested on a real repository with sample output provided.

A bug exists where pasting a quiz join code with a trailing space causes the application to incorrectly report "Quiz not found". This is because the input field does not trim whitespace before processing the code. The issue also affects nickname input, allowing padded names to appear on the leaderboard. The proposed fix involves trimming input values on change or submit.

This issue proposes increasing the maximum number of allowed links in a vulnerability finding from 5 to 10. The current limit prevents users from submitting findings with more than 5 links, which can be problematic for legitimate, complex vulnerabilities. The change aims to accommodate a greater number of supporting links without compromising the system's integrity.

Users installing the .rpm package are experiencing rendering issues, including unusually large text spacing and missing numbers in the UI. The error output suggests a missing CSS file, indicating a potential packaging or theme configuration problem.

A user is experiencing an issue where their central control gets stuck on the logo screen after updating to a newer version (9/23) and attempting to install a specific component (M.I.B3.7.1). They are unable to access engineering mode and are seeking a solution to unblock their system.

This issue proposes adding a new setting to the application that allows users to toggle the visibility of campus life events on their calendar. This feature aims to provide users with more control over the events displayed, enabling them to customize their calendar view.

A bug has been reported where the 'Max Number of Events' input field in the Condenser settings allows users to enter negative values. This is incorrect behavior as the value should be at least 0. While the application prevents saving with a negative number, the error message is not clear.

The LLM configuration currently accepts invalid data like incorrect URLs or API keys, which are only detected when the LLM is actually used. This issue proposes adding validation to the configuration saving process to prevent users from saving invalid settings and encountering errors later.

This feature aims to reduce LLM call costs for memory consolidation by implementing a tiered approach. It proposes using a lightweight pre-judgment to skip unnecessary LLM calls, limiting the frequency of consolidation, and scheduling LLM-intensive tasks for off-peak hours. The goal is to decrease LLM usage and avoid peak demand periods.

This issue is a placeholder for daily automatically generated morning reports. It serves as a repository for this information, with the label 'good first issue' suggesting it's intended for new contributors.

This issue requires adding backend health monitoring and automatic restart functionality to the `DesktopBackendManager`. The goal is to detect backend crashes after initial startup and attempt to recover by restarting the process, notifying the user during the process, and handling persistent failures with an error dialog. This will prevent the desktop app from showing a blank screen when the backend becomes unresponsive.

A user is experiencing a TLS handshake failure when connecting an iOS Bedrock client (version 26.51) to a Bedrock Dedicated Server (version 1.26.51.1) running on an ARM64 host via Box64. The client reports an 'InitialConnection-13' error, and the issue persists even with a fresh server setup.

This feature request proposes adding the ability to log custom events and stages during MLflow runs, which would then be visualized as annotations on system metrics plots. This would help users better understand the timing of key pipeline steps relative to resource utilization for debugging and optimization.

This issue tracks the implementation status of various Spark SQL array and map functions, specifically focusing on achieving parity with existing functionalities. The checklist indicates which functions are already covered and which are still pending implementation.

In Firefox, using `mock.respond()` with a response body causes intercepted network requests to remain blocked indefinitely. This is because Firefox's WebDriver BiDi protocol only supports the `body` parameter for responses during the `beforeRequestSent` phase, not the `responseStarted` phase where WebdriverIO currently provides it. This leads to unhandled rejections or hanging requests.

This issue proposes refactoring test files to remove hardcoded YAML workflows stored as variables. The goal is to improve readability and developer experience by directly embedding or referencing YAML definitions instead of using intermediate variables, without altering the core functionality of Argo.

This feature request proposes adding `it.step` or `test.step` functionality to integrated tests, similar to Playwright. The goal is to improve test structure and reporting by breaking down complex tests into named steps, making it easier to identify failures and understand test execution flow, especially for React/Redux/Saga applications.

This issue proposes adding a `typecheck` script to the `pr-checks` script. Currently, type errors are not caught before merging to `main` because the `typecheck` script is not executed in the build gating process.