Structs§
- An aligned COW vector of bytes which avoids copying data when its constructed. The vector is aligned on the 16-byte boundary
- An archived
JournalEntryChangeDirectoryV1 - An archived
JournalEntryClearEtherealV1 - An archived
JournalEntryCloseFileDescriptorV1 - An archived
JournalEntryCloseThreadV1 - An archived
JournalEntryCreateDirectoryV1 - An archived
JournalEntryCreateEventV1 - An archived
JournalEntryCreateHardLinkV1 - An archived
JournalEntryCreatePipeV1 - An archived
JournalEntryCreateSymbolicLinkV1 - An archived
JournalEntryDuplicateFileDescriptorV1 - An archived
JournalEntryEpollCreateV1 - An archived
JournalEntryEpollCtlV1 - An archived
JournalEntryFileDescriptorAdviseV1 - An archived
JournalEntryFileDescriptorAllocateV1 - An archived
JournalEntryFileDescriptorSeekV1 - An archived
JournalEntryFileDescriptorSetFlagsV1 - An archived
JournalEntryFileDescriptorSetRightsV1 - An archived
JournalEntryFileDescriptorSetSizeV1 - An archived
JournalEntryFileDescriptorSetTimesV1 - An archived
JournalEntryFileDescriptorWriteV1 - An archived
JournalEntryInitModuleV1 - An archived
JournalEntryOpenFileDescriptorV1 - An archived
JournalEntryPathRenameV1 - An archived
JournalEntryPathSetTimesV1 - An archived
JournalEntryPortAddAddrV1 - An archived
JournalEntryPortBridgeV1 - An archived
JournalEntryPortDelAddrV1 - An archived
JournalEntryPortGatewaySetV1 - An archived
JournalEntryPortRouteAddV1 - An archived
JournalEntryPortRouteDelV1 - An archived
JournalEntryProcessExitV1 - An archived
JournalEntryRemoveDirectoryV1 - An archived
JournalEntryRenumberFileDescriptorV1 - An archived
JournalEntrySetClockTimeV1 - An archived
JournalEntrySetThreadV1 - An archived
JournalEntrySnapshotV1 - An archived
JournalEntrySocketAcceptedV1 - An archived
JournalEntrySocketBindV1 - An archived
JournalEntrySocketConnectedV1 - An archived
JournalEntrySocketJoinIpv4MulticastV1 - An archived
JournalEntrySocketJoinIpv6MulticastV1 - An archived
JournalEntrySocketLeaveIpv4MulticastV1 - An archived
JournalEntrySocketLeaveIpv6MulticastV1 - An archived
JournalEntrySocketListenV1 - An archived
JournalEntrySocketOpenV1 - An archived
JournalEntrySocketSendFileV1 - An archived
JournalEntrySocketSendToV1 - An archived
JournalEntrySocketSendV1 - An archived
JournalEntrySocketSetOptFlagV1 - An archived
JournalEntrySocketSetOptSizeV1 - An archived
JournalEntrySocketSetOptTimeV1 - An archived
JournalEntrySocketShutdownV1 - An archived
JournalEntryTtySetV1 - An archived
JournalEntryUnlinkFileV1 - An archived
JournalEntryUpdateMemoryRegionV1 - An archived
JournalEpollEventCtlV1 - An archived
JournalIpCidrV1 - An archived
JournalWasiMemoryLayout - Journal which leave itself in a consistent state once it commits by closing all the file descriptors that were opened while it was recording writes.
- Represents the results of a compaction operation
- Deduplicates memory and stacks to reduce the number of volume of log events sent to its inner capturer. Compacting the events occurs in line as the events are generated
- Journal which will store the events locally in memory until it is either committed or rolled back
- Journal that counts the size of the entries that are written to it
- Filters out a specific set of journal events and drops the rest, this journal can be useful for restoring to a previous call point but retaining the memory changes (e.g. WCGI runner).
- Constructs a filter with a set of parameters that will be filtered on
- Journal
Effector journalThe journal effector is an adapter that will be removed in a future refactor. Its purpose is to put the code that does mappings from WASM memory through its abstractions into concrete journal objects that can be stored. Instead of this what should be done is that the syscalls themselves can be represented as a strongly typed object that can be passed directly to the journal but in order to do this we require an extensive refactoring of the WASIX syscalls which is not in scope at this time. - The resolver for an archived
JournalEntryChangeDirectoryV1 - The resolver for an archived
JournalEntryClearEtherealV1 - The resolver for an archived
JournalEntryCloseFileDescriptorV1 - The resolver for an archived
JournalEntryCloseThreadV1 - The resolver for an archived
JournalEntryCreateDirectoryV1 - The resolver for an archived
JournalEntryCreateEventV1 - The resolver for an archived
JournalEntryCreateHardLinkV1 - The resolver for an archived
JournalEntryCreatePipeV1 - The resolver for an archived
JournalEntryCreateSymbolicLinkV1 - The resolver for an archived
JournalEntryDuplicateFileDescriptorV1 - The resolver for an archived
JournalEntryEpollCreateV1 - The resolver for an archived
JournalEntryEpollCtlV1 - The resolver for an archived
JournalEntryFileDescriptorAdviseV1 - The resolver for an archived
JournalEntryFileDescriptorAllocateV1 - The resolver for an archived
JournalEntryFileDescriptorSeekV1 - The resolver for an archived
JournalEntryFileDescriptorSetFlagsV1 - The resolver for an archived
JournalEntryFileDescriptorSetRightsV1 - The resolver for an archived
JournalEntryFileDescriptorSetSizeV1 - The resolver for an archived
JournalEntryFileDescriptorSetTimesV1 - WARNING!!!! Do not change this structure without updating “/lib/cli/src/commands/journal/mount/fs.rs”
- The resolver for an archived
JournalEntryFileDescriptorWriteV1 - The resolver for an archived
JournalEntryInitModuleV1 - The resolver for an archived
JournalEntryOpenFileDescriptorV1 - The resolver for an archived
JournalEntryPathRenameV1 - The resolver for an archived
JournalEntryPathSetTimesV1 - The resolver for an archived
JournalEntryPortAddAddrV1 - The resolver for an archived
JournalEntryPortBridgeV1 - The resolver for an archived
JournalEntryPortDelAddrV1 - The resolver for an archived
JournalEntryPortGatewaySetV1 - The resolver for an archived
JournalEntryPortRouteAddV1 - The resolver for an archived
JournalEntryPortRouteDelV1 - The resolver for an archived
JournalEntryProcessExitV1 - The resolver for an archived
JournalEntryRemoveDirectoryV1 - The resolver for an archived
JournalEntryRenumberFileDescriptorV1 - The resolver for an archived
JournalEntrySetClockTimeV1 - The resolver for an archived
JournalEntrySetThreadV1 - The resolver for an archived
JournalEntrySnapshotV1 - The resolver for an archived
JournalEntrySocketAcceptedV1 - The resolver for an archived
JournalEntrySocketBindV1 - The resolver for an archived
JournalEntrySocketConnectedV1 - The resolver for an archived
JournalEntrySocketJoinIpv4MulticastV1 - The resolver for an archived
JournalEntrySocketJoinIpv6MulticastV1 - The resolver for an archived
JournalEntrySocketLeaveIpv4MulticastV1 - The resolver for an archived
JournalEntrySocketLeaveIpv6MulticastV1 - The resolver for an archived
JournalEntrySocketListenV1 - The resolver for an archived
JournalEntrySocketOpenV1 - The resolver for an archived
JournalEntrySocketSendFileV1 - The resolver for an archived
JournalEntrySocketSendToV1 - The resolver for an archived
JournalEntrySocketSendV1 - The resolver for an archived
JournalEntrySocketSetOptFlagV1 - The resolver for an archived
JournalEntrySocketSetOptSizeV1 - The resolver for an archived
JournalEntrySocketSetOptTimeV1 - The resolver for an archived
JournalEntrySocketShutdownV1 - The resolver for an archived
JournalEntryTtySetV1 - The resolver for an archived
JournalEntryUnlinkFileV1 - The resolver for an archived
JournalEntryUpdateMemoryRegionV1 - The resolver for an archived
JournalEpollEventCtlV1 - The resolver for an archived
JournalIpCidrV1 - The resolver for an archived
JournalWasiMemoryLayout - The LogFile snapshot capturer will write its snapshots to a linear journal and read them when restoring. It uses the
bincodeserializer which means that forwards and backwards compatibility must be dealt with carefully. - The results of an operation to read a log entry from the log
- The results of an operation to write a log entry to the log
- The memory file journal processes journal entries by writing any memory mutations directly to a file. Later this can be used as a mounting target for resuming a process without having to reload the journal from scratch.
- The null journal sends all the records into the abyss
- The printing journal writes all the journal entries to the console as either text or json.
- Journal which will store the events locally in memory until it is either committed or rolled back
- The default for runtime is to use the unsupported journal which will fail to write journal entries if one attempts to do so.
Enums§
- An archived
JournalAddressfamilyV1 - An archived
JournalAdviceV1 - An archived
JournalEntryRecordType - An archived
JournalEpollCtlV1 - An archived
JournalExitCodeV1 - An archived
JournalSnapshot0ClockidV1 - An archived
JournalSnapshotTriggerV1 - An archived
JournalSocketShutdownV1 - An archived
JournalSockoptionV1 - An archived
JournalSocktypeV1 - An archived
JournalStreamSecurityV1 - An archived
JournalThreadStartTypeV1 - An archived
JournalTimeTypeV1 - An archived
JournalWhenceV1 - The resolver for an archived
JournalAddressfamilyV1 - The resolver for an archived
JournalAdviceV1 - Represents a log entry in a snapshot log stream that represents the total state of a WASM process at a point in time.
- The resolver for an archived
JournalEntryRecordType - The resolver for an archived
JournalEpollCtlV1 - The resolver for an archived
JournalExitCodeV1 - Type of printing mode to use
- The resolver for an archived
JournalSnapshot0ClockidV1 - The resolver for an archived
JournalSnapshotTriggerV1 - The resolver for an archived
JournalSocketShutdownV1 - The resolver for an archived
JournalSockoptionV1 - The resolver for an archived
JournalSocktypeV1 - The resolver for an archived
JournalStreamSecurityV1 - The resolver for an archived
JournalThreadStartTypeV1 - The resolver for an archived
JournalTimeTypeV1 - The resolver for an archived
JournalWhenceV1 - Various triggers that will cause the runtime to take snapshot of the WASM state and store it in the snapshot file.
Constants§
Statics§
Traits§
- The snapshot capturer will take a series of objects that represents the state of a WASM process at a point in time and saves it so that it can be restored. It also allows for the restoration of that state at a later moment
- The snapshot capturer will take a series of objects that represents the state of a WASM process at a point in time and saves it so that it can be restored. It also allows for the restoration of that state at a later moment
- The snapshot capturer will take a series of objects that represents the state of a WASM process at a point in time and saves it so that it can be restored. It also allows for the restoration of that state at a later moment