-
Notifications
You must be signed in to change notification settings - Fork 407
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: Repository analytics is broken and not being marked as failling #3578
Labels
bug
Something isn't working
Comments
rubenfonseca
added
bug
Something isn't working
triage
Pending triage from maintainers
labels
Jan 2, 2024
github-project-automation
bot
moved this to Triage
in Powertools for AWS Lambda (Python)
Jan 2, 2024
rubenfonseca
moved this from Triage
to Working on it
in Powertools for AWS Lambda (Python)
Jan 2, 2024
7 tasks
7 tasks
github-project-automation
bot
moved this from Working on it
to Coming soon
in Powertools for AWS Lambda (Python)
Jan 2, 2024
|
github-actions
bot
added
the
pending-release
Fix or implementation already in dev waiting to be released
label
Jan 2, 2024
rubenfonseca
moved this from Coming soon
to Shipped
in Powertools for AWS Lambda (Python)
Jan 3, 2024
This is now released under 2.31.0 version! |
github-actions
bot
removed
the
pending-release
Fix or implementation already in dev waiting to be released
label
Jan 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behaviour
If there's a problem with the job, the GitHub job should fail instead of being marked as succeeded.
Current Behaviour
Since January 1st, the GitHub repository analytics job is broken. However, the jobs is still marked as "Succeeded".
Code snippet
Possible Solution
Check the output of the Lambda invocation for function errors.
Steps to Reproduce
Check the latest logs of the Dispatch Analytics job.
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.7
Packaging format used
PyPi
Debugging logs
No response
The text was updated successfully, but these errors were encountered: