andrew-rosca

Sometimes ksqlDB queries run against Kafka topics return no results, or fewer messages than expected. This can happen because ksqlDB is unable to deserialize messages successfully.

ksqlDB writes deserialization error messages to a dedicated topic, and exposes stream KSQL_PROCESSING_LOG to make them queriable. However, the messages from this topic are not very easy to interpret, among other things because the original record that failed deserialization is base64-encoded.

SELECT * FROM KSQL_PROCESSING_LOG LIMIT 1;

{

andrew-rosca

import backtrader as bt
import pandas as pd
from io import StringIO

class TestStrategy(bt.Strategy):
    def next(self):
        if self.position.size == 0:
            self.buy(size=10)
        else:
            self.sell(size=10)

andrew-rosca

Keybase proof

I hereby claim:

• I am andrew-rosca on github.
• I am arosca (https://keybase.io/arosca) on keybase.
• I have a public key ASBP7CKi-YRAGKBiRa76Geg0t2Q6kizhNQZOH1ihsusvZQo

To claim this, I am signing this object:

andrew-rosca

vagrant@ubuntu-bionic:~$ minishift start --show-libmachine-logs -v5
-- minishift version: v1.29.0+72fa7b2
-- Starting profile 'minishift'
Found binary path at /usr/local/bin/docker-machine-driver-kvm
Launching plugin server for driver kvm
Plugin server listening at address 127.0.0.1:45975
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName