You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO This is more or less expected. It takes up to a minute until the "OPEN" arrives in SILO. The history is fetched from the loculus backend, so this is up to date immediately.
The last time I checked, the "change data use terms" dialog also showed a message that it might take a bit, until it's updated.
Hmm, maybe works as intended but the intention is a bug then.
Should we not take all the fields for the seq details page from the (fast) backend as opposed to the (slow) LAPIS/SILO? This might require larger changes and not be worth it but it seems a bit unfortunate that we use a slow/out of date API where a fast one would work as well (I can't see technical reasons why we require the LAPIS capabilities when showing data about a single sequence entry).
If we can't find a good technical solution for the delayed update, we at least should somehow indicate on the page that an update is pending.
It should be possible to know for the backend whether a certain sequence is in the process of being updated to silo:
a) query the sequence via silo
b) compare the result to what's in the backend
c) if they disagree, we know that something is pending
d) we can show a banner: "update pending"
I overwrite the sequence details entry from silo with the latest entry in the data use terms history. This also allows me to refresh the page on success and show the result instantly.
Repro:
Related to #1580, @bh-ethz can you have a look? Is this expected?
The text was updated successfully, but these errors were encountered: