# Release preparation v1.104 **URL:** \ **Category:** STORJLINGS\ **Created:** [May 13, 2024, 2:21pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190 "2024-05-13T14:21:39Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Andrii](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/andrii/32/65_2.png) [@Andrii](https://forum.storj.io/u/Andrii)\ **Post date:** [May 13, 2024, 2:21pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/1 "2024-05-13T14:21:39Z")
New release candidate is already deployed on [QA Satellite](https://satellite.qa.storj.io/) # Changelog ### General - [9f7bdbe](https://github.com/storj/storj/commit/9f7bdbe) all: drop old build constraints - [ebac6ce](https://github.com/storj/storj/commit/ebac6ce) go.mod: bump dependencies (common) - [71c0c2d](https://github.com/storj/storj/commit/71c0c2d) shared/{dbutil|migrate|tagsql}: import db related packages from common - [7dfc648](https://github.com/storj/storj/commit/7dfc648) {versioncontrol,private/version}: remove support for old semver - [e725221](https://github.com/storj/storj/commit/e725221) go.mod: use [GitHub - storj/exp-spanner: Fork of spanner client from https://github.com/googleapis/google-cloud-go/ for fixes.](http://github.com/storj/exp-spanner) fork - [73c658f](https://github.com/storj/storj/commit/73c658f) blobstore: remove Chmod - [3b6cce9](https://github.com/storj/storj/commit/3b6cce9) shared/dbutil: spannerutil.Int utility function - [e018de0](https://github.com/storj/storj/commit/e018de0) all: fix `errs.New(fmt.Sprintf(...))` issues - [4d66b76](https://github.com/storj/storj/commit/4d66b76) Jenkinsfile.{public,verify}: Temporarily disable satellite UI tests - [2b13d98](https://github.com/storj/storj/commit/2b13d98) blobstore/filestore: cache Info for a second ### Satellite - [505c110](https://github.com/storj/storj/commit/505c110) satellite/overlay: update benchmark to have node tags - [49663eb](https://github.com/storj/storj/commit/49663eb) satellite/gc/bloomfilter: update tests to use both observers - [8f5ac63](https://github.com/storj/storj/commit/8f5ac63) satellite/db: added passphrase\_enc and path\_encryption columns to projects table - [4a45ffb](https://github.com/storj/storj/commit/4a45ffb) satellite/db: add role column for project\_members table - [aa573cb](https://github.com/storj/storj/commit/aa573cb) satellite/{console, web}: set length restrictions on onboarding inputs - [a5263ac](https://github.com/storj/storj/commit/a5263ac) satellite/metabase: move GetTableStats implementation to the adapter level - [e3b1ca8](https://github.com/storj/storj/commit/e3b1ca8) satellite/metabase: accept spanner as a first class db implementation - [1e5eff4](https://github.com/storj/storj/commit/1e5eff4) satellite/{payments,console}: add endpoint to manage user billing address - [dcd3ccc](https://github.com/storj/storj/commit/dcd3ccc) satellite/console: remove analytics rate limit - [a2db5e7](https://github.com/storj/storj/commit/a2db5e7) satellite/console: allow only 6-digit code for account activation - [532942c](https://github.com/storj/storj/commit/532942c) satellite/metabase: abstract away transaction formation - [c23ba19](https://github.com/storj/storj/commit/c23ba19) satellite/contact: accept self signed tags from storagenodes - [60a01eb](https://github.com/storj/storj/commit/60a01eb) web/satellite: add UI to manage billing address - [655a7bd](https://github.com/storj/storj/commit/655a7bd) satellite/{payments,console,stripe}: add endpoint to manage user tax information - [9802535](https://github.com/storj/storj/commit/9802535) web/satellite: add UI to manage tax IDs - [0aad164](https://github.com/storj/storj/commit/0aad164) satellite/metabase: spanner encoding/decoding for encryptionParameters - [31a9ca9](https://github.com/storj/storj/commit/31a9ca9) satellite/metabase: (Encode|Decode)Spanner for ObjectStatus - [f04a3c5](https://github.com/storj/storj/commit/f04a3c5) satellite/metabase: use spannerutil.Int in TestingGetAllSegments - [d230637](https://github.com/storj/storj/commit/d230637) satellite/metabase: split out PendingObjectExists() for db adapters - [d7f7d1c](https://github.com/storj/storj/commit/d7f7d1c) satellite/metabase: split out CommitSegment for db adapters - [094d27b](https://github.com/storj/storj/commit/094d27b) satellite/metabase: split out CommitInlineSegment for db adapters - [6d475df](https://github.com/storj/storj/commit/6d475df) satellite/metabase: split out TestingGetAllObjects for db adapters - [c5591ed](https://github.com/storj/storj/commit/c5591ed) satellite/metabase: TestingGetAllObjects for spanner - [3ef1143](https://github.com/storj/storj/commit/3ef1143) satellite/{console, db}: add functionality to update project member role - [bb35101](https://github.com/storj/storj/commit/bb35101) satellite/console: added endpoint to update project member’s role - [034770a](https://github.com/storj/storj/commit/034770a) web/satellite: added functionality to update project member’s role - [c689688](https://github.com/storj/storj/commit/c689688) satellite/metabase: (Encode|Decode)Spanner for ObjectKey - [860bbdd](https://github.com/storj/storj/commit/860bbdd) satellite/console: restrict deletion of non-owned API keys to members without Admin role - [a224d4a](https://github.com/storj/storj/commit/a224d4a) satellite/overlay: increase free space buffer to 5GB (#6948) - [37e3715](https://github.com/storj/storj/commit/37e3715) web/satellite: ui/ux updates (#6947) - [a4296c1](https://github.com/storj/storj/commit/a4296c1) satellite/console: Add rate limiting to api key handlers - [712add7](https://github.com/storj/storj/commit/712add7) satellite/{console,web}: add config for billing information tab - [44c8bd7](https://github.com/storj/storj/commit/44c8bd7) web/satellite: remove dynamic tax id length restriction ### Storagenode - [448d663](https://github.com/storj/storj/commit/448d663) storagenode: fix disk monitoring for FreeBSD - [aa84cb6](https://github.com/storj/storj/commit/aa84cb6) storagenodedb: buffer up piece expirations - [b9fe1e7](https://github.com/storj/storj/commit/b9fe1e7) storagenode/orders: Remove unnecessary V0 order version checks - [f00bf1e](https://github.com/storj/storj/commit/f00bf1e) storagenode/orders: Open “writable unsent orders file” less - [016090d](https://github.com/storj/storj/commit/016090d) storagenode/piecestore: fix monitoring cardinality issue - [ed819e9](https://github.com/storj/storj/commit/ed819e9) storagenode/blobstore: remove preallocate size - [491c019](https://github.com/storj/storj/commit/491c019) storagenode/blobstore/filestore: by default turn off fsync - [962ff04](https://github.com/storj/storj/commit/962ff04) storagenode: add bandwidth DB write cache - [4d93a3c](https://github.com/storj/storj/commit/4d93a3c) storagenode/piecestore: add bandwidth only when settling orders - [8c42f43](https://github.com/storj/storj/commit/8c42f43) cmd/storagenode: fix flaky test - [5bf9a60](https://github.com/storj/storj/commit/5bf9a60) storagenode/blobstore: remove some dead code - [d68abcf](https://github.com/storj/storj/commit/d68abcf) storagenode/pieces: update used space on trash-lazyfilewalker completion ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [May 13, 2024, 2:29pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/2 "2024-05-13T14:29:13Z")
> [@Andrii](#): > > [d68abcf](https://github.com/storj/storj/commit/d68abcf) storagenode/pieces: update used space on trash-lazyfilewalker completion After installing the new storage node version it might be a good time to run the used space calculation one time to correct the incorrect trash size this bug caused. After that you should be able to turn off the used space calculation again. ---
**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\ **Post date:** [May 13, 2024, 2:30pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/3 "2024-05-13T14:30:54Z")
Are there any plans to skip 1.103 and go straight to this? I run it on most of my nodes and don’t see anything that would suggest that it can’t be brought into production since it contains important fixes. ---
**Author:** ![jtolio](https://storj.bcdn.literatehosting.com/letter_avatar/jtolio/32/6_22734026db12803ebb3e059622ac3534.png) [@jtolio](https://forum.storj.io/u/jtolio)\ **Post date:** [May 13, 2024, 2:31pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/4 "2024-05-13T14:31:44Z")
We are skipping v1.103 for nodes ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [May 13, 2024, 2:40pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/5 "2024-05-13T14:40:22Z")
Is there any one time start command? that cold just start this function one time? ---
**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\ **Post date:** [May 13, 2024, 2:45pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/6 "2024-05-13T14:45:01Z")
What I did was stop the node, flip storage2.piece-scan-on-startup to true, start the node and flip storage2.piece-scan-on-startup to false again. ---
**Author:** ![agente](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/agente/32/1137_2.png) [@agente](https://forum.storj.io/u/agente)\ **Post date:** [May 13, 2024, 5:13pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/7 "2024-05-13T17:13:35Z")
> [@Vadim](#): > > Is there any one time start command? that cold just start this function one time? It would be great. I asked many times for something integrated. In the meanwhile I asked to chatgpt to write for me a script that restart containers changing false in true and come back after restart. I’m lazy ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [May 13, 2024, 7:44pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/8 "2024-05-13T19:44:51Z")
does the lazy filewalker also do this job just much longer? ---
**Author:** ![LrrrAc](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/lrrrac/32/8809_2.png) [@LrrrAc](https://forum.storj.io/u/LrrrAc)\ **Post date:** [May 13, 2024, 8:00pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/9 "2024-05-13T20:00:32Z")
How well did it write it? How much editing did it require afterward? ---
**Author:** ![agente](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/agente/32/1137_2.png) [@agente](https://forum.storj.io/u/agente)\ **Post date:** [May 13, 2024, 8:15pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/10 "2024-05-13T20:15:50Z")
it’s easy and no editing. It’s just a sed command ( sed -i ‘s/storage2.piece-scan-on-startup: false/storage2.piece-scan-on-startup: true/’) after stop and another for start. let gpt do all dirty job ---
**Author:** ![Dr.Ko](https://storj.bcdn.literatehosting.com/letter_avatar/dr.ko/32/6_22734026db12803ebb3e059622ac3534.png) [@Dr.Ko](https://forum.storj.io/u/Dr.Ko)\ **Post date:** [May 14, 2024, 2:17am UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/11 "2024-05-14T02:17:50Z")
![Screenshot_17](https://storj-s3.bcdn.literatehosting.net/original/3X/4/6/469c12cc9cc7cc2af9fbc569060aa0bfaa9c0c71.png) ![Screenshot_18](https://storj-s3.bcdn.literatehosting.net/original/3X/8/a/8a6af60843dd25e27a5035f3281d0f5c33cae844.png) I don’t know if it’s just me, but sending and receiving is the same as usual, but the graph display has changed as if it’s coming in all at once. (After update 1.104.1) There doesn’t seem to be any particular problem, so I’m leaving it alone. ---
**Author:** ![Ambifacient](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/ambifacient/32/7815_2.png) [@Ambifacient](https://forum.storj.io/u/Ambifacient)\ **Post date:** [May 14, 2024, 3:48am UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/12 "2024-05-14T03:48:19Z")
If you’re using the API, v.1.104 also introduces caching bandwidth writes to DB, and the API does not currently read from the cached DB. ---
**Author:** ![Dr.Ko](https://storj.bcdn.literatehosting.com/letter_avatar/dr.ko/32/6_22734026db12803ebb3e059622ac3534.png) [@Dr.Ko](https://forum.storj.io/u/Dr.Ko)\ **Post date:** [May 14, 2024, 4:05am UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/13 "2024-05-14T04:05:43Z")
I don’t know how to solve it, but it doesn’t seem to be a problem with the storage, so I’ll leave it alone and refer to the ‘storj\_exporter’ forum post. Thank you. ---
**Author:** ![LrrrAc](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/lrrrac/32/8809_2.png) [@LrrrAc](https://forum.storj.io/u/LrrrAc)\ **Post date:** [May 16, 2024, 3:36pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/14 "2024-05-16T15:36:20Z")
> [@Ambifacient](#): > > If you’re using the API, v.1.104 also introduces caching bandwidth writes to DB, and the API does not currently read from the cached DB. Is there any plan to change this so 1.104.x and onward pulls from the cached DB? (I know Im free to submit a PR myself) ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [May 16, 2024, 3:44pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/15 "2024-05-16T15:44:06Z")
I didn’t see a ticket like that. → not planed ---
**Author:** ![LrrrAc](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/lrrrac/32/8809_2.png) [@LrrrAc](https://forum.storj.io/u/LrrrAc)\ **Post date:** [May 16, 2024, 3:47pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/16 "2024-05-16T15:47:22Z")
Is this fixed by using the metrics api on the nodes themselves? Ive attempted to get this working, but cant seem to. So im stuck on the third-party exporter for now. ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [May 16, 2024, 3:56pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/17 "2024-05-16T15:56:47Z")
Yea metrics endpoint works fine. If you have already a grafana instance running it shouldn’t be hard to use the metrics endpoint. ---
**Author:** ![LrrrAc](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/lrrrac/32/8809_2.png) [@LrrrAc](https://forum.storj.io/u/LrrrAc)\ **Post date:** [May 16, 2024, 4:04pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/18 "2024-05-16T16:04:52Z")
Does it still go thru prometheus? Ive added the debug.addr: “:5999” and point prometheus to the node, but dont get any output on grafana. My prometheus scraper: ` - job_name: storj0` `metrics_path: /metrics` `static_configs:` ` - targets: ["172.20.0.80:5999"]` ` labels:` ` instance: "storj0"` ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [May 16, 2024, 5:05pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/19 "2024-05-16T17:05:06Z")
> [@LrrrAc](#): > > Does it still go thru prometheus? I think by default the storage node will open a random port. Make sure you set `debug.addr: ":5999"` ---
**Author:** ![LrrrAc](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/lrrrac/32/8809_2.png) [@LrrrAc](https://forum.storj.io/u/LrrrAc)\ **Post date:** [May 16, 2024, 5:12pm UTC](https://forum.storj.io/t/release-preparation-v1-104/26190/20 "2024-05-16T17:12:04Z")
I have and can curl from the port I set. There’s potential the issue is my docker networking. Update: I can successfully ping the metrics endpoint in a storj node from within my prometheus container. Now its prolly a configuration issue. weeeee Could it be I have the wrong log level or something? [Next page](https://forum.storj.io/t/release-preparation-v1-104/26190.md?page=2)