Added

• A new optional field label was added to the types AppWithOptions, ConductorOptions, CreateConductorOptions, and to the function addConductor. It allows overriding the default label which will prefix log messages of that Conductor instance.
• A new method integratedOpsCount that polls for integrated ops and checks if the number of integrated ops is equal to the desired number for a given dna hash. (#305)

Removed

• BREAKING: Utility function conductorCellsDhtSync has been removed. Use dhtSync directly instead. (#305)

Changed

• Log messages from Conductors that were created with addPlayers functions are now prefixed by Tryorama - Player # where "#" is the Player index. This makes it easier to distinguish log messages from different conductors. (#302)

Fixed

• When creating conductors with Scenario#addPlayers, Scenario#installAppsForPlayers, Scenario#installSameAppForPlayers, Scenario#addPlayersWithApps, and Scenario#addPlayersWithSameApp each conductor is created sequentially and waits for startup. This is a workaround to avoid connection failures which can cause test failures. (#303)
• Fixed flaky behavior in recognizing conductor startup success. (#303)

Added

• A new method storageArc that polls for network metrics to check if an agent's storage arc is equal to a desired storage arc for a given dna hash. (#301)
• A new configuration field targetArcFactor has been added to NetworkConfig, allowing test scenarios to be written with 0-arc conductors (#300)

Fixed

• Network options are now applied before the conductor launches, to ensure they actually alter the conductor configuration. (#300)

Fixed

• Upgrade all dependencies to Holochain v0.6.

Fixed

• Fixed the logic in dhtSync to determine whether conductors are in sync (#287)

Added

• A new method Scenario#addPlayers that creates the specified number of conductors and generates an agent per conductor.
• A new method Scenario#installAppsForPlayers that installs the specified apps for the provided players. The combination of these two methods caters for the use cases where agent keys are generated prior to app installation for further usage, e.g. when generating mem proofs in a separate step.
• A new method Scenario#installSameAppForPlayers that installs the specified app for the provided players. In contrast to installAppsForPlayers this is a simplified interface that just takes one app with options and install it for all players equally.
• A new method Scenario#addPlayersWithSameApp that creates players and installs the same specified app for each player. A counterpart to addPlayersWithApps, this is also a simplified interface for the most common case of installing the same app for each player.

Changed

• Updated dependencies to latest versions.
• BREAKING: Type Player is now a conductor with an associated agent key. It used to be the conductor with an installed app for the agent. That has been renamed to PlayerApp in alignment with the type AgentApp (app id + agent key + cells), which PlayerApp extends.

Added

• More options for conductor startup. All can be left at defaults in most cases but the defaults provided by Tryorama
  are more appropriate for testing than the defaults that Holochain provides. The new options are initiateJitterMs,
  roundTimeoutMs and transportTimeoutS.

Changed

• The utility function dhtSync parameter timeoutMs now defaults to 60000 milliseconds, and the parameter intervalMs now defaults to 500 milliseconds.

Fixed

• Return an error if spawning kitsune2-bootstrap-srv fails
• The utility functions dhtSync and conductorCellsDhtSync now check that all Ops have been integrated and are not in limbo.

Fixed

• Fix js-yaml still included as a dev-dependency

Added

• NetworkConfig with options to configure gossip in conductors and scenarios.

Removed

• TryCP server, client and test utilities for TryCP conductors.

Changed

• Update to @holochain/[email protected] and update types accordingly.
• Remove tape as test runner and switch to native NodeJS test runner and assertion library.

Fixed

• Local: Conductor startup string parsing. This lead to flaky tests because the client attempted to connect to Holochain before it was fully started up.