| Commit message (Collapse) | Author | Age | Lines |
... | |
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This was changed due to performance reasons, but after some tweaking in the database, such as increasing work memory and adding an index, this query runs much faster now.
To test this, I want to revert this change, so that we can stop the materialised view from refreshing, to see if the act of refreshing is what's causing this query to seem faster when runing against the database.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Bump drf up to 3.12.0
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
This is to add support for Django 3.1's database-agnositic JSONField.
|
| | | | | |
|
| |\ \ \ \
| |/ / / /
|/| | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Bump django from 3.1.13 to 3.1.14
|
| |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use new approx message count view
|
| |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We have added a new view to metricity that will keep track of an approximate message count, updating every 10 seconds.
By doing this, we avoid running a query against the whole message table every time we want to get a user's messages.
|
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bumps [django](https://github.com/django/django) from 3.1.13 to 3.1.14.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/3.1.13...3.1.14)
---
updated-dependencies:
- dependency-name: django
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <[email protected]>
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Bump django from 3.0.14 to 3.1.13
|
| |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \ |
|
|/ / / / / / |
|
| | | | | | |
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bumps [django](https://github.com/django/django) from 3.0.14 to 3.1.13.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/3.0.14...3.1.13)
---
updated-dependencies:
- dependency-name: django
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <[email protected]>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Clean Up Static Deployment Docs
|
| | | | | |
| | | | | |
| | | | | | |
Reorganize the static deploy readme, and clarify the content.
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Create a signal to unassign roles from user when the role is deleted
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
From now on the signal will only get executed after the Role has been deleted
The commit also introduces minor changes in the tests of roles
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Create a test that checks if a role gets deleted it will also get unassigned from the user
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Add a signal to the api app that automatically unassigns
deleted roles from users that have them
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Improve Gitpod section in Sir Lancebot contributing guide
|
| |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Adds Redirects To Static Builds
|
| |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
|\ \ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Alter message query to leverage index
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously this query would convert each row to an array just to check if it matched or not. By changing EXCLUDE_CHANNELS to a tuple instead of a list, it doesn't get passed as an array, so we can do a simple NOT IN check.
This will also allow us to add an index with this condition to speed it up further.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Don't always calc activity blocks
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We only actually care that thee key:value pairs are equal, the order of them isn't actually important.
The naming of `assertCountEqual` is a little misleading, since it actually tests that the first sequence contains the same elements as second, regardless of their order. See https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertCountEqual
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We only truly care about how many activity blocks a user has when they have a small number of messages, as we only use this for the voice gate.
If a user has more than say 1k messages, then we really don't need to calculate their activity blocks, as it's quite an expensive query with many messages.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Adds Redirect Filter List
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Adds a new filter list for URLs which should be treated as
redirects and unfurled.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Dynamically adds static HTML redirects for static builds.
Signed-off-by: Hassan Abouelela <[email protected]>
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- Add newlines so it's not a big unfriendly paragraph
- Fix gitpod workspace link
- Clarification on terminal commands
- Clarification on test server and bot
- Add links for that ^ and for environment variables
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|