Skip to content

Conversation

lsytj0413
Copy link
Contributor

Fix: #3004

@lsytj0413
Copy link
Contributor Author

It's very strange restatectl will start an metadata-server .....

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this problem @lsytj0413. I think we can use the TaskCenterFutureExt::in_tc call here.

@@ -58,7 +58,7 @@ where
.expect("task_center builds")
.into_handle();

let result = task_center.run_sync(|| fn_body(config)).await;
let result = task_center.run_async(|| fn_body(config)).await;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way to run the fn_body generated future in the task center context can be expressed via

let result = fn_body(config).in_tc(&task_center).await;

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your advise, fixed.

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the PR so quickly @lsytj0413. LGTM. Merging it now.

@tillrohrmann tillrohrmann merged commit 80c1f46 into restatedev:main Apr 11, 2025
25 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2025
@lsytj0413 lsytj0413 deleted the fix-3004 branch April 11, 2025 08:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

restatectl logs dump --log-id 1 panic
2 participants