Open mayel opened 6 months ago
If we can help to debug this (by explaining the CI context for instance), feel free to ping :)
Referencing https://github.com/YunoHost-Apps/bonfire_ynh/pull/5#issuecomment-1924190658
Apparently it's not only a CI issue. If you have any idea of to debug this, it would be very appreciated :)
Looking at the error of @lapineige it doesn't prevent your app to start but only prevents updating tz, right?
What is your tz config? Are you using the :data_dir
option? In which environment does this happen? Do you have that problem in localhost/dev or only when deployed?
Based on messages like Erlang has closed
or Application bonfire exited: Bonfire.Application.start(:normal, []) returned an error: shutdown: failed to start child: Tz.UpdatePeriodically
I'm pretty sure it's preventing the app from starting, right @lapineige?
IIRC the only config is:
config :tzdata, :autoupdate, :disabled
config :elixir, :time_zone_database, Tz.TimeZoneDatabase
and in Application
supervision tree {Tz.UpdatePeriodically, [interval_in_days: 10]}
The environment is an Elixir/OTP release built and running within https://yunohost.org (Debian-based and the whole setup is defined in code rather than manually). I haven't seen this issue when running a release in Docker or in dev.
Looking at the error of @lapineige it doesn't prevent your app to start but only prevents updating tz, right?
In that case it seems to fail the app start. In the CI and other people install situations, it prevent the first start.
In which environment does this happen?
A Yunohost x86 server on Debian 11, I don't know what information would be meaningful.
Do you have that problem in localhost/dev or only when deployed?
I'm deploying and app.
I can provide details about how the thing is installed in Yunohost environment. The main thing I guess is that it's a dedicated NodeJS (18 if I remember correctly) version for this app, and not a global npm package installation. It's running with the bonfire
user and file rights, not root or whatever.
Do you need additional details to help us on this issue ?
@lapineige how can one trigger such a build and observe its output?
It's not that quick, but relatively simple. You would need a Yunohost environment.
Basically:
yunohost app install bonfire
, possibly adding --no-remove-on-failure
if you don't want it to revert the installation when it will fail (this mean files will be kept).I can provide more details if needed.
couldn't we also do it by forking a repo and getting github's CI to run it?
Oh yes you're right. A PR with a dedicated branch in the repo is possible too (I can provide help on this, because you need write access). As for forking the repo, the CI won't be launched if it's not in Yunohost-Apps.
Sorry I'm not proficient with CI/deploys. We expect the files to be there: https://github.com/mathieuprog/tz/blob/v0.26.5/lib/tz/compiler.ex#L15
Those are under the /priv folder in this library: https://github.com/mathieuprog/tz/tree/v0.26.5/priv/tzdata2023c
Could you clarify the problem and context in further details?
I'm getting this error only in a particular CI env and not sure why, are those files that tz is meant to download or expects to already be there, and if so where do they usually come from?