Clement Sam
Clement Sam
Seems like @storjBuildBot is failing to identify Gerrit PRs that are related to this issue. PRs linked to this issue: - https://review.dev.storj.io/c/storj/storj/+/7932 (merged) - https://review.dev.storj.io/c/storj/storj/+/8012 (merged) - https://review.dev.storj.io/c/storj/storj/+/8042 (merged) -...
Yes we can but it should be in the pending release column on the project board since we have one last commit pending release (https://github.com/storj/storj/commit/31242f3820f2ae9b952fd8e84e1633b8b72b31b1) ... Thanks!
Hi @SideRocketeer0, looks like you've already run `storj-sim network setup`. You need to run `storj-sim network destroy` to destroy and clean up the network if it already exists before running...
And maybe add a contributing guide https://github.com/aws/aws-sdk-go#contributing?
Thanks @frob. Pinned it!
@Erikvv it is not only about the graph scale but all references using B*h (that including the header).
Currently, the _**total used space**_ displayed on the dashboard shows the total of _each daily byte*hour data_ in the current month. So for the screenshot you sent above, the 107.97GB*h...
> So that is option 5, only with unit `GB*day` instead of `GB*month`. I think we should still display `GB*day` explicitly else it is confusing. Makes sense.
https://review.dev.storj.io/c/storj/storj/+/8608
> I think this is because the month time range (link below) uses local time but everywhere else we use UTC. So my month starts and ends at 2h00 instead...