notatallshaw-gts commented on PR #30487: URL: https://github.com/apache/airflow/pull/30487#issuecomment-1516429143
FYI I see they actually replied in a more useful manner on this post that they are facing a bug in protobuf with trying to upgrade to protobuf 4: https://forums.mysql.com/read.php?50,708753,708764#msg-708764 > We are currently working on upgrading Python Protobuf to 4.x in the upcoming release, but we are facing a blocker. A bug in the latest protobuf version (https://github.com/protocolbuffers/protobuf/issues/12373) is affecting our implementation. From: Jarek Potiuk ***@***.***> Sent: Thursday, April 20, 2023 6:12 AM To: apache/airflow ***@***.***> Cc: Damian Shaw ***@***.***>; Manual ***@***.***> Subject: Re: [apache/airflow] Remove mysql-connector-python (PR #30487) FYI. MySQL does not really collaboarate. They released a new version of mysql-connector-python 8.0.33` two days ago, but it still has < 3.20 limit on protobuf. Also, I got this - completely useless and apparently automatically generated response today to my issue: Here are the general steps to upgrade to a newer version of protobuf: Check compatibility: Before upgrading to a newer version of protobuf, check if the new version is compatible with your current codebase and other dependencies. Review the release notes and documentation to see if there are any changes or deprecations that could affect your code. Update protobuf files: If you have any custom protobuf files, update them to the latest version. You can use the protoc compiler to generate updated code from the new protobuf files. Update dependencies: If you are using a language-specific implementation of protobuf (such as the Python protobuf package or the Java protobuf library), update your dependencies to the latest version. Update code: Update your code to use the new version of protobuf. This may involve updating method signatures, changing import statements, and updating serialization/deserialization code. Test thoroughly: After making the updates, test your code thoroughly to ensure that everything works as expected. Test both positive and negative cases to ensure that there are no regressions or new issues introduced by the upgrade. Roll back if necessary: If you encounter any issues or compatibility problems, be prepared to roll back to the previous version of protobuf until the issues can be resolved. By following these steps, you should be able to successfully upgrade to a newer version of protobuf while minimizing the risk of compatibility issues and regressions. I answered appropriately : https://forums.mysql.com/read.php?50,708413,708803#msg-708803 — Reply to this email directly, view it on GitHub<https://github.com/apache/airflow/pull/30487#issuecomment-1516073030>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2RHOLEW646OZOLINFQNFTTXCEDYDANCNFSM6AAAAAAWUEJ3QI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>> ________________________________ Strike Technologies, LLC (“Strike”) is part of the GTS family of companies. Strike is a technology solutions provider, and is not a broker or dealer and does not transact any securities related business directly whatsoever. This communication is the property of Strike and its affiliates, and does not constitute an offer to sell or the solicitation of an offer to buy any security in any jurisdiction. It is intended only for the person to whom it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this communication, or the information contained herein, by anyone other than the intended recipient is prohibited. If you have received this communication in error, please immediately notify Strike at ***@***.***, and delete and destroy any copies hereof. ________________________________ CONFIDENTIALITY / PRIVILEGE NOTICE: This transmission and any attachments are intended solely for the addressee. This transmission is covered by the Electronic Communications Privacy Act, 18 U.S.C ''2510-2521. The information contained in this transmission is confidential in nature and protected from further use or disclosure under U.S. Pub. L. 106-102, 113 U.S. Stat. 1338 (1999), and may be subject to attorney-client or other legal privilege. Your use or disclosure of this information for any purpose other than that intended by its transmittal is strictly prohibited, and may subject you to fines and/or penalties under federal and state law. If you are not the intended recipient of this transmission, please DESTROY ALL COPIES RECEIVED and confirm destruction to the sender via return transmittal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
