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

[Refactor proposal] futures can be hard to maintain/debug; let's consider alternatives #337

Open
cmcginley-splunk opened this issue Dec 10, 2024 · 0 comments
Open

[Refactor proposal] futures can be hard to maintain/debug; let's consider alternatives #337

cmcginley-splunk opened this issue Dec 10, 2024 · 0 comments

Comments

@cmcginley-splunk
Copy link
Collaborator

cmcginley-splunk commented Dec 10, 2024 •
edited
Loading

As described, we currently manage threads in contentctl using futures; these can be hard to debug and maintain. We should look into other options.
@cmcginley-splunk cmcginley-splunk changed the title [Refactor proposal] futures can be hard to maintain/debug; let [Refactor proposal] futures can be hard to maintain/debug; let's consider alternatives Dec 10, 2024
@cmcginley-splunk cmcginley-splunk mentioned this issue Dec 10, 2024
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cmcginley-splunk