Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several updates, including configuration changes, improvements to presence handling in the
RealtimeChannelmodule, and minor code cleanups. The most significant changes focus on enhancing functionality and simplifying the codebase for better maintainability.Configuration Updates:
urlconfiguration forlogflare_logger_backendfromconfig/config.exstoconfig/runtime.exs, allowing it to be set dynamically via theLOGFLARE_LOGGER_BACKEND_URLenvironment variable. This improves flexibility in different environments. [1] [2]Presence Handling Improvements:
presence_list_shard_bypassfunction with a newpresence_dirty_listfunction in theRealtimeChannelmodule. This simplifies the logic for fetching and grouping presence data and removes error handling for shard bypass. [1] [2]Code Cleanups:
importstatement in thePromExmodule, improving code clarity.IO.inspectstatement from theRealtimeChannelmodule to clean up logging.Metric Unit Adjustment:
unitfield for logical replication slot polling queries in theTenantPromEx plugin to use{:microsecond, :millisecond}for better precision.Version Update:
2.9.0to2.9.4in themix.exsfile to reflect the changes.