-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add basic testing for coldstart and scaling #9
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Aleksandr Tserepov-Savolainen <[email protected]>
Signed-off-by: Aleksandr Tserepov-Savolainen <[email protected]>
# Azure Function (verify-signature) URL | ||
URL = "https://ghaf-devenv-microsign-aleksandrtserepo-app.azurewebsites.net/api/verify-signature" | ||
#URL = "http://localhost:7071/api/VerifySignature" | ||
#URL = "https://ghaf-devenv-signverify.azurewebsites.net/api/verifysignature" |
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.
Do these commented out lines serve any purpose? They're ok for me, if one expects to regularly enable the lines e.g. when debugging.
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.
Not really, just a leftover from debugging session. Will clean. Thanks!
print(f"Received 503 from {url}. Retrying... (retry count: {retry_count + 1})") | ||
retry_count += 1 | ||
time.sleep(sleep_interval) | ||
else: |
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.
Should result code 1(?) indicating that signature verification process seems to work, but signature is wrong, be handled differently from a complete failure?
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.
Good point. The thing was that we were trying to catch 503 here as that was the biggest concern (intermittent 503 most likely due to cold start) and I didn't pay too much attention at the other details. Will fix. Thanks!
No description provided.