Skip to content

Conversation

@AkshatJoshi-18
Copy link

@AkshatJoshi-18 AkshatJoshi-18 commented Apr 14, 2023

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.rst or {issue_number}.significant.rst, in newsfragments.

@boring-cyborg boring-cyborg bot added area:providers provider:amazon AWS/Amazon - related issues labels Apr 14, 2023
@boring-cyborg
Copy link

boring-cyborg bot commented Apr 14, 2023

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)
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

@eladkal eladkal changed the title Update quicksight.py / QuickSightHook bug on wait_for_state() function: #30626 Fix QuickSightHook bug on wait_for_state() function Apr 14, 2023
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:
Copy link

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

Copy link
Author

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
Copy link
Member

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.

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label May 30, 2023
Co-authored-by: Vincent <97131062+vincbeck@users.noreply.github.com>
@github-actions github-actions bot removed the stale Stale PRs per the .github/workflows/stale.yml policy file label May 31, 2023
@o-nikolas
Copy link
Contributor

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.
@potiuk any ideas what's happening here or what I can do to debug further?

@potiuk
Copy link
Member

potiuk commented Jun 5, 2023

Just rebased it to see. Could be a temporary github problem.

@potiuk
Copy link
Member

potiuk commented Jun 5, 2023

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.

@o-nikolas
Copy link
Contributor

BTW. If you want to debug it, I do not have more tools than anyone else. It's just regular gihub docs/info.

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

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.

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 😃

@potiuk
Copy link
Member

potiuk commented Jun 7, 2023

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.

@potiuk
Copy link
Member

potiuk commented Jun 8, 2023

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?)

@potiuk potiuk added the use public runners Makes sure that Public runners are used even if commiters creates the PR (useful for testing) label Jun 8, 2023
@AkshatJoshi-18
Copy link
Author

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 :)

@AkshatJoshi-18 AkshatJoshi-18 closed this by deleting the head repository Jun 8, 2023
@potiuk
Copy link
Member

potiuk commented Jun 8, 2023

BTW. I think I have a fix for similar case in #31792

@o-nikolas
Copy link
Contributor

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?

@AkshatJoshi-18
Copy link
Author

@o-nikolas The repository that submitted this pull request has been deleted.

@o-nikolas
Copy link
Contributor

@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!

@AkshatJoshi-18
Copy link
Author

@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 :)

@o-nikolas
Copy link
Contributor

Sounds good, and no worries, hopefully we see you around again soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:amazon AWS/Amazon - related issues use public runners Makes sure that Public runners are used even if commiters creates the PR (useful for testing)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

QuickSightHook bug on wait_for_state() function:

6 participants