Skip to content

Conversation

@palfrey
Copy link
Member

@palfrey palfrey commented Nov 19, 2025

Description

Please include a summary of the changes and the related issue. Please also
include relevant motivation and context.

Fixes # (issue)

Type of change

Please delete options that aren't relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to
    not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please also list any relevant details for your test configuration

Checklist

  • Updated documentation if needed
  • Tests added/amended
  • bazel test //... passes locally
  • PR is contained in a single commit, using git amend see some docs

This change is Reviewable

let client = self.client_pool.next();
let config = client.client_config();
if config.mocks.is_none() {
if config.mocks.is_none() && !client.is_connected() {
Copy link
Member Author

Choose a reason for hiding this comment

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

This means Fred isn't logging every time we call this

@palfrey palfrey force-pushed the store-tester-stability branch from 711f91a to f2c36b6 Compare November 19, 2025 16:26
Copy link
Collaborator

@MarcusSorealheis MarcusSorealheis left a comment

Choose a reason for hiding this comment

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

Provided you can explain why we have commented out the CI workflow, that's fine. We have never used FIXME in this repo, or not that I can recall. Otherwise, I'm good with it.

fi
shell: bash

# FIXME(palfrey): Can't make this reliably run in CI
Copy link
Collaborator

Choose a reason for hiding this comment

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

why?

let res = store_clone.get_and_decode(data.clone()).await?;
if let Some(existing_data) = res {
data.version = existing_data.version + 1;
data.version = existing_data.version;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Didn't realize we tried to hack optimistic locking here. This change should prevent race conditions if the version was already up to date. Have you verified that this does not break the update logic of your tester?

Copy link
Collaborator

@MarcusSorealheis MarcusSorealheis left a comment

Choose a reason for hiding this comment

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

There is some issue in the queueing mechanism.

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.

2 participants