-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Graffiti hex support #8894
Graffiti hex support #8894
Conversation
This doesn't seem to be covered by any test case. Also I am not that big of a fan of |
So the "whatever" isn't actually what you'll get as an output, I just used it as a stand in. For example, if you put "hex:test 123", the graffiti used by the validator will be "hex:test 123", apologies for the lack of clarity here |
Thanks for addressing my comments @d00medman. You need to run |
PTAL @rkapka |
… graffiti-hex-support
E2E is currently failing with the following error:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please address e2e failure
… graffiti-hex-support
…rysm into graffiti-hex-support
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just some drive-by nits, feel free to ignore
Looks like some build failures:
|
It is unclear to me why the e2e test is failing; eyeball test alone is not doing the trick. I have thus far been unsuccessful in running this suite locally, any help in doing so would be very helpful. |
Its failing to write the correct graffiti. You also have unit test failures. I imagine that if you fix the issues causing failures in the unit test, then you'll also fix the issue in the e2e tests. |
E2E is failing for this error
|
The e2e test is supposed to use a random graffiti, and i see that this block had no graffiti.
|
Without changing the unit tests, if you can make all of |
Codecov Report
@@ Coverage Diff @@
## develop #8894 +/- ##
===========================================
- Coverage 60.78% 60.77% -0.02%
===========================================
Files 531 531
Lines 37862 37883 +21
===========================================
+ Hits 23015 23022 +7
- Misses 11567 11579 +12
- Partials 3280 3282 +2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work! Thanks so much
What type of PR is this?
Feature
What does this PR do? Why is it needed?
When a user provides a string prefixed with "hex:" followed by a hexidecimal string, this change will cause that piece of graffiti to be converted to ascii characters. It was deemed a reasonable feature for the system to have
Which issues(s) does this PR fix?
Fixes #8168
Other notes for review
Performs the conversion to ascii at startup; original value of yaml file captured by the hash field of the graffiti struct. Opted to make conversion errors non-blocking, when this happens the graffiti will be "hex:whatever"