state_machines | Adds support for creating state machines

RSpec verifying proxy in validate_arguments! getting call for post_activate with current transition. You can see it if you add something like byebug to your Gemfile, and add same byebug conditionally into validate_arguments! of Rspec:

You can accept an argument on your before_transition callback and obtain all data you need to implement an expected behaviour.

The code which passes the argument you can find at the source code of the library. You can implement this logic with around_transition as well.

The problem is that json_query filter expects to get a dictionary with ascii strings, but what you're providing it are unicode strings (notice the u'blabla' in your input).

This is an issue with json_query that apparently got introduced in Ansible 2.2.1 (although that is not really clear), here are some more details: https://github.com/ansible/ansible/issues/20379#issuecomment-284034650

I hope this gets fixed in a future version, but for now this is a workaround that worked for us:

I fixed this by removing the OBJECT target and just creating a static library.

This issue may reveal something to you:

https://github.com/activerecord-hackery/polyamorous/issues/34

After reading it, I would grep through your project for references to make_constraints, as it seems something has changed in 5.2 with regard to it that would lead to a similar error.

Or, if you see the polyamorous gem in your Gemfile.lock, problem solved, just update the gem as they fixed it in January.

Actually the problem was that i developed it on windows and was deploying to ubuntu. So the native gems were not being installed. when i added the required platforms in the gemfile and ran bundle install the app was working fine

As you suspect, the error is arising in print-map, which calls seq on its argument and then calls key and val on each element of that sequence. As the error message states, these two functions expect their argument to conform to the java.util.Map$Entry interface, and Clojure vectors do not conform to that interface.

The solution is to take the [k v] in your as-pairs function and replace it with an expression that creates a map entry; see this question for details.

...it looks to me that 'output' will be in a undefined state until 'input' transitions to '1'.

No (see below). At the beginning of the simulation, output will immediately take value "00", even if the reset is not asserted and there is no transition on input.

Isn't that bad practice, considering this is an official example from Altera ?

No, this code is fine. The state register (state) can be properly initialized, thanks to the reset, and output combinatorialy depends on state. This model will behave as expected, both in simulation and in hardware.

And by the way, what would be the proper way of initializing 'output' here ? With async reset ?

You don't initialize outputs of combinatorials with reset. Resets (asynchronous or synchronous) are used to initialize registers (state, in your example).

Sensitivity lists are just syntactical sugar. A process with sensitivity list is equivalent to the same process, without sensitivity list, and with a wait on ; as the last statement. Example: