Raising event requires attributes variable

When raising an event in the postlude, the parser will accept something along the lines of "raise gossip event 'send_rumor'", but this will fail in runtime with a message
"{
"readyState": 4,
"responseText": "{"error":"Cannot convert undefined or null to object"}",
"responseJSON": {
"error": "Cannot convert undefined or null to object"
},
"status": 500,
"statusText": "Internal Server Error"
}"
so I am required to provide "attributes " as opposed to just not giving any attributes. I'm wondering if this is the expected behavior or if attributes should be optional, like in the case of giving "attributes {}" which would be the equivalent of not providing attributes in the first place.

Start by reproducing the postlude case with raise gossip event 'send_rumor', then trace the parser and runtime handling of event attributes. Compare it with attributes {} and determine whether omitted attributes should behave equivalently; done means the behavior is defined and the reported runtime error no longer occurs for the intended syntax.