Skip to content

feat: add blob listing to space detail page#351

Merged
travis merged 3 commits intomainfrom
fix/blobs-listing
Aug 12, 2025
Merged

feat: add blob listing to space detail page#351
travis merged 3 commits intomainfrom
fix/blobs-listing

Conversation

@travis
Copy link
Copy Markdown
Contributor

@travis travis commented Aug 8, 2025

I was trying to track down some issues with deletions in my space yesterday and got far enough into this that I figured I'd polish it off.

This introduces a blob listing page and a separate "blob detail" page that will make it easier for people to track down blobs that aren't part of any particular upload.

Future work:

  1. We should make it possible to delete blobs from this page
  2. We should add something that filters the list of blobs down to only blobs that don't appear in any existing uploads
Screenshot 2025-08-08 at 1 13 33 PM Screenshot 2025-08-12 at 11 39 43 AM

I was trying to track down some issues with deletions in my space yesterday and got far enough into this that I figured I'd polish it off.

This introduces a blob listing page and a separate "blob detail" page that will make it easier for people to track down blobs that aren't part of any particular upload.

Future work:

1) We should make it possible to delete blobs from this page
2) We should add something that filters the list of blobs down to only blobs that don't appear in any existing uploads
@travis travis requested a review from a team August 8, 2025 20:28
@travis travis temporarily deployed to preview-351/merge August 8, 2025 20:28 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Aug 8, 2025

@travis travis temporarily deployed to preview-351/merge August 8, 2025 20:47 — with GitHub Actions Inactive
@BravoNatalie
Copy link
Copy Markdown
Contributor

If this is meant to help with debugging and provide a extended view of what the space is storing, I think it would be helpful to also label these blobs. For example, if it’s a shard, we could link it to the corresponding upload, if it’s an index or other type of data, we could indicate that as well. It would also be great to have the ability to search the list. Of course, this don't need to be done in this PR, just wanted to open this discussion

@travis
Copy link
Copy Markdown
Contributor Author

travis commented Aug 11, 2025

Yea agree! Some of that (particularly figuring out which upload a blob/shard is in) is fairly IO intensive (since we'd need to load the entire list of uploads and shards and it could be very large) and I think a separate page that loads the necessary data on command would be best. This would be a super useful tool, and is ultimately the thing this PR is trying to set up for, but yea I don't think it makes sense to get in right this second.

Copy link
Copy Markdown
Member

@alanshaw alanshaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️ I love this, thank you for implementing.

- get rid of blob detail page as it's confusing
- show size on listing page
@travis travis deployed to preview-351/merge August 12, 2025 18:40 — with GitHub Actions Active
@travis
Copy link
Copy Markdown
Contributor Author

travis commented Aug 12, 2025

thanks @alanshaw ! I think I've addressed all your feedback

@travis travis merged commit d14484e into main Aug 12, 2025
5 checks passed
fforbeck pushed a commit that referenced this pull request Aug 14, 2025
🤖 I have created a release *beep* *boop*
---


##
[2.3.0](console-v2.2.1...console-v2.3.0)
(2025-08-14)


### Features

* add blob listing to space detail page
([#351](#351))
([d14484e](d14484e))
* **console:** plan verification before encryption/decryption operations
([#354](#354))
([fe77ef0](fe77ef0))


### Fixes

* **console:** trigger console app release
([5deb02b](5deb02b))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants