Skip to content

cmd progress for git solution download#4051

Merged
Maheshkale447 merged 2 commits into
masterfrom
Feature/CLIProgressBar
Jan 10, 2025
Merged

cmd progress for git solution download#4051
Maheshkale447 merged 2 commits into
masterfrom
Feature/CLIProgressBar

Conversation

@GokulBothe99

@GokulBothe99 GokulBothe99 commented Jan 10, 2025

Copy link
Copy Markdown
Contributor

Thank you for your contribution.
Before submitting this PR, please make sure:

  • PR description and commit message should describe the changes done in this PR
  • Verify the PR is pointing to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
  • Latest Code from master or specific release branch is merged to your branch
  • No unwanted\commented\junk code is included
  • No new warning upon build solution
  • Code Summary\Comments are added to my code which explains what my code is doing
  • Existing unit test cases are passed
  • New Unit tests are added for your development
  • Sanity Tests are successfully executed for New and Existing Functionality
  • Verify that changes are compatible with all relevant browsers and platforms.
  • After creating pull request there should not be any conflicts
  • Resolve all Codacy comments
  • Builds and checks are passed before PR is sent for review
  • Resolve code review comments
  • Update the Help Library document to match any feature changes

Summary by CodeRabbit

  • New Features

    • Enhanced logging functionality with an option to overwrite console lines.
    • Improved progress reporting during solution download with detailed percentage tracking.
  • Bug Fixes

    • Updated progress notification mechanism to provide more granular download progress information.
  • Refactor

    • Modernized event handling for progress updates.
    • Simplified console logging methods with additional control parameters.

@coderabbitai

coderabbitai Bot commented Jan 10, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The pull request introduces enhancements to logging and progress reporting across multiple files in the Ginger project. In the Reporter and WorkSpaceReporterBase classes, a new overwriteCurrentLine parameter is added to logging methods, providing more control over console output. In the CLIHelper class, the progress reporting mechanism is updated to use a more detailed tuple-based approach for tracking download progress, replacing the previous string-based event with a more granular progress tracking method.

Changes

File Change Summary
Ginger/GingerCoreCommon/ReporterLib/Reporter.cs Added overwriteCurrentLine parameter to ToLog and ToConsole methods, enabling conditional line overwriting in console logging.
Ginger/GingerCoreCommon/ReporterLib/WorkSpaceReporterBase.cs Updated ToConsole method to support line overwriting with new overwriteCurrentLine parameter.
Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs Replaced ProgressText event with ProgressUpdated event using a tuple for more detailed progress tracking.

Possibly related PRs

  • BugFix - Telemetry Bug Fixes #3931: The changes in the UploadItemToRepository method involve the use of TelemetryMetadata, which is also referenced in the main PR's modifications to the ToLog and ToConsole methods, indicating a connection in how telemetry data is handled across different logging functionalities.

Suggested reviewers

  • Maheshkale447

Poem

🐰 A Rabbit's Logging Tale 🖨️
With lines that dance and messages bright,
Our console now dances with newfound might,
Overwriting text with magical grace,
Progress tracked in a percentage's embrace,
Logging evolved, a programmer's delight!


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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 or @coderabbitai title 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (2)
Ginger/GingerCoreCommon/ReporterLib/Reporter.cs (1)

40-40: Add XML documentation for the new parameter.

The method signature has been updated, but the XML documentation should be updated to describe the new overwriteCurrentLine parameter.

Add the following XML documentation:

+/// <param name="overwriteCurrentLine">When true, overwrites the current console line instead of appending a new line.</param>
 public static void ToLog(eLogLevel logLevel, string messageToLog, Exception exceptionToLog = null, TelemetryMetadata metadata = null, Boolean overwriteCurrentLine = false)

Also applies to: 54-54, 56-59

Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs (1)

573-573: Remove commented code.

The commented line //Console.WriteLine(); should be removed as it serves no purpose.

🧰 Tools
🪛 GitHub Check: Codacy Static Code Analysis

[warning] 573-573: Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs#L573
Remove this commented out code.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5af8791 and daf2ee6.

📒 Files selected for processing (3)
  • Ginger/GingerCoreCommon/ReporterLib/Reporter.cs (4 hunks)
  • Ginger/GingerCoreCommon/ReporterLib/WorkSpaceReporterBase.cs (3 hunks)
  • Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs (3 hunks)
🧰 Additional context used
🪛 GitHub Check: Codacy Static Code Analysis
Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs

[warning] 573-573: Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs#L573
Remove this commented out code.

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (4)
Ginger/GingerCoreCommon/ReporterLib/WorkSpaceReporterBase.cs (2)

35-35: LGTM!

The field declaration follows naming conventions and has appropriate access level.


37-37: LGTM!

The method signature change is backward compatible and the parameter name is descriptive.

Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs (2)

569-569: LGTM!

The event handler is properly subscribed and unsubscribed, following best practices.

Also applies to: 579-579


591-594: LGTM!

The XML documentation is well-written and follows documentation standards.

Comment thread Ginger/GingerCoreCommon/ReporterLib/WorkSpaceReporterBase.cs
Comment thread Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs (1)

568-568: Move success message inside try block.

The success message is logged after unsubscribing from the event, but it's outside the try block. This means it will be logged even if an exception occurs during the download process.

Apply this diff to fix the issue:

                progressNotifier.ProgressUpdated -= ProgressNotifier_ProgressUpdated;
-                Reporter.ToLog(eLogLevel.INFO, "Solution downloaded/updated successfully");
+                if (solutionDownloadedSuccessfully)
+                {
+                    Reporter.ToLog(eLogLevel.INFO, "Solution downloaded/updated successfully");
+                }

Also applies to: 578-579

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between daf2ee6 and 62b11f8.

📒 Files selected for processing (1)
  • Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Build Stage / build
🔇 Additional comments (1)
Ginger/GingerCoreNET/RunLib/CLILib/CLIHelper.cs (1)

589-602: Fix integer division and add null check.

The progress calculation has potential issues with integer division truncation and division by zero.

This issue was previously identified. Please refer to the existing comment for the recommended fix.

@Maheshkale447
Maheshkale447 merged commit 985f922 into master Jan 10, 2025
@Maheshkale447
Maheshkale447 deleted the Feature/CLIProgressBar branch January 10, 2025 14:39
@coderabbitai coderabbitai Bot mentioned this pull request Feb 6, 2025
15 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Feb 17, 2025
15 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Mar 3, 2025
15 tasks
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