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.

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

Add the ability to inspect the state of observable sequences #1859

Open
glopesdev opened this issue Jun 24, 2024 · 1 comment · May be fixed by #1975
Open

Add the ability to inspect the state of observable sequences #1859

glopesdev opened this issue Jun 24, 2024 · 1 comment · May be fixed by #1975
Labels
proposal Request for a new feature
Milestone

Comments

@glopesdev
Copy link
Member

  • Editor-integrated feature vs visualizer approach
  • Timestamp all events with performance counters and reconstruct timeline afterwards
  • Another idea was to use a subject that automatically collects timestamps (but this one would require merging all events)
  • Debug / trace panel dedicated for this vs drawing annotations in the workflow panel
  • How to keep memory of state before visualizer is open?
@glopesdev glopesdev added the proposal Request for a new feature label Jun 24, 2024
@glopesdev glopesdev added this to the 2.9 milestone Jun 24, 2024
@glopesdev
Copy link
Member Author

Maybe there are two types of "values" we want to get out of this:

  • Counter-based summary of changes in state (# of subscriptions, # of notifications, # of completed sequences, etc).
  • Expanded materialize node, with precisely timestamped value for every change in state (including subscription, cancellation, etc).

@glopesdev glopesdev linked a pull request Aug 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Request for a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant