You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From @j.schmoelder : I think we could also reconsider the naming convention of the output branches. While unlikely, a key collision is theoretically possible if two runs are started at the same time (see also #24). Instead, we could either simply use a unique ID (ideally s.t. we can use a long and a short format for referencing, just like for commit hashes) or if we go for some kind of queuing system, all runs must consecutive anyway, so we could simply give them an increasing counter.
The text was updated successfully, but these errors were encountered:
In GitLab by @r.jaepel on Nov 28, 2023, 11:32
From @j.schmoelder : I think we could also reconsider the naming convention of the output branches. While unlikely, a key collision is theoretically possible if two runs are started at the same time (see also #24). Instead, we could either simply use a unique ID (ideally s.t. we can use a long and a short format for referencing, just like for commit hashes) or if we go for some kind of queuing system, all runs must consecutive anyway, so we could simply give them an increasing counter.
The text was updated successfully, but these errors were encountered: