Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Triggering builds in quick succession results in duplicated IDs #108

Closed
Skarlso opened this issue Sep 21, 2018 · 5 comments
Closed

Triggering builds in quick succession results in duplicated IDs #108

Skarlso opened this issue Sep 21, 2018 · 5 comments
Assignees
@Skarlso
Labels
bug

Comments

@Skarlso
Copy link
Member

Skarlso commented Sep 21, 2018

screen shot 2018-09-21 at 11 46 54 am
@Skarlso Skarlso added the bug label Sep 21, 2018
@michelvocks
Copy link
Member

Uhm. That's pretty bad. The IDs are generated by boltDB as far as I can remember. I will check that.
Thanks for the report @Skarlso 🤗

@Skarlso
Copy link
Member Author

Skarlso commented Sep 23, 2018

@michelvocks No probs. I have a hunch that it might be only on the front-end. I didn't have the time to investigate deeper yet. That would be the best possible outcome... :) If it's deeper that's shait. We'd have to implement locking. :/

@Skarlso
Copy link
Member Author

Skarlso commented Sep 24, 2018 •
edited
Loading

Unfortunately it's boltdb.
screen shot 2018-09-24 at 06 39 44

Clarification, you can see here that the ids are, 1 1 1 2 2 2 3.

@Skarlso
Copy link
Member Author

Skarlso commented Sep 24, 2018

Aha, I see what's going on. I'll fix this.

@Skarlso Skarlso self-assigned this Sep 24, 2018
@Skarlso Skarlso mentioned this issue Sep 24, 2018
Merged
@Skarlso
Copy link
Member Author

Skarlso commented Sep 25, 2018

Fixed

@Skarlso Skarlso closed this as completed Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Skarlso Skarlso

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Skarlso @michelvocks