Protein Table spreads out when too many PubMed IDs

For this condensate, I noticed the behavior on Firefox and Chrome both.

https://cd-code.org/condensate/hybrid_Q7ZXV8

added bug front-end labels

Cannot reproduce it in the dev instance. https://dev.cd-code.org/condensate/hybrid_Q7ZXV8

Pubmed is disabled?

So data in dev and prod is at different versions, and testing on dev further deviates the data from the prod.

So, from time to time, we have to update the Dev data with Prod so that we have some sense still prevailing in our Dev setup. Wherever you see data disparity in Prod or Dev, its coz of the database.

As of now we copy the following from Prod to Dev DBs: MongoDB - All collections PostgreSQL - UpdateItems and NovelCondensates

As of now we copy the following from Prod to Dev DBs: MongoDB - All collections PostgreSQL - UpdateItems and NovelCondensates

For the strapi database (UpdateItems and NovelConndesates), I am worried that all those items are linked to the users. But, the users are different from Prod's. It can be inconsistent relationships.

Yes, I get that part. Wrong users might get connected to UpdateItems as reviewers and creators. But that is fine for the Dev env, I guess. It doesn't really matter that much, it is anyways treated as test data.

mentioned in commit 7f2ad430

closed