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

disable tq info caching in task queue test #726

Merged
merged 2 commits into from
Jan 8, 2025

Conversation

carlydf
Copy link
Contributor

@carlydf carlydf commented Dec 9, 2024

What was changed

Why?

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

Copy link
Collaborator

@josh-berry josh-berry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@carlydf Do you plan to merge this soon? Would like to take it in the next release if it's ready.

go.mod Outdated Show resolved Hide resolved
Comment on lines +219 to +221
// this is overridden since we don't want caching to be enabled while testing DescribeTaskQueue
// behaviour related to versioning
"matching.TaskQueueInfoByBuildIdTTL": 0 * time.Second,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we disable search attribute caching for all users of the dev server, not just our test suite. I wonder if we should do that here too. Though it may give the dev server users unreasonable expectations about eventual consistency for task queue info.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's reasonable for the dev server to have the caching for now -- can always change it later, but I think this caching mechanism may change in the future as well

@carlydf carlydf merged commit 7d54c66 into main Jan 8, 2025
7 checks passed
@carlydf carlydf deleted the cdf/disable-tq-info-caching branch January 8, 2025 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants