| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* materialize PublicChannels table
Introduce triggers for each supported database that automatically maintain a subset of the Channels table corresponding to only public channels. This improves corresponding queries that no longer need to filter out 99% DM channels.
This initial commit modifies the channel store directly for easier code reviewing, but the next wraps an experimental version around it to enable a kill switch in case there are unforeseen performance regressions.
This addresses [MM-11886](https://mattermost.atlassian.net/browse/MM-11886) and [MM-11945](https://mattermost.atlassian.net/browse/MM-11945).
* extract the experimental public channels materialization
Wrap the original channel store with an experimental version that
leverages the materialized public channels, but can be disabled to
fallback to the original implementation.
This addresses MM-11947.
* s/ExperimentalPublicChannelsMaterialization/EnablePublicChannelsMaterialization/
* simplify error handling
* move experimental config listener until after store is initialized
|
| |
| |
| |
| | |
Also add additional unit tests to make sure the permissions tests are
completely solid.
|
|\| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Minor grammar & spelling fixes
Minor grammar & spelling fixes
* Harmonizing error messages
First step to harmonize the error messges by using three formulations
that basically mean the same.
* Changed string after feedback.
* Change after feedback
* Removed typo
Head hit keyboard or something...
* Updated second occurence of an already changed string
Changed ssecond occurence of "Unable to know if the file exists. An error ocurred when trying to check file existence."
|
|\| |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This fixes an issue where the cached Channel objects would contain data
from a failed update when the update to the database failed.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
* MM-11855 Add App.HTTPService to allow mocking of HTTP client
* Initialize HTTPService earlier
|
| | |
|
| |
| |
| |
| |
| |
| | |
* Add preparatory upgrade code for 5.4.0
* add migration from bad merge
|
|\|
| |
| |
| | |
release-5.3-daily-merge-20180904
|
| |
| |
| |
| |
| |
| | |
* Uncomment upgrade for 5.3.0
* add missing version
|
| |
| |
| | |
There are numerous issues here, including some non-determinism in the viper library (fixable) and some annoying behaviour regarding periods in keys, often used by plugin ids (fix unknown). Let's defer the handling of same until we can get our config loading library to do what we need it to do vs. having to hack around viper all the time.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(#9265)
* MM-11703: Update incoming and outgoing webhook description to 500 characters
* MM-11703: Add upgrade code
* MM-11703: Remove MAX_DESCRIPTION_LENGTH constants
* MM-11703: GOFMT
* MM-11703: Move upgrade code to version 5.3
* MM-11703: Comment back upgrade to 5.3.0
* MM-11703: Add API errors back
* MM-11703: Copy-Paste
|
|\ \ |
|
|/| |
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Allow connetions to /plugins for interactive message buttons.
* Adding siteurl to exclusions for AllowedUntrustedInternalConnections
* Adding subpath support for allowing interactive message buttons plugin connections.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix code issues in channel_test.go
Fix Channel Test Issues detected by Megacheck
Fix API Emoji Test Issues detected by Megacheck
Fixed API Issues Reported by Megacheck
Fixed App issues reported by megacheck
Remaining fixes
removed test added by mistake from old HEAD
gofmt
Store Fixes
simplified returns
Fix test for multi member channel delete
revert to delete unused function
|
| |
|
|
|
|
|
|
|
|
| |
* Invalidate store cache after making changes
* Address feedback
* Make cache invalidation in stores always use defer
|
|
|
|
| |
channel for email subject (#9314)
|
|
|
|
|
|
|
|
| |
selected date (#9327)
* fix for date based flag support to make the after and before flags not inclusive of the selected date
* updated search posts tests using date flags to take into account new non inclusive of the selected date behavior of those flags
|
| |
|
| |
|
|
|
|
|
|
| |
* add --username in the example for the commands
* update per review
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* initial implementation of after, before, on search flags allowing to restrict the search to a specific day or a date range
* missed setting beforeDate in SearchParams in one place
* fixed condition when only flags are used for search without any plain terms
* changed date format used for after/before/on flags to be in ISO8601 format as suggested in PR comments, added a helper function to pad month and day with zeroes allowing the user user either format, with or without leading zeroes
* corrected expected compare to date setting for the TestParseDateFilterToTimeISO8601 test
* fixed a bug for the scenario when you only have the date flags without any terms, added a couple of tests for that scenario
* updated the date filter logic to use parameters to construct the query instead of simply appending strings together, as suggested in the pull request comments
* added search unit test using date flags
* added a helper function to create a test post with a createat date manually set, updated the test for search using date flags to create test posts with different createat dates to be able to better test the functionality
* MM-11817 Add support for after/before/on search flags with Elasticsearch
* add support to search posts to perform the search in context of the client's timezone when filtering by createat date using on: after: before: flags
* updated tests to match the new signature
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Check a team's AllowedDomains setting before adding users to the team.
* Updated AddUser tests to validate AllowedDomains restriction.
* Updated variable name to match convention.
* Removed AllowedDomains from team sanitization.
* Update AppError's Where to match the calling function.
* Added tests for user matching allowedDomains, and multi domain values of allowedDomains.
* Added test to make sure we block users who have a subdomain of a whitelisted domain.
* Revert "Removed AllowedDomains from team sanitization."
This reverts commit 17c2afea584da40c7d769787ae86408e9700510c.
* Update sanitization tests to include dockerhost, now that we enforce AllowedDomains.
* Added tests to verify the interplay between the global and per team domain restrictions.
* Validate AllowedDomains property against RestrictCreationToDomains before updating a team.
* Remove team.AllowedDomains from sanitization.
* Add i18n string for the team allowed domains restriction app error.
|
|
|
|
|
|
|
|
| |
* Adding IdAttribute setting for SAML
* Adding Saml Id Attribute to the diagnostics information
* Adding entry to default.json
|
|
|
| |
"id": "plugin.api.update_user_status.bad_status",Unable to set the user statys. Unknown user status.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|