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

[Bug] - Sets remain in "set refresh" screen, with bricklink issues, even after refreshing #109

New Issue
Closed
opened 2025-10-09 16:18:32 +02:00 by cainmp · 5 comments
cainmp commented 2025-10-09 16:18:32 +02:00
Copy Link
Copy Source

I have 16 sets that are showing as "needing refresh", despite refreshing each one of them. They show somewhere between 3 and 9 bricklink issues.

I have 16 sets that are showing as "needing refresh", despite refreshing each one of them. They show somewhere between 3 and 9 bricklink issues.
Screenshot 2025-10-09 at 10.18.18 AM.png
442 KiB
Screenshot 2025-10-09 at 10.18.18 AM.png
FrederikBaerentsen commented 2025-10-09 17:37:28 +02:00
Owner
Copy Link
Copy Source

Which docker version are you using ?

Could you share a copy of your database? I can't replicate this issue. I tried:

  1. Create a new instance using :1.2.2.
  2. Add 76408-1 and 71429-1
  3. Stop the container
  4. Change version to :1.2.4
  5. Start the container
  6. Upgrade db to V17
  7. Refresh both sets

Both sets now show no issues and no need to refresh again.

Alternatively set BK_DEBUG=true and see what the Docker logs says.

Which docker version are you using ? Could you share a copy of your database? I can't replicate this issue. I tried: 1. Create a new instance using `:1.2.2`. 2. Add 76408-1 and 71429-1 3. Stop the container 4. Change version to `:1.2.4` 5. Start the container 6. Upgrade db to V17 7. Refresh both sets Both sets now show no issues and no need to refresh again. Alternatively set `BK_DEBUG=true` and see what the Docker logs says.
FrederikBaerentsen added the Kind/Bug label 2025-10-09 17:37:33 +02:00
cainmp commented 2025-10-09 21:24:26 +02:00
Author
Copy Link
Copy Source

Docker version 28.5.1

Docker version 28.5.1
cainmp_dbBackup_v17.zip
752 KiB
FrederikBaerentsen commented 2025-10-09 21:27:09 +02:00
Owner
Copy Link
Copy Source

@cainmp sorry I meant what version of BrickTracker are you using ? What container tag?

@cainmp sorry I meant what version of BrickTracker are you using ? What container tag?
cainmp commented 2025-10-09 21:54:45 +02:00
Author
Copy Link
Copy Source

all good.
"image: gitea.baerentsen.space/frederikbaerentsen/bricktracker:latest"
Currently showing as 1.2.4

all good. "image: gitea.baerentsen.space/frederikbaerentsen/bricktracker:latest" Currently showing as 1.2.4
FrederikBaerentsen added this to the General Improvements project 2025-10-09 22:38:13 +02:00
FrederikBaerentsen commented 2025-12-21 00:30:54 +01:00
Owner
Copy Link
Copy Source

I've finally been able to analyze your database.

The "BrickLink Issues" that won't go away after refreshing is not a bug per se. Rebrickable's API doesn't provide BrickLink mapping data for all LEGO parts. In the your database, 11 out of 4,109 parts are missing BrickLink data. When you refresh a set containing these parts, Rebrickable returns NULL for the BrickLink fields, and they stay NULL.

Why it happens:

  • Some LEGO parts don't have BrickLink equivalents
  • Some mappings haven't been added to Rebrickable's database
  • Refreshing re-downloads the same incomplete data

For now, this is just how it is. I will try and see if i can find a way to avoid this or somehow change how the issues are counted.

I'll close the issue for now. Feel free to re-open, if you have any questions.

I've finally been able to analyze your database. The "BrickLink Issues" that won't go away after refreshing is not a bug per se. Rebrickable's API doesn't provide BrickLink mapping data for all LEGO parts. In the your database, 11 out of 4,109 parts are missing BrickLink data. When you refresh a set containing these parts, Rebrickable returns NULL for the BrickLink fields, and they stay NULL. Why it happens: - Some LEGO parts don't have BrickLink equivalents - Some mappings haven't been added to Rebrickable's database - Refreshing re-downloads the same incomplete data For now, this is just how it is. I will try and see if i can find a way to avoid this or somehow change how the issues are counted. I'll close the issue for now. Feel free to re-open, if you have any questions.
👍 1
FrederikBaerentsen added this to the Version 1.4 milestone 2025-12-21 00:31:12 +01:00
FrederikBaerentsen moved this to To Do in General Improvements on 2025-12-24 14:40:30 +01:00
FrederikBaerentsen moved this to Done in General Improvements on 2026-04-15 14:30:54 +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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#109
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?