Closed luismiramirez closed 5 months ago
:heavy_check_mark: All good!
This is a message from the daily scheduled checks.
Did some thorough testing around the packaging itself, because the build hook is tricky and not covered by any automated testing and I don't trust it very much. Writing it down here in case someone wants to follow at home:
_APPSIGNAL_BUILD_TRIPLE=any hatch build -t wheel
.hatch run build:me
(for my non-any platform) to make sure no artifacts leaked between the two buildstar -ztvf dist/appsignal-1.3.3-py3-none-any.whl
to list the filesappsignal/_appsignal_platform
was any
.hatch run build:all
to make sure it was built as part of the release processAll of that went fine, so the artifact is being built as expected.
To test the behaviour itself:
any
with _APPSIGNAL_BUILD_TRIPLE=any hatch build -t wheel
hatch shell
, then on a python3
repl:
import appsignal
appsignal.Appsignal(active=True, push_api_key="blah").start()
This is a message from the daily scheduled checks.
This is a message from the daily scheduled checks.
Add wildcard triple for unsupported systems
The
any
tag is now installed when downloading the package from an unsupported system.Don't start components when on unsupported arch
When trying to run the agent, OpenTelemetry and probes on an unsupported system (any-any), prevent the three of them from starting.
Closes #179