José Francisco Calvo

The new `status` column created at `records` table should be refreshed every time an associated response is created/updated/upserted/deleted. There are several approaches that we can explore to solve this issue:...

chore: expose search engine ping max time as a new environment variable

1

# Description This PR will expose a new `ARGILLA_SEARCH_ENGINE_PING_TIMEOUT` environment variable allowing us to control the maximum time (in seconds) waiting for the search engine to be ready when starting...

We should add `status` column to `records` table with the following details: * Possible values for this `status` column are `pending` and `completed`. * This new column will be non-nullable....

We should add a restriction to only allow updating a dataset distribution settings when the associated records for the dataset has not responses. As an alternative to this we could...

[FEATURE] Add a way to know which user is the creator of a dataset and record

2

**Is your feature request related to a problem? Please describe.** Right now we don't have a way to know the user that created a dataset or record. **Describe the solution...

[FEATURE] Take advantage of multiple cores when running tests

2

We should take advantage of running our test suite with multiple cores instead of running one by one, specially now that we have CPUs with 8 or more cores. In...