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

Lingering state of old BIs #270

Open
ghost opened this issue Aug 26, 2021 · 0 comments
Open

Lingering state of old BIs #270

ghost opened this issue Aug 26, 2021 · 0 comments
Labels
bug Something isn't working P2: soon Pretty important

Comments

@ghost
Copy link

ghost commented Aug 26, 2021

Apparently, Ds2 will allow the state of a BI to linger after the BI has finished:

  1. Add a (broken in some way) DC to the config
  2. Build the containing docset; wait until finished ("fail")
  3. Remove(!) the broken DC from the config again
  4. Rebuild containing docset; wait until finished

-> It fails again. Looking at the API, you can still see the broken DC's name under "deliverables", along with its failing status. To fix the issue, you need to quit Ds2, and importantly, delete the JSON from /var/cache/docserv.

There are two reasons why we did not notice this so far:

  1. We usually fix source documents rather than removing from the config.
  2. Only with Docserv 5.x did we actually introduce an overall build status. Before that we just used a document-based build status and copied whatever documents built successfully.
@ghost ghost added bug Something isn't working P2: soon Pretty important labels Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P2: soon Pretty important
Projects
None yet
Development

No branches or pull requests

0 participants