search

rchain / rchip-proposals

Where RChain improvement proposals can be submitted
Apache License 2.0
8 stars 5 forks source link

Create debugging technical resources and best practices for developers #28

Open 9rb opened 4 years ago

9rb commented 4 years ago

Currently, printing logs to stdio is being used but is not the best method to debug applications. Some options are

  1. in the short term, provide access to observer nodes for vetted developers so they can look at logs without running local nodes - how do we extend this to a larger population beyond the 'vetted'?
  2. Increase indexing on blocks to expose more elements that users and developers are typically interested
  3. Use exploratory deploy and/or write to a deployId channel
dckc commented 4 years ago

See also hackathon prep https://github.com/orgs/rchain-community/projects/1#card-45686729

stdout / stderr goes to the node operator; contract developers shouldn't expect to be able to see it. There's a technique used in liquid-democracy for logging to a per-deployer log store. https://github.com/rholang/rholang.github.io/issues/23