00:09 Pe_Elle joined 00:54 Pe_Elle left, Pe_Elle joined 00:55 Pe_Elle left 00:56 Pe_Elle joined 00:57 Pe_Elle left 00:59 Pe_Elle joined 01:04 Pe_Elle left 01:27 Pe_Elle joined 01:36 Pe_Elle left 01:51 Pe_Elle joined 02:27 Pe_Elle left, Pe_Elle joined 02:57 Pe_Elle left 03:02 Pe_Elle joined 03:16 Pe_Elle left 03:39 Pe_Elle joined 03:43 Pe_Elle left 04:04 Pe_Elle joined 04:42 Pe_Elle left 04:56 Pe_Elle joined
SmokeMachine librasteve: when you have some time, if you could take a look at my answer to your PR, please: github.com/FCO/Cromponent/pull/7#i...2563346884 05:51
for doing that I had to wrap add-handler to be able to access route-set from inside the handler... does any one know a better way? 05:53
06:51 Pe_Elle left 06:52 Pe_Elle joined 08:54 Pe_Elle left
librasteve lizmat: my initial guess was that this compile-dir is called on each cro run rebuild github.com/croservices/cro-webapp/...kumod#L110 10:01
lizmat that could well be it :-)
librasteve my new guess is that this monitor Cro::WebApp::Template::Repository::FileSystem::Reloading is used bu cro run github.com/croservices/cro-webapp/...kumod#L116 10:02
lizmat I'd suggest making an issue for it 10:03
librasteve lizmat ++ (I have asked arun to do that already)
the begumpura site they shared has (see my notes ^^) some other stuff in it that may be the botteneck and I would like to see that ruled out 10:07
(eg Red database start command)
also they may be running on an i286
10:31 sena_kun joined 10:32 Pe_Elle joined, Pe_Elle left 10:33 Pe_Elle joined