# Release preparation v1.108

**URL:** <https://forum.storj.io/t/release-preparation-v1-108/27006>\
**Category:** STORJLINGS\
**Created:** [July 8, 2024, 5:36pm UTC](https://forum.storj.io/t/release-preparation-v1-108/27006 "2024-07-08T17:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [July 9, 2024, 3:43am UTC](https://forum.storj.io/t/release-preparation-v1-108/27006/18 "2024-07-09T03:43:09Z")

</div>

> [@It seems that the new feature “save-state-resume GC filewalker” isn’t functioning as expected](https://forum.storj.io/t/it-seems-that-the-new-feature-save-state-resume-gc-filewalker-isn-t-functioning-as-expected/25874/47):
>
> retrieving the size and last modification time

This begs the question – why does the node need size and modification time for what’s supposed to be immutable objects?

And if the answer is “to show pretty pictures in the dashboard” – this only reinforces my earlier conviction that the dashboard must go. Satellite knows how much data is stored on the node. It knows the limit. Calculating sizes locally is counterproductive.

---

_[View the full topic](https://forum.storj.io/t/release-preparation-v1-108/27006)._