Operational Defect Database

BugZero found this defect 2500 days ago.

MongoDB | 375953

[SERVER-28888] libdeps dependency order unstable without --implicit-cache

Last update date:

10/30/2023

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.5.7

Description:

Info

In SERVER-27505, we added support for topsorting our libraries. As part of that change, we stopped sorting the results reported by the scanner: https://github.com/mongodb/mongo/commit/190dcaab71bcca027954e227ac73a36958aab762#diff-d90fa2623f9db54079c913e56e6183e0R188 That caused the dependency orders to change run-to-run, unless you were building with --implicit-cache. Since most users do build that way, we didn't notice. The solution is to simply append the results in the stable order returned by __get_libdeps.

Top User Comments

xgen-internal-githook commented on Fri, 21 Apr 2017 17:33:45 +0000: Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'} Message: SERVER-28888 Ensure scanner stability across rebuilds Also, a quick fix to eliminate a needless sort, since Node.sources is expected to be stable across rebuilds, unlike Node.sources_set Branch: master https://github.com/mongodb/mongo/commit/ab0fc1ebb4df846367d409e0223a085e0db1b98e

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...