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

Timing issue when API query includes modified_since #497

Open
Allda opened this issue May 22, 2019 · 0 comments
Open

Timing issue when API query includes modified_since #497

Allda opened this issue May 22, 2019 · 0 comments
Labels
high prio enhancement New feature or request that should be implemented ASAP

Comments

@Allda
Copy link

Allda commented May 22, 2019

Hi,
I just found a bit weird behavior when making API call which includes modified_since timestamp.

Here is an example...
Let's say that some script fetches data from v1/errata/ API every 2 hours and so it sets modified_since = now() - 2 * hour. It can happen that it always gets an empty response even if a new advisory is released in that time window.
I tried to debug this weird behavior and I found a root cause. It is related to a timing issue between when an advisory is released and how often VMaaS update data (is it every 6 hours?).

When an advisory is released more than 2 hours before VMaaS updates data the API query always return an emtpy response.

@jdobes jdobes added the high prio enhancement New feature or request that should be implemented ASAP label Jul 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high prio enhancement New feature or request that should be implemented ASAP
Projects
None yet
Development

No branches or pull requests

2 participants