jwulf / press-star

A node-based implementation of the popular Death Star authoring environment for PressGang / Docbook
4 stars 1 forks source link

Bug: Book does not finish rebuild after structural change w/ dirty patches #30

Open mishaone opened 11 years ago

mishaone commented 11 years ago

A rebuild for the JBoss Data Grid Infinispan Query book was automatically triggered after a structural change[1]. The build status as of now (4:17 BNE time) is as follows:

Socket.io loaded

Connected to server

2013-05-15 15:18:51 : Build log for 14318 - Infinispan Query Guide

2013-05-15 15:18:51 : Job queued.

2013-05-15 15:18:51 : Getting the Content Spec from PressGang for analysis

2013-05-15 15:18:51 : Latest Spec Revision 449202

2013-05-15 15:18:51 : CSProcessor assembly initiated

2013-05-15 15:19:11 : Unzipping publican book in /opt/deathstar-2.0/books/JBoss_Data_Grid/14318-Infinispan_Query_Guide-6.2/assembly

2013-05-15 15:19:11 : No custom Entity file specified

2013-05-15 15:19:11 : Publican build initiated and in progress

2013-05-15 15:21:00 : Publican build complete with code 0

2013-05-15 15:21:00 : Writing server information into the book

2013-05-15 15:21:04 : Checking the dirty buffer for live patches


[1] Structural changes to the content spec map were:

Removed Section: Mapping an Entity from Chapter: Mapping Entities to the Index Structure

Shifted back subsequent topics (as below) to accommodate new structure:

Chapter: Mapping Entities to the Index Structure

Section: Mapping an Entity << Mapping an Entity [14214] Section: Basic Mapping About Basic Mapping [14272] @Indexed [14287] @Field [14285] @NumericField [14284] @Id [14286] Mapping Properties Multiple Times [14278] Embedded and Associated Objects [14202] Limiting Object Embedding to Specific Paths [14290]


Additionally, I made edits to a topic (added a para and itemized list with condition) during the build. The topic was Mapping an Entity [14214]

jwulf commented 11 years ago

Misha, this is a tricky one, because even after trying to, I can't get this to reproduce under the microscope. It might rely on other concomitant factors like memory starvation.

I've added additional debugging so that we can track down exactly where in the dirty patcher it is hanging. Please grab the build log whenever it happens again, and add it to this bug.

I also added the remote server bounce feature, so that you can reset the build queue if you need to.

jwulf commented 11 years ago

Have you seen this again Misha?

mishaone commented 11 years ago

Not so far, Josh. I'll report here if it happens again.