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
PR - Fixing 4-byte UTF-8 character validation #2840
Comments
Comment from mreynolds (@mreynolds389) at 2018-06-14 21:23:15 Thanks for the contribution @djpadz! This looks good to me, can you rebase it with master branch? |
Comment from djpadz at 2018-06-14 21:26:09 Done. |
Comment from djpadz at 2018-06-14 21:26:23 rebased onto 2707e39 |
Comment from djpadz at 2018-06-14 21:26:41 Do you need a test for this? |
Comment from mreynolds (@mreynolds389) at 2018-06-14 21:29:51 You read my mind :-) Yes if you have a test (written in python-lib389), or even just the exact manual steps to reproduce, that would be great. |
Comment from djpadz at 2018-06-14 21:30:07 Okeedoke. I'll work on that :-) |
Comment from mreynolds (@mreynolds389) at 2018-06-14 21:30:49 What version of 389-ds-base are you using/need this fixed in? |
Comment from djpadz at 2018-06-14 21:33:10 We're using it with 1.2.11.15-94.el6_9, but the backport was (obviously) easy. I'm hoping to get the servers up to EL 7 before we go live with it. I'm not sure what version is in the repos for el7. |
Comment from djpadz at 2018-06-15 04:10:15 1 new commit added
|
Comment from djpadz at 2018-06-15 04:12:07 @mreynolds389 - I've pushed a test, but I can't seem to get it to run. I suspect it's something environmental, since none of the tests that call modify_s() are working. In any case, here's the output. Any advice would really be appreciated. I'm running this on a clean install of Fedora 28.
|
Comment from vashirov (@vashirov) at 2018-06-15 07:01:51
You're trying to replace |
Comment from djpadz at 2018-06-15 07:41:21 1 new commit added
|
Comment from djpadz at 2018-06-15 07:41:58 omg... I can't believe I missed that! Thanks, @vashirov! It's now fixed. |
Comment from djpadz at 2018-06-15 09:54:10 @mreynolds389 would you like PRs for each of the release branches as well? |
Comment from djpadz at 2018-06-17 19:51:54 Filed 49788 so the test can be common to all branches. |
Comment from djpadz at 2018-06-17 19:54:39 2 new commits added
|
Comment from mreynolds (@mreynolds389) at 2018-06-18 20:14:36 Pull-Request has been merged by mreynolds389 |
Comment from mreynolds (@mreynolds389) at 2018-06-18 20:30:24 @djpadz cherry picked the fixes to all the branches (even 1.2.11 - although we are not building it anymore) |
Comment from djpadz at 2018-06-18 20:31:59 @mreynolds389 The fix isn't exactly the same between versions... I mean, it's still |
Comment from mreynolds (@mreynolds389) at 2018-06-18 20:33:28 Its already done, are you saying my cherry-picks were wrong? |
Comment from djpadz at 2018-06-18 20:34:11 Oh, I hadn't looked at them. If you ended up putting them into the right places (it's pretty obvious where they go), then you're good. :-) |
Comment from mreynolds (@mreynolds389) at 2018-06-18 20:35:56 Only applying to 1.2.11 gave me problems, but it looks right to me. Do a "git pull" and check :-) |
Comment from djpadz at 2018-06-18 20:37:42 Just did a spot-check, and it looks good :-) |
Comment from mreynolds (@mreynolds389) at 2018-06-18 20:39:56 Thanks again for the contribution!! |
Patch |
Cloned from Pagure Pull-Request: https://pagure.io/389-ds-base/pull-request/49781
When validating syntax for four-byte UTF-8 characters, the pointer wasn't being advanced, which was causing false syntax validation failures for directory strings that, for example, included pictographs.
The text was updated successfully, but these errors were encountered: