-
Notifications
You must be signed in to change notification settings - Fork 29.7k
fix: content_aware_hash tag for fuchsia merge / upload #173253
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
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request refactors the CIPD package upload process to fix a race condition when tagging with content_aware_hash. The change separates the package creation and tagging steps. I've identified a critical issue where an incorrect package name is being used for the new tagging logic, which will likely cause failures. I've also suggested adding a docstring to the new helper function to adhere to the project's style guide. The Flutter style guide specifies that Python code should follow the Google Python Style Guide. The Google guide requires docstrings for public modules, functions, classes, and methods.
engine/src/flutter/tools/fuchsia/merge_and_upload_debug_symbols.py
Outdated
Show resolved
Hide resolved
engine/src/flutter/tools/fuchsia/merge_and_upload_debug_symbols.py
Outdated
Show resolved
Hide resolved
|
Also tag after the upload, similar to flutter#173140 fixes: flutter#173137
Also tag after the upload, similar to flutter#173140 fixes: flutter#173137
Also tag after the upload, similar to flutter#173140 fixes: flutter#173137
Also tag after the upload, similar to flutter#173140 fixes: flutter#173137
Also tag after the upload, similar to flutter#173140 fixes: flutter#173137
Also tag after the upload, similar to #173140
fixes: #173137