We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
draft
This is an issue @sunnyosun shared in a verbal discussion yesterday.
It can happen that two users work on the same transform draft at the same time.
Meaning, they both run
ln.track("3qIZOmDUVBwc0001")
in a notebook/script file with the same name.
The first user currently gets:
→ created Transform('3qIZOmDU'), started new Run('asi87URD') at 2024-09-29 10:03:01 UTC
The second user gets:
→ loaded Transform('3qIZOmDU'), started new Run('Q6dM7cRs') at 2024-09-29 10:03:05 UTC
For a script, this behavior is fine. For a notebook, it can lead to conflicting notebook versions for this uid.
uid
Hence, rather than triggering a new run, the second user should have gotten an error and a request to bump the revision.
The text was updated successfully, but these errors were encountered:
lamin load
Successfully merging a pull request may close this issue.
This is an issue @sunnyosun shared in a verbal discussion yesterday.
It can happen that two users work on the same transform draft at the same time.
Meaning, they both run
in a notebook/script file with the same name.
The first user currently gets:
The second user gets:
For a script, this behavior is fine. For a notebook, it can lead to conflicting notebook versions for this
uid
.Hence, rather than triggering a new run, the second user should have gotten an error and a request to bump the revision.
The text was updated successfully, but these errors were encountered: