Kerollmops
fa5f8f9531
Fix an issue with the update loop falsely breaking
2021-07-01 14:53:31 +02:00
bors[bot]
768987583a
Merge #1428
...
1428: Accept any content type as json r=curquiza a=irevoire
Co-authored-by: Tamo <tamo@meilisearch.com>
2021-06-30 18:29:57 +00:00
Tamo
a95c44193d
Do not block when sending update notifications
2021-06-30 17:29:22 +02:00
Tamo
2830853665
accept any content type as json
2021-06-30 17:05:59 +02:00
Tamo
29bf6a8d42
run rustfmt one the whole project and add it to the CI
2021-06-29 15:25:18 +02:00
Tamo
fe7640555d
fix the content-type
2021-06-29 13:16:56 +02:00
Tamo
1dc99ea451
accept no content-type as json
2021-06-29 11:59:25 +02:00
bors[bot]
f12ace3fbf
Merge #256
...
256: Update heed and milli r=irevoire a=curquiza
Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>
2021-06-29 08:49:22 +00:00
Clémentine Urquizar
c09e610bb5
Update heed and milli
2021-06-29 10:25:47 +02:00
bors[bot]
712abf4c5f
Merge #246
...
246: Stop logging the no space left on device error r=curquiza a=irevoire
closes #208
@qdequele what do you think of that?
Are there any other errors we need to ignore?
As you can see in the code, once we are in `Sentry` the error has already been converted to a `String` so the only thing we can do to see if we need to send the error or not is to match the `String` against our error message.
If we have a lot of other logs we want to ignore I would suggest prefixing all the logs with something like:
```
User error: No space left on device
```
So in Sentry, we could just check if the log start by `User error:` and ignore all these errors at once
Co-authored-by: Tamo <tamo@meilisearch.com>
2021-06-29 08:20:49 +00:00
Tamo
a59f437ee3
use only half of the computer threads for the indexation by default
2021-06-28 14:35:50 +02:00
Tamo
d74c698adc
stop logging the no space left on device error
2021-06-28 13:59:48 +02:00
Tamo
c1c50f6714
unused borrow that must be used
2021-06-28 13:35:25 +02:00
marin postma
01b09c065b
change route to service<resource>
2021-06-24 19:02:28 +02:00
marin postma
3b601f615a
declare new authentication related errors
2021-06-24 16:53:20 +02:00
marin postma
fbd58f2eec
clippy
2021-06-24 16:36:22 +02:00
marin postma
79fc3bb84e
fmt
2021-06-24 16:36:22 +02:00
marin postma
8e4928c7ea
fix tests
2021-06-24 16:36:22 +02:00
marin postma
d078cbf39b
remove authentication middleware
2021-06-24 16:36:21 +02:00
marin postma
561596d8bc
update stats routes
2021-06-24 16:36:18 +02:00
marin postma
549b489c8a
update settings routes
2021-06-24 16:35:48 +02:00
marin postma
1e9f374ff8
update running route
2021-06-24 16:35:12 +02:00
marin postma
817fcfdd88
update keys route
2021-06-24 16:35:12 +02:00
marin postma
fab50256bc
update index routes
2021-06-24 16:35:04 +02:00
marin postma
b044608b25
update health route
2021-06-24 16:32:45 +02:00
marin postma
ce4fb8ce20
update dump route
2021-06-24 16:32:43 +02:00
marin postma
adf91d286b
update documents and search routes
2021-06-24 16:32:15 +02:00
marin postma
0c1c7a3dd9
implement authentication policies
2021-06-24 16:31:30 +02:00
marin postma
5b71751391
policies macros
2021-06-24 16:31:30 +02:00
marin postma
12f6709e1c
move authencation to extractor mod
2021-06-24 16:31:28 +02:00
marin postma
5229f1e220
experimental auth extractor
2021-06-24 16:30:15 +02:00
bors[bot]
b6ca7929eb
Merge #240
...
240: Rework error messages r=irevoire a=MarinPostma
Simplify the error messages, and make them more compliant with legacy Meilisearch.
Basically, stop composing the messages, and simply forward the message of inner errors.
Co-authored-by: marin postma <postma.marin@protonmail.com>
2021-06-24 11:36:11 +00:00
Tamo
ad8d9a97d6
debug the body of every http request
2021-06-24 11:22:11 +02:00
Tamo
36f32f58d4
add the log_level variable to the cli and reduce the log level of milli and grenad
2021-06-24 11:20:52 +02:00
Tamo
b4fd4212ad
reduce the log level of some info!
2021-06-24 11:20:52 +02:00
marin postma
a1d34faaad
decompose error messages
2021-06-24 10:57:28 +02:00
bors[bot]
a2368db154
Merge #239
...
239: Bump milli to 0.6.0 r=MarinPostma a=MarinPostma
fix #231
Co-authored-by: marin postma <postma.marin@protonmail.com>
2021-06-24 08:08:41 +00:00
marin postma
74bb748a4e
bump milli to 0.6.0
2021-06-23 18:40:19 +02:00
bors[bot]
8638c9ab77
Merge #232
...
232: Fix payload size limit r=MarinPostma a=MarinPostma
Fix #223
This was due to the fact that Payload ignores the limit payload size limit. I fixed it by implementing my own `Payload` extractor that checks that the size of the payload is not too large.
I also refactored the `create_app` a bit.
Co-authored-by: marin postma <postma.marin@protonmail.com>
2021-06-23 16:06:08 +00:00
bors[bot]
b676b10cfe
Merge #238
...
238: Fix settings subroutes get r=MarinPostma a=MarinPostma
Fix #225
Co-authored-by: marin postma <postma.marin@protonmail.com>
2021-06-23 15:45:50 +00:00
marin postma
f68c257452
move flush in write_to_file function
2021-06-23 16:49:25 +02:00
marin postma
880fc069bd
remove dbg
2021-06-23 16:49:25 +02:00
marin postma
a838238a63
move payload to own module
2021-06-23 16:49:25 +02:00
marin postma
834995b130
clippy + fmt
2021-06-23 16:49:23 +02:00
marin postma
b000ae7614
remove file if write to update file fails
2021-06-23 16:48:33 +02:00
marin postma
f62779671b
change error message for payload size limit
2021-06-23 16:48:33 +02:00
marin postma
4b292c6e9b
add payload limit to app config
2021-06-23 16:48:33 +02:00
marin postma
1c13100948
implement custom payload
2021-06-23 16:48:31 +02:00
marin postma
71226feb74
refactor create_app macro
2021-06-23 16:47:15 +02:00
bors[bot]
3175f09989
Merge #235
...
235: Fix dump not found error r=MarinPostma a=MarinPostma
fix #233
Co-authored-by: marin postma <postma.marin@protonmail.com>
2021-06-23 14:21:07 +00:00
