You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Date


Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy . If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Attendees

Agenda

  • Record the meeting
  • Squash and merge commit message
  • Tests throw WalletInvalidHandle because afterAll function (that deletes wallet) is called before tests are finished
    • I think this is because outbound subject transporter and outbound transporter in general return when the message is send. But the other agent still has to process the whole message. However jest sees it as "oh the promise is resolved, the test is finished". 
  • How to handle auto accept
    • local config → stored with connection record on creation
    • global config → stored with connection record on creation?

Meeting Notes

  • everyone aware of agent running after jest tests resolve. 
  • auto accept connections logic
    • local config is stored with connection record, global config not
    • local config takes precedence over global config
  • using AFJ inside a react native application
    • Indy.framework is currently not built for simulator
    • Building Indy.framework from the core does not work at the moment
    • there are issues with building iOS targets in libindy. 

Future topics

  • State machines






  • No labels