Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⬆️ Update emqx/emqx to v5.8.4 #125

Merged
merged 1 commit into from
Dec 27, 2024
Merged

⬆️ Update emqx/emqx to v5.8.4 #125

merged 1 commit into from
Dec 27, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 27, 2024

This PR contains the following updates:

Package Update Change
emqx/emqx patch v5.8.3 -> v5.8.4

Release Notes

emqx/emqx (emqx/emqx)

v5.8.4: EMQX v5.8.4

Compare Source

v5.8.4

Make sure to check the breaking changes and known issues before upgrading to EMQX 5.8.4.

Enhancements

  • #​13739 Support clear monitor (statistics) data for the whole cluster.

    Send DELETE request to endpoint api/v5/monitor to clear all collected monitoring metrics.

  • #​14247 Write client attribute named tns to log messages if such client attribute exists.

  • #​14269 Added etc/base.hocon config file.

    In this release, we introduced a new configuration file, etc/base.hocon, to enhance configuration management and clarity.

    Previously, since emqx.conf was the only place for manually crafted configurations, and because it sits at the top-most layer
    of the configuration override system, it caused some confusion.
    While mutable (not read-only) configurations set in emqx.conf could be changed through the UI, API, or CLI and take effect immediately,
    those changes would not persist after a node restart — leading to inconsistent behavior.

    To address this, we’ve added etc/base.hocon as a foundational configuration layer.
    The updated configuration precedence order, from top to bottom, is as follows:

    1. Environment variables
    2. etc/emqx.conf
    3. data/configs/cluster.hocon
    4. etc/base.hocon

    The etc/base.hocon file serves as the base layer for configurations.
    While settings defined here can still be modified after the node starts,
    this layer ensures consistent override behavior.

  • #​14353 Make session rebalance and evacuation more robust. Previously, session evacuation could enter a dead loop after some clustering errors.

  • #​14360 Added listener shutdown counts labeled by shutdown reason to Prometheus metrics, under the emqx_client_disconnected_reason counters.

    Example output:

    emqx_client_disconnected_reason{node="[email protected]",reason="takenover"} 1
    emqx_client_disconnected_reason{node="[email protected]",reason="kicked"} 1
    

    Currently, this feature is limited to TCP and TLS listeners only.

  • #​14369 Introduced two size-related functions in the rule engine:

    • is_empty : return true if the map or array is empty
    • map_size : return the size of a map

Bug Fixes

  • #​14248 Fixed a class of issues where intermittent connectivity issues between cluster nodes could potentially cause partial loss of cluster-wide routing table state.

  • #​14267 Do not redact secrets in logs and HTTP responses when the secret string is a file path (file:///path/to/the/secret).

  • #​14272 auto_subscribe configuration loaded via CLI shows success but fails to take effect.

  • #​14317 Prevent potential issues where APIs involving paging may return empty pages, in case the internal APIs will be subtly misused in the future.

  • #​14318 Fixed the initialization of the HTTP connector state. When there was incoming traffic being handled by an HTTP action and its underlying connector restarted, cryptic crashes could be seen in the logs mentioning function_clause.

    Example:

    20:42:36.850 [error] msg: "resource_exception", info: #{error => {error, function_clause}, id => <<"action:http:a:connector:http:a">>, name => call_query, ...
    
  • #​14319 Refactored resource management internal state machine. As consequence, some race condition bugs have been eliminated. One such example is the HTTP action, which, when under incoming traffic and when its health check flap, may produce errors like the following:

    2024-11-29T14:58:17.994119+00:00 [error] msg: action_not_found, connector: <<"connector:http:a">>, action_id: <<"action:http:a:connector:http:a">>
    
  • #​14357 Fix bin/emqx help command.

  • #​14362 Refactored data integration resource manager state machine, which should eliminate a few race conditions that could lead to inconsistent states.

  • #​14371 Fix clientid override expression to render undefined as empty string.

  • #​14376 Made config import to tolerate non-existing log file dir.

    If log file handler is configured with a non-existing dir, the default value it will fallback to the default value "${EMQX_LOG_DIR}".

  • #​14424 Eliminated a false warning level "unexpected_info" log message.

  • #​14429 Fixed handling of rule action metrics when an underlying connector is disabled. Before the fix, the failed counter would be bumped twice for each message the action received (one categorized under unknown and another under out_of_service). Now, only out_of_service is bumped.

Breaking Changes

  • #​14360 When requesting Prometheus metrics in JSON format, now the client top-level key will always be an array of JSON objects instead of a single JSON object.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot. labels Dec 27, 2024
Copy link

coderabbitai bot commented Dec 27, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@frenck frenck merged commit 99489ba into main Dec 27, 2024
21 checks passed
@renovate renovate bot deleted the renovate/emqx-emqx-5.x branch December 27, 2024 06:53
@github-actions github-actions bot locked and limited conversation to collaborators Dec 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant