Skip to content
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

Backslashes in triggers are wonky #93

Open
dgw opened this issue Feb 8, 2017 · 1 comment
Open

Backslashes in triggers are wonky #93

dgw opened this issue Feb 8, 2017 · 1 comment
Assignees

Comments

@dgw
Copy link
Collaborator

dgw commented Feb 8, 2017

This kind of thing tells me that Bucket is inconsistent about escaping its input:

<Bucket> dgw aliased in #channel 'o\\\o' to 'o///o'
<Bucket> DB Error:  -> Duplicate entry 'o\\\o-o///o-<alias>' for key 'fact'
<dgw> Bucket, literal o\\\o
<Bucket> [a "don't know" response]
<dgw> Bucket: literal o\\\\\\o
<Bucket> o\\\o (=> o///o) (#7114) [-truncated-]

When teaching, backslashes are interpreted as-written, escaped as needed to be inserted in the database.

When looking up factoids, the necessary escaping is not happening. When given o\\\o, Bucket is actually trying to look up o\o:

<dgw> Bucket, alias o\o => o\\\o
<Bucket> Okay, dgw.
<dgw> Bucket: literal o\\\o
<Bucket> o\o (=> o///o) (#7114) [-truncated again-]
@dgw
Copy link
Collaborator Author

dgw commented Sep 29, 2017

Self-assigning—potential Hacktoberfest work item.

@dgw dgw self-assigned this Sep 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant