profile
viewpoint

lovoo/goka 1611

Goka is a compact yet powerful distributed stream processing library for Apache Kafka written in Go.

frairon/goka-godays2019 4

Goka Workshop for Godays 2019

db7/barrier 2

A barrier to synchronize a group of goroutines with an optional callback executed in isolation.

db7/bloom 0

Go package implementing Bloom filters

db7/cofire 0

An online Collaborative Filtering system for recommendations

db7/goka 0

Goka is a compact yet powerful distributed stream processing library for Apache Kafka written in Go.

db7/kazoo-go 0

Go library to access Kafka metadata in Zookeeper

db7/mockery 0

A mock code autogenerator for golang

db7/qmk_firmware 0

Open-source keyboard firmware for Atmel AVR and Arm USB families

push eventlovoo/goka

frairon

commit sha 09b1e04502f0a2415c1f199bc6e154330cd29278

Improve topic creation via topic manager fixed flaky tests by not resetting mockconsumergroup on close (not reused anyway) small fix to append to slices in GroupGraph

view details

push time in 9 hours

PR opened lovoo/goka

topic-manager improvements
+1060 -268

0 comment

15 changed files

pr created time in 9 hours

create barnchlovoo/goka

branch : improve-topicmanager-creation

created branch time in 9 hours

delete branch lovoo/goka

delete branch : LVPD-735-topic-fix

delete time in a day

PR closed lovoo/goka

LVPD-843 topic manager improvements
+1039 -268

0 comment

15 changed files

frairon

pr closed time in a day

PR opened lovoo/goka

LVPD-843 topic manager improvements
+1039 -268

0 comment

15 changed files

pr created time in a day

push eventlovoo/goka

Henri Koski

commit sha d905e7965f0480790a0c71466ccf2d5c21a46a4c

Use Go format for examples in README

view details

Jan Bickel

commit sha aa579ba792f414859c5ea2bb73aa7af7563875cd

Merge pull request #295 from heppu/patch-1 Use Go format for examples in README

view details

Jan Bickel

commit sha 55fae71f2c08188e4938ec9a7696830e29524d4b

Cleanup redis and monitoring example

view details

Jan Bickel

commit sha f8cff2d6658e8e08a4fdb08de10a548c8480950a

Merge pull request #294 from lovoo/redis-example-cleanup Cleanup redis and monitoring example

view details

frairon

commit sha 2b79ae1c9b9843185663d2c396267d1ab697aab4

wip topic fix

view details

frairon

commit sha d9b2c5b50b52dc17b46f35052d337d52a39a769d

LVPD-735 improve topic creation via topic manager fixed flaky tests by not resetting mockconsumergroup on close (not reused anyway) small fix to append to slices in GroupGraph

view details

push time in a day

PR closed willf/bloom

Fix link to murmurhash
+1 -1

1 comment

1 changed file

nak3

pr closed time in 6 days

delete branch lovoo/goka

delete branch : redis-example-cleanup

delete time in 6 days

push eventlovoo/goka

Jan Bickel

commit sha 55fae71f2c08188e4938ec9a7696830e29524d4b

Cleanup redis and monitoring example

view details

Jan Bickel

commit sha f8cff2d6658e8e08a4fdb08de10a548c8480950a

Merge pull request #294 from lovoo/redis-example-cleanup Cleanup redis and monitoring example

view details

push time in 6 days

PR merged lovoo/goka

Cleanup redis and monitoring example
+53 -73

0 comment

16 changed files

R053NR07

pr closed time in 6 days

push eventlovoo/goka

Jan Bickel

commit sha 55fae71f2c08188e4938ec9a7696830e29524d4b

Cleanup redis and monitoring example

view details

push time in 7 days

Pull request review commentlovoo/goka

Cleanup redis and monitoring example

+# Redis storage example++Using [Redis](https://redis.io/) as option of storage.++This example has an **Emitter** and one **Processor** with when this emitter+generates events with random keys (_user_id_) consumed by Kafka that uses+Redis as storage/cache.+++## Usage++Run a local Kafka cluster and redis server by calling `make start` in folder `examples/`.+This will start a kafka cluster accessible under `127.0.0.1:9092` and a redis service under+`127.0.0.1:6379` if you want to use a different configuration you need to adjust the config +file `config.yaml`.++The config file also has some more options to set:++```yaml+kafka:+  brokers:+    - "127.0.0.1:9092"+    group: "examples"+    stream: "events"+    redis: "127.0.0.1:6379"+    namespace: "producer"+```++Where:+  * **brokers** : slice of kafka brokers hosts.+  * **group** : group name of this example belongs.+  * **stream**: stream name of this example belongs.+  * **redis**: address of redis (`localhost:6379`).+  * **namespace**: namespace distinguish applications that write to the same keys on Redis.++After starting the machines and adjusting the config run the example with+`go run 7-redis/*.go -config 7-redis/config.yaml`.++The events are produced and consumed by Kafka with random keys. It's possible+run several of the same binary and check the behaviour of kafka+rebalancing and removing partitions without broken.

without broken, what does that mean?

R053NR07

comment created time in 7 days

Pull request review commentlovoo/goka

Cleanup redis and monitoring example

+# Redis storage example++Using [Redis](https://redis.io/) as option of storage.++This example has an **Emitter** and one **Processor** with when this emitter

"with when this" sounds strange. Did you forget a word or have too many? Not sure what you meant here :)

R053NR07

comment created time in 7 days

Pull request review commentlovoo/goka

Cleanup redis and monitoring example

+# Redis storage example++Using [Redis](https://redis.io/) as option of storage.++This example has an **Emitter** and one **Processor** with when this emitter+generates events with random keys (_user_id_) consumed by Kafka that uses+Redis as storage/cache.+++## Usage++Run a local Kafka cluster and redis server by calling `make start` in folder `examples/`.+This will start a kafka cluster accessible under `127.0.0.1:9092` and a redis service under+`127.0.0.1:6379` if you want to use a different configuration you need to adjust the config +file `config.yaml`.++The config file also has some more options to set:++```yaml+kafka:+  brokers:+    - "127.0.0.1:9092"+    group: "examples"

lines 23 to 26 need to be unindented one step to make it consistent with the actual config.yaml

R053NR07

comment created time in 7 days

push eventlovoo/goka

Henri Koski

commit sha d905e7965f0480790a0c71466ccf2d5c21a46a4c

Use Go format for examples in README

view details

Jan Bickel

commit sha aa579ba792f414859c5ea2bb73aa7af7563875cd

Merge pull request #295 from heppu/patch-1 Use Go format for examples in README

view details

push time in 8 days

PR merged lovoo/goka

Use Go format for examples in README
+2 -2

1 comment

1 changed file

heppu

pr closed time in 8 days

issue openedMPI-SWS/genmc

Stack variable and printf cause crash

#include <assert.h>
#include <stdio.h>

#define LEN 4

int main()
{ 
    int i = 6;
    printf("%d",i); // works
    char str[LEN] = {'%', 'd', 0};
    printf("%s",str); // crash
    printf(str, i); // would also crash
}

The crash also occurs without the initializer (using some other way to set up str). The crash does not occur if str is changed to static storage duration (I've tried both using the static keyword and moving it outside the function).

created time in 9 days

issue closedMPI-SWS/genmc

segmentation fault for initializers on stack

Repeating the problem from memory: when placed on locals in a function call,

 int x[4] = {0};
 my_struct x = { .a = 3, .y = 2 };

and friends all crash. Let me know if you need a full test case.

closed time in 9 days

JonasOberhauser

issue commentMPI-SWS/genmc

segmentation fault for initializers on stack

This is an old issue that has been fixed.

JonasOberhauser

comment created time in 9 days

pull request commentlovoo/goka

Use Go format for examples in README

Seems like we missed that. Thanks :)

heppu

comment created time in 9 days

PR opened lovoo/goka

Use Go format for examples in README
+2 -2

0 comment

1 changed file

pr created time in 9 days

issue openedMPI-SWS/genmc

segmentation fault for initializers

From memory,

 int x[4] = {0};
 my_struct x = { .a = 3, .y = 2 };

and friends all crash. Let me know if you need a full test case.

created time in 9 days

issue openedMPI-SWS/genmc

support full pthreads

CVs, recursive locks, ...

created time in 9 days

PR opened lovoo/goka

Cleanup redis and monitoring example
+53 -73

0 comment

16 changed files

pr created time in 9 days

create barnchlovoo/goka

branch : redis-example-cleanup

created branch time in 9 days

issue openedMPI-SWS/genmc

Support realloc

created time in 10 days

push eventlovoo/goka

frairon

commit sha 555c7788ed289d9290841b0106fe5a18f84d9ac1

LVPD-843 callback error leads to processor shutdown

view details

Thomas Linford

commit sha fd018080780f48cad545e0d88651e4a56abc2e82

fix topic manager stream retention not in milliseconds

view details

Franz Eichhorn

commit sha 5092fdc76776fd49b30c6e35b5fe516c17e85706

Merge pull request #291 from lovoo/LVPD-843-stuck-shutdown LVPD-843 callback error leads to processor shutdown

view details

Franz Eichhorn

commit sha 569d2e77a845555730d28f199ccce666954f98df

Merge pull request #293 from tlinford/master fix topic manager stream retention not in milliseconds

view details

frairon

commit sha 5e22ac16fadc6782062c1036c0b4b44c98252270

wip topic fix

view details

push time in 16 days

issue openedMPI-SWS/genmc

Print a non-termination warning if the graph becomes too large

Spin-Assume transformation does not apply to all blocking loops. These loops will be unrolled over and over without any graph being produced. Inexperienced users of GenMC get confused by the lack of output and have not idea what's happening. My suggestion is that if the execution graph grows too much due to repeated unrolling (e.g., 1000 times) of a loop with atomic events, GenMC should print a single warning message informing the user that there might be a non-terminating blocking loop in lines XXX-YYY which might prevent GenMC from terminating on this program, and that the user can use "__VERIFIER_assume(false);" or "--unroll=XXX" to truncate the search space.

created time in 16 days

push eventlovoo/goka

Thomas Linford

commit sha fd018080780f48cad545e0d88651e4a56abc2e82

fix topic manager stream retention not in milliseconds

view details

Franz Eichhorn

commit sha 569d2e77a845555730d28f199ccce666954f98df

Merge pull request #293 from tlinford/master fix topic manager stream retention not in milliseconds

view details

push time in a month

more