configdep: T6206 fix marker for last element of delete priority queues #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related task: T5660: add marker for last element of priority queues
Problem: In the priority queue we always have one empty root element after
_get_commit_prio_queuetherefore minimum length is 1 and we can't mark as last any deleted node, even when we try to delete only one node e.g.del vpnalso when we try to add\change one node, in the queue we have two element: one empty and one that we use.
This root element has state as
COMMIT_STATE_UNCHANGEDprobably will be better to filter this element in_get_commit_prio_queuebut i don't know how it affect feature not related with configdep.also, all other unchanged nodes filtered before
doCommit.Change Summary
Types of changes
Related Task(s)
Related PR(s)
Component(s) name
Proposed changes
How to test
or try to delete node with a dependency e.g
del vpn l2tpSmoketest result
Checklist: