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

Get requests fail second time #219

Closed

Conversation

artlowel
Copy link
Member

@artlowel artlowel commented Jan 31, 2018

This PR closes #216

The reason for the issue was that the request pending status was never removed after a request was completed, due to a mistake in the switch from hrefs to uuids as identifiers for requests. Subsequent requests for the same URL (after something had been removed from the cache) wouldn't be executed because the request seemed to be already pending

This PR contains a test for the issue, and a fix.

Art Lowel added 2 commits January 31, 2018 11:05
@ghost ghost assigned artlowel Jan 31, 2018
@ghost ghost added the needs review label Jan 31, 2018
@atarix83
Copy link
Contributor

I've tried the changes, new requests are executed, but I've noted an odd behavior.
After something had been removed from the cache the first subsequent request of a dso returns an observable of a RemoteData that emits a value many several times with no reason.

I also observed that In a RemoteData object returned, the value of isResponsePending doesn't reflect always the value of the responsePending, this could be an issue?

@artlowel artlowel changed the title Issue 216 get requests fail second time Get requests fail second time Feb 1, 2018
@artlowel
Copy link
Member Author

closing in favour of #367

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue with root endpoint response cache time to live
2 participants