FrederikBaerentsen/BrickTracker
8
20
Fork 12
Code Issues 11 Pull Requests Actions Packages Projects 1 Releases 9 Wiki Activity

[Bug] Set doesn't seem to be updated after a refresh #100

New Issue
Closed
opened 2025-09-23 19:38:05 +02:00 by Ventje23 · 8 comments
Ventje23 commented 2025-09-23 19:38:05 +02:00
Copy Link
Copy Source

Hello,

As you know I updated to the new version, 1.2.4. In my wishlist I have two sets with 0 parts (see attachment).
When I do a refresh to see which sets need to be updated, those sets are there among all the others that could use a refresh.
After doing a refresh/update of one of those whishlist sets, the set the number of parts is still 0.
I assume that after a refresh/update of the set should contain parts > 0.
Based on this result I was wondering is there a way to see what gets updated during a refresh, so I can see/check if a set really gets updated.

Hello, As you know I updated to the new version, 1.2.4. In my wishlist I have two sets with 0 parts (see attachment). When I do a refresh to see which sets need to be updated, those sets are there among all the others that could use a refresh. After doing a refresh/update of one of those whishlist sets, the set the number of parts is still 0. I assume that after a refresh/update of the set should contain parts > 0. Based on this result I was wondering is there a way to see what gets updated during a refresh, so I can see/check if a set really gets updated.
Bricktracker-wishlist.missing parts.png
87 KiB
Bricktracker-wishlist.missing parts.png
FrederikBaerentsen commented 2025-09-23 19:55:32 +02:00
Owner
Copy Link
Copy Source

I have a hard time recreating this issue.

I see that some sets on my own wishlist have 0 parts, but I'm unsure if it happened with the 1.2.4 update.

I tried a new environment and did the following:

  1. Setup a new container with new data on 1.2.2
  2. Add things to wishlist
  3. Add sets
  4. Stop container
  5. Pull 1.2.4
  6. Start container with 1.24

This did not give me any sets with 0 parts.

I would be interested in seeing how this happened.

I have a hard time recreating this issue. I see that some sets on my own wishlist have 0 parts, but I'm unsure if it happened with the 1.2.4 update. I tried a new environment and did the following: 1. Setup a new container with new data on 1.2.2 2. Add things to wishlist 3. Add sets 4. Stop container 5. Pull 1.2.4 6. Start container with 1.24 This did not give me any sets with 0 parts. I would be interested in seeing how this happened.
FrederikBaerentsen added the Kind/Bug label 2025-09-23 19:55:35 +02:00
FrederikBaerentsen changed title from Set doesn't seem to be updated after a refresh to [Bug] Set doesn't seem to be updated after a refresh 2025-09-23 19:55:44 +02:00
Ventje23 commented 2025-09-23 22:12:32 +02:00
Author
Copy Link
Copy Source

Thank you for trying to figure out what's going on!

Maybe some sort of hiccup occured while adding a set to the wishlist. So it ended up without parts. Or maybe there weren't parts in bricklink (don't think that was the case tho). I have 2 sets with no parts so that is strnage too.
But if i refresh can I axpect the missing parts to be added? because it doesn't.
Would a copy of the database be an option? For debugging purposes?

Also. I have a situation like in the attachment: a set with 87 parts AND 87 missing pieces. Also tried to fresh this set, but still the same.

Thank you for trying to figure out what's going on! Maybe some sort of hiccup occured while adding a set to the wishlist. So it ended up without parts. Or maybe there weren't parts in bricklink (don't think that was the case tho). I have 2 sets with no parts so that is strnage too. But if i refresh can I axpect the missing parts to be added? because it doesn't. Would a copy of the database be an option? For debugging purposes? Also. I have a situation like in the attachment: a set with 87 parts AND 87 missing pieces. Also tried to fresh this set, but still the same.
Bricktracker-missing pieces.png
62 KiB
Bricktracker-missing pieces.png
FrederikBaerentsen commented 2025-09-26 14:03:08 +02:00
Owner
Copy Link
Copy Source

A database copy would be very helpful for debugging. Can you download a copy from your admin page and uploud it and share a link to it?

A database copy would be very helpful for debugging. Can you download a copy from your admin page and uploud it and share a link to it?
Ventje23 commented 2025-09-30 20:12:21 +02:00
Author
Copy Link
Copy Source

Hi,

sorry for the late reply. Been busy these last couple of days.
Will upload a db this weekend. I think i will remove most part of it except for the ones that seem to be weird.

Hi, sorry for the late reply. Been busy these last couple of days. Will upload a db this weekend. I think i will remove most part of it except for the ones that seem to be weird.
deadbattery commented 2025-10-19 22:09:26 +02:00
Copy Link
Copy Source

To piggy back on this topic, refreshing a set does not pull the current set inventory from Rebrickable and update accordingly. If a set's inventory is updated on Rebrickable (e.g. adding, removing, updating parts) and then a set refresh is initiated on BrickTracker, the set inventory does not change.

What I have been doing is adding a new copy of the set which will have the update set info and then manually setting the metadata to match the previous set and then deleting said old set from BrickTracker.

This is quite common for newly released sets as the inventory is refined and updated.

Keep up the great work!

To piggy back on this topic, refreshing a set does not pull the current set inventory from Rebrickable and update accordingly. If a set's inventory is updated on Rebrickable (e.g. adding, removing, updating parts) and then a set refresh is initiated on BrickTracker, the set inventory does not change. What I have been doing is adding a new copy of the set which will have the update set info and then manually setting the metadata to match the previous set and then deleting said old set from BrickTracker. This is quite common for newly released sets as the inventory is refined and updated. Keep up the great work!
FrederikBaerentsen commented 2025-12-22 17:55:39 +01:00
Owner
Copy Link
Copy Source

I see the issue now. I'm working on a fix for it.

I see the issue now. I'm working on a fix for it.
FrederikBaerentsen commented 2025-12-24 14:39:46 +01:00
Owner
Copy Link
Copy Source

I found the issue and it should be fixed for testing on tag pre-1.4. Changelog can be seen on the release/1.4 branch.

I found the issue and it should be fixed for testing on tag `pre-1.4`. Changelog can be seen on the [release/1.4 branch](https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/src/branch/release/1.4/CHANGELOG.md#14).
FrederikBaerentsen added this to the Version 1.4 milestone 2025-12-24 14:39:53 +01:00
FrederikBaerentsen added this to the General Improvements project 2025-12-24 14:39:59 +01:00
FrederikBaerentsen moved this to In Progress in General Improvements on 2025-12-24 14:40:33 +01:00
FrederikBaerentsen commented 2025-12-26 19:00:04 +01:00
Owner
Copy Link
Copy Source

Closing the issue. New issues or comments should be added to #127.

Closing the issue. New issues or comments should be added to #127.
FrederikBaerentsen moved this to Done in General Improvements on 2026-04-15 14:30:57 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Out of Scope
Request is out of scope
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No Label Kind/Bug
Milestone
No items
No Milestone Version 1.4
Projects
Clear projects
No project General Improvements
Assignees
Clear assignees
FrederikBaerentsen
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#100
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?