Austin Godber
Austin Godber
Here's a slice error from the case where the link between the Teraslice worker and the S3 style server was broken. ``` TSError: Kafka Client is in an invalid state...
Here's the error on the first slice that failed on the 5/16 incident, which was a route dropped incident, I believe the job was paused, then resumed, then individual workers...
Here's a log snippet from a worker log:, I'm not sure if this is the same `AggregateError` as shown above or not ``` A slice error occurred { slice: {...
We are seeing similar or identical errors here when this happens. ``` "assets": [ "standard:1.6.1", "file:v3.2.2", "kafka:5.10.0" ], "kubernetes_image": "ghcr.io/terascope/teraslice:v2.17.2-nodev22.17.1", ``` Here's the error stored on the failed slices ```...
There's an argument that this could be a `--diff` option on the `view` subcommand.
I don't recall the exact context/use case for this but it does sound like useful information to have. It is a concrete piece of information that is determined at execution...
This might help https://nx.dev/
But changing to it might be a huge hassle.
This is a pretty lengthy read but it provides good insights: https://martinfowler.com/articles/branching-patterns.html In particular I think he makes a good case for continuous integration, though maybe it's not worth it....
Ok, here are the scenarios we need to consider: * Hotfix needed in production (v2.x) * Bug found in both v2.x and v3.x * Feature request for old version *...