Mochi Co Mqtt Versions Save

What's Changed

• add 0x04 Reason Code functionality by @dgduncan in https://github.com/mochi-mqtt/server/pull/395
• Update README example to reflect new listeners API by @thedevop in https://github.com/mochi-mqtt/server/pull/389
• Add logging level file config by @dgduncan in https://github.com/mochi-mqtt/server/pull/396
• Bump golang.org/x/net from 0.17.0 to 0.23.0 by @dependabot in https://github.com/mochi-mqtt/server/pull/388
• Bypassing asdine/storm and directly using bbolt. by @werbenhu in https://github.com/mochi-mqtt/server/pull/392

Lots of good updates, with many thanks to @dgduncan @werbenhu @thedevop!

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.6.2...v2.6.3

What's Changed

• Ability to limit maximum number of clients by @thedevop in https://github.com/mochi-mqtt/server/pull/379
• Fixed inline subscribers not receiving messages when all non-inline clients unsubscribe. by @werbenhu in https://github.com/mochi-mqtt/server/pull/386

Thank you @thedevop and @werbenhu !

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.6.1...v2.6.2

What's Changed

• Translate README.md into Chinese version. by @werbenhu in https://github.com/mochi-mqtt/server/pull/373
• Add a persistence hook based on cockroachdb/pebble. by @werbenhu in https://github.com/mochi-mqtt/server/pull/378
• Replace badgerhold with directly using BadgerDB v4 by @werbenhu in https://github.com/mochi-mqtt/server/pull/376

Thank you @werbenhu !

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.6.0...v2.6.1

What's Changed

Be advised - this release includes a breaking change for the Docker image which may be fixed in the future.

• Bump google.golang.org/protobuf from 1.28.1 to 1.33.0 by @dependabot in https://github.com/mochi-mqtt/server/pull/372
• Add BadgerDB garbage collection. by @werbenhu in https://github.com/mochi-mqtt/server/pull/371, which prevents the Badger log file from growing infinitely, resolving issues https://github.com/mochi-mqtt/server/issues/370, https://github.com/mochi-mqtt/server/issues/369, and https://github.com/mochi-mqtt/server/issues/363
• Implement File based configuration by @mochi-co in https://github.com/mochi-mqtt/server/pull/351, which adds a file-based configuration allowing server options, hooks, and listeners to be configured by yaml or json file.
  • As a result of this change, the docker image now requires a configuration file to be specified with the parameter-v $(pwd)/config.yaml:/config.yaml.

File Based Configuration

You can use File Based Configuration with either the Docker image (noted above), or by running the build binary with the --config=config.yaml or --config=config.json parameter.

Configuration files provide a convenient mechanism for easily preparing a server with the most common configurations. You can enable and configure built-in hooks and listeners, and specify server options and compatibilities:

listeners:
  - type: "tcp"
    id: "tcp12"
    address: ":1883"
  - type: "ws"
    id: "ws1"
    address: ":1882"
  - type: "sysinfo"
    id: "stats"
    address: ":1880"
hooks:
  auth:
    allow_all: true
options:
  inline_client: true

Please review the examples found in examples/config for all available configuration options.

There are a few conditions to note:

1. If you use file-based configuration, you can only have one of each hook type.
2. You can only use built in hooks with file-based configuration, as the type and configuration structure needs to be known by the server in order for it to be applied.
3. You can only use built in listeners, for the reasons above.

If you need to implement custom hooks or listeners, please do so using the traditional manner indicated in cmd/main.go.

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.6...v2.6.0

What's Changed

• Replace DefaultServerCapabilities with NewDefaultServerCapabilities()… by @thedevop in https://github.com/mochi-mqtt/server/pull/360, resolving data races in tests.
• Only pass a copy of system.Info to hooks by @thedevop in https://github.com/mochi-mqtt/server/pull/365, resolves #364 and race conditions in hooks that call system.Info directly.
• Allow configurable max stored qos > 0 messages by @thedevop in https://github.com/mochi-mqtt/server/pull/359, resolves #340, in which inflight messages were mismatched against the client message quota, causing a performance bottleneck.

Many thanks @thedevop!

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.5...v2.4.6

What's Changed

• Fix #349, MQTT v3 unsuback does not require Reason Code by @werbenhu in https://github.com/mochi-mqtt/server/pull/353
• Buffer optimizations by @thedevop in https://github.com/mochi-mqtt/server/pull/355

A couple of small improvements, thank you @werbenhu and @thedevop! 🙂

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.4...v2.4.5

What's Changed

• Fix data race issue with write buffer by @thedevop in https://github.com/mochi-mqtt/server/pull/347
• Packet encoding optimization by @thedevop in https://github.com/mochi-mqtt/server/pull/343, which should provide small but meaningful performance improvements at scale.
• feat: return tcp.Address from listener, if exists by @AeroNotix in https://github.com/mochi-mqtt/server/pull/336, to correctly allow use of port 0 for random port assignments.
• Move cl.WriteLoop() to attachClient() and call cl.Stop() in loadClients() to update client.State. by @werbenhu in https://github.com/mochi-mqtt/server/pull/344, to prevent goroutine leaks.

New Contributors

• @AeroNotix made their first contribution in https://github.com/mochi-mqtt/server/pull/336

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.3...v2.4.4

What's Changed

• Demo how to subscribe and publish directly within examples/hooks. by @werbenhu in https://github.com/mochi-mqtt/server/pull/333
• Add a Japanese version of README.md by @heya-naohiro in https://github.com/mochi-mqtt/server/pull/338
• Dynamically allocate write buffer if needed. (ready for merge) by @thedevop in https://github.com/mochi-mqtt/server/pull/324
• Handle expired clients in server.loadClients(). by @werbenhu in https://github.com/mochi-mqtt/server/pull/341

New Contributors

• @heya-naohiro made their first contribution in https://github.com/mochi-mqtt/server/pull/338

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.2...v2.4.3

What's Changed

• update README-CN.md by @werbenhu in https://github.com/mochi-mqtt/server/pull/312
• Bump golang.org/x/net from 0.7.0 to 0.17.0 by @dependabot in https://github.com/mochi-mqtt/server/pull/316
• Remove vendor folder by @mochi-co in https://github.com/mochi-mqtt/server/pull/319
• Fix for unlimited maximum message expiry interval by @dadebue in https://github.com/mochi-mqtt/server/pull/315

New Contributors

• @dadebue made their first contribution in https://github.com/mochi-mqtt/server/pull/315
• @x20080406 made their first contribution in https://github.com/mochi-mqtt/server/pull/321

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.1...v2.4.2

The weeks got away from me a bit so this release is a little overdue, but better late than never and it contains some good, minor updates.

What's Changed

• Refactor Listener WG to track clients by @mochi-co in https://github.com/mochi-mqtt/server/pull/301 resolves issue #298 in which hooks could shut down before all clients had gracefully concluded their runtime. The server will now wait until all clients have disconnected and their goroutines ended before proceeding from the listener shutdown stage to the hooks shutdown stage.
• Add some error logging in Listener.Serve(). by @werbenhu in https://github.com/mochi-mqtt/server/pull/303 which adds some extra logging to help track down issues in listeners, should they occur.
• Add a Chinese version of README.md. by @werbenhu in https://github.com/mochi-mqtt/server/pull/307 is an excellent initiative by @werbenhu to bring Mochi MQTT to a wider international audience.
• Emit warning if client keepalive is less than recommended minimum by @mochi-co in https://github.com/mochi-mqtt/server/pull/305 attempts to address some recurring issues where developers noticed client connection instability while using very low keepalive values (#293). Now we show a warning if a client connects with an insufficient keepalive value.

Also lots of great work happening with feature roadmapping and project planning in https://github.com/orgs/mochi-mqtt/discussions - so have a look if you are interested to get involved! 🚀

Full Changelog: https://github.com/mochi-mqtt/server/compare/v2.4.0...v2.4.1

Tests

• Builds
• Unit Tests Passing
• Paho Interoperability Passing