|
|
|
|
|
by jLaForest
1005 days ago
|
|
A few weeks ago their mandatory cloud printing service had a bug and caused printers to spontaneously crash in the middle of the night, in many cases doing significant damage to the printer. Other than that Bambu had a pretty good reputation. |
|
> The result was that the print job was successfully completed on the printer, but our cloud service believed it had not been done. When service resumed, the once-jammed job was resent, leading to the unexpected printing of an already finished job.
That's why you make message sends in a distributed system idempotent, unless you have a really excellent reason not to. Whatever generated the print job when the user pressed “print” should have generated a unique job id, and when the printer was resent the same job id it should just have replied “Done”.