Skip to content

New Release#363

Merged
emmanuelm41 merged 1 commit into
mainfrom
dev
May 7, 2025
Merged

New Release#363
emmanuelm41 merged 1 commit into
mainfrom
dev

Conversation

@emmanuelm41
Copy link
Copy Markdown
Member

No description provided.

…#362)

* feat: add system actors whose robust address is not present for calib

* chore: code improvements
@emmanuelm41 emmanuelm41 merged commit 69b97fe into main May 7, 2025
9 of 10 checks passed
Copy link
Copy Markdown

@windsurf-bot windsurf-bot Bot left a comment

Choose a reason for hiding this comment

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

Other comments: 0 Blocking, 0 Optional, 0 Nit, 1 FYI
  • FYI: tools/version_mapping.go (10-12) FYI: Mamma mia! 🍝 I like this refactoring - adding the new constant makes the code more readable and maintainable. The alignment of the constants is *chef's kiss* 🤌 - just like perfectly aligned lasagna layers!

Comment on lines +40 to +42
// CalibrationActorsId Map to identify system actors which don't have an associated robust address in the calibration network
// These are storage miners that initiated the calibration network
var CalibrationActorsId = map[string]bool{
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Mamma mia! 🍝 This new CalibrationActorsId map looks good, but the comment could use a bit more sauce! 🤌 Perhaps add more details about what these specific miners do in the calibration network and why they need special handling. It would help future developers understand the purpose better! 🍕

Comment on lines +127 to +131
if tools.ParseRawNetworkName(a.networkName) == tools.CalibrationNetwork {
if _, ok := CalibrationActorsId[add.String()]; ok {
return add.String(), nil
}
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

That's-a nice calibration network check! 🤌 But it might be helpful to add a debug log message when we hit this special case. Without logging, it's like trying to find a meatball in a bowl of spaghetti! 🍝 This would make troubleshooting easier if someone wonders why a particular address is being handled differently.

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

Successfully merging this pull request may close these issues.

1 participant