syedahsn commented on code in PR #30463: URL: https://github.com/apache/airflow/pull/30463#discussion_r1228765387
########## airflow/providers/amazon/aws/utils/waiter_with_logging.py: ########## @@ -0,0 +1,77 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +from __future__ import annotations + +import logging +import time + +from botocore.exceptions import WaiterError + +from airflow.exceptions import AirflowException + + +def wait( Review Comment: Thanks! I tried quite a few different things to get it working with tenacity, but my issue was with debugging. I found that using tenacity made the debugging very difficult. It also added complications in the unit tests (which I was able to resolve, but it took some playing around). In hindsight, I think using tenacity to implement a basic retry like this is overkill - tenacity seems to be able to implement fairly complex retry algorithms whereas we were using it as a `while` loop. I would have kept it if things were working smoothly, but I wasn't able to figure out how debugging worked, so I decided to stop before I went further down the rabbit hole :D. -- 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]
