Adrian Madrid
Adrian Madrid
@larskluge thx! I've looked at implementing 1hashify1/etc for pipelines/futures but I cannot seem to get it to work. Not sure how you feel about having streams not working there.
@stefanwille it does pass locally. I think the problem is that travis doesn't have the right redis version (>= 5). BTW I figured out a solution to the pipeline issue...
I've added a PR #78 that starts the process of supporting streams. @larskluge please check it out and let me know what you think.
@larskluge I've looked at implementing hashify for futures but I cannot quite get the hang of it. That affects how useful streams will be. For me living without pipeline/future support...
Not looking good. Could you give us some way to replicate the tests?
@waghanza I got an error in benchmarker because `kore.io` did not have a language version. I had to change benhmarker around line 74 to: ```crystal if row.has_key?("language") && row.has_key?("version") target...
I'd prefer being able to annotate endpoints with a DSL instead of annotations. They just look ugly to me: add a lot of noise that a clean DSL could clean...
same problem here.
We worked around it by passing the orderid option around in our local copy of the code. We started using two different vault types but are just using one lately...
This seems like a bottleneck to publishing. Unless I'm missing something it is sending a create topic request for every single publish call. By having an arn cache we can...