Skip to content
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

docs: Update reference of Approximation #22550

Merged
merged 2 commits into from
Nov 19, 2024
Merged

Conversation

NAIHANU
Copy link
Contributor

@NAIHANU NAIHANU commented Nov 19, 2024

it looks like the original link is deleted by the author, use wiki for updating.

Summary by CodeRabbit

  • Documentation
    • Enhanced clarity and comprehensiveness of security guidelines for developers using the Cosmos stack.
    • Expanded sections on "Non-Determinism," "In-Protocol Panics," "Unmetered Computation," and "Fee Market and Gas Issues" to provide detailed explanations and recommendations.
    • Added acknowledgments and references to external resources for better context and support.
    • Improved language for better readability and instructional quality.

@NAIHANU NAIHANU requested a review from a team as a code owner November 19, 2024 00:23
Copy link
Contributor

coderabbitai bot commented Nov 19, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request involves significant modifications to the security guidelines document for developers using the Cosmos stack. Enhancements include clearer language, expanded sections on non-determinism, in-protocol panics, unmetered computation, and fee market issues. The document now features acknowledgments and external references for better context. Specific risks and recommendations are outlined to improve understanding and handling of security considerations, ensuring developers are well-informed about potential vulnerabilities.

Changes

File Path Change Summary
docs/build/building-apps/04-security-part-1.md Enhanced clarity and comprehensiveness of security guidelines; expanded sections on non-determinism, in-protocol panics, unmetered computation, and fee market issues; added acknowledgments and external references; refined language for readability.

Possibly related PRs

  • docs: Update More Info link of SECURITY.md #22042: The updates to the SECURITY.md document enhance clarity on security guidelines, which aligns with the main PR's focus on improving security documentation for developers.
  • docs: Update nft docs #22060: The updates to the NFT documentation include clarifications that may relate to security practices in handling NFTs, relevant to the main PR's emphasis on security guidelines.
  • docs(x/consensus): fixes #22114: The fixes in the x/consensus documentation improve clarity, which is relevant to the main PR's goal of enhancing security documentation.
  • docs: pre,begin,end block #22127: The updates to the module management documentation include lifecycle methods that could relate to security practices, connecting to the main PR's focus on security guidelines.
  • docs: update learn/beginner docs #22191: The updates to beginner documentation enhance clarity on transaction lifecycle and security considerations, which aligns with the main PR's focus on security guidelines.

Suggested reviewers

  • sontrinh16
  • tac0turtle

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4bb2352 and 9ab68d3.

📒 Files selected for processing (1)
  • docs/build/building-apps/04-security-part-1.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/build/building-apps/04-security-part-1.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
🪧 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.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
docs/build/building-apps/04-security-part-1.md (2)

118-118: Consider using a more authoritative reference for approximation methods.

While Wikipedia provides a good overview, for security-critical documentation, consider citing academic papers, technical specifications, or established mathematical libraries that implement these approximation methods.


Line range hint 1-400: Consider enhancing visibility of critical security warnings.

While the documentation is comprehensive, consider adding prominent warning callouts (e.g., using blockquotes or bold text) for the most critical security considerations in each section. This would help developers quickly identify crucial security requirements.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9e36674 and 4bb2352.

📒 Files selected for processing (1)
  • docs/build/building-apps/04-security-part-1.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/build/building-apps/04-security-part-1.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🔇 Additional comments (2)
docs/build/building-apps/04-security-part-1.md (2)

Line range hint 1-24: Well-structured and comprehensive security documentation!

The document effectively presents security guidelines with a clear progression from fundamental concepts to advanced topics. The inclusion of acknowledgments and external references enhances credibility and provides additional resources for developers.


Line range hint 25-117: Technically accurate with practical code examples!

The documentation provides precise technical details with relevant code examples that effectively demonstrate security concepts. The examples are particularly valuable as they showcase real-world scenarios and common pitfalls.

Also applies to: 119-400

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Nov 19, 2024
@julienrbrt julienrbrt enabled auto-merge November 19, 2024 15:31
@julienrbrt julienrbrt added this pull request to the merge queue Nov 19, 2024
Merged via the queue into cosmos:main with commit bf6d6f3 Nov 19, 2024
71 of 73 checks passed
mergify bot pushed a commit that referenced this pull request Nov 19, 2024
Co-authored-by: Julien Robert <[email protected]>
(cherry picked from commit bf6d6f3)
julienrbrt pushed a commit that referenced this pull request Nov 19, 2024
alpe added a commit that referenced this pull request Nov 21, 2024
* main:
  build(deps): Bump cosmossdk.io/math from 1.3.0 to 1.4.0 (#22580)
  fix(server/v2/api/telemetry): enable global metrics  (#22571)
  refactor(server/v2/cometbft): add `codec.Codec` and clean-up APIs (#22566)
  feat(core/coretesting): make memDB satisfy db.Db interface (#22570)
  Merge commit from fork
  fix(server(/v2)): fix fallback genesis path (#22564)
  fix: only overwrite context chainID when necessary (#22568)
  docs(client): Update setFeeGranter and setFeePayer comments (#22526)
  fix(baseapp): populate header info in `NewUncachedContext` (#22557)
  build(deps): Bump buf.build/gen/go/cometbft/cometbft/protocolbuffers/go from 1.35.1-20240701160653-fedbb9acfd2f.1 to 1.35.2-20240701160653-fedbb9acfd2f.1 in /api (#22551)
  build(deps): Bump github.com/creachadair/atomicfile from 0.3.5 to 0.3.6 in /tools/confix (#22552)
  docs: Update reference of Approximation (#22550)
  fix(server/v2/comebft): wire missing services + fix simulation (#21964)
  ci: fix permissions for GITHUB_TOKEN on dependabot workflows (#22547)
  ci: fix permissions for GITHUB_TOKEN in spell check workflow (#22545)
  build(deps): Bump google.golang.org/protobuf from 1.35.1 to 1.35.2 (#22537)
  fix(cosmovisor): premature upgrade on restart (#22528)
  fix(store/v2/pebble): handle version 0 in keys (#22524)
  refactor(server/v2/telemetry): swap redirects (#22520)
  docs: Update content in  CODE_OF_CONDUCT.md (#22518)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants