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

EAM: Fails to deploy over an existing placeholder #1480

Closed
Stebalien opened this issue Jan 14, 2023 · 0 comments
Closed

EAM: Fails to deploy over an existing placeholder #1480

Stebalien opened this issue Jan 14, 2023 · 0 comments
Assignees
@arajasek
Labels
Topic: EVM runtime
Milestone
M2.1 (rr11) Carbo...

Comments

@Stebalien
Copy link
Member

(we'll have to investigate how this isn't caught by the current tests...)

Basically, now that we can resurrect an EVM actor, we:

  1. See that an actor (placeholder) is already deployed at the computed address.
  2. Try to resurrect it.

Which clearly fails. We need to check the target actor type instead of just checking to see if it exists.
@Stebalien Stebalien added this to the M2.1 (rr11) Carbonado.2 milestone Jan 14, 2023
@Stebalien Stebalien self-assigned this Jan 14, 2023
@jennijuju jennijuju changed the title EAM: Fails to deploy over an existing embryo EAM: Fails to deploy over an existing placeholder Jan 14, 2023
@jennijuju jennijuju assigned arajasek and unassigned Stebalien Jan 14, 2023
@arajasek arajasek mentioned this issue Jan 14, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arajasek arajasek

Labels
Topic: EVM runtime
Projects
None yet
Milestone
M2.1 (rr11) Carbonado.2
Development

No branches or pull requests
2 participants
@Stebalien @arajasek