warp-the-new-crac-engine

[foojayio-bot]

warp-the-new-crac-engine

https://foojay.io/today/warp-the-new-crac-engine/

Comments below were imported from the previous foojay.io WordPress site.

[foojayio-bot]

Originally posted by William on December 30, 2024 in Foojay.io Discussions.

Will Google Cloud Storage (bucket) also be considered?

[foojayio-bot]

Originally posted by Radim Vansa on January 6, 2025 in Foojay.io Discussions.

Hi, Google Cloud Storage is a good candidate and I don’t see why we couldn’t interface with that, too, though I think that we’ll gather some operational experience with S3 before jumping on the implementation of native Google Cloud Storage integration.

[foojayio-bot]

Originally posted by Yury on January 2, 2025 in Foojay.io Discussions.

Is there a way to debug failures? Something similar to criu tooling (crit). Or a way to turn on debug logging?

[foojayio-bot]

Originally posted by Radim Vansa on January 6, 2025 in Foojay.io Discussions.

Right now debug logging is a compile-time-only option; have you experienced any errors that wouldn’t have sufficient information printed out?
One advantage over working with CRIU I regularly use during development is that strace works (CRIU uses ptrace and therefore you can’t strace the same process).
Speaking about crit, I guess that you want to look into the image itself. Since Warp uses the ELF format, you could explore it using readelf, eu-readelf or objdump. Even better, you could open it as coredump using GDB (it might just need a little hinting on debug symbols to resolve stacks properly).