[SPARK-20727] Skip tests that use Hadoop utils on CRAN Windows

What changes were proposed in this pull request?
This change skips tests that use the Hadoop libraries while running
on CRAN check with Windows as the operating system. This is to handle
cases where the Hadoop winutils binaries are missing on the target
system. The skipped tests consist of

Tests that save, load a model in MLlib
Tests that save, load CSV, JSON and Parquet files in SQL
Hive tests

How was this patch tested?
Tested by running on a local windows VM with HADOOP_HOME unset. Also testing with https://win-builder.r-project.org

Test build #76876 has started for PR 17966 at commit 40273ab.

cc @felixcheung
FWIW it might easier to view the diff by adding w=1 to the URL. i.e. https://github.com/apache/spark/pull/17966/files?w=1

This doesn't seem to really have anything to do with the errors in SPARK-20666. As I pointed out, they do not only happen on Windows.

Sorry @vanzin  I got the wrong JIRA number. Fixing it now

This is SPARK-20727 - I just happened to have the other JIRA also open and pasted it incorrectly

Test build #76876 has finished for PR 17966 at commit 40273ab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76876/
Test PASSed.

Actually thinking more about this, I think we should be checking for availability of hadoop library / binaries rather than is_cran. For example I just found that win-builder only runs R CMD check (no --as-cran) and so this PR doesn't actually help on that machine.

@HyukjinKwon Do we know why things sometime queue for a long time on AppVeyor ? Like this PR has been queued for around 5 hours right now.

Thank you for cc'ing me. I think primarily it is because single AppVeyor account is shared across several Apache projects but the number of concurrent jobs is single up to my knowledge. So, it is a kind of a global queue.
I am monitoring ...
https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark
https://ci.appveyor.com/project/ApacheSoftwareFoundation/reef
https://ci.appveyor.com/project/ApacheSoftwareFoundation/nifi
https://ci.appveyor.com/project/ApacheSoftwareFoundation/thrift
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow
https://ci.appveyor.com/project/ApacheSoftwareFoundation/syncope

Just FYI, closing and opening a PR is a workaround to re-trigger the build in AppVeyor as (I assume) we all don't currently have the permission via AppVeyor Web UI.

Probably - but how to check for Hadoop? See if HADOOP_HOME is set?
We don't need to set that on *nix though, I think

So I'd propose this
is_cran <- function() { !identical(Sys.getenv("NOT_CRAN"), "true") }
is_windows <- function() { .Platform$OS.type == "windows" }
hadoop_home_set <- function() { !identical(Sys.getenv("HADOOP_HOME"), "") }

not_cran_or_windows_with_hadoop <- function() { !is_cran() && (!is_windows() || hadoop_home_set()) }

@shivaram have you got a chance to work on this again?

Sorry I've been out traveling -- I'll try to update this by tonight

@felixcheung I made the change - I'm right now going to test this in my Windows VM. Will update this PR with the results

Test build #77114 has started for PR 17966 at commit 7555501.

Test build #77114 has finished for PR 17966 at commit 7555501.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77114/
Test PASSed.

@felixcheung Unfortunately I'm out traveling and haven't been able to do the windows tests yet -- Would you have a chance to do that ? Also what are your thoughts on merging this while we test given the upcoming RC cut ?

testing now - could you submit to https://win-builder.r-project.org?

merged to master/2.2
I think we should still check win-builder. Also it's a bit hard to tell if the skipped tests are skipped - might want to follow up with a trace

Thanks I'll try to kick off the winbuilder build soon (i'm out of town till tomorrow). One more thing we might need to fix is that winbuilder has a 10 or 20 minute time limit for tests (not sure if the CRAN check has a similar limit ?)


Missing LICENSE

Hey there, this repo is missing a license, so it's not free to modify or edit by default. Can we please get clarification on the licensing for this repo? Cheers!

Sure!


Update install-the-tools.md

MS author clean-up

Docs Build status updates of commit 1cb6dd4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 2f217b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


AboutUs-page

As a user, I should be able to see description about the website.
As a user, I should be able to press a back button to go back to the previous page.

Acceptance criteria:

[ ] title
[ ] description
[ ]  back button

back button calls /dashboard

Copy has been noted in #32


promu exits with 0 for bad config

See: https://circleci.com/gh/prometheus/prometheus/8181
Using config file: /home/circleci/.go_workspace/src/github.com/prometheus/prometheus/.promu.yml
/!\ unknown/unhandled platforms: [linux/s390x]
github.com/prometheus/promu/cmd.runCrossbuild
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/cmd/crossbuild.go:128
github.com/prometheus/promu/cmd.glob..func5
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/cmd/crossbuild.go:62
github.com/prometheus/promu/vendor/github.com/spf13/cobra.(*Command).execute
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/vendor/github.com/spf13/cobra/command.go:653
github.com/prometheus/promu/vendor/github.com/spf13/cobra.(*Command).ExecuteC
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/vendor/github.com/spf13/cobra/command.go:728
github.com/prometheus/promu/vendor/github.com/spf13/cobra.(*Command).Execute
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/vendor/github.com/spf13/cobra/command.go:687
github.com/prometheus/promu/cmd.Execute
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/cmd/promu.go:64
main.main
	/home/circleci/.go_workspace/src/github.com/prometheus/promu/main.go:20
runtime.main
	/usr/local/go/src/runtime/proc.go:185
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:2337\n> running the base builder docker image
 +  docker run --rm -t -v /home/circleci/.go_workspace/src/github.com/prometheus/prometheus:/app quay.io/prometheus/golang-builder:1.10-base -i github.com/prometheus/prometheus -p linux/amd64 linux/386 darwin/amd64 darwin/386 windows/amd64 windows/386 freebsd/amd64 freebsd/386 openbsd/amd64 openbsd/386 netbsd/amd64 netbsd/386 dragonfly/amd64 linux/armv5 linux/armv6 linux/armv7 linux/arm64 freebsd/armv6 freebsd/armv7 netbsd/armv6 netbsd/armv7 linux/ppc64 linux/ppc64le

This refers to this PR: prometheus/prometheus#4605 where build succeeded even with bad config.

It exits with a code 0 because it's a warning, not a error.

@gouthamve Is this still a problem?


[Feature] How to use awq with my own dataset

Motivation
I want to use the awq with my own dataset to reduce the loss from quantization. Can anyone teach me how to organize the format of the local data?  Is there any documentation or tutorial for this?
Related resources
No response
Additional context
The format of my own dataset is a typical chat message like:
[
{"role": "system", "content": "You are an assistant."},
{"role": "user", "content": "Who you are?"},
{"role": "assistant", "content": "I am a language model ..."}
]
The goal is to make the quantized model as close as possible to the assistant's content.

It is get_calib_loaders that you should modify to take advantage of your own dataset.
Another direct way is just replace the data tensor with your own. Ref to https://github.com/InternLM/lmdeploy/blob/8b9f6abcaaa85e1f128e683079a39e7665d5940d/lmdeploy/lite/apis/calibrate.py#L245

Thank you very much for your kind help. It works for me.


Add JET

Thanks, looks good. Can you change the file extension to .yaml? Otherwise the file does not get detected and won't be rendered in the Readme.


crash when i use bows with the backhand/offhand

heres my crash report, log and config i used
crash-2023-03-21_02.59.29-client.txt
backhand.txt
fml-client-latest.log
latest.log

Fixed! Thanks for the report. https://streamable.com/3wzzdp


[atlmfc] Build error

Package: atlmfc:x86-windows -> 0#2
Host Environment

Host: x64-windows
Compiler: MSVC 19.24.28314.0
vcpkg-tool version: 2023-06-22-f19f3d9939100085fe2f7e41502d60b08e2083b6
vcpkg-scripts version: 4a3c366f2 2023-06-30 (26 hours ago)

To Reproduce
vcpkg install llvm opencv4[contrib,nonfree]
Failure logs
CMake Error at ports/atlmfc/portfile.cmake:7 (message):
  Unable to locate 'afxres.h'.  Ensure you have installed the ATL/MFC
  component of Visual Studio.
Call Stack (most recent call first):
  scripts/ports.cmake:147 (include)

Additional context

Ensure you have installed the ATL/MFC
component of Visual Studio.

Didn't this help?

@AymanAliH1 Please install ATL/MFC component of Visual Studio first.
If this doesn't solve your problem, please use this command: .\vcpkg.exe install atlmfc:x64-windows --debug and send the complete log to us.

We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!


Set temperature 2°C lower in my car.

I’m in Canada
I have a 2021 Kona Electric
When I start climate, temperature set in the car is 2°C lower.
Temperature shown in HA is same what I’ve set in with start climate. But when I go in my car, it’s 2 lower.
When using the Bluelink app, it’s set properly in my car.
i set it 2 higher in HA and it’s set at my desired temperature.

I will do another test on my car, assuming it works for me this means the temp range is different on the Hyundai car's vs Kia.  It should be a quick fix.  Thanks for raising it.

Hi.. first off.. thanks so much for your hard work on this.. I have been using it for awhile now and love the ability to finally start my car.. lol.. I also created a node-red to check for locked then following that command start the vehicle.. works awesome..
The reason I jumped in here is I am also in Canada with a Kia Seltos 2021 and when I start_climate with temperature it always sets the temp in the car to 22.5 .. I have tried to start with service set to 24 and 24.5 and 24.0 still always sets it to 22.5 ... Heated steering wheel works fine and front/rear defrost all seem to work fine.. I will try and grab the log and drop it here..

Hoping to grab time with my wife's car to test this out.  If I can replicate it will be a quick fix. Could I confirm what version you are running?

1.2.5 .. I just updated before testing this evening..
On Fri., Dec. 24, 2021, 9:32 p.m. cdnninja, @.***>
wrote:

Hoping to grab time with my wife's car to test this out. If I can
replicate it will be a quick fix. Could I confirm what version you are
running?
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1000961168,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RVHYBNT44FXT32AUTTUSUUKTANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

@cdnninja
As soon as you release something on the master branch, I’lol test it 😉

I tested it out.  In my single test using the default values in home assistant my car started but 0.5C off.  I have found a potential bug in the math that impacts 22C only.  Have you tried other temps to see if this impacts multiple temps?  If it is multiple I may need you to capture details from a web browser to see what Kia / Hyundai is passing to start the car.  This could be an electric car issue, I have an ICE.

@cdnninja
it's happening with multiple temperature for me.
I usually use 19.5 in Bluelink app. If I try with the same temperature in HA, it will set to 17.5 in the car. I actually do not see it in the car at this temperature (the screen is off), but next time I turn on my car, temperature is at 17.5.
After finding out about the 2°C difference, I set it to 21.5. and I've got 19.5 in my car.

Could you start the car via your webbrowser with correct settings? Ideally as close to HA defaults as possible while doing this:
https://github.com/fuatakgun/kia_uvo/wiki/How-to-sniff-API-via-MS-Edge You are looking for a section that will look like:         payload = {
"hvacInfo": {
"airCtrl": int(climate),
"defrost": defrost,
"heating1": int(heating),
"airTemp": {
"value": set_temp,
"unit": 0,
"hvacTempType": 1,
},
},
"pin": self.pin,

I can see my temperature when I look through the window when I start it and
mine is always 2 degrees lower..
On Sat, Dec 25, 2021 at 11:58 AM cdnninja @.***> wrote:

Could you start the car via your webbrowser with correct settings? Ideally
as close to HA defaults as possible while doing this:
https://github.com/fuatakgun/kia_uvo/wiki/How-to-sniff-API-via-MS-Edge
You are looking for a section that will look like: payload = {
"hvacInfo": {
"airCtrl": int(climate),
"defrost": defrost,
"heating1": int(heating),
"airTemp": {
"value": set_temp,
"unit": 0,
"hvacTempType": 1,
},
},
"pin": self.pin,
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001044938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RQWMF2U766QWWI3AF3USXZ3PANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

Actually a potentially easier way to check this.  In your app what range of options do you have for temp?  Our code is using 16-32 in 0.5 increments.  Do you see 14 as an option?

@cdnninja
in the app and on mybluelink.ca, I have 17-27 in 0.5 increments.

@cdnninja
when setting temp to 19.5 on mybluelink
hvacInfo: {airCtrl: 1, defrost: true, airTemp: {value: "0BH", unit: 0, hvacTempType: "1"}, heating1: 0}
airCtrl: 1
airTemp: {value: "0BH", unit: 0, hvacTempType: "1"}
hvacTempType: "1"
unit: 0
value: "0BH"
defrost: true
heating1: 0
pin: "XXXX"

So for my kia seltos there is a slider with "lo" at the min and "hi" at the
max.. in between I can set between 17.0-27.0 in .5 increments..
On Sat., Dec. 25, 2021, 12:06 p.m. cdnninja, @.***>
wrote:

Actually a potentially easier way to check this. In your app what range of
options do you have for temp? Our code is using 16-32 in 0.5 increments. Do
you see 14 as an option?
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001045692,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RVTRVJUCZKJYW6L263USX227ANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

Perfect that is exactly what I need.  It looks like your EV cars use the same range as what we found for EU EV which is different than Canadian ICE cars.   I will see if I can code something up quick before I head out.  If not this may be tonight or in a few days.

Sorry my car is a gas 2021 Kia Seltos .. not EV..
On Sat., Dec. 25, 2021, 12:44 p.m. cdnninja, @.***>
wrote:

Perfect that is exactly what I need. It looks like your EV cars use the
same range as what we found for EU EV which is different than Canadian ICE
cars. I will see if I can code something up quick before I head out. If not
this may be tonight or in a few days.
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001050372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RREHTTA2CXCLPQCRRDUSX7HNANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

#224 will solve this for an EV @zadigre could you replace your Canada API file with it to test?
@dallaby23 this means they have changed temperature ranges on cars, now we have to figure out which cars and how to detect this.  Mine is a 2019 Sorento ICE.  This could be a generation of the UVO system, or the year.

@cdnninja
is it available in Master branch directly?
FYI, Here’s the info for 17°C
hvacInfo: {airCtrl: 1, defrost: true, airTemp: {value: "06H", unit: 0, hvacTempType: 1}, heating1: 0}
And 27°C
hvacInfo: {airCtrl: 1, defrost: true, airTemp: {value: "1AH", unit: 0, hvacTempType: 1}, heating1: 0}

No it is under #224 so you will need to copy paste the one file.

@dallaby23 could you use the same sniff from above? I'm wondering if the temptype is the key. I have only seen that being different on an EV but if yours is 1 as well that may be it.

@cdnninja
looks like it's working as intended now with the new file. I tried my my 19.5 setting in HA... and car was set at 19.5.
I'll let you know if I encounter any other problem.

Could each of you also confirm on a start that the temp sensor displayed in home assistant is wrong?  Just want to confirm that. This only works while car is running otherwise will show a low number:

@cdnninja

so I guess the translation here is not done properly.

@cdnninja
and also when I set the temperature to 19.5 on mybluelink or Bluelink app, set temperature is also shown as 21.5

Out doing some Christmas stuff so might not be available till tomorrow..
On Sat., Dec. 25, 2021, 1:37 p.m. zadigre, @.***> wrote:

@cdnninja https://github.com/cdnninja
and also when I set the temperature to 19.5 on mybluelink or Bluelink app,
set temperature is also shown as 21.5
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001058890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RRZ5DVEVHNEXAWELCDUSYFODANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@cdnninja
and also when I set the temperature to 19.5 on mybluelink or Bluelink app, set temperature is also shown as 21.5 in HA

Yes I'll need to update that logic as well.  I'll wait to see if we can find out why your two cars are different than mine.

k.. quick test.. started 2021 Kia Seltos Canada.. car shows 21.. Set
Temperature in HA shows 23.. Air Temp value shows 0EH and unit is 0 .. Air
Temp unit is C ...
On Sat, Dec 25, 2021 at 2:17 PM cdnninja @.***> wrote:

@cdnninja https://github.com/cdnninja
and also when I set the temperature to 19.5 on mybluelink or Bluelink app,
set temperature is also shown as 21.5 in HA
Yes I'll need to update that logic as well. I'll wait to see if we can
find out why your two cars are different than mine.
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001063653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RXHKXWCC6YJOSDFBCDUSYKDBANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes the range is different for your car.  I am interested to see what the website sends and what hvacTempType is set to.

Basically the way it works is it send a hex number that is just the index of the temp from a list.   Your list seems to be 2 degree different than mine. Need to find a way to predict it so we can get it right for both cars. Could we also get the data for yours from the data element in home assistant?

@cdnninja
do you need anything else from me or we are all set for now?

@cdnninja
do you need anything else from me or we are all set for now?

Good for now. Thank you!  Hyundai and Kia we are finding are interesting. Very little consistency.

@zadigre  could I actually get the message that state "Get Vehicles Response " from your debug logs? Specifically looking to see what "genType" is.

@cdnninja
here's what I've got after starting climate :
2021-12-25 18:36:40 DEBUG (SyncWorker_4) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received Pin validation response <Response [200]>
2021-12-25 18:36:42 DEBUG (SyncWorker_4) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received start_climate_ev response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}}
2021-12-25 18:37:01 DEBUG (SyncWorker_1) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Last action_status: 200
2021-12-25 18:37:15 DEBUG (SyncWorker_0) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20211225233651', 'airCtrlOn': True, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '0BH', 'unit': 0}, 'defrost': True, 'acc': False, 'evStatus': {'batteryCharge': True, 'batteryStatus': 63, 'batteryPlugin': 2, 'remainTime2': {'etc1': {'value': 99, 'unit': 1}, 'etc2': {'value': 1400, 'unit': 1}, 'etc3': {'value': 300, 'unit': 1}, 'atc': {'value': 280, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 196.0, 'unit': 1}, 'totalAvailableRange': {'value': 196.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 1, 'sideBackWindowHeat': 1, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}
2021-12-25 18:37:18 DEBUG (SyncWorker_0) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 12920.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20211109', 'imatServiceOdometer': 24920.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20220509', 'currentOdometer': 17194.9, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}
2021-12-25 18:37:18 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - LastUpdated 2021-12-25 23:36:51+00:00 - Timezone UTC
2021-12-25 18:37:18 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Engine type set VEHICLE_ENGINE_TYPE.EV

The get vehicle response comes on first login or token renewal.

