Error Report: `func invoke` Command Testing (LFX Mentorship)

[RayyanSeliya]

Summary

Comprehensive testing of the func invoke command identified 40+ issues across 10 categories, with the primary concerns being critical validation gaps where CloudEvents specification violations (missing required fields like specversion, type, and source) are silently accepted with exit code 0, leading to server rejections; wrong error messages where validation failures show misleading "fetching remote instances requires namespace" errors instead of actual validation problems, causing confusion and wasted debugging time; and no early validation where the system attempts function discovery or remote connections before validating inputs like file paths, target formats, content-types, and data formats. Key findings include critical bugs where content-type mismatches (JSON sent as XML, XML sent as JSON) are accepted without validation; malformed JSON and XML data is sent to servers without pre-flight syntax checking; HTTP specification violations where GET requests are sent with request bodies; and missing validation for empty flags, invalid formats, and special characters that all result in the same misleading namespace error. Additionally, the verbose mode output lacks HTTP status codes and shows raw escape sequences, making debugging difficult.

** Full Detailed Report**: Link to Google Docs - https://docs.google.com/document/d/1rsmHYqZosA7Lx9jmERcAWSKyKQvq_6mUJ0RFAejSChQ/edit?usp=sharing

Resolved Issues

The following issues have been marked as resolved in the detailed report:

(No issues marked as resolved yet)