Add emv config diagnosis to the configure step #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dorezyuk
reviewed
Jan 14, 2025
Signed-off-by: Daniel-Jenkins <[email protected]>
Signed-off-by: Daniel-Jenkins <[email protected]>
d-r-jenkins
force-pushed
the
add_emv_config_diagnosis_to_the_configure_step
branch
from
3fe365d to
e6859df
Compare
dorezyuk
reviewed
Jan 14, 2025
Signed-off-by: Daniel-Jenkins <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The EMV diagnosis needs to be run whenever the TID changes, as there are per-TID settings set by the provider (entities such as Lavego) which are pulled by this. This PR adds this.
This also adds a
.bazelversionfile for ease of use for those who use bazelisk.