multiple feedings in a single day failing

I'll start by giving you a big THANK YOU for breathing new life into my feeder!
I successfully got everything set up about 3 months ago, and at the time, had only configured 1 feeding per day. It was working, but I ran into trouble when I tried to modify the feeding time by an hour - my feeder was still checking in regularly, but it was feeding at the, "old" time. I got around this by restarting the container, and switching the feeder off, then on via the switch on the back. Not a big deal, but unexpected - and I'm not sure if that behavior is related to my current issue, or not?
My current issue is that I added 2 additional feeding times (breakfast @9am and dinner @8pm), to see if I could rely on the feeder when I'm away from home overnight, but the new feeding times are not actually occurring (the original lunch feeding @1pm is still working).
So, my question is - are multiple feedings per day currently supported? If so, how can I help debug what's going wrong?
I do see this error in the logs, that occurs at 8pm, which is the new dinner feeding time - every night:
2021-06-12 20:00:40,825   ERROR    feeder.util.mqtt.client: Failed to decode message: bytearray(b'{"_|deviceHid":"cf4b00fd99b69286da9737c7bf4cbfba93b42e06","s|msg_type":"trace","i|tl":64,"s|ts":"Results - Actual: 536932240 tbsp(1g), End: 334565, \xf0\x08\xf8O\xf4\x80P\x01hI\x1c\x01"}')
Traceback (most recent call last):
  File "/tmp/feeder/util/mqtt/client.py", line 102, in handle_message
    payload = json.loads(packet.payload.data)
  File "/usr/local/lib/python3.8/json/__init__.py", line 343, in loads
    s = s.decode(detect_encoding(s), 'surrogatepass')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf0 in position 148: invalid continuation byte
