This is the exact same type of error that happened in their Rust code last time. Strong type systems don’t protect you from lazy programming.

It's not remotely the same type of error -- error non-handling is very visible in the Rust code, while the Lua code shows the happy path, with no indication that it could explode at runtime.

Perhaps it's the similar way of not testing the possible error path, which is an organizational problem.