15:00:18 #startmeeting horizon 15:00:19 Meeting started Wed Jun 9 15:00:18 2021 UTC and is due to finish in 60 minutes. The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 The meeting name has been set to 'horizon' 15:01:27 hi 15:01:46 o/ 15:02:00 o/ 15:02:02 hello everyone. 15:02:38 this meeting will be short as I am not having much update. 15:02:44 ok let's start. 15:02:53 #topic Notices 15:03:21 I have no notices for this week. 15:03:53 if anyone else have any announcement please go ahead. 15:04:30 I finally got the django-sass-processor to work 15:04:48 rdopiera: awesome! 15:04:49 I have a proof of concept patch here: https://review.opendev.org/c/openstack/horizon/+/794809 15:04:52 rdopiera: nice🙂) 15:04:55 hi 15:05:05 there three main problems: 15:05:32 rdopiera: ok let's discuss it after I change the topic 15:05:34 1. it doesn't seem to underastand absolute paths the same was as scss -- it looks for the files in that absolute location 15:05:40 #topic django sass processor 15:05:42 ok, soryr 15:05:52 there three main problems: 15:05:53 rdopiera: floor is yours, please go ahead. 15:05:55 there three main problems: 15:05:57 sorry 15:06:02 1. it doesn't seem to underastand absolute paths the same was as scss -- it looks for the files in that absolute location 15:06:14 (we can probably fix it by subclassing it) 15:07:10 2. the way it uses a django template tag for inclusion, it doesn't allow templating inside the scss code, so we need to find a different way of including the style overrides from user settings (or remove that setting) 15:07:44 3. it has some problems with the material theme that I don't fully understand -- something about calling a function with a function as a parameter 15:09:54 that's all I have 15:10:59 rdopiera: ok I will take a look and try your patch in my env. 15:12:30 regarding the second point, I am not sure it is really needed. it might be covered by a theme. 15:13:04 amotoki: or an additional file outside the theme 15:13:32 that we can @import 15:14:05 I see. it should work. 15:14:58 the 3. is probably just something that libsass doesn't support 15:17:35 do we have anything else to discuss? 15:17:45 rdopiera: regarding 3, what kind of functions? 15:17:59 let me quickly re-run it 15:18:52 Error: Functions may not be defined within control directives or other mixins. on line 5:13 of openstack_dashboard/themes/material/static/horizon/_styles.scss 15:18:55 >> @function selector-append($selector, $to-append) { 15:19:50 (by the way, the error reporting seems much nicer too) 15:20:04 ah, we have some workdaround on this already. 15:21:32 that workaround was added to support the material theme with the current pyscss 15:22:05 we may be able to adjust it to django-scss-processor. 15:22:22 amotoki: +1 15:22:37 the commands needed to generate the static files will change too 15:22:55 we will need to add one more manage command 15:23:12 but if we can solve 1. and 3., I think we can use this 15:23:43 rdopiera: great... 15:24:20 ok moving to next topic. 15:24:48 #Nodejs14 migration 15:24:58 #topic Nodejs14 migration 15:25:08 small update on this topic. 15:25:42 All horizon plugins run horizon nodejs14 job template 15:25:51 https://review.opendev.org/q/topic:%22migrate-to-nodejs14%22+(status:open%20OR%20status:merged) 15:26:24 I forgot to push patches for some plugins to drop nodejs10 job which I try to push by today. 15:26:48 https://review.opendev.org/q/topic:%22drop-nodejs10%22+(status:open%20OR%20status:merged) 15:27:16 I was thinking if we can drop horizon-nodejs10 job template from horizon. 15:28:36 then horizon plugins must have to drop horizon-nodejs10 template to make their CI/CD green. 15:29:10 What you say or we should wait for more time? 15:30:35 vishalmanchanda: why didn't you replace node10 jobs with node14 jobs in plugins rather than adding node14 jobs? 15:31:12 if so, dropping nodejs10 job template would be simpler. 15:31:58 amotoki: yeah I didn't done that initially to avoid any failure. 15:32:42 the goal is to migrate jobs to nodejs14, so we don't need to keep both in plugins 15:33:07 I am not sure how it is realted to avoiding failures... 15:33:07 amotoki: yes. 15:34:07 I am against dropping nodejs10 template from horizon first. I think we should avoid breakage we can easily expect. 15:34:08 yeah my bad I missed that:( 15:34:21 vishalmanchanda: np 15:35:33 amotoki: ok I will wait till horizon-nodejs10 template removed from all plugins. 15:36:05 that's all update from my side. 15:36:16 #topic open-discussion 15:37:05 This week I am working on testing horizon with XStatic-Angular 1.8.2.1 version. 15:37:13 npm-test are failing as of now. 15:37:26 https://review.opendev.org/c/openstack/horizon/+/794774 15:37:46 will reach to you guys if I need any help. 15:38:23 any update on django 3.x? 15:40:19 amotoki: I was thinking to start reviewing your django3 patches. 15:40:27 #link https://review.opendev.org/q/topic:%22django3-support%22+(status:open%20OR%20status:merged) 15:41:02 vishalmanchanda: how about django-pyscss? does it depend on rdopiera's effort? 15:42:28 amotoki: need to check, I was thinking how should I start. 15:43:00 amotoki: Should we merge that patch which add a django3 job(non-voting) first 15:43:56 vishalmanchanda: non-voting job patch is okay (unless the numberr of jobs is not a problem) 15:45:45 it is nice to have such jobs if we plan to move djnago30 support forward soon. otherwise, the django3 non-voting always fails and would be meaningless. 15:45:50 that's my point. 15:46:21 amotoki: sure, I will start with this one https://review.opendev.org/c/openstack/horizon/+/777390 15:46:34 amotoki: will reach to you if have any doubts. 15:47:12 thanks 15:47:31 Does anyone have any other topics to discuss? 15:47:44 or we can end this meeting. 15:48:03 nothing 15:48:19 none from me 15:48:58 nothing 15:49:11 Thanks everyone for your contributions! 15:49:26 will see you next week. 15:49:45 #endmeeting