HomeMesosphereNo notifications. 4 unresolved issues.

Always set the RootGroup version to the current timestamp whenever it or its elements are updated.
ClosedAll Users

Authored by ichernetsky on Jul 19 2017, 12:09 AM.

Diff Detail

Repository
rMARATHON marathon
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
ichernetsky created this revision.Jul 19 2017, 12:09 AM
jenkins requested changes to this revision.Jul 19 2017, 12:12 AM
This revision now requires changes to proceed.Jul 19 2017, 12:12 AM
✗ Build of 3815 failed jenkins-public-marathon-phabricator-536.

Error message:

Stage Compile and Test failed.

(๑′°︿°๑)

✗ Build of 3815 failed jenkins-public-marathon-phabricator-537.

Error message:

Stage Compile and Test failed.

(๑′°︿°๑)

✗ Build of 3815 failed jenkins-public-marathon-phabricator-538.

Error message:

Stage Compile and Test failed.

(๑′°︿°๑)

✗ Build of 3815 failed jenkins-public-marathon-phabricator-539.

Error message:

Stage Compile and Test failed.

(๑′°︿°๑)

jenkins accepted this revision.Jul 19 2017, 6:09 AM
This revision is now accepted and ready to land.Jul 19 2017, 6:09 AM
✔ Build of 3815 completed jenkins-public-marathon-phabricator-540.

You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:

"url": "https://downloads.mesosphere.io/marathon/snapshots/marathon-1.5.0-SNAPSHOT-660-g128bc41.tgz",
"sha1": "43d84d10cfba6c6d040103ca1ce0e852ec624325"

\\ ٩( ᐛ )و //

jenkins requested changes to this revision.Jul 19 2017, 6:22 AM
This revision now requires changes to proceed.Jul 19 2017, 6:22 AM
✗ Build of 3815 failed jenkins-public-marathon-phabricator-542.

Error message:

Stage Compile and Test failed.

(๑′°︿°๑)

jenkins accepted this revision.Jul 19 2017, 6:53 AM
This revision is now accepted and ready to land.Jul 19 2017, 6:53 AM
✔ Build of 3815 completed jenkins-public-marathon-phabricator-543.

You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:

"url": "https://downloads.mesosphere.io/marathon/snapshots/marathon-1.5.0-SNAPSHOT-660-g128bc41.tgz",
"sha1": "3e13ad168ee82f5bfea81f5dff369708a8d95895"

\\ ٩( ᐛ )و //

Could you please add a diff description? I'm not sure for example why GroupManager defaults version to Group.defaultVersion (instead of Timestamp.now()).
Also - why does the RootGroup has a default at all - shouldn't we rather leave it empty and force the caller to pass the version?

In D932#36691, @zen-dog wrote:

Could you please add a diff description? I'm not sure for example why GroupManager defaults version to Group.defaultVersion (instead of Timestamp.now()).
Also - why does the RootGroup has a default at all - shouldn't we rather leave it empty and force the caller to pass the version?

Group.defaultVersion is Timestamp.now(). As far as I can tell, initially the intention was to use it everywhere, implying that unless one has a good reason to pass a specific version, it is better to use Group.defaultVersion by default which in turn is Timestamp.now().

As to why "GroupManager defaults version to Group.defaultVersion", it is because GroupManager deals with group versions.

zen-dog accepted this revision.Jul 25 2017, 3:25 PM

Accept assuming a proper diff description ;) Thx!

kensipe accepted this revision.Jul 25 2017, 3:46 PM
ichernetsky added 1 JIRA issue(s): MARATHON-7401.Jul 25 2017, 6:49 PM
This revision was automatically updated to reflect the committed changes.
jdef added a subscriber: jdef.Jul 25 2017, 7:21 PM

Sad to see this land w/o a proper description in the review Summary. Please don't let this happen again

Seriously! My accept was conditional. Next guy to come across this code will wonder why you did what you did. The bug wasn't subtle and it deserves explanation and a link to JIRA ticket.

Guys, would you like me to elaborate on why there is no reason to be sad or serious or both about it?