Release preparation v1.131

Alexey · June 23, 2025, 6:56am

Yes, you are right the autocorrection is a wonderful invention, always may make your day

ItsHass · July 2, 2025, 10:50pm

Hi ,
Is vetted status in API ?

Thanks

alpharabbit · July 2, 2025, 10:57pm

Yes, it can be found in /api/sno endpoint.

vettedAt	"2021-02-13T07:11:17.67771Z"

Roberto · July 4, 2025, 2:32pm

To my pleasant surprise the Quic is back up and running from version 1.31.7 on 64-bit ARM, Realtek RTD1296 4-core 1.4GHz
This is the situation as far as vetted is concerned

Eu seems normal, I live in Rome

ItsHass · July 4, 2025, 3:38pm

Is it only going to show in US date format ? - for UI might be good to be User friendly date, API to be DB ISO date

zip · July 4, 2025, 10:30pm

Might be based on the locale you have configured in the OS as I see a different format:

ItsHass · July 4, 2025, 10:44pm

Oh nice find - good of the developers if they took that into account

minerone · July 10, 2025, 7:38pm

I was running node on windows, on any version 1.131 and found frequent misconfigs on QUIC, so I finally rolled back to version 1.130.8.

Alexey · July 11, 2025, 4:19am

Hello @minerone,
Welcome to the forum!

You may try this workaround:

seanr22a · July 11, 2025, 3:11pm

Here is another one.

[EDIT]
Found two more nodes,

I still have several nodes not updated to v1.131.7 We will see if more unvetted nodes show up.

Alexey · July 12, 2025, 4:11am

Please add to the GitHub issue and subscribe to it

minerone · July 12, 2025, 7:45pm

I’ve tried it and double checked NAT forwarding, firewalls, and so on, but QUIC is still misconfigured. Version 1.130.8 is still the best for me.

arrogantrabbit · July 12, 2025, 9:32pm

I would update to the latest version and ignore quic

minerone · July 13, 2025, 1:13am

Is there any impact if we ignore the quick and what will be the long-term effects?

arrogantrabbit · July 13, 2025, 2:11am

Did you read this post linked above? Release preparation v1.131 - #15 by arrogantrabbit

Virtually no customers are using quic

However, every single customer attempts TFO. Therefore I would channel the efforts to verifying that TFO is working instead, It will be much more impactful. QUIC is only interesting to Google, as evidence by it incessant breakages in the upstream library.

If I was storj I would remove QUIC from dashboard and add TFO status instead.

github.com/storj/storj

Replace QUiC status in the dashboard with TFO status

opened 02:28AM - 13 Jul 25 UTC

arrogantrabbit

Enhancement

**Describe the feature or problem you'd like to solve** Virtually no customers …are using QUIC: https://forum.storj.io/t/quic-misconfiguration-in-v1-86-1/23610/25?u=arrogantrabbit QUIC connectivity is flaky and breaks from upstream library release to release A lot of SNO see red Misconfigured and waste a lot of time fixing it, with zero benefit to anyone. On the contrary, every single customer attempts to use TFO. https://forum.storj.io/t/please-enable-tcp-fastopen-on-your-storage-nodes/22886/183?u=arrogantrabbit Therefore, there is much more bang for buck for storj and SNO in spending time ensuring TFO is enabled. **Propose a Solution** 1. Add TFO status to dashboard. 1. Optionally, remove QUIC status from the dashboard, and then perhaps retire is and stop wasting development cycles maintaining it.

How to check if TFO is working: Please enable TCP fastopen on your storage nodes - #184 by arrogantrabbit

minerone · July 13, 2025, 2:33am

I agree with you, if QUIC often has problems it should be taken out of the dashboard because it is very annoying.