[03:39:55]
<Émy - OniriCorpe> config_panel.toml https://github.com/YunoHost-Apps/adguardhome_ynh/blob/b5a1c3955401b510fc8bde8387dc9a54ae2ca42c/config_panel.toml
[03:39:56]
<Émy - OniriCorpe> ynh_app_setting_set "$app" --key=open_port_53 --value="$open_port_53"
[03:42:49]
<Émy - OniriCorpe> I think I've found a bug
[03:42:49]
<Émy - OniriCorpe> using the config panel, I toggle the setting "open_port_53" to false
and in the settings.yml, I still have "open_port_53: 'true'" but "-k open_port_53: -v false" is appeared at the top of the file
[03:42:49]
<Émy - OniriCorpe> config script https://github.com/YunoHost-Apps/adguardhome_ynh/blob/b5a1c3955401b510fc8bde8387dc9a54ae2ca42c/scripts/config
[03:53:03]
<Émy - OniriCorpe> also [resources.ports] seems not exposed to config panel :/ https://paste.yunohost.org/raw/eluwimokeg
[03:53:36]
<Émy - OniriCorpe> > <@oniricorpe:im.emelyne.eu> using the config panel, I toggle the setting "open_port_53" to false
> and in the settings.yml, I still have "open_port_53: 'true'" but "-k open_port_53: -v false" is appeared at the top of the file
when no bind nor getter/setter are used
[11:15:56]
<Yunohost Git/Infra notifications> [issues] @renne opened [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[11:24:01]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872924958) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: Outgoing SMTP with DANE: Add file /etc/dnsmasq.d/dnssec to enable [DNSSEC](https://de.wikipedia.org/wiki/Domain_Name_S...
[11:25:00]
<Yunohost Git/Infra notifications> [issues] @renne edited [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[11:28:35]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872924958) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: Outgoing SMTP with DANE: Add file /etc/dnsmasq.d/dnssec to enable [DNSSEC](https://de.wikipedia.org/wiki/Domain_Name_S...
[11:57:49]
<tituspijean> Why tf are they pinging me...
[11:57:54]
<Yunohost Git/Infra notifications> [issues] @ericgaspar [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872928618) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: why ping @tituspijean?
[12:00:23]
<tituspijean> "Let's pick a random contributor, because I need it implemented by January 1st, 2024 00:00 or I will be a German outlaw" is most reasonable cause I came up with. 😅
[12:00:24]
<eric_G> ...and let's thumb up my own issue 😅
[12:01:27]
<lapineige> what are you talking about 😂
[12:02:03]
<tituspijean> you are missing out on the good yunobot notifications dear 🙂
[12:04:43]
<lapineige> It includes pings ? 😱
[12:10:06]
<tituspijean> nah I got notified on github and went to growl here 😅
[12:16:01]
<lapineige> so what is that issue ? ^^
[12:18:11]
<tituspijean> https://github.com/YunoHost/issues/issues/2303
[12:19:50]
<tituspijean> I'm thinking lapineige... did you choose to ignore the bot because it would display as new notifications in Element? or because it was cluttering the room?
[12:20:33]
<tituspijean> for reason #1 I think we can tweak the message format so that they are displayed as bots/lower priority
[12:22:53]
<tituspijean> darn I cannot remember where I put magnetocassette
[12:24:52]
<lapineige> > <@titus:pijean.ovh> I'm thinking lapineige... did you choose to ignore the bot because it would display as new notifications in Element? or because it was cluttering the room?
Both ! ^^
[12:26:02]
<lapineige> And I already subcribed to the repo/issues/PR that matters to me… it's already tooooo much emails 😂 (and I don't want to split that in yet-anothel-channel)
[13:00:08]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872943121) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: Dumb idea -)
[13:00:12]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872943143) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: Incoming SMTP with DANE: Install debian package ldnsutils 1. Enable DNSSEC at your domain registrar. 1. When the certi...
[13:10:48]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872943143) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: Incoming SMTP with DANE: 1. Install debian package ldnsutils 1. Enable DNSSEC at your domain registrar. 1. When the ce...
[13:11:50]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872943143) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: Incoming SMTP with DANE: 1. Enable DNSSEC at your domain registrar. 1. Install debian package ldnsutils 1. When the ce...
[13:41:08]
<Yunohost Git/Infra notifications> [yunohost-admin] @yunohost-bot opened [pull request #540](https://github.com/YunoHost/yunohost-admin/pull/540): Translations update from Weblate
[13:41:08]
<Yunohost Git/Infra notifications> [yunohost] @yunohost-bot opened [pull request #1757](https://github.com/YunoHost/yunohost/pull/1757): Translations update from Weblate
[13:55:25]
<Yunohost Git/Infra notifications> [issues] @tituspijean [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872954537) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: > Dumb idea -) Most likely, though I am curious about your thought process. > It is required in Germany No. These ar...
[13:56:48]
<Yunohost Git/Infra notifications> [issues] @tituspijean labeled :globe_with_meridians: DNS on [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[13:56:49]
<Yunohost Git/Infra notifications> [issues] @tituspijean labeled :mailbox: Email on [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[13:56:49]
<Yunohost Git/Infra notifications> [issues] @tituspijean labeled :closed_lock_with_key: Security on [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[13:56:49]
<Yunohost Git/Infra notifications> [issues] @tituspijean labeled :lock: Certificate on [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[14:36:00]
<Yunohost Git/Infra notifications> [issues] @renne edited [issue #2303](https://github.com/YunoHost/issues/issues/2303): Enforce SMTP transport encryption with DNS-based Authentication of Named Entities
[14:44:57]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872966046) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: > > Dumb idea -) > > Most likely, though I am curious about your thought process. Probably just the habit of addressin...
[14:46:20]
<Yunohost Git/Infra notifications> [issues] @renne [commented](https://github.com/YunoHost/issues/issues/2303#issuecomment-1872966046) on [issue #2303](https://github.com/YunoHost/issues/issues/2303) Enforce SMTP transport encryption with DNS-based Authentication of Named Entities: > > Dumb idea -) > > Most likely, though I am curious about your thought process. Probably just the habit of addressi...
[18:18:43]
<eric_G> we are getting overwhelmed by the wishlist, again
[18:19:00]
<Aleks (he/him/il/lui)> yeah :/
[18:19:11]
<eric_G> must be the Christmas effect 🤶
[19:11:23]
<Dante> Hi all! 🙂
I'm trying to setup a dev env with Yunohost, from my previous understanding it isn't possible to set it up with Docker, is that right? I've done some brief testing and I couldn't get it working.
[19:13:53]
<Aleks (he/him/il/lui)> yes, YunoHost inside Docker doesn't make sense ...
[19:13:54]
<Aleks (he/him/il/lui)> we use LXC
[19:14:08]
<Aleks (he/him/il/lui)> https://github.com/YunoHost/ynh-dev/blob/master/README.md
[19:19:21]
<Dante> I know, but sadly I can't use LXC (I use MacOS...) so I was experimenting with podman to see if I could achieve it, but I'm not sure where I could find the image that you use with LXC or if I can actually use that one...
[19:19:49]
<Dante> the one referenced here: https://github.com/YunoHost/ynh-dev/blob/5c8e3e773b140b81e55a6e6977d3bf165e7c4ae2/ynh-dev#L184
[19:21:51]
<Aleks (he/him/il/lui)> cf the README: `lxc remote add yunohost https://devbaseimgs.yunohost.org --public`
[19:23:24]
<Dante> 🤦 how I missed that
[19:23:27]
<Aleks (he/him/il/lui)> note you can also use an external VPS, or a virtualbox, though of course cost and modalities will vary between the different setups
[19:23:39]
<Dante> thanks!
[19:24:36]
<Aleks (he/him/il/lui)> but yeah ultimately docker/podman are designed to run a single process or "app", but Yunohost is more like a full ecosystem, and trying to make Yunohost run inside Docker is like trying to have your bedroom, your kitchen, and your garden all inside the bathroom
[19:25:38]
<Dante> yeah, I already had a previous setup with Virtualbox but I didn't like it that much... also I have a devbox that works but I want some setup that has the Docker way of work
[19:27:26]
<Dante> I know :/ I'll try and see what can I do with that setup
[20:40:43]
<Émy - OniriCorpe> > <@oniricorpe:im.emelyne.eu> I think I've found a bug
Any idea ?
[20:55:52]
<Aleks (he/him/il/lui)> > <@oniricorpe:im.emelyne.eu> using the config panel, I toggle the setting "open_port_53" to false
> and in the settings.yml, I still have "open_port_53: 'true'" but "-k open_port_53: -v false" is appeared at the top of the file
eeeh, wut, you mean at the top of the settings.yml ?
[20:58:00]
<Émy - OniriCorpe> Yes
[21:01:54]
<Aleks (he/him/il/lui)> eeeh okay x_X
[21:02:02]
<Aleks (he/him/il/lui)> are you able to reproduce the issue if you remove the line from settings.yml ?
[21:03:08]
<Émy - OniriCorpe> Yes, I’ve done it several time yesterday
[21:03:19]
<Émy - OniriCorpe> I can do it again if you want
[21:03:40]
<Aleks (he/him/il/lui)> zbleuarg okay then can you we look at the `yunohost config set <whatever> --debug`
[21:15:43]
<Émy - OniriCorpe> First I remove the previous `-k open_port_53: v true` at the top of the `/etc/yunohost/apps/adguardhome/settings.yaml`, `open_port_53: ‘false’`
Then I go to the config panel and I turn the setting to `true` and I save
Now the `settings.yaml` file have `-k open_port_53: -v true` for first line but `open_port_53: ‘false’` is still here
https://paste.yunohost.org/raw/tejivihuwe
[21:20:52]
<Aleks (he/him/il/lui)> `ynh_app_setting set adguardhome '-k open_port_53' '-v true'` wtf how does this happen 🤔
[21:21:19]
<Aleks (he/him/il/lui)> ah that looks like it' because
[21:21:29]
<Aleks (he/him/il/lui)> `ynh_app_setting_set "$app" --key=open_port_53 --value="$open_port_53"`
[21:21:31]
<Aleks (he/him/il/lui)> instead of
[21:21:40]
<Aleks (he/him/il/lui)> `ynh_app_setting_set --app="$app" --key=open_port_53 --value="$open_port_53"`
[21:21:42]
<Émy - OniriCorpe> https://privatebin.net/?ec1118abd365f184#ASG9DfFw6PA1x9j64pKkdNzZcEztAESRF9PieW7zwxCD
[21:21:43]
<Émy - OniriCorpe> yunohost settings set open_port_53 -v true --debug
245 DEBUG initializing base actions map parser for cli
247 DEBUG loading actions map
249 DEBUG building parser...
254 DEBUG building parser took 0.005s
256 DEBUG acquiring lock...
277 DEBUG lock has been acquired
298 DEBUG loading python module yunohost.settings took 0.021s
299 DEBUG processing action [100492.1]: yunohost.settings.set with args={'key': 'open_port_53', 'value': 'true', 'args': None}
307 DEBUG action [100492.1] executed in 0.008s
307 DEBUG lock has been released
308 ERROR La clé de filtre 'open_port_53' est incorrecte.
[21:22:16]
<Aleks (he/him/il/lui)> djeesus it's so infuriating to have to repeat `--app` while 99.99% of cases you want to update $app's setting and we never do this for any other helpers ~_~
[21:24:23]
<Émy - OniriCorpe> Ah yes, well see :O
[21:25:29]
<Émy - OniriCorpe> Ah the error is in the config script of the example_ynh
[21:25:37]
<Émy - OniriCorpe> I’ll made a PR
[21:28:11]
<Émy - OniriCorpe> > <@oniricorpe:im.emelyne.eu> yunohost settings set open_port_53 -v true --debug
> 245 DEBUG initializing base actions map parser for cli
> 247 DEBUG loading actions map
> 249 DEBUG building parser...
> 254 DEBUG building parser took 0.005s
> 256 DEBUG acquiring lock...
> 277 DEBUG lock has been acquired
> 298 DEBUG loading python module yunohost.settings took 0.021s
> 299 DEBUG processing action [100492.1]: yunohost.settings.set with args={'key': 'open_port_53', 'value': 'true', 'args': None}
> 307 DEBUG action [100492.1] executed in 0.008s
> 307 DEBUG lock has been released
> 308 ERROR La clé de filtre 'open_port_53' est incorrecte.
But this, is still wtf
[21:29:10]
<Aleks (he/him/il/lui)> yes i think for that one you have to explicitly state `main.options.open_port_53` but yeah that's not consistent with other things
[21:30:26]
<Émy - OniriCorpe> > <@Alekswag:matrix.org> yes i think for that one you have to explicitly state `main.options.open_port_53` but yeah that's not consistent with other things
Same error with `main.options.open_port_53` :/
[21:30:57]
<Aleks (he/him/il/lui)> 🤔
[21:31:12]
<Émy - OniriCorpe> > <@oniricorpe:im.emelyne.eu> https://privatebin.net/?ec1118abd365f184#ASG9DfFw6PA1x9j64pKkdNzZcEztAESRF9PieW7zwxCD
And the key is just `open_port_53` in the file
[21:31:20]
<Émy - OniriCorpe> It’s really weird
[21:31:52]
<Aleks (he/him/il/lui)> does just `main` or `main.options` work ? It should open some sort of interactive mode asking what value to set for every parameters
[21:32:38]
<Émy - OniriCorpe> Like this? `yunohost settings set main`
[21:32:57]
<Aleks (he/him/il/lui)> ah but you gotta specify the app name
[21:33:11]
<Aleks (he/him/il/lui)> uuh wait i'm super confused
[21:34:02]
<Émy - OniriCorpe> > <@Alekswag:matrix.org> uuh wait i'm super confused
We’re both :’3
[21:34:12]
<Aleks (he/him/il/lui)> should be something like `yunohost app config set adguardhome main.options.open_port_53`
[21:35:16]
<Aleks (he/him/il/lui)> `yunohost app config` is kinda confusing versus `yunohost app settings` which is like more "low level" but meh it's difficult to revamp this API
[21:39:12]
<Émy - OniriCorpe> yunohost app config set adguardhome open_port_53 -v true
Erreur : La clé de filtre 'open_port_53' est incorrecte.
yunohost app config set adguardhome main.options.open_port_53 -v true
Info : [+++++...............] > Reading config panel description and current configuration...
Info : [#####+++++..........] > Checking what changed in the new configuration...
Info : [##########+++++.....] > Validating the new configuration...
Info : [###############+++++] > Applying the new configuration...
[21:40:45]
<Émy - OniriCorpe> I fix the --app in the config script and i test
[21:46:43]
<Émy - OniriCorpe> 😐 https://paste.yunohost.org/raw/akimeriyuw
[21:47:11]
<Émy - OniriCorpe> Ah the --debug i guess
[21:47:36]
<Aleks (he/him/il/lui)> yeah
[21:48:48]
<Émy - OniriCorpe> Big sigh :’3
[21:53:30]
<Émy - OniriCorpe> Now the config panel works as expected to change the `open_port_53` value
[21:54:30]
<Émy - OniriCorpe> > <@oniricorpe:im.emelyne.eu> also [resources.ports] seems not exposed to config panel :/ https://paste.yunohost.org/raw/eluwimokeg
But I still have this bug
[21:56:33]
<Émy - OniriCorpe> Omg logs are insanely slow to display on the web admin x____x
[21:58:38]
<Émy - OniriCorpe> https://paste.yunohost.org/raw/esawisuzeq
[22:12:39]
<Émy - OniriCorpe> Also, can I use `get_network_interface` from `utils/network.py` in my package?
[22:14:12]
<Aleks (he/him/il/lui)> eeeh if you're running python and import the function, i guess yes, though honestly when we refactor code it's unlikely that we'll look at app using these
[22:15:48]
<Émy - OniriCorpe> Hm yes okay, I thought of that because I have many ‘personal helpers’ in this packages that reimplement core utils
[22:15:51]
<Aleks (he/him/il/lui)> > <@oniricorpe:im.emelyne.eu> https://paste.yunohost.org/raw/esawisuzeq
i still don't understand wether or not settings are automatically loaded in that context .. maybe you need to fetch the current value, i'm confused
[22:16:09]
<Émy - OniriCorpe> One to get the network interfaces and another one to know if one IP is public or private (not so many :’3)
[22:18:13]
<Émy - OniriCorpe> Yes, i’ll do that but it’s still confusing yes
I have some settings that are loaded and some not
[22:18:36]
<Émy - OniriCorpe> Also yunopaste doesn’t have a --help outpout or similar, idk if it’s intentional
[22:19:15]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯
[23:59:52]
<Yunohost Git/Infra notifications> [yunohost] @OniriCorpe opened [pull request #1758](https://github.com/YunoHost/yunohost/pull/1758): add --after= in the usage section of ynh_read_var_in_file and ynh_write_var_in_file
[23:59:57]
<Yunohost Git/Infra notifications> [yunohost] @OniriCorpe edited [pull request #1758](https://github.com/YunoHost/yunohost/pull/1758): add --after= in the usage section of ynh_read_var_in_file and ynh_write_var_in_file