Adding figures after adding a set just duplicates the last added set. #150

New Issue

2026-04-17T08:06:59+02:00

commenter commented

2026-04-17 08:06:59 +02:00

Repro:
In 1.4.0-
Add single new set to the DB via the "add" menu, in my case I was also assigning storage and purchase data for individual collectable minifigures.
Without refreshing the page or navigating away, add a individual minifigure (fig-XXXXX). Instead of adding the minifigure to the database, the previously added set has a duplicate added.

Workaround:
Refresh the add page, navigate away and return, or open a new tab when adding minifigures if sets were already added.

Repro: In 1.4.0- Add single new set to the DB via the "add" menu, in my case I was also assigning storage and purchase data for individual collectable minifigures. Without refreshing the page or navigating away, add a individual minifigure (fig-XXXXX). Instead of adding the minifigure to the database, the previously added set has a duplicate added. Workaround: Refresh the add page, navigate away and return, or open a new tab when adding minifigures if sets were already added.

FrederikBaerentsen added the Kind/Bug label 2026-04-17 09:49:56 +02:00

FrederikBaerentsen added reference release/1.4

2026-04-17 09:55:02 +02:00

FrederikBaerentsen referenced this issue from a commit

2026-04-18 14:03:35 +02:00

fix(add): replace two-socket approach with single BrickSetSocket for minifigure error where duplicate sets were added (see #150)

FrederikBaerentsen commented

2026-04-18 14:25:35 +02:00

Good catch and workaround. Turns out the add page was spinning up a second socket connection just for minifigures, which conflicted with the existing set socket. Didn't need to do that at all since the server already handles fig- routing automatically. Removed the whole thing and it should work seamlessly now without needing to refresh between adds. I generally only add one thing at a time, or use bulk-add, so I never saw this issue happening!

The fixes are available now in the pre-1.4.1 Docker tag if you want to test. Will be pushed to 1.4.1 and latest once a couple more things are sorted.

Good catch and workaround. Turns out the add page was spinning up a second socket connection just for minifigures, which conflicted with the existing set socket. Didn't need to do that at all since the server already handles `fig-` routing automatically. Removed the whole thing and it should work seamlessly now without needing to refresh between adds. I generally only add one thing at a time, or use bulk-add, so I never saw this issue happening! The fixes are available now in the `pre-1.4.1` Docker tag if you want to test. Will be pushed to `1.4.1` and `latest` once a couple more things are sorted.

FrederikBaerentsen closed this issue

2026-04-18 14:25:35 +02:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#150