holochain 0.0.107

• Adds experimental feature for one storage agent per space to kitsune tuning params. gossip_single_storage_arc_per_space.
• Adds the ability to lower the synchronous level for the sqlite backend to the conductor config. db_sync_level. See sqlite documentation. This allows running on slower HDD but can result in corrupted databases and is not recommended for production or SSDs.
• Fixes bug where WAL mode was set on every opening connection.

---

Please also read this release's top-level CHANGELOG to see what changed in other crates alongside this one.

holochain 0.0.106

Changed

• HDK sys_time now returns a holochain_zome_types::Timestamp instead of a core::time::Duration.
• Exposes UninstallApp in the conductor admin API.

---

Please also read this release's top-level CHANGELOG to see what changed in other crates alongside this one.

holochain 0.0.104

• Updates lair to 0.0.4 which pins rcgen to 0.8.11 to work around rustls/rcgen#63

---

Please also read this release's top-level CHANGELOG to see what changed in the other crates repository.

holochain 0.0.103

Fixed

• This release solves the issues with installing happ bundles or registering DNA via the admin API concurrently. #881.

Changed

• Header builder now uses chain top timestamp for new headers if in the future
• Timestamps in headers require strict inequality in sys validation

---

Please also read this release's top-level CHANGELOG to see what changed in the other crates repository.

holochain 0.0.102

Known Issues ❗

• We’ve become aware of a bug that locks up the conductor when installing happ bundles or registering DNA via the admin API concurrently. Please perform these actions sequentially until we’ve resolved the bug.

Fixed

• Concurrent zome calls could cause the init() zome callback to run multiple times concurrently, causing HeadMoved errors. This is fixed, so that init() can only ever run once.
  • If a zome call has been waiting for another zome call to finish running init() for longer than 30 seconds, it will timeout.

Changed

• Apps now have a more complex status. Apps now can be either enabled/disabled as well as running/stopped, the combination of which is captured by three distinctly named states:
  • “Running” (enabled + running) -> The app is running normally
  • “Paused” (enabled + stopped) -> The app is currently stopped due to some minor problem in one of its cells such as failed network access, but will start running again as soon as it’s able. Some Cells may still be running normally.
  • “Disabled” (disabled + stopped) -> The app is stopped and will remain so until explicitly enabled via EnableApp admin method. Apps can be disabled manually via DisableApp, or automatically due to an unrecoverable error in a Cell.
• Some admin methods are deprecated due to the app status changes:
  • ActivateApp is deprecated in favor of EnableApp
  • DeactivateApp is deprecated in favor of DisableApp
• Apps will be automatically Paused if not all of their cells are able to join the network during startup

Added

• InstallAppBundle command added to admin conductor API. #665
• DnaSource in conductor_api RegisterDna call now can take a DnaBundle #665
• New admin interface methods:
  • EnableApp (replaces ActivateApp)
  • DisableApp (replaces DeactivateApp)
  • StartApp (used to attempt to manually restart a Paused app)
• Using the 3 level PLRU instance cache from latest holochain wasmer v0.0.72

holochain 0.0.101

This version contains breaking changes to the conductor API as well as a major upgrade to the underlying Wasm runtime.

❗ Performance impact

The version of wasmer that is used in this holochain release contains bugs in the scoping of wasmer modules vs. instances, such that it blocks the proper release of memory and slows down execution of concurrent Wasm instances. While we were able to at least mitigate these effects and are coordinating with wasmer to find a proper solution as soon as possible.

The severity of these issues increases with cell concurrency, i.e. using multiple cells with the same DNA. Application development with a single conductor and a few cells are expected to work well unless your machine has serious resource restrictions.

Added

• InstallAppBundle command added to admin conductor API. #665
• DnaSource in conductor_api RegisterDna call now can take a DnaBundle #665

Removed

• BREAKING: InstallAppDnaPayload in admin conductor API InstallApp command now only accepts a hash. Both properties and path have been removed as per deprecation warning. Use either RegisterDna or InstallAppBundle instead. #665
• BREAKING: DnaSource(Path) in conductor_api RegisterDna call now must point to DnaBundle as created by hc dna pack not a DnaFile created by dna_util #665

CHANGED

• Updated to a version of holochain_wasmer that includes a migration to wasmer v2+. #773, #801, #836
• Introduced a simple instance cache to mitigate and potentially outweigh the effects of the aforementioned wasmer conditions #848

Holo-Testing

Commit being tested for deployment to holoports