mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

module:set_global()

local custom_metric = require "core.statsmanager".metric
local gc_bytes = custom_metric(
	"gauge", "lua_heap", "bytes",
	"Memory used by objects under control of the Lua garbage collector"
):with_labels()

module:hook("stats-update", function ()
	local kbytes = collectgarbage("count");
  gc_bytes:set(kbytes * 1024);
end);

custom_metric("gauge", "lua_info", "", "Lua runtime version", { "version" }):with_labels(_VERSION):set(1);