Release preparation v1.131

New release candidate is already deployed on QA Satellite

Changelog

General

  • 501755a go.mod: bump storj.io/common
  • 3921bc6 cmd/tools/segment-verify: don’t stop segments csv processing too soon
  • ae0b658 cmd/jobq: add GCP profiling support
  • 7f80e40 ci: increase timeouts
  • 20b9ee1 go.mod: bump common and uplink
  • 2588271 cmd/write-hashtbl: command to write out a hashtbl from log files
  • d6d5b3f dev: use local-first lint configuration (with go tool)
  • dba95ec all: fix deferInLoop issues
  • 547e0f8 satelllite/metainfo: allow arbitrary prefixes in ListObjects
  • 01ef057 ci: use go-critic to check for defers in loop
  • 1e9a5bf release v1.131.1-rc

Satellite

  • 4fffa2c web/satellite: remove references to no minimum charge
  • 5cc4b10 satellite/satellitedb: another attempt to fix flaky TestGetProjectTotalByPartnerAndPlacement
  • 06b5f7e satellite/{payments,console}: simplify minimum charge config
  • 92bee81 satellite/web: add minimum charge banner
  • 7bd2ba5 web/satellite: updates for estimated charges
  • 0286505 satellite/web: specify minimum charge date time zone
  • dda73bc web/satellite: add minimum charge notice to add tokens step
  • 4583961 satellite/satellitedb: project accounting, pause chores
  • 4b306fb satellite/accounting: move tests to the correct package
  • ef0635b satellite/satellitedb: account for completely deleted buckets
  • dfe8e30 satellite/jobq: get rid of funnel goroutine
  • 4753289 satellite/metainfo: update tests for uplink changes
  • a6041c5 satellite/accounting: fix failing TestGetBucketTotals
  • f949566 web/satellite: open minimum charge link in new tab
  • 20f54de satellite/metabase: Add error message for context
  • 0d9f506 web/satellite: Fix typo in AccountDeleteDialog (#7494)
  • ca0d447 satellite/satellitedb: use partitioned update query for DeleteTalliesBefore
  • 5434f1b satellite/orders: Enhance method documentation
  • dbf1da7 satellite/accounting/tally: add monkit task to Purge method
  • 4dfcbcb web/{satellite, storagenode}: Add README & drop trailing spaces
  • 97c6527 satellite/satellitedb/projectaccounting: optimize non-empty bucket search for spanner
  • 265962f cmd/satellite: Replace user-accounts set-status cmd
  • 2904ebf satellite/metabase: use BufferWrite for DeleteBucket
  • cbeb28a satellite/metainfo: add bitshift-noise tracker
  • 62df627 satellite/audit: improve monitoring for not found pieces during audit
  • d13fe6a satellite/admin: fix flaky TestProjectDelete_withUsagePreviousMonthCharged
  • 86e4709 satellite/metabase: Rephrase stale doc comment
  • 76efeb4 satellite/payments: Fix project-based invoicing
  • 7a8f2c6 web/satellite: update minimum fee texts
  • 4690e04 satellite/satellitedb: add tags column to bucket_metainfos
  • 0df6acd {cmd|satellite}: Split get segment for Audit & Repair
  • debd0a5 satellite/metabase: account for deleted rows while deleting a bucket
  • c17d36b satellite/metabase: Add get segment for Audit & Repair to adapter
  • 390ac59 satellite/metabase: Use Spanner ReadRow for GetSegmentByPosition
  • bcd019e {cmd|satellite}: Remove plain size of segment for Audit & Repair
  • 1550db3 {cmd|satellite}: Remove plain offset of segment for Audit & Repair
  • 05f8169 {cmd|satellite}: Remove inline data of segment for Audit & Repair
  • 29d5fbf satellite/{console,payments}: account for cost threshold in account delete
  • f9d4398 satellite/metabase: add encrypted_etag column
  • f62c346 satellite/metabase: add EncryptedETag field
  • f49ca19 satellite/metabase: add EncryptedETag to update metadata
  • b1f967e satellite/metabase: add EncryptedETag to object creation
  • 272ee9b satellite/metabase: add EncryptedETag to accounting
  • de74aa0 satellite/metabase: add EncryptedETag support for get object
  • 3b99561 satellite/metabase: add EncryptedETag for deletion
  • 559d107 satellite/metabase: add EncryptedETag to listing
  • a5e301c satellite/metabase: add EncryptedETag to precommit
  • 5de0930 satellite/metabase: add EncryptedETag in move and copy
  • 0b94544 satellite/payments: do not apply minimum charge for empty invoices
  • bd63ccc satellite/{metabase,metainfo}: make FinishMove and FinishCopy naming consistent with db
  • 8d7995c satellite/payments: updates for minimum charge invoicing
  • c2e12fc satellite/jobq: get stat from repair checker

Storagenode

  • 49cbc27 storagenode: add identity binary to modular storagenode image
  • 249cc3f storagenode/piecestore: configurable order/limit signature checking
  • eaaee83 {storagenode,web/storagenode}: Expose vetted time
  • 2907554 storagenode/piecestore: adjust error handling of upload/download
  • d516adf storagenode/db: make the db_stat metric opt-in
  • ffbd18b storagenode/hashstore: compaction only waits for flush
  • 79614f5 storagenode/hashstore: optionally fsync every write
  • e68cad6 storagenode/hashstore: add test for crash scenarios
  • fb8e948 storagenode/hashstore: fix potential log corruption from rewrite

Test

Uplink

  • 39af13d cmd/uplink{/internal}: move uplink CLI tests to separate package
  • 413d761 cmd/uplink{/external}: show free tier expiration of credentials
4 Likes

Very cool! Not very applicable to me as of right now, but I do think it will take the load of some of the questions that the forum gets. :slight_smile:

I am just wondering if users now will be going to ask why they are not vetted.
I am wondering if “vetting” is the better term to make clear this is something in progress.

Having a percentage shown for vetting state would be nice.

Ha-ha )

