-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fixes paginator call #3448
Fixes paginator call #3448
Conversation
Terraform plan for meta No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #2460 |
Terraform plan for dev No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #2460 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 7cd3826 |
Spoke with Jadud, this looks at the |
The paginator call was pages = paginator.paginate(Bucket="bucket", Prefix="prefix") which was therefore attempting to access the bucket named "bucket" at the path "prefix." It is unclear how this worked. Changed to pages = paginator.paginate(Bucket=bucket, Prefix=path) which provides the correct behavior in local testing. Testing in preview.
We need the non-friendly/brokered name for the bucket in production environments, not the friendly name. This looks up the brokered name, and sets the bucket name accordingly. Committing for testing.
From 15s -> 30s
19f5441
to
34f9fec
Compare
@jadudm @asteel-gsa - what's the status on this one? Should it be marked as draft? |
Moved to draft. |
This whole PR is out of date, and no longer applies. Closing. |
The paginator call was
pages = paginator.paginate(Bucket="bucket", Prefix="prefix")
which was therefore attempting to access the bucket named "bucket" at the path "prefix." It is unclear how this worked.
Changed to
pages = paginator.paginate(Bucket=bucket, Prefix=path)
which provides the correct behavior in local testing. Testing in preview.
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)git status | grep migrations
. If there are any results, you probably need to add them to the branch for the PR. Your PR should have only one new migration file for each of the component apps, except in rare circumstances; you may need to delete some and re-runpython manage.py makemigrations
to reduce the number to one. (Also, unless in exceptional circumstances, your PR should not delete any migration files.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.