mirror of
https://github.com/zulip/zulip.git
synced 2026-06-24 21:08:25 +08:00
2b4faaa847
For filters like has:link, where the web app doesn't necessarily want to guess whether incoming messages meet the criteria of the filter, the server is asked to query rows that match the query. Usually these queries are search queries, which have fields for content_matches and subject_matches. Our logic was handling those correctly. Non-search queries were throwing an exception related to tuple unpacking. Now we recognize when those fields are absent and do the proper thing. There are probably situations where the web app should stop hitting this endpoint and just use its own filters. We are making the most defensive fix first. Fixes #6118 |
||
|---|---|---|
| .. | ||
| fixtures | ||
| lib | ||
| management | ||
| migrations | ||
| templatetags | ||
| tests | ||
| tornado | ||
| views | ||
| webhooks | ||
| worker | ||
| __init__.py | ||
| apps.py | ||
| context_processors.py | ||
| decorator.py | ||
| filters.py | ||
| forms.py | ||
| logging_handlers.py | ||
| middleware.py | ||
| models.py | ||
| signals.py | ||
| static_header.txt | ||
| storage.py | ||