not only EU1

4 Likes

I’m having exactly the same problem on one node - showing vetted between April and June 2024 on all sats but the EU.
This node is getting almost no EU ingress despite being in the Europe, as was mentioned here: Unusually low EU ingress - Node Operators - Storj Community Forum (official).
The node apparently hasn’t been vetted on EU satellite despite being 16 months old now.
Can someone please look into this?

1 Like

What the script of BS sais?

That is the thing.
As per the script it looks to be vetted, but I think BS is only looking at the amount of audits and if it is 100, the node is considered vetted.
But maybe that isn’t really the way it works and satellite has to mark the node as vetted at some point.
And it really looks like this node still hasn’t been vetted on EU1 and that is the reason it receives almost no EU1 data.
I have other nodes and none of them are experiencing this low EU ingress and all of them are showing vetted date next to EU1 satellite. So I don’t think this is an issue with representing the vetted data in 1.131, but it really looks to be a problem with node not being vetted on this specific sat after 16 months for some reason.
And it looks like there might be more nodes having the exact same problem.

Or there is a bug, @ifraixedes could you please take a look?

I imagine the saltellite keeps the vetting records, because it sends the audits. Maybe if an audit was missed by the node, the satellite considers it unvetted, even though the node responded to 100+ audits? Just speculating…

@Alexey create a ticket in storj repo, please.

This should be scheduled during future spring plannings.

1 Like

My windows nodes showing QUIC misconfigured after upgrade to v1.131. Nothing else changed from my side. :thinking:

Try the “specify binding IP explicitly” workaround.
QUIC library in go seems to be utter garbage is unstable crap can benefit from improvement .

1 Like

Explicit binding did not help. I wonder if it is worth to spend time on solving this issue? Is there anything using QUIC?

Nope:

2 Likes
1 Like

All windows nodes showing QUIC OK now. I have no idea what happened, maybe storj solved the problem at satellite side.


This does not look right. One satellite not vetted after 12 months but still receiving traffic. Earnings calculator shows it is vetted

You may subscribe to the issue above, or send a pull request with a fix, we will be happy to review it and merge.

He means PULL request :slight_smile: :hot_beverage: :teacup_without_handle:

3 Likes