-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove unneeded base64 encoders #128
Conversation
// 000000|00 0000|0000 00|000000| 000000|00 0000|0000 00|000000| | ||
// Char1 Char2 Char3 Char4 | ||
// See the above, the first byte has a character beginning at index 0, the second byte has a character beginning at index 4, the third byte has a character beginning at index 2 and then the pattern repeats | ||
// We register byte offsets for all these possible values | ||
public static String Base64StringEscapeShift1(String value) |
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.
should we keep 0/2/4? not 0/1/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.
Right, I thought it was the even bit shifts ...
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.
it should be 0/1/2, since it's byte... not bit...
the shift is for shifting bytes.
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.
I added an L0 for this: #129
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.
I added a Server side pr with tests as well!
The ticket has information on why these shifts were selected!
* Remove unneeded base64 encoders * update comment
Allow runner_org to be provided as string.
Context
Server PR with test!
Essentially, these extra encoders weren't really doing anything besides slowing down compute, so we are safe to remove them.