Ralph Weires

It's really an awful amount of clutter that's added by this inadvertently - would be nice to have this removed again without having to declare exclusions in all projects depending...

> Please check result of ITs - and fix ITs or code according I'd be happy to, but I'm unable to run the ITs locally to do this in the...

> Can you show me more logs for your erro: > > > Failed to install project dependencies: MavenProject: org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M10-SNAPSHOT > > [...] > > cannot install /home/me/.m2/repository/org/apache/maven/maven-parent/36/maven-parent-36.pom to same...

> very strange ... when I build from master I have different plugin versions: > > ``` > INFO] --- jar:3.3.0:jar (default-jar) @ maven-failsafe-plugin --- > [INFO] Building jar: /Users/slawomir.jaranowski/repos/apache/maven-surefire/maven-failsafe-plugin/target/maven-failsafe-plugin-3.0.0-M10-SNAPSHOT.jar...

As follow-up: The sequence numbers can even go backwards. Encountered this sequence of messages earlier today (`q: 587` is clearly out-of-order) ``` {"ev":"T","sym":"MPNGY","i":"00000930","x":62,"p":35.55,"s":10,"c":[12,37],"t":1679661689099,"q":586,"z":3} {"ev":"T","sym":"MPNGY","i":"00000934","x":62,"p":35.43,"s":20,"c":[12,37],"t":1679661689099,"q":588,"z":3} {"ev":"T","sym":"MPNGY","i":"00000932","x":62,"p":35.475,"s":2,"c":[12,37],"t":1679661689099,"q":587,"z":3}

@jrbell19 - sure, here you go: - For the first instances (duplicate sequence numbers, initial ticket description): `0a58bf54-f4fc-4e48-af22-2dd35d078902` - For the decreasing sequence number today: `9f4789f9-32dd-409c-935c-5f44b37e9bd2`

FWIW - I have some further instances of messages with duplicate sequence-numbers, also in (currently-active) connection `4f1fc134-eb60-4583-861e-43bd740db96a`. About 10 minutes ago (around epoch-second `1679924700`) there was a whole batch of...

And several further instances of sequence numbers going backwards, from today (still from same connection `4f1fc134-eb60-4583-861e-43bd740db96a`, now-inactive) ``` {"ev":"Q","sym":"PRPL","i":[604],"bx":11,"ax":12,"bp":2.62,"ap":2.75,"bs":1,"as":5,"t":1679961429122,"q":95506673,"z":3} {"ev":"Q","sym":"PRPL","i":[604],"bx":11,"ax":12,"bp":2.62,"ap":2.72,"bs":1,"as":3,"t":1679961594712,"q":95510132,"z":3}

Hi @jrbell19 - still wondering here, any update / input you could give on these issues? I'd like to understand, for a given stream that's subscribed to `T.*,Q.*` (delayed stream):...

> [....] easily introduce a feature that "calculates" the target partition id for a given key? +1 for adding this somewhere. A simple way to find the right partition for...