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

fix(mu): messages not making it to SU on processes spawned from other processes #1125

Open
VinceJuliano opened this issue Jan 24, 2025 · 0 comments

Comments

@VinceJuliano
Copy link
Collaborator

Background

When processes spawn other processes and immediately send them messages, the MU cannot detect that the target is a process and sends the message to arweave, the CU then receives this from the SU, for example https://www.ao.link/#/message/owRdq8EJXTtwKnlS8Yd5iJAlTxiIrGOgI7VUzJ3VDEE

{
"error": "Error Encountered when loading message from Scheduler Unit: 400: {"error":"Message or Process not found"}"
}

Solution

It would be possible in the MU to store freshly spawned ids and then it would know they are a process and not a wallet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant