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

Migration failing after update #295

Open
0xArdi opened this issue Aug 27, 2024 · 1 comment
Open

Migration failing after update #295

0xArdi opened this issue Aug 27, 2024 · 1 comment

Comments

@0xArdi
Copy link
Collaborator

0xArdi commented Aug 27, 2024

A user updated from rc86 to rc117. The user was staked on the pearl_alpha.
After updating pearl, the user opened the app and clicked Start agent.
The steps the service then took are:

  1. Service got unstaked from pearl_alpha
  2. Service got updated
  3. Service was NOT be staked on pearl_beta.

Upon a look at cli.log, step 3 was a result of the provided params requiring the CLI to stake the service on pearl_alpha instead of pearl_beta. The issue was resolved by simply restarting pearl and starting the agent again.

Another thing to note is that when step 3 failed, the agent started running without being staked. This is not desired behaviour, as it could lead to agent draining the trader balance since it will never stop trading.

@adrianoVal
Copy link
Collaborator

Another user seems to have had a similar issue:
pearl_logs_2024-08-28T17:44:16.341Z-0.1.0-rc118.zip

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

No branches or pull requests

2 participants