text:
Integration Error - Could not convert string to float: '01H'

Region and Brand of car
US / Hyundai Sante Fe
Describe the bug
After entering all the configuration details no data appears in the dashboard. When you view the Integrations screen you see "Retrying setup..." with error details. See below for traceback.
I am using v1.4.0, updated today.
Debug logs if an error occurred
This error originated from a custom integration.

Logger: custom_components.ha_kia_hyundai.vehicle
Source: custom_components/ha_kia_hyundai/util.py:61
Integration: Kia/Hyundai (documentation, issues)
First occurred: 1:36:27 PM (3 occurrences)
Last logged: 1:36:47 PM

Unexpected error fetching Vehicle KM8SNXXXXXX data: could not convert string to float: '01H'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/ha_kia_hyundai/vehicle.py", line 112, in async_update_data
    await self.api_cloud.update(vehicle=self)
  File "/config/custom_components/ha_kia_hyundai/api_cloud_us_hyundai.py", line 297, in update
    vehicle.climate_temperature_value = safely_get_json_value(
  File "/config/custom_components/ha_kia_hyundai/util.py", line 61, in safely_get_json_value
    value = callable_to_cast(value)
ValueError: could not convert string to float: '01H'

To Reproduce
Setup integration. Error shows that vehicle is found but couldn't setup.
Expected behavior
Integration setup and device/entities installed.
Screenshots*

@twinkie0101 thanks for providing a well written bug report. I think the fix I pushed https://github.com/dahlb/ha_kia_hyundai/commit/557c7867f7ed885d4a19163fd91481ee969c8833 will fix it for you if you try the version master from HACS.
I had to guess on the temperature range based on what I know from US Kia's implementation so if you find the temperature value doesn't match what's in the official app, please let me know what the lowest and highest temperatures you can set in the official app for your car, and I should be able to quickly calibrate it.

Thanks for the quick reply.  Switched to the master and getting the following error:
This error originated from a custom integration.

Logger: custom_components.ha_kia_hyundai.vehicle
Source: custom_components/ha_kia_hyundai/api_cloud_us_hyundai.py:303
Integration: Kia/Hyundai (documentation, issues)
First occurred: 12:40:28 AM (3 occurrences)
Last logged: 12:40:46 AM

Unexpected error fetching Vehicle KM8SN4HF9HU169346 data: 'NoneType' object has no attribute 'replace'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/ha_kia_hyundai/vehicle.py", line 112, in async_update_data
    await self.api_cloud.update(vehicle=self)
  File "/config/custom_components/ha_kia_hyundai/api_cloud_us_hyundai.py", line 303, in update
    safely_get_json_value(api_vehicle_status, "status.airTemp.value")
AttributeError: 'NoneType' object has no attribute 'replace'

I think https://github.com/dahlb/ha_kia_hyundai/commit/c18d4618860c55cf70a29f89b1447a20795b4bb5 will fix your second error, if your temperature sensor is missing after updating to this on master please add a sample of you api response in case your mapping is different then what's in the current us hyundai code

Making progress.  Was able to get the integration configured in HA, but looks like the API is having some issues.  Multiple sensors were added and the door lock was added but can't be executed (error msg is Hyundai attribute has no username).  Assuming this is related to the API issue.
Here's the API error log:
This error originated from a custom integration.

Logger: custom_components.ha_kia_hyundai
Source: custom_components/ha_kia_hyundai/__init__.py:260
Integration: Kia/Hyundai (documentation, issues)
First occurred: 9:29:25 AM (2 occurrences)
Last logged: 9:31:06 AM

Exception in interval update : sync requested but not completed! 2021-12-30 14:29:25.485733+00:00
Exception in interval update : sync requested but not completed! 2021-12-30 14:31:06.116862+00:00

Here is a screenshot of HA for the entities added:

can you attach logs for "but can't be executed (error msg is Hyundai attribute has no username)."
If you goto Configurations -> Devices & Services -> click the 1 device link within the kia/hyundai square -> click the device from the list of devices you'll get a better view of the sensors all together, screenshot attached for reference.  It is similar to the page your screenshots are from but includes the sensors current values

as for the error listed, this should improve the HA logs to improve clarity some until the request_sync api call is mapped.  "Exception in interval update : sync requested but not completed! 2021-12-30 14:29:25.485733+00:00" is saying the integration asked the Hyundai server to get new data from your vehicle but the server didn't full fill the request. I made that an exception because one of my main goal in this integration is reliability and having up to date information can really help with that. However that api call is not yet mapped for US Hyundai, updated message should read like "Exception in interval update : request_sync not implemented, api sniffing needed for this feature"

Here's the log data I believe you're asking for (maybe more):
2021-12-30 09:27:57 DEBUG (MainThread) [custom_components.ha_kia_hyundai.api_cloud_util] US HYUNDAI in use
2021-12-30 09:28:07 DEBUG (MainThread) [custom_components.ha_kia_hyundai.api_cloud_util] US HYUNDAI in use
2021-12-30 09:28:07 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/v2/ac/oauth/token request with {'username': 'email@email.com', 'password': 'password'}
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:28:08 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OY6JlRFD2vHTpm8T4iZ0001Di01MUpV', 'X-ORACLE-DMS-ECID': '000OY6JlRFD2vHTpm8T4iZ0001Di01MUpV', 'elapsedtime': '21', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '14e38144df284a50a14cd1f38ee80909', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"access_token":"access.token","refresh_token":"access.token","expires_in":"1799","username":"email@email.com"}
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/enrollment/details/email@email.com request
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:28:08 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OY6JlqHH2vHTpm8T4iZ0001Di01MUpZ', 'X-ORACLE-DMS-ECID': '000OY6JlqHH2vHTpm8T4iZ0001Di01MUpZ', 'elapsedtime': '157', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '74f561407b3a4318802e385ac57d69f5', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"enrolledVehicleDetails":[{"packageDetails":[{"assetNumber":"1-ASSET#","displayCategory":"Connected Care","packageId":"1-XXXXXX","term":"12","renewalDate":"20220317000000","packageType":"Connected Care","startDate":"20160319000000"},{"assetNumber":"1-10846338248","displayCategory":"Remote","packageId":"1-5MAJHK","term":"12","renewalDate":"20220317000000","packageType":"Remote","startDate":"20190317000000"}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20160319","svdDay":"18","trim":"SE","modelCode":"SANTA FE","ubiCapabilityInd":"Y","vin":"VEHICLE_ID","enrollmentId":"XXXXXXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"66011","nickName":"2017 SANTA FE","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"N","modelYear":"2017","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"BUTTON","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/suv/Dashboard-01.svg","sapColorCode":"TU9","bluelinkEnabled":true,"odometerUpdateDate":"20211201042545","fatcAvailable":"Y","color":"BLUE","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"0","mapProvider":"GOOGLE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"VYN","accessoryCode":"D-AUDIO","nadid":"6572923993","mit":"3750","regid":"H00001765689VVEHICLE_ID","blueLink":"Y","waypointInd":"NO","billingInd":"YEARLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png","imat":"3750","additionalVehicleDetails":{"combinedHeatSettingsEnable":"Y","temperatureRange":"false","tmuSleepMode":"No","enableHCAModule":"Y","hyundaiHome":"N","remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","dkEnrolled":"N","icpAvntCapable":"N","icpAACapable":"N","enableRoadSideAssitanceAAAModule":"Y","evAlarmOptionInfo":"No","remoteLockConsentForRemoteStartCapable":"No","mapOtaAccepted":"N","icpCPCapable":"N","dkCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"setChargeSchedule":"0","rearWindowHeatCapable":"NO","preferredDealerCode":"VA003","hmaModel":"NC","series":"SANTA FE","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"South Chesterfield","street":"1307 Majestic Creek Ct","postalCode":"23834","type":"PRIMARY","region":"VA"}],"user":{"accountId":"2141261","firstName":"WILLIAM","lastName":"BROWN","phonesOptIn":[{"number":"cellphone#","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"}],"loginId":"email@email.com","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"appRating":"N","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"cellphone#"},"tncFlag":"N","phones":[{"number":"cellphone#","type":"cell","order":1}],"idmId":"IDMID","userId":"email@email.com","notificationEmail":"email@email.com","email":"email@email.com"}}
2021-12-30 09:28:08 DEBUG (MainThread) [custom_components.ha_kia_hyundai.api_cloud_util] US HYUNDAI in use
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/v2/ac/oauth/token request with {'username': 'email@email.com', 'password': 'password'}
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:28:08 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OY6JmlkJ2vHTpm8T4iZ0001Di01MUpe', 'X-ORACLE-DMS-ECID': '000OY6JmlkJ2vHTpm8T4iZ0001Di01MUpe', 'elapsedtime': '19', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': 'ab30368a948a40c48132a9758760784b', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"access_token":"access.token","refresh_token":"access.token","expires_in":"1799","username":"email@email.com"}
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/enrollment/details/email@email.com request
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:28:08 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OY6JnAD92vHTpm8T4iZ0001Di01MUpj', 'X-ORACLE-DMS-ECID': '000OY6JnAD92vHTpm8T4iZ0001Di01MUpj', 'elapsedtime': '141', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '4aca382d22f64db9b6028bac5d83ae4e', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"enrolledVehicleDetails":[{"packageDetails":[{"assetNumber":"1-ASSET#","displayCategory":"Connected Care","packageId":"1-XXXXXX","term":"12","renewalDate":"20220317000000","packageType":"Connected Care","startDate":"20160319000000"},{"assetNumber":"1-10846338248","displayCategory":"Remote","packageId":"1-5MAJHK","term":"12","renewalDate":"20220317000000","packageType":"Remote","startDate":"20190317000000"}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20160319","svdDay":"18","trim":"SE","modelCode":"SANTA FE","ubiCapabilityInd":"Y","vin":"VEHICLE_ID","enrollmentId":"XXXXXXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"66011","nickName":"2017 SANTA FE","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"N","modelYear":"2017","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"BUTTON","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/suv/Dashboard-01.svg","sapColorCode":"TU9","bluelinkEnabled":true,"odometerUpdateDate":"20211201042545","fatcAvailable":"Y","color":"BLUE","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"0","mapProvider":"GOOGLE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"VYN","accessoryCode":"D-AUDIO","nadid":"6572923993","mit":"3750","regid":"H00001765689VVEHICLE_ID","blueLink":"Y","waypointInd":"NO","billingInd":"YEARLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png","imat":"3750","additionalVehicleDetails":{"combinedHeatSettingsEnable":"Y","temperatureRange":"false","tmuSleepMode":"No","enableHCAModule":"Y","hyundaiHome":"N","remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","dkEnrolled":"N","icpAvntCapable":"N","icpAACapable":"N","enableRoadSideAssitanceAAAModule":"Y","evAlarmOptionInfo":"No","remoteLockConsentForRemoteStartCapable":"No","mapOtaAccepted":"N","icpCPCapable":"N","dkCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"setChargeSchedule":"0","rearWindowHeatCapable":"NO","preferredDealerCode":"VA003","hmaModel":"NC","series":"SANTA FE","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"South Chesterfield","street":"1307 Majestic Creek Ct","postalCode":"23834","type":"PRIMARY","region":"VA"}],"user":{"accountId":"2141261","firstName":"WILLIAM","lastName":"BROWN","phonesOptIn":[{"number":"cellphone#","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"}],"loginId":"email@email.com","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"appRating":"N","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"cellphone#"},"tncFlag":"N","phones":[{"number":"cellphone#","type":"cell","order":1}],"idmId":"IDMID","userId":"email@email.com","notificationEmail":"email@email.com","email":"email@email.com"}}
2021-12-30 09:28:08 DEBUG (MainThread) [custom_components.ha_kia_hyundai] first update start
2021-12-30 09:28:08 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/rcs/rvs/vehicleStatus request
2021-12-30 09:28:10 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:28:09 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OY6Jo1ZN2vHTpm8T4iZ0001Di01MUpp', 'X-ORACLE-DMS-ECID': '000OY6Jo1ZN2vHTpm8T4iZ0001Di01MUpp', 'elapsedtime': '1099', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'vin': 'VEHICLE_ID', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '13a881b1057a431491192948e38243e9', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:28:10 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"hataTID":"ABeX0GF9TDmqx4sTx7erog","vehicleStatus":{"dateTime":"2021-12-22T20:38:40Z","acc":false,"trunkOpen":false,"doorLock":false,"defrostStatus":"false","doorLockStatus":"false","doorOpen":{"frontRight":1,"frontLeft":0,"backLeft":0,"backRight":0},"airCtrlOn":false,"airTemp":{"unit":0,"hvacTempType":0,"value":"01H"},"vehicleLocation":{"coord":{"lon":-77.38712183333334,"type":0,"lat":37.25009183}},"ign3":false,"ignitionStatus":"false","lowFuelLight":false,"sideBackWindowHeat":0,"engine":false,"defrost":false,"airConditionStatus":"false","steerWheelHeat":0,"trunkOpenStatus":"false"}}
2021-12-30 09:28:10 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/enrollment/details/email@email.com request
2021-12-30 09:28:10 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:28:10 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OY6JsYGh2vHTpm8T4iZ0001Di01MUqK', 'X-ORACLE-DMS-ECID': '000OY6JsYGh2vHTpm8T4iZ0001Di01MUqK', 'elapsedtime': '140', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '4c95dcd488034562b143b1a37a90220a', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:28:10 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"enrolledVehicleDetails":[{"packageDetails":[{"assetNumber":"1-ASSET#","displayCategory":"Connected Care","packageId":"1-XXXXXX","term":"12","renewalDate":"20220317000000","packageType":"Connected Care","startDate":"20160319000000"},{"assetNumber":"1-10846338248","displayCategory":"Remote","packageId":"1-5MAJHK","term":"12","renewalDate":"20220317000000","packageType":"Remote","startDate":"20190317000000"}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20160319","svdDay":"18","trim":"SE","modelCode":"SANTA FE","ubiCapabilityInd":"Y","vin":"VEHICLE_ID","enrollmentId":"XXXXXXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"66011","nickName":"2017 SANTA FE","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"N","modelYear":"2017","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"BUTTON","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/suv/Dashboard-01.svg","sapColorCode":"TU9","bluelinkEnabled":true,"odometerUpdateDate":"20211201042545","fatcAvailable":"Y","color":"BLUE","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"0","mapProvider":"GOOGLE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"VYN","accessoryCode":"D-AUDIO","nadid":"6572923993","mit":"3750","regid":"H00001765689VVEHICLE_ID","blueLink":"Y","waypointInd":"NO","billingInd":"YEARLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png","imat":"3750","additionalVehicleDetails":{"combinedHeatSettingsEnable":"Y","temperatureRange":"false","tmuSleepMode":"No","enableHCAModule":"Y","hyundaiHome":"N","remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","dkEnrolled":"N","icpAvntCapable":"N","icpAACapable":"N","enableRoadSideAssitanceAAAModule":"Y","evAlarmOptionInfo":"No","remoteLockConsentForRemoteStartCapable":"No","mapOtaAccepted":"N","icpCPCapable":"N","dkCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"setChargeSchedule":"0","rearWindowHeatCapable":"NO","preferredDealerCode":"VA003","hmaModel":"NC","series":"SANTA FE","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"South Chesterfield","street":"1307 Majestic Creek Ct","postalCode":"23834","type":"PRIMARY","region":"VA"}],"user":{"accountId":"2141261","firstName":"WILLIAM","lastName":"BROWN","phonesOptIn":[{"number":"cellphone#","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"}],"loginId":"email@email.com","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"appRating":"N","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"cellphone#"},"tncFlag":"N","phones":[{"number":"cellphone#","type":"cell","order":1}],"idmId":"IDMID","userId":"email@email.com","notificationEmail":"email@email.com","email":"email@email.com"}}
2021-12-30 09:28:10 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] Finished fetching Vehicle VEHICLE_ID data in 1.499 seconds (success: True)
2021-12-30 09:28:10 DEBUG (MainThread) [custom_components.ha_kia_hyundai] first update finished
2021-12-30 09:29:10 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:29:10 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] requesting a sync based on scan interval; age_of_last_sync:7 days, 17:50:30.485151; last synced:2021-12-22 20:38:40+00:00; now:2021-12-30 14:29:10.484867+00:00
2021-12-30 09:29:25 DEBUG (MainThread) [custom_components.ha_kia_hyundai.api_cloud_us_hyundai] request_sync no implemented
2021-12-30 09:29:25 ERROR (MainThread) [custom_components.ha_kia_hyundai] Exception in interval update : sync requested but not completed! 2021-12-30 14:29:25.485733+00:00
2021-12-30 09:29:48 DEBUG (MainThread) [custom_components.ha_kia_hyundai.config_flow] user input in option flow : {'scan_interval': 30, 'force_scan_interval': 240, 'no_force_scan_hour_start': 18, 'no_force_scan_hour_finish': 6}
2021-12-30 09:29:48 DEBUG (MainThread) [custom_components.ha_kia_hyundai.api_cloud_util] US HYUNDAI in use
2021-12-30 09:29:48 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/v2/ac/oauth/token request with {'username': 'email@email.com', 'password': 'password'}
2021-12-30 09:29:49 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:29:49 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OasVNoNi2vHTpm8S4yZ0006sn01MWu5', 'X-ORACLE-DMS-ECID': '000OasVNoNi2vHTpm8S4yZ0006sn01MWu5', 'elapsedtime': '19', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '868a55be140d4c79b7e04aacb39718a1', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:29:49 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"access_token":"access.token","expires_in":"1799","username":"email@email.com"}
2021-12-30 09:29:49 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/enrollment/details/email@email.com request
2021-12-30 09:29:49 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:29:49 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OasVOE9j2vHTpm8S4yZ0006sn01MWu8', 'X-ORACLE-DMS-ECID': '000OasVOE9j2vHTpm8S4yZ0006sn01MWu8', 'elapsedtime': '185', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '2f5c521263994860b3327107d721e62e', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:29:49 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"enrolledVehicleDetails":[{"packageDetails":[{"assetNumber":"1-ASSET#","displayCategory":"Connected Care","packageId":"1-XXXXXX","term":"12","renewalDate":"20220317000000","packageType":"Connected Care","startDate":"20160319000000"},{"assetNumber":"1-10846338248","displayCategory":"Remote","packageId":"1-5MAJHK","term":"12","renewalDate":"20220317000000","packageType":"Remote","startDate":"20190317000000"}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20160319","svdDay":"18","trim":"SE","modelCode":"SANTA FE","ubiCapabilityInd":"Y","vin":"VEHICLE_ID","enrollmentId":"XXXXXXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"66011","nickName":"2017 SANTA FE","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"N","modelYear":"2017","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"BUTTON","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/suv/Dashboard-01.svg","sapColorCode":"TU9","bluelinkEnabled":true,"odometerUpdateDate":"20211201042545","fatcAvailable":"Y","color":"BLUE","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"0","mapProvider":"GOOGLE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"VYN","accessoryCode":"D-AUDIO","nadid":"6572923993","mit":"3750","regid":"H00001765689VVEHICLE_ID","blueLink":"Y","waypointInd":"NO","billingInd":"YEARLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png","imat":"3750","additionalVehicleDetails":{"combinedHeatSettingsEnable":"Y","temperatureRange":"false","tmuSleepMode":"No","enableHCAModule":"Y","hyundaiHome":"N","remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","dkEnrolled":"N","icpAvntCapable":"N","icpAACapable":"N","enableRoadSideAssitanceAAAModule":"Y","evAlarmOptionInfo":"No","remoteLockConsentForRemoteStartCapable":"No","mapOtaAccepted":"N","icpCPCapable":"N","dkCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"setChargeSchedule":"0","rearWindowHeatCapable":"NO","preferredDealerCode":"VA003","hmaModel":"NC","series":"SANTA FE","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"South Chesterfield","street":"1307 Majestic Creek Ct","postalCode":"23834","type":"PRIMARY","region":"VA"}],"user":{"accountId":"2141261","firstName":"WILLIAM","lastName":"BROWN","phonesOptIn":[{"number":"cellphone#","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"}],"loginId":"email@email.com","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"appRating":"N","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"cellphone#"},"tncFlag":"N","phones":[{"number":"cellphone#","type":"cell","order":1}],"idmId":"IDMID","userId":"email@email.com","notificationEmail":"email@email.com","email":"email@email.com"}}
2021-12-30 09:29:49 DEBUG (MainThread) [custom_components.ha_kia_hyundai] first update start
2021-12-30 09:29:49 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/rcs/rvs/vehicleStatus request
2021-12-30 09:29:50 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:29:49 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OasVPKFb2vHTpm8S4yZ0006sn01MWuD', 'X-ORACLE-DMS-ECID': '000OasVPKFb2vHTpm8S4yZ0006sn01MWuD', 'elapsedtime': '1095', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'vin': 'VEHICLE_ID', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '8af2bae97e434ba58413e7666f43237a', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:29:50 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"hataTID":"aqrhY_oGRLmQ0bavk454_g","vehicleStatus":{"dateTime":"2021-12-22T20:38:40Z","acc":false,"trunkOpen":false,"doorLock":false,"defrostStatus":"false","doorLockStatus":"false","doorOpen":{"frontRight":1,"frontLeft":0,"backLeft":0,"backRight":0},"airCtrlOn":false,"airTemp":{"unit":0,"hvacTempType":0,"value":"01H"},"vehicleLocation":{"coord":{"lon":-77.38712183333334,"type":0,"lat":37.25009183}},"ign3":false,"ignitionStatus":"false","lowFuelLight":false,"sideBackWindowHeat":0,"engine":false,"defrost":false,"airConditionStatus":"false","steerWheelHeat":0,"trunkOpenStatus":"false"}}
2021-12-30 09:29:50 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] sending https://api.telematics.hyundaiusa.com/ac/v2/enrollment/details/email@email.com request
2021-12-30 09:29:51 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response headers:<CIMultiDictProxy('Date': 'Thu, 30 Dec 2021 14:29:50 GMT', 'Server': 'Oracle-Application-Server-11g', 'Access-Control-Allow-Methods': 'POST, GET, PUT, ', 'Access-Control-Max-Age': '1000', 'Access-Control-Allow-Headers': 'language, offset, UCID, From, x-requested-with, Content-Type, origin, authorization, accept, client-security-token, accesstoken, clientId, clientSecret', 'Access-Control-Allow-Credentials': 'true', 'Access-Control-Allow-Headers': 'x-requested-with', 'Content-Language': 'en,en-us', 'to': 'ISS', 'X-ORACLE-DMS-ECID': '000OasVTqE52vHTpm8S4yZ0006sn01MWum', 'X-ORACLE-DMS-ECID': '000OasVTqE52vHTpm8S4yZ0006sn01MWum', 'elapsedtime': '264', 'Access-Control-Allow-Methods': 'POST, GET', 'gen': '2', 'Access-Control-Allow-Origin': '*', 'From': 'SPA', 'guid': '568e9dcbd6914401a07cb85194058430', 'X-ORACLE-DMS-RID': '0:1', 'X-ORACLE-DMS-RID': '0:1', 'Access-Control-Expose-Headers': 'transactionId, transactionDate, offset, language', 'Access-Control-Max-Age': '3600', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json', 'Public-Key-Pins-Report-Only': 'pin-sha256="NoKLOeGQwqGYqDPaJlMu2LvRPdj298oekgJLhW1wiFA="; pin-sha256="256_PIN_#/yOhI/y+ho="; max-age=86400; report-uri="https://hyundaiusa.com/pin/"')>
2021-12-30 09:29:51 DEBUG (MainThread) [kia_hyundai_api.us_hyundai] response text:{"enrolledVehicleDetails":[{"packageDetails":[{"assetNumber":"1-ASSET#","displayCategory":"Connected Care","packageId":"1-XXXXXX","term":"12","renewalDate":"20220317000000","packageType":"Connected Care","startDate":"20160319000000"},{"assetNumber":"1-10846338248","displayCategory":"Remote","packageId":"1-XXXXXX","term":"12","renewalDate":"20220317000000","packageType":"Remote","startDate":"20190317000000"}],"vehicleDetails":{"svrStatus":"NONE","dynamicBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","remoteStartWakeupDays":"four","enrollmentDate":"20160319","svdDay":"18","trim":"SE","modelCode":"SANTA FE","ubiCapabilityInd":"Y","vin":"VEHICLE_ID","enrollmentId":"XXXXXXX","sideMirrorHeatCapable":"NO","ownersuccession":"1","odometer":"66011","nickName":"2017 SANTA FE","defaultBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","evStatus":"N","modelYear":"2017","steeringWheelHeatCapable":"NO","defaultDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/default/Dashboard-01.png","vehicleGeneration":"2","starttype":"BUTTON","silhouette":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/suv/Dashboard-01.svg","sapColorCode":"TU9","bluelinkEnabled":true,"odometerUpdateDate":"20211201042545","fatcAvailable":"Y","color":"BLUE","maintSyncCapable":"NO","brandIndicator":"H","deviceStatus":"ENROLLED","setOffPeak":"0","mapProvider":"GOOGLE","generalBurgerMenu":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png/jcr:content/renditions/cq5dam.thumbnail.105.68.png","interiorColor":"VYN","accessoryCode":"D-AUDIO","nadid":"6572923993","mit":"3750","regid":"H00001765689VVEHICLE_ID","blueLink":"Y","waypointInd":"NO","billingInd":"YEARLY","dynamicDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/se/exterior/base/storm-blue/Dashboard-01.png","imat":"3750","additionalVehicleDetails":{"combinedHeatSettingsEnable":"Y","temperatureRange":"false","tmuSleepMode":"No","enableHCAModule":"Y","hyundaiHome":"N","remoteLockConsentForRemoteStart":"No","calendarVehicleSyncEnable":"No","dkEnrolled":"N","icpAvntCapable":"N","icpAACapable":"N","enableRoadSideAssitanceAAAModule":"Y","evAlarmOptionInfo":"No","remoteLockConsentForRemoteStartCapable":"No","mapOtaAccepted":"N","icpCPCapable":"N","dkCapable":"N","enableValetActivate":"N","energyConsoleCapable":"No"},"transmissiontype":"AUTO","bluelinkEnrolled":true,"setChargeSchedule":"0","rearWindowHeatCapable":"NO","preferredDealerCode":"VA003","hmaModel":"NC","series":"SANTA FE","enrollmentStatus":"ACTIVE","generalDashboard":"https://owners.hyundaiusa.com/content/dam/hyundai/us/myhyundai/image/2017/santa-fe/general/exterior/base/default/Dashboard-01.png","userprofilestatus":"NA"},"roleDetails":[{"roleCode":"OWN","roleName":"OWNER"},{"roleCode":"SUB","roleName":"SUBSCRIBER"}],"responseHeaderMap":{}}],"addressDetails":[{"city":"South Chesterfield","street":"1307 Majestic Creek Ct","postalCode":"23834","type":"PRIMARY","region":"VA"}],"user":{"accountId":"2141261","firstName":"WILLIAM","lastName":"BROWN","phonesOptIn":[{"number":"cellphone#","primaryPhoneIndicator":"YES","fccOptIn":"","type":"MOBILE"}],"loginId":"email@email.com","additionalUserDetails":{"userProfileUpdate":"N","timezoneOffset":-5,"appRating":"N","timezoneAbbr":"EST","otaAcceptance":"N","telematicsPhoneNumber":"cellphone#"},"tncFlag":"N","phones":[{"number":"cellphone#","type":"cell","order":1}],"idmId":"IDMID","userId":"email@email.com","notificationEmail":"email@email.com","email":"email@email.com"}}
2021-12-30 09:29:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] Finished fetching Vehicle VEHICLE_ID data in 1.553 seconds (success: True)
2021-12-30 09:29:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai] first update finished
2021-12-30 09:30:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:30:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] requesting a sync based on scan interval; age_of_last_sync:7 days, 17:52:11.115862; last synced:2021-12-22 20:38:40+00:00; now:2021-12-30 14:30:51.115700+00:00
2021-12-30 09:31:06 DEBUG (MainThread) [custom_components.ha_kia_hyundai.api_cloud_us_hyundai] request_sync no implemented
2021-12-30 09:31:06 ERROR (MainThread) [custom_components.ha_kia_hyundai] Exception in interval update : sync requested but not completed! 2021-12-30 14:31:06.116862+00:00
2021-12-30 09:31:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:31:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] sync request skipping, interval sync request failed to be fulfilled by Vehicle, REQUEST_TO_SYNC_COOLDOWN:0:15:00; age_of_last_request_to_sync:0:00:45.000039
2021-12-30 09:32:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:32:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] sync request skipping, interval sync request failed to be fulfilled by Vehicle, REQUEST_TO_SYNC_COOLDOWN:0:15:00; age_of_last_request_to_sync:0:01:45.000711
2021-12-30 09:33:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:33:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] sync request skipping, interval sync request failed to be fulfilled by Vehicle, REQUEST_TO_SYNC_COOLDOWN:0:15:00; age_of_last_request_to_sync:0:02:45.001313
2021-12-30 09:34:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:34:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] sync request skipping, interval sync request failed to be fulfilled by Vehicle, REQUEST_TO_SYNC_COOLDOWN:0:15:00; age_of_last_request_to_sync:0:03:45.002215
2021-12-30 09:35:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:35:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] sync request skipping, interval sync request failed to be fulfilled by Vehicle, REQUEST_TO_SYNC_COOLDOWN:0:15:00; age_of_last_request_to_sync:0:04:45.003764
2021-12-30 09:36:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] interval update skipping
2021-12-30 09:36:51 DEBUG (MainThread) [custom_components.ha_kia_hyundai.vehicle] sync request skipping, interval sync request failed to be fulfilled by Vehicle, REQUEST_TO_SYNC_COOLDOWN:0:15:00; age_of_last_request_to_sync:0:05:45.004660
2021-12-30 09:37:36 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139758756181808] 'UsHyundai' object has no attribute 'username'

that's exactly what I needed, thank. found the error https://github.com/dahlb/kia_hyundai_api/commit/6687124931783c7391315c370a31c2f0248ae169 and updated in master https://github.com/dahlb/ha_kia_hyundai/commit/d77dc2255135f8ee66cd29388082bd00fb4463fc

looks like it's working, thanks for quick responses and updates!


text:
Revert #489

https://github.com/dahlbyk/posh-git/pull/489 accidentally brought all of develop into master. That's what I get for being lazy and trying to do everything from GitHub dot com. 😒

But I thought #489 merged master down to develop instead of the other way around?

But I thought #489 merged master down to develop instead of the other way around?

It did, but resolving the conflict online created https://github.com/dahlbyk/posh-git/pull/489/commits/79770b8ed5fe8b065483d6433896fbc00d3fc9af: "Merge branch 'develop' into master". Oops!

Doh!

Blah. So merging master into develop now includes this change, undoing all our work. Reverting the revert does work, but essentially discards the individual commits for blame purposes.
So.... I'm going to --force master back pre-#489 and try this all again. 👿

source: gharchive/pull-request

authors: dahlbyk rkeithhill

repo: dahlbyk/posh-git

license: mit

license_type: permissive

license_source: bigquery


text:
该领域属于字体生成领域吗

作者你好，请问手写体生成 属于font genaration吗? 我搜索手写体生成相关的论文不多，font genaration 倒是有一些，我能从font genaration的文章中 找灵感吗hh

手写体生成不属于font generation领域。论文可以广泛的看: Handwriting Generation, Font Generation, Vector Font Generation, Scene Text Generation，这些都可以看看找找灵感

手写体生成不属于font generation领域。论文可以广泛的看: Handwriting Generation, Font Generation, Vector Font Generation, Scene Text Generation，这些都可以看看找找灵感

好的，谢谢作者。 还有一个问题就是，CASIA数据集可以下载到它的手写字的png或jpg图像吗。（不想自己写字构造了..)

手写体生成不属于font generation领域。论文可以广泛的看: Handwriting Generation, Font Generation, Vector Font Generation, Scene Text Generation，这些都可以看看找找灵感

好的，谢谢作者。 还有一个问题就是，CASIA数据集可以下载到它的手写字的png或jpg图像吗。（不想自己写字构造了..)

可以在这个网页中下载到png数据集

source: gharchive/issue

repo: dailenson/SDT

license: MIT

license_source: github-api


text:
More abstract serializer and deserializer for encode() and decode()

Is your feature request related to a problem? Please describe.
Currently pyseto implicitly assumes the function name of the serializer.
I am using ormsgpack for my API & I so decided to use ormsgpack but it has different alias for dumps and loads so the serializer parameter becomes useless .It would be better if could accept a function which serializes thus we can use any serialization method

@Shahprogrammer Thanks for the request. But I'm busy now and I think it takes some time to consider your request. Could you consider to send a PR to resolve this? I welcome your contribution.

authors: Shahprogrammer dajiaji

repo: dajiaji/pyseto


text:
TestServ is missing a method to add a property

Currently if we want to add invidual properties onto a mock service that we've generated using MockServ we cannot use the chaining pattern and need to declare the property on the object with full syntax breaking the flow.
Instead there should be an addProperty method on TestServ that although will not add a spy (since it's merely a value), it will allow us to follow a standard chaining syntax.
I plan to submit a PR within the next week for this
var MockServ = new TestServ();
MockServ
    .addMethod('foo', 'barVal');
    .addMethod('fooFunc', function() { return 'barFunc' } )
    .addProperty('fooStream', new Rx.Subject())

Good idea, thanks. I will try to add this method today.

It's available in release 0.0.11 now.

authors: HipsterZipster dakolech

repo: dakolech/angular-unit-testing-helpers


text:
Add a shortcut to copy a query

I'd like to easily and quickly grab a copy of a query that's been running for a long time in order to save it off before killing it. Even better if it was a keyboard shortcut that copied to my system clipboard.
Perhaps pyperclip can be of use?

I second this request!

I have a patch to "zoom" on the query and display it full screen.
I didn't think about the clipboard. I will look into it.
Thanks for the issue.

Perhaps pyperclip can be of use?

I'm not sure this would be a good fit for pg_activity as it seems to me that pyperclip relies on graphical selections (e.g. xsel) whereas pg_activity is often used without a graphical environment (i.e. remotely through, e.g. ssh or on using sudo -iu postgres).

authors: blogh dhenson02 dlax nogweii

license: PostgreSQL


text:
Update search box with sort order option

Summary

Closes #217

Test plan
React tests verified

Two CI checked failed:

More vulnerabilities found in Dropbox SDK module
SourceClear check in Travis fails due to over usage of free account, so I'll remove from Travis

repo: danactive/history


text:
Async would be awesome

All my api is async but this piece of code.
I understand you need to support old .net but what about a new branch for 4.5?

Please see this wiki article and this issue.  What changes do you think we'd need to make to support async (and probably remove ServiceStack.Text at the same time)?

(FYI -- I'm asking because you seem opinionated and experienced with async)

Well, the only thing I did with this library is install it and used the subscribe method with some merge tags. So I will have to take a deep look before evaluating that. I´ve never used ServiceStack.text before. To understand it better, Is there any reason not to use Json.NET ?

I think the trick is to make this line async somehow (on MakeAPICall method) :
var resultString = fullUrl.PostJsonToUrl(args);

Then, making the method awaitable:
private async Task<T> MakeAPICall<T>(string apiAction, object args)
And then, making awaitable all the methods with calls to MakeApiCall(). For example:
public async Task<Opened> GetReportOpened(string cId, OpenedOptions opts = null)
        {
            //  Our api action:
            string apiAction = "reports/opened";

            //  Create our arguments object:
            object args = new
            {
                apikey = this.APIKey,
                cid = cId,
                opts = opts
            };

            //  Make the call:
            return await MakeAPICall<Opened>(apiAction, args);
        }

Another option would be creating an extension library with all the async method extension, if you want to keep compatibility with 3.5. I need to make some tests

Hi again,
Take a look at this:
Task<string> PostJsonToUrlAsync(...)

https://github.com/ServiceStack/ServiceStack/wiki/Http-Utils#async-http-utils
It seams that upgrading ServiceStack, making Mailchimp async would be easy.
What do you think?

The reason we don't upgrade the ServiceStack dependency is because it's not free anymore.

I understand and so I would suggest to change the underlying REST client to something like this: https://github.com/paulcbetts/refit

+1 on this. I have a scenario where i need to subscribe a single user to 3 lists. Using the current implementation, can take up to 5-10 seconds. Unfortunately MailChimp don't support a batch operation for this (only support multiple emails to 1 list, not the other way around). So i need a SubscribeAsync method. Might fork this repo and submit a PR. Agree with @xleon - suggest changing to use HttpClient

authors: RPM1984 SteveVaneeckhout danesparza xleon


text:
Allow drag and drop for text

Hi,
I would like to add an option for the users to drag and drop both text and images (or other files) to the same element.
But I encountered a problem when setting the directive on the element that contain text input elements inside it. Adding files is working like it should, but when I try to drag and drop text to those input elements it's not accepted - nothing happens.
Am I overlooking something here or it can not be set to accept plain text?
Thanks for the great plug in!

This is a plugin for file upload so dropping a text wouldn't make much sense for this plugin.
You could set the ngf-stop-propagation to false and then add another drop listener to the element to handle text drops.

Hi,
Thank for you reply
Ngf-stop-propagation didn't work for me, so I came up with a different solution.
I've created a new directive and assigned it to the text input element.
That directive looks like this:
define([], function () {
var dropTextDirective = function ()
{

    var dragdroptext = {};

    dragdroptext.restrict = 'A';

    dragdroptext.link = function(scope, element)
    {
		// convert current element to javascript DOM element
		var raw_element = angular.element(element)[0];

		var handleTextDrop = function(e)
		{
			// if text is being dragged allow it to be dropped on the element
			// and stop propagation - stop event to be handled by dropFilesDirective
			if ($.inArray('text/plain', e.dataTransfer.types) > -1)
			{
				e.stopPropagation();
			}
		};

		raw_element.addEventListener("dragover", handleTextDrop, false);
		raw_element.addEventListener("drop", handleTextDrop, false);

    };

	return dragdroptext;
};

return [dropTextDirective];

});
Thank for the great plug-in!

repo: danialfarid/ng-file-upload


text:
Broken in 10.10

Error
Couldn't parse ISO 8601 date string '2024-05-24 20:30:00'
Error: Couldn't parse ISO 8601 date string '2024-05-24 20:30:00'
at o (https://domain/web/main.jellyfin.bundle.js?a287d3e18cbd61b097f5:2:297893)
at https://domain/web/plugins-plugin.942f3de331163293b572.chunk.js:1:9626
at Array.map ()
at en (https://domain/web/plugins-plugin.942f3de331163293b572.chunk.js:1:9435)
at hu (https://domain/web/node_modules.react-dom.bundle.js?a287d3e18cbd61b097f5:2:60311)
at xi (https://domain/web/node_modules.react-dom.bundle.js?a287d3e18cbd61b097f5:2:119252)
at bs (https://domain/web/node_modules.react-dom.bundle.js?a287d3e18cbd61b097f5:2:108504)
at vs (https://domain/web/node_modules.react-dom.bundle.js?a287d3e18cbd61b097f5:2:108432)
at gs (https://domain/web/node_modules.react-dom.bundle.js?a287d3e18cbd61b097f5:2:108295)
at as (https://domain/web/node_modules.react-dom.bundle.js?a287d3e18cbd61b097f5:2:105130)

Hi there,
I've just released a new version. Could you please check if everything is working as expected now? Let me know if you encounter any issues.
Thank you!

repo: danieladov/jellyfin-plugin-themesongs


text:
EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)

I am getting EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
How to fix it?

That's because the JavaScript file is not found. You need to run the gulp task.

authors: danielbuechele lubieapki

repo: danielbuechele/goofy


text:
Upload the prerendered JSON files into S3

This PR implements the getStaticProps part of https://github.com/danielcondemarin/serverless-next.js/issues/355 for getStaticPaths, falback: false
There was no need to define a new cache behaviour will be created in CloudFront for the path pattern for /_next/data/* because this cache behaviour already covers those paths with /_next/* wildcard.
The page has to be visited for caching it. While ZEIT(Vercel) Now has some sort of mechanism to always keep it on cache. I think @danielcondemarin your https://github.com/danielcondemarin/serverless-next.js/issues/355#issuecomment-612516359 indicates that it's possible but with a limit. Also I guess that's why ZEIT(Vercel) Now implemented a 24 Serverless Functions per Deployment limit for Pro plan recently. For a website that with never changing static pages, on certain paths, can we make MinTTL infinite(or at least a huge value)?
The old deployments will consume quite amount of S3 storage space, so I think there should be a clean up after the deployment. The build IDs are always 21 characters long, so maybe we can look up for directories under /_next/data/ with 21 characters name and not equal to current build ID.

I tried to redeploy using this PR but CloudFront uses the old cache somehow and pages suppose to be updated are not updating.

Thanks for looking into this @mertyildiran !

There was no need to define a new cache behaviour will be created in CloudFront for the path pattern for /_next/data/* because this cache behaviour already covers those paths with /_next/* wildcard.

The cache behaviour in your link is for the old version of this project. serverless-plugin is not the same as serverless-component. Components are a new project the serverless framework folks started. The cache behaviour you're looking for is this one: https://github.com/danielcondemarin/serverless-next.js/blob/master/packages/serverless-component/serverless.js#L139
And yes you're right, for supporting getStaticProps and getStaticPaths: fallback: false we I think we don't need another cache behaviour 👍

For a website that with never changing static pages, on certain paths, can we make MinTTL infinite(or at least a huge value)
There is a PR that will allow configuring the cache behaviour TTLs etc > https://github.com/danielcondemarin/serverless-next.js/pull/282

The old deployments will consume quite amount of S3 storage space, so I think there should be a clean up after the deployment. The build IDs are always 21 characters long, so maybe we can look up for directories under /_next/data/ with 21 characters name and not equal to current build ID.

We have to be careful about this, since serverless-next apps are replicated across the globe, we can only cleanup old builds once Cloudfront has fully propagated the changes, so it may not be as easy as it seems. I think is better to handle that on a separate issue / PR.

One more thing, could you add a test like this one 🙏 ?

@danielcondemarin OK, I've added a test.

I tried to redeploy using this PR but CloudFront uses the old cache somehow and pages suppose to be updated are not updating.

:point_up: OK, I think people will have to use serverless-cloudfront-invalidate package to invalidate the cache if they want to invalidate. So I see now that's an issue of this PR.

There is a PR that will allow configuring the cache behaviour TTLs etc > #282

Great! :+1:

We have to be careful about this, since serverless-next apps are replicated across the globe, we can only cleanup old builds once Cloudfront has fully propagated the changes, so it may not be as easy as it seems. I think is better to handle that on a separate issue / PR.

Cached pages do not come from S3, I've tested that just a moment ago by deleting all of the old build folders. If the page is cached, it will be fetch from CloudFront CDN, otherwise AWS will pull it from S3. That's what I understand, I might be wrong. Sure we can discuss on another issue or PR.

@mertyildiran Is this PR ready ✅ now?

@danielcondemarin I was afraid that upload time will take too long but for ~4000 pages it got only 0.4% slower. I'm not sure what happens if we hit huge numbers though. Is it possible to bulk upload to S3 or upload in parallel(if it's not in parallel already)?
As I said in here, ZEIT Now has some sort of mechanism to cache the pages by default. I mean even if you are the first visitor of the page, because the page is cached before-hand, you get the HTML instantly. Maybe it's related to https://github.com/danielcondemarin/serverless-next.js/issues/355#issuecomment-617615399 Check this website of mine which I've deployed to ZEIT Now, for example. Everything is instantaneous in that website. How can we achieve the same result with serverless-next.js? Please guide me.

@danielcondemarin I was afraid that upload time will take too long but for ~4000 pages but it got only 0.4% slower. I'm not sure what happens if we hit huge numbers though. Is it possible to bulk upload to S3 or upload in parallel(if it's not in parallel already)?

Only 0.4% slower is awesome! It already should be uploading to S3 in parallel. As you may have seen on top of that it tries to use S3 accelerated uploads which is much faster.
One question, how long does it take for you to upload the 4k pages?

As I said in here, ZEIT Now has some sort of mechanism to cache the pages by default. I mean even if you are the first visitor of the page, because the page is cached before-hand, you get the HTML instantly. Maybe it's related to #355 (comment) Check this website of mine which I've deployed to ZEIT Now, for example. Everything is instantaneous in that website. How can we achieve the same result with serverless-next.js? Please guide me.

AFAIK I know CloudFront doesn't support what you are describing. Do you have any reference ~ZEIT~ Vercel  😁 documentation I can take a look at? Couldn't find much here.

@danielcondemarin actually I tried to calculate the elapsed time with two different approaches and I get 200 - 300 seconds for uploading 9k pages, on a 5 mbps upload speed connection.
With the same internet connection, deployment of 9k pages took 2265 seconds.

AFAIK I know CloudFront doesn't support what you are describing. Do you have any reference ZEIT Vercel grin documentation I can take a look at? Couldn't find much here.

I don't have any proof but I rely on my observations. Maybe I should visit all pages(programmatically) after every deployment(via a shell script for example) and set MinTTL to a huge value(I don't know what's the maximum value, maybe you can tell me?) therefore I trigger the caching.

@danielcondemarin actually I tried to calculate the elapsed time with two different approaches and I get 200 - 300 seconds for uploading 9k pages, on a 5 mbps upload speed connection.

Do you know how long it takes when deploying to Zeit NOW?
Uploads to S3 are async as you can see here. Not sure how else we could optimise here tbh. Since this task is IO and not CPU bound, creating a few more node processes won't make much difference.

Maybe I should visit all pages(programmatically) after every deployment(via a shell script for example) and set MinTTL to a huge value(I don't know what's the maximum value, maybe you can tell me?) therefore I trigger the caching.

You could do that but bear in mind that would only result in caching at one of CloudFront's points of presence / edge location and possibly a regional cache as well. For minimum TTL I'd recommend you set it to one year if you want it to not expire. This RFC recommends doing that.

To mark a response as "never expires," an origin server sends an
Expires date approximately one year from the time the response is
sent. HTTP/1.1 servers SHOULD NOT send Expires dates more than one
year in the future.

@danielcondemarin I cannot deploy to ZEIT Now because of maximum 24 Serverless Functions per Deployment limit. :smile:
There is a package called s3-batch-upload but I'm not sure how usable it's in this scenario.
OK, I'm gonna set MinTTL to 31556952 then. But until https://github.com/danielcondemarin/serverless-next.js/pull/282 merged, I have to do it using AWS's beautiful web UI :smile:

@danielcondemarin by the way, I'm gonna do a few more checks before marking this PR Ready.

@danielcondemarin I put console.log into getStaticProps and getStaticPaths function bodies and whenever I visit an uncached page I see a log created by getStaticProps in the CloudWatch. That means this PR is not working. What could be wrong?

@danielcondemarin I put console.log into getStaticProps and getStaticPaths function bodies and whenever I visit an uncached page I see a log created by getStaticProps in the CloudWatch. That means this PR is not working. What could be wrong?

Did you set fallback: false ? getStaticProps should only be called once at build time unless fallback: true (which we haven't implemented yet).

@danielcondemarin I put console.log into getStaticProps and getStaticPaths function bodies and whenever I visit an uncached page I see a log created by getStaticProps in the CloudWatch. That means this PR is not working. What could be wrong?

Did you set fallback: false ? getStaticProps should only be called once at build time unless fallback: true (which we haven't implemented yet).

Also, could you check if there is a .js file for the page bundle? If that's the case we may need to check fallback: false to avoid SSR the js page bundle and proxy the request to the prerendered HTML that lives in S3.

@danielcondemarin I return fallback: false from getStaticPaths functions like:
return { paths, fallback: false };

There are .js files on my local machine in directories like .serverless_nextjs/default-lambda/pages/post/[id].js if that's the thing you are asking.
If you're talking about the existence of .js files in AWS then where should I look? There are no .js files in S3, if that's the case.

There are .js files on my local machine in directories like .serverless_nextjs/default-lambda/pages/post/[id].js if that's the thing you are asking.

Right, so I have a theory of what is happening:
Because next.js outputs a .js file for fallback: false pages (don't see why) serverless-next.js thinks is a server side rendered page, therefore the request is treated as such, leading to getStaticProps getting called.
An easy way around it would be to look at the prerender-manifest.json and don't copy the .js page file to the lambda artefact if fallback: false. For example:
  "dynamicRoutes": {
    "/post/[id]": {
      "routeRegex": "...",
      "dataRoute": "/_next/data/123/post/[id].json",
      "fallback": false,
      "dataRouteRegex": "..."
    }

When fallback: false we only need to copy the pre-rendered HTML page and its associated JSON props file:
.next/serverless/pages/post/
 > [id].js                # ignore this file when uploading assets to S3
 > id-123.html      # this needs to be uploaded to S3
 > id-456.html     # this needs to be uploaded to S3
 > ...
 > id-123.json      # this needs to be uploaded to S3
 > id-456.json     # this needs to be uploaded to S3
 > ...

To do this, you'll need to change a few things:

Make sure we upload the prerender-manifest.json file to the Lambda@Edge default artefact. You'll have to do that here

Make sure we upload the pre-rendered HTML pages (id-123, id-456, etc.) to S3. You can do that in the s3-static-assets package which you are already familiar with. The HTML pages are listed in the routes field of the prerender-manifest.json

Update the default lambda@edge handler so it checks the prerender-manifest. Using the regex provided in routeRegex match against the incoming user request and forward to S3 if it matches.

I may be missing something here, but its the best I can do in 15 mins of writing 😄
Btw: I think I may start a disqus chat group for people to be able to join, especially contributors like yourself. That way communication happens quicker 💨

@danielcondemarin thanks for the detailed guide. I can do 1 and 2, but 3 is beyond my understanding of inner workflows of serverless-next.js. Could you do 3?

@danielcondemarin thanks for the detailed guide. I can do 1 and 2, but 3 is beyond my understanding of inner workflows of serverless-next.js. Could you do 3?

Yes! I’m happy to. Just let me know once the prerender-manifest is being uploaded and I’ll jump on the PR

@danielcondemarin I did 1 and 2, although;
I added this function sort of a duplicate of index.ts#L52-L66 in terms of purpose, and a duplicate of index.ts#L72-L87 in terms of coding. I kept index.ts#L52-L66 because it seemed like it has some different purposes.
I'm not sure what's the point of uploading JSON if we're gonna upload the HTML files.
I observed that the functions specified in here are executed twice. I don't know if that's the intended behaviour.
Anyway, I'm not sure that if I made any mistakes but I'm sure that you'll be able to detect and fix my mistakes. :blush:

@danielcondemarin I did 1 and 2, although;
I added this function sort of a duplicate of index.ts#L52-L66 in terms of purpose, and a duplicate of index.ts#L72-L87 in terms of coding. I kept index.ts#L52-L66 because it seemed like it has some different purposes.
I'm not sure what's the point of uploading JSON files if we're gonna upload the HTML files.
I observed that the functions specified in here are executed twice. I don't know if that's the intended behaviour.
Anyway, I'm not sure that if I made any mistakes but I'm sure that you'll be able to detect and fix my mistakes. 😊

Cheers @mertyildiran . I'll take a look tomorrow!

@danielcondemarin OK, I've added a test.

I tried to redeploy using this PR but CloudFront uses the old cache somehow and pages suppose to be updated are not updating.

OK, I think people will have to use serverless-cloudfront-invalidate package to invalidate the cache if they want to invalidate. So I see now that's not an issue of this PR.

There is a PR that will allow configuring the cache behaviour TTLs etc > #282

Great!

We have to be careful about this, since serverless-next apps are replicated across the globe, we can only cleanup old builds once Cloudfront has fully propagated the changes, so it may not be as easy as it seems. I think is better to handle that on a separate issue / PR.

Cached pages do not come from S3, I've tested that just a moment ago by deleting all of the old build folders. If the page is cached, it will be fetched directly from CloudFront CDN, otherwise AWS will pull it from S3. That's what I understand, I might be wrong. Sure we can discuss on another issue or PR.

Hey guys, absolutely awesome work on this by the way, I'm from a startup who's rewriting their e-commerce on next/react after a quick PoC on wordpress/woo(I feel very dirty) - we're pretty much a serverless house so this is very interesting, quick note don't add that cloudfront invalidate plugin just call createInvalidation from the AWS/js cloudfront sdk since you've got creds already to do it!
By the way we'll have a about 4000 items this week that will need staticPaths/props implemented so I can try and give this a whirl on our staging env if it helps?

@danielcondemarin I did 1 and 2, although;
I added this function sort of a duplicate of index.ts#L52-L66 in terms of purpose, and a duplicate of index.ts#L72-L87 in terms of coding. I kept index.ts#L52-L66 because it seemed like it has some different purposes.

I can see why you'd be confused between this function and index.ts#L52-L66 as they both upload HTML Static Pages. However, the pages uploaded from the prerender-manifest.json are only those that use getStaticProps and there is an associated JSON props file,  whereas the other ones are what Next.js pre-rendered before getStaticProps existed.

I'm not sure what's the point of uploading JSON files if we're gonna upload the HTML files.

The JSON files are for client side transitions. Click a next  that links to a page using getStaticProps and you'll see Next.js requesting the json file: GET _next/data/build-id/foo.json

I observed that the functions specified in here are executed twice. I don't know if that's the intended behaviour.

Do you mean HTML pages uploaded in 2 places? If that's it, that's intended as I explained above.

Anyway, I'm not sure that if I made any mistakes but I'm sure that you'll be able to detect and fix my mistakes

I just had to fix the path to the HTML pages to put them in the S3 bucket static-pages/ directory and add support for the prerender-manifest to the Lambda@Edge default handler.
I've done some testing of my own using getStaticPaths & getStaticProps with fallback: false and seems to work as expected! Do you mind doing some testing of your own?, as you have quite a large number of static pages to test with :)

@danielcondemarin OK, I've added a test.

I tried to redeploy using this PR but CloudFront uses the old cache somehow and pages suppose to be updated are not updating.

OK, I think people will have to use serverless-cloudfront-invalidate package to invalidate the cache if they want to invalidate. So I see now that's not an issue of this PR.

There is a PR that will allow configuring the cache behaviour TTLs etc > #282

Great!

We have to be careful about this, since serverless-next apps are replicated across the globe, we can only cleanup old builds once Cloudfront has fully propagated the changes, so it may not be as easy as it seems. I think is better to handle that on a separate issue / PR.

Cached pages do not come from S3, I've tested that just a moment ago by deleting all of the old build folders. If the page is cached, it will be fetched directly from CloudFront CDN, otherwise AWS will pull it from S3. That's what I understand, I might be wrong. Sure we can discuss on another issue or PR.

Hey guys, absolutely awesome work on this by the way, I'm from a startup who's rewriting their e-commerce on next/react after a quick PoC on wordpress/woo(I feel very dirty) - we're pretty much a serverless house so this is very interesting, quick note don't add that cloudfront invalidate plugin just call createInvalidation from the AWS/js cloudfront sdk since you've got creds already to do it!
By the way we'll have a about 4000 items this week that will need staticPaths/props implemented so I can try and give this a whirl on our staging env if it helps?

@marcfielding1 Please do test it! That would be much appreciated.  Bear in mind that this PR only works for getStaticPaths using fallback: false though 🙂

@danielcondemarin is there a way to skip next build on local machine?
I think next build does not scale for huge amount of pages. Instead maybe we can directly push the code into AWS Lambda and triger the build with, for example Scrapy SitemapSpider or a Node.js script that traverses the URLs in sitemap. Therefore we solely rely on the CloudFront caching and get rid of the build time. I mean, I realized that we should make AWS Lambda to do the build work, not our local machines. I think you describe a similar workflow with the schema in this comment of yours, am I right?
I opened this PR to implement your:

All JSON files for a given build can be found in .next/prerender-manifest.json.
serverless-next.js will lookup the files and upload them to S3 so they can be fetch-ed from the browser.

description in here. But now, I think we should follow a different strategy to reduce the build and/or upload time. Hence, this PR might become irrelevant.

@danielcondemarin is there a way to skip next build on local machine?
I think next build does not scale for huge amount of pages. Instead maybe we can directly push the code into AWS Lambda and triger the build with, for example Scrapy SitemapSpider or a Node.js script that traverses the URLs in sitemap. Therefore we solely rely on the CloudFront caching and get rid of the build time. I mean, I realized that we should make AWS Lambda to do the build work, not our local machines. I think you describe a similar workflow with the schema in this comment of yours, am I right?
I opened this PR to implement your:

All JSON files for a given build can be found in .next/prerender-manifest.json.

serverless-next.js will lookup the files and upload them to S3 so they can be fetch-ed from the browser.
description in here. But now, I think we should follow a different strategy to reduce the build and/or upload time. Hence, this PR might become irrelevant.

@mertyildiran You should be able to skip the build locally by using build: false. All the available inputs are here.
Also, the problem you are describing as to having a large number of pages and build scalability issues is what getStaticPaths in combination with fallback: true were designed for. Basically Next.js renders a fallback page whilst in the background the static page is compiled, so the build is brought to Lambda. You are right, my architecture proposal implements that and also the more simple case fallback: false.
I don’t think this PR would be irrelevant though, it’s a good step closer to supporting the more complex workflow.

@danielcondemarin yeah I remembered build: false after I post the comment then edited my comment later on :point_up:
I will adjust my workflow according to build: false and sitemap crawling, let's see how much it will reduce the deployment time.

@mertyildiran If you don't have any objections I'm planning on getting this PR merged.
A separate one can be created for the fallback: true workflow.

@danielcondemarin sure, feel free to anything with this PR.

@danielcondemarin sure, feel free to do anything with this PR.

Thanks. Out of interest did you manage to test it using build: false?

@danielcondemarin what I'm looking for was actually Incremental Static Regeneration which is not implemented yet. So build: false does not a solution in my case.

@danielcondemarin what I'm looking for was actually Incremental Static Regeneration which is not implemented yet. So build: false is not a solution in my case.

Makes sense. Let me know if you would like to collaborate on supporting that. More than happy to work on it with you.


text:
Server will accept any websocket connection on the correct port

The server should refuse connections that do not connect with a name specified in the url parameters.

Server will now refuse connections without name parameter.

repo: danieldupriest/beachat


text:
[PATCHED] VAC is unable to communicate error

As title..
VAC-Bypass + Osiris
Disconnected on 3rd round, keeps disconnecting on retry..
Keeps disconnecting on restart + retry + no inject..
Used [start C:\Program Files (x86)\Steam\bin\SteamService.exe /repair] + restart
Reconnected successfully with no inject..
Match end followed by 20 mins cooldown
WIN11, Build x86, SDK 10.0.22621.0, platform v143, Microsoft Visual Studio 2022 v17.2.4, Latest repositories SRC
https://help.steampowered.com/en/faqs/view/22C0-03D0-AE4B-04E8

verify game files and play a round without vac bypass/ cheats in (casual) exit csgo and launch vac bypass then inject

repo: danielkrupinski/VAC-Bypass


text:
Query - Get Available Storage Location

[ ] Handler
[ ] Endpoint
[ ] Tests

No need to do this.  Will simply have one command to allocate storage instead

repo: danielmackay/dotnet-modular-monolith


text:
React Capstone group project

https://github.com/danielsafari143/space-x/projects/1
We are 2 partners in my team

Invalid ❌
Hi @mosidrum and @danielsafari143
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Your Code Review Request is marked as invalid for this reason:

[ ] Please add the correct project link this one.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request Does not count into the code reviews limit.

This is the link to the project
https://github.com/danielsafari143/space-x/projects/1

Changes Required ♻
Hi @,
Nice job, you are almost there.

(Changes Required) Aspects to improve: ♻

[ ] The number of kanban cards for two people is suppose to be 17 cards, not 15 as you did, Please add the 2 missed cards.

[ ] All issues suppose to be active until you implement them and then you close them, I can see that you're already closed one of the issues you have please reopen it again.

[Optional] suggestions:

[ ] It would be better professionally if you make the in Progress column before the in review column.

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear, and please remember to tag me in your question so I can receive the notification**
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi @mosidrum and @danielsafari143
After you ask for a review to your project,
Kindly don't push any changes until you get the review from the code reviewer.
Have a great day 😊

https://github.com/danielsafari143/space-x/projects/1
We are 2 partners in my team

Hi Team,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

good job following the instructions of the previous CR.

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

authors: Omar-Muhamad mikethreels mosidrum


text:
Add support for Webpack

Trying to import in app.js like this:
import ngAudio from 'ng-audio';
gives error: "Module not found: Error: Cannot resolve module 'ng-audio'".

I'd be happy to look at a PR that resolves this

authors: danielstern vinjegaard

repo: danielstern/ngAudio


text:
Can't pair/add devices properly anymore

Hey!
For some reason I can't properly pair/add anything anymore, despite it working pretty flawlessly the past few months. I mostly use aqara motion and temp sensors, as well as some ikea tradfri spotlights, all of these have worked great, up until now when I noticed that one motion sensor wasn't updating so I decided to repair it, and all hell broke lose.
I keep getting the message
Device with modelID 'undefined' is not supported.
after I get the "device connected" etc, it just becomes a "unknown" device when restarting the addon. It doesn't properly pair it, even if it's literally next to the coordinator.
What I tried doing to troubleshoot was:
Tried basic restart of the addon/reset stick, plug stick in plug out and then restart etc, but it keeps giving same messages. I also removed the device with the mqtt command, removed it from database, but still same issues upon re-pairing.
I then went the complete remove/reset route:

Remove devices/entities in hassio entity registry (even removed mqtt broker setup altogether after removing in entity registry) to get a clean slate, all traces of all my zigbee2mqtt devices were gone in hassio when fully rebooting the system.
uninstalled addon as well and entirely deleted all traces off it like the folders etc, then re-installed it, and I tried with both regular and dev versions.

Running latest hassio as well.
But it keeps giving the same results, I get the "device connected" message with its device id number but it then spams with the Device with modelID 'undefined' is not supported. messages, even when just pairing one simple device such as the aqara motion sensor, a aqara temperature sensor, or a cc2531 router. I never had this issue before, after several pairings/re/pairings.
I don't know what to do or try now anymore, any suggestions/tips?
Thanks in advance!

Well I went as far as reinstalling my entire hassos from scratch, and only adding zigbee2mqtt, starting simple with adding one device, and still same thing, devices gets "added/connected" quickly but not fully, the neverending Device with modelID 'undefined' is not supported keeps spaming the log. Don't know what else I can do now :/

Can you try reflashing the original coordinator stick?

I'd try that next time there is a need to redo stuff, all the troubleshooting took pretty much entire day, and re pairing everything is a bit tedious, so I'd rather not touch anything for now since it's working :)
It was just weird since the original stick was flashed with the same firmware and had worked so well this far.

I've the same problem only with Ikea Tradfri lamps, any other devices work.
Solution?
I don't have the possibility of reflash the firmware...

authors: FrankZZ ilsalgo lv-88


text:
Converting Scale.notes results to midi values

I can't seem to figure out how to convert the results from Scale.notes('Bb lydian') to MIDI values.
The results from Scale.notes('Bb lydian') are in the form ["Bb", "C", "D" ...]. There's no pitch data . This is causing an issue because I need the MIDI values of this scale. midi(...) doesn't seem to work unless there's a pitch associated with the note.
I have also tried toNote from tonal-abc-notation but the following fails: toNote("Bb"). It returns null for the flat notes. Not sure if that's a bug or intended.
Is there an easier way to get the scale values as midi number as opposed to ABC strings?

Yes, the problem is that you are using pitch classes (notes without octaves).
You should write (notice the 4 after the note name):
Scale.notes("Bb4 lydian").map(Note.midi)

Hope it helps. Feel free to reopen if needed.

authors: JamesJefferyUK danigb

repo: danigb/tonal


text:
Docker image fails to build

[*snip*]
Step 7/9 : RUN poetry install
 ---> Running in 152d259ac155
Skipping virtualenv creation, as specified in config file.
Installing dependencies from lock file

Because borg-exporter depends on pytest-celery (^0.0.0-alpha.1) which doesn't match any versions, version solving failed.
The command '/bin/sh -c poetry install' returned a non-zero code: 1

With the following modifications I was able to get it to build and run:

Amend Dockerfile to run instead poetry install --only main to skip dev dependencies that are causing the issue
poetry add pyinstaller^4.0 # it's only added as a dev dependency, which isn't strictly true
poetry add py # generated dist depends on it

repo: danihodovic/borg-exporter


text:
Too many error logs

Hi,
Is it possible to add a function or flag to disable error logs? I am caching multiple videos and some videos are not available to download and that's fine, but our Logs are getting overflown with your proxy cache error logs.
Example: (This is just for 1 video that throws an error)

E/ProxyCache: Error fetching info from MY_URL java.io.FileNotFoundException: MY_URL
                                                                 at com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:210)
                                                                 at com.danikula.videocache.HttpUrlSource.fetchContentInfo(HttpUrlSource.java:111)
                                                                 at com.danikula.videocache.HttpUrlSource.length(HttpUrlSource.java:53)
                                                                 at com.danikula.videocache.HttpProxyCache.newResponseHeaders(HttpProxyCache.java:61)
                                                                 at com.danikula.videocache.HttpProxyCache.processRequest(HttpProxyCache.java:39)
                                                                 at com.danikula.videocache.HttpProxyCacheServerClients.processRequest(HttpProxyCacheServerClients.java:42)
                                                                 at com.danikula.videocache.HttpProxyCacheServer.processSocket(HttpProxyCacheServer.java:221)
                                                                 at com.danikula.videocache.HttpProxyCacheServer.access$300(HttpProxyCacheServer.java:55)
                                                                 at com.danikula.videocache.HttpProxyCacheServer$SocketProcessorRunnable.run(HttpProxyCacheServer.java:331)
                                                                 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
                                                                 at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                                 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
                                                                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
                                                                 at java.lang.Thread.run(Thread.java:818)

E/ProxyCache: ProxyCache error
                                                             com.danikula.videocache.ProxyCacheException: Error opening connection for MY_URL with offset 0
                                                                 at com.danikula.videocache.HttpUrlSource.open(HttpUrlSource.java:66)
                                                                 at com.danikula.videocache.ProxyCache.readSource(ProxyCache.java:122)
                                                                 at com.danikula.videocache.ProxyCache.access$100(ProxyCache.java:19)
                                                                 at com.danikula.videocache.ProxyCache$SourceReaderRunnable.run(ProxyCache.java:179)
                                                                 at java.lang.Thread.run(Thread.java:818)
                                                              Caused by: java.io.FileNotFoundException: MY_URL
                                                                 at com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:210)
                                                                 at com.danikula.videocache.HttpUrlSource.open(HttpUrlSource.java:63)
                                                                 at com.danikula.videocache.ProxyCache.readSource(ProxyCache.java:122)
                                                                 at com.danikula.videocache.ProxyCache.access$100(ProxyCache.java:19)
                                                                 at com.danikula.videocache.ProxyCache$SourceReaderRunnable.run(ProxyCache.java:179)
                                                                 at java.lang.Thread.run(Thread.java:818)

E/ProxyCache: HttpProxyCacheServer error
                                                             com.danikula.videocache.ProxyCacheException: Error processing request
                                                                 at com.danikula.videocache.HttpProxyCacheServer.processSocket(HttpProxyCacheServer.java:228)
                                                                 at com.danikula.videocache.HttpProxyCacheServer.access$300(HttpProxyCacheServer.java:55)
                                                                 at com.danikula.videocache.HttpProxyCacheServer$SocketProcessorRunnable.run(HttpProxyCacheServer.java:331)
                                                                 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
                                                                 at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                                 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
                                                                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
                                                                 at java.lang.Thread.run(Thread.java:818)
                                                              Caused by: com.danikula.videocache.ProxyCacheException: Error reading source 1 times
                                                                 at com.danikula.videocache.ProxyCache.checkReadSourceErrorsCount(ProxyCache.java:58)
                                                                 at com.danikula.videocache.ProxyCache.read(ProxyCache.java:44)
                                                                 at com.danikula.videocache.HttpProxyCache.responseWithCache(HttpProxyCache.java:78)
                                                                 at com.danikula.videocache.HttpProxyCache.processRequest(HttpProxyCache.java:44)
                                                                 at com.danikula.videocache.HttpProxyCacheServerClients.processRequest(HttpProxyCacheServerClients.java:42)
                                                                 at com.danikula.videocache.HttpProxyCacheServer.processSocket(HttpProxyCacheServer.java:221)
                                                                 at com.danikula.videocache.HttpProxyCacheServer.access$300(HttpProxyCacheServer.java:55)
                                                                 at com.danikula.videocache.HttpProxyCacheServer$SocketProcessorRunnable.run(HttpProxyCacheServer.java:331)
                                                                 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
                                                                 at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                                 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
                                                                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
                                                                 at java.lang.Thread.run(Thread.java:818)

Well I think it is important to log any problem. AndroidVideoCache uses slf4j for logging, so you can try to play with it. For example you can set you custom slf4j logger to mute any library's log output.
From my side I won't do anything.

authors: danikula ebomb

repo: danikula/AndroidVideoCache


text:
Hotfix/MacOS install docs

Reformatted the MacOS Install documentation to improve document structure and order of instruction to be more intuitive for the dependencies order. Enhanced using ## instead of ** to segment different sections.

DO NOT MERGE yet, we are looking for potential changes to the MacOS install documentation.

not sure if this is now addressed in #345? if not there might be a conflict, could be good to get any extra bits here onto the other one

Going to close this for now, any additions should be made to the latest instructions

authors: ClaraLeigh danny-avila ocontant

repo: danny-avila/chatgpt-clone


text:
Indrag brugerne

Features skulle gerne være styret af hvad forbrugerne ønsker.
Så der skal laves en form for "feature request"-feature samt en "Rapporter en fejl"
Der findes sikkert externe systemer, som kan bruges til at indsamle denne slags data.

https://nembadminton.voteboards.com/board
Er implementeret

repo: dansk-badminton-tech/nembadminton