pico-engine icon indicating copy to clipboard operation
pico-engine copied to clipboard

An implementation of the pico-engine hosted on node.js

Results 100 pico-engine issues
Sort by recently updated
recently updated
newest added

wrangler captures the pico name during the pico creation process subsequent changes of the name in the developer UI do not make their way into wrangler

bug

Currently a rule like this one ``` rule test_foreach { select when foreach content content re#(.+)# setting(content) foreach content.split(":") setting(string) send_directive("content",{"substring":string}) } ``` sees the name `content` bound to the...

bug
language fix

enhancement
good first issue

See discussion [here](https://picolabs.atlassian.net/wiki/spaces/PLM/pages/1694433657/Discussion+of+evaluation+algorithms), in which I attempted to prove that v0 and v1 had equivalent semantics. Included therein is a small ruleset which can be compiled, installed, and used in...

bug

Issue #536 did the desired filtering out of visual clutter. This issue is about having a widget in the Logging tab where the developer could select desired filtering. Such as...

enhancement

So that a clever ruleset could keep track of its version in an entity variable. Then, when a flush happens that upgrades the version, a rule could migrate the other...

enhancement

Phi wrote, "Seems like the definedness checker that is part of the parser is single pass, so names must be declared before they are used (textually, not temporally). That’s probably...

enhancement
question

A couple of things could make it more useful 1. Remove the Tx_host and password boxes for a new subscription 2. Show the tags of the Rx channel beside the...

enhancement
UI

Actions and defactions can return a result, which can be bound to a name with a `setting` clause. Often the result isn't directly useful to subsequent actions in the sequence...

enhancement
question
language fix

From Phil: Failing silently is tough on programmers. If we checked to ensure the name is present in the test rather than the eventex, then we could at least put...

bug