Skip to content
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

Retracted cache listing not recognized #8334

Open
Lineflyer opened this issue May 12, 2020 · 1 comment
Open

Retracted cache listing not recognized #8334

Lineflyer opened this issue May 12, 2020 · 1 comment
Labels
Prio - Low A minor issue not having significant influence to a feature/function.

Comments

@Lineflyer
Copy link
Member

This is a rather special/rare case coming in from support mail:

  • Save a cache (in this case an event) in c:geo
  • The listing gets retrated by a reviewer (in this case because the event must not take place...Corona)
  • Refresh the listing in c:geo

Result:
Refreshing progress ends rather fast, no visual change in cache status / logs, etc.
(Info: Reason is probably, that a retracted cache page just returns a 404 error)

Expected result:
We cannot get any retracted information or similar, as the webpage just provides a 404 after retraction. However if we are unable to update a cache (for whatever reason) I would expect any kind of error message or toast at least. In case of a 404 e.g. a "This cache does not exist/no longer exist" response

@Lineflyer Lineflyer added the Prio - Low A minor issue not having significant influence to a feature/function. label May 12, 2020
@MagpieFourtyTwo
Copy link

MagpieFourtyTwo commented May 13, 2020

Yep - could just verify with https://coord.info/GC6Z2Q3

This was a tradi, which was withdrawn by reviewer due to a kind of obscure distance violation (right after I logged the FTF, that's why I still have it offline ;) ). And the described behavior was the same on 08.01.2017, as I remember now (I was a little bit astonished then, as nothing happened after refreshing the cache).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio - Low A minor issue not having significant influence to a feature/function.
Projects
None yet
Development

No branches or pull requests

2 participants