fix humanUnits for hostd using 1e7 for millions

[iuri-gg]

hostd settings is showing incorrect number for base rpc price and Sector access price. It's off by 10 due to using 1e7 instead of 1e6 for calculating millions

[changeset-bot]

🦋 Changeset detected

Latest commit: 3043df5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
hostd	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[alexfreska]

@iuri-gg hey thank you so much for finding this bug and your contribution!

The repo follows conventional commits, please prefix your commit with fix:.

Also, could you add a changeset so that your fix shows up in the next version's change log?

Locally run npx changeset select hostd, select patch change, and then add a description such as:

Fixed an issue where the base RPC and sector access price calculation was off by 10.

and then add the file to this commit.

[alexfreska]

@iuri-gg also while you are in this file, could you fix the comment, it says PRC instead of RPC 😄

[iuri-gg]

@alexfreska Thanks for the feedback. Hope I got it correctly this time 🤞

[alexfreska]

@alexfreska Thanks for the feedback. Hope I got it correctly this time 🤞

@iuri-gg thats perfect. I will run the CI and double check the values.

[alexfreska]

@iuri-gg looks like you need to update a few tests - they are currently checking for the incorrect values.
https://github.com/SiaFoundation/web/actions/runs/7533680654/job/20506787267?pr=466#step:7:124

To run the hostd tests:

nx test hostd

[iuri-gg]

dont know why package-lock.json got updated. is that expected? if I run npm install, it updates the package-lock.json

[alexfreska]

dont know why package-lock.json got updated. is that expected? if I run npm install, it updates the package-lock.json

yeah thats good, a previous PR likely missed an update

[alexfreska]

@iuri-gg merging, thank you! 🚀 Your change will show up in the release PR shortly: #465

Note: The CI failed because the package-lock change triggered a build across all projects, and external contributors do not have permission to build the website, which is the only project that failed, everything else passed!