You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently missing tests that exercise all the code and behavior involved:
Supervision tree
Accepting connections and receiving traffic for the different protocol versions.
KPL aggregated records (as sent by KCL)
Records that are neither KPL/Custom KPL (as sent by KCL)
We do have some tests that actually run some parts of the code, but a good set of integration tests would come in handy (to test incoming data from KCL, how the code behaves and interacts with our users).
Something that can be used for this is to have a small tool built in our tests that will actually connect to the erlmld server, send traffic, and assert the behavior at different parts of the code. In addition, creating some implementations of the erlmld behaviors to make those assertions and test (between other things) checkpointing, etc.
The text was updated successfully, but these errors were encountered:
To control if it should or not deflate, the library was
accepting a flag on kpl_agg:finish/2.
But, this wasn't applied to aggregated records created implicitly
when adding new items.
This PR makes the should_deflate part of the state, and allow it
to be initialized using kpl_agg:new/1 (default is to not deflate).
Note:
It has a backward incompatible change, as kpl_agg:finish/2 is removed.
* make the should_deflate flag part of the state (#2)
To control if it should or not deflate, the library was
accepting a flag on kpl_agg:finish/2.
But, this wasn't applied to aggregated records created implicitly
when adding new items.
This PR makes the should_deflate part of the state, and allow it
to be initialized using kpl_agg:new/1 (default is to not deflate).
Note:
It has a backward incompatible change, as kpl_agg:finish/2 is removed.
* Avoid cuadratic complexity, keep track of current list length (#3)
Do not calculate length(List) on each item addition, keep a track
of the current buffer length.
* Remove dialyzer warnings
* Fix #stream_record.timestamp type
We're currently missing tests that exercise all the code and behavior involved:
We do have some tests that actually run some parts of the code, but a good set of integration tests would come in handy (to test incoming data from KCL, how the code behaves and interacts with our users).
Something that can be used for this is to have a small tool built in our tests that will actually connect to the erlmld server, send traffic, and assert the behavior at different parts of the code. In addition, creating some implementations of the erlmld behaviors to make those assertions and test (between other things) checkpointing, etc.
The text was updated successfully, but these errors were encountered: