-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Error with forked repo without changes. #653
Comments
Hello @carlosb1. Don't forget to add the Header to say that you're sending json body. |
Thanks! it works with the v0.10.1 I will use it temporally. also thanks for the fast feedback |
@carlosb1 Did you try the quentin's response? Does it work? |
@Kerollmops I didn t need to include -H in the curl command... Directly, I changed branch... I can try to use master and the json flag if I have a gap. |
653: Fix #652 - Change Spelling of `author` in `README.md` r=curquiza a=anirudhRowjee # Pull Request ## What does this PR do? Fixes #652 - Changes spellings of `au{hor` to `author` - Minor formatting changes in Markdown ## PR checklist Please check if your PR fulfills the following requirements: - [x] Does this PR fix an existing issue? - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes? Co-authored-by: Anirudh Rowjee <ani.rowjee@gmail.com>
Hi,
these last days I has been working with meilisearch to index information and links from Internet... It works perfectly when I run the docker (compiled) image but I can not use a forked version (no modified) from this repo... I only forked it a few days ago and I ran
cargo run --release
. But when I execute the index command:It doesn t work... it is curious, it is the same command that it works with the docker image... I have tired different things: remove caches, rebuilding, remove data.ms, run from docker or cargo... but same result... I will appreciate any help, the only reply that I receive from meilisearch:
[2020-05-03T14:31:31Z INFO actix_web::middleware::logger] 127.0.0.1:50760 "POST /indexes HTTP/1.1" 400 0 "-" "curl/7.58.0" 0.000170
The text was updated successfully, but these errors were encountered: