kburger
commented
9 months ago That sounds like a nice addition, thanks for the suggestion. The authentication is already in place, so adding an override type parameter should be possible. If we have/can get the timeout threshold information in the client it make perfect sense to inform them. Not sure about that one, a bit farther from my comfort zone.
I've created FAIRDataTeam/FAIRDataPoint-client#146 to track this issue in the client.
What components are related to the issue?
API, FDP Index
Which FDP are you using?
FDP managed by someone else
Version
What happened?
The interface with the status and trashcan icons has a button with the title text "Synch FDP". That apparently emits a request which is subject to a 5-minute timeout for congestion control, i.e. if you've already pinged in the last 5 mins, the request is silently dropped, which leads users to think that the FDP was re-indexed and that the status didn't change. (Clever folks may notice that the Modification time didn't change, but that's a lot to ask of users.)
Ideally, the Synch FDP button would bypass the timeout by passing some extra parameter (maybe requiring authentication some day). Barring that, some user feedback that their request was dropped would at least reduce confusion and despair.
Relevant log output
No response