Florian Wilhelm

Not stale. Any updates?

Hi @yurecz support for OData v4 Bound Functions and Actions is implemented in version [2.11.0](https://github.com/SAP/cloud-sdk-js/releases/tag/v2.11.0) of the sdk. See the [updated docs section](https://sap.github.io/cloud-sdk/docs/js/features/odata/v4-client#operations-functions-and-actions) for info on how to use them....

Hi @carlonnheim as a first step, support for OData v4 Bound Functions and Actions is implemented in version [2.11.0](https://github.com/SAP/cloud-sdk-js/releases/tag/v2.11.0) of the sdk. See the [updated docs section](https://sap.github.io/cloud-sdk/docs/js/features/odata/v4-client#operations-functions-and-actions) for info on...

Hi @ybbus Thanks for raising this issue. I currently can't tell you if this is supposed to work, we have an issue in our backlog to clarify this. We'll come...

Hi @ybbus after some more research, I have a few follow up questions to better understand the issue: It looks like the error message thrown by the SDK is truncated....

Thanks @jlebon that helps. Just to be clear: `os-init` is different in that regard, right?

Maybe relevant to mention: It's booting using systemd-boot (despite this not being officially supported, as documented [here](https://github.com/ostreedev/ostree/issues/1719)). This might be an issue when loading the repository, I guess.

I've made some progress in debugging this: [inside `ostree_sysroot_load_if_changed`](https://github.com/ostreedev/ostree/blob/878d601665fd15781adf774d99dd86e9a172cb92/src/libostree/ostree-sysroot.c#L1248) there is an early exit based on timestamps: `self->loaded_ts.tv_sec == stbuf.st_mtim.tv_sec && self->loaded_ts.tv_nsec == stbuf.st_mtim.tv_nsec`. This condition seems to be true...

Hi @jlebon, oh, yeah, has not occurred to me. ``` root@garden:~# stat /ostree/deploy File: /ostree/deploy Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 254,2 Inode: 28 Links: 3 Access:...

Okay, I've verified that this is the issue. I've learned that our tooling for making filesystems can set an arbitrary timestamp, and if I set it to a non-zero timestamp...