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

Properly implement and expose: Profile, Backtrace. #17

Open
NotJustAnna opened this issue Feb 15, 2020 · 0 comments
Open

Properly implement and expose: Profile, Backtrace. #17

NotJustAnna opened this issue Feb 15, 2020 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@NotJustAnna
Copy link
Member

NotJustAnna commented Feb 15, 2020 •
edited
Loading

This issue is a continuation of rethinkdb/rethinkdb#5005 and rethinkdb/rethinkdb#5006

Apparently some drivers may or may not expose the Profile and Backtrace. According to the original issue 5005:

The Profile object should be something useful and convenient for end users.

I suppose we should expose it here too, but I would need another driver maintainer's hand here. Do you expose profile or backtrace? if so, how? (@gabor-boros)
@NotJustAnna NotJustAnna added the help wanted Extra attention is needed label Feb 15, 2020
@NotJustAnna NotJustAnna changed the title Implement Profile-related stuff. Properly implement and expose: Profile, Backtrace. Feb 15, 2020
NotJustAnna pushed a commit that referenced this issue Feb 17, 2020
Expose profile in Result. Partially implements #17
10cff9f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NotJustAnna