Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Duplicate entries returned by GET /schedules for a challenge #25

Open
callmekatootie opened this issue Feb 20, 2021 · 6 comments
Open

Comments

@callmekatootie
Copy link
Collaborator

Example:

GET https://api.topcoder-dev.com/v5/schedules?externalId=65cecf2c-7763-4854-b0de-2850cbe634b2.

I see three entries that are identical (in the sense that these are invoked at the same time, on the same endpoint, with the same payload)

    {
        "url": "https://api.topcoder-dev.com/v5/challenges/65cecf2c-7763-4854-b0de-2850cbe634b2",
        "externalId": "65cecf2c-7763-4854-b0de-2850cbe634b2",
        "method": "patch",
        "scheduleTime": "2021-02-27T07:21:00.000Z",
        "headers": {
            "content-type": "application/json",
            "Authorization": "Bearer <redacted>"
        },
        "payload": "{\"phases\":[{\"phaseId\":\"1c24cfb3-5b0a-4dbd-b6bd-4b0dff5349c6\",\"isOpen\":true}]}",
        "id": "npik4nPSj5fuepL6tIZK"
    }
@callmekatootie callmekatootie changed the title Duplicate entries returned by GET /scheduled for a challenge Duplicate entries returned by GET /schedules for a challenge Feb 20, 2021
@callmekatootie
Copy link
Collaborator Author

And this is not restricted to just this challenge id - I am finding that every challenge that I created has duplicate entries for the phases...

@ThomasKranitsas
Copy link
Contributor

The problem is on the GET endpoint that's duplicating the data... The entries in dynamo are correct. I'll fix this.

@ThomasKranitsas
Copy link
Contributor

this has been fixed

@callmekatootie
Copy link
Collaborator Author

Confirmed. I no longer see duplicates

@callmekatootie
Copy link
Collaborator Author

Issue observed again today - challenge id 78122ac7-f3d2-456e-8f53-e68627c45adc

@callmekatootie
Copy link
Collaborator Author

callmekatootie commented Feb 25, 2021

If it helps, for this challenge, I ended up submitting and reviewing (and modifying the timelines by PATCHing challenge api)... Which was not the case with the previous challenges (for which I do not see duplicates).

Duplicates were observed AFTER the actions above... Not before...

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

No branches or pull requests

2 participants