[
https://issues.apache.org/jira/browse/WHIMSY-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889519#comment-16889519
]
Sebb commented on WHIMSY-278:
-----------------------------
The member status change processing removes the existing entry and adds it back
in the new section, so failure to find the entry could result in a
near-duplicate.
Member text update tries to replace the original entry with the new one, so
operating on the wrong file version could result in no change being made.
I've implemented a check to ensure that the member entry is found when updating
the file. This appears to be working OK.
However, there is a problem with caching.
I dropped Creadur from my list of projects.
Long after the members.txt file has been updated and synched to the workspace,
my entry still shows Creadur.
If I attempt to remove it again, I get an error as expected (because the
original text does not agree with the brand-new checkout).
The old text seems to persist way beyond its sell by date.
Note: I have tried several browsers, but my page still shows Creadur.
> Stale members.txt after update
> ------------------------------
>
> Key: WHIMSY-278
> URL: https://issues.apache.org/jira/browse/WHIMSY-278
> Project: Whimsy
> Issue Type: Bug
> Reporter: Sebb
> Priority: Major
>
> Updated my entry in members.txt, changing the list of moderations
> File was updated (r91854), however the GUI display did not change, even when
> I logged in on a different browser.
> Looks like changes are not invalidating the cache and/or workspace is not
> being updated.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
