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.

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

[UX] Setting randuid's based off pipeline hash #265

Open
eddiebergman opened this issue Feb 27, 2024 · 0 comments
Open

[UX] Setting randuid's based off pipeline hash #265

eddiebergman opened this issue Feb 27, 2024 · 0 comments
Assignees
Labels
ux Something to make user experience better

Comments

@eddiebergman
Copy link
Contributor

Currently, when no name is provided for a pipeline, a randuid of length 8 is provided along with the type of component, i.e. Seq-X5jlIsas. This is required to prevent naming overlaps but can lead to issues when collecting results across many experiments.

A better solution would be for the component to traverse its children, using some hashing mechanism to provide at least a seeded variation of these 8 characters.

@eddiebergman eddiebergman added the ux Something to make user experience better label Feb 27, 2024
@eddiebergman eddiebergman self-assigned this Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ux Something to make user experience better
Projects
None yet
Development

No branches or pull requests

1 participant