Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

KEYCLOAK-14316 Fix "assignment to entry in nil map" error #229

Merged

Conversation

slaskawi
Copy link
Contributor

JIRA ID

https://issues.redhat.com/browse/KEYCLOAK-14316

Additional Information

Checklist:

@slaskawi slaskawi requested a review from mhajas July 13, 2020 12:27
@coveralls
Copy link

coveralls commented Jul 13, 2020

Coverage Status

Coverage increased (+0.008%) to 43.816% when pulling d5b4fda on slaskawi:KEYCLOAK-14316-Fix-nil-map-assignment-error into 5ab2e91 on keycloak:master.

@slaskawi slaskawi requested a review from abstractj July 15, 2020 14:05
@slaskawi slaskawi force-pushed the KEYCLOAK-14316-Fix-nil-map-assignment-error branch from 3489d55 to d5b4fda Compare July 20, 2020 10:59
@abstractj abstractj requested a review from ASzc August 4, 2020 13:50
Copy link
Contributor

@ASzc ASzc left a comment

Choose a reason for hiding this comment

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

Seems from here the built in casting for golang will correctly handle unicode in both directions, so that's ok. It cautions against trying to perform operations on the byte[], as your code would break with unicode multi-byte characters. I don't see any problems like that in this PR.

@slaskawi
Copy link
Contributor Author

@abstractj May I ask you to review and merge this one (already approved by @ASzc).

Copy link
Contributor

@abstractj abstractj left a comment

Choose a reason for hiding this comment

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

@slaskawi approving based on @ASzc review.

@slaskawi slaskawi merged commit 3578a52 into keycloak:master Aug 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants