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.

Sign up for GitHub

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

Jump to bottom

Train data fetch is not working properly when there is two parallel requests with the same datasetId #83

Open
cguz opened this issue Oct 12, 2022 · 1 comment
Open

Train data fetch is not working properly when there is two parallel requests with the same datasetId #83

cguz opened this issue Oct 12, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@cguz
Copy link
Contributor

cguz commented Oct 12, 2022 •
edited
Loading

To reproduce the error execute in parallel two train data fetch with the same expId and datasetId but with different labels.

This is happening because we got the total number of current obtained train data from the database with the "exp_id + dataset_id", which I think is wrong.

We need to consider a unique session id for each train data fetch
@georgeslabreche
Copy link
Collaborator

Is there a use-case for having two separate data feed subscriptions with the same experiment id and dataset id?

@georgeslabreche georgeslabreche removed their assignment Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@georgeslabreche @cguz