here's everything... not sure what you are looking for exactly.
2021-12-25 18:32:51 DEBUG (MainThread) [custom_components.kia_uvo] kia_uvo - async_setup_entry started - <homeassistant.config_entries.ConfigEntry object at 0x7f92aa7e00>
2021-12-25 18:32:51 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Received token into Vehicle Object {'valid_until': '2021-12-26 05:12:54.049911', 'access_token': 'eyJlbmMiOiJreVJMMEc2SEVPY1ZNdFl2a2pHdmRGRXN6RzJGemYySGw4eFJzYzRFelA3amlxcC80aXBNN0RueXFuRUVIYzhDdFJ2UkRGbXRZV0E1L3N2VjZzMHZYbnBUTnpMUlZjelZXbEVsemRZaDVZQ0g4WFI5RFpRL1FHT0YwZ0dVNURSMFU1OWtuNlB3S3gvYUtSVEVlYXFvOXhxSEppMllaY0E5Z0g4V0QyeWk1OS9uakF5Tm51Q1RHL3NlQnlRSEFHWXBabFFzZEQrL2JiWFhiR0ZiSnpVc1ZoZG5IMWZJcXRpTEJoNzhHVWNQYUxYRGVNUjE2M1RBbm9FdTFuaHJhNFNGeTU4bnZoMk5zRnpTZWx4bzZ4TGFoZEVvUU1QcW9lUFM5a1FXTTg1dGY3dUZITjliZGNVVHpOWWMwTjRZZEtYUmZwY2hZNTlqbzEyaFg2UHYraDVQSzZSc055dlhvVDkyQWxKK1U5ZGo3aGt1aU1tVDcycSs4dlNheGl3U1Y0VUd6NndJR0lpWU5XUGdGSlQzaURTang3M3BySXRxNi9jUlA0RFJ5UUQzK2oxazZaakw5R04zby9TdmJ1ZEZZRDJKR0pKN2ZjNW1NZXFLMG56SWlPbmtGdzlBREt6RGNoeTJoQlpFUWJkc2x0V0RZLzRzZ0JDTjF5M3Z3ZmxrdzFsYitsWlBIZXhYa1B3MmpwTnc1V0ZIN0pJSW1yRFFLUmRVR0tLTWUvN1Vsd3ZrbjljNTZaeEx0VEk0L0piMUFtTkNnMUVmUktIN2xIS0hwTUFpSG53SmxQWVZHYjAvQzl3ek1ML0t0R3YrQTZZWHgyRzNuQVp1d0tybm9DQkpQNmZzblZpS3ZEYnRuaW05ZCthT3d5QkM0TmU2K1g2NUhMbXRwN2NKME5BaC8xUEVQMnkxd3lDUWFodHR3TXU0R3QvMkllMjhnOHNTbXM0Rkp3RElqTkpwalJoUWJZQUJhOW9kRXlwcEc2MmI4U0tFNXNYdzJOdU1ncHEwWTFHbXovcnUzUVg5Q2x3R3NLR2xXWlNXdXdQU0J0UE9SQll2VjBZaE5kcGtsVVBBa09OVnZIQUo5cnY4R2RiaUMxemNjVCtPbVMxZjhMKzN4TythTUg3REYyeU9rTHdJY3dGdEJRMzlPTDhRWUZqZUNkdjhiMGtBcWFGZWpBWkdVTG5QU0ZVUjFrSXBrUm44YkRtbHptWFYvWm1TMHd6RVByY3NmZWNNUDd2cnk5ZkU2QVp1SGlFMlhDdmtkYTUwVHhxT2doMmU0NFg4UmVkWUtVamJ0YXphQXJueWtxYmJkTG9EbVRTWjQyWUp4TGVoRUNVVUlGdTZvNjE1Y01HQ2ZUUG1vK0hscjBON0ZtcWdyU3czWThZWHZ5Rjh3dmhzTU1iaFZ5MS9LTUJNVjViWVQ0Zz0iLCJrZXkiOiJKcDBPZ2RDRnp1L3pJWkdyR2g3dUliRVg4d2pidHJqeXVvcFUzVmIwejhJcjJDc0E3TTUycnBkZG9WT2haSUo0eC9xb1hxejFXdU91RzNWSEEreVV6QT09In0=', 'refresh_token': 'eyJlbmMiOiJKK3FwTnFEbnowYU9FNE4vcmJMZzgzN0NTcUhZMlR5Q0RROFVaY2lUdXpRYW95Rmg1VXhKck1ucjBQUjdjTXM1M0VoVnFJY0FLTVpDanJvVjg4UklJN2FWSVNpRUk3ZTJCVUpxRU5MWVV0OVN5Y0V5VWptc3FKTDg2NXNmNWlEeHpKTElHRXlsT1ZXakxwUkRUZFZwT3VSRkJwVEl6VzgwVXlOMVpEMVZiSVFETWx2QW5KVHIzUlpXSVdZNk9HdUdVOUovcFRSRG53b2M5Q0pUMTJEdm1ENlFVYzBaR2tBMUlja3VsZUxrbDlXU1hlZjQrdzh6U2JoTGxoMUFyWi9CSldhNGRXOVRsTENvZk9nOXFGY0g1OWNCV2FUMXlJTTBiUlhnbmRMMlFOeFhQdnhlOVo2WkY0OUhPVk1BZmpxR3N5SjVhQ0MyblVWaXpCOXZFaUp4T2x3aVpId2pDYVZQTUJJcVROUEVHZkYrZXZuazM5ZFFtQWh3dWFLcElBdWNnY2xXNnN6M1REeUZmeVdRMXRJcG9ueERWdlo0K0d3RGdYdUlhM0hwWTFEWjhNanIwSXZzcmk3VWs4UmVnTFl1eFNpdmJWT0NkMUV2d0NGUzI1QkZyUHUvRWNlNHVEVzVHZy9Ta3BlWTVOc3YzVWo4UkFkYk50OFlXa1hnQklFSkxuSTV6OHFtMlN0NnZIbkpvdzdRNFpYRUUvazIwZDVrckRCUTgvNWw0bVo1KzJCRFpPakh3a1QrODNFeTIrU2pCQjR5OWxWMFZHeWtaQVZiQVZlL25mc0w4WENSeThFbGVoRmJ5Y0JUUElOaFlWTzVMTDVQbDFnTmZGZTYrVlZxVzVtazlzZVdSZ2VmT2FXdHhoVThKSHRhTUo2N3JQN0xBWUdvM2k5SHR0a1RYSGx0VURuY1F0SXJUQThRZjZJdnEybGtibXlUTlRkYlVqU1V5a3lJbFZmU1FhRW5FUkVsaUZ2N1lWUEdWdnhyeUpCMlB1RzdNbkhLc09IVjlSVnFpeFUvSllIbHErMWprbzRHdTJ3UlNzWTFvN2dZSVQ4c0tGYmp0NVkrUkdEQUZNaEZNVlhySHptVUx6Q3dKVm1kSVlwQXN2WEh1VFcyWkY5TFRSa01SRXBSZGlWQ2lBVzkvNFdLeGgvdE1hdjZETlJmbmd0aG1WS2VhYWlLSTRUMXJraWZqc2VGTkJSU3dMQllNQ1FGVGl0bjZ4M054QThDMmxHWTA2T3lSQ3FIVjRSRTFFdjVBb2t0MzlpWVZZbVB3UlZXU3UvSVUrWE5ubmdaUlVpT1duUUVFam5zYzlCNmt6L3QyNENFK3g2dHMxcHZEWXJOdmN6M3U1SmVCTG5EZWNwTVV0Vng3QWkwZ0pLdDlhdjhpUEFHeGoveTF1eWFBc3ZyTVc5T2U4MD0iLCJrZXkiOiJWRlhvdEZWUGhDUldLSUF6MFpJMnVDVlNoRjBjclltWCtiTzNQa0ZSbnU1OW9LenRlSEFoUXJXQXcxNkxZYVh3NjV6eU5tZndmK2w1KzJzRFFGS240dz09In0=', 'device_id': None, 'vehicle_name': 'Kona VÉ', 'vehicle_id': 'qLHNk/TY2fGJeLL1FVGDXA==', 'vehicle_regid': None, 'vehicle_model': 'Kona VÉ', 'vehicle_registration_date': 'missing', 'stamp': 'NoStamp'}
2021-12-25 18:32:51 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Refresh token started 2021-12-26 05:12:54.049911 2021-12-25 18:32:51.904872 False
2021-12-25 18:33:07 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20211225232342', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'acc': False, 'evStatus': {'batteryCharge': True, 'batteryStatus': 61, 'batteryPlugin': 2, 'remainTime2': {'etc1': {'value': 104, 'unit': 1}, 'etc2': {'value': 1470, 'unit': 1}, 'etc3': {'value': 320, 'unit': 1}, 'atc': {'value': 295, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 216.0, 'unit': 1}, 'totalAvailableRange': {'value': 216.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}
2021-12-25 18:33:10 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 12920.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20211109', 'imatServiceOdometer': 24920.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20220509', 'currentOdometer': 17194.9, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}
2021-12-25 18:33:13 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received Pin validation response <Response [200]>
2021-12-25 18:33:20 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Vehicle Location {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'head': 218, 'coord': {'lat': 45.579855, 'lon': -73.516379, 'alt': 10.04, 'type': 0}, 'accuracy': {'hdop': 0, 'pdop': 1}, 'time': '20211225233317', 'speed': {'value': 0, 'unit': 0}}}
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - LastUpdated 2021-12-25 23:23:42+00:00 - Timezone UTC
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Engine type set VEHICLE_ENGINE_TYPE.EV
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.1.targetSOClevel
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.0.targetSOClevel
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.1.dte.rangeByFuel.totalAvailableRange.value
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.0.dte.rangeByFuel.totalAvailableRange.value
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleLocation.geocodedLocation.display_name
2021-12-25 18:36:40 DEBUG (SyncWorker_4) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received Pin validation response <Response [200]>
2021-12-25 18:36:42 DEBUG (SyncWorker_4) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received start_climate_ev response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}}
2021-12-25 18:37:01 DEBUG (SyncWorker_1) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Last action_status: 200
2021-12-25 18:37:15 DEBUG (SyncWorker_0) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20211225233651', 'airCtrlOn': True, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '0BH', 'unit': 0}, 'defrost': True, 'acc': False, 'evStatus': {'batteryCharge': True, 'batteryStatus': 63, 'batteryPlugin': 2, 'remainTime2': {'etc1': {'value': 99, 'unit': 1}, 'etc2': {'value': 1400, 'unit': 1}, 'etc3': {'value': 300, 'unit': 1}, 'atc': {'value': 280, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 196.0, 'unit': 1}, 'totalAvailableRange': {'value': 196.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 1, 'sideBackWindowHeat': 1, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}
2021-12-25 18:37:18 DEBUG (SyncWorker_0) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 12920.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20211109', 'imatServiceOdometer': 24920.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20220509', 'currentOdometer': 17194.9, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}
2021-12-25 18:37:18 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - LastUpdated 2021-12-25 23:36:51+00:00 - Timezone UTC
2021-12-25 18:37:18 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Engine type set VEHICLE_ENGINE_TYPE.EV

Try restarting home assistance and try searching for the strings I mentioned earlier.

On Dec 25, 2021, at 4:46 PM, zadigre @.***> wrote:

here's everything... not sure what you are looking for exactly.
2021-12-25 18:32:51 DEBUG (MainThread) [custom_components.kia_uvo] kia_uvo - async_setup_entry started - <homeassistant.config_entries.ConfigEntry object at 0x7f92aa7e00>
2021-12-25 18:32:51 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Received token into Vehicle Object {'valid_until': '2021-12-26 05:12:54.049911', 'access_token': 'eyJlbmMiOiJreVJMMEc2SEVPY1ZNdFl2a2pHdmRGRXN6RzJGemYySGw4eFJzYzRFelA3amlxcC80aXBNN0RueXFuRUVIYzhDdFJ2UkRGbXRZV0E1L3N2VjZzMHZYbnBUTnpMUlZjelZXbEVsemRZaDVZQ0g4WFI5RFpRL1FHT0YwZ0dVNURSMFU1OWtuNlB3S3gvYUtSVEVlYXFvOXhxSEppMllaY0E5Z0g4V0QyeWk1OS9uakF5Tm51Q1RHL3NlQnlRSEFHWXBabFFzZEQrL2JiWFhiR0ZiSnpVc1ZoZG5IMWZJcXRpTEJoNzhHVWNQYUxYRGVNUjE2M1RBbm9FdTFuaHJhNFNGeTU4bnZoMk5zRnpTZWx4bzZ4TGFoZEVvUU1QcW9lUFM5a1FXTTg1dGY3dUZITjliZGNVVHpOWWMwTjRZZEtYUmZwY2hZNTlqbzEyaFg2UHYraDVQSzZSc055dlhvVDkyQWxKK1U5ZGo3aGt1aU1tVDcycSs4dlNheGl3U1Y0VUd6NndJR0lpWU5XUGdGSlQzaURTang3M3BySXRxNi9jUlA0RFJ5UUQzK2oxazZaakw5R04zby9TdmJ1ZEZZRDJKR0pKN2ZjNW1NZXFLMG56SWlPbmtGdzlBREt6RGNoeTJoQlpFUWJkc2x0V0RZLzRzZ0JDTjF5M3Z3ZmxrdzFsYitsWlBIZXhYa1B3MmpwTnc1V0ZIN0pJSW1yRFFLUmRVR0tLTWUvN1Vsd3ZrbjljNTZaeEx0VEk0L0piMUFtTkNnMUVmUktIN2xIS0hwTUFpSG53SmxQWVZHYjAvQzl3ek1ML0t0R3YrQTZZWHgyRzNuQVp1d0tybm9DQkpQNmZzblZpS3ZEYnRuaW05ZCthT3d5QkM0TmU2K1g2NUhMbXRwN2NKME5BaC8xUEVQMnkxd3lDUWFodHR3TXU0R3QvMkllMjhnOHNTbXM0Rkp3RElqTkpwalJoUWJZQUJhOW9kRXlwcEc2MmI4U0tFNXNYdzJOdU1ncHEwWTFHbXovcnUzUVg5Q2x3R3NLR2xXWlNXdXdQU0J0UE9SQll2VjBZaE5kcGtsVVBBa09OVnZIQUo5cnY4R2RiaUMxemNjVCtPbVMxZjhMKzN4TythTUg3REYyeU9rTHdJY3dGdEJRMzlPTDhRWUZqZUNkdjhiMGtBcWFGZWpBWkdVTG5QU0ZVUjFrSXBrUm44YkRtbHptWFYvWm1TMHd6RVByY3NmZWNNUDd2cnk5ZkU2QVp1SGlFMlhDdmtkYTUwVHhxT2doMmU0NFg4UmVkWUtVamJ0YXphQXJueWtxYmJkTG9EbVRTWjQyWUp4TGVoRUNVVUlGdTZvNjE1Y01HQ2ZUUG1vK0hscjBON0ZtcWdyU3czWThZWHZ5Rjh3dmhzTU1iaFZ5MS9LTUJNVjViWVQ0Zz0iLCJrZXkiOiJKcDBPZ2RDRnp1L3pJWkdyR2g3dUliRVg4d2pidHJqeXVvcFUzVmIwejhJcjJDc0E3TTUycnBkZG9WT2haSUo0eC9xb1hxejFXdU91RzNWSEEreVV6QT09In0=', 'refresh_token': 'eyJlbmMiOiJKK3FwTnFEbnowYU9FNE4vcmJMZzgzN0NTcUhZMlR5Q0RROFVaY2lUdXpRYW95Rmg1VXhKck1ucjBQUjdjTXM1M0VoVnFJY0FLTVpDanJvVjg4UklJN2FWSVNpRUk3ZTJCVUpxRU5MWVV0OVN5Y0V5VWptc3FKTDg2NXNmNWlEeHpKTElHRXlsT1ZXakxwUkRUZFZwT3VSRkJwVEl6VzgwVXlOMVpEMVZiSVFETWx2QW5KVHIzUlpXSVdZNk9HdUdVOUovcFRSRG53b2M5Q0pUMTJEdm1ENlFVYzBaR2tBMUlja3VsZUxrbDlXU1hlZjQrdzh6U2JoTGxoMUFyWi9CSldhNGRXOVRsTENvZk9nOXFGY0g1OWNCV2FUMXlJTTBiUlhnbmRMMlFOeFhQdnhlOVo2WkY0OUhPVk1BZmpxR3N5SjVhQ0MyblVWaXpCOXZFaUp4T2x3aVpId2pDYVZQTUJJcVROUEVHZkYrZXZuazM5ZFFtQWh3dWFLcElBdWNnY2xXNnN6M1REeUZmeVdRMXRJcG9ueERWdlo0K0d3RGdYdUlhM0hwWTFEWjhNanIwSXZzcmk3VWs4UmVnTFl1eFNpdmJWT0NkMUV2d0NGUzI1QkZyUHUvRWNlNHVEVzVHZy9Ta3BlWTVOc3YzVWo4UkFkYk50OFlXa1hnQklFSkxuSTV6OHFtMlN0NnZIbkpvdzdRNFpYRUUvazIwZDVrckRCUTgvNWw0bVo1KzJCRFpPakh3a1QrODNFeTIrU2pCQjR5OWxWMFZHeWtaQVZiQVZlL25mc0w4WENSeThFbGVoRmJ5Y0JUUElOaFlWTzVMTDVQbDFnTmZGZTYrVlZxVzVtazlzZVdSZ2VmT2FXdHhoVThKSHRhTUo2N3JQN0xBWUdvM2k5SHR0a1RYSGx0VURuY1F0SXJUQThRZjZJdnEybGtibXlUTlRkYlVqU1V5a3lJbFZmU1FhRW5FUkVsaUZ2N1lWUEdWdnhyeUpCMlB1RzdNbkhLc09IVjlSVnFpeFUvSllIbHErMWprbzRHdTJ3UlNzWTFvN2dZSVQ4c0tGYmp0NVkrUkdEQUZNaEZNVlhySHptVUx6Q3dKVm1kSVlwQXN2WEh1VFcyWkY5TFRSa01SRXBSZGlWQ2lBVzkvNFdLeGgvdE1hdjZETlJmbmd0aG1WS2VhYWlLSTRUMXJraWZqc2VGTkJSU3dMQllNQ1FGVGl0bjZ4M054QThDMmxHWTA2T3lSQ3FIVjRSRTFFdjVBb2t0MzlpWVZZbVB3UlZXU3UvSVUrWE5ubmdaUlVpT1duUUVFam5zYzlCNmt6L3QyNENFK3g2dHMxcHZEWXJOdmN6M3U1SmVCTG5EZWNwTVV0Vng3QWkwZ0pLdDlhdjhpUEFHeGoveTF1eWFBc3ZyTVc5T2U4MD0iLCJrZXkiOiJWRlhvdEZWUGhDUldLSUF6MFpJMnVDVlNoRjBjclltWCtiTzNQa0ZSbnU1OW9LenRlSEFoUXJXQXcxNkxZYVh3NjV6eU5tZndmK2w1KzJzRFFGS240dz09In0=', 'device_id': None, 'vehicle_name': 'Kona VÉ', 'vehicle_id': 'qLHNk/TY2fGJeLL1FVGDXA==', 'vehicle_regid': None, 'vehicle_model': 'Kona VÉ', 'vehicle_registration_date': 'missing', 'stamp': 'NoStamp'}
2021-12-25 18:32:51 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Refresh token started 2021-12-26 05:12:54.049911 2021-12-25 18:32:51.904872 False
2021-12-25 18:33:07 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20211225232342', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'acc': False, 'evStatus': {'batteryCharge': True, 'batteryStatus': 61, 'batteryPlugin': 2, 'remainTime2': {'etc1': {'value': 104, 'unit': 1}, 'etc2': {'value': 1470, 'unit': 1}, 'etc3': {'value': 320, 'unit': 1}, 'atc': {'value': 295, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 216.0, 'unit': 1}, 'totalAvailableRange': {'value': 216.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}
2021-12-25 18:33:10 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 12920.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20211109', 'imatServiceOdometer': 24920.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20220509', 'currentOdometer': 17194.9, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}
2021-12-25 18:33:13 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received Pin validation response <Response [200]>
2021-12-25 18:33:20 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Vehicle Location {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'head': 218, 'coord': {'lat': 45.579855, 'lon': -73.516379, 'alt': 10.04, 'type': 0}, 'accuracy': {'hdop': 0, 'pdop': 1}, 'time': '20211225233317', 'speed': {'value': 0, 'unit': 0}}}
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - LastUpdated 2021-12-25 23:23:42+00:00 - Timezone UTC
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Engine type set VEHICLE_ENGINE_TYPE.EV
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.1.targetSOClevel
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.0.targetSOClevel
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.1.dte.rangeByFuel.totalAvailableRange.value
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.0.dte.rangeByFuel.totalAvailableRange.value
2021-12-25 18:33:20 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleLocation.geocodedLocation.display_name
2021-12-25 18:36:40 DEBUG (SyncWorker_4) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received Pin validation response <Response [200]>
2021-12-25 18:36:42 DEBUG (SyncWorker_4) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received start_climate_ev response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}}
2021-12-25 18:37:01 DEBUG (SyncWorker_1) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Last action_status: 200
2021-12-25 18:37:15 DEBUG (SyncWorker_0) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20211225233651', 'airCtrlOn': True, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '0BH', 'unit': 0}, 'defrost': True, 'acc': False, 'evStatus': {'batteryCharge': True, 'batteryStatus': 63, 'batteryPlugin': 2, 'remainTime2': {'etc1': {'value': 99, 'unit': 1}, 'etc2': {'value': 1400, 'unit': 1}, 'etc3': {'value': 300, 'unit': 1}, 'atc': {'value': 280, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 196.0, 'unit': 1}, 'totalAvailableRange': {'value': 196.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 1, 'sideBackWindowHeat': 1, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}
2021-12-25 18:37:18 DEBUG (SyncWorker_0) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 12920.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20211109', 'imatServiceOdometer': 24920.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20220509', 'currentOdometer': 17194.9, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}
2021-12-25 18:37:18 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - LastUpdated 2021-12-25 23:36:51+00:00 - Timezone UTC
2021-12-25 18:37:18 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Engine type set VEHICLE_ENGINE_TYPE.EV
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

I don't see this specific string.
nothing different.
2021-12-25 21:14:12 DEBUG (MainThread) [custom_components.kia_uvo] kia_uvo - async_setup_entry started - <homeassistant.config_entries.ConfigEntry object at 0x7f9d38ee00>
2021-12-25 21:14:12 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Received token into Vehicle Object {'valid_until': '2021-12-26 05:12:54.049911', 'access_token': 'eyJlbmMiOiJreVJMMEc2SEVPY1ZNdFl2a2pHdmRGRXN6RzJGemYySGw4eFJzYzRFelA3amlxcC80aXBNN0RueXFuRUVIYzhDdFJ2UkRGbXRZV0E1L3N2VjZzMHZYbnBUTnpMUlZjelZXbEVsemRZaDVZQ0g4WFI5RFpRL1FHT0YwZ0dVNURSMFU1OWtuNlB3S3gvYUtSVEVlYXFvOXhxSEppMllaY0E5Z0g4V0QyeWk1OS9uakF5Tm51Q1RHL3NlQnlRSEFHWXBabFFzZEQrL2JiWFhiR0ZiSnpVc1ZoZG5IMWZJcXRpTEJoNzhHVWNQYUxYRGVNUjE2M1RBbm9FdTFuaHJhNFNGeTU4bnZoMk5zRnpTZWx4bzZ4TGFoZEVvUU1QcW9lUFM5a1FXTTg1dGY3dUZITjliZGNVVHpOWWMwTjRZZEtYUmZwY2hZNTlqbzEyaFg2UHYraDVQSzZSc055dlhvVDkyQWxKK1U5ZGo3aGt1aU1tVDcycSs4dlNheGl3U1Y0VUd6NndJR0lpWU5XUGdGSlQzaURTang3M3BySXRxNi9jUlA0RFJ5UUQzK2oxazZaakw5R04zby9TdmJ1ZEZZRDJKR0pKN2ZjNW1NZXFLMG56SWlPbmtGdzlBREt6RGNoeTJoQlpFUWJkc2x0V0RZLzRzZ0JDTjF5M3Z3ZmxrdzFsYitsWlBIZXhYa1B3MmpwTnc1V0ZIN0pJSW1yRFFLUmRVR0tLTWUvN1Vsd3ZrbjljNTZaeEx0VEk0L0piMUFtTkNnMUVmUktIN2xIS0hwTUFpSG53SmxQWVZHYjAvQzl3ek1ML0t0R3YrQTZZWHgyRzNuQVp1d0tybm9DQkpQNmZzblZpS3ZEYnRuaW05ZCthT3d5QkM0TmU2K1g2NUhMbXRwN2NKME5BaC8xUEVQMnkxd3lDUWFodHR3TXU0R3QvMkllMjhnOHNTbXM0Rkp3RElqTkpwalJoUWJZQUJhOW9kRXlwcEc2MmI4U0tFNXNYdzJOdU1ncHEwWTFHbXovcnUzUVg5Q2x3R3NLR2xXWlNXdXdQU0J0UE9SQll2VjBZaE5kcGtsVVBBa09OVnZIQUo5cnY4R2RiaUMxemNjVCtPbVMxZjhMKzN4TythTUg3REYyeU9rTHdJY3dGdEJRMzlPTDhRWUZqZUNkdjhiMGtBcWFGZWpBWkdVTG5QU0ZVUjFrSXBrUm44YkRtbHptWFYvWm1TMHd6RVByY3NmZWNNUDd2cnk5ZkU2QVp1SGlFMlhDdmtkYTUwVHhxT2doMmU0NFg4UmVkWUtVamJ0YXphQXJueWtxYmJkTG9EbVRTWjQyWUp4TGVoRUNVVUlGdTZvNjE1Y01HQ2ZUUG1vK0hscjBON0ZtcWdyU3czWThZWHZ5Rjh3dmhzTU1iaFZ5MS9LTUJNVjViWVQ0Zz0iLCJrZXkiOiJKcDBPZ2RDRnp1L3pJWkdyR2g3dUliRVg4d2pidHJqeXVvcFUzVmIwejhJcjJDc0E3TTUycnBkZG9WT2haSUo0eC9xb1hxejFXdU91RzNWSEEreVV6QT09In0=', 'refresh_token': 'eyJlbmMiOiJKK3FwTnFEbnowYU9FNE4vcmJMZzgzN0NTcUhZMlR5Q0RROFVaY2lUdXpRYW95Rmg1VXhKck1ucjBQUjdjTXM1M0VoVnFJY0FLTVpDanJvVjg4UklJN2FWSVNpRUk3ZTJCVUpxRU5MWVV0OVN5Y0V5VWptc3FKTDg2NXNmNWlEeHpKTElHRXlsT1ZXakxwUkRUZFZwT3VSRkJwVEl6VzgwVXlOMVpEMVZiSVFETWx2QW5KVHIzUlpXSVdZNk9HdUdVOUovcFRSRG53b2M5Q0pUMTJEdm1ENlFVYzBaR2tBMUlja3VsZUxrbDlXU1hlZjQrdzh6U2JoTGxoMUFyWi9CSldhNGRXOVRsTENvZk9nOXFGY0g1OWNCV2FUMXlJTTBiUlhnbmRMMlFOeFhQdnhlOVo2WkY0OUhPVk1BZmpxR3N5SjVhQ0MyblVWaXpCOXZFaUp4T2x3aVpId2pDYVZQTUJJcVROUEVHZkYrZXZuazM5ZFFtQWh3dWFLcElBdWNnY2xXNnN6M1REeUZmeVdRMXRJcG9ueERWdlo0K0d3RGdYdUlhM0hwWTFEWjhNanIwSXZzcmk3VWs4UmVnTFl1eFNpdmJWT0NkMUV2d0NGUzI1QkZyUHUvRWNlNHVEVzVHZy9Ta3BlWTVOc3YzVWo4UkFkYk50OFlXa1hnQklFSkxuSTV6OHFtMlN0NnZIbkpvdzdRNFpYRUUvazIwZDVrckRCUTgvNWw0bVo1KzJCRFpPakh3a1QrODNFeTIrU2pCQjR5OWxWMFZHeWtaQVZiQVZlL25mc0w4WENSeThFbGVoRmJ5Y0JUUElOaFlWTzVMTDVQbDFnTmZGZTYrVlZxVzVtazlzZVdSZ2VmT2FXdHhoVThKSHRhTUo2N3JQN0xBWUdvM2k5SHR0a1RYSGx0VURuY1F0SXJUQThRZjZJdnEybGtibXlUTlRkYlVqU1V5a3lJbFZmU1FhRW5FUkVsaUZ2N1lWUEdWdnhyeUpCMlB1RzdNbkhLc09IVjlSVnFpeFUvSllIbHErMWprbzRHdTJ3UlNzWTFvN2dZSVQ4c0tGYmp0NVkrUkdEQUZNaEZNVlhySHptVUx6Q3dKVm1kSVlwQXN2WEh1VFcyWkY5TFRSa01SRXBSZGlWQ2lBVzkvNFdLeGgvdE1hdjZETlJmbmd0aG1WS2VhYWlLSTRUMXJraWZqc2VGTkJSU3dMQllNQ1FGVGl0bjZ4M054QThDMmxHWTA2T3lSQ3FIVjRSRTFFdjVBb2t0MzlpWVZZbVB3UlZXU3UvSVUrWE5ubmdaUlVpT1duUUVFam5zYzlCNmt6L3QyNENFK3g2dHMxcHZEWXJOdmN6M3U1SmVCTG5EZWNwTVV0Vng3QWkwZ0pLdDlhdjhpUEFHeGoveTF1eWFBc3ZyTVc5T2U4MD0iLCJrZXkiOiJWRlhvdEZWUGhDUldLSUF6MFpJMnVDVlNoRjBjclltWCtiTzNQa0ZSbnU1OW9LenRlSEFoUXJXQXcxNkxZYVh3NjV6eU5tZndmK2w1KzJzRFFGS240dz09In0=', 'device_id': None, 'vehicle_name': 'Kona VÉ', 'vehicle_id': 'qLHNk/TY2fGJeLL1FVGDXA==', 'vehicle_regid': None, 'vehicle_model': 'Kona VÉ', 'vehicle_registration_date': 'missing', 'stamp': 'NoStamp'}
2021-12-25 21:14:12 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Refresh token started 2021-12-26 05:12:54.049911 2021-12-25 21:14:12.487724 False
2021-12-25 21:14:26 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - get_cached_vehicle_status response {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'status': {'lastStatusDate': '20211226014044', 'airCtrlOn': False, 'engine': False, 'doorLock': True, 'doorOpen': {'frontLeft': 0, 'frontRight': 0, 'backLeft': 0, 'backRight': 0}, 'trunkOpen': False, 'airTempUnit': 'C', 'airTemp': {'value': '00H', 'unit': 0}, 'defrost': False, 'acc': False, 'evStatus': {'batteryCharge': True, 'batteryStatus': 80, 'batteryPlugin': 2, 'remainTime2': {'etc1': {'value': 58, 'unit': 1}, 'etc2': {'value': 760, 'unit': 1}, 'etc3': {'value': 180, 'unit': 1}, 'atc': {'value': 150, 'unit': 1}}, 'drvDistance': [{'rangeByFuel': {'gasModeRange': {'value': 0.0, 'unit': 1}, 'evModeRange': {'value': 291.0, 'unit': 1}, 'totalAvailableRange': {'value': 291.0, 'unit': 1}}, 'type': 2}]}, 'hoodOpen': False, 'transCond': True, 'steerWheelHeat': 0, 'sideBackWindowHeat': 0, 'dte': {}, 'tirePressureLamp': {'tirePressureLampAll': 0}, 'battery': {'batSoc': 83, 'batState': 0, 'batSignalReferenceValue': {}}, 'remoteIgnition': True, 'seatHeaterVentInfo': {}, 'sleepModeCheck': False, 'lampWireStatus': {'headLamp': {}, 'stopLamp': {}, 'turnSignalLamp': {}}, 'windowOpen': {}, 'engineRuntime': {}}}}
2021-12-25 21:14:29 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Service status data {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'maintenanceInfo': {'msopServiceOdometer': 12920.0, 'msopServiceOdometerUnit': 1, 'mtspServiceDate': '20211109', 'imatServiceOdometer': 24920.0, 'imatServiceOdometerUnit': 1, 'mtitServiceDate': '20220509', 'currentOdometer': 17194.9, 'currentOdometerUnit': 1, 'serviceOdometerDuration': 12000.0, 'serviceDaysDuration': 180, 'serviceMonthsThreshold': 6}}}
2021-12-25 21:14:33 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Received Pin validation response <Response [200]>
2021-12-25 21:14:41 DEBUG (SyncWorker_3) [custom_components.kia_uvo.KiaUvoApiCA] kia_uvo - Get Vehicle Location {'responseHeader': {'responseCode': 0, 'responseDesc': 'Success'}, 'result': {'head': 220, 'coord': {'lat': xxx, 'lon': xxx, 'alt': 13.64, 'type': 0}, 'accuracy': {'hdop': 0, 'pdop': 1}, 'time': '20211226021438', 'speed': {'value': 0, 'unit': 0}}}
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - LastUpdated 2021-12-26 01:40:44+00:00 - Timezone UTC
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.Vehicle] kia_uvo - Engine type set VEHICLE_ENGINE_TYPE.EV
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.1.targetSOClevel
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.0.targetSOClevel
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.1.dte.rangeByFuel.totalAvailableRange.value
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleStatus.evStatus.targetSOC.0.dte.rangeByFuel.totalAvailableRange.value
2021-12-25 21:14:41 DEBUG (MainThread) [custom_components.kia_uvo.sensor] skipping sensor for missing data, key:vehicleLocation.geocodedLocation.display_name

my last message was after a restart of home assistant. the message before was after a restart of the host os.
I also tried to reload the integration... and I get the same log file

I guess #224 has not been included in 1.2.6 release?

This PR is still open, i believe @cdnninja is still figuring out what is the main point to differentiate temperature range. Yes, it is not part of latest release.

@zadigre  are you able to restart again and search for "Get Vehicles Response"?  It for sure happens when login occurs. It could be that the token wasn't expired above so it didn't try log in.  @dallaby23 this is something you could help with as well.
@fuatakgun  is right - at this point I don't know why your cars are different than mine, I need to find a reason so we can have this work for both our cars.

Not sure if I am missing something but I don't see hvactemptype at all in
my home assistant logs..
On Sat., Dec. 25, 2021, 1:01 p.m. cdnninja, @.***>
wrote:

@dallaby23 https://github.com/dallaby23 could you use the same sniff
from above? I'm wondering if the temptype is the key. I have only seen that
being different on an EV but if yours is 1 as well that may be it.
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001053363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RXK6ANQS7ZESS2FUDTUSYBGHANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Two separate things we were looking for. hvactemptype won't be in the logs as we currently don't log it.   The above post was from sniffing the connection to Hyundai / Kia.   At this point I want to focus on "Get Vehicles Response" as it holds something called gentype that for my car is G1, thinking yours may report G2 or something like that.  This may be my clue.

Mine is reporting G1 for gentype
On Mon., Dec. 27, 2021, 12:51 p.m. cdnninja, @.***>
wrote:

Two separate things we were looking for. hvactemptype won't be in the logs
as we currently don't log it. The above post was from sniffing the
connection to Hyundai / Kia. At this point I want to focus on "Get Vehicles
Response" as it holds something called gentype that for my car is G1,
thinking yours may report G2 or something like that. This may be my clue.
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001676082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RQSZLECU2RFGPAK7ETUTCRS3ANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@cdnninja
I still do not see what you are looking for in my log.
Token is expiring 2021-12-28 03:16:21.539661
So I guess i la get have to wait a few hours before seeing it.
Will it automatically appear in the log when it automatically refreshes the token?

Yes it will show up assuming debug is enabled.   Considering dallaby23 is G1 I don't think that will help us.  Maybe this is just a 2021 thing?  I could assume it impacts all 2021 and wait until I get a complain of it being 2C wrong in the other direction.

@cdnninja
I have this in my config file...
logger:
default: warning
logs:
custom_components.kia_uvo: debug
anything else I should add?
is the valid_until date&time in GMT?

@Kevr0n228 What year is your car and do you have this issue?
@zadigre yes that is correct for debug.   As for time I think that one is local time - that is something we should clarify in the logs.

I've got a 2019 and it seems I have the same issue. Just set the climate at 22 degC, but the Homeassistant Bluelink shows the set temperature as 24.

@kevr0n228  thanks for confirming.  Just to clarify so when you did a remote start for 22 and went to look it was at 20?  Or did you set at 24 and car went to 22 with bluelink showing 24 as well?

I'm actually just finishing a charge while driving home. I was waiting in
the car with the climate set to 22 when I checked my email. I VPN'd into
home and checked hass where it said 24. I have not checked whether the
temperature I use when I call start_climate also comes up with a 2 degree
difference. I can take a look later once I'm done the drive.
On Mon., Dec. 27, 2021, 16:29 cdnninja, @.***> wrote:

@Kevr0n228 https://github.com/Kevr0n228 thanks for confirming. Just to
clarify so when you did a remote start for 22 and went to look it was at
20? Or did you set at 24 and car went to 22 with bluelink showing 24 as
well?
—
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/kia_uvo/issues/220#issuecomment-1001767883,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACP3WYXNUG6CX3HRW6YOLPLUTDLCPANCNFSM5KW4SQXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@cdnninja
my genType is G3.

Once @Kevr0n228 confirms on a start command his is two off that means this seems to be all EVs in Canada plus at least 2021 ICE cars.  This is my current theory atleast.

@Kevr0n228
any news? we are all waiting for you! 😉

Sorry for the delay, I've been trying to test but for some reason my set temperature is just stuck at 16. Not sure if I'm not waiting long enough but running a forced update doesn't seem to do it either.

Which version are you on?  I put in a fix that would cause this for certain temps but that is only for read. Not for starting.

On Dec 31, 2021, at 1:03 PM, Kevin @.***> wrote:

Sorry for the delay, I've been trying to test but for some reason my set temperature is just stuck at 16. Not sure if I'm not waiting long enough but running a forced update doesn't seem to do it either.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

I'm on v1.24 currently

The newer version solves a reading issue for 22c. The version doesn't change remote start though.  Just the sensor view.

Alright, updating to v1.26 got the set temperature to update after calling start_climate_ev. No discrepancy this time, requested 22C, got 22C.

Alright, updating to v1.26 got the set temperature to update after calling start_climate_ev. No discrepancy this time, requested 22C, got 22C.

Sounds good, thanks for checking.  In car showed the same values?
I’m going to assume the 2c issue is a 2021 and newer thing.

On Jan 1, 2022, at 12:44 PM, Kevin @.***> wrote:

Alright, updating to v1.26 got the set temperature to update after calling start_climate_ev. No discrepancy this time, requested 22C, got 22C.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Sounds good, thanks for checking.  In car showed the same values?
I’m going to assume the 2c issue is a 2021 and newer thing.

On Jan 1, 2022, at 12:44 PM, Kevin @.***> wrote:

Alright, updating to v1.26 got the set temperature to update after calling start_climate_ev. No discrepancy this time, requested 22C, got 22C.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

For what it's worth, am seeing the 2c discrepancy here on a 2020 Kona electric. Am running newer than 1.2.6 for sure, as I just set this up a few days ago.

@unsoluble  great info.  So that means it is potentially 2020 and newer.

I have been spending most of my time here working on version 2.0 of this integration.   This issue is easy to resolve in that version.   Is it okay if we leave this for 2.0?

Closing as per #386

Resolved in 2.0

For what it's worth, I'm still seeing this discrepancy as of 2.0.49 (in a 2020 Kona E). Car temp still ends up 2° cooler than instructed by HA scripts.

@unsoluble  Is this a Canadian car?

Ahh, okay, thanks! :)

If you update from "master" in HACS this should be fixed for you. Next release version number will include it.

@unsoluble  are you able to let me know if not solved. I will close for now.

Yep, works, thanks! Heated seats don't, as far as I can tell, but that's something for another ticket. :)

Yep, works, thanks! Heated seats don't, as far as I can tell, but that's something for another ticket. :)

We have a thread for that new feature.  Would love feedback and logs on this.  I know the underlying api works but I don't have a car with support for this to test it all out.

Temperature is correct on my 2021 kia seltos.. I am in Canada as well..
On Thu., Dec. 22, 2022, 8:22 p.m. cdnninja, @.***>
wrote:

Yep, works, thanks! Heated seats don't, as far as I can tell, but that's
something for another ticket. :)
We have a thread for that new feature. Would love feedback and logs on
this. I know the underlying api works but I don't have a car with support
for this to test it all out.
—
Reply to this email directly, view it on GitHub
https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/220#issuecomment-1363493988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFF6RQJHNZACSFFGEHJGTLWOT5EXANCNFSM5KW4SQXQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I just started using the preheat on my 2019 Electric Kona (Canada) again and it seems that this issue has returned. I'm running the latest version of the integration, updated it this morning.  I tried requesting several different temperatures. The set temperature in homeassistant was the same as what I requested, just the actual set temp in the car (and what was shown in the bluelink app) was 2 degrees lower.

I just tired it on my 2021 Kona Electric (also in Canada)… and it works as intended (same temperature is showing everywhere).Le 7 nov. 2023 à 20:07, Kevin @.***> a écrit :
I just started using the preheat on my 2019 Electric Kona (Canada) again and it seems that this issue has returned. I'm running the latest version of the integration, updated it this morning.  I tried requesting several different temperatures. The set temperature in homeassistant was the same as what I requested, just the actual set temp in the car (and what was shown in the bluelink app) was 2 degrees lower.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


FrameData is limited in size

A simulation frame is represented by a FrameData that is sent as a single gRPC message. Because a gRPC message is limited by default to 4MB, a frame is limited to what can be represented in that volume. This limits the size of the system we can simulate and stream.
The maximum system size is related to the number of particles in the system but not linearly so. Indeed, the limit accounts for the topology that depends on the number of residues and chains and the number of bonds. For the same number of particles, a system with explicit water is likely to take more space than a system with a single-chain protein, except if all the water molecules are counted as a single residue. The size limit also needs to account for optional data that can be included such as forces, velocities, energies, user forces...
There are short-term solutions to the issue that would push the size limit:

increase the size of a gRPC message
enable HTTP compression

These solutions would push the size limit but not remove it. An actual solution would be to stream chunks of frames rather than streaming frames. This adds some complexity but would allow infinitely sized frames. At this point, the issue will become the time needed to produce and send the frames rather than the size of the frame itself.
Any of these changes would be breaking and would require changes on both the servers and the clients. The short-term solutions require limited changes as they are configuration values when creating the gRPC connection. The long-term solution is more involved. It could be implemented while keeping the current way of sending frames alongside the new one until the transition is done. Indeed, only larger systems will require the more complex system.

For now we will use the built-in unlimited message length and see if there's an issue.


XMLTextDecode cannoit handle the !CDATA flag

See this thread
https://groups.google.com/forum/#!msg/mitappinventortest/TZO5InFSIkU/nqGwb4dPrUcJ

This bug has been around for a long time.  Can we take a look and try to killl it?


Update stepper input styles with latest styles

Describe the bug
The input fields in stepper example display labels chopped off
What is the expected behavior?
label to display while input field contains text
What are the steps to reproduce?

Go to...showcase demo
Click on...http://localhost:4200/material-components/navigation-components
stepper card and fill in input fields

Screenshots or links to minimum reproduction example

Environment

Anything else to add?

Changes are merged.


connection error

erro whwn connecting to websoket

can you copy the log from Advanced -> Logs and paste it here?
There seems to be an error. Just not sure where it exactly occured based on your screenshot alone.

i can not copy the logs . i hope screen is enough

yes. thanks.
One big thing is definetly running it from OneDrive. I heard from multiple people that this is problematic.
So please try to run it from a normal harddrive first. Maybe that already fixes the issue.

thanks . onedrive was the issue
it is working fine now


Question about creating "000000.00000.TA.124_0_Payload.xml.signed" file (from example)

TestMain.java
After line 48 after "m.signer.signStreaming(canadaXml, signedCanadaXml, m.canadaSigKey, m.canadaPubCert);" created file "000000.00000.TA.124_0_Payload.xml.signed"
After line 49 after "m.signer.signDOM(canadaXml, signedCanadaXml, m.canadaSigKey, m.canadaPubCert);" created new version of "000000.00000.TA.124_0_Payload.xml.signed" file. Previuos file is overwritten.
These *.xml.signed files are different by digests and "Transforms" section.
What version of *.xml.signed file is correct? First or second?
Vladimir.
P.S. Sorry for my English.

Anybody?

The streaming and DOM versions should both work fine. One was intended for very large files and the other is for smaller files. I do have a newer version of the Signer class that will be posted very shortly though.

Thank you for reply.


add a useless file

add a useless txt file.

Sorry, I think that your modification is not very useful for the project. From your perspective, you can try to help us add entity classes.

add a useless txt file.
Sorry, I think that your modification is not very useful for the project. From your perspective, you can try to help us add entity classes.


Extend roles for policy matching

We need to extend roles to limit users to access data that are associated with their (users) site only.
In addition, we could consider designing a generic policy matching of such roles.

Resolved in https://github.com/ideafast/ideafast-portal/pull/1130.


fix: change 'key' -> 'property' in README

Changes

Changes the sample config in the README to use 'property' instead of 'key'.

Closes #1

@pjhul thanks a lot! Merging :)


Thyroid disease Classification

💥 Proposal
I want to create a model that could classify the type of thyroid disease
i will do this by using searchGridCV and i would select the best classifier possible
@khusheekapoor
i am GSSOC'23 contributor
i want to do this project so please kindly assign me this
the dataset i would use is:- https://www.kaggle.com/datasets/emmanuelfwerr/thyroid-disease-data

💥 Proposal
I want to create a model that could classify the type of thyroid disease
i will do this by using searchGridCV and i would select the best classifier possible
@khusheekapoor
i am GSSOC'23 contributor
i want to do this project so please kindly assign me this
the dataset i would use is:- https://www.kaggle.com/datasets/emmanuelfwerr/thyroid-disease-data

@lcs2022026 - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


Update responses of the User Controller

Some User controller methods have not followed the standard responses.
Implement the soft delete for user controller.

fixed with commit 785f366db4debbfe30b0f78b0c6efda41625c385


Add spark-hyperloglog to Mozilla

This also adds the changes I made for Quantum RC, as well as updates some tests. I bumped the version to 2.0.0 since the API has changed. We can release this on spark-packages under the mozilla name and it will be separate from vitillo/spark-hyperloglog.

I wanted to change the license to MPL 2.0 but I don't think we can switch it from Apache.

@mreid-moz RFAL


User import fails to set bidding roles

Not essential - "Fix Problems" button on bid management page takes care of this.  Hold open for a while...


[Record checking 1/2] API, Documentation and Stubs

This is a side-port to development of https://github.com/ARMmbed/mbedtls-restricted/pull/618 that has already been merged to baremetal.
This PR introduces the record checking API with documentation, stub implementation and test programs.
Background
This is the first in a series of two PRs implementing the record checking API.
For more information on this feature, please refer to the HLD.
The two PR's in the series are
r618 -> This PR
r619 -> TBD
The second PR is still waiting for merge in baremetal.
Side-porting details
Side-porting was quite straightforward with couple of conflicts because of the context serialization feature already merged in baremetal.
The table shows how each side-ported commit was handled:
-(nothing) cherry-picking worked without conflict
-"r" manual rework after cherry-picking

resolution
original commit
commit message

r
https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/02f2609551c6cd42edc8d2f8ff9cb24361795df4
Introduce configuration option and API for SSL record checking

r
https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/14219feb278508d71e592b133f3f8dd54864d9b7
Add IO wrappers to ssl_client2 as interm's between NET and SSL layer

r
https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/fe24b3b269e164f90ef54a62add2ecf8adb03f0d
Add IO wrappers to ssl_server2 as interm's between NET and SSL layer

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/de9e36e6b3729d79e38b77aafd78bfcfafee4f76
Pass dgrams to mbedtls_ssl_check_record in ssl_client2/server2

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/82ff6f1e17b636e80cc359d69c4125e3df5cbd0b
Update version_features.c

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/bec8885b7deb5337529ac2e3c7fe1b1f4aba2c8e
State that record checking is DTLS only and doesn't check content type

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/c2b08d12519bdd81ce0ce70d5995eb7f66f0f9fb
Fix minor issues in documentation of mbedtls_ssl_check_record()

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/83b8c3b8eb2c1a34dea5aa1d345faf1aa5f8e438
cli/srv ex: Add dbg msg if record checking gives inconsistent result

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/e29dfb2157cdfe3fa1736a98530b2bd601252710
Add missing word in documentation of mbedtls_ssl_check_record()

https://github.com/ARMmbed/mbedtls-restricted/pull/618/commits/32bbe4a66b2631b2261b72d0fc2f6ed409352da7
Remove unused label in ssl_client2/ssl_server2

It doesn't look like the server software needs to call the API, but if it does, has the API been approved by Szymon's team? If not we need approval before this is merged.

This is a feature specifically for the server side, and the API has been requested and approved by the server team.

@sbutcher-arm I think the review comments has been addressed. Could you please re-review. @k-stachowiak could you also please re-review.

Amended the last commit with changes suggested by @hanno-arm

@sbutcher-arm Pleaser re-review


Teams Tabs Sample [Experimental]

Fixes: Our lack of this sample in Node.
Needs testing, since I can't get on a Teams ring that has Tab Fetch/Submit yet. @EricDahlvang?

Closing, we've decided to not include this.


Rc2.39

Merge late rc changes into devel

@sabrine33 Could you at some point take a look at the conflicts in this PR between the rc branch and devel? Thanks


skeema help should show that skeema init help is a possible combination

skeema help output
Usage:
      skeema [<options>] <command>

Commands:
      add-environment  Add a new named environment to an existing host directory
      diff             Compare a DB instance's schemas and tables to the filesystem
      help             Display usage information
      init             Save a DB instance's schemas and tables to the filesystem
      lint             Verify table files and reformat them in a standardized way
      pull             Update the filesystem representation of schemas and tables
      push             Alter tables on DBs to reflect the filesystem representation
      version          Display program version

excludes skeema init help while it is supported.
Explaining that the help option can be combined with the other commands should help newcomers.

First, pretty much every Linux command suite I've ever used works in this fashion, so this should not be surprising or unexpected.
Second, the output also includes this line, which you cut off in your issue:
  -?, --help[=value]                  Display usage information for the specified command

For example, all of these combinations work properly and are completely equivalent: skeema help diff, skeema diff --help, skeema diff help, skeema --help=diff
While I agree the help information could be improved (nothing's ever perfect!), this issue report feels trivial and unnecessary. Please understand Skeema is primarily a single-person bootstrapped project, and I simply do not have the bandwidth for trivial / nitpick issues unless a corresponding pull request is submitted with them.


Remove references to std::tr1

Visual Studio 2017 version 15.5 has deprecated the std::tr1 namespace, leading to significant warning spew. It'll also fail to compile if we set the C++17 flag. The other condition where we could require <tr1/tuple> would be on Android if using STLport, but we've never supported that config.
According to the gtest docs, setting the flag in the build flow is preferred over editing gtest.h directly.

looks good.


Gitops issue

close https://github.com/devtron-labs/devtron/issues/305

@shivani170 Please rename Github token to Personal Access Token both for GitHub and GitLab.

@shivani170 Please rename Github token to Personal Access Token both for GitHub and GitLab.

ok


Update jjwt to 0.12.2

cc @electrum

@electrum review addressed

Rebased to resolve conflict. @electrum PTAL

Ping @electrum

Ping @electrum @martint

@electrum rebased


Runtime Segmentation fault (core dumped)

Steps to reproduce

CentOS release 6.9 (Linux version 2.6.32-696.16.1.el6.x86_64 (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) )
Complier: gcc 7.2.0
Compilation status: success
Python version: 3.6.5

Observed Results
"python src/habitat-sim/examples/example.py --scene ~/data/habitat/scene_datasets/habitat-test-scenes/skokloster-castle.glb" leads to:

Possible Reasons

Incorrect EGL version? I locally installed the following two packages by "rpm2cpio XX | cpio -idv" : mesa-libEGL-11.0.7-4.el6.x86_64.rpm  & mesa-libEGL-devel-11.0.7-4.el6.x86_64.rpm. Then I directly replace the header files by EGL 1.5 to include necessary DEFINEs as suggested in https://github.com/facebookresearch/habitat-sim/issues/145#issuecomment-521318477

Is the version of EGL .so file enough for habitat? (v11.0.7 for centos 6)
"ldd libEGL.so.1.0.0" gives:
linux-vdso.so.1 =>  (0x00007ffd3c318000)
/usr/local/gcc/7.2.0/lib64/libstdc++.so.6 (0x00002b3c37694000)
/usr/local/gcc/7.2.0/lib64/libgcc_s.so.1 (0x00002b3c37a2b000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00002b3c37c56000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b3c37e75000)
libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00002b3c38093000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00002b3c38294000)
libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00002b3c385d1000)
libxcb-xfixes.so.0 => /usr/lib64/libxcb-xfixes.so.0 (0x00002b3c387d6000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00002b3c389dd000)
libxcb-shape.so.0 => /usr/lib64/libxcb-shape.so.0 (0x00002b3c38be9000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00002b3c38ded000)
libgbm.so.1 => /usr/lib64/libgbm.so.1 (0x00002b3c39012000)
libm.so.6 => /lib64/libm.so.6 (0x00002b3c3921d000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002b3c394a2000)
libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00002b3c396a6000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00002b3c398b3000)
libc.so.6 => /lib64/libc.so.6 (0x00002b3c39adc000)
/lib64/ld-linux-x86-64.so.2 (0x0000003af4a00000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00002b3c39e70000)
librt.so.1 => /lib64/librt.so.1 (0x00002b3c3a074000)

Incorrect CUDA or GPU version? I loaded cuda 7.5 / 9.2 / 10.0 with Tesla V100 but still not working

Other missing or incorrect dependencies?

CUDA 9.2 and 10.0 on a V100 should work.  In order for EGL to work correctly, habitat-sim needs to pick up Nvidia's version of EGL at runtime.  If it doesn't by default, it is likely that your system has a non-standard Nvidia driver install and you need to add the path to Nvidia's libEGL to LD_LIBRARY_PATH.

CUDA 9.2 and 10.0 on a V100 should work. In order for EGL to work correctly, habitat-sim needs to pick up Nvidia's version of EGL at runtime. If it doesn't by default, it is likely that your system has a non-standard Nvidia driver install and you need to add the path to Nvidia's libEGL to LD_LIBRARY_PATH.

Hit the point! Thanks. Actually I noticed this answer https://github.com/facebookresearch/habitat-sim/issues/18#issuecomment-483930596 which should also be the right answer here. But I misunderstood and thought libglvnd is one of the dependencies of EGL, trying to fix by updating EGL to latest mesa version and installing libglvnd. Now figure out that mesa-egl and libglvnd-egl are two distributions. "python example/example.py --scene ...." seems working now:

To those who might be interested, the final solution is straight-forward (on CentOS6 without root):
(1) locally install (rpm2cpio) libglvnd-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, libglvnd-core-devel-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, libglvnd-devel-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, libglvnd-egl-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, libglvnd-gles-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, libglvnd-glx-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, libglvnd-opengl-1.0.1-0.1.git5baa1e5.el6.x86_64.rpm, mesa-libEGL-18.0.5-4.el7_6.x86_64.rpm, mesa-libEGL-devel-18.0.5-4.el7_6.x86_64.rpm, mesa-libGL-18.0.5-4.el7_6.x86_64.rpm, mesa-libGL-devel-18.0.5-4.el7_6.x86_64.rpm (install mesa version to get the header files for compilation)
(2) add "-DEGL_LIBRARY=/path/to/libglvnd/libEGL.so" and "-DEGL_INCLUDE_DIR=/path/to/include" to setup.py
(3) modify some system variables (gcc version should be >= 7.1.0
export CC=/path/to/gcc/7.2.0/bin/gcc
export CXX=/path/to/gcc/7.2.0/bin/g++
WARNING: playing with LD_PRELOAD in ~/.bashrc could be super-dangerous (unexpected missing dependencies can crash everything and hard to fix w.o. root). DO export necessary LD_LIBRARY_PATH at the same time or leave some bashes running either on tmux or other terminals to remedy the system whenever needed.
export LD_PRELOAD=/path/to/gcc/7.2.0/lib64/libstdc++.so.6:/path/to/gcc/7.2.0/lib64/libgcc_s.so.1
export LD_PRELOAD=$LD_PRELOAD:/path/to/libglvnd/libEGL.so
export LD_PRELOAD=$LD_PRELOAD:/path/to/libglvnd/libGL.so
lib64 below is the library path for your local installation
export LD_LIBRARY_PATH=/path/to/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=/path/to/lib64/libglvnd:$LD_LIBRARY_PATH
(4) "python setup.py install --headless"

Just for future reference,

(2) Add "-DEGL_LIBRARY=/path/to/libglvnd/libEGL.so" and "-DEGL_INCLUDE_DIR=/path/to/include" to setup.py

is likely unneeded as using whatever EGL gets picked up at compile time is totally fine, its just at run-time that the correct EGL needs to be picked up.

Just for future reference,

(2) Add "-DEGL_LIBRARY=/path/to/libglvnd/libEGL.so" and "-DEGL_INCLUDE_DIR=/path/to/include" to setup.py

is likely unneeded as using whatever EGL gets picked up at compile time is totally fine, its just at run-time that the correct EGL needs to be picked up.

Yes the version of libEGL.so does not matter for compilation. Adding the path of whatever libEGL.so to LD_LIBRARY_PATH should also work. But the EGL header files should be up-to-date to include some necessary variables for compilation.

Ah yes, they should be :)


Mutliline text is cut

I have an issue when I use the composeBar to enter more than a line , the first one is displayed correctly the lines after are being cut and not visible.
Check attached photo

I'm sorry, can't really help you. Maybe something with the font size?

I have ended up solving it by the following code in the composeBarView delegate
- (void)composeBarView:(PHFComposeBarView *)composeBarView
   willChangeFromFrame:(CGRect)startFrame
               toFrame:(CGRect)endFrame
              duration:(NSTimeInterval)duration
        animationCurve:(UIViewAnimationCurve)animationCurve
{
    float diff = (startFrame.size.height - endFrame.size.height);
    CGRect frame = self.tableView.frame;
    frame.size.height += diff;
    self.tableView.frame = frame;

    CGRect textViewFrame = composeBarView.textView.frame;
    textViewFrame.size.height -= diff;
    composeBarView.textView.frame = textViewFrame;

}

:+1: Glad you found a solution


first aggregated stats

output some basic stats in footer
fetched on start of app, and refetched every 10 sec. when in viewport

numbers fetched from new endpoint
https://github.com/oceanprotocol/market-stats
https://market-stats.oceanprotocol.com

so does it make sense just logging the cancel?
if (axios.isCancel(error)) {
  Logger.log(error.message)
 } else {
  Logger.error(error.message)
}

You can leave it like that, but it doesn't provide much information

meh, just pushed the change I already committed as that cancel token logging doesn't seem to matter much


Switch golang -> rust

Pretty much equivalent except much simpler now.
Help already works:
rk@rk-dell:~/ae$ cargo run -- --help
    Finished dev [unoptimized + debuginfo] target(s) in 0.02s
     Running `target/debug/ae`
Usage: ae <COMMAND>

Commands:
  create  Create a container from a bundle directory
  delete  Release container resources after the container process has exited
  kill    Send a signal to the container process
  start   Start the user-specified code from process
  state   Request the container state
  help    Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help information

Following the discussion in the discord, I'm going to leave a note here that this PR is going to be closed to prevent confusion.
The aurae repo has got plenty of rust. Hope to see you there.
@krisnova let's close this PR when you have a chance.


Assembly App: hidden folders are now shown in the output folder selection

don't remember seeing them before.

Fixed and pushed to beta.

looks better now! :)


MySQL JSON doesn't work

MySQL 5.7+ has JSON type, I add your typehandler but it doesn't work, and there are errors.

Error parsing Mapper XML. Cause: java.lang.IllegalStateException: No typehandler found for property friends

Is there anything wrong with my usage?

Hi. As you can see this JSON mapper can work with any string type, thus you must pass JSON to/from JDBC as String other cases are not supported.
BTW error you posted here is totally irrelevant, because  JSON type handler has nothing to do with XML.


Remaining task checklist

List of tasks to complete Token-Negotiator (Client Side Demo and Package)

[ ] Add an authenticate discount button inside modal in place of the 'select ticket'

[ ] Create a Devcon account management page (showing use of tokens inside Devcon website example)

| Page should show tickets loading into view when enabled.

[ ] Responsive Styling (ensure the modal can be viewed in mobile device widths e.g. Iphone5-X)

[ ] Split the Negotiator Code into Client, Modal, Core logic (responsbilities).

[ ] Safari Fix (change event dispatching method used)

[ ] Unit Tests

[x] Move examples into separate location

[ ] Update Readme

[ ] White List Functionality

[ ] Move Signed Devcon Ticket (can discuss this, however this will enable the lib to better scale)

[ ] Switch out any T-N code naming to Token /rather than Ticket or anything containing Devcon

[ ] Github actions when the unit tests are done to stop merges before code is of a specific quality

[ ] Deploy NPM to @tokenscript

[ ] Update Readme, Demo notes

[ ] Development testing across devices / fixes / updates

[ ] Align Webpack build script / Typescript configs

[ ] Move Demo examples into seperate repository (as discussed in last weeks meeting with Weiwu)

Examples from 'main' migrated to https://github.com/TokenScript/token-negotiator-examples/settings
Tested and working as per Demo with Devcon.

@nicktaras Gradle issue fixed, but pushing  version 0.1.4 directly from main (since now the Maven issuance branch has been merged)


unsupported type: <class 'NoneType'>

Hi all,
I have been using quanstats for a while but decided to switch over to the lumi fork.
With the same df that works for an HTML tearsheet in Quantstats however, I get an error in lumi. Maybe I am missing something, I would highly appreciate someone giving me a hint:
Debugging: First rows of equity_returns:
changeEquity%
04.06.2024       0.000000
05.06.2024       0.001630
06.06.2024       0.001174
...
qs.reports.html(returns=equity_returns,
rf=0.039,
title=merged_title,
output=output_html,
match_dates=True,
compounded=True)
The error reads: unsupported type: <class 'NoneType'>
Thank you so much!

What is the error that you are getting?
Robert Grzesik<PHONE_NUMBER>
On Fri, Jul 5, 2024 at 2:51 AM JF1805 @.***> wrote:

Hi all,
I have been using quanstats for a while but decided to switch over to the
lumi fork.
With the same df that works for an HTML tearsheet in Quantstats however, I
get an error in lumi. Maybe I am missing something, I would highly
appreciate someone giving me a hint:
Debugging: First rows of equity_returns:
changeEquity%
04.06.2024 0.000000
05.06.2024 0.001630
06.06.2024 0.001174
...
qs.reports.html(returns=equity_returns,
rf=0.039,
title=merged_title,
output=output_html,
match_dates=True,
compounded=True)
Thank you so much!
—
Reply to this email directly, view it on GitHub
https://github.com/Lumiwealth/quantstats_lumi/issues/47, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIYQK7CAZGMIKZGOPMROUDZKY7APAVCNFSM6AAAAABKMT7HUKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TCOJWGA4DKNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


run_modal.py (application protocol failed to receive SSL data)

This is for bugs only
Did you already ask in the discord?
Yes
You verified that this is a bug and not a feature request or question by asking in the discord?
Yes
Describe the bug
The modal version doesn't work:
modal run run_modal.py --config-file-list-str=/root/ai-toolkit/config/modal_train_lora_flux_24gb.yaml
I run it with this command and after a while I get an error:
application protocol failed to receive SSL data
protocol: <asyncio.sslproto.SSLProtocol object at 0x0000024DF7041FF0>
transport: <_SelectorSocketTransport fd=185608 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "C:\Users\Dragoy\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 551, in data_received
    self._app_protocol.data_received(chunk)
  File "D:\Program Files\Stable Diffusion\FLUX_TRAIN\modal_com\ai-toolkit\venv\lib\site-packages\grpclib\protocol.py",
line 714, in data_received
    events = self.connection.feed(data)
  File "D:\Program Files\Stable Diffusion\FLUX_TRAIN\modal_com\ai-toolkit\venv\lib\site-packages\grpclib\protocol.py",
line 189, in feed
    return self._connection.receive_data(data)  # type: ignore
  File "D:\Program Files\Stable Diffusion\FLUX_TRAIN\modal_com\ai-toolkit\venv\lib\site-packages\h2\connection.py", line
1463, in receive_data
    events.extend(self._receive_frame(frame))
  File "D:\Program Files\Stable Diffusion\FLUX_TRAIN\modal_com\ai-toolkit\venv\lib\site-packages\h2\connection.py", line
1487, in _receive_frame
    frames, events = self._frame_dispatch_table[frame.__class__](frame)
AttributeError: 'H2Connection' object has no attribute '_frame_dispatch_table'

#158 - the patch also doesn't help....

i fixxed this error installing the venv with python version 3.11

@jaretburkett


[UI] Command line option to reset the wallet-UI added

Reference: https://bitcointalk.org/index.php?topic=421615.msg17362363#msg17362363 (and some more I can't find any more)
Sometimes (settings corrupt, change to a smaller screen resolution, other end-user-error, ...) parts of the UI are not visible/accessible anymore, and if that includes the Reset Options button the user has a problem.
Instead of explaining the user how to navigate to the folder/registry-entry where the Qt-settings are persisted it's much more convenient to just tell him "Start the wallet with the option -resetui".

Hmm... How is that different from -resetguisettings   Reset all settings changes made over the GUI https://github.com/dashpay/dash/blob/v0.12.1.x/src/qt/utilitydialog.cpp#L89 ?

I think what @crowning- is trying to address is the scenario when the settings are SO broken, that you can't even access that menu anymore :)
utACK

n/m - should have read your comment twice ....

Oops, I didn't know this feature, I just checked init.cpp for available command line options, and there wasn't anything there :-/
Okay, it's utilitydialog.cpp...I'll close this one.


Support Local Ratelimiting

Description:
Add support for local ratelimiting in envoy gateway project.
Similar to https://github.com/envoyproxy/gateway/issues/670

closing in favor of https://github.com/envoyproxy/gateway/issues/1336


build: automate running E2E tests with coverage

Issue or need
Running E2E tests with coverage requires several steps:

Building the library
Instrument the library for coverage reporting
Create an example app
Build an example app
Serve an example app
Run Cypress E2E tests

So the feedback loop from a change in the library to the coverage change in E2E tests is waaaaay too long

Proposed changes
In order to automate the whole process, a WebStorm run configuration is created with all those steps. It also includes steps to clean caches (lib build cache / app build cache) in between to avoid stale results.
However, in order to start the server, run Cypress tests and then stop server, something extra is needed. Otherwise WebStorm starts serving and given the process doesn't stop, next tasks aren't run.
To solve that, start-server-and-test package is used in order to run an app, run tests and stop running the app in a single command. This also allows to improve the CLI DX to run E2E tests as just 1 command is needed after creation & build of an example app to run E2E tests against it.
Finally, given the script knows which app is running, uses the env var introduced in #733 to automatically name the resulting code coverage report by suffixing it with the app that was ran

Quick reminders

🤝 I will follow Code of Conduct
✅ No existing pull request already does almost same changes
👁 Contributing docs are something I've taken a look at
📝 Commit messages convention has been followed
💬 TSDoc comments have been added or updated indicating API visibility if API surface has changed.
🧪 Tests have been added if needed. For instance, if adding new features or fixing a bug. Or removed if removing features.
⚙ API Report has been updated if API surface is altered.

#734  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


boilerplate for plugin interface

What does this PR change?

Does this PR relate to any other PRs?

How will this PR impact users?

Does this PR address any GitHub or Zendesk issues?

How was this PR tested?

Does this PR require changes to documentation?

@sajit this hasn't been tested, but just sort of wanted to contribute some boilerplate here and sketch out how this interacts with the plugin infrastructure itself. Feel free to ask me questions on what has been done here.
next, I'm going to write an integration test harness that invokes the whole plugin to test all that grpc stuff


[WILL NOT MERGE] Update skips and xfails for test_jvp

After applying https://github.com/pytorch/pytorch/pull/72309
What remains to be done:

also update test_vmapjvp, and test_vmapjvpall

I'm cleaning up old PRs in preparation for the functorch->pytorch merge; we've already landed this in some form so closing.


Bug in Documentation to do with deprecatedPropType

Some of the API docs are broken when they use deprecatedPropType

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Since the release of v4.12.1 there is a bug with some of the documentation files whenever you use deprecatedPropType. I was having a look at the Grid API  and if you scroll down to Justify, you can see that the formatting is now off. I tried to have a look through the code to try and resolve it but it wouldn't build on my machine.
Expected Behavior 🤔

Pretty self explanitoy but I expect the docs to be formatted nicely and easily readable.
Steps to Reproduce 🕹

Steps:

Just go to the Grid API  docs and you can see it there. It is also on another other page that uses deprecatedPropType

Duplicate of #27191.


MySql :  Compare / Migrate --> Simple Structure Compare not showing Expected output

Description
The Simple Structure Compare Feature does not show the column datatype difference if there is any.
In the Below Shown Example, both the columns have different datatypes but the same is not shown in the compare results.
DBeaver Version
<IP_ADDRESS>302060909
Operating System
Windows 10
Database and driver
No response
Steps to reproduce
Reproducible Steps:

Create a table with below query:

CREATE TABLE `employee` (
  `employee_id` bigint DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

Create Another Table with below query:

CREATE TABLE `employee2` (
  `employee_id` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

From the Database Navigator, Select these two created tables and click on
Compare / Migrate --> Simple Structure Compare

Additional context
Mysql Version : MySQL 8.0.35-0ubuntu<IP_ADDRESS>
Dbeaver Version: <IP_ADDRESS>302060909

I don't think it's a bug, that happens when you check an option to ignore properties. Would it happen if you uncheck this option?


Stop trying to outsmart gopath

Coverage remained the same at 100.0% when pulling 6b0888b9151d03db9700f9a599ac0f30db39642b on conform-to-gopath-standard into c454953f02c7e77463fd3606705ee0bf4c75bf96 on master.