Gleipnir/nidus-sync
4
0
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

Address Compliance bug #1

New issue
Closed
opened 2026-05-13 23:31:17 +00:00 by tzipporahribble · 4 comments
tzipporahribble commented 2026-05-13 23:31:17 +00:00
Member
Copy link

In staging Compliance when I add the 1313 Disneyland Drive, Anaheim, California 92802, United States of America address I can’t continue to submit the report. The continue button doesn’t work and looks as if it’s loading.

In staging Compliance when I add the 1313 Disneyland Drive, Anaheim, California 92802, United States of America address I can’t continue to submit the report. The continue button doesn’t work and looks as if it’s loading.
eliribble commented 2026-05-13 23:32:21 +00:00
Owner
Copy link

Log entries at the same time:

May 13 23:09:21 nocix-amd-legacy-quadcore nidus-sync[652274]: 11:09PM ERR failed to insert stadia request error="collect row: ERROR: duplicate key value violates unique constraint "api_request_request_key" (SQLSTATE 23505)"
May 13 23:09:24 nocix-amd-legacy-quadcore nidus-sync[652274]: 11:09PM ERR failed to insert stadia request error="collect row: ERROR: duplicate key value violates unique constraint "api_request_request_key" (SQLSTATE 23505)"

Log entries at the same time: > May 13 23:09:21 nocix-amd-legacy-quadcore nidus-sync[652274]: 11:09PM ERR failed to insert stadia request error="collect row: ERROR: duplicate key value violates unique constraint \"api_request_request_key\" (SQLSTATE 23505)" > May 13 23:09:24 nocix-amd-legacy-quadcore nidus-sync[652274]: 11:09PM ERR failed to insert stadia request error="collect row: ERROR: duplicate key value violates unique constraint \"api_request_request_key\" (SQLSTATE 23505)"
😕 1
eliribble commented 2026-05-21 15:50:57 +00:00
Owner
Copy link

I think this got fixed in e93c88003e. It's in staging now.

I think this got fixed in e93c88003eeeed160212ab00cc836cda41e014c3. It's in staging now.
tzipporahribble was assigned by eliribble 2026-05-21 15:51:05 +00:00
eliribble commented 2026-05-21 15:51:24 +00:00
Owner
Copy link

@tzipporahribble please test in staging when you have a chance.

@tzipporahribble please test in staging when you have a chance.
tzipporahribble commented 2026-05-23 22:43:51 +00:00
Author
Member
Copy link

I can't test this bug until this ( #21 ) Is solved.

I can't test this bug until this ( https://source.gleipnir.technology/Gleipnir/nidus-sync/issues/21 ) Is solved.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.0.14
0.0.13
0.0.12
0.0.11
0.0.10
0.0.9
0.0.8
0.0.7
v0.0.6
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
tzipporahribble
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Gleipnir/nidus-sync#1
No description provided.
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?