Find meaningful ways to contribute

This issue aims to enhance the observability of ingestion jobs by adding richer metadata to document status and Server-Sent Events (SSE) payloads. This includes timestamps, attempt counts, durations, and classified failure classes, which will be persisted in the database for cross-host debugging without requiring a dedicated operations dashboard.

This issue involves localizing the custom 404 error page. The goal is to move all hardcoded English strings from the `404.tsx` page into translation keys within the `common.json` files for all supported locales. This ensures that users see the 404 page in their preferred language and that the existing i18n test suite passes.

This issue proposes establishing clear guidelines for AI-assisted or AI-authored contributions to the repository. The core decision is whether to accept all AI contributions, only AI-assisted ones, or decline them entirely, with a recognition that allowing AI-generated code is likely irreversible and has legal implications.

The `get_stats` function in the contract currently returns aggregated total volume and fees across all tokens, which is misleading when multiple tokens are involved. This issue proposes adding a new function `get_token_stats` to retrieve per-token statistics and deprecating the mixed totals in the existing `Stats` struct.

This issue proposes adding validation for proposal parameters within the `propose()` function of the smart contract. Currently, invalid proposal parameters are only caught during the `execute()` phase, leading to wasted administrative effort. The goal is to refactor validation logic into helper functions that are called in both `propose()` and `execute()`, and to add tests to ensure invalid proposals are rejected early.

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.

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 proposes removing the obsolete `version` key from three `docker-compose.yml` files in the repository. This change is intended to eliminate a warning message that appears during Docker Compose invocations, improving developer and CI output. The task also includes verifying that the modified files still validate correctly.

The `/fund/direct` API endpoint is incorrectly throwing a generic 500 Internal Server Error instead of a 501 Not Implemented error. This is because the `submitDirectFunding` function always throws an error indicating it's not supported and requires a different flow. The fix involves returning a 501 status code with a helpful message or removing the endpoint entirely, along with adding a corresponding test.

Alerts with the label `team=blockchain` are not reaching their intended receiver (`slack-blockchain`) because higher-priority severity routes (`critical`, `warning`) are configured with `continue: false`. This stops the alert processing before it can reach the `team: blockchain` route. The fix involves reordering the Alertmanager routes to process the `team: blockchain` route before the severity routes.

This issue asks to investigate and remove an unused `vite.config.ts` file in a Next.js frontend project. The file might be a remnant of a past migration or intended for a tool like Storybook or Vitest, which needs to be confirmed. If it's truly unused, it should be deleted along with any redundant dependencies to improve project clarity.

The Alertmanager configuration file `alertmanager.yaml` uses environment variable placeholders like `${VAR}` which Alertmanager itself does not expand. This causes `amtool` to reject the file because the placeholders are treated as literal strings, leading to invalid configurations like an invalid URL for `slack_api_url`. The issue also notes that the `templates:` configuration points to non-existent files.

This issue requests the addition of unit tests for the skills API routes. The goal is to create a Jest test suite that mirrors the existing pattern in `ratings.test.js`, ensuring that the skills endpoints are properly tested for happy paths, validation failures, and authentication requirements. This will help prevent silent regressions that could impact job matching and assessment quality.

This issue requests the removal of a `.orig` file, which is a merge conflict artifact, from the repository. It also suggests adding `*.orig` and `*.rej` to `.gitignore` to prevent future occurrences of such files. The goal is to clean up the repository and improve developer experience by avoiding confusion and unnecessary clutter.

The `test_full_scenario` in the contract tests is currently ignored because it attempts to execute a proposal before the minimum governance delay has passed, causing a panic. The fix involves advancing the ledger's sequence number before each `execute` call to satisfy the timelock guard and then removing the ignore attribute.

This issue is a beginner-friendly task for Hacktoberfest, asking contributors to add a new anime quote to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute.

The health check for Redis is inefficient, creating a new connection for each check instead of using the existing one. Additionally, the Soroban RPC health check incorrectly treats certain client errors (4xx) as healthy and doesn't leverage the RpcPool's health status.

This issue proposes adding support for several IVI (In-Vehicle Infotainment) configuration options, including automatic lights, parking sensor menus, RPM widgets, and TPMS initialization. It also seeks solutions for known bugs such as missing turn signal sounds, language synchronization issues between IVI and the cluster, and incorrect trip distance readings on 2024 cockpits.

This issue identifies a bug in `backend/src/server.js` where the `/api/contributors` route is mounted twice. This duplication leads to inefficient processing and potential confusion. The fix involves removing one of the duplicate mount points to ensure the route is registered only once.

This issue requires implementing a cross-check mechanism to ensure the backend's PostgreSQL escrow state accurately reflects the on-chain Soroban escrow contract. This involves verifying the contract's state during sensitive escrow transitions (release, refund, dispute) to prevent data desynchronization. Any detected mismatches should be logged, recorded in metrics, and made alertable.

This issue requests the addition of unit tests for the `proposalTemplateService.js` file, which handles freelancer proposal templates. The goal is to ensure the service and its associated routes are thoroughly tested, covering CRUD operations, ownership enforcement, and potentially placeholder substitution. The tests should pass under the `npm run test:unit` command.

The docker-compose healthcheck for the backend is configured to use the incorrect URL '/api/health'. This needs to be updated to '/health' to match the actual route defined in the backend server, which is currently causing containers to be reported as unhealthy and breaking service dependency chains.

Users on Windows with the official ROCm profile for PyTorch and Torchaudio are encountering errors when synthesizing audio. This is due to a missing `TorchCodec` dependency, which leads to a false 'empty_candidate' diagnosis and failure in generating the first sentence. The issue appears to stem from upstream code that doesn't install `torchcodec` and incorrectly handles token counts.

This issue requests the migration of acceptance tests for the lesson-creator feature from Puppeteer to Playwright. The goal is to fully retire Puppeteer from the acceptance test suite and ensure these specific tests are rewritten and configured to use Playwright, following established conventions and verifying their functionality across desktop and mobile environments.

This issue highlights a lack of documentation for the ELK logging profile within the project's docker-compose setup. The existing configuration for Elasticsearch, Kibana, and Filebeat is not explained in the README or other documentation, making it difficult for users to discover and utilize this feature. The goal is to add documentation explaining how to enable the profile, its resource requirements, and how to access logs through Kibana.

This issue addresses a duplication in the backend API where the `aiScorerRoutes` are mounted under both `/api/ai-scorer` and `/api/ai`. The goal is to consolidate these to a single canonical path, either by removing the alias and implementing a redirect or by removing the alias entirely with a deprecation notice. This will simplify documentation, analytics, and prevent future inconsistencies.

The `getNegatedExpression` function in LLVM's SelectionDAG needs to be updated to correctly handle `FP16_TO_FP` and `FP_TO_FP16` opcodes. This change is expected to improve the utilization of source modifiers on AMDGPU for situations involving illegal f16 operations.

This issue proposes refactoring a large `server.js` file into smaller, more manageable modules for Express app creation, WebSocket handling, and overall application bootstrapping. The goal is to improve testability, maintainability, and prevent regressions by separating concerns and making the Express app factory importable without needing to bind a port.

This issue addresses 39 findings reported by golangci-lint, specifically focusing on missing or improperly formatted doc comments for exported APIs within the `pkg/golang` directory. The findings are grouped for independent resolution, encouraging small, manageable pull requests.