-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
Testing a project stores the user contribution. #1582
Comments
This behavior is as expected. Why? Because we want also to allow you to test your webhooks solution (if you have any), so we need to store everything as "it is published". When you click in the publish button, everything is cleaned, so you are all the time in a sandbox until you publish it. |
On Wed, Jul 12, 2017 at 1:47 PM Daniel Lombraña González < ***@***.***> wrote:
Closed #1582 <#1582>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1582 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AQy7cu778-iKjuQDrjNQrzmwV5PgduS2ks5sNIExgaJpZM4OLF69>
.
Dear Daniel,
The published results are not cleaned on publishing.
|
Oh, then that's a bug. But in our code we can see clearly that task_runs, results, and even webhooks entries in the log are deleted (see this). Can you give us more details? Which domain object is not deleted? Also, this could be an issue with the cache, the objects in the DB are deleted but they're still cached for a few minutes. Can you check if after publishing the project you can get the task_run and results via the API? |
I've been checking the code, and yes, the problem is that we have not cleaned the cache. We should add in that method the following: cached_projects.delete_project(short_name) Good catch! |
Be sure that we clean the cache after publishing the project.
When a project is tested by clicking on "Test it" before publishing, it stores the answers provided by the project owner and considers them to have contributed to the task. It should be done in a sandbox mode.
The text was updated successfully, but these errors were encountered: