Rust unwrap causes Cloudflare panic

blog.cloudflare.com When the bad file with more than 200 features was propagated to our servers, this limit was hit — resulting in the system panicking. The FL2 Rust code that makes the check and was the source of the unhandled error is shown below: /// Fetch edge features based on `input` struct into [`Features`] buffer. pub fn fetch_features( &mut self, input: &dyn BotsInput, features: &mut Features, ) -> Result<(), (ErrorFlags, i32)> { // update features checksum (lower 32 bits) and copy edge feature names features.checksum &= 0xFFFF_FFFF_0000_0000; features.checksum |= u64::from(self.config.checksum); let (feature_values, _) = features .append_with_names(&self.config.feature_names) .unwrap();

A screenshot from blog.cloudflare.com explains that a malformed file with more than 200 features exceeded a limit and caused the system to panic. The highlighted Rust code ends with .unwrap(), turning an unexpected error into a crash. The joke is a technical reaction to production failures caused by assuming an operation could never fail. EN: A screenshot from blog.cloudflare.com explains that a malformed file with more than 200 features exceeded a limit and caused the system to panic. The highlighted Rust code ends with .unwrap(), turning an unexpected error into a crash. The joke is a technical reaction to production failures caused by assuming an operation could never fail.

• @gentoomemes / 19366 2025-11-19