[16:34:32]
<Salamandar> and if the ping is not received, it is considered down
[16:34:32]
<m606> ok thanks
[16:34:32]
<m606> i.e. theoretically, yesterday evening I guess autoupdater should have triggered a PR for the new commit (which is not the case).
[16:34:33]
<m606> I was wondering because for jsoncrack_ynh i have set autoupdater to `latest_github_commits`, and here is what i get today:
```
last commit on YNH repo (master): 17/12/2024 01:44 (github time)
last commit on upstream repo: 17/12/2024 15:59 (github time)
last autoupdater run: 17/12/2023 23:22 (status.yunohost.org time)
```
[16:34:33]
<m606> I was wondering because for jsoncrack_ynh i have set autoupdater to `latest_github_commits`, and here is what i get today:
```
last commit on YNH repo (master): 17/12/2024 01:44 (github time)
last commit on upstream repo: 17/12/2024 15:59 (github time)
last autoupdater run: 17/12/2023 23:22 (status.yunohost.org time)
```
[16:34:33]
<m606> I was wondering because for jsoncrack_ynh i have set autoupdater to `latest_github_commits`, and here is what i get today:
```
last commit on YNH repo (master): 17/12/2024 01:44 (github time)
last commit on upstream repo: 17/12/2024 15:59 (github time)
last autoupdater run: 17/12/2023 23:22 (status.yunohost.org time)
```
[16:34:33]
<m606> i can wait of course, that's not an issue, but was just wondering why
[16:34:34]
<m606> I was wondering because for jsoncrack_ynh i have set autoupdater to `latest_github_commit`, and here is what i get today:
```
last commit on YNH repo (master): 17/12/2024 01:44 (github time)
last commit on upstream repo: 17/12/2024 15:59 (github time)
last autoupdater run: 17/12/2023 23:22 (status.yunohost.org time)
```
[16:34:34]
<m606> I was wondering because for jsoncrack_ynh i have set autoupdater to `latest_github_commit`, and here is what i get today:
```
last commit on YNH repo (master): 17/12/2024 01:44 (github time)
last commit on upstream repo: 17/12/2024 15:59 (github time)
last autoupdater run: 17/12/2024 23:22 (status.yunohost.org time)
```
[16:34:34]
<quiwy> eric_G : thank you for the merge :)
However, I just tried the update of actual you merged on master, and it seems that actual is not looking in the same directory after the update, so we cannot use previously created budgets.
Before the directory was something like `/home/yunohost.app/actual/data/server-files`, now there is no the `data` part anymore.
Is there anything preventing from doing what I suggested in the PR about the env file ? https://github.com/YunoHost-Apps/actual_ynh/pull/52#discussion_r1886998631