fix: v0.3 smaller fixes

[QuantumExplorer]

Max Withdrawal should now work.
Changing alias name should now persist.
Updated to v0.3

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a new ProofLogScreen for visualizing proof logs.
  • Added a ToolsSubscreen chooser panel for easier navigation between tools.
  • Enhanced WithdrawalScreen with new status management for withdrawal processes.

• Improvements

  • Improved error handling and data retrieval in identity management.
  • Enhanced display logic for contested names and registration processes.
  • Updated UI components for better user experience and clarity.

• Refactor

  • Restructured module organization for identities and tools, improving code maintainability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces several changes across multiple files, primarily focusing on standardizing naming conventions for architecture identifiers in the release workflow, updating package dependencies, enhancing error handling, and adding new user interface components. Key modifications include renaming job matrix entries in the GitHub Actions workflow, updating the version and dependencies in Cargo.toml, and introducing new modules and methods for managing proof logs and withdrawal processes. The overall structure and logic of the application remain intact while improving functionality and user experience.

Changes

File Path	Change Summary
.github/workflows/release.yml	Updated job matrix configurations: renamed architecture identifiers from "amd64" to "x86_64" for Linux and macOS.
Cargo.toml	Updated package version from 0.2.0 to 0.3.0, changed dash-sdk dependency to a new commit, and added regex dependency version 1.11.
src/app.rs	Modified imports and initialization of screens: added ProofLogScreen, renamed WithdrawsStatusScreen to WithdrawsStatusesScreen, and updated RootScreenType.
src/backend_task/contested_names/query_dpns_contested_resources.rs	Restructured resource fetching logic to accommodate pagination and enhanced error handling for proof verification errors.
src/backend_task/mod.rs	Renamed module from withdrawals to withdrawal_statuses, updated imports accordingly.
src/database/contested_names.rs	Enhanced error handling in update_ending_time method to use match statement for querying existing ending time.
src/database/identities.rs	Improved error handling in set_alias method and modified get_local_qualified_identities to include alias in results.
src/database/initialization.rs	Updated database versioning logic, added migration handling, and renamed backup method.
src/database/mod.rs	Added new module proof_log.
src/database/proof_log.rs	Introduced methods for managing proof_log table: dropping, remaking, initializing, inserting, and retrieving proof log items.
src/database/settings.rs	Added method update_database_version to update the database_version field in settings.
src/model/mod.rs	Added new module declaration for proof_log_item.
src/model/proof_log_item.rs	Introduced RequestType enum and ProofLogItem struct for managing proof log details.
src/ui/components/left_panel.rs	Updated button linking from RootScreenType::RootScreenTransitionVisualizerScreen to RootScreenType::RootScreenToolsTransitionVisualizerScreen.
src/ui/components/mod.rs	Added new module declaration for tools_subscreen_chooser_panel.
src/ui/components/tools_subscreen_chooser_panel.rs	Introduced UI component for selecting tools subscreens with methods for displaying and managing user interactions.
src/ui/dpns_contested_names_screen.rs	Enhanced UI rendering logic for displaying contested names and improved voting process handling.
src/ui/identities/add_new_identity_screen/mod.rs	Removed KeyInfo struct, simplified dependencies, and updated logic for funding methods and identity registration.
src/ui/identities/identities_screen.rs	Updated import paths for AddKeyScreen and KeyInfoScreen, added new import for WithdrawalScreen, and enhanced error handling in show_alias.
src/ui/identities/keys/mod.rs	Added new modules: add_key_screen, key_info_screen, and keys_screen.
src/ui/identities/mod.rs	Added new modules: keys and withdraw_from_identity_screen.
src/ui/identities/register_dpns_name_screen.rs	Updated UI rendering logic and cost display for contested names.
src/ui/identities/withdraw_from_identity_screen.rs	Introduced WithdrawFromIdentityStatus enum for managing withdrawal state and enhanced methods for handling withdrawals.
src/ui/mod.rs	Restructured module imports and added new tool_screens module; updated RootScreenType and ScreenType enums to include new screen types.
src/ui/tool_screens/mod.rs	Added new modules: proof_log_screen and transition_visualizer_screen.
src/ui/tool_screens/proof_log_screen.rs	Introduced ProofLogScreen struct with methods for fetching and rendering proof log items.
src/ui/tool_screens/transition_visualizer_screen.rs	Updated ui method to include new subscreen chooser panel and modified RootScreenType reference.
src/ui/transfers/mod.rs	Updated import path for KeyInfoScreen to reflect new module organization.
src/ui/withdrawal_statuses_screen.rs	Updated import path for withdrawal_statuses module, reflecting the new module structure.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant Database
    participant UI

    User->>App: Initiate withdrawal
    App->>Database: Validate withdrawal details
    Database-->>App: Return validation result
    App->>UI: Update withdrawal status
    UI->>User: Display withdrawal status

Loading

Possibly related PRs

• release: provide zip for release #19: The changes in the .github/workflows/release.yml file involve updates to the job matrix configurations, specifically renaming architecture identifiers from "amd64" to "x86_64," which directly relates to the changes made in the main PR.
• refactor: renamed amd64 to x86_64 in release #61: Similar to the main PR, this PR also involves renaming architecture identifiers from "amd64" to "x86_64" in the release workflow, indicating a consistent approach to standardizing naming conventions across different platforms.
• feat: log proof log errors to db #64: This PR introduces functionality for logging proof log errors to a database, which is relevant to the overall context of managing application errors and logging, although it does not directly relate to the changes in the release workflow. However, it enhances the application's error handling capabilities, which may be indirectly connected to the overall improvements in the system's robustness.

Suggested reviewers

• ogabrielides

Poem

🐰 In the garden of code, we hop and play,
With screens and logs brightening the day.
From amd64 to x86_64 we cheer,
New tools and fixes, oh what a year!
With each little change, our project will grow,
A bunny's delight in the code we sow! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.