Skip to content
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

Igor auto bump #31

Draft
wants to merge 18 commits into
base: master
Choose a base branch
from
Draft

Igor auto bump #31

wants to merge 18 commits into from

Conversation

Xanewok
Copy link
Contributor

@Xanewok Xanewok commented Nov 30, 2020

No description provided.

Xanewok and others added 18 commits November 24, 2020 12:12
Squashed commit of the following:

commit 4ec98b3
Author: Benjamin Kampmann <[email protected]>
Date:   Tue Oct 27 17:45:46 2020 +0100

    resolve git, better erroring

commit a17b9fc
Author: Benjamin Kampmann <[email protected]>
Date:   Tue Oct 27 13:08:31 2020 +0100

    calculating the graph

commit 5c18fd1
Merge: 9009841 9cbfd17
Author: Benjamin Kampmann <[email protected]>
Date:   Tue Oct 27 12:08:46 2020 +0100

    Merge remote-tracking branch 'origin/master' into ben-auto-bump

commit 9009841
Merge: ce42cac a9bed52
Author: Benjamin Kampmann <[email protected]>
Date:   Tue Oct 27 09:18:56 2020 +0100

    Merge branch 'ben-update-to-latest-cargo' into ben-auto-bump

commit ce42cac
Merge: 23b187e f8eeefc
Author: Benjamin Kampmann <[email protected]>
Date:   Tue Oct 27 09:14:14 2020 +0100

    Merge remote-tracking branch 'origin/master' into ben-auto-bump

commit 23b187e
Author: Benjamin Kampmann <[email protected]>
Date:   Mon Sep 21 11:51:17 2020 +0200

    adding current state

commit aff288f
Author: Benjamin Kampmann <[email protected]>
Date:   Tue Sep 8 18:29:50 2020 +0200

    update to latest dependencies
This brings it in line with what implementation does and should be more
in line with what --packages does (i.e. it does not figure out
dependents).
This groups package selection logic in one place, reducing the need for
boxing the resulting closure and making it easier to reason locally
about the package selection.
Previous version was traversing the entire graph for each member,
yielding a quadratic time. Moreover, an auxiliary data structure used
internally by petgraph panicked while traversing, so we run a simple DFS
ourselves to mark all transitive dependents and remove packages that
were not marked in the process.
We want to start with packages whose changes can have the most rippling
effect across the graph rather than the ones no other package depends
on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants