Skip to content
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

[Migrated] Add touch_try_count and raise RequestException #713

Closed
jneves opened this issue Feb 20, 2021 · 2 comments
Closed

[Migrated] Add touch_try_count and raise RequestException #713

jneves opened this issue Feb 20, 2021 · 2 comments
Labels
auto-closed [Bot] Closed, details in comments no-activity [Bot] Closing soon if no new activity

Comments

@jneves
Copy link
Contributor

jneves commented Feb 20, 2021

Originally from: Miserlou/Zappa#1808 by sebatyler

Description

Update for my project using zappa is often failing. It is because of 2 reasons.

  • Downloading dependency is facing read timeout. Message is below.
Downloading and installing dependencies..
 - ruamel.yaml==0.15.60: Downloading
HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Read timed out. (read timeout=2)
  • Checking touch_path is failing. Message is below.
Error: Warning! Status check on the deployed lambda failed. A GET request to '/' yielded a 504 response code.

Fatal error: local() encountered an error (return code 1) while executing 'zappa update prod'

So I want to add 'touch_try_count' setting and raise exception explicitly when request failed.

Copy link

github-actions bot commented Apr 3, 2024

Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.

@github-actions github-actions bot added the no-activity [Bot] Closing soon if no new activity label Apr 3, 2024
Copy link

Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue.

@github-actions github-actions bot added the auto-closed [Bot] Closed, details in comments label Apr 13, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-closed [Bot] Closed, details in comments no-activity [Bot] Closing soon if no new activity
Projects
None yet
Development

No branches or pull requests

1 participant