Was trying to delete a few jobs, it crashed at 59%:
Strange. I suspect the problem is just that the Job got deleted elsewhere after the deletes got queued up, doesn’t look like we’re handling that edge case.
Should be easy enough to fix
Still getting this with 8.0.3.0:
2016-06-09 11:24:44: An unexpected error occurred while Deleting Job(s):
2016-06-09 11:24:44: An unexpected error occurred while interacting with the database (deadline01.scanlinevfxla.com:27017,deadline02.scanlinevfxla.com:27017,deadline03.scanlinevfxla.com:27017):
2016-06-09 11:24:44: Value cannot be null.
2016-06-09 11:24:44: Parameter name: document (System.ArgumentNullException)
2016-06-09 11:24:44: at MongoDB.Driver.MongoCollection.Save(Type nominalType, Object document, MongoInsertOptions options)
2016-06-09 11:24:44: at Deadline.StorageDB.MongoDB.MongoJobStorage.DeleteJob(String jobID) (FranticX.Database.DatabaseConnectionException)
2016-06-09 11:24:44: at j.a(MongoServer A_0, Exception A_1)
2016-06-09 11:24:44: at Deadline.StorageDB.MongoDB.MongoJobStorage.DeleteJob(String jobID)
2016-06-09 11:24:44: at Deadline.Controllers.DataController.DeleteJobAndAuxiliaryFiles(Job job)
2016-06-09 11:24:44: at Deadline.Monitor.WorkItems.DeleteJobsWI.InternalDoWork()
2016-06-09 11:24:44: at Deadline.Monitor.MonitorWorkItem.DoWork()
2016-06-09 11:24:44: ---------- Inner Stack Trace (System.ArgumentNullException) ----------
2016-06-09 11:24:44: at MongoDB.Driver.MongoCollection.Save(Type nominalType, Object document, MongoInsertOptions options)
2016-06-09 11:24:44: at Deadline.StorageDB.MongoDB.MongoJobStorage.DeleteJob(String jobID)Yeah, the fix for this just missed the cut for 8.0.3.0, but is in the hopper for the planned release next week (8.0.4.x) 
Are 8.1 and 8.0 going to branch separately? Whats your advice, sticking to 8.0 point releases, or going to 8.1?
Basically 8.0 is getting all the bugfixes (unless they’re more in-depth), and 8.1 is getting some new features (albeit not a huge list of them, mostly integration stuff) and higher profile changes. 8.0 is getting merged into 8.1, but 8.1 is generally going to be a bit less stable since it is a beta and has new stuff in it.
It’s honestly up to you guys, but the safer path would definitely be to stick to 8.0 for production unless there’s an 8.1 feature that you really need.
The remote update command and using pulse for remote commands look pretty appetizing… As long as we don’t miss out on any bugfixes that go into the 8.0 branch, we might jump to 8.1.
The idea is that I will merge everything from 8.0 into 8.1 after each revision release of 8, so everything released in 8.0 should be in subsequent 8.1 builds as well.
Cheers,
Jon