-
Notifications
You must be signed in to change notification settings - Fork 15
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
Processing step fails on chstream transactions #114
Comments
The The removal of a timelock is a tricky one. If there have been no promotes into this stream, then we can "fast-forward" the child stream, otherwise we need to do a merge from the parent into the child stream. I think that the script tries to do this, but without more details about the error you're getting I'm not sure I can help. What kind of failure is it? Is there a warning that is printed? Is it an exception? Or does the graph just look weird? |
The script stops with an exception. One error was:
I increased the start transaction number to try to get past it and got this error:
Increasing the start transaction number by a couple weeks avoids the error. |
The big problem now is that after much pain and frustration and pulling of hair, I think I have a complete conversion as of 2 weeks ago. But I try to run it again to get the changes in the last couple weeks and it won't update the branches with the latest changes. It downloads them, because I see the changes listed in the refs (e.x. by running What might cause it to stop updating the branches? The end transaction is set to "now", and I tried rerunning the script as I ran it the first time, and also with |
If I change the merge-strategy to |
The The first exception you posted is triggered here. The line above is trying to get the last transaction on Clearly my assumption is that this branch or commit would exist but for some reason that is wrong. From your message I can't really infer why that is the case but there is something you could do to try and get past this error. Instead of raising the exception simply set the |
For whatever reason it seems that you have some branch that either doesn't exist any more or something else is making the |
Sorry, I was not clear that
is an acceptable solution for us. I had picked an arbitrary start date far enough back to make sure that it grabs everything we need. Moving the start date forward by a couple weeks is going to be fine for us. I probably should have created a new issue for the following: I need to figure out why it is not updating branches with the latest changes when I run the script again, or at least find some kind of workaround. I see there is an option to run the script repeatedly to pick up new changes, but it is not working. The new transaction data gets downloaded (and can be found by running |
What is the last log message that it prints? Knowing the path the program took in the |
When trying to update, there are no errors. The script looks like it runs fine, but does not add the additional commits to the branches. |
I didn't mean the errors, I meant the Are you running the script with the verbose and debug output? |
The second stage, where it creates the branches, seems to fail a lot for us when processing chstream transactions that remove a timelock. I do not know what information to provide for this issue...
It looks like the script is trying to rebase the stream. Is there a reason it does not do a merge from the parent stream instead? Can the script differentiate between a timelock add/remove and reparenting a stream?
The text was updated successfully, but these errors were encountered: