(WIP) - Added layer wise reporting on push

[MetsysEht]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @MetsysEht, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the image push functionality by introducing a more detailed, layer-wise progress reporting mechanism. It allows for streaming progress updates via a standard io.Writer, improving the transparency and user experience during image uploads. The changes involve refactoring the core Write function to accept a progress writer and adapting the client-side calls accordingly.

Highlights

• Refactored Progress Reporting: The image push operation has been refactored to support more granular, layer-wise progress reporting, providing better visibility into the upload status of individual layers.
• io.Writer for Progress: The remote.Write function now accepts an io.Writer parameter, allowing external components to receive real-time progress updates during the image push.
• Thread-Safe Writing: A new syncWriter type has been introduced to ensure thread-safe concurrent writes to the provided io.Writer, crucial for handling progress updates from multiple goroutines.
• Client-Side Integration: The registry/client.go has been updated to integrate with the new remote.Write signature, passing its progressWriter directly and removing its previous direct dependency on the internal/progress package.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces layer-wise progress reporting for image pushes. The implementation creates a progress reporter for each layer. My review focuses on ensuring the new progress reporting logic is correct and robust. I've identified a few issues related to incorrect progress value calculations, which could lead to a confusing user experience, and a potential goroutine leak due to improper lifecycle management of the progress reporter. The suggested changes aim to fix these issues to make the feature reliable.