bug: event deserialization fails w/ "relative URL without a base" about sdk-rust HOT 5 CLOSED

Hey, thanks for the bug report! I believe the problem is with using "#" as the value for dataschema. If I'm interpreting the spec correctly, I believe that needs to be an absolute URI.

Am I missing something in the spec that would make "#" a valid dataschema?

from sdk-rust.

Unsure, but as you say: https://github.com/cloudevents/spec/blob/master/spec.md#dataschema points to # being technically invalid.

This is an event generated by Azure using 1.0 schema. As a user I have no way to alter the event.

from sdk-rust.

Is there some change to this library that would help you short of accepting an invalid event? Is there no way you can filter out the invalid fields before invoking sdk-rust?

from sdk-rust.

Is there some change to this library that would help you short of accepting an invalid event?

The use case was to receive CloudEvent data from Azure cloud. The data cannot be received via this library.

Is there no way you can filter out the invalid fields before invoking sdk-rust?

Yes, but that defeats the purpose. I completely removed the library because it was unhelpful.

--

FWIW, a quick scan on the other SDKs says this validation is not enforced across the board. What to do is beyond my pay grade.

from sdk-rust.

Closing for now. Maybe in the future we can introduce some sort of "lenient" mode if Azure insists on sending dataschema=#, but I feel like that's a bug on their side.

from sdk-rust.