Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download and compile model function fix #208

Merged
merged 2 commits into from
Aug 18, 2020
Merged

Download and compile model function fix #208

merged 2 commits into from
Aug 18, 2020

Conversation

jaimejiyepark
Copy link
Collaborator

@jaimejiyepark jaimejiyepark commented Aug 17, 2020

the downloaded task's temporary location gets emptied when the completion handler completes so the ml model compiling has to be done in the same function.

DispatchQueue.main.async {
completion(["mlmodel_url": location], nil)
completion(["compiled_model_url": compiledUrl], nil)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will changing this break any existing code? I couldn't find anything referencing this string, is it used anywhere?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this function is used in model updates in cardverify

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, so there will be a corresponding change in CardVerify here? makes sense, although this is breaking. Do we have any way of indicating which versions of CardVerify are compatible with which versions of CardScan?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes that is correct. We indicate compatibility in the cardverify podspec file, where cardverify's version dependency of cardscan is stated.

@jaimejiyepark
Copy link
Collaborator Author

i can use an @available attribute to indicate deprecation but im not sure if this change is it worth it since its only been used internally. but im not sure, what do you think @awushensky?

@awushensky
Copy link
Contributor

awushensky commented Aug 17, 2020

@jaimejiyepark In this case, let's skip it. For future changes that introduce new APIs that are not ready for public consumption, let's mark them as @available to indicate that they are experimental features that could change.

@jaimejiyepark jaimejiyepark merged commit edf26f0 into master Aug 18, 2020
@jaimejiyepark jaimejiyepark deleted the api_fix branch August 18, 2020 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants