Skip to content

Enhance Troubleshooting & FAQ sections #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MAYANK-MAHAUR
Copy link
Contributor


title: "Added 'WASI-NN Backend Error' troubleshooting; update FAQs"
labels: documentation

Type of Change

  • New documentation page
  • Update to existing page
  • Fix (typo, broken link, etc.) - [ ] Content restructuring/organization
  • Other (please describe):

This Pull Request introduces a new troubleshooting entry to address the common "Backend Error: WASI-NN Backend Error: Caller module passed an invalid argument / 'store_force: command not found'" error encountered by users, especially when the AI model snapshot is corrupted during download.

The new section provides:

  • The exact error message snippet for easy identification.
  • A clear explanation of the cause (corrupted model download, improper shutdown).
  • A step-by-step solution involving stopping the node, removing the corrupted installation, and a clean re-installation to ensure a fresh model download.

Additionally, this PR includes minor updates and clarifications within the existing Troubleshooting and FAQ sections as part of improving overall documentation clarity.

Screenshots (if applicable)

image

Screenshot of the error being addressed:

image
haha.mp4

Checklist

  • I have reviewed the Contributing Guidelines (if available).
  • My changes are focused on a single documentation topic.
  • I have checked for spelling and grammar errors.
  • I have previewed the changes locally to ensure they render correctly.
  • I have included any necessary updates to the sidebar or navigation. - [X] I have also read the Code Of Conduct

Additional Notes

This new troubleshooting entry directly addresses a common frustration point for users experiencing issues with model initialization due to incomplete downloads. It provides a clear, actionable solution to get their GaiaNet node operational.

Copy link
Contributor

juntao commented Jul 26, 2025

Hello, I am a PR summary agent on flows.network. Here are my reviews of code commits in this PR.


Commit 6f56c42d59265172f90ca72832fc3e5ff27d61de

Summary of Key Changes:

  1. FAQ Section Enhancement:

    • Added a new :::tip[Why Gaianet?] section to emphasize key differentiators and benefits.
    • Explained unique features like decentralized ownership, domain-specific AI, monetization options, and the open ecosystem.
  2. Troubleshooting Section:

    • Introduced an image (image.png) for visual aids in troubleshooting.
    • Expanded troubleshooting.md with detailed information to assist users effectively.
  3. Dependencies & Versioning:

    • Updated package-lock.json to ensure dependencies and package versions are correctly recorded for reproducibility.

These changes aim to enhance the documentation's usability, making it easier for users to find troubleshooting solutions and understand Gaianet’s unique selling points.

@MAYANK-MAHAUR
Copy link
Contributor Author

i've thoroughly researched on this error and found a solution :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants