When a Flight is not available in NodeODM (when, for example, it was manually added, or NodeODM has already deleted the Flight from its database), some fields (namely, the number of images and the processing time) stay empty and look odd.
[x] Add a num_images field on the Flight model, make it a PositiveIntegerField, default to 0.
[x] Create the migration
[x] On the webhook, save the imagesCount field into flight.num_images, just after saving the processingTime.
[x] On the /nodeodm/uuid/info view, if Flight is Complete, Canceled or Error, don't send subrequest to NodeODM. Instead, respond with data saved in Flight model (this ensures that all info will still be shown after the Flight gets deleted from NodeODM). Important keys: status.code, processingTime, imagesCount (all obtainable from the Model)
When a Flight is not available in NodeODM (when, for example, it was manually added, or NodeODM has already deleted the Flight from its database), some fields (namely, the number of images and the processing time) stay empty and look odd.
num_imagesfield on the Flight model, make it a PositiveIntegerField, default to 0.imagesCountfield intoflight.num_images, just after saving theprocessingTime./nodeodm/uuid/infoview, if Flight is Complete, Canceled or Error, don't send subrequest to NodeODM. Instead, respond with data saved in Flight model (this ensures that all info will still be shown after the Flight gets deleted from NodeODM). Important keys:status.code,processingTime,imagesCount(all obtainable from the Model)