Jens Reimann
Jens Reimann
I created PR https://github.com/eclipse/ditto/pull/905 … following up in content-type suffix , optional data schema and additional content type.
To my understanding the following: > The event binding is identical for both HTTP request and response messages. Simply states that the cloud event binding for HTTP **can** be used...
A few ideas: * I think type should be something more like `org.eclipse.ditto.v2` * Maybe it makes sense to use the `datacontenttype` to indicate it is something ditto specific? *...
> I would have expected that the `datacontenttype`is the IANA registered content type for Ditto Protocol: > https://www.eclipse.org/ditto/protocol-specification.html#content-type Fancy! :grin: … absolutely!
I see … I will raise an issue there … However, I think the operator could be more open to accepting other versions. It looked like it pulled a specific...
I was trying to do this, but it didn't work. It continued to pull the specific sha256 images
Looks good to me. I only think there should be some note that `alloc` is still required. Maybe having an `alloc` feature, like here: https://serde.rs/no-std.html#memory-allocation
I agree, support for an alloc-free model is too much effort. My goal was more to make the user aware that `alloc` is required.
Ok, after digging a bit into this issue: It seems that self hosted runner (when installed as service using `./svc.sh`) get installed as "root", which doesn't seem to have "HOME"...
No. As by default a TCP keepalive timeout still is somewhat around two days IIRC.