Lars Francke

icon indicating a website link https://www.stackable.tech icon indicating an email [email protected]

icon company @stackabletech icon location Hamburg, Germany icon location Co-Founder of @stackabletech and @opencore. Building a modern data platform at Stackable: Open Source based on Kubernetes

Results 85 comments of Lars Francke

Trailing zeros in fractional digits of timestamp fails validation.

I have started a discussion in the CycloneDX Slack and I'll see if there are any results. If not I'll close this issue as I'm relatively sure that this is...

Trailing zeros in fractional digits of timestamp fails validation.

I opened an [issue](https://github.com/CycloneDX/cyclonedx-dotnet-library/issues/265) in the .NET library which is used by the CLI. I'm going to close this issue as our JSON documents do indeed seem to be valid....

Trailing zeros in fractional digits of timestamp fails validation.

I looked into it again and technically we are doing something wrong I believe. We use ISO 8601 when we should be using RFC 3339. I'll reopen this issue for...

Trailing zeros in fractional digits of timestamp fails validation.

To be more precice: JSON requires RFC 3339, XML ISO 8601, yay

Record the rustc target platform into the SBOM

I think this is basically good to go, we just need to wait for the result of https://github.com/CycloneDX/cyclonedx-property-taxonomy/issues/75

Capture data only available during the build process

There is a [ticket](https://github.com/rust-lang/cargo/issues/7614) to maybe delete build-plan support so I would not recommend relying on it. In any case it is the plan on what will run not what...

Import transitive dependencies from SBOMs if available

Examples of where this would be useful?

Support Kerberos authentication in Kafka

Thank you! And could you also include a snippet for the release notes please?

Default replication factor for internal offsets topic prevents users from reading from clusters that have less than three nodes.

Good catch. Technical question: Let's say a customer starts with 1 node, we set the setting to `1` as well. Customer later scales up to 5 nodes, we set it...

Default replication factor for internal offsets topic prevents users from reading from clusters that have less than three nodes.

This _at least_ needs some documentation but I'd prefer an automatic setting change I believe