-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fix cached datasets diff #8386
base: master
Are you sure you want to change the base?
Fix cached datasets diff #8386
Conversation
📝 WalkthroughWalkthroughThe changes update the dataset comparison logic within the Changes
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
CHANGELOG.unreleased.md (1)
23-23
: Spelling Correction in Changelog EntryThe entry currently reads "silient bug" on line 23. Please correct the typo to "silent bug" for clarity and accuracy.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
CHANGELOG.unreleased.md
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: circleci_build
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.
@philippotto Could you please check this PR?
Sadly I did not manage to find a why to test this reliably. Somehow the diff code is triggered relatively arbitrarily. I only managed it on wkorg in our orga and then switching between folders. When I locally switched between folders, it did not work :/
Regarding the two suggestion to fix this: I would prefer to remove the check in total (current version of the branch)
What do you think?
return !_.isEqualWith(oldDataset, newDataset, (oldValue, newValue, key) => { | ||
const didUpgradeToRenamableDS = | ||
!("directoryName" in oldValue) && "directoryName" in newValue; // TODO: Can be remove after a few weeks / months. | ||
if (key === "lastUsedByUser" || didUpgradeToRenamableDS) { | ||
// Ignore the lastUsedByUser timestamp when diffing datasets and migrating datasets to new renamable version. | ||
// Ignore updates when migrating to new renamable datasets. | ||
const didUpgradeToRenamableDS = ("directoryName" in oldDataset && "directoryName" in newDataset); // TODO: Can be remove after a few weeks / months. | ||
if(didUpgradeToRenamableDS) { | ||
return false; | ||
} | ||
return !_.isEqualWith(oldDataset, newDataset, (_oldValue, _newValue, key) => { | ||
if (key === "lastUsedByUser") { | ||
// Ignore the lastUsedByUser timestamp when diffing datasets. |
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.
@philippotto We have 2 possiblilities of fixing this: Either avoid the invalid access by extracting the check from the inner isEqualWith
method like done here.
// Ignore updates when migrating to new renamable datasets. | ||
const didUpgradeToRenamableDS = ("directoryName" in oldDataset && "directoryName" in newDataset); // TODO: Can be remove after a few weeks / months. | ||
if(didUpgradeToRenamableDS) { | ||
return false; | ||
} |
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.
Or we remove whole check as we think that most of the user already refreshed their cached datasets after the dataset renaming pr. That's why this TODO comment was here.
const didUpgradeToRenamableDS = | ||
!("directoryName" in oldValue) && "directoryName" in newValue; // TODO: Can be remove after a few weeks / months. | ||
if (key === "lastUsedByUser" || didUpgradeToRenamableDS) { |
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.
what will happen if a user hasn't logged into wk for the past few months and logs in now?
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.
I'd say that all dataset are maked as diffs and thus are listed in the notification toast.
See:
webknossos/frontend/javascripts/dashboard/dataset/queries.tsx
Lines 518 to 549 in 5447c6e
export function generateDiffMessage(diff: { | |
changed: number; | |
onlyInOld: number; | |
onlyInNew: number; | |
}) { | |
const joinStrings = (a: string, b: string) => { | |
if (a && b) { | |
return `${a} ${b}`; | |
} | |
return `${a}${b}`; | |
}; | |
const newOrChangedCount = diff.onlyInNew + diff.changed; | |
const newStr = diff.onlyInNew > 0 ? `${diff.onlyInNew} new ` : ""; | |
const changedStr = diff.changed > 0 ? `${diff.changed} changed ` : ""; | |
const maybeAnd = changedStr && newStr ? "and " : ""; | |
const maybeAlso = newOrChangedCount ? "Also, " : ""; | |
const removedStr = | |
diff.onlyInOld > 0 | |
? `${maybeAlso}${diff.onlyInOld} ${Utils.pluralize( | |
"dataset", | |
diff.onlyInOld, | |
)} no longer ${Utils.conjugate("exist", diff.onlyInOld)} in this folder.` | |
: ""; | |
const maybeNewAndChangedSentence = newOrChangedCount | |
? `There ${Utils.conjugate( | |
"are", | |
newOrChangedCount, | |
"is", | |
)} ${newStr}${maybeAnd}${changedStr}${Utils.pluralize("dataset", newOrChangedCount)}.` | |
: ""; | |
return joinStrings(maybeNewAndChangedSentence, removedStr); | |
} |
And
webknossos/frontend/javascripts/dashboard/dataset/queries.tsx
Lines 204 to 215 in 5447c6e
Toast.info( | |
<> | |
{generateDiffMessage(diff)}{" "} | |
<a href="#" onClick={acceptNewDatasets}> | |
Show updated list. | |
</a> | |
</>, | |
{ | |
key: `new-datasets-are-available-${folderId || null}`, | |
timeout: DATASET_POLLING_INTERVAL / 2, | |
}, | |
); |
So it might be confusing 🤷. Alternatively we need to maintain this check for ever or at least some more months 🤔
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.
ok, I think, this is okay as it's low impact :)
Co-authored-by: Philipp Otto <[email protected]>
URL of deployed dev instance (used for testing):
Steps to test:
Issues:
(Please delete unneeded items, merge only when none are left open)