-
Notifications
You must be signed in to change notification settings - Fork 123
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
Ijod #914
base: master
Are you sure you want to change the base?
Conversation
… code/logic in the process
…now between synclets and push
getCurrent is unlost and functioning. |
This is now ready to merge and start testing on our sandbox. I'd appreciate any final reviews before I pull the trigger. There is a verification tool in the Ops directory called checkCurrent.js. It is ran such as: |
This reverts commit 2df12ab.
This reverts commit 7735358.
This changes transactions so it has actual transaction rollback. The batch add defaults to using this with 5 attempts to land a commit. I'm going fail hard if those 5 attempts fail until I understand why it's failing.
This stuff is much more transparent if we push it into the source tree, rather than putting it in the jenkins config. To the greatest extent possible, Jenkins should just run "make jenkins" and let us take care of the rest here.
@@ -27,36 +26,24 @@ module.exports = function(locker) { | |||
}); | |||
}); | |||
|
|||
// copy pasta from the synclet code, these should be utilizing some generic stuff instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmmm, pasta
There were known and unknown logic bombs in the code that have been purged by this pass. All scheduling is centralized and synclets are only executed from one location now.
This implemens ijod for core synclet results.
A few of the highlights now are:
There are currently two primary TODOs before looking to merge.
Please test this branch and see how it feels.