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

Merge develop into master #408

Open
wants to merge 25 commits into
base: master
Choose a base branch
from
Open

Merge develop into master #408

wants to merge 25 commits into from

Conversation

niczem
Copy link
Contributor

@niczem niczem commented Jul 8, 2020

contains:
#335
#389
#343
#402

xmacex and others added 25 commits October 2, 2018 01:36
…new bin, both at the web UI and further down the stack.
… to throw an exception in addition to an error message for humans. This is a risky move up the stack I might think, if it is not caught under normal operations.
… to throw an exception in addition to an error message for humans. This is a risky move up the stack I might think, if it is not caught under normal operations.
… procrastination commit under cognitive stress of getting all the tests in place. Please bear with me.
…ctionality in modify_bin() too. On the UI side the same validateQuery() is used as when making a new bin, so I that should be fine.
…ing on a more substantial task of adding tests in TDD style. Feedback provided by PHP Code Sniffer with default settings.
…ong because there is too much whitespace in the middle of it.
…e format familiar from the Twitter UI with disjunctions marked by ' OR ' instead of the comma ',' as the query bin manager thing on TCAT. Updated tests pass (hmm how can I have a test suite that I can commit to, but that does not get pushed to the repo? Maybe a separate project outside of the dmi-tcat top directory or something. Anyway...).
Sometimes deleting large query bins can fail or timeout, removing
the tweet tables but not the entry from the bins table. This
results in the app crashing when accessing the capture page.

This change attempts to prevent this by a) putting deletion
operations in a single transaction and b) catching errors when
retrieving bin info. The latter change is required because MySQL
does not do schema changes such as table deletion in transactions
so the problem with incomplete bin removal can still occur.
Attempt to make bin removal and info lookup more robust.
Consider all DB-collations beginning w/ 'utf8mb4' to be utf8mb4 collations
Removed recursive call to search
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

Successfully merging this pull request may close these issues.

5 participants