...
- Interpreter can be invoked via gRPC API
- Rholang Code can be evaluated in the Node regardless of the mode the node boots up in
- standalone mode
- Bootstrap mode
- Connected mode
- Rholang CLI can be invoked in 2 modes
- REPL
- Execute: @"listCh"!([1, 2, 3]) | for(@list <- @"listCh"){ match list { [a, b, c] => { @"stdout"!(a) } } }
- EVAL - accepts a file
- REPL
STDOUT channel works:
...
Who? | What Test the tasks described above in your assigned environment below. | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Jeremy | Ubuntu 16.04 LTS Results (DEB):
Comments: | Fedora 27 VM Results (RPM):
Comments: | Debian Stable VM Results (DEB):
Comments: | I can't see my cursor/text after I exit using CTRL-C from REPL 1GB Ubuntu VM 2GB Debian VM 4GB Fedora VM Ubuntu LTS baremetal 32GB | ||||||||||||||||
Henry | Debian Stable VM (1 GB RAM, 1 CPU): (DEB, Binary Tarball) Results (Binary Tarball):
Results (DEB):
| Fedora Laptop (8 GB RAM, 4 CPU) (RPM, Binary Tarball) Results (Binary Tarball):
Results (RPM):
| Comments: Still seeing NPE when I exit REPL with CTRL-C
Eval works "as advertised" but it is really counterintuitive to have to provide the absolute path to a file on the server, rather than client. Jeremy and I evaluated every file in the top-level of We should exit immediately with status code >= 1 and error message when libsodium is not found:
| |||||||||||||||||
Medha | Test docker 1 CPU, 1 GB RAM | Results (Docker)
| Comments: If the path is wrong in eval mode, exception is not returned to user. Exception appears on server side. Need to file a ticket.
Casper issue, at some point the same block is passed around (observed at block 8) Starting standalone mode after having been in connected mode results in: 17:35:55.795 [main] INFO logger - Starting stand-alone node. 17:36:04.044 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352}) 17:36:04.061 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352}) 17:36:10.500 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5}) 17:36:10.506 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5}) 17:36:10.512 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352}) 17:36:10.517 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5}) 17:36:10.520 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352}) 17:36:44.116 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352}) 17:36:44.127 [repl-io-27] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352}) 17:36:50.709 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5}) 17:36:50.715 [repl-io-27] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5}) 17:36:50.725 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})
| |||||||||||||||||
Mateusz | Ubuntu 16.04 (8 CPU 32GB RAM)
Comments: Still seeing NPE when I exit REPL with CTRL-C | |||||||||||||||||||
Michael Birch | test locally with dev | assembly jar docker Result: Both work fine (modulo NPE on exit of repl via ^D) | ||||||||||||||||||
Sebastian | test locally with dev | test docker with dev |
...