-
Notifications
You must be signed in to change notification settings - Fork 75
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
wrong time to call 'TraceBatchFinishFunc' #63
Comments
I just noticed this too. By calling it here, it captures the wrong items slice, so the finish function from the tracing always gets an empty slice. |
PRs are open :) |
mjq
pushed a commit
to mjq/dataloader
that referenced
this issue
Mar 29, 2021
The slice of *Result objects passed to TraceBatchFinishFunc was always empty. By moving the `defer finish(items)` down below where items is assigned the results of the batch function, tracers are passed the actual results. Fixes graph-gophers#63.
mjq
pushed a commit
to mjq/dataloader
that referenced
this issue
Mar 29, 2021
The slice of *Result objects passed to TraceBatchFinishFunc was always empty. By moving the `defer finish(items)` down below where items is assigned the results of the batch function, tracers are passed the actual results. Fixes graph-gophers#63.
mjq
added a commit
to mjq/dataloader
that referenced
this issue
Mar 30, 2021
The slice of *Result objects passed to TraceBatchFinishFunc was always empty. By moving the `defer finish(items)` down below where items is assigned the results of the batch function, tracers are passed the actual results. Fixes graph-gophers#63.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: