Skip to content

Fix vector get application config#977

Merged
zariiii9003 merged 9 commits into
hardbyte:developfrom
danielhrisca:fix_vector_get_application_config
Jan 10, 2022
Merged

Fix vector get application config#977
zariiii9003 merged 9 commits into
hardbyte:developfrom
danielhrisca:fix_vector_get_application_config

Conversation

@danielhrisca

Copy link
Copy Markdown
Contributor

No description provided.

@mergify mergify Bot requested a review from hardbyte February 9, 2021 16:31
@codecov

codecov Bot commented Apr 9, 2021

Copy link
Copy Markdown

Codecov Report

Merging #977 (18726a2) into develop (291af86) will increase coverage by 0.16%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #977      +/-   ##
===========================================
+ Coverage    70.12%   70.28%   +0.16%     
===========================================
  Files           76       76              
  Lines         7381     7398      +17     
===========================================
+ Hits          5176     5200      +24     
+ Misses        2205     2198       -7     

@felixdivo

Copy link
Copy Markdown
Collaborator

Hey @danielhrisca what problem does this PR try to solve? I don't quite get it. Was the value just not wrapped into a c_uint? Was it tested on real hardware? If yes, IMHO this can be merged.

@zariiii9003

Copy link
Copy Markdown
Collaborator

@felixdivo i assume this solves #971

@danielhrisca

Copy link
Copy Markdown
Contributor Author

I think it was related to using the udsoncan package. I will check tomorrow

@zariiii9003

zariiii9003 commented Apr 18, 2021

Copy link
Copy Markdown
Collaborator

The ctypes documentation says

Python integers are passed as the platforms default C int type, their value is masked to fit into the C type.

So while using app_channel = ctypes.c_uint(app_channel) is technically correct it should not make a difference unless app_channel is greater than 2147483647 (2^31 - 1).
@danielhrisca did you see any difference with your version?

@felixdivo

Copy link
Copy Markdown
Collaborator

Can someone test this change locally?

@felixdivo

Copy link
Copy Markdown
Collaborator

@zariiii9003 Shall we merge this an close #971?

@zariiii9003

Copy link
Copy Markdown
Collaborator

I would say we can merge this, but not close the issue you mentioned. I'm not sure if this fixes anything, but i'm very confident that it does not break anything.

Let's wait and see if someone else has similar problems once we release version 4.

@zariiii9003 zariiii9003 merged commit 2e24af0 into hardbyte:develop Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants