Compile error after telemetry 1.4.0 bump

[ftes]

Describe the bug

After bumping telemetry from 1.3.0 to 1.4.0, appsignal 2.16.0 fails to compile:

mix deps.compile
...
#24 112.7 ==> appsignal
#24 112.7 Downloading agent release
#24 112.7 could not compile dependency :appsignal, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile appsignal --force", update it with "mix deps.update appsignal" or clean it with "mix deps.clean appsignal"
#24 112.7 ** (ArgumentError) errors were found at the given arguments:
#24 112.7 
#24 112.7   * 1st argument: no persistent term stored with this key
#24 112.7 
#24 112.7     :persistent_term.get(:telemetry)
#24 112.7     (telemetry 1.4.0) /app/deps/telemetry/src/telemetry_handler_table.erl:58: :telemetry_handler_table.list_for_event/1
#24 112.7     (telemetry 1.4.0) /app/deps/telemetry/src/telemetry.erl:193: :telemetry.execute/3
#24 112.7     (telemetry 1.4.0) /app/deps/telemetry/src/telemetry.erl:353: :telemetry.span/3
#24 112.7     mix_helpers.exs:218: Mix.Appsignal.Helper.do_download_file!/2
#24 112.7     mix_helpers.exs:186: anonymous fn/5 in Mix.Appsignal.Helper.do_download_file!/3
#24 112.7     (elixir 1.19.5) lib/enum.ex:5023: Enumerable.List.reduce/3
#24 112.7     (elixir 1.19.5) lib/enum.ex:2574: Enum.reduce_while/3
#24 ERROR: process "/bin/sh -c mix deps.compile" did not complete successfully: exit code: 1

To Reproduce

Steps to reproduce the behavior:

• Using AppSignal for Elixir package version 2.16.0
• In my app using telemetry 1.4.0
• In Github Actions: ubuntu 24.04 runner, building via docker buildx

Maybe related: beam-telemetry/telemetry#144

[unflxw]

Thank you for reporting this @ftes! Looking into it to see if we can work around it on our end, though it seems that the telemetry team will address it as well: beam-telemetry/telemetry#144

[unflxw]

Overriding the telemetry dependency to 1.3.0 should fix it for now.

[ftes]

Overriding the telemetry dependency to 1.3.0 should fix it for now.

I can confirm that works.

Also, now already fixed in telemetry main branch (11210b).

So it looks like this is a telemetry side issue, and we can close this issue here.
Pin to 1.3.0 until telemetry 1.4.x fix is released.

[unflxw]

Telemetry 1.4.1 has been released, with a fix to the above.

[ftes]

Thanks for checking in on this issue so quickly Noemi!

[unflxw]

🙇 Any time, and thank you for reporting it on Telemetry's end!