accounting-crawler doesn't create starter-leases properly #2877

New Issue

meejah · 2017-06-07T19:24:39Z

meejah commented

2017-06-07 19:24:39 +00:00

On the cloud-backend branch, it looks like (from code inspection of a stack-trace from leastauthority production) that the AccountingCrawler isn't creating new starter leases properly.

There is not any test-coverage for the lines in question, so writing a unit-test is the first step.

On the cloud-backend branch, it looks like (from code inspection of a stack-trace from leastauthority production) that the [AccountingCrawler](wiki/AccountingCrawler) isn't creating new starter leases properly. There is not any test-coverage for the lines in question, so writing a unit-test is the first step.

meejah added the

labels 2017-06-07 19:24:39 +00:00

meejah added this to the soon milestone 2017-06-07 19:24:39 +00:00

exarkun commented

2020-10-30 12:35:44 +00:00

The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.

If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).

If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.

Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.

The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets. If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway). If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction. Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.

exarkun added the

wontfix

label 2020-10-30 12:35:44 +00:00

exarkun closed this issue

2020-10-30 12:35:44 +00:00

Sign in to join this conversation.