Rust good first issues

The payment details page currently displays the creation time in UTC without a timezone, while the recent activity tooltip shows the local time. This issue aims to align the payment details display with the recent activity by showing the creation time in the user's local timezone.

This bug occurs because the automatically generated temporary directory path for agent runs is too long for Unix sockets on Linux, exceeding the 108-byte limit for `sun_path`. This causes socket-based tests to fail. The expected behavior is a shorter per-run TMPDIR or a documented way to override it.

The `/api/v1/zip321/parse` endpoint incorrectly accepts URIs with `amount=0`, which then causes issues with sending and requesting Zcash transactions. The expected behavior is for the parse endpoint to reject such URIs with a 400 error, similar to how the request endpoint handles zero amounts.

The dashboard's account balances are not updating correctly after a Server-Sent Events (SSE) connection is re-established. This means that any balance changes made while the connection was down are not reflected on the dashboard until a manual refresh. The expected behavior is for balances to automatically update upon reconnection.

The `send_quote` API endpoint returns a 500 Internal Server Error when the wallet has not yet scanned blocks, causing the Send dialog's fee quote to fail during startup. This is inconsistent with other endpoints like `send` and `faucet`, which correctly return a 503 Service Unavailable error in this scenario. The fix involves adding a startup check to `send_quote` to map the unscanned wallet error appropriately.

The server's log output is incorrectly including ANSI color codes when running in a containerized environment. This results in unreadable log messages instead of plain text. The issue requires removing these color codes from the server's logging mechanism.

The `ths --json update` command fails to print a JSON report when it actually performs an installation. Instead, it only outputs the installer's text to stdout. The expected behavior is to always output a JSON report, consistent with when the tool is already up-to-date.

This issue describes a bug where theme changes made in one browser tab are not reflected in another tab until a reload. The `useTheme` hook correctly listens for storage events, but the `applyTheme` function, responsible for visually updating the theme, only triggers when the current tab itself selects a theme, leading to a desynchronized theme experience across tabs.

The 'Mine' dialog in the web application incorrectly accepts block counts in exponent, hexadecimal, and binary formats. The `mineSchema` function uses `Number(value)` which allows these non-decimal inputs. The expected behavior is to only accept decimal whole numbers.

The web application's amount field for ZEC transactions lacks an upper bound, allowing users to submit amounts exceeding the maximum supply. This leads to server-side rejections, which are then displayed as generic errors to the user. The fix involves implementing a validation to prevent amounts above 21,000,000 ZEC from being submitted.

This issue describes a bug where clicking the "View transaction" link within the Payments dialog on the web application does not close the dialog. Instead, it navigates the user to the transaction explorer page while the Payments dialog remains open, obscuring the content. The expected behavior is for the dialog to close upon clicking the link.

This issue describes a bug where the block list footer in the web interface incorrectly labels the "Older blocks" link. The server's `before` parameter is inclusive, meaning it includes the specified block, but the web UI displays it as exclusive, causing the label to be one block off from the first block shown on the page.

This issue proposes adding a new command-line flag, `--env`, to the `ths endpoints` command. This flag will output environment variables in an `export` format, allowing users to easily set them for separately started environments, mirroring the variables used by `ths run`. The goal is to provide a way to access these environment variables for standalone environments.

This issue proposes adding shell completion generation for bash, zsh, and fish to the `ths` CLI tool. The goal is to mirror the functionality already present in `anvil` and `forge` CLIs, making the `ths` tool more user-friendly by providing command-line auto-completion. The acceptance criteria include ensuring comprehensive completion scripts and updating the README with installation instructions.

The dashboard's "Mine" functionality is inaccessible on mobile viewports (below 640px) when there are no active or failed mining jobs. This is because the primary entry point is hidden on smaller screens, and there's no alternative mobile navigation option. The fix involves ensuring a way to initiate manual mining remains available on narrow viewports.

This feature proposal aims to add a new command-line interface (CLI) option to inspect wallet fees and maximum spend quotes without initiating a transaction. The goal is to provide users and scripts with information about available funds and route-dependent fees before committing to a transfer, leveraging an existing API endpoint.

The `demo_multiple_consumers_rebalance` test in the Kafka demo infrastructure is experiencing flaky failures, with consumers not receiving expected partition assignments during rebalancing. This is likely due to sequential waiting for consumer assignments, which may create coordination gaps and prevent both consumers from processing group membership events concurrently.

This issue addresses a flaky test in the broadcast consensus concurrency test that fails due to unserviced subscribers. The problem arises when new subscribers join and stop receiving messages while still being considered eligible for subsequent publishes, leading to a timeout in tracking publish receipts. The likely root cause is a race condition where a joining subscriber is retained before it has fully processed all messages, and subsequent messages are sent without a mechanism to re-poll that subscriber.

This issue requests the addition of tests for the `http-tracker-core` package within the bittorrent-http-tracker project. The provided code coverage report highlights areas with lower test coverage, particularly in `announce.rs` and `scrape.rs`, indicating specific modules that need attention. The goal is to improve the overall test suite for this core component.

This feature request proposes allowing `simdnoise` to write generated noise directly into user-provided memory buffers. This would enable more efficient parallel noise generation by avoiding intermediate allocations and copies, especially for large datasets.

The user is asking if it's possible to implement voice input for prompting. This would allow users to speak their prompts instead of typing them.

External links clicked within the Escouade application's chat interface are currently opening inside the application's main window instead of the system browser. This behavior traps the user on the loaded page, as there's no navigation or back functionality, requiring the app to be closed and reopened. The issue is identified as a common Tauri problem related to unintercepted anchor clicks.

This issue proposes refactoring the `SqlToRel::sql_statement_to_plan_with_context_impl` function in DataFusion to improve its readability and maintainability. The large `match` statement will be broken down into smaller, dedicated functions for each statement type, reducing complexity and making it easier to handle future `sqlparser` upgrades.

This issue proposes to replace unchecked `HashMap::get` unwraps in the `detect_potential_deadlocks` function with safer alternatives. The current implementation relies on the assumption that all node names exist in the `node_map`, but a refactor could break this, leading to panics. The suggested fixes include using `expect` for clearer error messages, skipping missing nodes, or returning a `Result`.

The `register_tool` function in `swarms-rs` currently accepts tool names that are invalid according to OpenAI and Anthropic's requirements, leading to errors later in the process. The proposed solution is to add validation for tool names during registration, ensuring they adhere to the specified character set and length constraints, and to return a `Result` for clearer error handling.

This issue is a chore to remove a commented-out `load_from_json` function from the `conversation.rs` file. The function is no longer needed as its functionality is already covered by `import_from_file`. The proposed fix is to simply delete the commented-out code block.

This issue proposes refactoring three similar panel printing functions in `swarms-rs/src/agent/swarms_agent.rs` into a single helper function. This will reduce code duplication by consolidating the table-building logic, making future style changes more manageable and the codebase cleaner.