2021-06-12 20:00:41,673   INFO     feeder.util.mqtt.client: Committing feed result data for cf4b00fd99b69286da9737c7bf4cbfba93b42e06
2021-06-12 20:03:40,677   INFO     uvicorn.access: <IP_ADDRESS>:52824 - "GET /home HTTP/1.0" 404
2021-06-12 20:13:41,119   INFO     uvicorn.access: <IP_ADDRESS>:53306 - "GET /home HTTP/1.0" 404
2021-06-12 20:23:41,591   INFO     uvicorn.access: <IP_ADDRESS>:54880 - "GET /home HTTP/1.0" 404
2021-06-12 20:33:42,142   INFO     uvicorn.access: <IP_ADDRESS>:55362 - "GET /home HTTP/1.0" 404
2021-06-12 20:40:49,149   INFO     uvicorn.access: <IP_ADDRESS>:55700 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-12 20:40:53,336   INFO     uvicorn.access: <IP_ADDRESS>:55706 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-12 20:40:57,127   INFO     uvicorn.access: <IP_ADDRESS>:55712 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-12 20:40:59,778   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-12 20:40:59,778   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:62583 on listener 'tcp-ssl-1'
2021-06-12 20:43:42,588   INFO     uvicorn.access: <IP_ADDRESS>:55850 - "GET /home HTTP/1.0" 404
2021-06-12 20:53:42,986   INFO     uvicorn.access: <IP_ADDRESS>:56350 - "GET /home HTTP/1.0" 404
2021-06-12 21:01:47,606   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-12 21:03:43,447   INFO     uvicorn.access: <IP_ADDRESS>:56896 - "GET /home HTTP/1.0" 404
2021-06-12 21:13:43,952   INFO     uvicorn.access: <IP_ADDRESS>:57378 - "GET /home HTTP/1.0" 404
2021-06-12 21:23:44,440   INFO     uvicorn.access: <IP_ADDRESS>:57860 - "GET /home HTTP/1.0" 404
2021-06-12 21:28:57,717   INFO     uvicorn.access: <IP_ADDRESS>:59232 - "GET / HTTP/1.0" 200
2021-06-12 21:28:58,205   INFO     uvicorn.access: <IP_ADDRESS>:59244 - "GET / HTTP/1.0" 200
2021-06-12 21:28:58,217   INFO     uvicorn.access: <IP_ADDRESS>:59250 - "GET /token HTTP/1.0" 404
2021-06-12 21:28:58,228   INFO     uvicorn.access: <IP_ADDRESS>:59256 - "GET /user/ajax/menu-bar?ts=1623531600&_=748 HTTP/1.0" 404
2021-06-12 21:28:58,238   INFO     uvicorn.access: <IP_ADDRESS>:59262 - "GET / HTTP/1.0" 200
2021-06-12 21:33:45,040   INFO     uvicorn.access: <IP_ADDRESS>:59584 - "GET /home HTTP/1.0" 404
2021-06-12 21:43:45,513   INFO     uvicorn.access: <IP_ADDRESS>:60066 - "GET /home HTTP/1.0" 404
2021-06-12 21:53:46,450   INFO     uvicorn.access: <IP_ADDRESS>:60548 - "GET /home HTTP/1.0" 404
2021-06-12 22:03:46,854   INFO     uvicorn.access: <IP_ADDRESS>:32850 - "GET /home HTTP/1.0" 404
2021-06-12 22:13:47,361   INFO     uvicorn.access: <IP_ADDRESS>:33332 - "GET /home HTTP/1.0" 404
2021-06-12 22:23:47,886   INFO     uvicorn.access: <IP_ADDRESS>:33814 - "GET /home HTTP/1.0" 404
2021-06-12 22:33:48,346   INFO     uvicorn.access: <IP_ADDRESS>:35394 - "GET /home HTTP/1.0" 404
2021-06-12 22:41:45,583   INFO     uvicorn.access: <IP_ADDRESS>:35780 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-12 22:41:49,362   INFO     uvicorn.access: <IP_ADDRESS>:35786 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-12 22:41:53,155   INFO     uvicorn.access: <IP_ADDRESS>:35792 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-12 22:41:55,622   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-12 22:41:55,623   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:63999 on listener 'tcp-ssl-1'
2021-06-12 22:43:48,803   INFO     uvicorn.access: <IP_ADDRESS>:35894 - "GET /home HTTP/1.0" 404
2021-06-12 22:53:49,176   INFO     uvicorn.access: <IP_ADDRESS>:36372 - "GET /home HTTP/1.0" 404
2021-06-12 23:02:45,718   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-12 23:03:49,665   INFO     uvicorn.access: <IP_ADDRESS>:36906 - "GET /home HTTP/1.0" 404
2021-06-12 23:09:49,647   INFO     uvicorn.access: <IP_ADDRESS>:37304 - "GET / HTTP/1.0" 200
2021-06-12 23:09:50,156   INFO     uvicorn.access: <IP_ADDRESS>:37316 - "GET / HTTP/1.0" 200
2021-06-12 23:09:50,168   INFO     uvicorn.access: <IP_ADDRESS>:37322 - "GET /token HTTP/1.0" 404
2021-06-12 23:09:50,180   INFO     uvicorn.access: <IP_ADDRESS>:37328 - "GET /user/ajax/menu-bar?ts=1623538800&_=796 HTTP/1.0" 404
2021-06-12 23:09:50,190   INFO     uvicorn.access: <IP_ADDRESS>:37334 - "GET / HTTP/1.0" 200
2021-06-12 23:13:50,138   INFO     uvicorn.access: <IP_ADDRESS>:37620 - "GET /home HTTP/1.0" 404
2021-06-12 23:23:50,598   INFO     uvicorn.access: <IP_ADDRESS>:38102 - "GET /home HTTP/1.0" 404
2021-06-12 23:33:51,131   INFO     uvicorn.access: <IP_ADDRESS>:38584 - "GET /home HTTP/1.0" 404
2021-06-12 23:43:51,548   INFO     uvicorn.access: <IP_ADDRESS>:40164 - "GET /home HTTP/1.0" 404
2021-06-12 23:53:52,122   INFO     uvicorn.access: <IP_ADDRESS>:40646 - "GET /home HTTP/1.0" 404
2021-06-13 00:03:52,628   INFO     uvicorn.access: <IP_ADDRESS>:41174 - "GET /home HTTP/1.0" 404
2021-06-13 00:13:18,600   INFO     uvicorn.access: <IP_ADDRESS>:42860 - "GET /?sub1=20210613-1013-189e-b427-2e8de6061fc2 HTTP/1.0" 200
2021-06-13 00:13:49,058   INFO     uvicorn.access: <IP_ADDRESS>:42964 - "GET / HTTP/1.0" 200
2021-06-13 00:13:49,636   INFO     uvicorn.access: <IP_ADDRESS>:42976 - "GET / HTTP/1.0" 200
2021-06-13 00:13:49,648   INFO     uvicorn.access: <IP_ADDRESS>:42982 - "GET /token HTTP/1.0" 404
2021-06-13 00:13:49,660   INFO     uvicorn.access: <IP_ADDRESS>:42988 - "GET /user/ajax/menu-bar?ts=1623542400&_=748 HTTP/1.0" 404
2021-06-13 00:13:49,672   INFO     uvicorn.access: <IP_ADDRESS>:42994 - "GET / HTTP/1.0" 200
2021-06-13 00:14:27,042   INFO     uvicorn.access: <IP_ADDRESS>:43152 - "GET /home HTTP/1.0" 404
2021-06-13 00:14:28,032   INFO     uvicorn.access: <IP_ADDRESS>:43168 - "GET /home HTTP/1.0" 404
2021-06-13 00:14:30,314   INFO     uvicorn.access: <IP_ADDRESS>:43190 - "GET /home HTTP/1.0" 404
2021-06-13 00:24:31,317   INFO     uvicorn.access: <IP_ADDRESS>:43748 - "GET /home HTTP/1.0" 404
2021-06-13 00:34:31,792   INFO     uvicorn.access: <IP_ADDRESS>:44238 - "GET /home HTTP/1.0" 404
2021-06-13 00:42:45,393   INFO     uvicorn.access: <IP_ADDRESS>:44636 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 00:42:49,180   INFO     uvicorn.access: <IP_ADDRESS>:44638 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 00:42:52,896   INFO     uvicorn.access: <IP_ADDRESS>:44644 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 00:42:55,415   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 00:42:55,415   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:56304 on listener 'tcp-ssl-1'
2021-06-13 00:44:32,217   INFO     uvicorn.access: <IP_ADDRESS>:44734 - "GET /home HTTP/1.0" 404
2021-06-13 00:54:32,729   INFO     uvicorn.access: <IP_ADDRESS>:45220 - "GET /home HTTP/1.0" 404
2021-06-13 01:03:39,734   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 01:04:33,184   INFO     uvicorn.access: <IP_ADDRESS>:45738 - "GET /home HTTP/1.0" 404
2021-06-13 01:14:33,628   INFO     uvicorn.access: <IP_ADDRESS>:47376 - "GET /home HTTP/1.0" 404
2021-06-13 01:24:34,095   INFO     uvicorn.access: <IP_ADDRESS>:47866 - "GET /home HTTP/1.0" 404
2021-06-13 01:34:34,602   INFO     uvicorn.access: <IP_ADDRESS>:48356 - "GET /home HTTP/1.0" 404
2021-06-13 01:44:35,301   INFO     uvicorn.access: <IP_ADDRESS>:48858 - "GET /home HTTP/1.0" 404
2021-06-13 01:54:15,426   INFO     uvicorn.access: <IP_ADDRESS>:49352 - "GET / HTTP/1.0" 200
2021-06-13 01:54:15,911   INFO     uvicorn.access: <IP_ADDRESS>:49364 - "GET / HTTP/1.0" 200
2021-06-13 01:54:15,923   INFO     uvicorn.access: <IP_ADDRESS>:49370 - "GET /token HTTP/1.0" 404
2021-06-13 01:54:15,935   INFO     uvicorn.access: <IP_ADDRESS>:49376 - "GET /user/ajax/menu-bar?ts=1623546000&_=748 HTTP/1.0" 404
2021-06-13 01:54:15,947   INFO     uvicorn.access: <IP_ADDRESS>:49382 - "GET / HTTP/1.0" 200
2021-06-13 01:54:35,734   INFO     uvicorn.access: <IP_ADDRESS>:49450 - "GET /home HTTP/1.0" 404
2021-06-13 02:04:36,232   INFO     uvicorn.access: <IP_ADDRESS>:50004 - "GET /home HTTP/1.0" 404
2021-06-13 02:14:36,811   INFO     uvicorn.access: <IP_ADDRESS>:50546 - "GET /home HTTP/1.0" 404
2021-06-13 02:24:37,460   INFO     uvicorn.access: <IP_ADDRESS>:52130 - "GET /home HTTP/1.0" 404
2021-06-13 02:34:38,675   INFO     uvicorn.access: <IP_ADDRESS>:52632 - "GET /home HTTP/1.0" 404
2021-06-13 02:43:39,579   INFO     uvicorn.access: <IP_ADDRESS>:53098 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 02:43:43,370   INFO     uvicorn.access: <IP_ADDRESS>:53100 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 02:43:47,456   INFO     uvicorn.access: <IP_ADDRESS>:53106 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 02:43:49,927   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 02:43:49,927   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:50041 on listener 'tcp-ssl-1'
2021-06-13 02:44:39,177   INFO     uvicorn.access: <IP_ADDRESS>:53156 - "GET /home HTTP/1.0" 404
2021-06-13 02:54:39,707   INFO     uvicorn.access: <IP_ADDRESS>:53646 - "GET /home HTTP/1.0" 404
2021-06-13 03:04:40,137   INFO     uvicorn.access: <IP_ADDRESS>:54136 - "GET /home HTTP/1.0" 404
2021-06-13 03:04:54,230   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 03:14:40,583   INFO     uvicorn.access: <IP_ADDRESS>:54692 - "GET /home HTTP/1.0" 404
2021-06-13 03:24:41,040   INFO     uvicorn.access: <IP_ADDRESS>:56280 - "GET /home HTTP/1.0" 404
2021-06-13 03:34:41,554   INFO     uvicorn.access: <IP_ADDRESS>:56770 - "GET /home HTTP/1.0" 404
2021-06-13 03:35:10,026   INFO     uvicorn.access: <IP_ADDRESS>:56820 - "GET / HTTP/1.0" 200
2021-06-13 03:35:10,563   INFO     uvicorn.access: <IP_ADDRESS>:56832 - "GET / HTTP/1.0" 200
2021-06-13 03:35:10,576   INFO     uvicorn.access: <IP_ADDRESS>:56838 - "GET /token HTTP/1.0" 404
2021-06-13 03:35:10,587   INFO     uvicorn.access: <IP_ADDRESS>:56844 - "GET /user/ajax/menu-bar?ts=1623553200&_=748 HTTP/1.0" 404
2021-06-13 03:35:10,599   INFO     uvicorn.access: <IP_ADDRESS>:56850 - "GET / HTTP/1.0" 200
2021-06-13 03:44:42,053   INFO     uvicorn.access: <IP_ADDRESS>:57404 - "GET /home HTTP/1.0" 404
2021-06-13 03:54:42,508   INFO     uvicorn.access: <IP_ADDRESS>:57886 - "GET /home HTTP/1.0" 404
2021-06-13 04:04:43,031   INFO     uvicorn.access: <IP_ADDRESS>:58376 - "GET /home HTTP/1.0" 404
2021-06-13 04:14:43,522   INFO     uvicorn.access: <IP_ADDRESS>:58916 - "GET /home HTTP/1.0" 404
2021-06-13 04:24:44,014   INFO     uvicorn.access: <IP_ADDRESS>:59398 - "GET /home HTTP/1.0" 404
2021-06-13 04:34:44,569   INFO     uvicorn.access: <IP_ADDRESS>:60978 - "GET /home HTTP/1.0" 404
2021-06-13 04:44:37,136   INFO     uvicorn.access: <IP_ADDRESS>:33212 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 04:44:40,919   INFO     uvicorn.access: <IP_ADDRESS>:33218 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 04:44:44,917   INFO     uvicorn.access: <IP_ADDRESS>:33226 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 04:44:45,106   INFO     uvicorn.access: <IP_ADDRESS>:33234 - "GET /home HTTP/1.0" 404
2021-06-13 04:44:47,394   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 04:44:47,394   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:51283 on listener 'tcp-ssl-1'
2021-06-13 04:54:45,587   INFO     uvicorn.access: <IP_ADDRESS>:33754 - "GET /home HTTP/1.0" 404
2021-06-13 05:04:45,995   INFO     uvicorn.access: <IP_ADDRESS>:34256 - "GET /home HTTP/1.0" 404
2021-06-13 05:06:41,494   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 05:14:46,440   INFO     uvicorn.access: <IP_ADDRESS>:34790 - "GET /home HTTP/1.0" 404
2021-06-13 05:15:41,391   INFO     uvicorn.access: <IP_ADDRESS>:34860 - "GET / HTTP/1.0" 200
2021-06-13 05:15:41,844   INFO     uvicorn.access: <IP_ADDRESS>:34872 - "GET / HTTP/1.0" 200
2021-06-13 05:15:41,866   INFO     uvicorn.access: <IP_ADDRESS>:34878 - "GET /token HTTP/1.0" 404
2021-06-13 05:15:41,880   INFO     uvicorn.access: <IP_ADDRESS>:34884 - "GET /user/ajax/menu-bar?ts=1623560400&_=748 HTTP/1.0" 404
2021-06-13 05:15:41,892   INFO     uvicorn.access: <IP_ADDRESS>:34890 - "GET / HTTP/1.0" 200
2021-06-13 05:24:46,861   INFO     uvicorn.access: <IP_ADDRESS>:35416 - "GET /home HTTP/1.0" 404
2021-06-13 05:34:47,490   INFO     uvicorn.access: <IP_ADDRESS>:36996 - "GET /home HTTP/1.0" 404
2021-06-13 05:44:47,982   INFO     uvicorn.access: <IP_ADDRESS>:37478 - "GET /home HTTP/1.0" 404
2021-06-13 05:54:48,461   INFO     uvicorn.access: <IP_ADDRESS>:37960 - "GET /home HTTP/1.0" 404
2021-06-13 06:04:48,916   INFO     uvicorn.access: <IP_ADDRESS>:38442 - "GET /home HTTP/1.0" 404
2021-06-13 06:14:49,342   INFO     uvicorn.access: <IP_ADDRESS>:38976 - "GET /home HTTP/1.0" 404
2021-06-13 06:24:49,744   INFO     uvicorn.access: <IP_ADDRESS>:39458 - "GET /home HTTP/1.0" 404
2021-06-13 06:34:50,318   INFO     uvicorn.access: <IP_ADDRESS>:39940 - "GET /home HTTP/1.0" 404
2021-06-13 06:44:50,761   INFO     uvicorn.access: <IP_ADDRESS>:41528 - "GET /home HTTP/1.0" 404
2021-06-13 06:45:36,442   INFO     uvicorn.access: <IP_ADDRESS>:41566 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 06:45:40,221   INFO     uvicorn.access: <IP_ADDRESS>:41572 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 06:45:44,015   INFO     uvicorn.access: <IP_ADDRESS>:41578 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 06:45:46,665   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 06:45:46,665   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:53174 on listener 'tcp-ssl-1'
2021-06-13 06:54:51,515   INFO     uvicorn.access: <IP_ADDRESS>:42016 - "GET /home HTTP/1.0" 404
2021-06-13 06:56:17,767   INFO     uvicorn.access: <IP_ADDRESS>:42124 - "GET /user/ajax/menu-bar?ts=1623564000&_=748 HTTP/1.0" 404
2021-06-13 06:56:18,152   INFO     uvicorn.access: <IP_ADDRESS>:42138 - "GET / HTTP/1.0" 200
2021-06-13 06:56:18,615   INFO     uvicorn.access: <IP_ADDRESS>:42150 - "GET / HTTP/1.0" 200
2021-06-13 06:56:18,627   INFO     uvicorn.access: <IP_ADDRESS>:42156 - "GET /token HTTP/1.0" 404
2021-06-13 06:56:18,641   INFO     uvicorn.access: <IP_ADDRESS>:42162 - "GET /user/ajax/menu-bar?ts=1623564000&_=748 HTTP/1.0" 404
2021-06-13 06:56:18,657   INFO     uvicorn.access: <IP_ADDRESS>:42168 - "GET / HTTP/1.0" 200
2021-06-13 07:04:51,919   INFO     uvicorn.access: <IP_ADDRESS>:42670 - "GET /home HTTP/1.0" 404
2021-06-13 07:06:54,550   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 07:14:52,375   INFO     uvicorn.access: <IP_ADDRESS>:43206 - "GET /home HTTP/1.0" 404
2021-06-13 07:24:52,952   INFO     uvicorn.access: <IP_ADDRESS>:43688 - "GET /home HTTP/1.0" 404
2021-06-13 07:34:53,448   INFO     uvicorn.access: <IP_ADDRESS>:44170 - "GET /home HTTP/1.0" 404
2021-06-13 07:44:53,934   INFO     uvicorn.access: <IP_ADDRESS>:45750 - "GET /home HTTP/1.0" 404
2021-06-13 07:54:54,439   INFO     uvicorn.access: <IP_ADDRESS>:46232 - "GET /home HTTP/1.0" 404
2021-06-13 08:04:54,889   INFO     uvicorn.access: <IP_ADDRESS>:46710 - "GET /home HTTP/1.0" 404
2021-06-13 08:14:55,316   INFO     uvicorn.access: <IP_ADDRESS>:47244 - "GET /home HTTP/1.0" 404
2021-06-13 08:24:55,838   INFO     uvicorn.access: <IP_ADDRESS>:47726 - "GET /home HTTP/1.0" 404
2021-06-13 08:34:56,330   INFO     uvicorn.access: <IP_ADDRESS>:48228 - "GET /home HTTP/1.0" 404
2021-06-13 08:36:51,148   INFO     uvicorn.access: <IP_ADDRESS>:48350 - "GET / HTTP/1.0" 200
2021-06-13 08:36:51,621   INFO     uvicorn.access: <IP_ADDRESS>:48362 - "GET / HTTP/1.0" 200
2021-06-13 08:36:51,644   INFO     uvicorn.access: <IP_ADDRESS>:48368 - "GET /token HTTP/1.0" 404
2021-06-13 08:36:51,660   INFO     uvicorn.access: <IP_ADDRESS>:48374 - "GET /user/ajax/menu-bar?ts=1623571200&_=748 HTTP/1.0" 404
2021-06-13 08:36:51,671   INFO     uvicorn.access: <IP_ADDRESS>:48380 - "GET / HTTP/1.0" 200
2021-06-13 08:44:56,791   INFO     uvicorn.access: <IP_ADDRESS>:48858 - "GET /home HTTP/1.0" 404
2021-06-13 08:46:31,747   INFO     uvicorn.access: <IP_ADDRESS>:48936 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 08:46:35,528   INFO     uvicorn.access: <IP_ADDRESS>:48938 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 08:46:39,322   INFO     uvicorn.access: <IP_ADDRESS>:48944 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 08:46:43,100   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 08:46:43,100   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:58196 on listener 'tcp-ssl-1'
2021-06-13 08:54:57,220   INFO     uvicorn.access: <IP_ADDRESS>:50444 - "GET /home HTTP/1.0" 404
2021-06-13 09:04:57,664   INFO     uvicorn.access: <IP_ADDRESS>:50926 - "GET /home HTTP/1.0" 404
2021-06-13 09:07:52,662   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 09:14:58,150   INFO     uvicorn.access: <IP_ADDRESS>:51460 - "GET /home HTTP/1.0" 404
2021-06-13 09:24:58,507   INFO     uvicorn.access: <IP_ADDRESS>:56786 - "GET /home HTTP/1.0" 404
2021-06-13 09:34:59,069   INFO     uvicorn.access: <IP_ADDRESS>:59974 - "GET /home HTTP/1.0" 404
2021-06-13 09:44:59,530   INFO     uvicorn.access: <IP_ADDRESS>:60452 - "GET /home HTTP/1.0" 404
2021-06-13 09:55:00,014   INFO     uvicorn.access: <IP_ADDRESS>:33820 - "GET /home HTTP/1.0" 404
2021-06-13 10:05:00,443   INFO     uvicorn.access: <IP_ADDRESS>:34302 - "GET /home HTTP/1.0" 404
2021-06-13 10:15:00,987   INFO     uvicorn.access: <IP_ADDRESS>:34838 - "GET /home HTTP/1.0" 404
2021-06-13 10:17:25,182   INFO     uvicorn.access: <IP_ADDRESS>:34980 - "GET / HTTP/1.0" 200
2021-06-13 10:17:25,621   INFO     uvicorn.access: <IP_ADDRESS>:34992 - "GET / HTTP/1.0" 200
2021-06-13 10:17:25,636   INFO     uvicorn.access: <IP_ADDRESS>:34998 - "GET /token HTTP/1.0" 404
2021-06-13 10:17:25,648   INFO     uvicorn.access: <IP_ADDRESS>:35004 - "GET /user/ajax/menu-bar?ts=1623578400&_=796 HTTP/1.0" 404
2021-06-13 10:17:25,660   INFO     uvicorn.access: <IP_ADDRESS>:35010 - "GET / HTTP/1.0" 200
2021-06-13 10:25:01,455   INFO     uvicorn.access: <IP_ADDRESS>:35468 - "GET /home HTTP/1.0" 404
2021-06-13 10:35:02,000   INFO     uvicorn.access: <IP_ADDRESS>:35950 - "GET /home HTTP/1.0" 404
2021-06-13 10:45:02,443   INFO     uvicorn.access: <IP_ADDRESS>:36432 - "GET /home HTTP/1.0" 404
2021-06-13 10:47:31,977   INFO     uvicorn.access: <IP_ADDRESS>:36550 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 10:47:35,754   INFO     uvicorn.access: <IP_ADDRESS>:36556 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 10:47:39,444   INFO     uvicorn.access: <IP_ADDRESS>:36558 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 10:47:41,995   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 10:47:41,995   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:63212 on listener 'tcp-ssl-1'
2021-06-13 10:55:02,881   INFO     uvicorn.access: <IP_ADDRESS>:36916 - "GET /home HTTP/1.0" 404
2021-06-13 11:05:03,345   INFO     uvicorn.access: <IP_ADDRESS>:38496 - "GET /home HTTP/1.0" 404
2021-06-13 11:08:42,582   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 11:15:03,827   INFO     uvicorn.access: <IP_ADDRESS>:39030 - "GET /home HTTP/1.0" 404
2021-06-13 11:25:04,255   INFO     uvicorn.access: <IP_ADDRESS>:39512 - "GET /home HTTP/1.0" 404
2021-06-13 11:35:04,720   INFO     uvicorn.access: <IP_ADDRESS>:40016 - "GET /home HTTP/1.0" 404
2021-06-13 11:45:05,134   INFO     uvicorn.access: <IP_ADDRESS>:40498 - "GET /home HTTP/1.0" 404
2021-06-13 11:55:05,688   INFO     uvicorn.access: <IP_ADDRESS>:40980 - "GET /home HTTP/1.0" 404
2021-06-13 11:58:19,057   INFO     uvicorn.access: <IP_ADDRESS>:41162 - "GET / HTTP/1.0" 200
2021-06-13 11:58:19,510   INFO     uvicorn.access: <IP_ADDRESS>:41174 - "GET / HTTP/1.0" 200
2021-06-13 11:58:19,531   INFO     uvicorn.access: <IP_ADDRESS>:41180 - "GET /token HTTP/1.0" 404
2021-06-13 11:58:19,545   INFO     uvicorn.access: <IP_ADDRESS>:41186 - "GET /user/ajax/menu-bar?ts=1623582000&_=748 HTTP/1.0" 404
2021-06-13 11:58:19,557   INFO     uvicorn.access: <IP_ADDRESS>:41192 - "GET / HTTP/1.0" 200
2021-06-13 12:05:06,210   INFO     uvicorn.access: <IP_ADDRESS>:42708 - "GET /home HTTP/1.0" 404
2021-06-13 12:15:06,615   INFO     uvicorn.access: <IP_ADDRESS>:43256 - "GET /home HTTP/1.0" 404
2021-06-13 12:25:07,016   INFO     uvicorn.access: <IP_ADDRESS>:43740 - "GET /home HTTP/1.0" 404
2021-06-13 12:35:07,506   INFO     uvicorn.access: <IP_ADDRESS>:44222 - "GET /home HTTP/1.0" 404
2021-06-13 12:45:07,965   INFO     uvicorn.access: <IP_ADDRESS>:44704 - "GET /home HTTP/1.0" 404
2021-06-13 12:48:26,567   INFO     uvicorn.access: <IP_ADDRESS>:44862 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 12:48:30,346   INFO     uvicorn.access: <IP_ADDRESS>:44868 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 12:48:51,036   INFO     uvicorn.access: <IP_ADDRESS>:44886 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 12:48:52,535   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 12:48:52,536   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:52174 on listener 'tcp-ssl-1'
2021-06-13 12:55:08,566   INFO     uvicorn.access: <IP_ADDRESS>:45192 - "GET /home HTTP/1.0" 404
2021-06-13 13:05:09,017   INFO     uvicorn.access: <IP_ADDRESS>:45674 - "GET /home HTTP/1.0" 404
2021-06-13 13:09:40,694   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 13:15:09,448   INFO     uvicorn.access: <IP_ADDRESS>:47320 - "GET /home HTTP/1.0" 404
2021-06-13 13:25:09,903   INFO     uvicorn.access: <IP_ADDRESS>:47802 - "GET /home HTTP/1.0" 404
2021-06-13 13:35:10,344   INFO     uvicorn.access: <IP_ADDRESS>:48280 - "GET /home HTTP/1.0" 404
2021-06-13 13:38:53,934   INFO     uvicorn.access: <IP_ADDRESS>:48486 - "GET / HTTP/1.0" 200
2021-06-13 13:38:54,414   INFO     uvicorn.access: <IP_ADDRESS>:48498 - "GET / HTTP/1.0" 200
2021-06-13 13:38:54,435   INFO     uvicorn.access: <IP_ADDRESS>:48504 - "GET /token HTTP/1.0" 404
2021-06-13 13:38:54,450   INFO     uvicorn.access: <IP_ADDRESS>:48510 - "GET /user/ajax/menu-bar?ts=1623589200&_=796 HTTP/1.0" 404
2021-06-13 13:38:54,462   INFO     uvicorn.access: <IP_ADDRESS>:48516 - "GET / HTTP/1.0" 200
2021-06-13 13:45:13,131   INFO     uvicorn.access: <IP_ADDRESS>:48914 - "GET /home HTTP/1.0" 404
2021-06-13 13:55:13,659   INFO     uvicorn.access: <IP_ADDRESS>:49396 - "GET /home HTTP/1.0" 404
2021-06-13 14:05:14,137   INFO     uvicorn.access: <IP_ADDRESS>:49874 - "GET /home HTTP/1.0" 404
2021-06-13 14:15:14,583   INFO     uvicorn.access: <IP_ADDRESS>:51506 - "GET /home HTTP/1.0" 404
2021-06-13 14:25:20,699   INFO     uvicorn.access: <IP_ADDRESS>:51992 - "GET /home HTTP/1.0" 404
2021-06-13 14:35:21,262   INFO     uvicorn.access: <IP_ADDRESS>:52474 - "GET /home HTTP/1.0" 404
2021-06-13 14:45:21,745   INFO     uvicorn.access: <IP_ADDRESS>:52956 - "GET /home HTTP/1.0" 404
2021-06-13 14:49:26,793   INFO     uvicorn.access: <IP_ADDRESS>:53162 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 14:49:30,573   INFO     uvicorn.access: <IP_ADDRESS>:53168 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 14:49:34,386   INFO     uvicorn.access: <IP_ADDRESS>:53174 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 14:49:36,913   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 14:49:36,913   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:51621 on listener 'tcp-ssl-1'
2021-06-13 14:55:22,297   INFO     uvicorn.access: <IP_ADDRESS>:53456 - "GET /home HTTP/1.0" 404
2021-06-13 15:05:22,758   INFO     uvicorn.access: <IP_ADDRESS>:53938 - "GET /home HTTP/1.0" 404
2021-06-13 15:10:42,902   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 15:15:23,234   INFO     uvicorn.access: <IP_ADDRESS>:54472 - "GET /home HTTP/1.0" 404
2021-06-13 15:19:48,810   INFO     uvicorn.access: <IP_ADDRESS>:55808 - "GET / HTTP/1.0" 200
2021-06-13 15:19:49,749   INFO     uvicorn.access: <IP_ADDRESS>:55820 - "GET / HTTP/1.0" 200
2021-06-13 15:19:49,761   INFO     uvicorn.access: <IP_ADDRESS>:55826 - "GET /token HTTP/1.0" 404
2021-06-13 15:19:49,774   INFO     uvicorn.access: <IP_ADDRESS>:55832 - "GET /user/ajax/menu-bar?ts=1623596400&_=796 HTTP/1.0" 404
2021-06-13 15:19:49,786   INFO     uvicorn.access: <IP_ADDRESS>:55838 - "GET / HTTP/1.0" 200
2021-06-13 15:25:23,666   INFO     uvicorn.access: <IP_ADDRESS>:56200 - "GET /home HTTP/1.0" 404
2021-06-13 15:35:24,188   INFO     uvicorn.access: <IP_ADDRESS>:56678 - "GET /home HTTP/1.0" 404
2021-06-13 15:45:24,635   INFO     uvicorn.access: <IP_ADDRESS>:57160 - "GET /home HTTP/1.0" 404
2021-06-13 15:55:25,145   INFO     uvicorn.access: <IP_ADDRESS>:57642 - "GET /home HTTP/1.0" 404
2021-06-13 16:05:25,674   INFO     uvicorn.access: <IP_ADDRESS>:58124 - "GET /home HTTP/1.0" 404
2021-06-13 16:15:26,124   INFO     uvicorn.access: <IP_ADDRESS>:58678 - "GET /home HTTP/1.0" 404
2021-06-13 16:25:26,526   INFO     uvicorn.access: <IP_ADDRESS>:60256 - "GET /home HTTP/1.0" 404
2021-06-13 16:35:27,046   INFO     uvicorn.access: <IP_ADDRESS>:60738 - "GET /home HTTP/1.0" 404
2021-06-13 16:45:27,510   INFO     uvicorn.access: <IP_ADDRESS>:32988 - "GET /home HTTP/1.0" 404
2021-06-13 16:50:22,202   INFO     uvicorn.access: <IP_ADDRESS>:33222 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 16:50:25,937   INFO     uvicorn.access: <IP_ADDRESS>:33224 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 16:50:29,777   INFO     uvicorn.access: <IP_ADDRESS>:33230 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 16:50:32,327   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 16:50:32,327   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:57429 on listener 'tcp-ssl-1'
2021-06-13 16:55:27,958   INFO     uvicorn.access: <IP_ADDRESS>:33476 - "GET /home HTTP/1.0" 404
2021-06-13 17:00:26,849   INFO     uvicorn.access: <IP_ADDRESS>:33738 - "GET / HTTP/1.0" 200
2021-06-13 17:00:27,321   INFO     uvicorn.access: <IP_ADDRESS>:33750 - "GET / HTTP/1.0" 200
2021-06-13 17:00:27,336   INFO     uvicorn.access: <IP_ADDRESS>:33756 - "GET /token HTTP/1.0" 404
2021-06-13 17:00:27,348   INFO     uvicorn.access: <IP_ADDRESS>:33762 - "GET /user/ajax/menu-bar?ts=1623603600&_=748 HTTP/1.0" 404
2021-06-13 17:00:27,360   INFO     uvicorn.access: <IP_ADDRESS>:33768 - "GET / HTTP/1.0" 200
2021-06-13 17:05:28,356   INFO     uvicorn.access: <IP_ADDRESS>:34102 - "GET /home HTTP/1.0" 404
2021-06-13 17:11:57,398   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 17:15:28,790   INFO     uvicorn.access: <IP_ADDRESS>:34584 - "GET /home HTTP/1.0" 404
2021-06-13 17:25:29,197   INFO     uvicorn.access: <IP_ADDRESS>:35118 - "GET /home HTTP/1.0" 404
2021-06-13 17:35:29,610   INFO     uvicorn.access: <IP_ADDRESS>:36698 - "GET /home HTTP/1.0" 404
2021-06-13 17:45:30,120   INFO     uvicorn.access: <IP_ADDRESS>:37180 - "GET /home HTTP/1.0" 404
2021-06-13 17:55:30,711   INFO     uvicorn.access: <IP_ADDRESS>:37662 - "GET /home HTTP/1.0" 404
2021-06-13 18:05:31,117   INFO     uvicorn.access: <IP_ADDRESS>:38144 - "GET /home HTTP/1.0" 404
2021-06-13 18:15:31,596   INFO     uvicorn.access: <IP_ADDRESS>:38626 - "GET /home HTTP/1.0" 404
2021-06-13 18:25:32,034   INFO     uvicorn.access: <IP_ADDRESS>:39156 - "GET /home HTTP/1.0" 404
2021-06-13 18:35:32,436   INFO     uvicorn.access: <IP_ADDRESS>:40750 - "GET /home HTTP/1.0" 404
2021-06-13 18:40:58,545   INFO     uvicorn.access: <IP_ADDRESS>:41036 - "GET / HTTP/1.0" 200
2021-06-13 18:40:58,990   INFO     uvicorn.access: <IP_ADDRESS>:41048 - "GET / HTTP/1.0" 200
2021-06-13 18:40:59,005   INFO     uvicorn.access: <IP_ADDRESS>:41054 - "GET /token HTTP/1.0" 404
2021-06-13 18:40:59,017   INFO     uvicorn.access: <IP_ADDRESS>:41060 - "GET /user/ajax/menu-bar?ts=1623607200&_=748 HTTP/1.0" 404
2021-06-13 18:40:59,029   INFO     uvicorn.access: <IP_ADDRESS>:41066 - "GET / HTTP/1.0" 200
2021-06-13 18:45:32,867   INFO     uvicorn.access: <IP_ADDRESS>:41382 - "GET /home HTTP/1.0" 404
2021-06-13 18:51:18,857   INFO     uvicorn.access: <IP_ADDRESS>:41656 - "POST /api/v1/kronos/gateways HTTP/1.0" 200
2021-06-13 18:51:22,731   INFO     uvicorn.access: <IP_ADDRESS>:41662 - "GET /api/v1/kronos/gateways/d04b3e0934f35ee0f523d5c8e1b734dc88ef7c4c/config HTTP/1.0" 200
2021-06-13 18:51:26,522   INFO     uvicorn.access: <IP_ADDRESS>:41668 - "POST /api/v1/kronos/devices HTTP/1.0" 200
2021-06-13 18:51:28,763   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 2 connections acquired
2021-06-13 18:51:28,763   INFO     hbmqtt.broker: Connection from <IP_ADDRESS>:54839 on listener 'tcp-ssl-1'
2021-06-13 18:55:33,383   INFO     uvicorn.access: <IP_ADDRESS>:41870 - "GET /home HTTP/1.0" 404
2021-06-13 19:05:33,801   INFO     uvicorn.access: <IP_ADDRESS>:42352 - "GET /home HTTP/1.0" 404
2021-06-13 19:12:39,126   INFO     hbmqtt.broker: Listener 'tcp-ssl-1': 1 connections acquired
2021-06-13 19:15:34,283   INFO     uvicorn.access: <IP_ADDRESS>:42834 - "GET /home HTTP/1.0" 404
2021-06-13 19:25:34,794   INFO     uvicorn.access: <IP_ADDRESS>:43316 - "GET /home HTTP/1.0" 404
2021-06-13 19:35:35,202   INFO     uvicorn.access: <IP_ADDRESS>:43864 - "GET /home HTTP/1.0" 404
2021-06-13 19:45:35,753   INFO     uvicorn.access: <IP_ADDRESS>:45438 - "GET /home HTTP/1.0" 404
2021-06-13 19:55:36,172   INFO     uvicorn.access: <IP_ADDRESS>:45920 - "GET /home HTTP/1.0" 404
2021-06-13 20:00:28,252   ERROR    feeder.util.mqtt.client: Failed to decode message: bytearray(b'{"_|deviceHid":"cf4b00fd99b69286da9737c7bf4cbfba93b42e06","s|msg_type":"trace","i|tl":64,"s|ts":"Results - Actual: 536932240 tbsp(1g), End: 334565, \xf0\x08\xf8O\xf4\x80P\x01hI\x1c\x01"}')
Traceback (most recent call last):
  File "/tmp/feeder/util/mqtt/client.py", line 102, in handle_message
    payload = json.loads(packet.payload.data)
  File "/usr/local/lib/python3.8/json/__init__.py", line 343, in loads
    s = s.decode(detect_encoding(s), 'surrogatepass')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf0 in position 148: invalid continuation byte

Thanks in advance, for any help you can provide!

Is this still happening, @phrend ?

@kruton I'm sorry to say that I could not get my feeder to reliably respond to changes in the feeding schedule. With the right combination of reboots and luck, it would sometimes update, but since a change to my feeding schedule is almost always linked to me going away from home and needing to depend on the feeder to feed my pets, I decided to buy a new feeder from another manufacturer. (I kept my PetNet, with the idea that I might replace the controller with an ESP-32 or that this software might find better ways of dealing with the existing hardware/software limitations, but it's not currently in use.)


iOS 9 emoji label size calculation

Hi!
Thanks for the great UI component!
I have following issue when displaying label with emoji inside.

So from the right side there is a space for emoji but it is not used.
Here is what I receive in 'sizeThatFits' method:

I've managed to fix this by adding following lines to my attributed string:
    NSMutableParagraphStyle* style = [NSMutableParagraphStyle new];
    style.lineBreakMode = NSLineBreakByCharWrapping;

And received the result:

But this fix breaks simple and mixed text.
On iOS 8.4 there is no such issues.
Have anyone faced such problem and knows how to deal with it?

I have encountered the same problem and setting the label's preferredMaxLayoutWidth to a non-zero value fixed it for me.


Allow for configurable org/space/user

This changes the hard coded "CATS" names to configurable items for those using this repo outside of CATS.
Signed-off-by: Paul Warren<EMAIL_ADDRESS>

Looks good, merged.


Minor error in vector API reset method

For the vector API, reset method (https://www.gymlibrary.ml/content/vector_api/#reset), currently it shows

Note that for the parameter "options" - If to return the options
I doubt the actually meaning is

that is options actually is the reset option

Thanks for spotting this, we will update it

By the way, is it possible to pass different options for each of the environment in VecEnv, like how we handle the seed argument? The current implementation can only pass the same option to all the environments. Although we can pass a single option (which is actually a list of options) to every environment, and let each environment read its own option from the list, but I think it's better if there's an elegant official API.

Definitely will do! The implementation should not be that difficult.

发件人: Mark Towers @.>
发送时间: Monday, June 13, 2022 7:20:47 PM
收件人: Farama-Foundation/gym-docs @.>
抄送: Shuffle-Official @.>; Author @.>
主题: Re: [Farama-Foundation/gym-docs] Minor error in vector API reset method (Issue #150)
Interesting idea, currently that is not a feature, would you want to make the PR?
―
Reply to this email directly, view it on GitHubhttps://github.com/Farama-Foundation/gym-docs/issues/150#issuecomment-1153793497, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGCUWJTUZQCJHQ4E2I5X3N3VO4KQ7ANCNFSM5YRXVWFA.
You are receiving this because you authored the thread.Message ID: @.***>


zmath: Add perspectiveFovLhGl()

I thought it might be useful to provide a left-handed variant of perspectiveFovRhGl() that also makes use of the entire OpenGL default [-1, 1] range and yields the desired result. This neatly completes the set of the four perspectiveFov() variants.
The previous perspective functions didn't have any tests and I wouldn't know where to start 😅 but if a demonstration is enough, here are the results of using the four perspectiveFov() to render a clipped cube in OpenGL. The cube is 2x2x2 and positioned in the center of a frustum where far - near = 1. Only the GL variants clip correctly.

Thanks for the PR and for the demonstration!


jsonstream.cpp warning regarding an unused variable under ARM

src/jsonstream.cpp:194:14: warning: unused variable ‘supports’ [-Wunused-variable]
     uint32_t supports = detect_supported_architectures();
              ^~~~~~~~

Hmm. This change caused the quick arm64 tests to fail.

Did it? Where is the failing test? In CI?


Use AccumulatedMouseMotion, AccumulatedMouseScroll in examples

Objective
Use the new AccumulatedMouseMotion and AccumulatedMouseScroll resources in place of mouse event handling.
I left the mouse_input_events example alone, since by its nature it demonstrates event detection.
Fixes #14066
Testing
Ran each example locally before and after changes.

The Vec2::ZERO checks probably aren't super necessary

Ah yeah, probably a touch over-zealous! :laughing:


Change "Important Shortcuts" on Welcome Page, AI interface and Documentation since you've changed it in code

Context
Ctrl + O right now has been changed to open new file/directory (which is right), so you might want to change description of shortcuts on a Welcome page as well, here's the screenshot what I mean:
Here:

Also here:

Also don't forget to change it in the docs as well: https://trypear.ai/docs/important-shortcuts
Solution
@Fryingpannn @nang-dev Since you're the authors and did Shortcuts changes, pls look at this.
I would do it myself but I just don't really know the actual changes you guys have made, but it should be fast and easy

Nvm, I think all the commands here are valid, I'll just do a little bit of refinement on docs: https://github.com/trypear/pearai-documentation/pull/9


[Bug]: When the library administrator approves the work order whose library administrator privileges have been deleted, click OK or Reject, and two prompt boxes with the same prompt will pop up.

ODC version
ODC 4.3.0
OB version
No related
What happened?
When the library administrator approves the work order whose library administrator privileges have been deleted, click OK or Reject, and two prompt boxes with the same prompt will pop up.

What did you expect to happen?
The same error only pops up once
How can we reproduce it (as minimally and precisely as possible)?
Use the library administrator to approve a work order and enter the confirmation or rejection page. At this time, use an account with the project library administrator's deletion permission to delete the administrator. At this time, return to the library administrator's approval or rejection interface and click approve or reject. Two identical error messages will pop up on the interface.
Anything else we need to know?
No response

Fixed In Commit 29528084deeb56f8d2a1bcf064198310000fbf79
------
畅晚
Fri May 31 13:55:27 2024 +0800

PASS


Update package.json

Add project repository -- I tried to find the source from npmjs.com and couldn't; this should fix that.

Thanks!


The paginate method is incorrect work with the distinct method

Laravel Version: 5.3.9
PHP Version: 7.0.10
Database Driver & Version: mysql 5.6.31

Description:
When I use the distinct method with the paginate method followed, the response result's 'total' is incorrect
Steps To Reproduce:
like this...
        $result = DB::table('users')
            ->leftJoin('students','students.user_id','=','users.id')
            ->leftJoin('wrong_questions','wrong_questions.student_id','=','students.id')
            ->leftJoin('questions','questions.id','=','wrong_questions.question_id')
            ->leftJoin('question_knowledges','question_knowledges.question_id','=','questions.id')
            ->leftJoin('knowledge_points','knowledge_points.id','=','question_knowledges.knowledge_point_id')
            ->leftJoin('course_points','course_points.knowledge_point_id','=','knowledge_points.id')
            ->leftJoin('courses','course_points.course_id','=','courses.id')
            ->select('questions.id as questionId',
                'questions.question_outline as questionOutline',
                'courses.name as courseName'
            )->distinct()
            ->where('users.id', $userId)
            ->orderBy('wrong_questions.updated_at','desc')
            //->groupBy('questions.id')
            ->paginate(10);
        return response()->json(['WrongQuestionList' => $result]);

the response JSON is:
{
    WrongQuestionList: {
        total: 3,
        per_page: 10,
        current_page: 1,
        last_page: 1,
        next_page_url: null,
        prev_page_url: null,
        from: 1,
        to: 2,
        data: [
            {
                questionId: 2,
                questionOutline: "C语言for循环的注意事项",
                courseName: "C程序设计"
            },
            {
                questionId: 4,
                questionOutline: "C语言标识符",
                courseName: "C程序设计"
            }
        ]
    }
}

total should be 2, but it's 3, I solved my problem by add the groupBy method before paginate, I think is a bug and this is my first time to report bug on git,I'm a green hand.

Please mention the full laravel version.

Sorry, I added it.

I'm also facing the same issue with Laravel 5.1.11 and have reported the same on larachat a few weeks ago.

A PR was submitted a couple of days ago that attempts to fix the issue.

It looks like it's a nofix situation, I suggest you do this ->paginate(10, 'questions.id'); and your issue will be solved.

+1.

please reopen this, it's NOT related to groupBy. here is my code (snippet, simplified):
$entities = new Model();

$entities = $entities->leftJoin('accounts AS source_account', 'transactions.source_account_id', '=', 'source_account.id');
$entities = $entities->leftJoin('accounts AS target_account', 'transactions.target_account_id', '=', 'target_account.id');
$entities = $entities->join('categories', 'transactions.category_id', '=', 'categories.id');
$entities = $entities->leftJoin('label_transaction', 'transactions.id', '=', 'label_transaction.transaction_id');
$entities = $entities->leftJoin('labels', 'label_transaction.label_id', '=', 'labels.id');

$entities = $this->processWhereForTermFields($entities, $arguments);

$entities = $entities->select(
    'transactions.id AS id',
    'user_id',
    'source_account_id',
    'target_account_id',
    'category_id',
    'amount',
    'date',
    'comments',
    'transactions.created_at AS created_at',
    'transactions.updated_at AS updated_at'
)->distinct()->paginate(100);

altering the code like "->paginate(100, 'transactions.id');" was not a help.

My version of laravel is 5.5.* and i try it and dont work


Add support of ATTACH/DETACH PARTITION for ClickHouse

See:

https://clickhouse.com/docs/en/sql-reference/statements/alter/partition#attach-partitionpart
https://clickhouse.com/docs/en/sql-reference/statements/alter/partition#detach-partitionpart

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

52 of 53 (98.11%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 89.25%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/mod.rs
15
16
93.75%

Totals

Change from base Build<PHONE_NUMBER>3:
0.02%

Covered Lines:
27523

Relevant Lines:
30838

💛  - Coveralls


Error message if there is no floorplan defined in Domoticz

On the device list, there is a an error message "Unable to reach Domoticz server" if there is no floorplan defined. Everything else works fine.
Excellent work, I really like it!

Hi there. Are you sure that's the reason? I can't reproduce the issue at home even though I don't have any floorplans either.

I'm not sure but it seems to be related. I'm running Domoticz Beta v3.6591 on Rasp Pi
Chrome console:
Unable to reach Domoticz TypeError: Cannot read property 'length' of undefined
at RoomplanSelector.js:46
at JSONClientSingleton.js:65
And the Json response associated:
{
"status" : "OK",
"title" : "Plans"
}

In fact, it's related to scene. A control as you did for plan is missing:
if (!data.result) {
return;
}

Ah nice catch. I do have scenes, that's why I never noticed the issue. Thanks for fixing it yourself.


Game Board Grid Implementation with Consideration for Other Board Provided Board Skins for Easy Customization.

Description
Create the central game board using a grid layout with interactive tiles. Ensure that the Ludo tiles can move uniformly and parametrically on the board. The React component should accept props that make the movement of the Ludo tiles deterministic, in relation to the board component and its tiles:

[ ] Implement grid structure
[ ] Implement tile hover states
[ ] Make sure the tile can move determinstically like the description stated add transition to the movement
[ ] Add movement indicators
[ ] Mark sure it is responsive given that it could be a child component to a parent. Make sure there are adjustable breakpoint fpr the board component.

Technical Requirements:

Use Tailwind Grid for layout to ensure consistency
Implement tile components as reusable React components
Add proper spacing and borders
Match the design colors for different tile types
Ensure the grid scales properly on all screen sizes without causing overflow

May I pick this up?

May I try my hand at this?

Can I try solving this issue?

Can I start working on this?

I can handle this ser the description is straight to the point... I will send a PR in 48hrs

I'd be happy to do this.

Thank you @princeibs I'll get in with it now


set maximize flag for handled views

very small update.
as i used weston-terminal to test, the gaps were bothering me, and i thought of this.
when implementing floating windows later this should be unset for them.

Hmm, alright. I use urxvt on sway, fwiw.

i get urxvt: can't open display :1, aborting.
guess its what happens when running in x

works for me in x.

Make sure you have xwayland installed.

thanks, that works.


Create index.html

LGTM, but is the docs/ folder necessary or should we rather put the index.html in the root folder?

Removed docs/ folder.

Thanks!


The unfortunate thing is that the device does not require power supply as "Disabled"

Please use the search functionality before reporting an issue. Also take a look at the closed issues!
Issue description:
Specifies in the en_us.lang translation file that the device is not required for power operation is "Disabled". I believe that this term may mislead the user and should be "Not required", which makes it clear that no power supply is required for operation.
Steps to reproduce:

Change in the English variable (file en_us.lang) the term "control.disabled=Disabled" to "control.disabled=Not Required".

Version (make sure you are on the latest version before reporting):
Forge:
Mekanism:
Other relevant version:
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
[gist/pastebin/etc link here]

The terminology is correct. Disabled refers to the Redstone control.


Added Brazilian Portuguese (pt-br) language files

This pull request adds Brazilian Portuguese (pt-br) language files.

Hey! We went under a heavy localisation refactor a few days and I think some of these are still old translation keys - may you update to the latest version and recheck each please?
Here are the directories that contain translations:
https://github.com/laravel-filament/filament/tree/main/resources/lang
https://github.com/laravel-filament/filament/tree/main/packages/forms/resources/lang
https://github.com/laravel-filament/filament/tree/main/packages/tables/resources/lang

@danharrin I know it's not about this pr but are you open to have the French translations ? I can do this if you want this :)

@danharrin I know it's not about this pr but are you open to have the French translations ? I can do this if you want this :)

Hey! Yes, that would be perfect if you could.

Dan, please see if it’s suitable now. I have reviewed all the code.

Thank you so much @cpereiraweb! These are amazing.


add BSU txt

add bsu

@KaymMikael I am sorry, the domain g.batstate-u.edu.ph is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Option to Include Deleted Files with Diff

Related to #256, this PR adds an extra flag to diff that allows files deleted from the project, but present in the template, to be included in cruft diff output. This is especially helpful when trying to backport cruft / cookiecutter to existing projects for compliance.
I believe the work should be mostly compatible with PR #233, given that it affects how the cookiecutter is generated and only makes small changes to the diff step.  The argument may need clarifying in the event #233 is to be merged.

@millsks are you looking for maintainers? This is something that's being a big blocker for us right now.
@padraic-padraic how are you working around this right now?

I use my own fork, installed from git directly rather than pypi. The master branch includes this change plus a couple of other fixes I've opened PRs for.

@millsks are you looking for maintainers? This is something that's being a big blocker for us right now.
@padraic-padraic how are you working around this right now?

Hi Caio. I myself am not a maintainer for cruft. I have contributed in the past to include a new feature.

@samj1912 are you available to review and merge this PR?


CB-26928: Added security patches for Azure

This needs to be extended to other cloud providers and also tested, including FreeIPA images.


Update notebooks with factory and getter / setter

continue from #4269 , update more Jupyter notebooks with feature factory, tag getter / setter

If nobody objects, Ill merge this


Added Changes for bottom_sheet

Description
Fixes #4597.
Changed the drawables tint and the text color to the primary color of the android application to improve the themability and the user interface of the android application.
Tests performed
Tested 3.0.2-debug-master on Realme XT with API level 28.
Screenshots
Current bottom sheet:

Improved bottom sheet:

@madhurgupta10 @prtksxna @whym @mikehc Please review my  PR

@misaochan @translatewiki @yuvipanda @neslihanturan @maskaravivek @domdomegg @ashishkumar468 @madhurgupta10 @psh @brion @prtksxna @whym @mikehc @nicolas-raoul please review my Pull Request.

Thanks for your enthusiasm!
No need to ping everyone, as those of us who are interested in new PRs already receive notifications :-)
Also, have you read https://github.com/commons-app/commons-app-documentation/blob/master/android/Volunteers-welcome!.md , especially the part about the 5 issues with a "bug" or "good first issue" label?

Yes  Sir , I have read , Thanks for the suggestion .
Have a great day sir !
On Tue, Sep 14, 2021, 9:48 PM Nicolas Raoul @.***>
wrote:

Thanks for your enthusiasm!
No need to ping everyone, as those of us who are interested in new PRs
already receive notifications :-)
Also, have you read
https://github.com/commons-app/commons-app-documentation/blob/master/android/Volunteers-welcome!.md
, especially the part about the 5 issues with a "bug" or "good first issue"
label?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/pull/4598#issuecomment-919305785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANDEQKC6D3DSBIOOLQ5GUX3UB5YV3ANCNFSM5DEJ44ZQ
.

How about working on a few bugs first? That would be super-helpful :-)


Upgrade Node images with the Mar 2022 security releases

NodeJS recently released some new Security Updates.
https://nodejs.org/en/blog/vulnerability/mar-2022-security-releases/
There are plans to release versions with these new versions?

I can pick up this change.

Thanks @vaibsaraswat

@abnersajr PR is merged with nodeJs version: node:17.8.0-buster

@jordanpowell88 actually not all versions were released. There is the version 16.14.2, which is the version we are using.
I'm more than happy to contribute to this. The past week was hard for me, but this one I have some time.
Would you mind if I take it?

@abnersajr that would be fantastic!

@jordanpowell88 @abnersajr Have upgraded the version for browser as well: https://github.com/cypress-io/cypress-docker-images/pull/629


"var in object" check breaks highlighting when var is named "type"

1.45.0
function test(type, obj) {
	return type in obj && 'broken';
}

Happens in the latest grammar in my testing


Productize/cleanup01

Description
This PR does a bit of cleanup for the codebase by removing testing print statements, renaming variables, and adding to docstrings. This is part of https://github.com/scimma/snews/issues/8.
Other changes are:

retooled generate so that it sends one message by default, and can be specified to continuously send messages with -p to persist
clarified the looseThreshold parameter in the decider by renaming it (to emphasize that it's the coincidence threshold for messages) and adding it as an environment variable so it can be customized at runtime

Looks good!


feat(vercel): support on-demand static reganaration (isr)

🔗 Linked issue
https://github.com/unjs/nitro/issues/1694
❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] ✨ New feature (a non-breaking change that adds functionality)

📚 Description
It adds support for "On-Demand Incremental Static Regeneration (ISR)" for the Vercel preset.
Resolves #1694
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

@pi0 sry to ping you but wanted to know what the next steps here would be.
One thing I do not know is how I would go about testing this in vercel. But happy to do it with some guidance.
Thank you for your time

I cannot understand how to use it. Who can help me? Thanks a lot!

@TangsWang Have you tried steps in the docs ?


Suggestion: Could you provide a free font alternative?

Theme looks awesome. But, it would be great if you have an alternative version using a free font.
Congrats!

Sure! Fira Mono is one: https://github.com/tonsky/FiraCode. To be clear, this theme doesn't "use" Dank Mono, it's just the font in the screenshots because I knew people would ask. Thanks


Mockup multiple bonus content

Makes use of Session Granular in storyblok

No longer needed as we're going with a column view rather than a grid view for bonus content


Access to Receiver.ColorFormat

Hi, using your compiled jar as the basis for a library in B4J as I explained in #5 I have a testbed application functioning, but while I am I am able to set the FourCCType of the Sender, I'm having difficulties setting the ColorFormat of the Receiver.
I notice that you have a separate DevolayFrameFourCCType.java file which contains the enum relevant setting the VideoFrame FourCCType, but by comparison the enum relevant setting the Receiver ColorFormat are not in a similar "DevolayReceiverColorFormat.java" file.
This structure may be inherited from the original NewTek SDK, but I can't see how I can set the ColorFormat of the Receiver with my derived library.
However below is an image of my testbed app which shows an image being received via NDI sent from the NewTek Test Pattern tool.

I'm not sure how to apply this to B4J, but the expanded DevolayReceiver(DevolaySource, ColorFormat, int, boolean) constructor allows you to set the desired ColorFormat (I should probably make a utility constructor for just setting the ColorFormat, but I haven't yet).
However, the issue is that, as far as I can tell, the C API doesn't expose a way to get the color format of a receiver once it's created. This makes the ColorFormat.FASTEST and ColorFormat.BEST formats essentially useless, so I'm not sure why they don't.
Anyways, the default constructor is new DevolayReceiver(source, DevolayReceiver.ColorFormat.UYVY_BGRA, DevolayReceiver.RECEIVE_BANDWIDTH_HIGHEST, true, null);. If you want to set a ColorFormat, replacing UYVU_BGRA with the desired enum should work in most cases. From reading the docs, it looks like it's not guaranteed to be supported by all systems, though.

Thanks for the further information. I've now figured out how to access the Constructors with parameters  and so have been able to set the ColorFormat to BGRX_BGRA as I wanted.
Thanks for your great support!


remove lvalue overloads for as_array and as_object

Unfortunately, std::optional::operator-> means you can have a dangling reference:
std::optional<matjson::Value> foo();

auto& x = foo->as_array();
// x is dangling!

i see no way of fixing it other than just only allowing copying
this is an abi break, so will have to wait for geode v4.

ok no longer doing this as that would mean mutating the json as an array would be impossible. even standard c++ suffers from this, operator-> is just flawed when it comes to rvalues


New Feature : Add to top of Queue

Added two new methods for queue item and queue items to the top of the queue

Hi @senthilsivanath
Could you update this PR?
Also, I was thinking of using an enum to define where to add the items on the queue and passing that parameter in the current method. What do you think about that?
For now, the enum would have 2 cases: . beginning and .ending.


Support declaring nix system dependencies in Cargo.toml

e.g. when I have a -sys crate which links against C stuff using build.rs, and could reuse already installed stuff, it would be cool if I could declare a dependency in Cargo.toml (in the package.metadata section, e.g. [package.metadata.crate2nix]), and crate2nix should then (when giving a corresponding command line flag, e.g. should be opt-in) scan the whole dependency chain and add the appropriate dependencies.

alternative: allow specifying a map from "links" defined in Cargo.toml files to nixpkgs dependencies.

I think it is nicer to add native dependencies (at least of widely-used crates) to the default crate overrides. Then everyone benefits from them across all projects.

Ah ok.


Functional Tests need to be updated for Travis CI

Yesterday the version of Chromium installed for the Travis CI functional tests jumped to version 79. Initially this broke the tests due to an unsupported chromedriver version being manually downloaded, however once this was fixed it was found a significant number of tests in Legacy UI mode failed (mainly around selection sessions - skinny) and some in New UI (but for different reasons).
As a result, tests have been disabled for now on Travis:
https://github.com/openequella/openEQUELLA/blob/develop/.travis.yml#L68
We need to create a branch, re-enable the tests, and then figure out and fix what is happening.
Initial investigations show that when working on the issues locally you must:

Make sure you run the failing test with the matching version of chrome (or chromium) and chromedriver
Make sure you run headless
Make sure you match the UI mode (old vs new)

Also of interest, sometimes we'd see it fail the first time, then work the next.

I've set-up a branch to address this: https://github.com/openequella/openEQUELLA/tree/travis/fix-functional-tests
And on this branch (key) the tests are re-enabled.

@PenghaiZhang is currently waiting for the chromium-driver for version 80 to be available in the ubuntu packages.

All back now to using standard APT packages for Chromium and Chromium driver. Should stay in sync, and should be an improved way going forward.


Cannot set date outside date range

My use case is that a user cannot set a follow up date in the past, nor more than 10 days in the future by using the datepicker. However, when a user goes in to a record later, I cannot load that date if it is outside the startDate/endDate range and we need to display the database value regardless of the date range. The best I have been able to do is set the date in the input field prior to instantiating the datepicker. However, as soon as I click on the date field and exit by clicking elsewhere on the page, the date blanks out.
Is there a way to display a different value in the input field, but have the control only allow selection within the date range?

Hey @cdelstad, I'm not sure what your exact intentions are, but here's how I hacked a solution together for a similar problem. My issue was that we have an input field with a datepicker attached and listening with a startDate and endDate set. Users can interact with this input by clicking on it and choosing a date, or by typing in a date. In the case that the typed-in date is outside the instantiated start/endDate restrictions, the datepicker field is getting set to blank. To solve this, I set an event listener on the hide event and set the date on the datepicker to the original value it was instantiated with. We are using a sad mix of jQuery and React, so think of this more as pseudo-code:
const element = $("#your-input")
element.datepicker({
  yourOptions: ...
}).on("hide", (e) => {
  this.resetBlank();
});

resetBlank(element) {
  // This will reset the date field to the originally instantiated value in my case,
  // but you could use any `new Date` obj or date string (ie. "YYYY-MM-DD" etc) that is within the bounds.
  if (_.isEmpty(element.val())) {
    element.datepicker("setDate", this.props.value);
  }
}

This isn't a perfect solution imo because the date fields will silently change to the previously known date, but it is a quick hack to get things behaving without blank inputs.


Document how to get working with create react app

We should have a section in the readme similar to the css modules block that explains how to set emotion up when using create-react-app

Just going to document a few of my notes I have collected while trying to get both Emotion and Styled-JSX working with create-react-app.
Short Story: Currently its pretty difficult as far as I can tell, and sometimes requires manual editing of the compiled files to get it to play nicely.
Documented some of this in this gist: https://gist.github.com/hamlim/ede060b163a1d323ffebad97ef1cc03f which is specifically for Styled-JSX but follows the same pattern:

Install babel-cli and  emotion after setting up CRA
Edit the package.json file to add a babel entry point:

"babel": {
  "plugins": [
    "emotion/babel"
  ]
}

You may also need to install any plugins/presets as well and include them in the babel entry point if you are using anything that babel won't understand (i.e. babel-plugin-transform-object-rest-spread if you use { ...object })

Add a script to compile out Emotion uses:

"scripts": {
  "compile-emotion": "babel src/ --out-dir src/",
  // or for a cleaner dev experience:
  // "compile-emotion": "babel someSourceDirectory/ --out-dir src/"
}

Optionally copy src files to another dir like cleanSrc or any name so you can edit the source code in a clean folder and compile to /src where react-scripts will compile to browser runnable code
Example:

// directory structure:
someOtherSrcDirectory/
  app.js // where you actually write the code
src/
  app.js // compiled out after running `yarn run compile-emotion`

(Optional) If you do split the actual source code out to a new location you will need to copy over the compiled out *.emotion.css files to the src/ directory so they can get picked up when CRA picks up the second stage of compiling. (I haven't found an easy way to manually do this but I assume there is some unix command that you can run to copy those files over in the same directory structure.) (You would also need to do this for any other static assets like images, etc.)

In some of the compiled files babel might add some code at the top of the file above import statements. This will break CRA, and the only fix I have found so far is to manually move the imports above the code babel adds to the top of the file within the compiled src files (i.e. the ones that get generated after running compile-emotion from above).

Those are a few of the general steps I have found to get Emotion (as well as other babel-based libraries) to work with CRA. Ideally there should be an issue opened within create-react-app to track this pain point and address it at some point as it is pretty limiting in my opinion.
If you find something that I missed/found a way to get around any of these steps feel free to let me know/call it out. I would happy to open a PR to add some of this information to the docs once more people agree on the steps/phrasing!

@hamlim thanks for the info. It looks... complicated.
Have you seen this https://github.com/timarney/react-app-rewired
I think we may be able to do something like this.
https://github.com/timarney/react-app-rewired/blob/master/packages/react-app-rewire-relay/index.js#L7

Why go through all that? Why not eject? (genuinely curious)

Added some more comments to the twitter thread, figured I would come back here and explain some more. I haven't yet tried ejecting from CRA so not sure on the benefits/losses in doing so (Unsure on what you lose and what you gain out of ejecting).
React-app-rewired sounds like a really great solution to this issue, and sounds a lot (like a ton) better than my complicated process!

@hamlim thank you for your help. I got it working with react-app-rewired! I just need to release it

In the meantime, if anyone finds this thread.
npm install react-app-rewired --save-dev

// config-overrides.js
const babelLoader = function(conf) {
  if (!conf.loader) return false;
  return conf.loader.indexOf('babel-loader') > -1;
};

function rewireEmotion(config, env) {
  const babelrc = config.module.rules.find(babelLoader).options;
  babelrc.plugins = ['emotion/babel'].concat(babelrc.plugins || []);

  return config;
}

module.exports = function override(config, env) {
  config = rewireEmotion(config, env);
  return config;
};

// package.json
"scripts": {
  "start": "react-app-rewired start",
  "build": "react-app-rewired build",
  "test": "react-app-rewired test --env=jsdom"
},

For what it's worth, I've made an example of configuring an ejected Create React App application to use Emotion in conjunction with React Toolbox and CSS Modules. It's a lot simple than what was described earlier here, but not as simple as using react-app-rewired.
This example shows not only how to eject Create React App and configure Webpack and Babel for use with Emotion, but also how to configure them for React Toolbox, a popular material design implementation for React which utilizes CSS Modules.
Since emotion also plays well with CSS Modules, I thought I'd experiment with configuring CRA to utilize the two libraries together. This wasn't a ton of work, but could help out others looking to use CRA with Emotion if they're not interested to use a custom react-scripts implementation. It was largely for my own learning in how CSS Modules works and can be configured and composed, but I thought I might share it here in case it could be useful to someone else.

All it involves is:

Ejecting CRA to expose config and manually update react-scripts in the future
Adding plugins: [ "emotion/babel" ] to the babel section of package.json
Configuring Webpack files for React Toolbox and Emotion without conflict by using each library's suggested config settings

I tend to prefer to eject CRA instead of using third party react-scripts implementations like react-app-rewired, so I just wanted to document what that process would look like. But, since Emotion plays well with CSS Modules, I decided to also take this as an opportunity to finally configure React Toolbox the more idiomatic way, instead of using their themr.
In all honesty, an example of ejecting CRA and not involving react toolbox may be more beneficial to your users, but since this was a learning opportunity for myself, I involved it with the intent to explore composing the two together somehow before ruling out react toolbox for a beneficial example for emotion users altogether.
Finally, there's still some work to do to clean up the example a little bit, but it'll involve myself becoming a bit more familiar with Webpack and CSS Modules - so the example is in a "100% working but not perfect" stage for now.

Finally back to the issue, would it be beneficial to have two blessed examples for CRA usage with Emotion? I.e., 1 without ejecting, and 1 with ejecting?

For anyone trying to get emotion to work in a typescript CRA app:
https://gist.github.com/mrlundis/ca809eea890fa9fd5d98facd51cde731

@mrlundis This is amazing :-) !
I have spent a huge amount of time looking for a solution for exactly that :-) !
What is the reason for the babel config's need for further changes for production builds :-) ? Would yo be able to provide an example for a babel config :-) ?

Update to the comment above by @tkh44 on using react-app-rewired
Using<EMAIL_ADDRESS>&<EMAIL_ADDRESS>my config-overrides.js file was much simpler.
const { injectBabelPlugin } = require('react-app-rewired');

rewireEmotion = (config) => {
  return injectBabelPlugin('emotion/babel', config);
};

module.exports = rewireEmotion;

Or even better https://github.com/osdevisnot/react-app-rewire-contrib/tree/master/packages/react-app-rewire-emotion

aldreth's solution is almost perfect, I had to change emotion/babel to just emotion
As of today, this is working:
// config-overrides.js
const { injectBabelPlugin } = require('react-app-rewired');

rewireEmotion = (config) => {
    return injectBabelPlugin('emotion', config); // <-- updated
};

module.exports = rewireEmotion;

for reference, this is the error I get when using emotion/babel instead of emotion:
Module build failed: ReferenceError: Unknown plugin "emotion/babel" specified in "base" at 0, attempted to resolve relative to [path]

Version used:

react-scripts: 1.1.4
react-app-rewired: 1.5.2
babel-plugin-emotion: 9.2.6

So I guess you can now do
import styled from 'react-emotion/macro'

More info
https://emotion.sh/docs/babel-plugin-emotion#babel-macros

Sorry about commenting on closed issue but this is first Google hit for "react-create-app emotion" and there's no mention about the macro.


No error message for missing pre-requisites on Windows

New to micro - install your plugin via 'plugin install jump' but when I press the F4 key micro crashes/shuts down 🤔
(using micro on win10 - installed via choco)

Jump requires you to have the prerequisites installed and in your path, as listed in the README:

fzf
ctags

Do you have those in the path?

yes (both installed via choco)
Exuberant Ctags 5.8, Copyright (C) 1996-2009 Darren Hiebert
  Compiled: Jul  9 2009, 17:05:35
  Addresses<EMAIL_ADDRESS>http://ctags.sourceforge.net
  Optional compiled features: +win32, +regex, +internal-sort
PS C:\WINDOWS\system32> fzf --version
0.27.2 (e086f0b)```

Do you have bash?

...this look like a windows/bash problem - the used bash can't find fzf/ctags executables
I have recorded my try and for a few msec I have found these errors

Great, I think you found the problem.
Do you know how to add those commands to PATH in Windows bash? In Linux, that would be something like
$ export PATH="/path/to/fzf:/path/to/ctags:$PATH"

Micro was installed over choco here on my win10 machine (same for fzf/ctags)- but the bash came from installing the win10 Debian Linux stack (win10 store).
So I think the main thing to check (I don't know how) is which bash that choco installed micro is using at all ;)
but that is out of the scope of your plugin I think
I added fzf/ctags to my .bashrc
~$ echo $PATH
/mnt/c/ProgramData/chocolatey/bin/fzf.exe:/mnt/c/ProgramData/chocolatey/bin/ctags.exe:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files/WindowsApps/TheDebianProject.DebianGNULinux_<IP_ADDRESS>_x64__76v4gfsz19hv4:/mnt/c/Users/Hermann/AppData/Local/Programs/Python/Python39/Scripts/:/mnt/c/Users/Hermann/AppData/Local/Programs/Python/Python39/:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath:/mnt/c/ProgramData/Oracle/Java/javapath:/mnt/c/Program Files (x86)/Intel/iCLS Client/:/mnt/c/Program Files/Intel/iCLS Client/:/mnt/c/WINDOWS/system32:/mnt/c/Program Files/gs/gs9.52/bin:/mnt/c/Program Files/gs/gs9.52/lib:/mnt/c/Program Files/Inkscape/bin:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/ProgramData/Lenovo/ReadyApps:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/SourceGear/Common/DiffMerge/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/Intel/WiFi/bin/:/mnt/c/Program Files/Common Files/Intel/WirelessCommon/:/mnt/c/Program Files/PuTTY/:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/tools/BCURRAN3:/mnt/c/Program Files/dotnet/:/mnt/c/PHP:/mnt/c/Program Files (x86)/dotnet/:/mnt/c/Program Files/Git/cmd:/mnt/c/Users/Hermann/AppData/Local/Microsoft/WindowsApps

but that didn't change aynthing regarding the not found fzf/ctags when I click F4 key in micro.

That looks promising.
About the scope thing: maybe micro-jump can't solve that situation without human intervention, but it could still give an error message.
Micro-jump calls bash, fzf and ctags in a one-liner
bash -c  "ctags -f - --fields=n 'foo.go'|fzf --layout=reverse|tr ':' '\n'|tail -1"

So, it might be interesting to try (interactively, on your bash command line):
$ fzf
$ ctags -f - --fields=n foo.go

I can see that your binaries are named .exe, which differs from how micro-jump calls them.

Ok

reverted/uninstalled that fzf/ctags choco installations
installed fzf and ctags in the debian bash stack (through apt)
removed my own set paths to fzf/ctags windows versions

The fzf/ctags tests work in the debian bash stack
When I now run the choco installed micro and press F4 it doesn't crash anymore but I stand in the fzf screen (without any output)

I've recorded that test again and for a msec I can see a warning again - but only that (without any further ctags warnings/info/text) :(

You can test the main thing interactively to avoid millisecond timing. Replacing foo.go with your own file, what kind of error messages do you get?
$ ctags -f - --fields=n 'foo.go'
$ ctags -f - --fields=n 'foo.go'|fzf --layout=reverse
$ ctags -f - --fields=n 'foo.go'|fzf --layout=reverse|tr ':' '\n'|tail -1

all three commands looking good when I run them in the debian win10 linux stack bash but as said I don't know which bash micro is using (which was installed over choco 🤔)

You might get an idea what micro is using by calling bash from micro. What does this produce: ctrl-E
term bash --version

What are the first lines of the output of the commands above?

Unfortunately, it's unlikely to get this plugin to work on your system (Choko+Windows 10+Debian win10 Linux stack).
It will most likely require terminal emulation to run the plugin, because it uses terminal emulation to show fzf function selection dialog. In addition to that, your setup with multiple bashes is also a challenge. As you mentioned earlier, this is moving out of scope for micro-jump. Thus, I'm closing this issue.
Thank you for your report and prompt answers to my questions.


tensorboards of step 1 and step 2

could you plz share screenshots of the tensorboards for
Step1. Train the SyncNet Model
Step2. Train the Audio2motion model
over lrs3?
thanks.

Here you are. This audio2motion:

This is postnet for May.mp4

This is syncnet:


Failed to load save: invalid or unsupported verion.

Everytime I try to load and start to mod my borderlands 2 save file from horizon I get this message.

Same issue :(

The 2015 save editor worked fine for me a couple of years ago, but I am now getting this same issue with all versions of it. It will not let me open any of my Xbox 360 saves. It won't even let me re-open the saves that I newly made with the save editor itself. :(

@Brandon125911 Are you sure you're selecting Xbox 360 in the open file dialog?

I think that was the issue. It's been a while since I last used it. Thank
you for letting me know this. It works fine now.
On Fri, Apr 24, 2020 at 11:16 PM Rick Gibbed<EMAIL_ADDRESS>wrote:

@Brandon125911 https://github.com/Brandon125911 Are you sure you're
selecting Xbox 360 in the open file dialog?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gibbed/Gibbed.Borderlands2/issues/129#issuecomment-619261466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APKMIJIV4GO6PETMNEAGKULROIFTBANCNFSM4ILCNCPQ
.

I have extracted my Xbox 360 file in Horizon and opened it in Gibbed as a Xbox 360 save file and even if I try to put it back in Horizon without altering it, I get a message about an invalid signature type for the loaded package.  I have read many threads and have no idea what I am doing wrong.  In Gibbed in the general tab Xbox 360 is the selected platform.  Is there something I am doing wrong on Horizon to reopen it?  I am just dragging and dropping like I did my original save file.

You're probably not selecting the correct platform in the Open File dialog, in the file type.

Thanks so much for answering!!!  It was how I was putting it back in Horizon.  The manual I read said inject it back in Horizon, so I was dragging it in like the original file.  I finally found a video that showed right clicking on the file and replacing it.  That is where I went wrong.
On Monday, September 13, 2021, 09:09:28 PM CDT, Rick Gibbed @.***> wrote:
You're probably not selecting the correct platform in the Open File dialog, in the file type.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


feat(layer): layers proposal

am I correct to assume, that if folks in their application import this and start using it, if they create layers for themselves, our components will still respect those?

So what would be the implementation of <Layer>?
const Layer = ({ children }) => ReactDOM.createPortal(children, mountNode)

where the mountNode comes from the <LayerManager>?

In the current RFC we want to solve the first two issues (z-index and visibility management) on a component library level.

There are many more other layers related issues that include focus management, hover management, keyboard navigation, click events and hotkeys usage.

I think it would be nice to tackle all those other things as well so we have some idea what the final API
will be even if we introduce them in multiple iterations.
There are interesting aspects like some layers should disable the body scrolling (modals), some should trap the focus etc. So I wonder how could we make all those things configurable (more components or more props?).
It might be easier to prevent future breaking changes this way.

Could we make LayerManager as a part of the ThemeProvider so everyone gets it automatically? A lot of our components will need it to function, right?

Could we make LayerManager as a part of the ThemeProvider so everyone gets it automatically? A lot of our components will need it to function, right?
We could also rename ThemeProvider to BaseProvider but maybe not worth it.

I like the idea of combining the two. It also functions without the LayersManager in the way as before attaching the layers to the body elm.

It also functions without the LayersManager in the way as before attaching the layers to the body elm.

But once we want to also tackle the focus management etc, it will require to have a central authority (the context provider) in place, right?

right now, theme provider can safely be nested. will that be maintained if combined?

right now, theme provider can safely be nested. will that be maintained if combined?

We can detect that LayerManager is already present and not instantiate it again?

right now, theme provider can safely be nested. will that be maintained if combined?

We can detect that LayerManager is already present and not instantiate it again?

That's a good point, for the layers manager it's important to have it as the outermost wrapper, and the ThemeProvider may only be added as a component or part of app wrapper for instance.

ah good idea. seems like a nice approach

PRs #1147 - #1150 are merged


[Az.Reservations] Fix reservation update command to accept location …

…parameter

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Az.Reservations

Related change in swagger https://github.com/Azure/azure-rest-api-specs/pull/25192


Colcon does not log where it's expected to

Colcon logging options don't work as documented. It seems, contrary to the documentation, that:

$COLCON_HOME  is ignored for determining the logging location. Relative paths are always resolved relative to cwd. (in particular COLCON_LOG_PATH is documented as defaulting to $COLCON_HOME/log`, which is not the case)
COLCON_LOG_PATH handles /dev/null as documented, whereas --log-base crashes. This crash does not appear to produce log files anywhere.
Contrary to expectation, COLCON_LOG_PATH takes priority over the --log-base argument

$ colcon --help
...
optional arguments:
  -h, --help            show this help message and exit
  --log-base LOG_BASE   The base path for all log directories (default: log,
                        to disable: /dev/null)
  --log-level LOG_LEVEL
                        Set log level for the console output, either by
                        numeric or string value (default: warn)
...
Environment variables:
...
  COLCON_HOME           Set the configuration directory (default: ~/.colcon)
  COLCON_LOG_LEVEL      Set the log level (debug|10, info|20, warn|30,
                        error|40, critical|50, or any other positive numeric
                        value)
  COLCON_LOG_PATH       Set the log directory (default: $COLCON_HOME/log, to
                        disable: /dev/null)

test setup:
$ function logtest {
rm -rf /tmp/ws/ /tmp/colcon/ ~/.colcon/log
mkdir -p /tmp/ws/ /tmp/colcon/ ~/.colcon/log
cd /tmp/ws
eval ${1}
find ~/.colcon /tmp/colcon /tmp/ws -name log
}

test results (same in both zsh and bash):
$ logtest "colcon list"
/tmp/ws/log
$ logtest "COLCON_HOME=/tmp/colcon colcon list"
/tmp/ws/log
$ logtest "COLCON_HOME=/tmp/colcon colcon --log-base log list"
/tmp/ws/log
$ logtest "COLCON_HOME=/tmp/colcon COLCON_LOG_PATH=log colcon list"
/tmp/ws/log

$ logtest "COLCON_LOG_PATH=/dev/null colcon list"
$ logtest "colcon --log-base /dev/null list"
Traceback (most recent call last):
  File "/home/dan/.local/bin/colcon", line 8, in <module>
    sys.exit(main())
  File "/home/dan/.local/lib/python3.6/site-packages/colcon_core/command.py", line 161, in main
    create_log_path(args.verb_name)
  File "/home/dan/.local/lib/python3.6/site-packages/colcon_core/location.py", line 143, in create_log_path
    os.makedirs(str(path))
  File "/usr/lib/python3.6/os.py", line 220, in makedirs
    mkdir(name, mode)
NotADirectoryError: [Errno 20] Not a directory: '/dev/null/list_2019-10-31_11-17-18'

$ logtest "COLCON_LOG_PATH=/tmp/colcon/log colcon list"
/tmp/colcon/log
$ logtest "colcon --log-base /tmp/colcon/log list"
/tmp/colcon/log
$ logtest "COLCON_LOG_PATH=log COLCON_HOME=/tmp/colcon colcon list"
/tmp/ws/log
$ logtest "COLCON_LOG_PATH=/tmp/colcon/env/log colcon --log-base /tmp/colcon/arg/log list"
/tmp/colcon/env/log

Thanks for the detailed report. Please see #264 which should resolve all three issues.

Sweet! Thanks!


remove references to comcast in readme. change dns-id param to dns-txt-url

remove references to comcast in readme. change dns-id param to dns-txt-url

Codecov Report

Merging #165 into master will increase coverage by 0.25%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
+ Coverage   82.61%   82.86%   +0.25%
==========================================
  Files          39       39
  Lines        3584     3584
  Branches      313      313
==========================================
+ Hits         2961     2970       +9
+ Misses        385      376       -9
  Partials      238      238

Impacted Files
Coverage Δ

src/token.c
0% <0%> (ø)
:arrow_up:

tests/test_config.c
96.93% <100%> (ø)
:arrow_up:

src/config.c
74.33% <85.71%> (ø)
:arrow_up:

tests/test_client_list.c
91.42% <0%> (+6.42%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0a7d2f3...2aa134c. Read the comment docs.


Block activation of primary buttons on background screens

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/7623
Tests

Open two RHN modals and test that pressing enter does not trigger callback for background RHN screen.
Test the StoryBook that all pages are opening properly.

[x] Verify that no errors appear in the JS console

Contributor (PR Author) Checklist

[x] I verified the PR has a small number of commits behind main
[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I clearly indicated the environment tests should be run in (Staging vs Production)

[x] I wrote testing steps that cover success & fail scenarios (if applicable)
[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests & veryfy they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors related to changes in this PR
[x] I followed proper code patterns (see Reviewing the code)

[x] I added comments when the code was not self explanatory
[x] I put all copy / text shown in the product in all src/languages/* files (if applicable)
[x] I followed proper naming convention for platform-specific files (if applicable)
[x] I followed style guidelines (in Styling.md) for all style edits I made
[x] I followed the JSDocs style guidelines (in STYLE.md)

[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I corroborated the UI performance was not affected (the performance is the same than main branch)
[x] If I created a new component I verified that a similar component doesn't exist in the codebase

PR Reviewer Checklist

[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. “toggleReport” and not “onIconClick”).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct english, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct english and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components are not impacted by changes in this PR (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY
[x] I verified any variables that can be defined as constants (ie. in CONST.js) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] Any internal methods are bound to “this” properly so there are no scoping issues
[ ] Any internal methods bound to “this” are necessary to be bound
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function
(i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

QA Steps

Open any Workspace then its general settings.
Go to the Get assistance page via clicking ? on header.
Click on Request a setup Call.
Select any field and press Enter/Return.
Observer that it does not trigger save on Workspace general settings page And request a call is triggered.
Close Request a call page.
Press enter and observe that Workspace save operation is triggered.

Open Storybook at https://taging.new.expensify.com/docs/index.html. Check that Button Story is working fine.

Logout from the app on the web.
Login back and observe that you are able to login.

[ ] Verify that no errors appear in the JS console

Screenshots

Mobile Web

Desktop | Web

https://user-images.githubusercontent.com/24370807/159547375-047d087f-9185-410f-8948-510fbd79b657.mp4
iOS

Android

Can we add tests to make sure we don't fail the error boundary as well?

these are covered with StoryBook tests. Other than this, I don't QA will be able to test Error UI unless there is a app crash.

Tests well on web, running into issue building storybook but seems unrelated to this change

Open Storybook at taging.new.expensify.com/docs/index.html. Check that Button Story is working fine.

Link needs to be updated
Also can you add a SC for the storybook build? Running into an issue with @react-native-community/netinfo/jest/netinfo-mock when trying to run storybook

@thienlnam I reported the issue about storybook https://expensify.slack.com/archives/C01GTK53T8Q/p1651081332743029.
We will have to apply this fix https://expensify.slack.com/archives/C01GTK53T8Q/p1651082528577659?thread_ts=1651081332.743029&cid=C01GTK53T8Q to fix the stories. This is out of scope for this PR.

Updated.

Cool cool thanks!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by @sketchydroide in version: 1.1.57-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @chiragsalian in version: 1.1.57-17 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


IAPP Migration: Biological Treatments part II

Describe the Task
Migration of IAPP "Biological Treatments" into InvasivesBC app
Acceptance Criteria

[ ] Make UI

need a csv in order to start


No TOC header visible in index.html

Hi, I'm totally new to this and figuring out how this could benefit our project. It looks very promising!
Downloaded the example Unity project and opened it in Unity 2020.3.3f1.

Upgraded the project
Copied readme.md to /Documentation folder as stated
Build documentation in Terminal in VScode.
Open page, no 'Manual', 'Scripting API' and 'Search' as shown here: https://normanderwan.github.io/DocFxForUnity/

Notes:

The /Documentation/api/ folder is generated and the files are in there.
Only get 1 warning when building (Invalid cref value "!:AudioClip" found in triple-slash-comments for HurtClip, ignored.)
In /_site/toc.html contains the correct HREF definitions.

Tried on Firefox, Edge, Chrome.
Using Unity 2020.3.3f1
I feel like I'm just missing ONE thing somewhere.

The ONE thing was running it through a webserver apparently.
Firefox & Chrome developer tools for the win.


Issue installing Docker -  Permission denied: '/code/media/debug.log'

While installing Docker, I had an issue when running make makemigrations. I keep running into this error - Permission denied: '/code/media/debug.log'. When I looked at the permissions for the /code/media folder in the docker shell, I found: drwxr-xr-x  1   1000 staff   170 Apr 11 23:56 media. However, all of the other files look like they are owned by apache (ex: -rw-r--r--  1 apache root  39183 Mar 23 20:23 README.md). Aileen and I tried changing the permissions and owners within the docker shell, but nothing seemed to change and make makemigrations doesn't work.
@mechanicjay any thoughts?

Closing because we have likely solved this with newer Docker instructions and WSL2, etc.