Patchwork: Corrupt tag names on completion box

[ivilata]

I came across a weird behaviour in Patchwork 3.12.0 (also present in 3.14.1). When I hit the Tags button in a message and start writing the name of a tag, I only get mangled, randomish 9-character tags which look like truncated Base64 text. All completions look like that, tags that I see in other posts or tags that I already used are not among completions either (or maybe they are under a mangled name since some bogus completions show a positive count). Tags already applied to the post show fine, but they don't show up in the completion box either.

I’m not sure if this will be related with #1037 that @christianbundy answered to (I noticed the same slowdown there), and I found no other similar reported issues.

[christianbundy]

Hey, just wanted to let you know that your issue is seen and understood. Sorry this is causing trouble for you. I don't really know how the tags code works, and I don't think anyone does (yet!). I've got some other things on my plate right now so I don't have the bandwidth to look into it, but I appreciate you taking the time to make an issue for this bug. I'll update you when I have time to debug and resolve this. Thanks!

On Thu, Jun 20, 2019, at 18:09, Ivan Vilata-i-Balaguer wrote:

I came across a weird behaviour in Patchwork 3.12.0 (also present in 3.14.1). When I hit the Tags button in a message and start writing the name of a tag, I only get mangled, randomish 9-character tags which look like truncated Base64 text. All completions look like that, tags that I see in other posts or tags that I already used are not among completions either (or maybe they are under a mangled name since some bogus completions show a positive count). Tags already applied to the post show fine, but they don't show up in the completion box either.

I’m not sure if this will be related with #1037 https://github.com/ssbc/patchwork/issues/1037 that @christianbundy https://github.com/christianbundy answered to (I noticed the same slowdown there), and I found no other similar reported issues.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ssbc/patchwork/issues/1124?email_source=notifications&email_token=AAEDIZH46GPUGDG2TDXXB33P3QS4LA5CNFSM4H2FWQU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G23E4HA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEDIZBUCNPOTTEJF5IEWBLP3QS4LANCNFSM4H2FWQUQ.

[ivilata]

I checked and the issue is still present for me in 3.15.0.

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

[ivilata]

Still happening in 3.17.1. Is there anything I can run that involves cleaning up some cached items or something? Thanks!

[black-puppydog]

stumbled over this myself. seems similar to #930 ?

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

[black-puppydog]

I just had this again and after debugging a bit for #1037 I think this is related; after I specifically opened the tags page and let the in-memory representation of all tags be loaded, the suggestions started working fine.

[ivilata]

@black-puppydog I can reproduce the behavior that you mention in 3.18.0: tags appear mangled, then I visit the Tags page, let tags load, then go back to whatever page I was in and voilà, completion shows correct tag names again.

Thanks for the workaround! :smile: