fix: xtoken.json

[tuxcanfly]

Overview

User reported facing this issue, upon investigation I found that the correct path is xtoken.json:

Error: could not build arguments for function "github.com/celestiaorg/celestia-node/nodebuilder/gateway".Handler (/src/nodebuilder/gateway/constructors.go:12): failed to build state.Module: could not build arguments for function "reflect".makeFuncStub (/usr/local/go/src/reflect/asm_amd64.s:28): failed to build *grpc.ClientConn: received non-nil error from function "github.com/celestiaorg/celestia-node/nodebuilder/core".grpcClient (/src/nodebuilder/core/constructors.go:24): file does not exist

Summary by CodeRabbit

• Documentation
  • Updated the filename reference in the guide to ensure users reference the correct token file for proper permissions.

[coderabbitai]

Walkthrough

The pull request updates the documentation in the light node guide. The file now references the filename as xtoken.json instead of the previous x-token.json. This change ensures that users refer to the correct file name when following the documentation. No modifications were made to any exported or public entities.

Changes

File(s)	Change Summary
how-to-guides/light-node.md	Updated documentation to change the file reference from x-token.json to xtoken.json.

Suggested Reviewers

• jcstein

Poem

I'm a rabbit with a hop so spry,
Updating docs as time goes by.
I switched the name with a joyful spin,
From "x-token" to "xtoken"—let's begin!
With carrot dreams in lines so neat,
I celebrate this change with a happy beat.
🐰💻

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc90f2e and 0237a1d.

📒 Files selected for processing (1)

• how-to-guides/light-node.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• how-to-guides/light-node.md

---

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 generate docstrings to generate docstrings for this 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.

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://celestiaorg.github.io/docs-preview/pr-1914/
Built to branch main at 2025-03-03 16:07 UTC. Preview will be ready when the GitHub Pages deployment is complete.