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

[BUG]: Paddle Version checking can get into an infinite loop when failing or PADDLE_HTTP_ENDPOINT is not specified #192

Open
drobison00 opened this issue Oct 24, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@drobison00
Copy link
Collaborator

Version

24.10

Which installation method(s) does this occur on?

Docker

Describe the bug.

The paddle version check requires the HTTP endpoint, if it is not specified (or doesn't exist), the progress engine will wait/retry forever.

Proposed solution

  • Make PADDLE_HTTP_ENDPOINT a required parameter in the paddle schema
  • Set some kind of maximum threshold on the @backoff decorator (maybe configurable?) so that if we fail to get the version after 5-10 minutes we fail the job.

Minimum reproducible example

No response

Relevant log output

No response

Other/Misc.

No response

@drobison00 drobison00 added the bug Something isn't working label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants