Grafana now longer accessible

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Today i noticed that i'm no longer able to open grafana. The Home page 'http://teslamate..:4000/' is still available and works fine. I've updated teslamate and docker but i cannot access: http://teslamate..:3000/d/jchmRiqUfXgTM
The chrome browser throws the error 'ERR_CONNECTION_TIMED_OUT'.
Sometimes it does load half way but then grafana is showing 'no data' everywhere

It has allways worked. I checked it a few days ago and now i don't know what to do. Can someone point me in the right direction?
Expected Behavior
Browse the dashboard as usual.
Steps To Reproduce

open the teslamate home page: http://teslamate.*.:4000
Click on 'dashboards'
Click on 'Battery health' for example

Relevant log output
teslamate-1  | 2024-06-16 12:07:54.133 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/929702988599314/vehicle_data -> 408 (74.465 ms)
teslamate-1  | 2024-06-16 12:08:24.293 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/929702988599314/vehicle_data -> 408 (78.781 ms)
teslamate-1  | 2024-06-16 12:08:54.514 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/929702988599314/vehicle_data -> 408 (101.411 ms)
teslamate-1  | 2024-06-16 12:09:24.811 car_id=1 [info] Vehicle came back online after 1691 min
teslamate-1  | 2024-06-16 12:09:24.812 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 12:11:27.025 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 282, latitude: 52.074083, longitude: 4.76017, native_latitude: 52.074083, native_location_supported: 1, native_longitude: 4.76017, native_type: "wgs", power: 1, shift_state: "R", speed: 1, timestamp:<PHONE_NUMBER>963}
teslamate-1  | 2024-06-16 12:11:27.026 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-16 12:26:21.852 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (88.627 ms)
teslamate-1  | 2024-06-16 12:26:22.351 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (497.086 ms)
teslamate-1  | 2024-06-16 12:26:22.361 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 26, latitude: 52.125651, longitude: 4.625122, native_latitude: 52.125651, native_location_supported: 1, native_longitude: 4.625122, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>699}
teslamate-1  | 2024-06-16 12:26:22.361 car_id=1 [info] Driving / Ended / 14 km – 15 min
teslamate-1  | 2024-06-16 12:26:22.361 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 13:20:57.765 [info] Refreshing access token ...
teslamate-1  | 2024-06-16 13:20:58.048 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (282.805 ms)
teslamate-1  | 2024-06-16 13:20:58.052 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-16 13:54:52.836 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 26, latitude: 52.125652, longitude: 4.625123, native_latitude: 52.125652, native_location_supported: 1, native_longitude: 4.625123, native_type: "wgs", power: 1, shift_state: "R", speed: 1, timestamp:<PHONE_NUMBER>944}
teslamate-1  | 2024-06-16 13:54:52.837 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-16 14:06:15.456 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (119.970 ms)
teslamate-1  | 2024-06-16 14:06:16.021 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (561.072 ms)
teslamate-1  | 2024-06-16 14:06:16.031 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 146, latitude: 52.083327, longitude: 4.743829, native_latitude: 52.083327, native_location_supported: 1, native_longitude: 4.743829, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>518}
teslamate-1  | 2024-06-16 14:06:16.031 car_id=1 [info] Driving / Ended / 11 km – 11 min
teslamate-1  | 2024-06-16 14:06:16.032 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 14:29:29.401 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 126, latitude: 52.083374, longitude: 4.743793, native_latitude: 52.083374, native_location_supported: 1, native_longitude: 4.743793, native_type: "wgs", power: 2, shift_state: "R", speed: 1, timestamp:<PHONE_NUMBER>322}
teslamate-1  | 2024-06-16 14:29:29.401 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-16 14:36:45.874 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (114.448 ms)
teslamate-1  | 2024-06-16 14:36:46.368 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (491.306 ms)
teslamate-1  | 2024-06-16 14:36:46.379 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 284, latitude: 52.074092, longitude: 4.760163, native_latitude: 52.074092, native_location_supported: 1, native_longitude: 4.760163, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>566}
teslamate-1  | 2024-06-16 14:36:46.380 car_id=1 [info] Driving / Ended / 3 km – 7 min
teslamate-1  | 2024-06-16 14:36:46.380 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 14:55:09.854 car_id=1 [info] Suspending logging
teslamate-1  | 2024-06-16 15:16:10.004 car_id=1 [info] Start / :offline
teslamate-1  | 2024-06-16 17:27:41.858 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 17:28:27.352 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 283, latitude: 52.074082, longitude: 4.7602, native_latitude: 52.074082, native_location_supported: 1, native_longitude: 4.7602, native_type: "wgs", power: 2, shift_state: "R", speed: 1, timestamp:<PHONE_NUMBER>287}
teslamate-1  | 2024-06-16 17:28:27.353 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-16 17:32:22.236 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (113.028 ms)
teslamate-1  | 2024-06-16 17:32:22.732 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (491.553 ms)
teslamate-1  | 2024-06-16 17:32:22.750 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 23, latitude: 52.070735, longitude: 4.742091, native_latitude: 52.070735, native_location_supported: 1, native_longitude: 4.742091, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>024}
teslamate-1  | 2024-06-16 17:32:22.750 car_id=1 [info] Driving / Ended / 2 km – 4 min
teslamate-1  | 2024-06-16 17:32:22.750 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 17:33:53.958 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (102.716 ms)
teslamate-1  | 2024-06-16 17:33:53.975 car_id=1 [info] Charging / SOC: 49%
teslamate-1  | 2024-06-16 17:34:22.560 car_id=1 [info] Derived efficiency factor: 142.28 Wh/km (8x confirmed)
teslamate-1  | 2024-06-16 17:34:22.561 car_id=1 [info] Charging / Stopped / 0.00 kWh – 0 min
teslamate-1  | 2024-06-16 17:34:22.562 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 17:35:23.337 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 22, latitude: 52.070856, longitude: 4.742437, native_latitude: 52.070856, native_location_supported: 1, native_longitude: 4.742437, native_type: "wgs", power: 1, shift_state: "D", speed: 0, timestamp:<PHONE_NUMBER>279}
teslamate-1  | 2024-06-16 17:35:23.337 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-16 17:37:18.589 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (95.458 ms)
teslamate-1  | 2024-06-16 17:37:19.069 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (476.000 ms)
teslamate-1  | 2024-06-16 17:37:19.078 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 299, latitude: 52.067787, longitude: 4.739896, native_latitude: 52.067787, native_location_supported: 1, native_longitude: 4.739896, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>427}
teslamate-1  | 2024-06-16 17:37:19.078 car_id=1 [info] Driving / Ended / 1 km – 2 min
teslamate-1  | 2024-06-16 17:37:19.079 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 17:49:27.178 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 299, latitude: 52.067787, longitude: 4.739896, native_latitude: 52.067787, native_location_supported: 1, native_longitude: 4.739896, native_type: "wgs", power: 1, shift_state: "D", speed: 0, timestamp:<PHONE_NUMBER>104}
teslamate-1  | 2024-06-16 17:49:27.178 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-16 17:55:05.278 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (119.363 ms)
teslamate-1  | 2024-06-16 17:55:05.798 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (518.148 ms)
teslamate-1  | 2024-06-16 17:55:05.808 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 102, latitude: 52.074096, longitude: 4.760162, native_latitude: 52.074096, native_location_supported: 1, native_longitude: 4.760162, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>909}
teslamate-1  | 2024-06-16 17:55:05.808 car_id=1 [info] Driving / Ended / 3 km – 6 min
teslamate-1  | 2024-06-16 17:55:05.809 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-16 18:11:25.813 car_id=1 [info] Suspending logging
teslamate-1  | 2024-06-16 18:32:25.837 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/929702988599314 -> error: "socket closed" (22.210 ms)
teslamate-1  | 2024-06-16 18:32:25.838 [warning] TeslaApi.Error / socket closed
teslamate-1  | 2024-06-16 18:32:25.838 car_id=1 [error] Error / :unknown
teslamate-1  | 2024-06-16 18:32:56.008 car_id=1 [info] Start / :offline
teslamate-1  | 2024-06-16 19:20:58.053 [info] Refreshing access token ...
teslamate-1  | 2024-06-16 19:20:58.359 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (306.367 ms)
teslamate-1  | 2024-06-16 19:20:58.365 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-17 01:20:58.366 [info] Refreshing access token ...
teslamate-1  | 2024-06-17 01:20:58.850 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (484.263 ms)
teslamate-1  | 2024-06-17 01:20:58.856 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-17 05:08:27.742 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 05:38:54.111 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 11, latitude: 52.074221, longitude: 4.760337, native_latitude: 52.074221, native_location_supported: 1, native_longitude: 4.760337, native_type: "wgs", power: 6, shift_state: "D", speed: 11, timestamp:<PHONE_NUMBER>061}
teslamate-1  | 2024-06-17 05:38:54.112 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-17 05:42:58.368 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (159.131 ms)
teslamate-1  | 2024-06-17 05:42:58.885 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (514.017 ms)
teslamate-1  | 2024-06-17 05:42:58.894 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 204, latitude: 52.077582, longitude: 4.751104, native_latitude: 52.077582, native_location_supported: 1, native_longitude: 4.751104, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>147}
teslamate-1  | 2024-06-17 05:42:58.894 car_id=1 [info] Driving / Ended / 1 km – 4 min
teslamate-1  | 2024-06-17 05:42:58.894 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 05:52:02.669 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 114, latitude: 52.07755, longitude: 4.751163, native_latitude: 52.07755, native_location_supported: 1, native_longitude: 4.751163, native_type: "wgs", power: 0, shift_state: "R", speed: 2, timestamp:<PHONE_NUMBER>609}
teslamate-1  | 2024-06-17 05:52:02.671 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-17 05:56:09.726 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (127.393 ms)
teslamate-1  | 2024-06-17 05:56:10.195 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (466.330 ms)
teslamate-1  | 2024-06-17 05:56:10.208 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 107, latitude: 52.074081, longitude: 4.76016, native_latitude: 52.074081, native_location_supported: 1, native_longitude: 4.76016, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>391}
teslamate-1  | 2024-06-17 05:56:10.208 car_id=1 [info] Driving / Ended / 1 km – 4 min
teslamate-1  | 2024-06-17 05:56:10.208 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 06:11:17.889 car_id=1 [info] Suspending logging
teslamate-1  | 2024-06-17 06:32:18.049 car_id=1 [info] Start / :offline
teslamate-1  | 2024-06-17 07:20:58.858 [info] Refreshing access token ...
teslamate-1  | 2024-06-17 07:20:59.143 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (284.441 ms)
teslamate-1  | 2024-06-17 07:20:59.147 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-17 13:20:59.149 [info] Refreshing access token ...
teslamate-1  | 2024-06-17 13:20:59.444 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (294.993 ms)
teslamate-1  | 2024-06-17 13:20:59.449 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-17 13:31:33.585 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 13:44:07.163 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/929702988599314/vehicle_data -> 408 (222.205 ms)
teslamate-1  | 2024-06-17 13:44:17.605 car_id=1 [info] Start / :offline
teslamate-1  | 2024-06-17 15:12:13.727 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 15:15:55.045 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/929702988599314/vehicle_data -> 408 (9114.367 ms)
teslamate-1  | 2024-06-17 15:15:55.045 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
teslamate-1  | 2024-06-17 15:15:55.045 car_id=1 [error] Error / :unknown
teslamate-1  | 2024-06-17 15:16:15.257 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 98, latitude: 52.074428, longitude: 4.760753, native_latitude: 52.074428, native_location_supported: 1, native_longitude: 4.760753, native_type: "wgs", power: 16, shift_state: "D", speed: 17, timestamp:<PHONE_NUMBER>174}
teslamate-1  | 2024-06-17 15:16:15.259 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-17 15:22:59.881 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (160.860 ms)
teslamate-1  | 2024-06-17 15:23:00.360 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (477.124 ms)
teslamate-1  | 2024-06-17 15:23:00.369 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 320, latitude: 52.086118, longitude: 4.737982, native_latitude: 52.086118, native_location_supported: 1, native_longitude: 4.737982, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>666}
teslamate-1  | 2024-06-17 15:23:00.369 car_id=1 [info] Driving / Ended / 4 km – 7 min
teslamate-1  | 2024-06-17 15:23:00.369 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 15:46:26.335 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 320, latitude: 52.086118, longitude: 4.737982, native_latitude: 52.086118, native_location_supported: 1, native_longitude: 4.737982, native_type: "wgs", power: 2, shift_state: "D", speed: 0, timestamp:<PHONE_NUMBER>283}
teslamate-1  | 2024-06-17 15:46:26.335 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-17 15:52:35.088 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (130.883 ms)
teslamate-1  | 2024-06-17 15:52:35.650 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (559.526 ms)
teslamate-1  | 2024-06-17 15:52:35.659 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 206, latitude: 52.077578, longitude: 4.751118, native_latitude: 52.077578, native_location_supported: 1, native_longitude: 4.751118, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>733}
teslamate-1  | 2024-06-17 15:52:35.659 car_id=1 [info] Driving / Ended / 2 km – 6 min
teslamate-1  | 2024-06-17 15:52:35.659 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 16:11:30.067 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 78, latitude: 52.077544, longitude: 4.751195, native_latitude: 52.077544, native_location_supported: 1, native_longitude: 4.751195, native_type: "wgs", power: 0, shift_state: "D", speed: 4, timestamp:<PHONE_NUMBER>535}
teslamate-1  | 2024-06-17 16:11:30.067 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-17 16:16:11.533 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (255.649 ms)
teslamate-1  | 2024-06-17 16:16:11.914 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (378.269 ms)
teslamate-1  | 2024-06-17 16:16:11.923 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 104, latitude: 52.074077, longitude: 4.760163, native_latitude: 52.074077, native_location_supported: 1, native_longitude: 4.760163, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>708}
teslamate-1  | 2024-06-17 16:16:11.923 car_id=1 [info] Driving / Ended / 1 km – 5 min
teslamate-1  | 2024-06-17 16:16:11.923 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-17 16:32:51.194 car_id=1 [info] Suspending logging
teslamate-1  | 2024-06-17 16:53:51.670 car_id=1 [info] Vehicle is still online. Falling asleep for: 36 min
teslamate-1  | 2024-06-17 17:14:51.826 car_id=1 [info] Start / :offline
teslamate-1  | 2024-06-17 19:20:59.450 [info] Refreshing access token ...
teslamate-1  | 2024-06-17 19:20:59.746 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (296.438 ms)
teslamate-1  | 2024-06-17 19:20:59.752 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-18 01:20:59.753 [info] Refreshing access token ...
teslamate-1  | 2024-06-18 01:21:00.061 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (308.227 ms)
teslamate-1  | 2024-06-18 01:21:00.066 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-18 05:08:27.949 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-18 05:43:30.149 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 102, latitude: 52.07408, longitude: 4.760198, native_latitude: 52.07408, native_location_supported: 1, native_longitude: 4.760198, native_type: "wgs", power: 2, shift_state: "D", speed: 2, timestamp:<PHONE_NUMBER>657}
teslamate-1  | 2024-06-18 05:43:30.150 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-18 05:47:46.295 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (251.370 ms)
teslamate-1  | 2024-06-18 05:47:46.719 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (421.334 ms)
teslamate-1  | 2024-06-18 05:47:46.725 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 205, latitude: 52.077531, longitude: 4.751055, native_latitude: 52.077531, native_location_supported: 1, native_longitude: 4.751055, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>959}
teslamate-1  | 2024-06-18 05:47:46.725 car_id=1 [info] Driving / Ended / 1 km – 4 min
teslamate-1  | 2024-06-18 05:47:46.725 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-18 05:55:35.627 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 205, latitude: 52.077531, longitude: 4.751055, native_latitude: 52.077531, native_location_supported: 1, native_longitude: 4.751055, native_type: "wgs", power: 1, shift_state: "D", speed: 0, timestamp:<PHONE_NUMBER>559}
teslamate-1  | 2024-06-18 05:55:35.627 car_id=1 [info] Driving / Start
teslamate-1  | 2024-06-18 05:59:18.351 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (1044.187 ms)
teslamate-1  | 2024-06-18 05:59:18.455 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (101.408 ms)
teslamate-1  | 2024-06-18 05:59:18.470 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{active_route_destination: nil, active_route_energy_at_arrival: nil, active_route_latitude: 52.074091, active_route_longitude: 4.760074, active_route_miles_to_arrival: nil, active_route_minutes_to_arrival: nil, active_route_traffic_minutes_delay: 0.0, gps_as_of:<PHONE_NUMBER>, heading: 17, latitude: 52.081374, longitude: 4.747293, native_latitude: 52.081374, native_location_supported: 1, native_longitude: 4.747293, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>127}
teslamate-1  | 2024-06-18 05:59:18.470 car_id=1 [info] Driving / Ended / 1 km – 4 min
teslamate-1  | 2024-06-18 05:59:18.470 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-18 07:21:00.068 [info] Refreshing access token ...
teslamate-1  | 2024-06-18 07:21:00.365 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (296.912 ms)
teslamate-1  | 2024-06-18 07:21:00.369 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-18 07:54:50.591 [info] GET /settings
teslamate-1  | 2024-06-18 07:54:50.596 [info] Sent 200 in 5ms
teslamate-1  | 2024-06-18 07:54:51.346 [info] GET /settings
teslamate-1  | 2024-06-18 07:54:51.355 [info] Sent 200 in 8ms
teslamate-1  | 2024-06-18 07:54:54.224 [info] GET /
teslamate-1  | 2024-06-18 07:54:54.230 [info] Sent 200 in 5ms
teslamate-1  | 2024-06-18 07:55:34.895 [warning] MQTT connection has been dropped
teslamate-1  | 2024-06-18 07:55:34.895 [info] [Tortoise311] Connection went down. Reconnecting.
teslamate-1  | 2024-06-18 07:55:34.901 [warning] [Tortoise311] Connection failed: {:connection_refused, ~c"mosquitto", 1883}, %{port: 1883, status: :down, protocol: "MQTT", host: ~c"mosquitto", protocol_version: 4, keep_alive: 60, transport: Tortoise311.Transport.Tcp, subscriptions: %Tortoise311.Package.Subscribe{__META__: %Tortoise311.Package.Meta{opcode: 8, flags: 2}, identifier: nil, topics: []}, client_id: "TESLAMATE_302E3333323", clean_session: false}. Retrying in 100 msecs.
teslamate-1  | 2024-06-18 07:55:35.032 [warning] [Tortoise311] Connection failed: {:nxdomain, ~c"mosquitto", 1883}, %{port: 1883, status: :down, protocol: "MQTT", host: ~c"mosquitto", protocol_version: 4, keep_alive: 60, transport: Tortoise311.Transport.Tcp, subscriptions: %Tortoise311.Package.Subscribe{__META__: %Tortoise311.Package.Meta{opcode: 8, flags: 2}, identifier: nil, topics: []}, client_id: "TESLAMATE_302E3333323", clean_session: false}. Retrying in 200 msecs.
teslamate-1  | 2024-06-18 07:55:35.236 [warning] [Tortoise311] Connection failed: {:connection_refused, ~c"mosquitto", 1883}, %{port: 1883, status: :down, protocol: "MQTT", host: ~c"mosquitto", protocol_version: 4, keep_alive: 60, transport: Tortoise311.Transport.Tcp, subscriptions: %Tortoise311.Package.Subscribe{__META__: %Tortoise311.Package.Meta{opcode: 8, flags: 2}, identifier: nil, topics: []}, client_id: "TESLAMATE_302E3333323", clean_session: false}. Retrying in 400 msecs.
teslamate-1  | 2024-06-18 07:55:35.339 [error] Postgrex.Protocol (#PID<0.2450.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.339 [error] Postgrex.Protocol (#PID<0.2449.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.339 [error] Postgrex.Protocol (#PID<0.2452.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.343 [error] Postgrex.Protocol (#PID<0.2455.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.363 [error] Postgrex.Protocol (#PID<0.2444.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.371 [error] Postgrex.Protocol (#PID<0.2445.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.372 [error] Postgrex.Protocol (#PID<0.2450.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.379 [error] Postgrex.Protocol (#PID<0.2444.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.382 [error] Postgrex.Protocol (#PID<0.2448.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:35.382 [error] Postgrex.Protocol (#PID<0.2449.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.383 [error] Postgrex.Protocol (#PID<0.2455.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.387 [error] Postgrex.Protocol (#PID<0.2452.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.393 [error] Postgrex.Protocol (#PID<0.2448.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.399 [error] Postgrex.Protocol (#PID<0.2445.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate-1  | 2024-06-18 07:55:35.639 [info] MQTT connection has been established
teslamate-1  | 2024-06-18 07:55:36.339 [error] Postgrex.Protocol (#PID<0.2454.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:36.339 [error] Postgrex.Protocol (#PID<0.2453.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:36.339 [error] Postgrex.Protocol (#PID<0.2451.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:55:36.424 [notice] SIGTERM received - shutting down
teslamate-1  |
teslamate-1  | 2024-06-18 07:55:36.425 [info] Shutting down 2 sockets in 1 rounds of 2000ms
teslamate-1  | 2024-06-18 07:55:46.978 [info] Migrations already up
teslamate-1  | 2024-06-18 07:55:49.403 [info] System Info: Erlang/OTP 26 (jit)
teslamate-1  | 2024-06-18 07:55:49.403 [info] Version: 1.29.1
teslamate-1  | 2024-06-18 07:55:49.719 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (268.512 ms)
teslamate-1  | 2024-06-18 07:55:49.719 [info] Refreshed api tokens
teslamate-1  | 2024-06-18 07:55:49.731 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-18 07:55:49.747 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
teslamate-1  | 2024-06-18 07:55:49.750 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate-1  | 2024-06-18 07:55:49.777 [info] GET /
teslamate-1  | 2024-06-18 07:55:49.961 [info] GET /
teslamate-1  | 2024-06-18 07:55:50.138 [info] Starting logger for 'TessY'
teslamate-1  | 2024-06-18 07:55:50.145 [info] Sent 200 in 184ms
teslamate-1  | 2024-06-18 07:55:50.149 [info] MQTT connection has been established
teslamate-1  | 2024-06-18 07:55:50.367 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-18 07:56:41.836 [info] GET /settings
teslamate-1  | 2024-06-18 07:56:41.839 [info] GET /settings
teslamate-1  | 2024-06-18 07:56:41.847 [info] Sent 200 in 11ms
teslamate-1  | 2024-06-18 07:56:41.848 [info] Sent 200 in 8ms
teslamate-1  | 2024-06-18 07:56:42.193 [info] GET /settings
teslamate-1  | 2024-06-18 07:56:42.209 [info] Sent 200 in 16ms
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2451.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2453.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2445.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2444.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2455.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2448.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.406 [error] Postgrex.Protocol (#PID<0.2454.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2453.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2444.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2454.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2445.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2451.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2455.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.407 [error] Postgrex.Protocol #PID<0.2448.0> could not cancel backend: tcp connect: connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2453.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2444.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2454.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2445.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2451.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2455.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:37.408 [error] Postgrex.Protocol (#PID<0.2448.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate-1  | 2024-06-18 07:59:38.407 [error] Postgrex.Protocol (#PID<0.2450.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:38.408 [error] Postgrex.Protocol (#PID<0.2452.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:38.408 [error] Postgrex.Protocol (#PID<0.2449.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 07:59:42.520 [info] GET /
teslamate-1  | 2024-06-18 07:59:42.531 [info] Sent 200 in 10ms
teslamate-1  | 2024-06-18 07:59:53.386 [info] GET /settings
teslamate-1  | 2024-06-18 07:59:53.398 [info] Sent 200 in 12ms
teslamate-1  | 2024-06-18 08:00:01.116 [info] GET /
teslamate-1  | 2024-06-18 08:00:01.122 [info] Sent 200 in 5ms
teslamate-1  | 2024-06-18 08:01:02.530 [info] GET /settings
teslamate-1  | 2024-06-18 08:01:02.545 [info] Sent 200 in 14ms
teslamate-1  | 2024-06-18 08:02:07.734 [info] GET /
teslamate-1  | 2024-06-18 08:02:07.743 [info] Sent 200 in 8ms
teslamate-1  | 2024-06-18 08:04:00.202 [info] GET /settings
teslamate-1  | 2024-06-18 08:04:00.222 [info] Sent 200 in 19ms
teslamate-1  | 2024-06-18 08:04:11.042 car_id=1 [info] Connecting ...
teslamate-1  | 2024-06-18 08:04:26.710 car_id=1 [info] Disconnecting ...
teslamate-1  | 2024-06-18 08:06:27.690 [info] GET /
teslamate-1  | 2024-06-18 08:06:27.700 [info] Sent 200 in 9ms
teslamate-1  | 2024-06-18 08:06:59.811 [info] GET /geo-fences
teslamate-1  | 2024-06-18 08:06:59.823 [info] Sent 200 in 12ms
teslamate-1  | 2024-06-18 08:07:26.068 [notice] SIGTERM received - shutting down
teslamate-1  |
teslamate-1  | 2024-06-18 08:07:26.069 [info] Shutting down 1 sockets in 1 rounds of 2000ms
teslamate-1  | 2024-06-18 08:07:26.408 [error] Postgrex.Protocol (#PID<0.2451.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:26.408 [error] Postgrex.Protocol (#PID<0.2453.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:26.408 [error] Postgrex.Protocol (#PID<0.2448.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:26.408 [error] Postgrex.Protocol (#PID<0.2452.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:27.408 [error] Postgrex.Protocol (#PID<0.2455.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:27.409 [error] Postgrex.Protocol (#PID<0.2454.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:27.409 [error] Postgrex.Protocol (#PID<0.2450.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:27.409 [error] Postgrex.Protocol (#PID<0.2449.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:27.409 [error] Postgrex.Protocol (#PID<0.2444.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:07:27.409 [error] Postgrex.Protocol (#PID<0.2445.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | waiting for postgres at database:5432
teslamate-1  | 2024-06-18 08:08:02.624 [info] Migrations already up
teslamate-1  | 2024-06-18 08:08:09.442 [info] System Info: Erlang/OTP 26 (jit)
teslamate-1  | 2024-06-18 08:08:09.442 [info] Version: 1.29.1
teslamate-1  | 2024-06-18 08:08:09.770 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (279.197 ms)
teslamate-1  | 2024-06-18 08:08:09.770 [info] Refreshed api tokens
teslamate-1  | 2024-06-18 08:08:09.778 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-18 08:08:09.794 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
teslamate-1  | 2024-06-18 08:08:09.797 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate-1  | 2024-06-18 08:08:10.181 [info] Starting logger for 'TessY'
teslamate-1  | 2024-06-18 08:08:10.213 [info] MQTT connection has been established
teslamate-1  | 2024-06-18 08:08:10.276 [info] GET /settings
teslamate-1  | 2024-06-18 08:08:10.295 [info] Sent 200 in 18ms
teslamate-1  | 2024-06-18 08:08:10.465 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-18 08:08:13.717 [info] GET /settings
teslamate-1  | 2024-06-18 08:08:13.729 [info] Sent 200 in 12ms
teslamate-1  | 2024-06-18 08:09:49.403 [info] GET /
teslamate-1  | 2024-06-18 08:09:49.411 [info] Sent 200 in 8ms
teslamate-1  | 2024-06-18 08:09:51.850 [info] GET /
teslamate-1  | 2024-06-18 08:09:51.857 [info] Sent 200 in 6ms
teslamate-1  | 2024-06-18 08:09:52.376 [info] GET /
teslamate-1  | 2024-06-18 08:09:52.383 [info] Sent 200 in 6ms
teslamate-1  | 2024-06-18 08:09:52.621 [info] GET /
teslamate-1  | 2024-06-18 08:09:52.629 [info] Sent 200 in 8ms
teslamate-1  | 2024-06-18 08:09:52.812 [info] GET /
teslamate-1  | 2024-06-18 08:09:52.818 [info] Sent 200 in 5ms
teslamate-1  | 2024-06-18 08:11:41.888 [info] GET /
teslamate-1  | 2024-06-18 08:11:41.894 [info] Sent 200 in 5ms
teslamate-1  | 2024-06-18 08:11:46.550 [info] GET /geo-fences
teslamate-1  | 2024-06-18 08:11:46.560 [info] Sent 200 in 10ms
teslamate-1  | 2024-06-18 08:12:24.836 [info] GET /
teslamate-1  | 2024-06-18 08:12:24.842 [info] Sent 200 in 6ms
teslamate-1  | 2024-06-18 08:20:07.304 [warning] MQTT connection has been dropped
teslamate-1  | 2024-06-18 08:20:07.305 [info] [Tortoise311] Connection went down. Reconnecting.
teslamate-1  | 2024-06-18 08:20:07.314 [warning] [Tortoise311] Connection failed: {:connection_refused, ~c"mosquitto", 1883}, %{port: 1883, status: :down, protocol: "MQTT", host: ~c"mosquitto", protocol_version: 4, keep_alive: 60, transport: Tortoise311.Transport.Tcp, subscriptions: %Tortoise311.Package.Subscribe{__META__: %Tortoise311.Package.Meta{opcode: 8, flags: 2}, identifier: nil, topics: []}, client_id: "TESLAMATE_302E3931373", clean_session: false}. Retrying in 100 msecs.
teslamate-1  | 2024-06-18 08:20:07.438 [warning] [Tortoise311] Connection failed: {:nxdomain, ~c"mosquitto", 1883}, %{port: 1883, status: :down, protocol: "MQTT", host: ~c"mosquitto", protocol_version: 4, keep_alive: 60, transport: Tortoise311.Transport.Tcp, subscriptions: %Tortoise311.Package.Subscribe{__META__: %Tortoise311.Package.Meta{opcode: 8, flags: 2}, identifier: nil, topics: []}, client_id: "TESLAMATE_302E3931373", clean_session: false}. Retrying in 200 msecs.
teslamate-1  | 2024-06-18 08:20:07.468 [error] Postgrex.Protocol (#PID<0.2444.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:20:07.468 [error] Postgrex.Protocol (#PID<0.2445.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:20:07.468 [error] Postgrex.Protocol (#PID<0.2452.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:20:07.468 [error] Postgrex.Protocol (#PID<0.2449.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate-1  | 2024-06-18 08:20:08.189 [notice] SIGTERM received - shutting down
teslamate-1  |
teslamate-1  | 2024-06-18 08:20:08.190 [info] Shutting down 4 sockets in 1 rounds of 2000ms
teslamate-1  | 2024-06-18 08:20:10.604 [info] Migrations already up
teslamate-1  | 2024-06-18 08:20:13.356 [info] System Info: Erlang/OTP 26 (jit)
teslamate-1  | 2024-06-18 08:20:13.356 [info] Version: 1.29.1
teslamate-1  | 2024-06-18 08:20:13.676 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (280.451 ms)
teslamate-1  | 2024-06-18 08:20:13.676 [info] Refreshed api tokens
teslamate-1  | 2024-06-18 08:20:13.684 [info] Scheduling token refresh in 6 h
teslamate-1  | 2024-06-18 08:20:13.700 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
teslamate-1  | 2024-06-18 08:20:13.703 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate-1  | 2024-06-18 08:20:14.152 [info] GET /
teslamate-1  | 2024-06-18 08:20:14.172 [info] Starting logger for 'TessY'
teslamate-1  | 2024-06-18 08:20:14.181 [info] MQTT connection has been established
teslamate-1  | 2024-06-18 08:20:14.183 [info] Sent 200 in 31ms
teslamate-1  | 2024-06-18 08:20:14.198 [info] GET /
teslamate-1  | 2024-06-18 08:20:14.204 [info] Sent 200 in 6ms
teslamate-1  | 2024-06-18 08:20:14.328 [info] GET /
teslamate-1  | 2024-06-18 08:20:14.332 [info] Sent 200 in 4ms
teslamate-1  | 2024-06-18 08:20:14.391 car_id=1 [info] Start / :online
teslamate-1  | 2024-06-18 08:20:16.460 [info] GET /
teslamate-1  | 2024-06-18 08:20:16.465 [info] Sent 200 in 4ms

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.29.1

I figured out that when i do some trial and error that sometimes it works for a few seconds after the container starts and stops working again.

Well, oke. I was trying to look at the dashboards from a remote location over VPN(WireGuard). This always worked. All other services/containers are working over the VPN connection. When I came home I saw everything is working as expected. Is it possible that something within grafana/teslamate is blocking access over VPN?

teslamate-1  | 2024-06-18 08:20:07.468 [error] Postgrex.Protocol (#PID<0.2449.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command

Looks like that is your issue. I would investigate there.

Well, oke. I was trying to look at the dashboards from a remote location over VPN(WireGuard). This always worked. All other services/containers are working over the VPN connection. When I came home I saw everything is working as expected. Is it possible that something within grafana/teslamate is blocking access over VPN?

Did you find a solution for this? I have run into the same issue but am not returning to the base site for a few weeks so unable to test if grafana would work from within the network instead of over VPN. Until the last few weeks, VPN —> Grafana was working without any issue so this is a new problem.

Well, oke. I was trying to look at the dashboards from a remote location over VPN(WireGuard). This always worked. All other services/containers are working over the VPN connection. When I came home I saw everything is working as expected. Is it possible that something within grafana/teslamate is blocking access over VPN?

Did you find a solution for this? I have run into the same issue but am not returning to the base site for a few weeks so unable to test if grafana would work from within the network instead of over VPN. Until the last few weeks, VPN —> Grafana was working without any issue so this is a new problem.

No, but i did not spent a lot of time in it since it is working from within the same network. I'm quite sure this is not me doing something wrong. I use the default settings with docker compose and it stopped working after my last update of teslamate. I hope the developer can do something about it.

This is either a proxy or adblocker issue with newer grafana, not a teslamate issue

Hi Jakob, thanks for your suggestion. I’m not sure how it could be an ad blocker or proxy problem. I’ve got ad blockers turned off and the only proxy-like thing going on is the VPN into the network. The thing is, this worked previously and the only thing that’s changed recently is an update to Teslamate. Unfortunately, I won’t be at that site for a couple more weeks to try deploying the previous version to see if that fixes this issue.

I would love to test a previous version. But I’m not aware of my previous version. I update as soon as I see one available. And I do not know how to revert to a previous version.

off and the only proxy-like thing going on is the VPN into the network. The thing is, this worked previously and the only thing that’s changed recently is an update to Teslamate.

As wrote before, Grafana base image is updated which is more sensitive to ad blockers, proxy VPN.
That being said: tunneling in my network as well without any issues with v1.29.2. only needed to disable ad blocker on browser side

g said: tunneling in my network as well witho

I tested with disabling my ad blocker but it didn't fix the issue for me. Do you have any more guidance to fix this?
My setup is basicaly:
ISP --> Unifi Dream Machine --> LAN --> Docker Server --> Teslamate
The Dream Machine is my VPN server.

My setup is basicaly:
ISP --> Unifi Dream Machine --> LAN --> Docker Server --> Teslamate

I have similar with a UDM-Pro instead. The UDM-Pro is my VPN link into the network. The Docker runs on a Synology NAS. I don’t know enough about the technicalities to know why the new image may be more sensitive or what to do about it. Any guidance would be appreciated though. Thank you.


lähdeviitteiden avainten muokkaus toteutettu

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 14.28571% with 24 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/commands/add_reference.py
11.53%
23 Missing :warning:

src/bibtex_manager.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/bibtex_manager.py
36.36% <50.00%> (+0.87%)
:arrow_up:

src/commands/add_reference.py
47.36% <11.53%> (-18.67%)
:arrow_down:


feat: sozo scaffold

Proposal to add a sozo scaffold command which would:

create Scarb.toml with basic params
create sample components and systems
present the next steps in the terminal (links etc)

Simple addition, but would kickstart developers in a matter of minutes.

we have this with sozo init right now


Change the ControlCore layer to own a copy of its settings

Summary of the Pull Request
Currently, the TermControl and ControlCore recieve a settings object that implements IControlSettings. They use for this for both reading the settings they should use, and also storing some runtime overrides to those settings (namely, Opacity). The object they recieve currently is a T.S.M.TerminalSettings object, as well as another TerminalSettings object if the user wants to have an unfocusedAppearance. All these are all hosted in the same process, so everything is fine and dandy.
With the upcoming move to having the Terminal split into multiple processes, this will no longer work. If the ControlCore in the Content Process is given a pointer to a TerminalSettings in a certain Window Process, and that control is subsequently moved to another window, then there's no guarantee that the original TerminalSettings object continues to exist. In this scenario, when window 1 is closed, now the Core is unable to read any settings, because the process that owned that object no longer exists.
The solution to this issue is to have the ControlCore's own their own copy of the settings they were created with. that way, they can be confident those settings will always exist.  I used x-macros for this, so that we don't need to copy-paste into this file every time we add a setting.
Changing this has all sorts of other fallout effects:

Previewing a scheme/anything is a tad bit more annoying. Before, we could just sneak the previewed scheme into a TerminalSettings that lived between the settings we created the control with, and the settings they were actually using, and it would just work. Even explaining that here, it sounds like magic, because it was. However, now, the TermControl can't use a layered TerminalSettings for the settings anymore. Now we need to actually read out the current color table, and set the whole scheme when we change it. So now there's also a Microsoft.Terminal.Core.Scheme struct for holding that data.

Why a struct? Because that will go across the process boundary as a blob, rather than as a pointer to an object in the other process. That way we can transit the whole struct from window to core safely.

A TermControl doesn't have a IControlSettings at all anymore - it initalizes itself via the settings in the Core. This will be useful for tear-out, when we need to have the TermControl initialize itself from just a ControlCore, without being able to rebuild the settings from scratch.
The TabTests that were written under the assumption that the Control had a layered TerminalSettings obviously broke, as they were designed to. They've been modified to reflect the new reality.
When we initialize the Control, we give it the settings and the UnfocusedAppearance all at once. If we don't give it an unfocusedAppearance, it will just use the focused appearance as the unfocused appearance.
The Control no longer can write settings to the ControlSettings. We don't want to be storing things in there. Pretty much everything we set in the control, we store somewhere other than in the settings object itself. However, opacity and useAcrylic, we need to store in a handy new RUNTIME_SETTING property. We can write those runtime overrides to those properties.
We no longer store the color scheme for a pane in the persisted state. I'm tracking that in #9800. I don't think it's too hard to add back, but I wanted this in front of eyes sooner than later.

References

#1256
#5000
#9794 has the scheme previewing in it.
#9818 is WAY more possible now.

PR Checklist

[x] Surprisingly there wasn't ever a card or issue for this one. This was only ever a bullet point in #5000.
A bunch of these issues were fixed along the way, though I never intended to fix them:

[x] Closes #11571
[x] Closes #11586
[x] Closes #7219
[x] Closes #11067
[x] I think #11623 actually ended up resolving this one, but I'm double tapping on it here: Closes #5703

[x] I work here
[x] Tests added/passed
[n/a] Requires documentation to be updated

Detailed Description of the Pull Request / Additional comments
Along the way I tried to clean up code where possible, but not too agressively.
I didn't end up converting the various MockTerminalSettings classes used in tests to the x macros quite yet. I wanted to merge this with #11416 in main before I went too crazy.
Validation Steps Performed

[x] Scheme previewing works
[x] Adjusting the font size works
[x] focused/unfocused appearances still work
[x] mouse-wheeling opacity still works
[x] acrylic & cleartype still does the right thing
[x] saving the settings still works
[x] going wild on sliding the opacity slider in the settings doesn't crash the terminal
[x] toggling retro effects with a keybinding still works
[x] toggling retro effects with the command palette works
[x] The matrix of (useAcrylic(true,false))x(opacity(50,100))x(antialiasingMode(cleartype, grayscale)) works as expected. Slightly changed, falls back to grayscale more often, but looks more right.

cleartype/grayscale, acrylic/vintage, 50%/100% opacity:

We've been selfhosting this and I haven't run into any issues, so... gonna give it another look :P

@msftbot merge this in 8 hours


Equivalent of async.series / async.each?

Let's say I have an array (not an array of promises) which I want to perform async operations on. What is the right method to use?
e.g.:
var hosts = [ 'google.com', 'yahoo.com' ];

BPromise.IS_THERE_A_METHOD_FOR_THIS(hosts, function () {
   return ping(host);
}).then(....)

If you're okay with firing all requests at once, then try the following approach:
var hostPromises = hosts.map(ping); // create an array of promises by mapping ping function for each host
BPromise.all(hostPromises).then(function(responses) {
    responses.forEach(function(response) {
        // do something with each response.
    });
});

this is what .map is for, it accepts normal values as well as arrays of promises

Please ask support questions on StackOverflow or IRC.


How to replicate the performance of transformer

srun --pty --gres gpu:8 -c 16 fairseq-train     data-bin/wmt16_en_de_bpe32k     --arch transformer --share-all-embeddings     --optimizer adam --adam-betas '(0.9, 0.98)' --clip-norm 0.0     --lr 0.0006 --lr-scheduler inverse_sqrt --warmup-updates 4000 --warmup-init-lr 1e-07     --dropout 0.1 --weight-decay 0.0     --criterion label_smoothed_cross_entropy --label-smoothing 0.1     --max-tokens 5500 --fp16
I want to replicate the base transformer performance on WMT EN-DE
However, I can only get 26.65 BLUE score.
Can you give me any suggestion?

The original Attention Is All You Need paper reported 27.3 BLEU, but that included several tricks:

checkpoint averaging: you should try averaging the last few checkpoints using the average_checkpoints script: https://github.com/pytorch/fairseq/blob/master/scripts/average_checkpoints.py
during generation make sure you're using --beam 4 --lenpen 0.6 --remove-bpe
compound splitting: you will get slightly higher BLEU scores by using compound splitting. Save the output from generate.py and then use the compound_split_bleu.sh script: https://github.com/pytorch/fairseq/blob/master/scripts/compound_split_bleu.sh

closing this issue after myle's answer


Add ecologyPlaygroundLoading func to docs

Will load placeholder boxes on initial render and fix https://github.com/FormidableLabs/formidable-landers/issues/23

cc @paulathevalley

LGTM!


Improving server side error handling

In a case of an error on the server side, the next middleware in chain is called without logging the error. In some cases the rendering logic silently fails and it's hard to debug rendering issues. An example would be rendering a template from an existing error middleware.
Suggested improvement: Adding a debug statement in the catch block.

@slatkovic are you suggesting to add something like debuglog? A PR would be awesome. if not will address this as soon as we get done with making react-engine compatible with react-router 1.x


Publish this as an NPM package

It would be nice to have fixtable published to NPM (in addition to Bower). Then, we wouldn't have to deal with mixing NPM and Bower dependencies when using this via the fixtable-ember Ember addon, which has a Bower dependency on this project.
I could submit a PR for this at some point.

👍 x 10,000 - bumping this!

Done!
https://www.npmjs.com/package/fixtable


Code and documentation cleanup

Update documentation to address #529
Clean up deprecation warnings in S3 code
Move @RequestMapping(method = RequestMethod.{METHOD}... to convenience annotations like @GetMapping, @PostMapping etc for clarity
Enable unchecked and deprecation warnings into the compiler arguments so we catch them

Coverage decreased (-0.06%) to 88.454% when pulling e226a7e1cdabc7ed5e517efff2e97d5dd5a1eef7 on tgianos:cleanup into 3241b8735d8a35a2a930fd5209aa1c1dd773fa42 on Netflix:master.

Coverage decreased (-0.06%) to 88.454% when pulling 6510766f8becbf6b1747c2a498d95d85f3417ede on tgianos:cleanup into 3241b8735d8a35a2a930fd5209aa1c1dd773fa42 on Netflix:master.


returned predicted algorithm

I want to use the AutoFolio prediction mode within a python script, so without making use of the cli. I can import the AutoFolio class and run "read_model_and_predict", but this forces me to redirect the stdout and parse it to obtain the predicted algorithm.
This modification returns the predicted algorithm and moves the print statement to the "run_cli" function.

Thanks for providing the PR.
Could you also please update the docstring of read_model_and_predict(), reflecting the returned type.
Afterwards, I will merge the PR.

I also changed the return type from 'list of tuple' to 'tuple' by selecting the first entry. So far I can see, that will not cause a problem.

Thanks for the changes.
Please note that AutoFolio can predict a schedule of algorithms (i.e., first run algorithm A for X seconds, then run algorithm B for Y seconds and so on). If you use a static presolving schedule, A and X will in fact the same for all instances and that's not what you actually want. Therefore, you have to return and potentially consider the entire list of selected algorithms.

Great. Thank you


Add path and args to exec cmd

What type of PR is this?

/kind feature

What this PR does / why we need it:
This PR adds Path and Args to the exec command proxy. I need access to the os.Command.Args for another PR and cannot type cast/assert.
Which issue(s) this PR fixes:
Ref: https://github.com/kubernetes/kubernetes/pull/108199
Special notes for your reviewer:
Release note:
NONE

/assign @lavalamp
I am not sure what to do about the apidiff failing. Does this need a release note for people when they upgrade to this so they can update their mocks?

Because we need changes to this repo to be compatible with a wide variety of Kubernetes versions, we don't allow breaking go API changes, and apidiff helps avoid merging accidental breaks. Adding methods to the interface would mean someone bumping to this version who had their own impl would no longer compile correctly.
You can create a second interface that in lines the first and adds these two new methods.

Going to switch to using plain old os/exec.


Fix code style issues.

Every time make pretty, these issues are made. This PR just submit what make pretty result in so that one don't have to remove these changes after make pretty.

Codecov Report

Merging #1622 into master will decrease coverage by 20.87%.
The diff coverage is 50%.

@@             Coverage Diff             @@
##           master    #1622       +/-   ##
===========================================
- Coverage   71.16%   50.28%   -20.88%
===========================================
  Files         155      150        -5
  Lines       18495    16063     -2432
  Branches     2264     2004      -260
===========================================
- Hits        13162     8078     -5084
- Misses       4511     7360     +2849
+ Partials      822      625      -197

Impacted Files
Coverage Δ

src/core/crypto/pbkdf2_cmac.cpp
0% <ø> (ø)
:arrow_up:

src/core/meshcop/dtls.cpp
9.79% <0%> (-78.42%)
:arrow_down:

src/core/api/instance_api.cpp
40.81% <100%> (ø)
:arrow_up:

src/core/thread/lowpan.hpp
0% <0%> (-100%)
:arrow_down:

src/core/net/dhcp6_server.hpp
0% <0%> (-100%)
:arrow_down:

src/core/net/dhcp6.hpp
0% <0%> (-100%)
:arrow_down:

src/core/meshcop/leader_ftd.hpp
0% <0%> (-100%)
:arrow_down:

src/core/meshcop/meshcop.hpp
0% <0%> (-100%)
:arrow_down:

src/core/crypto/sha256.cpp
0% <0%> (-100%)
:arrow_down:

src/core/thread/src_match_controller.hpp
0% <0%> (-100%)
:arrow_down:

... and 111 more

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 fc931e9...a186663. Read the comment docs.


Support setting Nessus web server port

🗣 Description
This PR adds a new optional Terraform variable nessus_web_server_port, which when set will modify the web server port used by any Nessus instances that are deployed.  The port defaults to 8834, which is the default port used by Nessus.

💭 Motivation and context
If the Nessus port is set to 443, it will make life simpler for assessors who connect to the Nessus web server using a browser.  This also gives us more flexibility in general if the port ever needs to be set to something specific.
Resolves #52.

🧪 Testing
I deployed a fresh Nessus instance using the code changes in this PR, set nessus_web_server_port to 443, and verified that the script ran as expected and that the port was indeed modified.
Log snippet (/var/log/cloud-init-output.log):
Setting Nessus web server port to 443...
Successfully set 'xmlrpc_listen_port' to '443'.
The Nessus web server will be restarted.

Manual verification that port was correctly changed to 443:
$ sudo /opt/nessus/sbin/nessuscli fix --show xmlrpc_listen_port

--------------------------------------------------
  User Interface
--------------------------------------------------
  * Nessus Web Server Port (xmlrpc_listen_port)
    - Current value: 443
    - Description: Port for the Nessus web server to listen on.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] All new and existing tests pass.

✅ Post-merge checklist

[ ] Coordinate with Operations and Assessment teams to make them aware of this new feature.

Please update
https://github.com/cisagov/cool-assessment-terraform/blob/78996187fde58028b5debae30a207f3c683b230d/versions.tf#L3
to reflect the version requirement mentioned in #222 (comment) to ensure an expected experience.

Excellent catch!  Remedied in https://github.com/cisagov/cool-assessment-terraform/pull/222/commits/94c796e31ad3d3135e2d3481c761751ca83bfb8b.


Check entity version return body

Some changes have impacted the fields returned by the GET entity version.
We are seeing some errors in the python integration tests for the Ometa wrapper:
Error
Traceback (most recent call last):
  File "/Users/p.brull/projects/OpenMetadata/ingestion/tests/integration/ometa/test_ometa_chart_api.py", line 225, in test_get_entity_version
    res = self.metadata.get_entity_version(
  File "/Users/p.brull/projects/OpenMetadata/ingestion/src/metadata/ingestion/ometa/mixins/version_mixin.py", line 76, in get_entity_version
    return self._get(entity=entity, path=path, fields=fields)
  File "/Users/p.brull/projects/OpenMetadata/ingestion/src/metadata/ingestion/ometa/ometa_api.py", line 380, in _get
    return entity(**resp)
  File "pydantic/main.py", line 331, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for Chart
service
  field required (type=value_error.missing)

It is failing when trying to convert the response body to the specific Entity.
Let's take a look and see if it makes sense to keep returning the service or if we should update the OpenMetadata API wrapper expected behavior.

Hi @harshach, I was trying to figure out the source from this and it might come from not properly recovering deleted entities in the backend.
The issue we are having is that during the integration tests, we are stressing all operations on the entities with a series of PUT, GET, DELETE, etc. We also test the versions endpoint trying to obtain the version 0.1.
It looks like the combination of DELETE + PUT + GET/versions/0.1 does not properly return all the information, as the service is missing from the response body. It is a bit weird as the usual GET returns the whole info and it is just the versions endpoint the one that is having this issue.
You can replicate the issue with
from metadata.generated.schema.api.data.createDashboard import (
    CreateDashboardEntityRequest,
)
from metadata.generated.schema.api.services.createDashboardService import (
    CreateDashboardServiceEntityRequest,
)
from metadata.generated.schema.api.teams.createUser import CreateUserEntityRequest
from metadata.generated.schema.entity.data.dashboard import Dashboard
from metadata.generated.schema.entity.services.dashboardService import (
    DashboardService,
    DashboardServiceType,
)
from metadata.generated.schema.type.entityReference import EntityReference
from metadata.ingestion.ometa.ometa_api import OpenMetadata
from metadata.ingestion.ometa.openmetadata_rest import MetadataServerConfig

import requests

server_config = MetadataServerConfig(api_endpoint="http://localhost:8585/api")
metadata = OpenMetadata(server_config)

# Prepare and create service
service = CreateDashboardServiceEntityRequest(
    name="test-service-dashboard",
    serviceType=DashboardServiceType.Superset,
    dashboardUrl="https://localhost:1000",
)

service_entity = metadata.create_or_update(data=service)

# Prepare and create Dashboard
create = CreateDashboardEntityRequest(
    name="test",
    service=EntityReference(id=service_entity.id, type="dashboardService"),
)

entity = metadata.create_or_update(data=create)

# Delete
metadata.delete(entity=Dashboard, entity_id=entity.id)

# Recreate
metadata.create_or_update(data=create)

requests.get(f"http://localhost:8585/api/v1/dashboards/{str(entity.id.__root__)}/versions/0.1").json()

Looks like at DELETE we insert the entity JSON in entity_extension already without the service information

@pmbrull when the entity is deleted we are setting all the relations to be deleted.
so in our calls after the delete if we want to get the full picture of the entity that is deleted we should pass "include=deleted" as the query param.
cc @amiorin

@pmbrull ping me in Slack if you need help with the debugging.

Thank you both! ended up being a one-liner, you just needed to know where to add it 😅


[ML] Create Heart Disease Prediction Model

Create a new python notebook containing detailed study and analysis of different models for prediction of heart disease risks.
Use Kaggle / google colab for working on the notebook.
Use the dataset from https://www.kaggle.com/dileep070/heart-disease-prediction-using-logistic-regression.
Before working on your notebook, please look at the existing notebook for diabetes prediction.

Suggestions of all kinds are always welcomed.

Please assign me this issue as a part of LGM-SOC'21

@Ashuto7h Please check my pull request

@Ashuto7h Please check my pull request


Update DockerHub references to MCR.

Starting July 1st, 2021 repositories from microsoft/ org on Docker Hub will be removed. At this point development, deployment and automation scripts that still reference microsoft/ org images from Docker Hub registry will fail. More information here: https://techcommunity.microsoft.com/t5/azure-developer-community-blog/deprecating-the-distribution-of-microsoft-container-images-via/ba-p/2366861
To avoid failures, I've updated the microsoft/ references to MCR. If you feel they are incorrect, please use the "Docker to MCR mapping" link below or contact us at<EMAIL_ADDRESS>for help.
References:
Contributor's guide: https://review.docs.microsoft.com/en-us/help/contribute/contribute-how-to-reference-public-container-images?branch=master
Docker to MCR mapping: https://github.com/microsoft/containerregistry/blob/master/docs/dockerhub-to-mcr-repo-mapping.md

@msangapu-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@msangapu-msft - can you address the merge conflict?  after that @shashban  can take a look at the changes. Thanks.

@msangapu-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@shashban - please review this PR.

#sign-off

@steved0x: I'm sorry - only the author of this article, @shashban, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


SuperSafe for Scala 2.12.8

Hi, would it be possible to make a release of SuperSafe for Scala 2.12.8?

@mwz I'll be working on it today.


Web Server Down - Cannot End Recording

Hello!
This agent baseline experiment is supposed to take screenshots and save them in a folder called 'results'. However, the agent is unable to end the recording because it is unable to access the url that OSWorld is supposed to have made. The URL that is supposed to be is based on my VMWare's IP address.
Although I am able to find a folder called 'screenshots' in 'results', the json files inside display the following message  {"Error": "Time limit exceeded in chrome/06fe7178-4491-4589-810f-2e2bc9502122"} and the program was unable to end the recording so nothing was saved.
I will attach a screenshot of the result I received.
I believe when I run the Agent Baseline Experiment command, a server should have started and I should be able to open up the URL in VMWare through Ubuntu's Firefox. I already tried finding the URL using my VMWare's IP address and various ports such as 5000, 8080, and 9222. All of these servers are down.
Is there a place in the source code where I can take a look at how the server is started? - thus far, I have not been able to find where the server is started in the source code.

UPDATE
I think this is the root of the error that causes the "failed to stop recording" error message. Is there a way to fix this?

Dear Tongxiang,
Thanks for the question. The code of the server is being run inside the virtual machine file (and not in the host machine) we provided and you auto-downloaded. For your reference, the source code is at https://github.com/xlang-ai/OSWorld/blob/main/desktop_env/server/main.py .
For the URL connection problem you mentioned, I didn't see that situation before, it seems the example didn't start successfully and caused the corruption. And I need more information for debugging.
Best,
Tianbao

Thank you for your response!
I have resolved the URL connection problem and when I go to the URL I am able to see screenshots that the agent has taken. However, there is an issue with sending the screenshots to the actual 'results' folder - I continue to see json files with {"Error": "Time limit exceeded in chrome/06fe7178-4491-4589-810f-2e2bc9502122"}.
The other issue I had was the error message that said "Failed to stop recording" and then "Retrying to stop recording".
I'm not sure how to fix this issue.
In the screenshot below, you can see the Exception error message that says: "Cannot pickle ThreadLocalFileContext" object.
Is there a solution to this?

Thanks for the question again!
May I ask about the version of Python you are using (if it is > 3.9), the error message you are showing seems to be caused by the version.
Thanks

Hello!
I do not believe the Python version is the source of the issue. I am using 3.11.0.
Instead, I believe the part of the error message that says: "Cannot pickle ThreadLocalFileContext" object is more likely to be the cause.

Yes, I also encounter this problem, have you solved it and do you have any recommendation for tickling it?

And here is the error output, it seems something wrong with the multiprocessing and pickle package?

Hi, we have fixed this issue, please pull the latest code to see if it works.


As a user, I should be able to pick from at least two challenges that cover unique and interesting topics.

This is a continually moving user story! It will likely be in-progress the entirety of this first semester.
Acceptance Criteria

[ ] User can pick from at least two different challenges designed by our team.
[ ] User can decide between an easier or more difficult topic, and the difficult one may depend on skills learned from the easy one.
...

Sub-Challenge 1:
Created a basic login webpage so far. Still working on adding additional levels to more closely represent a real world website (JS Files and CSS etc).
Next Steps are to finalize the page.

As of now we have 3 fully working challenges, however waiting on some adaptations so they can be added to our sys in order to be considered fully done.

Still waiting on ensuring out challenges spin up as desired.

The acceptance criteria was 2 challenges, We are past that I am closing this as complete.


Is there a wrong in the agent.py?

Thanks for your working!
Maybe I found a mistake in your code. Can you check this?
distance_map = (feature_map-point_feature)**2
distance_map = torch.norm( distance_map, dim=1 ).view(real_batch_size, 1, self.p.grid_y*self.p.grid_x, self.p.grid_y*self.p.grid_x)
on line 203-204 in agent.py.
torch.norm() already compute the L2 norm of distance_map, there is no need to square  the  (feature_map-point_feature).

Thank you! This is my mistake. In new version, the problem is fixed.


chore: Pin and upgrade all immutable-eligible actions to their semantic versions

Hello from Product Security! 👋
We noticed that at least one of your Actions workflows is using one or more eligible immutable actions without semantic versioning. This PR will update the workflow to use the latest version of the action, using semantic versioning to opt into immutable actions.
Why is this important?
Using an immutable action without indicating proper semantic version will result in the version being resolved to a tag that is mutable. This means the action code can between runs and without your knowledge.
Using an immutable action with proper semantic versioning will resolve to the exact version of the action stored in the GitHub package registry. The action code will not change between runs. This is a key security control to ensure the code you are running is the code you expect.
More Information

Here's the announcement and some context on why this is important: https://github.com/github/c2c-actions/discussions/8601
More documentation on immutable actions: https://github.com/github/package-registry-team/blob/main/docs/immutable-actions/immutable-actions-howto.md

If you have any questions or concerns, please don't hesitate to tag @github/prodsec-engineering or reach out in #prodsec-securing-actions. We're here to help!
Thanks and happy coding! 🎉

@mrecachinas thank you for this PR.  Very happy to learn about immutable actions via tags.  Definitely more human readable.  Cheers 🙇


Streaming responses from scaled-to-zero Inference Endpoints return undefined

Hey folks, what's the recommended way to deal with the initializing period of a scaled-to-zero Inference Endpoint when using .textGenerationStream()?
For example, when using .textGeneration() directly, we get the 503 error directly that we can catch and maybe retry on.
However, when using .textGenerationStream(), fetching the next response chunk appears to succeed, except the .value at that chunk happens to be undefined. Reproducing code:
import { HfInferenceEndpoint } from "@huggingface/inference";
import { experimental_buildLlama2Prompt } from "ai/prompts";

const hf = new HfInferenceEndpoint(
  "DEPLOYED_LLAMA2_ENDPOINT",
  "API_TOKEN",
);

const response = hf.textGenerationStream({
  inputs: experimental_buildLlama2Prompt([
    {
      role: "user",
      content: "hello",
    },
  ]),
});

response.next().then((res) => {
  console.log("print next chunk");
  console.log(res.value);
  console.log("done");
});

Running via terminal results in the following:
> npx ts-node hf-test.ts
print next chunk
undefined
done

My (possibly naive) expectation would be for the generator returned by textGenerationStream() to wait for the corresponding Inference Endpoint to fully initialize -- maybe with exponential backoff -- before allow the chunk to be returned via .next(). But I am a novice here so I could be missing something. 😆
Is this expected behavior or a bug?

@co42 @Narsil , does HF endpoints support wait_for_model like Inference API?

It would be nice for API compatibiltity between inference API & inference endpoints!

@jinnovation you will now get a 503 in streaming requests with most recent version 2.6.5
With your current version, you can get a 503 if you set retry_on_error to false:
const response = hf.textGenerationStream({
  inputs: experimental_buildLlama2Prompt([
    {
      role: "user",
      content: "hello",
    },
  ]),
  {
    retry_on_error: false
  }
});

Soon the inference endpoint API will be updated, so that a call by default with @huggingface/inference will wait until the model is loaded (you can disable this behavior with retry_on_error: false to handle the 503 yourself)

Soon the inference endpoint backend will be updated, so that a call by default with @huggingface/inference will wait until the model is loaded

Fantastic! Thank you.


Integrity check published times

We want to integrity check publishing times when we import whitehall documents, the times we're concerned about checking are public_updated_at and first_published_at.
More info in the commits ->
Trello:
https://trello.com/c/aCQ4qhB3/1464-check-integrity-of-whitehall-firstpublishedat-and-publicupdatedat

Hey, just summarising our quick face-to-face review.

We want to be comparing Whitehalls details->first_public_at rather than first_published_at. Some past about the magic first_public_at value is available here: https://github.com/alphagov/government-frontend/pull/996
When the times don't match we want to be displaying the different values - which will likely mean using the problem description method
We're not sure if we yet need to add the precision checking in, we want to give this a test run with NDA first and see if they have any issues first to guide us.

Rebased to accommodate the json payload changes and now should be ready for another review @kevindew.

Thanks for the review @kevindew, have made the changes you've requested.


Is is possible to support both password and client_credentials flow in swagger-ui?

Is is possible to support both password and client_credentials flow in swagger-ui?
@Bean
public SecurityScheme oauth() {
    return new OAuthBuilder()
            .name(OAUTH2_SECURITY_SCHEMA)
            .grantTypes(grantTypes())
            .scopes(scopes())
            .build();
}

private List<GrantType> grantTypes() {
    GrantType passwordGrant = new ResourceOwnerPasswordCredentialsGrant(TOKEN_URL);
    GrantType clientCredentialsGrant = new ClientCredentialsGrant(TOKEN_URL);
    return Arrays.asList(passwordGrant, clientCredentialsGrant);
}

This doesn't seem to work, and my passwordGrant also gets broken. But if I remove clientCredentialsGrant then password flow works fine via the authorize button in the swagger ui.
What is the recommended way to support multiple flows when pressing the authorize button?

I think it might be a limitation with the current swagger-ui version supported by springfox


Loaded but does nothing

I'm using neovim 0.7.2 but I also tried the vim plugin with a bare vim configuration. The filetype isn't set and even if I set it manually there's no coloration or anything :/
I can confirm plugin is loaded by checking packer_plugins global

The filetype is not set by ntangle.nvim. That's normal. The filetype was set in the previous tangle.vim, to have a cheap hack to still have syntax coloring. But it now relies on an external plugin ntangle-ts.nvim. Installing it will enable syntax coloring.

Did you succeed in something?

i didnt try yet. i'll tell you as soon as i do

Ok

I tried with only your plugins and treesitter but nothing happens. I'm unsure if I'm doing something wrong.
Here the result:

And you can reproduce with the following script, passing as argument the init.lua below and somewhere to store runtime data and config dir.
# nvim-alt

if [[ ! -n "$(LC_ALL=C type -t realpath)" ]]
then
    realpath() (
        OURPWD=$PWD
        cd "$(dirname "$1")"
        LINK=$(readlink "$(basename "$1")")
        while [ "$LINK" ]; do
            cd "$(dirname "$LINK")"
            LINK=$(readlink "$(basename "$1")")
        done
        REALPATH="$PWD/$(basename "$1")"
        cd "$OURPWD"
        echo "$REALPATH"
    )
fi

if [[ $TERMUX_VERSION ]];
then
    TMPDIR="$TMUX_TMPDIR"
else
    TMPDIR="${TMPDIR:-/tmp}"
fi

if [[ ! -f "$(realpath $1)" ]]
then
    echo "Invalid argument"
    echo "syntax: $0 VIMRC [DIR]"
    echo "VIMRC is the configuration file to use"
    echo "DIR is where runtime and configuration will be stored."
    echo "if not specified a temporary one will be used."
fi

if [[ ! -n "$2" ]]
then
    NVIM_DIR="$(mktemp --directory nvim-test.XXXXXXXX)"
else
    if [[ ! -d "$(realpath $2)" ]]
    then
        mkdir "$2"
    fi
    NVIM_DIR="$2"
fi

ROOT="$(dirname "$(dirname "$(realpath "$0")")")"
export XDG_DATA_HOME="$NVIM_DIR/data"
export XDG_CONFIG_HOME="$NVIM_DIR/conf"
export MYVIMRC="$1"

echo data stored in $NVIM_DIR
nvim -u "$MYVIMRC"
#rm -rf "$TEST_TMP_DIR"

with the following configuration:
-- vim: et sw=4 ts=4:
local function clone_packer()
    local path = vim.fn.stdpath('data') .. '/site/pack/packer/start/packer.nvim'
    if vim.fn.empty(vim.fn.glob(path)) > 0 then
        vim.fn.system {
            'git',
            'clone',
            '--depth=1',
            'https://github.com/wbthomason/packer.nvim',
            path
        }
    end
end

local function bootstrap_packer(pkgs, opts)
    pkgs = pkgs or {}
    opts = opts or {}
    clone_packer()
    -- Load Packer
    vim.cmd('packadd packer.nvim')
    local packer = require('packer')
    packer.startup({ pkgs, opts })
    packer.sync()
end

local pkgs = {
    'wbthomason/packer.nvim',
    'jbyuki/ntangle.nvim',
    'jbyuki/ntangle-ts.nvim',
    {
        'nvim-treesitter/nvim-treesitter',
        run = function()
            require('nvim-treesitter.install').update({ with_sync = true })
        end,
    },
}

bootstrap_packer(pkgs)

I don't see the extension of the file on the top-left but is that a neorg file? To syntax color that, you need to install neorg.nvim probably. My plugins support *.t files such as *.lua.t file, that's a completely different way to program to neorg.

My confusion, I got here thinking it was a plugin for Literate (which anyway I was going to drop because of some bugs)


Mobile PLP: images not centered

Environment: mobile (here: iPhone 1 mini, iOS 16.3.1, Nokia 7.1, Android 10)
Reproduce:

Open random category landing page such as https://<IP_ADDRESS>:8443/posters/topCategory/Panoramas?categoryId=4

Issue: the product images are not centered on the page. Looks like they display a little closer to the left than the right, This way, the product name, description overview and price are also not centered below the image.
Similar to https://github.com/Xceptance/posters-demo-store/issues/201.

Issue fixed for poster v2.1.


virtiofsd: 1.10.1 -> 1.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/virtiofsd/versions.
meta.description for virtiofsd is: vhost-user virtio-fs device backend written in Rust
meta.homepage for virtiofsd is: https://gitlab.com/virtio-fs/virtiofsd
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.11.0 with grep in /nix/store/dk036kcp5dhdfgs8j3k6gzwljpwhi10i-virtiofsd-1.11.0
found 1.11.0 in filename of file in /nix/store/dk036kcp5dhdfgs8j3k6gzwljpwhi10i-virtiofsd-1.11.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

lxd-lts
virtiofsd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dk036kcp5dhdfgs8j3k6gzwljpwhi10i-virtiofsd-1.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A virtiofsd https://github.com/r-ryantm/nixpkgs/archive/a10d39c9e1ef6030e2109306c9f562b1cc9f6c6b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a10d39c9e1ef6030e2109306c9f562b1cc9f6c6b#virtiofsd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dk036kcp5dhdfgs8j3k6gzwljpwhi10i-virtiofsd-1.11.0
ls -la /nix/store/dk036kcp5dhdfgs8j3k6gzwljpwhi10i-virtiofsd-1.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

3 packages built:

lxd-lts
virtiofsd
virtiofsd.debug

Maintainer pings
cc @alyssais @astro for testing.

We now have Cloud Hypervisor 40 in Nixpkgs, which is compatible with this version of virtiofsd.  QEMU always was, and crosvm didn't work with virtiofsd before, so there's no need to wait for that.  @astro can you check any other VMMs you care about?


support functionLoad and functionDelete with GlideString

support functionLoad and functionDelete with GlideString

many function commands are not supported with GlideString yet so it is problematic to add integration test yet
I suggest to add it later after we add the GlideString version of the commands

Update all in one PR then, otherwise there is no warranty that currect code works.

Added integration tests for the GlideString versions of the functions


Feat: add f-string

Supported f-string and jinja2 template in python langchain. This PR aims to add f-string support to go langchain.
https://github.com/langchain-ai/langchain/blob/81886ad34598b2092ee9efd84e837c22c5faea58/libs/core/langchain_core/prompts/string.py#L86
Although f-string is a feature of python, within our company, our existing projects are based on python langchain, and a large number of f-string templates are stored in the database.
We need to support f-string in go. In order to migrate existing business from python to go.

Can you clarify what this is for? Is there an issue explaining the use cases and the problem(s) this PR is solving?

support by langchain python: https://github.com/langchain-ai/langchain/blob/81886ad34598b2092ee9efd84e837c22c5faea58/libs/core/langchain_core/prompts/string.py#L86

Can you clarify what this is for? Is there an issue explaining the use cases and the problem(s) this PR is solving?

support by langchain python: https://github.com/langchain-ai/langchain/blob/81886ad34598b2092ee9efd84e837c22c5faea58/libs/core/langchain_core/prompts/string.py#L86

f-string is a Python feature and is useful and natural in Python code. It's not something that exists in Go -- perhaps a text/template-based implementation would be more natural.

Can you clarify what this is for? Is there an issue explaining the use cases and the problem(s) this PR is solving?

support by langchain python: https://github.com/langchain-ai/langchain/blob/81886ad34598b2092ee9efd84e837c22c5faea58/libs/core/langchain_core/prompts/string.py#L86

f-string is a Python feature and is useful and natural in Python code. It's not something that exists in Go -- perhaps a text/template-based implementation would be more natural.

We already have a text/template based templating scheme and just recently added a jinja2-inspired approach. While I don't think we should have a large number of templating implementations I'm open to alternatives to some extent. Happy to have the discussion.

@tmc update the PR description, updated the purpose and background of this PR


Runes pagination

Issue: add a runes page #3213

@casey @raphjaph please review this idea

@casey sorry for disturbing :(

When mainnet is launched, I think runes will explode and there will be a large number of runes being etched. I believe creating pagination will be necessary. Please give me more input on developing this feature.

@raphjaph help me review again

remove NUMBER_TO_RUNE_INFO
move RUNE_NUMBER_TO_RUNE_INFO to RUNE_NUMBER_TO_RUNE_ENTRY
move RUNE_ID_TO_RUNE_ENTRY to RUNE_ID_TO_RUNE_NUMBER

@raphjaph  @casey  I really hope you can review and give me feedback.

There seem to be a lot of merge conflicts, which are probably our fault because the runes part of the codebase is changing a lot. Could you fix them?

ok. I will fix soon

There seem to be a lot of merge conflicts, which are probably our fault because the runes part of the codebase is changing a lot. Could you fix them?

@raphjaph merged master

@raphjaph hope you spend time to review this PR!

all tests is ok

RUNE_ID_TO_RUNE_NUMBER is, as far as I can tell, not needed. To get rune N, you can open RUNE_ID_TO_RUNE_ENTRY, and use .skip(N) to get to that rune, since rune IDs and rune numbers are in the same order.

@casey understood and fix code


Pass granularity from backend to frontend as ISO duration

Currently the backend will pass the granularity as a string that is engine dependent, e.g, "30 seconds". I changed the backend so that an ISO 8601 duration is passed instead. This allows the frontend to handle the granularity better, eg, for the play slider.

@betodealmeida @mistercrunch
I exported a postgres backed set of charts and dashboards to another postgres instance with this change included. It seems to work when viewing the actual chart, but when a time grain is persisted on a chart used in a dashboard I'm getting an error as such:
Traceback (most recent call last):
  File "/home/superset/superset/viz.py", line 362, in get_df_payload
    df = self.get_df(query_obj)
  File "/home/superset/superset/viz.py", line 160, in get_df
    self.results = self.datasource.query(query_obj)
  File "/home/superset/superset/connectors/sqla/models.py", line 705, in query
    sql = self.get_query_str(query_obj)
  File "/home/superset/superset/connectors/sqla/models.py", line 419, in get_query_str
    qry = self.get_sqla_query(**query_obj)
  File "/home/superset/superset/connectors/sqla/models.py", line 545, in get_sqla_query
    timestamp = dttm_col.get_timestamp_expression(time_grain)
  File "/home/superset/superset/connectors/sqla/models.py", line 134, in get_timestamp_expression
    expr = grain.function.format(col=expr)
AttributeError: 'str' object has no attribute 'function'

I was able to backfill values stored on slices.params.time_grain_sqla, to the ISO durations from here and this resolved the issue.  Did I miss a migration someplace or should one be added for this?

@NathanQuinn i think the ".function" part should be removed

@betodealmeida should there be a DB migration associated with this PR to update slices which reference the deprecated time grains?
cc: @michellethomas


Suggestion: "Format as single line" to convert multi-line statement back to a single line

I'd like the inverse of the "Format as multi-line" command. See also: https://github.com/aheze/Multiliner/issues/8
Use case: I've split an init or function declaration into multiple lines because it exceeds my team's preferred line length. But now I've removed a parameter or two and so I'd like to quickly be able to switch it back to a more-compact single line statement.

Sounds great - thanks for the suggestion! I can get a basic version out today that will reformat the existing line into a single one and then can spend some time this weekend playing around with how to do that reliably across the entire file 👍

Implemented and submitted to App Store! This will be available in v1.4 🚀

Wow, thanks! 🚀
On Thu, Apr 6, 2023 at 12:14 PM Aryaman Sharda @.***>
wrote:

Implemented and submitted to App Store! This will be available in v1.4 🚀
—
Reply to this email directly, view it on GitHub
https://github.com/aryamansharda/EditKitPro/issues/1#issuecomment-1499504876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFYB73GSFUHHSEA7SJOVVLW74IYPANCNFSM6AAAAAAWVSY66Y
.
You are receiving this because you authored the thread.Message ID:
@.***>


Vector Search for Historical Documents Database

Downloaded a complete Open Historical Documents from FDA other-historicaldocument-0001-of-0001.json.zip
Build ELK stack (elasticsearch, kibana, logstash) in Docker
Configure Logstash to ingest json file to elasticsearch
Install a text embedding model to convert text into vectors
Reindex imported json with text embedding in Elasticsearch
Update Flask backend code to query elasticsearch instead of FDA api

 Vector Search for Historical Documents Database (40)


Add invenio GitHub

closes https://github.com/inveniosoftware/invenio-github/issues/98

Tests are failing because invenio-github version is still the old one and has some old dependencies.
We need to:

Merge https://github.com/inveniosoftware/invenio-webhooks/issues/65 ( invenio-webhooks)
Release invenio-webhooks
Bump invenio-webhooks in invenio-github(https://github.com/inveniosoftware/invenio-github/issues/98)
Release https://github.com/inveniosoftware/invenio-github/issues/98
Bump invenio-github in the current PR