-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix QuickSightHook bug on wait_for_state() function
#30637
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
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
|
QuickSightHook bug on wait_for_state() function
| self.log.info("Current status is %s", status) | ||
| if status in self.FAILED_STATES: | ||
| status = self.get_status(aws_account_id, data_set_id, ingestion_id) | ||
| if status in self.FAILED_STATES: |
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.
here, there is an indentation error
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.
Thank for help.
| time.sleep(check_interval) | ||
| sec += check_interval | ||
| status = self.get_status(aws_account_id, data_set_id, ingestion_id) | ||
| # wait and try again |
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.
The indentation is really wrong here.
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
Co-authored-by: Vincent <97131062+vincbeck@users.noreply.github.com>
|
I've retried the build several times now with fresh main, but every time the jobs fail immediately with the GH error "This job failed", no logs at all to debug with. |
|
Just rebased it to see. Could be a temporary github problem. |
|
BTW. If you want to debug it, I do not have more tools than anyone else. It's just regular gihub docs/info. Usually "job failed" (but this is just observation, I have no other tools to verify it) means that something is wrong on github side. The "Job failed" has exactly "0" indication (as you noticed) of what's going on, But the right tool to help in the future, if we see jobs consistently failing is that any committer can open an issue to github https://support.github.com/ where there is a "other issue" or "report a bug" section when you can open an issue to GitHub support. You can choose "ASF Enterprise" level support and if you do, and describe the problem they usually answer in few hours. |
Yupp, I know, but you've been working particularly close with Github Actions/CI longer than I have, so you have many tips, tricks and knowledge that I don't
And this proves my point 😆 I had no idea that we could do this, thanks for the tip. I'll try build this a few more times and if it doesn't unstick itself I'll open a ticket 😃 |
|
I honestly, have no idea what's up with this one - I can't even rebase it any more. Opening it from scratch is probably a good idea. |
|
Ok @o-nikolas @AkshatJoshi-18 I think I know what could have caused it - > can you please REBASE it instead of retrying the build and let me know (For some reason I cannot rebase it any more @AkshatJoshi-18 - maybe you can rebase it again?) |
ok i will try :) |
|
BTW. I think I have a fix for similar case in #31792 |
Nice! @AkshatJoshi-18 can you re-open a PR with the changes that remained in this one? |
|
@o-nikolas The repository that submitted this pull request has been deleted. |
Yes, you'll need to re-create a fork and the changes :) But if you're withdrawing yourself from this task that's also fine! |
|
@o-nikolas I think ! the second option will be great for you guys :) because i created a lot of mess for you people 😅 . so I guess i will withdrawing myself :) |
|
Sounds good, and no worries, hopefully we see you around again soon! |
Closes: #30626
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.