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

Pedro/cleanup forks #11

Merged
merged 8 commits into from
Jan 24, 2025
Merged

Pedro/cleanup forks #11

merged 8 commits into from
Jan 24, 2025

Conversation

otherview
Copy link
Member

Describe your changes

Multiple cleanups + tech debt + update thor to v2.1.6

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have executed relevant tests
  • I have added thorough tests for the changes
  • Does this need a documentation update?

@otherview otherview force-pushed the pedro/cleanup_forks branch 2 times, most recently from b7fb83c to 5105b34 Compare December 30, 2024 15:37
@otherview otherview force-pushed the pedro/cleanup_forks branch 3 times, most recently from e6d0c12 to 164411e Compare December 30, 2024 16:54
Copy link
Member

@paologalligit paologalligit left a comment

Choose a reason for hiding this comment

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

Looks good, just left a minor comment

thorbuilder/thorbuilder_test.go Outdated Show resolved Hide resolved
Copy link
Member

@freemanzMrojo freemanzMrojo left a comment

Choose a reason for hiding this comment

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

LGTM, I put a couple of comments though 👍

sudo apt-get update
sudo apt-get install -y make git build-essential

- name: Pull Docker Image
Copy link
Member

Choose a reason for hiding this comment

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

I guess this is because of the docker_test.go file, right? Should not this be pulled within the code? I can see actually at docker_node.go code trying to do so.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeap! it's mainly to speed up things.

Identity: thor.MustParseBytes32("0x0000000000000068747470733a2f2f617070732e7665636861696e2e6f72672f"),
Authority: []thorgenesis.Authority{
{
MasterAddress: *SixNNAccount1.Address,
Copy link
Member

Choose a reason for hiding this comment

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

I am using these SixNN... as part of my config (I renamed them in my branch and put them in the preset file). Not sure whether they are meant to be reused or not. Is there a specifc reason not to? Tbh for the Galactica config I had in place I did not see the need to create from scratch more accounts.

To sum up, not sure if it makes sense to put common preset configuration somewhere (I picked preset.go but maybe there is a better home).

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah it's incentivized to use those.
The presets are meant to be pre-defined network configurations. It's handy to avoid massive setups.

I think the design still needs a bit of work, for example I removed the hardcoding of the thor binary and added a check to make sure that if the preset is used in the local execution, the user of the preset would make sure to superseed the config and add a ExecArtifact path.

@otherview otherview merged commit c2d3a3b into main Jan 24, 2025
8 checks passed
@otherview otherview deleted the pedro/cleanup_forks branch January 24, 2025 11:30
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.

3 participants