Paweł Pacana

Aside to running tests on CI, I've scoped down the test run to `ruby_event_store` and it fails on: ```ruby rspec ./spec/batch_enumerator_spec.rb:22 # RubyEventStore::BatchEnumerator rspec ./spec/batch_enumerator_spec.rb:50 # RubyEventStore::BatchEnumerator should receive call(kind...

```ruby irb(main):003:0> (0...Float::INFINITY).step(1).next ArgumentError: Infinite or NaN ```

To be revisited after oracle/truffleruby#1503 and #422 (comment) are solved.

Let's check this in what's left from 2020

@LifeIsStrange one minor issue in `ruby_event_store` gem (in test code) that would require reporting in TruffleRuby tracker: an instance of what is Integer on MRI is a Float under Truffleruby....

Possibly related to #335

First of all we do not allow events with duplicate ids, regardless of stream. We allow linking to multiple streams but also disallow linking to same event twice. For both...

At least communicating event_id would definitely help

Related: https://ruby-doc.org/core-2.5.0/Object.html#method-i-inspect

> What's stopping us here? Probably one more rebase since I had to resurrect separate CSS assets for [#1346] 🙃 I'd love to have it to experiment with some browser...