By default setting rerate to true also sets refund to true, but
flags should take precedence over defaults.
If rerate is true and refund is false, remove any previous
CostDetails from event to force rerate.
Centralize the parsing of processing flags.
This 'can't find service' error is harmless and occurs due to a
mismatch between the standard net/rpc server and the cgrates/birpc
client. The standard server does not support context cancellation
requests sent by the client.
Fixes#4357
Fixes an issue where 0 values would become empty inside the cron
expressions.
Added unit tests for the edge cases and grouped them together with
the previous ones under the same table test.
Previously made two trips (get and set) for each group of items from
an index key being removed. Now, we fetch indexes once at the beginning
and store the updated indexes once at the end.
Related to #4357
Git 2.45+ introduced a backward incompatible change in the iso-strict
date format, showing time in the Zulu timezone with "Z" suffix instead
of "+00:00". This commit adds parsing for the new date format before
falling back to the old format.
Revise GetCGRVersion error messages.
Revise GetCGRVersion unit test.
200 -> 16
Previously, considering the fibonacci back off strategy, if engine failed to
start it would have tried to attempt connections for 2.862799e+33 years.
Now, the amount of attempts is 16, equivalent to around 2 and a half seconds.
Should be more than enough, considering that usually 6-7 attempts are enough.
The rpcclient constructor could not see the centralized
Encoding flag because it didn't have the necessary build
constraints. Added the constraints in lib_test.go files
where it wasn't alone. In all the other cases, it was
moved to the first file where it was needed.
Moved resources cache tests relying on DBType flag value
to a separate integration test file. Before it was getting
skipped for *internal anyway.